User equipment, base station and method for configurable downlink control information of demodulation reference signal for physical downlink shared channel

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a demodulation reference signal (DMRS) for a physical downlink shared channel (PDSCH). When the number of bits of downlink control information (DCI) for indicating DMRS sequence initialization is 1 bit, a sequence of the DMRS for the PDSCH is generated based on a value indicated by the DCI for indicating DMRS sequence initialization. The value is between a value of a first scrambling identifier (ID) and a value of a second scrambling ID. When the number of bits of the DCI for indicating DMRS sequence initialization is 0 bit, the sequence of the DMRS for the PDSCH is generated based on a value of a third scrambling ID.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems and more particularly to a user equipment (UE), a base station and a method for configurable downlink control information for a demodulation reference signal of a physical uplink shared channel. Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage areas, and enhanced functionality. A wireless communication system may provide communication for multiple wireless communication devices, each of which may be served by a base station. A base station may be a device that communicates with a wireless communication device.

[0003] With the development of wireless communication equipment, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.

[0004] For example, a wireless communication device may communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the invention

[0005] In one example, a user equipment (UE) includes: a receiving circuit configured to receive a radio resource control (RRC) message, the RRC message including first information indicating a value of a first scrambling identifier (ID), second information indicating a value of a second scrambling ID, and third information indicating a value of a third scrambling ID; the receiving circuit is configured to receive a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate a demodulation reference signal (DMRS) sequence initialization, the DCI format being used to schedule a physical downlink co-location. the receiving circuit being configured to receive the DMRS for the PDSCH, wherein when the number of bits of the DCI for indicating the initialization of the DMRS sequence is 1 bit, the sequence of the DMRS for the PDSCH is generated based on a value indicated by the DCI for indicating the initialization of the DMRS sequence, the value being between the value of the first scrambling ID and the value of the second scrambling ID, and when the number of bits of the DCI for indicating the initialization of the DMRS sequence is 0 bit, the sequence of the DMRS for the PDSCH is generated based on the value of the third scrambling ID.

[0006] In one example, a base station device includes: a transmission circuit, the transmission circuit is configured to transmit a radio resource control (RRC) message, the RRC message including first information for indicating a value of a first scrambling identifier (ID), second information for indicating a value of a second scrambling ID, and third information for indicating a value of a third scrambling ID; the transmission circuit is configured to transmit a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate a demodulation reference signal (DMRS) sequence initialization, the DCI format being used to schedule a physical downlink shared signal a first scrambling ID and a second scrambling ID; and the transmission circuit is configured to transmit the DMRS for the PDSCH, wherein when the number of bits of the DCI for indicating the initialization of the DMRS sequence is 1 bit, the sequence of the DMRS for the PDSCH is generated based on a value indicated by the DCI for indicating the initialization of the DMRS sequence, the value being between the value of the first scrambling ID and the value of the second scrambling ID, and when the number of bits of the DCI for indicating the initialization of the DMRS sequence is 0 bit, the sequence of the DMRS for the PDSCH is generated based on the value of the third scrambling ID.

[0007] In one example, a communication method of a user equipment (UE) includes: receiving a radio resource control (RRC) message, the RRC message including first information for indicating a value of a first scrambling identifier (ID), second information for indicating a value of a second scrambling ID, and third information for indicating a value of a third scrambling ID; receiving a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate a demodulation reference signal (DMRS) sequence initialization, the DCI format being used to schedule a physical downlink shared channel (PDCCH); DSCH); and receiving the DMRS for the PDSCH, wherein, in a case where the number of bits of the DCI for indicating the initialization of the DMRS sequence is 1 bit, the sequence of the DMRS for the PDSCH is generated based on a value indicated by the DCI for indicating the initialization of the DMRS sequence, the value being between the value of the first scrambling ID and the value of the second scrambling ID, and in a case where the number of bits of the DCI for indicating the initialization of the DMRS sequence is 0 bit, the sequence of the DMRS for the PDSCH is generated based on the value of the third scrambling ID.

[0008] In one example, a communication method of a base station device includes: transmitting a radio resource control (RRC) message, the RRC message including first information for indicating a value of a first scrambling identifier (ID), second information for indicating a value of a second scrambling ID, and third information for indicating a value of a third scrambling ID; transmitting a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate demodulation reference signal (DMRS) sequence initialization, the DCI format being used to schedule a physical downlink shared channel (PDSCH); and transmitting the DMRS for the PDSCH, wherein when the number of bits of the DCI for indicating the DMRS sequence initialization is 1 bit, the sequence of the DMRS for the PDSCH is generated based on a value indicated by the DCI for indicating the DMRS sequence initialization, the value being between the value of the first scrambling ID and the value of the second scrambling ID, and when the number of bits of the DCI for indicating the DMRS sequence initialization is 0 bit, the sequence of the DMRS for the PDSCH is generated based on the value of the third scrambling ID. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] [ Figure 1 ] Figure 1 is a block diagram illustrating one specific implementation of one or more gNBs and one or more UEs in which systems and methods for signaling may be implemented.

[0010] [ Figure 2 ] Figure 2 Examples of multiple parameters are shown.

[0011] [ Figure 3 ] Figure 3 is a diagram showing one example of a resource grid and resource blocks.

[0012] [ Figure 4 ] Figure 4 An example of a resource area is shown.

[0013] [ Figure 5 ] Figure 5 An example of downlink transmission is shown.

[0014] [ Figure 6 ] Figure 6 An example of uplink transmission is shown.

[0015] [ Figure 7 ] Figure 7 Various components that may be utilized in a UE are shown.

[0016] [ Figure 8 ] Figure 8 Various components that may be utilized in a gNB are shown.

[0017] [ Fig. 9 ] Fig. 9 is a block diagram illustrating one specific implementation of a UE in which one or more of the systems and / or methods described herein may be implemented.

[0018] [ Fig.10 ] Fig.10 is a block diagram illustrating one specific implementation of a gNB in ​​which one or more of the systems and / or methods described herein may be implemented.

[0019] [ Fig.11 ] Fig.11 is a block diagram illustrating a specific implementation of a gNB.

[0020] [ Fig.12 ] Fig.12 is a block diagram illustrating one specific implementation of a UE. DETAILED DESCRIPTION

[0021] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a radio resource control (RRC) message, the RRC message including first information for indicating a value of a first scrambling identity (ID), second information for indicating a value of a second scrambling ID, and third information for indicating a value of a third scrambling ID. The receiving circuit is further configured to receive a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate demodulation reference signal (DMRS) sequence initialization. The DCI format is used to schedule a physical downlink shared channel (PDSCH). The receiving circuit is further configured to receive a DMRS for PDSCH. When the number of bits of the DCI for indicating DMRS sequence initialization is 1 bit, a sequence of DMRS for PDSCH is generated based on the value indicated by the DCI for indicating DMRS sequence initialization. The value is between the value of the first scrambling ID and the value of the second scrambling ID. When the number of bits of the DCI for indicating DMRS sequence initialization is 0 bit, a sequence of DMRS for PDSCH is generated based on the value of the third scrambling ID.

[0022] The present invention also describes a base station device. The base station device includes a transmission circuit, which is configured to transmit a radio resource control (RRC) message, the RRC message including a first information indicating a value of a first scrambling identifier (ID), a second information indicating a value of a second scrambling ID, and a third information indicating a value of a third scrambling ID. The transmission circuit is further configured to transmit a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate demodulation reference signal (DMRS) sequence initialization. The DCI format is used to schedule a physical downlink shared channel (PDSCH). The transmission circuit is further configured to transmit a DMRS for PDSCH. When the number of bits of the DCI for indicating DMRS sequence initialization is 1 bit, a sequence of DMRS for PDSCH is generated based on the value indicated by the DCI for indicating DMRS sequence initialization. The value is between the value of the first scrambling ID and the value of the second scrambling ID. When the number of bits of the DCI for indicating DMRS sequence initialization is 0 bit, a sequence of DMRS for PDSCH is generated based on the value of the third scrambling ID.

[0023] The present invention describes a communication method of a user equipment (UE). The communication method includes receiving a radio resource control (RRC) message, the RRC message including first information for indicating the value of a first scrambling identity (ID), second information for indicating the value of a second scrambling ID, and third information for indicating the value of a third scrambling ID. The communication method also includes receiving a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate demodulation reference signal (DMRS) sequence initialization. The DCI format is used to schedule a physical downlink shared channel (PDSCH). The communication method also includes receiving a DMRS for PDSCH. When the number of bits of the DCI for indicating DMRS sequence initialization is 1 bit, a sequence of DMRS for PDSCH is generated based on the value indicated by the DCI for indicating DMRS sequence initialization. The value is between the value of the first scrambling ID and the value of the second scrambling ID. When the number of bits of the DCI for indicating DMRS sequence initialization is 0 bit, a sequence of DMRS for PDSCH is generated based on the value of the third scrambling ID.

[0024] The present invention describes a communication method for a base station device. The communication method includes: a transmission circuit is configured to transmit a radio resource control (RRC) message, the RRC message including first information for indicating the value of a first scrambling identifier (ID), second information for indicating the value of a second scrambling ID, and third information for indicating the value of a third scrambling ID. The communication method also includes transmitting a DCI format including downlink control information (DCI) on a physical downlink control channel (PDCCH), the DCI being used to indicate demodulation reference signal (DMRS) sequence initialization. The DCI format is used to schedule a physical downlink shared channel (PDSCH). The communication method also includes transmitting a DMRS for PDSCH. When the number of bits of the DCI for indicating DMRS sequence initialization is 1 bit, a sequence of DMRS for PDSCH is generated based on the value indicated by the DCI for indicating DMRS sequence initialization. The value is between the value of the first scrambling ID and the value of the second scrambling ID. When the number of bits of the DCI for indicating DMRS sequence initialization is 0 bit, a sequence of DMRS for PDSCH is generated based on the value of the third scrambling ID.

[0025] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that aims to develop globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems and devices.

[0026] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0027] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), 5G New Radio (5th Generation NR), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0028] A wireless communication device may be an electronic device that is used to transmit voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In the 3GPP specification, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device". UE may also be more generally referred to as a terminal device.

[0029] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a gNB, a home enhanced or evolved Node B (HeNB), or some other similar term. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station", "Node B", "eNB", "gNB", and "HeNB" may be used interchangeably herein to represent the more general term "base station". In addition, the term "base station" may be used to represent an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.

[0030] It should be noted that as used herein, a "cell (e.g., a serving cell)" may be any communication channel that is specified by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced) and all or a subset thereof, so that it is adopted by 3GPP as an authorized band (e.g., a frequency band) for communication between an eNB and a UE. It should also be noted that in the E-UTRA and E-UTRAN general description, as used herein, a "cell (e.g., a serving cell)" may be defined as a "combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

[0031] The fifth generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions using time / frequency / space resources to enable services such as eMBB (enhanced mobile broadband) transmission, URLLC (ultra-reliable and low-latency communication) transmission, and eMTC (massive machine type communication) transmission. Also, in NR, one or more bandwidth parts (BWPs) in a serving cell and / or one or more serving cells may be designated (e.g., configured) for transmission of different services. A user equipment (UE) may perform reception of downlink signals and / or transmission of uplink signals in a BWP of a serving cell.

[0032] In order for a service to use time, frequency and / or space resources efficiently, it would be useful to be able to effectively control downlink and / or uplink transmissions. Therefore, a process for effectively controlling downlink and / or uplink transmissions should be designed. Therefore, a detailed design of the process for downlink and / or uplink transmissions may be beneficial.

[0033] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods as generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0034] Figure 1 1 is a block diagram illustrating one embodiment of one or more gNBs 160 and one or more UEs 102 in which systems and methods for signaling may be implemented. The one or more UEs 102 communicate with the one or more gNBs 160 using one or more physical antennas 122a-n. For example, the UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some implementations, the terms “base station,” “eNB,” and / or “gNB” may refer to and / or be replaced by the term “transmission reception point (TRP).” For example, in some implementations, in conjunction with Figure 1 The gNB 160 described may be a TRP.

[0035] The UE 102 and the gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)), etc. For example, the one or more gNBs 160 may also use one or more downlink channels 119 to transmit information or data to the one or more UEs 102. Examples of downlink channels 119 include physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel)) and / or physical control channels (PDCCH (Physical Downlink Control Channel)), etc.). Other types of channels and / or signals may be used.

[0036] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operation module 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0037] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

[0038] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate a decoded signal 110, which may include the UE-decoded signal 106 (also referred to as the first UE-decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as the second UE-decoded signal 110) may include overhead data and / or control data. For example, the second UE-decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0039] Generally speaking, the UE operation module 124 can enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include one or more UE scheduling modules in the UE scheduling module 126.

[0040] The UE scheduling module 126 may perform downlink reception and uplink transmission. The one or more downlink receptions may include reception of data, reception of downlink control information, and / or reception of downlink reference signals. In addition, uplink transmissions may include transmission of data, transmission of uplink control information, and / or transmission of uplink reference signals.

[0041] In a radio communication system, physical channels (uplink physical channels and / or downlink physical channels) may be defined. The physical channels (uplink physical channels and / or downlink physical channels) may be used to transmit information delivered from a higher layer.

[0042] For example, in the uplink, a PRACH (physical random access channel) may be defined. In some methods, the PRACH (e.g., random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection reestablishment, timing adjustment (e.g., for synchronization of uplink transmissions, for UL synchronization), and / or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0043] In another example, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI) and / or a scheduling request (SR). The HARQ-ACK is used to indicate a positive acknowledgement (ACK) or a negative acknowledgement (NACK) of downlink data (e.g., a transport block, a medium access control protocol data unit (MAC PDU) and / or a downlink shared channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel (e.g., a downlink signal). The CSI may include aperiodic CSI (e.g., transmitted on a PUSCH), semi-persistent CSI (e.g., transmitted on a PUSCH and / or a PUCCH) and / or periodic CSI (e.g., transmitted on a PUSCH and / or a PUCCH). In addition, the SR is used to request resources for uplink data (e.g., a transport block, a MAC PDU and / or an uplink shared channel (UL-SCH)).

[0044] Here, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. In addition, a transport block (TB) and / or a MAC PDU may be defined as a unit of a transport channel used in the MAC layer. A transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver a transport block to the physical layer (e.g., the MAC layer delivers data as a transport block to the physical layer). In the physical layer, a transport block may be mapped to one or more codewords.

[0045] In the downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). Here, more than one DCI format may be defined for DCI transmission on the PDCCH. That is, fields may be defined in the DCI format and mapped to information bits (e.g., DCI bits).

[0046] For example, DCI format 1_0 for scheduling PDSCH in a cell may be defined as a DCI format for downlink. In addition, as described herein, one or more radio network temporary identifiers (e.g., cell RNTI (C-RNTI), configured scheduling RNTI (CS-RNTI), system information RNTI (SI-RNTI), random access RNTI (RA-RNTI), MCS-C-RNTI (Modulation and Coding Scheme-C-RNTI) and / or first RNTI) may be used to transmit DCI format 1_0. In addition, DCI format 1_0 may be monitored (e.g., transmitted, mapped) in a common search space (CSS) and / or a UE-specific search space (USS). Alternatively, DCI format 1_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0047] For example, the DCI included in DCI format 1_0 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 may be a priority indicator.

[0048] Additionally or alternatively, DCI format 1_1 for scheduling PDSCH in a cell may be defined as a DCI format for downlink. Additionally or alternatively, C-RNTI, CS-RNTI, MCS-C-RNTI and / or the first RNTI may be used to transmit DCI format 1_1. Additionally or alternatively, DCI format 1_1 may be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0049] For example, the DCI included in the DCI format 1_1 may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_1 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_1 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_1 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_1 may be a priority indicator. Additionally or alternatively, the DCI included in the DCI format 1_1 may be a DCI for indicating an antenna port (i.e., a downlink antenna port) (e.g., an index (one or more) of an antenna port, the number of antenna ports). Additionally or alternatively, the DCI included in the DCI format 1_1 may be a DCI for indicating a demodulation reference signal (DMRS) sequence initialization. That is, the DCI included in the DCI format 1_1 may be used to indicate sequence initialization of the DMRS for the PDSCH, as described in detail below.

[0050] Additionally or alternatively, the DCI included in DCI format 1_1 (e.g., the number of bits (e.g., the number of bit fields)) may be configurable. For example, for each DCI (i.e., the DCI included in DCI format 1_1), the gNB 160 may configure information for indicating (e.g., determining) the number of bits. For example, the gNB 160 may transmit information (e.g., one or more parameters) for indicating (e.g., determining) the number of bits for each DCI (i.e., the DCI included in DCI format 1_1) by using an RRC message (e.g., a dedicated RRC message). That is, each of the information (e.g., each of the one or more parameters) may be used to indicate (e.g., determine) the number of bits for each DCI, respectively.

[0051] For example, the number of bits of the BWP indicator included in the DCI format 1_1 may be 0, 1, or 2 bits. Additionally or alternatively, the number of bits of the frequency domain resource allocation included in the DCI format 1_1 may be determined based on the number of active DL BWPs configured by using information (e.g., information transmitted by using an RRC message). Additionally or alternatively, the number of bits of the time domain resource allocation included in the DCI format 1_1 may be 0, 1, 2, 3, or 4 bits. Additionally or alternatively, the number of bits of the modulation and coding scheme included in the DCI format 1_1 may be 5 bits. Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 1_1 may be 1 bit (i.e., always 1 bit). Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 1_1 may be 0 or 1 bit (i.e., the gNB 160 may transmit information for configuring (e.g., determining) the number of bits of the priority indicator, e.g., by using an RRC message). Additionally or alternatively, the number of bits of DCI included in DCI format 1_1 for indicating antenna ports (e.g., (one or more) indexes of antenna ports, the number of antenna ports) may be 4 bits, 5 bits, or 6 bits. That is, the number of bits of DCI included in DCI format 1_1 for indicating antenna ports may not be a "0" bit (i.e., may not be configured as a "0" bit). Additionally or alternatively, the number of bits of DCI included in DCI format 1_1 for indicating DMRS sequence initialization may be 1 bit (i.e., always 1 bit). That is, the number of bits of DCI included in DCI format 1_1 for indicating DMRS sequence initialization may not be a "0" bit (i.e., may not be configured as a "0" bit).

[0052] Additionally or alternatively, DCI format 1_X for scheduling PDSCH in a cell may be defined as a DCI format for downlink. Additionally or alternatively, C-RNTI, CS-RNTI, MCS-C-RNTI and / or first RNTI may be used to transmit DCI format 1_X. Additionally or alternatively, DCI format 1_X may be monitored (e.g., transmitted and / or mapped) in CSS and / or USS.

[0053] For example, the DCI included in the DCI format 1_X may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a priority indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be a DCI for indicating an antenna port (i.e., a downlink antenna port) (e.g., an index (one or more) of an antenna port, the number of antenna ports). Additionally or alternatively, the DCI included in the DCI format 1_X may be a DCI for indicating a demodulation reference signal (DMRS) sequence initialization. That is, the DCI included in the DCI format 1_X may be used to indicate sequence initialization of a DMRS for a PDSCH, as described in detail below.

[0054] Additionally or alternatively, the DCI (e.g., the number of bits (e.g., the number of bit fields)) included in the DCI format 1_X may be configurable. For example, for each DCI (i.e., the DCI included in the DCI format 1_X), the gNB 160 may configure information for indicating (e.g., determining) the number of bits. For example, the gNB 160 may transmit information (e.g., one or more parameters) for indicating (e.g., determining) the number of bits for each DCI (i.e., the DCI included in the DCI format 1_X) by using an RRC message (e.g., a dedicated RRC message). That is, each of the information (e.g., each of the one or more parameters) may be used to indicate (e.g., determine) the number of bits for each DCI, respectively.

[0055] For example, the number of bits of the BWP indicator included in the DCI format 1_X may be 0, 1, or 2 bits. Additionally or alternatively, the number of bits of the frequency domain resource allocation included in the DCI format 1_X may be determined based on the number of active DL BWPs configured by using information (e.g., information transmitted by using an RRC message). Additionally or alternatively, the number of bits of the time domain resource allocation included in the DCI format 1_X may be 0, 1, 2, 3, or 4 bits. Additionally or alternatively, the number of bits of the modulation and coding scheme included in the DCI format 1_X may be 5 bits. Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 1_X may be 1 bit (i.e., always 1 bit). Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 1_X may be 0 or 1 bit (i.e., the gNB 160 may transmit information for configuring (e.g., determining) the number of bits of the priority indicator, e.g., by using an RRC message). Additionally or alternatively, the number of bits of DCI included in DCI format 1_X for indicating antenna ports (e.g., (one or more) indexes of antenna ports, the number of antenna ports) may be 0 bits, 4 bits, 5 bits, or 6 bits. That is, the number of bits of DCI included in DCI format 1_X for indicating antenna ports may be "0" bits (i.e., may be configured as "0" bits). Additionally or alternatively, the number of bits of DCI included in DCI format 1_X for indicating DMRS sequence initialization may be 0 bits or 1 bits. That is, the number of bits of DCI included in DCI format 1_X for indicating DMRS sequence initialization may be "0" bits (i.e., may be configured as "0" bits).

[0056] For example, the gNB 160 may transmit information for configuring (e.g., determining) the DCI for indicating the antenna port included in the DCI format 1_1 and / or the DCI format 1_X to be 4 bits, 5 bits, or 6 bits, for example, by using an RRC message. That is, for the DCI for indicating the antenna port included in the DCI format 1_1 and / or the DCI format 1_X, the gNB 160 may generally configure the number of bits (e.g., 4 bits, 5 bits, or 6 bits) (e.g., by using information (e.g., single information)). For example, the number of bits (e.g., 4 bits, 5 bits, or 6 bits) may be defined (e.g., configured, determined) by using Table 1, Table 2, Table 3, and / or Table 4.

[0057] Table 1: Antenna port (1000+DMRS port), dmrs-Type=1, maxLength=1

[0058]

[0059]

[0060] Table 2: Antenna port (1000 + DMRS port), dmrs-Type = 1, maxLength = 2

[0061]

[0062]

[0063] Table 3: Antenna port (1000 + DMRS port), dmrs-Type = 2, maxLength = 1

[0064]

[0065]

[0066] Table 4: Antenna port (1000 + DMRS port), dmrs-Type = 2, maxLength = 2

[0067]

[0068]

[0069]

[0070] Here, for Table 1, Table 2, Table 3, and / or Table 4, dmrs-Type may be information (e.g., first information) transmitted from gNB 160 to UE 102 by using an RRC message. That is, for example, gNB 160 may transmit the first information by using an RRC message. For example, the first information may be used to select a DMRS type to be used for DL ​​(e.g., PDSCH, PDSCH transmission). For example, UE 102 may assume that a DMRS for PDSCH is mapped to a physical resource (e.g., a resource element) based on the first information. That is, the position of the physical resource to which the DMRS for PDSCH is mapped (e.g., the position of the DMRS for PDSCH) may be determined based on the first information. Here, in a case where the first information is not configured (e.g., in a case where there is no field for the first information (e.g., in a case where the first information does not exist)), dmrs-Type=1 may be used (e.g., the UE may use dmrs-Type=1).

[0071] Additionally or alternatively, for Table 1, Table 2, Table 3, and / or Table 4, maxLength may be information (e.g., second information) transmitted from the gNB 160 to the UE 102 by using an RRC message. That is, for example, the gNB 160 may transmit the second information by using an RRC message. For example, the second information may be used to configure (e.g., indicate) the maximum number of OFDM symbols of a DMRS for a PDSCH (e.g., a DL front-load DMRS (e.g., for a PDSCH). For example, the UE 102 may determine the position of the DMRS for the PDSCH in the time domain (e.g., the duration of the DMRS for the PDSCH) based on the second information. That is, the position of the DMRS for the PDSCH may be determined based on the second information. Here, in the case where the second information is not configured (e.g., in the case where there is no field for the second information (e.g., in the case where the second information does not exist)), maxLength=1 may be used (e.g., the UE may use maxLength=1).

[0072] As described, the number of bits of DCI for indicating an antenna port included in DCI format 1_1 and / or DCI format 1_X may be defined (e.g., configured) based on Table 1, Table 2, Table 3, and / or Table 4. That is, the number of bits of DCI for indicating an antenna port included in DCI format 1_1 and / or DCI format 1_X may be determined based on the first information and / or the second information. For example, when the first information (i.e., dmrs-Type)=1 is configured and the second information (i.e., maxLength)=1 is configured, the number of bits of DCI for indicating an antenna port included in DCI format 1_1 and / or DCI format 1_X may be 4 bits. Additionally or alternatively, when the first information (i.e., dmrs-Type)=1 is configured and the second information (i.e., maxLength)=2 is configured, the number of bits of DCI for indicating an antenna port included in DCI format 1_1 and / or DCI format 1_X may be 5 bits. Additionally or alternatively, when the first information (ie, dmrs-Type) = 2 is configured and the second information (ie, maxLength) = 1 is configured, the number of bits of the DCI for indicating the antenna port included in the DCI format 1_1 and / or DCI format 1_X may be 5 bits. Additionally or alternatively, when the first information (ie, dmrs-Type) = 2 is configured and the second information (ie, maxLength) = 2 is configured, the number of bits of the DCI for indicating the antenna port included in the DCI format 1_1 and / or DCI format 1_X may be 6 bits.

[0073] Additionally or alternatively, as described above, for DCI format 1_X, the gNB 160 may transmit information (e.g., third information) for configuring the number of bits of DCI for indicating the antenna port to be 0 bits by using an RRC message. For example, as the third information, the gNB 160 may transmit information for configuring (e.g., indicating) the number of bits of DCI for indicating the antenna port included in the DCI format 1_X to be 0 bits. That is, in a case where the third information (e.g., information for configuring the number of bits of DCI for indicating the antenna port to be 0 bits) is not configured, 4 bits, 5 bits, or 6 bits (e.g., determined based on the first information and the second information, as described above) may be used as (e.g., configured to be used as, indicated to be used as) the number of bits of DCI for indicating the antenna port included in the DCI format 1_X. Additionally or alternatively, as the third information, the gNB 160 may transmit information for configuring whether the number of bits of DCI for indicating the antenna port included in the DCI format 1_X is 0 bits or greater than 0 bits (e.g., 4 bits, 5 bits, or 6 bits). For example, as the third information, the gNB 160 may transmit information for configuring true (i.e., the number of bits of DCI for indicating the antenna port included in the DCI format 1_X is 0 bit) or false (i.e., the number of bits of DCI for indicating the antenna port included in the DCI format 1_X is greater than 0 bit (e.g., 4 bits, 5 bits, or 6 bits)). And, in the case where false (i.e., the number of bits of DCI for indicating the antenna port included in the DCI format 1_X is greater than 0 bit (e.g., 4 bits, 5 bits, or 6 bits)) is configured, the UE 102 may determine the number of bits of DCI for indicating the antenna port included in the DCI format 1_X based on the first information and the second information, as described above. Additionally or alternatively, for the DCI format 1_X, in the case where the first information is not configured and / or the second information is not configured, the number of bits of DCI for indicating the antenna port included in the DCI format 1_X may be regarded as (e.g., assumed to be) 0 bit (e.g., 0 bit may be used, and the UE 102 may use 0 bit). That is, for DCI format 1_1, when the first information is not configured, dmrs-Type=1 may be used (eg, the UE may use dmrs-Type=1). Additionally or alternatively, for DCI format 1_1, when the second information is not configured, maxLength=1 may be used (eg, the UE may use maxLength=1).

[0074] Additionally or alternatively, as described above, for DCI format 1_X, gNB 160 may transmit information (e.g., fourth information) for configuring the number of bits of DCI for indicating DMRS sequence initialization to 0 bits by using an RRC message. For example, as the fourth information, gNB 160 may transmit information for configuring (e.g., indicating) the number of bits of DCI for indicating DMRS sequence initialization included in DCI format 1_X to be 0 bits. That is, in a case where the fourth information (e.g., information for configuring the number of bits of DCI for indicating DMRS sequence initialization to be 0 bits) is not configured, 1 bit may be used (e.g., configured to be used as, indicated to be used as) the number of bits of DCI for indicating DMRS sequence initialization included in DCI format 1_X. Additionally or alternatively, as the fourth information, gNB 160 may transmit information for configuring the number of bits of DCI for indicating DMRS sequence initialization included in DCI format 1_X to be 0 bits or 1 bits. For example, as the fourth information, gNB 160 may transmit information for configuring true (i.e., the number of DCI bits included in DCI format 1_X for indicating DMRS sequence initialization is 0 bits) or false (i.e., the number of DCI bits included in DCI format 1_X for indicating DMRS sequence initialization is 1 bit).

[0075] Additionally or alternatively, the gNB 160 may transmit information for generating a sequence of DMRS for the PDSCH by using an RRC message. For example, the information may include information for indicating a scrambling identifier (e.g., scrambling ID0) for the DMRS for the PDSCH. Here, the scrambling identifier may be a DMRS scrambling initialization. Additionally or alternatively, in a case where information for indicating a scrambling identifier (e.g., scrambling ID0) is not configured (e.g., in a case where there is no field for indicating a scrambling identifier (e.g., scrambling ID0)) (e.g., in a case where there is no information for indicating a scrambling identifier (e.g., scrambling ID0)), a physical cell identifier may be used (e.g., the UE 102 may use a physical cell identifier). Additionally or alternatively, the information may include information for indicating a scrambling identifier (e.g., scrambling ID1) for the DMRS for the PDSCH. Additionally or alternatively, in a case where information indicating a scrambling identity (e.g., scrambling ID1) is not configured (e.g., in a case where there is no field for indicating information of a scrambling identity (e.g., scrambling ID1)) (e.g., in a case where there is no information for indicating a scrambling identity (e.g., scrambling ID1)), a physical cell identity may be used (e.g., UE 102 may use the physical cell identity). Here, for a DMRS for a PDSCH (e.g., for generation of a sequence of a DMRS for a PDSCH), a scrambling identity (e.g., scrambling ID1 and / or scrambling ID1) may be included in a DMRS-DownlinkConfig IE (i.e., an information element).

[0076] Additionally or alternatively, DCI format 0_0 for scheduling PUSCH in a cell may be defined as a DCI format for uplink. Additionally or alternatively, C-RNTI, CS-RNTI, temporary C-RNTI, MCS-C-RNTI and / or first RNTI may be used to transmit DCI format 0_0. Additionally or alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) in CSS and / or USS. Alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) only in CSS.

[0077] For example, the DCI included in DCI format 0_0 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a priority indicator.

[0078] Additionally or alternatively, the DCI format 0_1 ​​for scheduling the PUSCH in the cell may be defined as a DCI format for the uplink. Here, the DCI format 0_1 ​​may be described as the first DCI format 601. Additionally or alternatively, C-RNTI, CS-RNTI and / or MCS-C-RNTI may be used to transmit DCI format 0_1 ​​(i.e., the first DCI format 601). That is, the first DCI format 601 may be a DCI format 0_1 ​​with a CRC scrambled by C-RNTI, CS-RNTI and / or MCS-C-RNTI. Here, as described below, the DCI format 0_1 ​​with a CRC scrambled by MCS-C-RNTI and / or the first RNTI may be a second DCI format 603. Additionally or alternatively, the DCI format 0_1 ​​(i.e., the first DCI format 601) may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0079] For example, the DCI included in the DCI format 0_1 ​​may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_1 ​​may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_1 ​​may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_1 ​​may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_1 ​​may be a priority indicator. Additionally or alternatively, the DCI included in the DCI format 0_1 ​​may be a DCI for indicating an antenna port (i.e., uplink antenna port) (e.g., (one or more) indexes of the antenna port, the number of antenna ports). Additionally or alternatively, the DCI included in the DCI format 0_1 ​​may be a DCI for indicating DMRS sequence initialization. That is, the DCI included in the DCI format 0_1 ​​may be used to indicate sequence initialization of the DMRS for the PUSCH, as described in detail below.

[0080] Additionally or alternatively, the DCI included in DCI format 0_1 ​​(e.g., the number of bits (e.g., the number of bit fields)) may be configurable. For example, for each DCI (i.e., the DCI included in DCI format 0_1), the gNB 160 may configure information for indicating (e.g., determining) the number of bits. For example, the gNB 160 may transmit information (e.g., one or more parameters) for indicating (e.g., determining) the number of bits for each DCI (i.e., the DCI included in DCI format 0_1) by using an RRC message (e.g., a dedicated RRC message). That is, each of the information (e.g., each of the one or more parameters) may be used to indicate (e.g., determine) the number of bits for each DCI, respectively.

[0081] For example, the number of bits of the BWP indicator included in the DCI format 0_1 ​​may be 0, 1, or 2 bits. Additionally or alternatively, the number of bits of the frequency domain resource allocation included in the DCI format 0_1 ​​may be determined based on the number of active UL BWPs configured by using information (e.g., information transmitted by using an RRC message). Additionally or alternatively, the number of bits of the time domain resource allocation included in the DCI format 0_1 ​​may be 0, 1, 2, 3, or 4 bits. Additionally or alternatively, the number of bits of the modulation and coding scheme included in the DCI format 0_1 ​​may be 5 bits. Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 0_1 ​​may be 1 bit (i.e., always 1 bit). Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 0_1 ​​may be 0 or 1 bit (i.e., the gNB 160 may transmit information for configuring (e.g., determining) the number of bits of the priority indicator, e.g., by using an RRC message). Additionally or alternatively, the number of bits of DCI included in DCI format 0_1 ​​for indicating antenna ports (e.g., (one or more) indexes of antenna ports, the number of antenna ports) may be 2 bits, 3 bits, 4 bits, or 5 bits. That is, the number of bits of DCI included in DCI format 0_1 ​​for indicating antenna ports may not be a "0" bit (i.e., may not be configured as a "0" bit). Additionally or alternatively, the number of bits of DCI included in DCI format 1_1 for indicating DMRS sequence initialization may be 1 bit (i.e., always 1 bit). That is, the number of bits of DCI included in DCI format 1_1 for indicating DMRS sequence initialization may not be a "0" bit (i.e., may not be configured as a "0" bit).

[0082] Additionally or alternatively, DCI format 0_Y for scheduling PUSCH in a cell may be defined as a DCI format for uplink. Additionally or alternatively, C-RNTI, CS-RNTI, MCS-C-RNTI and / or the first RNTI may be used to transmit DCI format 0_Y. Additionally or alternatively, DCI format 0_Y may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0083] For example, the DCI included in DCI format 0_Y may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a priority indicator. Additionally or alternatively, the DCI included in DCI format 0_Y may be a DCI for indicating an antenna port (i.e., an uplink antenna port) (e.g., an index (one or more) of an antenna port, the number of antenna ports). Additionally or alternatively, the DCI included in DCI format 0_Y may be a DCI for indicating a DMRS sequence initialization. That is, the DCI included in the DCI format 0_Y may be used to indicate sequence initialization of the DMRS for the PUSCH, as described in detail below.

[0084] Additionally or alternatively, the DCI (e.g., the number of bits (e.g., the number of bit fields)) included in DCI format 0_Y may be configurable. For example, for each DCI (i.e., DCI included in DCI format 0_Y), the gNB 160 may configure information for indicating (e.g., determining) the number of bits. For example, the gNB 160 may transmit information (e.g., one or more parameters) for indicating (e.g., determining) the number of bits for each DCI (i.e., DCI included in DCI format 0_Y) by using an RRC message (e.g., a dedicated RRC message). That is, each of the information (e.g., each of the one or more parameters) may be used to indicate (e.g., determine) the number of bits for each DCI, respectively.

[0085] For example, the number of bits of the BWP indicator included in the DCI format 0_Y may be 0, 1, or 2 bits. Additionally or alternatively, the number of bits of the frequency domain resource allocation included in the DCI format 0_Y may be determined based on the number of active UL BWPs configured by using information (e.g., information transmitted by using an RRC message). Additionally or alternatively, the number of bits of the time domain resource allocation included in the DCI format 0_Y may be 0, 1, 2, 3, or 4 bits. Additionally or alternatively, the number of bits of the modulation and coding scheme included in the DCI format 0_Y may be 5 bits. Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 0_Y may be 1 bit (i.e., always 1 bit). Additionally or alternatively, the number of bits of the priority indicator included in the DCI format 0_Y may be 0 or 1 bit (i.e., the gNB 160 may transmit information for configuring (e.g., determining) the number of bits of the priority indicator, e.g., by using an RRC message). Additionally or alternatively, the number of bits of the DCI included in the DCI format 0_Y for indicating the antenna port (e.g., (one or more) indexes of the antenna port, the number of antenna ports) may be 0, 2, 3, 4, or 5 bits. That is, the number of bits of the DCI included in the DCI format 0_Y for indicating the antenna port may be a "0" bit (i.e., may be configured as a "0" bit). Additionally or alternatively, the number of bits of the DCI included in the DCI format 0_Y for indicating the initialization of the DMRS sequence may be 0 or 1 bit. That is, the number of bits of the DCI included in the DCI format 0_Y for indicating the initialization of the DMRS sequence may be a "0" bit (i.e., may be configured as a "0" bit).

[0086] For example, the gNB 160 may transmit information for configuring (e.g., determining) the DCI for indicating the antenna port included in the DCI format 0_1 ​​and / or the DCI format 0_Y to be 2 bits, 3 bits, 4 bits, or 5 bits, for example, by using an RRC message. That is, for the DCI for indicating the antenna port included in the DCI format 0_1 ​​and / or the DCI format 0_Y, the gNB 160 may generally configure the number of bits (e.g., 2 bits, 3 bits, 4 bits, or 5 bits) (e.g., by using information (e.g., single information)). For example, the number of bits (e.g., 2 bits, 3 bits, 4 bits, or 5 bits) may be limited (e.g., configured, determined) by using Table 5, Table 6, Table 7, and / or Table 8.

[0087] Table 5: Antenna port, transform precoder is enabled, DMRS-Type = 1, maxLength = 1

[0088] value Number of DMRS CDM groups without data DMRS Port 0 2 0 1 2 1 2 2 2 3 2 3

[0089] Table 6: Antenna port, transform precoder disabled, dmrs-Type = 1, maxLength = 1, level = 1

[0090] value Number of DMRS CDM groups without data DMRS Port 0 1 0 1 1 1 2 2 0 3 2 1 4 2 2 5 2 3 6-7 Reserve Reserve

[0091] Table 7: Antenna ports, transform precoder enabled, DMRS-Type = 1, maxLength = 2

[0092] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0 1 1 2 1 1 2 2 2 1 3 2 3 1 4 2 0 2 5 2 1 2 6 2 2 2 7 2 3 2 8 2 4 2 9 2 5 2 10 2 6 2 11 2 7 2 12-15 Reserve Reserve Reserve

[0093] Table 8: Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 2, level = 1

[0094]

[0095]

[0096] Here, the transform precoder may be configured (e.g., enabled and / or disabled) by the gNB 160 to the UE 102 by using an RRC message. That is, for example, the gNB 160 may transmit information (e.g., fifth information) for enabling the transform precoder by using an RRC message. For example, the fifth information may be information related to the DMRS for the PUSCH (e.g., DMRS-related parameters of the DFT-S-OFDM (e.g., transform precoding)). For example, the fifth information may include information for indicating an identity (e.g., nPUSCH-Identity) of the DFT-S-OFDM DMRS for the PUSCH. Additionally or alternatively, the fifth information may include information for enabling and / or disabling sequence group hopping (e.g., sequenceGroupHopping). For example, for transmission of the DMRS for the PUSCH (e.g., with a transform precoder), the gNB 160 may enable and / or disable group hopping by using cell-specific parameters. Additionally or alternatively, for transmission of DMRS for PUSCH (e.g., with a transform precoder) (e.g., in addition to Msg.3 transmission in the random access procedure), the gNB 160 may disable group hopping by using information (e.g., sequenceGroupHopping). Additionally or alternatively, in a case where the information (e.g., sequenceGroupHopping) is not configured (e.g., in a case where there is no field for the information (e.g., sequenceGroupHopping) (e.g., in a case where the information (e.g., sequenceGroupHopping) does not exist)), a physical cell identifier may be used (e.g., the UE 102 may use the physical cell identifier). Additionally or alternatively, the fifth information may include information for enabling and / or disabling sequence hopping (e.g., sequenceHopping). For example, for transmission of DMRS for PUSCH (e.g., with a transform precoder), the gNB 160 may enable and / or disable sequence hopping by using cell-specific parameters. Additionally or alternatively, for transmission of DMRS for PUSCH (e.g., with a transform precoder) (e.g., except for Msg.3 transmission in a random access procedure), the gNB 160 may disable sequence hopping by using information (e.g., sequence Hopping). Additionally or alternatively, in a case where the information (e.g., sequence Hopping) is not configured (e.g., in a case where there is no field for the information (e.g., sequence Hopping) (e.g., in a case where the information (e.g., sequence Hopping) does not exist)), a physical cell identifier may be used (e.g., the UE 102 may use the physical cell identifier).

[0097] Additionally or alternatively, the gNB 160 may transmit information for disabling the transform precoder (e.g., the sixth information) by using an RRC message. For example, the sixth information may be information related to the DMRS used for the PUSCH (e.g., DMRS-related parameters for OFDM (e.g., cyclic prefix OFDM (CP-OFDM))). For example, the sixth information may include information for indicating a scrambling identifier (e.g., scrambling ID0) of the CP-OFDM DMRS used for the PUSCH. Here, the scrambling identifier may be a DMRS scrambling initialization (e.g., for CP-OFDM). Additionally or alternatively, in a case where information for indicating a scrambling identifier (e.g., scrambling ID0) is not configured (e.g., in a case where there is no field for indicating a scrambling identifier (e.g., scrambling ID0)) (e.g., in a case where there is no information for indicating a scrambling identifier (e.g., scrambling ID0)), a physical cell identifier may be used (e.g., the UE 102 may use the physical cell identifier). Additionally or alternatively, the sixth information may include information for indicating a scrambling identifier (e.g., scrambling ID1) of the CP-OFDM DMRS for the PUSCH. Additionally or alternatively, in a case where information for indicating a scrambling identifier (e.g., scrambling ID1) is not configured (e.g., in a case where there is no field for indicating information for indicating a scrambling identifier (e.g., scrambling ID1)) (e.g., in a case where there is no information for indicating a scrambling identifier (e.g., scrambling ID1))), a physical cell identifier may be used (e.g., UE 102 may use a physical cell identifier). Here, for the DMRS for the PUSCH (e.g., for the generation of a sequence of DMRS for the PUSCH), the scrambling identifier (e.g., scrambling ID1 and / or scrambling ID1) may be included in the DMRS-UplinkConfig IE (i.e., information element).

[0098] Here, for Table 5, Table 6, Table 7, and / or Table 8, dmrs-Type may be information (e.g., seventh information) transmitted from gNB 160 to UE 102 by using an RRC message. That is, for example, gNB 160 may transmit the seventh information by using an RRC message. For example, the seventh information may be used to select a DMRS type to be used for UL (e.g., PUSCH, PUSCH transmission). For example, UE 102 may assume that the DMRS for PUSCH is mapped to a physical resource (e.g., a resource element) based on the seventh information. That is, the position of the physical resource to which the DMRS for PUSCH is mapped (e.g., the position of the DMRS for PUSCH) may be determined based on the seventh information. Here, in the case where the seventh information is not configured (e.g., in the case where there is no field for the seventh information (e.g., in the case where the seventh information does not exist)), dmrs-Type=1 may be used (e.g., the UE may use dmrs-Type=1).

[0099] Additionally or alternatively, for Table 5, Table 6, Table 7, and / or Table 8, maxLength may be information (e.g., eighth information) transmitted from the gNB 160 to the UE 102 by using an RRC message. That is, for example, the gNB 160 may transmit the eighth information by using an RRC message. For example, the eighth information may be used to configure (e.g., indicate) the maximum number of OFDM symbols of the DMRS for PUSCH (e.g., UL frontload DMRS (e.g., for PUSCH)). For example, the UE 102 may determine the position of the DMRS for PUSCH in the time domain (e.g., the duration of the DMRS for PUSCH) based on the eighth information. That is, the position of the DMRS for PUSCH may be determined based on the eighth information. Here, in the case where the eighth information is not configured (e.g., in the case where there is no field for the eighth information (e.g., in the case where the eighth information does not exist)), maxLength=1 may be used (e.g., the UE may use maxLength=1).

[0100] As described, the number of bits of DCI for indicating antenna ports included in DCI format 0_1 ​​and / or DCI format 0_Y may be limited (e.g., configured) based on Table 5, Table 6, Table 7, and / or Table 8. That is, the number of bits of DCI for indicating antenna ports included in DCI format 0_1 ​​and / or DCI format 0_Y may be determined based on the fifth information, the sixth information, the seventh information, and / or the eighth information. That is, the number of bits of DCI for indicating antenna ports included in DCI format 0_1 ​​and / or DCI format 0_Y may be determined based on the seventh information, the eighth information, and / or whether the transform is enabled or disabled. For example, when the transform precoder is enabled, the seventh information (i.e., dmrs-Type) = 1 is configured, and the eighth information (i.e., maxLength) = 1 is configured, the number of bits of DCI for indicating antenna ports included in DCI format 0_1 ​​and / or DCI format 0_Y may be 2 bits. Additionally or alternatively, when the transform precoder is disabled, the seventh information (ie, dmrs-Type) = 1 is configured, and the eighth information (ie, maxLength) = 1 is configured, the number of bits of DCI for indicating the antenna port included in DCI format 0_1 ​​and / or DCI format 0_Y may be 3 bits. Additionally or alternatively, when the transform precoder is enabled, the seventh information (ie, dmrs-Type) = 1 is configured, and the eighth information (ie, maxLength) = 2 is configured, the number of bits of DCI for indicating the antenna port included in DCI format 0_1 ​​and / or DCI format 0_Y may be 4 bits. Additionally or alternatively, when the transform precoder is disabled, the seventh information (ie, dmrs-Type) = 2 is configured, and the eighth information (ie, maxLength) = 2 is configured, the number of bits of DCI for indicating the antenna port included in DCI format 0_1 ​​and / or DCI format 0_Y may be 5 bits.

[0101] Additionally or alternatively, as described above, for DCI format 0_Y, the gNB 160 may transmit information (e.g., ninth information) for configuring the number of bits of DCI for indicating the antenna port to be 0 bits by using an RRC message. For example, as the ninth information, the gNB 160 may transmit information for configuring (e.g., indicating) the number of bits of DCI for indicating the antenna port included in the DCI format 0_Y to be 0 bits. That is, in a case where the ninth information (e.g., information for configuring the number of bits of DCI for indicating the antenna port to be 0 bits) is not configured, 2 bits, 3 bits, 4 bits, or 5 bits (e.g., determined based on the fifth information, the sixth information, the seventh information, and the eighth information, as described above) may be used as (e.g., configured to be used as, indicated to be used as) the number of bits of DCI for indicating the antenna port included in the DCI format 0_Y (e.g., configured to be used as, indicated to be used as) the number of bits of DCI for indicating the antenna port included in the DCI format 0_Y. Additionally or alternatively, as the ninth information, the gNB 160 may transmit information for configuring whether the number of bits of the DCI for indicating the antenna port included in the DCI format 0_Y is 0 bit or greater than 0 bit (for example, 2 bits, 3 bits, 4 bits, or 5 bits). For example, as the ninth information, the gNB 160 may transmit information for configuring true (that is, the number of bits of the DCI for indicating the antenna port included in the DCI format 0_Y is 0 bit) or false (that is, the number of bits of the DCI for indicating the antenna port included in the DCI format 0_Y is greater than 0 bit (for example, 2 bits, 3 bits, 4 bits, or 5 bits)). And, in the case where false (that is, the number of bits of the DCI for indicating the antenna port included in the DCI format 0_Y is greater than 0 bit (for example, 4 bits, 5 bits, or 6 bits)) is configured, the UE 102 may determine the number of bits of the DCI for indicating the antenna port included in the DCI format 0_Y based on the fifth information, the sixth information, the seventh information, and the eighth information, as described above. Additionally or alternatively, for DCI format 0_Y, when the fifth information is not configured, the sixth information is not configured, the seventh information is not configured, and / or the eighth information is not configured, the number of bits of the DCI for indicating the antenna port included in DCI format 0_Y may be regarded as (e.g., assumed to be) 0 bits (e.g., 0 bits may be used, and UE 102 may use 0 bits). That is, for DCI format 0_1, when the fifth information is not configured, the physical cell identifier is used (e.g., the UE may use the physical cell identifier). Additionally or alternatively, for DCI format 0_1, when the sixth information is not configured, the physical cell identifier is used (e.g., the UE may use the physical cell identifier). Additionally or alternatively, for DCI format 0_1, when the seventh information is not configured, dmrs-Type=1 may be used (e.g., the UE may use dmrs-Type=1).Additionally or alternatively, for DCI format 0_1, in a case where the eighth information is not configured, maxLength=1 may be used (eg, the UE may use maxLength=1).

[0102] Additionally or alternatively, as described above, for DCI format 0_Y, gNB 160 may transmit information (e.g., tenth information) for configuring the number of bits of DCI for indicating DMRS sequence initialization to 0 bits by using an RRC message. For example, as the tenth information, gNB 160 may transmit information for configuring (e.g., indicating) the number of bits of DCI for indicating DMRS sequence initialization included in DCI format 0_Y to be 0 bits. That is, in a case where the tenth information (e.g., information for configuring the number of bits of DCI for indicating DMRS sequence initialization to be 0 bits) is not configured, 1 bit may be used (e.g., configured to be used as, indicated to be used as) the number of bits of DCI for indicating DMRS sequence initialization included in DCI format 0_Y. Additionally or alternatively, as the tenth information, gNB 160 may transmit information for configuring the number of bits of DCI for indicating DMRS sequence initialization included in DCI format 0_Y to be 0 bits or 1 bits. For example, as the tenth information, gNB 160 may transmit information for configuring true (i.e., the number of DCI bits included in DCI format 0_Y for indicating DMRS sequence initialization is 0 bits) or false (i.e., the number of DCI bits included in DCI format 0_Y for indicating DMRS sequence initialization is 1 bit).

[0103] Additionally or alternatively, the number of bits of the DCI included in the DCI format 0_Y for indicating the initialization of the DMRS sequence may be determined based on the tenth information, the fifth information and / or the sixth information. That is, the number of bits of the DCI included in the DCI format 0_Y for indicating the initialization of the DMRS sequence may be determined based on the tenth information and / or whether the transform precoder is enabled or disabled. For example, in the case where the tenth information is configured as false (e.g., or true) and the transform precoder is enabled, the number of bits of the DCI included in the DCI format 0_Y for indicating the initialization of the DMRS sequence may be 0 bits. Additionally or alternatively, in the case where the tenth information is configured as false (e.g., or true) and the transform precoder is disabled, the number of bits of the DCI included in the DCI format 0_Y for indicating the initialization of the DMRS sequence may be 1 bit.

[0104] Here, for DCI format 0_1, when the transform precoder is enabled, the number of bits of DCI used to indicate DMRS sequence initialization may be 0. Additionally or alternatively, for DCI format 0_1, when the transform precoder is enabled, the number of bits of DCI used to indicate DMRS sequence initialization may be 1 bit.

[0105] Additionally or alternatively, as described above, the RNTI (e.g., radio network temporary identifier) ​​allocated to UE 102 may be used for transmission of DCI (e.g., DCI format, DL control channel (e.g., PDCCH)). That is, gNB 160 may transmit information for configuring (e.g., allocating) the RNTI to UE 102 (e.g., by using an RRC message).

[0106] For example, a CRC (cyclic redundancy check) parity bit (also referred to as CRC) generated based on the DCI is attached to the DCI, and after attachment, the CRC parity bit is scrambled by the RNTI. The UE 102 may attempt to decode (e.g., blindly decode, monitor, detect) the DCI to which the CRC parity bit scrambled by the RNTI is attached. For example, the UE 102 detects a DL control channel (e.g., PDCCH, DCI, DCI format) based on blind decoding. That is, the UE 102 may decode the DL control channel using the CRC scrambled by the RNTI. In other words, the UE 102 may monitor the DL control channel using the RNTI. For example, the UE 102 may detect the DCI format using the RNTI.

[0107] Here, the RNTI may include C-RNTI (Cell-RNTI), CS-RNTI (Configured Scheduling C-RNTI), SI-RNTI (System Information RNTI), RA-RNTI (Random Access RNTI), Temporary C-RNTI, MCS-C-RNTI (Modulation and Coding Scheme-C-RNTI) and / or First RNTI.

[0108] For example, C-RNTI can be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, CS-RNTI can be a unique identifier for authorized scheduling transmission based on configuration. Additionally or alternatively, SI-RNTI can be used to identify a system message (SI) (e.g., SI message) mapped on BCCH and dynamically carried on DL-SCH. Additionally or alternatively, SI-RNTI can be used for broadcasting SI. Additionally or alternatively, RA-RNTI can be an identifier for a random access procedure (e.g., Msg.2 transmission). Additionally or alternatively, a temporary C-RNTI can be used for a random access procedure (e.g., scheduling of Msg.3 (re) transmission (e.g., Msg.3 PUSCH (re) transmission)). Additionally or alternatively, MCS-C-RNTI can be a unique identifier for indicating an MCS table (e.g., an alternative MCS table) for PDSCH and / or PUSCH. The first RNTI may be different from a C-RNTI, a CS-RNTI, a SI-RNTI, a RA-RNTI, a temporary C-RNTI and / or an MCS-C-RNTI.

[0109] Here, in a random access procedure (e.g., a contention-based random access procedure), a Msg.3 PUSCH transmission (e.g., initial transmission) may be scheduled by using a random access response grant. For example, in a random access procedure, a random access response grant may be included in a PDSCH (e.g., a Msg.2 transmission). In addition, in a random access procedure, a random access response grant may be used to schedule a PUSCH for Msg.3 transmission. In addition, as described above, a PDCCH (i.e., DCI format 0_0) with a CRC scrambled by a temporary C-RNTI may be used to schedule a PUSCH for Msg.3 transmission (e.g., a Msg.3 retransmission).

[0110] Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, in the case where PDSCH (e.g., PDSCH resources) are scheduled by using a DCI format for downlink, UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Additionally or alternatively, in the case where PUSCH (e.g., PUSCH resources) are scheduled by using a DCI format for downlink, UE 102 may transmit uplink data on the scheduled PUSCH (e.g., PUSCH resources). For example, PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport blocks). Additionally or alternatively, PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport blocks, MAC PDUs).

[0111] In addition, the PDSCH and / or the PUSCH may be used to transmit information of a higher layer (e.g., a radio resource control (RRC) layer and / or a MAC layer). For example, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit an RRC message (RRC signal). Additionally or alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit a MAC control element (MAC CE). Here, the RRC message and / or the MAC CE are also referred to as a higher layer signal.

[0112] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast a MIB (Master Information Block). Here, the system information may be divided into a MIB and a plurality of SIBs (System Information Blocks). For example, the MIB may be used to carry minimum system information. Additionally or alternatively, the SIB may be used to carry system information messages.

[0113] In some methods, in the downlink, a SS (synchronization signal) may be defined. The SS may be used to acquire time and / or frequency synchronization with a cell. Additionally or alternatively, the SS may be used to detect a physical layer cell ID of a cell.

[0114] In radio communication for uplink, UL RS may be used as an uplink physical signal. Additionally or alternatively, in radio communication for downlink, DL RS may be used as a downlink physical signal. The uplink physical signal and / or the downlink physical signal may not be used to transmit information provided from a higher layer, but may be used by a physical layer.

[0115] Here, for simplicity of description, in some implementations, it may be assumed that the downlink physical channel and / or downlink physical signal described herein is included in a downlink signal (e.g., DL signal). Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the uplink physical channel and / or uplink physical signal described herein is included in an uplink signal (i.e., UL signal).

[0116] In addition, in carrier aggregation (CA), the gNB 160 and the UE 102 may communicate with each other using one or more serving cells. Here, the one or more serving cells may include a primary cell and one or more secondary cells. For example, the gNB 160 may transmit information for configuring one or more secondary cells to form a serving cell set together with the primary cell by using an RRC message. That is, the serving cell set may include a primary cell and one or more secondary cells. Here, the primary cell may always be activated. In addition, the gNB 160 may activate one or more secondary cells within the configured secondary cell. Here, in the downlink, the carrier corresponding to the primary cell may be a downlink primary component carrier (i.e., DL PCC), and the carrier corresponding to the secondary cell may be a downlink secondary component carrier (i.e., DL SCC). In addition, in the uplink, the carrier corresponding to the primary cell may be an uplink primary component carrier (i.e., UL PCC), and the carrier corresponding to the secondary cell may be an uplink secondary component carrier (i.e., UL SCC).

[0117] Additionally or alternatively, dual connection operation may be supported. For example, in dual connection operation, special cells may be defined. For example, special cells may include a primary cell (e.g., a primary cell of a primary cell group (e.g., MSG)) and / or a primary secondary cell (e.g., a primary secondary cell of a secondary cell group (e.g., SCG)). Here, the primary secondary cell may be referred to as a primary secondary cell group cell (e.g., a primary SCG cell). That is, the term "special cell" refers to a primary cell (e.g., a primary cell of an MCG) and / or a primary secondary cell (e.g., a primary secondary cell of an SCG).

[0118] For example, the primary cell may be a serving cell (e.g., an MCG cell) operating a primary frequency, in which the UE 102 may perform an initial connection establishment procedure and / or initiate a connection reestablishment procedure. In addition, the primary and secondary cells may be serving cells (e.g., an SCG cell), in which the UE 102 may perform a random access procedure (e.g., in the case where the UE 102 performs a reconfiguration (e.g., a reconfiguration with a synchronization procedure)).

[0119] Additionally or alternatively, the special cell may be always activated (e.g., the special cell may not be deactivated). That is, the secondary cell may be activated and deactivated. In addition, transmission of PUCCH may be performed (e.g., supported) only on the special cell. That is, transmission of PUCCH may be always performed on the special cell. For example, resources (e.g., resource sets) for PUCCH transmission may be configured and / or indicated only on the special cell (e.g., by the gNB 160 for the UE 102 (e.g., by using RRC messages and / or DCI formats)). Additionally or alternatively, resources (e.g., resource sets) for PUCCH transmission may be configured and / or indicated only on each UL BWP of the special cell (e.g., by the gNB 160 for the UE 102 (e.g., by using RRC messages and / or DCI formats)) (e.g., only on each UL BWP in the UL BWP set of the special cell). Additionally or alternatively, a contention-based random access procedure may be performed (e.g., supported) only on the special cell.

[0120] That is, the serving cell may include a primary cell (eg, a primary cell of an MCG), a primary secondary cell (eg, a primary secondary cell of an SCG), and / or a secondary cell (eg, a secondary cell of an MCG and / or an SCG).

[0121] For example, gNB 160 may transmit information for configuring the index of a serving cell (e.g., the index of a primary and secondary cell and / or the index of a secondary cell) by using an RRC message. That is, the index of the serving cell may be used to identify the serving cell. UE 102 may identify the serving cell based on the index of the serving cell. Here, the index of the primary cell may be defined as "0". That is, the index of the primary cell may always be "0". For example, gNB 160 may transmit information for configuring the index of a secondary cell by using an RRC message. And, UE 102 may identify the index of the serving cell (e.g., the secondary cell) based on the information.

[0122] Additionally or alternatively, the gNB 160 may transmit information for configuring a cell group (e.g., a cell group associated with dual connectivity operation (e.g., MCG and / or SCG)) by using an RRC message. As described above, the MCG may include a primary cell and / or a secondary cell. In addition, the SCG may include a primary secondary cell and / or a secondary cell. For example, in dual connectivity operation, in a case where the UE 102 is configured with a cell group (e.g., MCG and / or SCG), the UE 102 is configured with two MAC entities (e.g., one MAC entity for the MCG and one MAC entity for the SCG). For example, in a case where the UE 102 is not configured with a cell group (e.g., MCG and / or SCG), the UE 102 is configured with one MAC entity (e.g., one MAC entity for the MCG). That is, for dual connectivity operation, the term "special cell" may refer to a primary cell of an MCG or a primary secondary cell of an SCG, depending on whether the MAC entity is associated with the MCG or the SCG, respectively.

[0123] The UE operations module 124 may provide the information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the one or more receivers 120 when to receive a retransmission.

[0124] The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of the modulation pattern expected for transmissions from the gNB 160.

[0125] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the encoding expected for the transmission from the gNB 160.

[0126] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0127] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0128] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmission to gNB 160. Modulator 154 may modulate coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0129] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit signals to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may up-convert the modulated signal 156 and transmit the modulated signal to the one or more gNBs 160.

[0130] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0131] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert the signals to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0132] The demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may decode the signal using the decoder 166. The decoder 166 may produce one or more decoded signals 164, 168. For example, the signal 164 decoded by the first eNB may include received payload data, which may be stored in the data buffer 162. The signal 168 decoded by the second eNB may include overhead data and / or control data. For example, the signal 168 decoded by the second eNB may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operations module 182 may use to perform one or more operations.

[0133] In general, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include one or more gNB scheduling modules in the gNB scheduling module 194. The gNB scheduling module 194 may perform scheduling of downlink and / or uplink transmissions as described herein.

[0134] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.

[0135] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding expected for transmissions from one or more UEs 102.

[0136] The gNB operation module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the gNB operation module 182 may instruct the encoder 109 to encode the information 101, including the transmission data 105.

[0137] The encoder 109 may encode the transmission data 105 and / or other information included in the information 101 provided by the gNB operation module 182. For example, encoding the transmission data 105 and / or other information included in the information 101 may involve error detection and / or correction coding, mapping the data to space, time and / or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide the encoded data 111 to the modulator 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0138] The gNB operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of the type of modulation (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0139] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (and when not) to transmit signals to the one or more UEs 102. The one or more transmitters 117 may upconvert the one or more modulated signals 115 and transmit the one or more modulated signals to the one or more UEs 102.

[0140] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.

[0141] It should also be noted that one or more of the elements or components thereof included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0142] Figure 2 An example of multiple parameter sets 201 is shown. Figure 2As shown, multiple parameters 201 (e.g., multiple subcarrier spacings) may be supported. For example, μ (e.g., subcarrier space configuration) and cyclic prefix (e.g., μ and cyclic prefix of a carrier bandwidth portion) may be configured by higher layer parameters (e.g., RRC messages) for downlink and / or uplink. Here, 15kHz may be a reference parameter 201. For example, the RE of the reference parameter 201 may be defined as having a subcarrier spacing of 15kHz in the frequency domain and a 2048Ts+CP length (e.g., 160Ts or 144Ts) in the time domain, where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds.

[0143] Additionally or alternatively, the number of OFDM symbols 203 per time slot may be determined based on μ (eg, subcarrier spatial configuration). Here, for example, slot configuration 0 (eg, the number of OFDM symbols 203 per slot may be 14) and / or slot configuration (eg, the number of OFDM symbols 203 per slot may be 7) may be defined.

[0144] Figure 3 is a diagram showing one example of a resource grid 301 and resource blocks 391 (eg, for downlink and / or uplink). Figure 3 The resource grid 301 and resource blocks 391 shown may be used in some implementations of the systems and methods disclosed herein.

[0145] exist Figure 3 In the example, a subframe 369 may include Symbols 387. Additionally or alternatively, a resource block 391 may include a plurality of resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) may be adopted, which may also be referred to as CP-OFDM. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair may include two downlink RBs 391 that are consecutive in the time domain. Additionally or alternatively, a downlink RB 391 may include twelve subcarriers in the frequency domain, and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. An area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is referred to as a resource element (RE) 389, and is uniquely identified by an index pair (k, l), where k and l are indexes in the frequency domain and the time domain, respectively.

[0146] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme may be adopted, which is also called discrete Fourier transform spread OFDM (DFT-S-OFDM). An uplink radio frame may include multiple pairs of uplink resource blocks 391. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair may include two uplink RBs 391 that are consecutive in the time domain. An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l) in the time slot, where k and l are indexes in the frequency domain and the time domain, respectively.

[0147] Each element in the resource grid 301 (eg, antenna port p) and subcarrier configuration μ is referred to as a resource element 389 and is uniquely identified by an index pair (k, l), where k=0, ..., is an index in the frequency domain, and l refers to the symbol position in the time domain. The resource element (k, l) 389 on antenna port p and the subcarrier spacing configuration μ are denoted as (k, l) p, μ. The physical resource block 391 is defined as The physical resource block 391 is from 0 to Number. Physical resource block number in the frequency domain n The relationship between PRB and resource element (k, l) is given by:

[0148] Figure 4 An example of a resource region (e.g., a resource region for a downlink) is shown. One or more PRB 491 sets 401 (e.g., a control resource set (i.e., CORESET)) may be configured for DL ​​control channel monitoring (e.g., PDCCH monitoring). For example, a CORESET is a PRB 491 set 401 in the frequency domain and / or time domain, within which the UE 102 attempts to decode DCI (e.g., DCI format, PDCCH), and in the case where the PRB 491 may or may not be frequency-contiguous and / or time-contiguous, the UE 102 may be configured with one or more control resource sets (e.g., CORESET), and one DCI message may be mapped within one control resource set. In the frequency domain, a PRB 491 is a resource unit size of a DL control channel (which may or may not include a DM-RS).

[0149] The UE 102 may monitor a set of candidates for PDCCH (e.g., PDCCH candidates) in one or more control resource sets (e.g., CORESET) on an active DL bandwidth part (BWP) on each activated serving cell according to a corresponding search space set. Here, the term "monitoring" may imply that the UE 102 attempts to decode each DL control channel (e.g., a set of candidates for PDCCH) according to the monitored DCI format. In addition, the candidates for PDCCH may be candidates to which a DL control channel may be mapped, allocated, and / or transmitted.

[0150] A candidate set of PDCCHs to be monitored by UE 102 may be defined according to a search space set (e.g., also referred to as a search space for short). UE 102 may monitor a set of PDCCH candidates in a search space. A search space set may include a common search space (CSS, UE common search space) and / or a user equipment specific search space (USS, UE specific search space).

[0151] That is, CSS and / or USS may be defined (e.g., configured) in the region of the DL control channel. For example, CSS may be used to transmit DCI to multiple UEs 102. For example, a Type0-PDCCH common search space may be defined for one or more DCI formats having a CRC scrambled by SI-RNTI. Additionally or alternatively, a Type1-PDCCH common search space may be defined for a DCI format having a CRC scrambled by RA-RNTI, a temporary C-RNTI, and / or a C-RNTI. Additionally or alternatively, a Type3-PDCCH common search space may be defined for a DCI format having a CRC scrambled by C-RNTI and / or CS-RNTI.

[0152] The USS may be used to transmit the DCI to a specific UE 102. For example, the USS may be determined based on a radio network temporary identifier (RNTI) (e.g., C-RNTI). For example, the USS may be defined for a DCI format having a CRC scrambled by a C-RNTI and / or a CS-RNTI.

[0153] Here, the gNB 160 may transmit the eleventh information for configuring (e.g., determining) one or more CORESETs by using an RRC message. For example, for each DL BWP in the DL BWP (e.g., each DL BWP in the DL BWP in the serving cell), the gNB 106 may transmit the eleventh information for configuring the one or more CORESETs by using an RRC message. For example, the eleventh information may include information for configuring an index of the CORESET. In addition, the eleventh information may include information for configuring a plurality of consecutive symbols of the CORESET. In addition, the eleventh information may include information for configuring a resource block set of the CORESET.

[0154] Here, the index "0" of the CORESET (i.e., the value "0" of the CORESET, CORESET#0) can be configured by using the MIB and / or SIB. For example, the index "0" of the CORESET can be used to identify a common CORESET configured in the MIB and / or SIB. That is, the index of the CORESET other than the value "0" can be configured as the index of the CORESET. In addition, the index of the CORESET with the value "0" can be configured by using information of CORESET-zero. In addition, the index "0" of the CORESET can be configured by using a dedicated RRC message (i.e., a UE-specific RRC message and / or a serving cell-specific RRC message). That is, the gNB 160 can transmit information for configuring the CORESET with the index "0" (i.e., CORESET#0) by using the MIB. Additionally or alternatively, the gNB 160 can transmit information for configuring CORESET#0 by using the SIB. Additionally or alternatively, gNB 160 may transmit information for configuring CORESET#0 by using a dedicated RRC message.

[0155] Here, CORESET#0 may be configured for an initial BWP (e.g., an initial DL BWP). Here, the gNB 160 may transmit information for the initial BWP (e.g., an initial BWP) by using an RRC message (e.g., an MIB, an SIB, and / or a dedicated RRC message). In addition, the index of the initial BWP (e.g., an initial DL BWP) may be "0". That is, an index "0" (e.g., a value "0") may be applied (e.g., defined) for the initial BWP (e.g., an initial DL BWP). For example, (e.g., for a primary cell), the initial BWP (i.e., a BWP with an index of "0") may be a BWP for initial access. Additionally or alternatively, (e.g., for a secondary cell), the initial BWP (i.e., a BWP with an index of "0") may be a BWP configured for the UE to first operate at the secondary cell activation.

[0156] Here, the gNB 160 may transmit information for configuring an index of a DL BWP (e.g., an index other than index '0') by using an RRC message (e.g., MIB, SIB, and / or a dedicated RRC message). In addition, the gNB 160 may transmit information for configuring an index of a UL BWP (e.g., an index other than index '0') by using an RRC message (e.g., MIB, SIB, and / or a dedicated RRC message). That is, the index of the DL BWP may be used to identify the DL BWP. In addition, the index of the UL BWP may be used to identify the UL BWP. The UE 102 may identify the DL BWP based on the index of the DL BWP. In addition, the UE 102 may identify the UL BWP based on the index of the UL BWP.

[0157] As described above, CORESET#0 may be referred to as a common CORESET. In addition, a CORESET other than CORESET#0 may be referred to as a UE-specific CORESET. That is, a CORESET having an index "X" other than index "0" (e.g., X=1, 2, 3, ...) may be referred to as a UE-specific CORESET. For example, the gNB 160 may transmit information for configuring a UE-specific CORESET (e.g., an index of a UE-specific CORESET) by using a dedicated RRC message.

[0158] Additionally or alternatively, for each of the one or more CORESETs, a search space set (e.g., a set of CSS and / or USS) may be configured. That is, the search space set may be associated with a CORESET. For example, the UE 102 may monitor the PDCCH (e.g., PDCCH candidates) in a CSS set associated with CORESET#0. In addition, the UE 102 may monitor the PDCCH (e.g., PDCCH candidates) in a CSS set not associated with CORESET#0. In addition, the UE may monitor the PDCCH (e.g., PDCCH candidates) in a USS (e.g., a USS not associated with a USS). In addition, for example, a search space set may be configured for each DL BWP. That is, a search space set may be configured for each DL BWP in a DL BWP in a serving cell.

[0159] Additionally or alternatively, the gNB 160 may transmit twelfth information for configuring the search space set by using an RRC message. For example, the twelfth information may be configured for each search space set. For example, the twelfth information may include information for configuring an index of the search space set. Additionally or alternatively, the twelfth information may include information for configuring an index of a CORESET associated with the search space set. Additionally or alternatively, the twelfth information may include information for indicating a PDCCH monitoring periodicity and / or a PDCCH monitoring offset in which the UE 102 monitors the PDCCH in the search space set. Additionally or alternatively, the twelfth information may include information for indicating a PDCCH monitoring mode within a time slot. For example, the information for indicating the PDCCH monitoring mode may be used to indicate the first symbol within the time slot for PDCCH monitoring. For example. The UE 102 may determine the PDCCH monitoring timing based on the PDCCH monitoring periodicity, the PDCCH monitoring offset, and / or the PDCCH monitoring mode within the time slot.

[0160] Additionally or alternatively, the twelfth information may include information indicating the type of the search space set (e.g., information indicating whether the search space set is a CSS or a USS). Additionally or alternatively, the twelfth information may include information indicating one or more DCI formats for indicating that UE102 monitors the PDCCH in the search space set accordingly. For example, if the search space set is a CSS (e.g., if the search space set is configured as a CSS), DCI format 0_0 and / or DCI format 1_0 may be configured to monitor the PDCCH (e.g., a PDCCH candidate). Here, the DCI format for monitoring the PDCCH in the CSS may be scrambled by a C-RNTI, a CS-RNTI, a RA-RNTI, a temporary C-RNTI, an SI-RNTI, and / or a first RNTI.

[0161] Additionally or alternatively, if the search space set is USS (e.g., if the search space set is configured as USS), DCI format 0_0, DCI format 1_0, DCI format 0_Y and / or DCI format 1_X may be configured to monitor PDCCH (e.g., PDCCH candidates). Additionally or alternatively, if the search space set is USS, DCI format 0_1, DCI format 1_1, DCI format 0_Y and / or DCI format 1_X may be configured to monitor PDCCH (e.g., PDCCH candidates). For example, if the search space set is USS, any of the first group of DCI formats (e.g., DCI format 0_0, DCI format 1_0 and / or DCI format 0_Y and / or DCI format 1_X) or the second group of DCI formats (e.g., DCI format 0_1, DCI format 1_1, DCI format 0_Y and / or DCI format 1_X) may be configured to monitor PDCCH (e.g., PDCCH candidates). For example, if the search space set is USS, any one of the third group of DCI formats (e.g., DCI format 0_Y and / or DCI format 1_X) or the fourth group of DCI formats (e.g., DCI format 0_1 ​​and / or DCI format 1_1) may be configured to monitor PDCCH. In addition, if the search space set is USS, any one of the fifth group of DCI formats (e.g., DCI format 0_Y and / or DCI format 1_X) or the sixth group of DCI formats (e.g., DCI format 0_0 and / or DCI format 1_0) may be configured to monitor PDCCH. Here, the DCI format for monitoring the PDCCH in the USS may be scrambled by C-RNTI, CS-RNTI and / or the first RNTI. For example, the twelfth information may be configured for the search space set. That is, the twelfth information may be configured for each in the search space set.

[0162] Here, the index "0" of the search space set (i.e., the value "0" of the search space set) can be configured by using the MIB and / or SIB. For example, the index "0" of the search space set can be used to identify a common search space set configured in the MIB and / or SIB. That is, the index of the search space set other than the value "0" can be configured as the index of the search space. In addition, the index of the search space set with the value "0" can be configured by using information of search space-zero. In addition, the index "0" of the search space set can be configured by using a dedicated RRC message (i.e., a UE-specific RRC message and / or a serving cell-specific RRC message). That is, the gNB 160 can transmit information for configuring the search space set with the index "0" (i.e., search space set #0) by using the MIB. Additionally or alternatively, the gNB 160 can transmit information for configuring the search space set #0 by using the SIB. Additionally or alternatively, the gNB 160 can transmit information for configuring the search space set #0 by using a dedicated RRC message. Here, search space set #0 may be configured for an initial BWP (eg, initial DL BWP).

[0163] As described above, search space set #0 may be referred to as a common search space set. In addition, search space sets other than search space set #0 may be referred to as UE-specific search space sets. That is, search space sets having indexes "X (e.g., X=1, 2, 3, ...)" other than index "0" may be referred to as UE-specific search space sets. For example, gNB 160 may transmit information for configuring a UE-specific search space set (e.g., an index of a UE-specific search space set) by using a dedicated RRC message.

[0164] Here, for example, for a serving cell, gNB 160 may configure four DL BWP sets (e.g., up to four DL BWPs, one DL BWP set) by using an RRC message (e.g., for reception by UE 102). Additionally or alternatively, gNB 160 may indicate an active DL BWP by using a DCI format for the downlink. For example, for each DL BWP in a DL BWP set, gNB 160 may configure a subcarrier spacing, a cyclic prefix, a number of consecutive PRBs 491 (e.g., a bandwidth of a PRB), and / or an index (e.g., an index of a DL BWP, a DL BWP ID) in the DL BWP set by using an RRC message.

[0165] Additionally or alternatively, for a serving cell, gNB 160 may configure four UL BWP sets (e.g., up to four UL BWPs, one UL BWP set) by using RRC messages (e.g., for transmission by UE 102). Additionally or alternatively, gNB 160 may indicate an active UL BWP by using a DCI format for the uplink. Additionally or alternatively, for each UL BWP in a UL BWP set, gNB 160 may configure a subcarrier spacing, a cyclic prefix, a number of consecutive PRBs 491 (e.g., a bandwidth of the PRBs), an index (e.g., an index of the UL BWP) in the UL BWP set by using RRC messages.

[0166] Additionally or alternatively, the UE 102 may perform reception on the PDCCH in the DL BWP and / or reception on the PDSCH in the DL BWP based on the configuration for the DL BWP. Additionally or alternatively, the UE 102 may perform based on the configuration for the UL BWP.

[0167] Figure 5 An example of downlink transmission is shown. Figure 5 As shown, UE 102 may use an antenna port (i.e., a downlink antenna port) to receive a DMRS for a PDSCH. Here, as described above, the antenna port for the DMRS for the PDSCH may be indicated by using a DCI for indicating an antenna port included in DCI format 1_1 and / or DCI format 1_X. In addition, as described above, the number of bits of the DCI for indicating an antenna port included in DCI format 1_1 and / or DCI format 1_X may be configurable.

[0168] As described above, for example, in the case where the number of bits of the DCI for indicating the antenna port included in the DCI format 1_1 and / or the DCI format 1_X is 4 bits (e.g., based on the first information and / or the second information), Table 1 may be used to indicate (e.g., determine) the antenna port (i.e., the DMRS port in Table 1) (e.g., the index of the antenna port, the number of antenna ports). For example, in the case where the 4-bit (e.g., 4-bit field) DCI for indicating the antenna port is set to a value of "5", the UE 102 may use the antenna port with an index of "1" (i.e., DMRS port = 2) to receive the DMRS for the PDSCH.

[0169] Additionally or alternatively, for example, in the case where the number of bits of the DCI for indicating the antenna port included in the DCI format 1_1 and / or the DCI format 1_X is 6 bits (e.g., based on the first information and / or the second information), Table 4 may be used to indicate (e.g., determine) the antenna port (i.e., the DMRS port in Table 4) (e.g., the index of the antenna port, the number of antenna ports). For example, in the case where the 6-bit (e.g., 4-bit field) DCI for indicating the antenna port is set to a value of "15", the UE 102 may use the antenna port with an index of "4" (i.e., DMRS port = 4) to receive the DMRS for the PDSCH.

[0170] Additionally or alternatively, as described above, 0 bits may be configured (e.g., indicated, defined) as the number of bits of DCI used to indicate an antenna port in DCI format 1_X. For example, in a case where the number of bits of DCI used to indicate an antenna port is 0 bits (e.g., the DCI used to indicate an antenna port does not exist in DCI format 1_X, and there is no DCI used to indicate an antenna port in DCI format 1_X), UE 102 may use an antenna port having an index of a "first predetermined value" to receive a DMRS for a PDSCH. For example, the first predetermined value may be specified (e.g., defined) by a specification and known information between gNB 160 and UE 102. For example, the first predetermined value may be "0". That is, for example, in a case where the number of bits of DCI used to indicate an antenna port is 0 bits, UE 102 may use an antenna port having an index of "0" to receive a DMRS for a PDSCH. Here, as an example, "0" is described as the first predetermined value, however, it is apparent that a value other than "0" may be the first predetermined value.

[0171] Additionally or alternatively, in a case where the number of bits of the DCI for indicating the antenna port included in the DCI format 1_1 and / or the DCI format 0_X is 0 bits, the UE 102 may receive the DMRS for the PDSCH using the antenna port having an index that is “a value corresponding to a second predetermined value in a corresponding table (e.g., Table 1, Table 2, Table 3, or Table 4)”. For example, the second predetermined value may be specified (e.g., defined) by the specification and known information between the gNB 160 and the UE 102. For example, the second predetermined value may be “0 (e.g., a value of the lowest row index)” in Table 1, Table 2, Table 3, or Table 4. Also, for example, the second predetermined value may be “a value of the highest row index” in the table (e.g., a value of “11” in Table 1, a value of “30” and / or “3” in Table 2, a value of “23” and / or “1” in Table 3, and / or a value of “57” and / or “5” in Table 4). As described above, the table may be configured (e.g., determined, selected) based on the first information and / or the second information. For example, in the case where Table 2 is configured (e.g., based on the first information and the second information) and the number of bits of the DCI used to indicate the antenna port is configured as a "0" bit, for one codeword (i.e., codeword 0 is enabled, codeword 1 is disabled), the UE 102 may use an antenna port with an index of "0" (i.e., it corresponds to the value "0" in Table 2) to receive the DMRS for the PDSCH. Additionally or alternatively, in the case where Table 2 is configured (e.g., based on the first information and the second information) and the number of bits of the DCI used to indicate the antenna port is configured as a "0" bit, for two codewords (i.e., codeword 0 is enabled, codeword 1 is enabled), the UE 102 may use an antenna port with an index of "0-4" (i.e., it corresponds to the value "0" in Table 2) to receive the DMRS for the PDSCH.

[0172] Additionally or alternatively, in a case where the number of bits of the DCI for indicating the antenna port is 0 bits, the UE 102 may receive the DMRS for the PDSCH using the antenna port having an index that is “a value configured by the gNB 160”. For example, the gNB 160 may transmit information (e.g., the thirteenth information) for indicating the antenna port (e.g., the index of the antenna port, the number of antenna ports) by using an RRC message (e.g., a dedicated RRC message). That is, in a case where the number of bits of the DCI for indicating the antenna port is 0 bits, the UE 102 may receive the DMRS for the PDSCH using the antenna port having an index that is “a value configured by using the thirteenth information”. That is, the antenna port configured by using the thirteenth information may be used for a case where the number of bits of the DCI for indicating the antenna port is 0 bits.

[0173] As described above, in the case where the number of bits of the DCI for indicating the antenna port is 0, the UE 102 may receive the DMRS for the PDSCH using the antenna port having an index determined based on a predetermined manner. Similarly, in the case where the number of bits of the DCI for indicating the antenna port is 0, the gNB 160 may transmit the DMRS for the PDSCH using the antenna port having an index determined based on a predetermined manner. Here, the predetermined manner may be specified by the specification and known information between the gNB 160 and the UE 120.

[0174] The sequence generation of DMRS for PDSCH is described here. UE 102 may assume that the sequence of DMRS for PDSCH is generated as follows. Regarding the demodulation reference signal (DMRS) sequence generation for PDSCH, the UE may assume that the sequence r(n) is defined by the following formula:

[0175]

[0176] Where the pseudo-random sequence c(i) is defined in clause 5.2.1. The pseudo-random sequence generator can be initialized using the following formula:

[0177]

[0178] Where l is the number of OFDM symbols in a time slot, is the number of time slots in a frame.

[0179] This may be given using information (e.g., scrambling ID0) (e.g., as described above) and / or information (e.g., scrambling ID1) respectively in the DMRS-DownlinkConfig IE (if provided), and the PDSCH is scheduled by the PDCCH using DCI format 1_1 (e.g., DCI format 11 with a CRC scrambled by C-RNTI, MCS-C-RNTI, the first RNTI and / or CS-RNTI).

[0180] This may be given by using information (e.g., scrambling ID0) (e.g., as described above) and / or information (e.g., scrambling ID1) respectively in the DMRS-DownlinkConfig IE (if provided), and the PDSCH is scheduled by the PDCCH using DCI format 1_X (e.g., DCI format 1_X with a CRC scrambled by C-RNTI, MCS-C-RNTI, the first RNTI and / or CS-RNTI) (e.g., if the number of DCI bits used to indicate DMRS sequence initialization is a "1" bit (e.g., if the number of DCI bits used to indicate DMRS sequence initialization is not a "0" bit)).

[0181] This may be given using information (e.g., scrambling ID0) in the DMRS-DownlinkConfig IE (if provided) (e.g., as described above), and the PDSCH is scheduled by the PDCCH using DCI format 1_0 (e.g., DCI format 1_0 with a CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI and / or CS-RNTI).

[0182] otherwise (For example, there may be "exceptions", as described in detail below).

[0183] Here, the number n SCID ∈{0, 1} may be indicated by using a DCI for indicating DMRS sequence initialization (ie, DMRS sequence initialization field) included in DCI format 1_1 for scheduling PDSCH transmission (ie, DCI format 1_1 associated with PDSCH transmission), otherwise n SCID =0.

[0184] Additionally or alternatively, the number n SCID ∈{0, 1} may be given by a DCI for indicating DMRS sequence initialization (i.e., a DMRS sequence initialization field) included in a DCI format 1_X for scheduling PDSCH transmission (i.e., a DCI format 1_X associated with PDSCH transmission). Here, in this case, the number of bits of the DCI for indicating DMRS sequence initialization may be a "1" bit (i.e., may not be a "0" bit).

[0185] Regarding pseudo-random sequence generation, the universal pseudo-random sequence can be defined by a length 31 Gold sequence. PN The output sequence c(n) (where n = 0, 1..., M PN -1) can be defined by the following formula:

[0186] c(n)=(x1(n+Nc )+x2(n+N C ))mod 2

[0187] x1(n+31)=(x i (n+3)+x i (n))mod 2

[0188] x2(n+31)=(x2(n+3)+x2(n+2)+x2(n+1)+x2(n))mod 2

[0189] Where N C = 1600, and the first m-sequence x1(n) should be initialized with x1(0) = 1, x1(n) = 0, n = 1, 2, ..., 30. The second m-sequence x2(n) can be initialized by , whose value depends on the application of the sequence.

[0190] As described above, in the case where the PDSCH is scheduled by using DCI format 1_1 (e.g., DCI format 1_1 having a CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI, and / or CS-RNTI), the UE 102 may assume that a sequence of DMRS for the PDSCH is generated based on the DCI for indicating DMRS sequence initialization (i.e., it is included in the DCI format 1_1). Here, as described above, the number of bits of the DCI for indicating DMRS sequence initialization may always be 1 bit. That is, the DCI for indicating DMRS sequence initialization included in the DCI format 1_1 may be used to indicate n SCID =0 or n SCID =1. Here, n SCID = 0 may correspond to information (eg, scrambled ID0). SCID =1 may correspond to information (eg, scrambling ID 1). That is, UE 102 may determine the number of scrambling IDs based on n SCID The UE 102 may determine (eg, select) the value of the scrambling identifier (eg, the value of scrambling ID0 or the value of scrambling ID1) based on the value of the scrambling identifier. SCID The value of is used to generate the DMRS sequence for PDSCH.

[0191] Additionally or alternatively, in the case where the PDSCH is scheduled by using a DCI format 1_X (e.g., a DCI format 1_X having a CRC scrambled by a C-RNTI, an MCS-C-RNTI, a first RNTI, and / or a CS-RNTI), the UE 102 may assume that a sequence of DMRS for the PDSCH is generated based on a DCI for indicating DMRS sequence initialization (i.e., it is included in the DCI format 1_X). Here, in this case, the number of bits of the DCI for indicating DMRS sequence initialization may be 1 bit (i.e., 1 bit is configured as the number of bits of the DCI for indicating DMRS sequence initialization included in the DCI format 1_X). That is, the DCI for indicating DMRS sequence initialization included in the DCI format 1_X may be used to indicate n SCID =0 or n SCID =1. Here, n SCID = 0 may correspond to information (eg, scrambled ID0). SCID =1 may correspond to information (eg, scrambling ID 1). That is, UE 102 may determine the number of scrambling IDs based on n SCID The UE 102 may determine (eg, select) a scrambling identifier value (eg, a scrambling ID0 value or a scrambling ID1 value) based on the value of the scrambling identifier and / or n. SCID The value of is used to generate the DMRS sequence for PDSCH.

[0192] Additionally or alternatively, in the case where the PDSCH is scheduled by using DCI format 1_0 (e.g., DCI format 1_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI and / or CS-RNTI), the UE 102 may assume that a sequence of DMRS for the PDSCH is generated based on information (e.g., scrambling ID0) (i.e., the value of scrambling ID0). Additionally or alternatively, n SCID =0 may be used to generate a sequence of DMRS for PDSCH. In addition, as described above, DCI format 1_0 may not include DCI for indicating DMRS sequence initialization (ie, a field of DCI for indicating DMRS sequence initialization).

[0193] Additionally or alternatively, in the absence of configuration information (e.g., scrambling ID0) and / or information (e.g., scrambling ID0) (i.e., otherwise, as described above), UE 102 may assume that the sequence of DMRS for PDSCH is generated based on the physical cell identity. Additionally or alternatively, n SCID= 0 may be used to generate a sequence of DMRS for PDSCH. That is, in the absence of information (e.g., scrambling ID0) and / or information (e.g., scrambling ID0) (i.e., in the absence of a value of information (e.g., scrambling ID0) and / or a value of information (e.g., scrambling ID0) not configured), UE 102 may assume that a sequence of DMRS for PDSCH is generated based on a physical cell identifier.

[0194] Additionally or alternatively, in the case where the number of bits of the DCI used to indicate DMRS sequence initialization is configured as a "0" bit (ie, otherwise, as described above), the UE 102 may assume that the sequence of the DMRS for the PDSCH is generated based on the physical cell identity. SCID =0 may be used to generate a sequence of DMRS for PDSCH. That is, in the case where the number of bits of DCI for indicating DMRS sequence initialization is configured as "0" bit, the physical cell identity may be used to generate a sequence of DMRS for PDSCH.

[0195] Additionally or alternatively, in the case where the number of bits of the DCI for indicating the DMRS sequence initialization is configured as a “0” bit, the UE 102 may assume that the DMRS sequence initialization is based on the n bits configured by using the gNB 160. SCID For example, gNB 160 may transmit a sequence indicating n by using an RRC message (e.g., a dedicated RRC message). SCID (e.g., 0 or 1 (i.e., the value of the parameter related to the DMRS of the PDSCH, the value of the parameter related to the scrambling identifier)) (e.g., the fourteenth information). That is, the UE 102 may be based on the n configured by the gNB SCID The UE 102 may determine (e.g., select) a scrambling identifier value (e.g., a scrambling ID0 value or a scrambling ID1 value) based on the value of the scrambling identifier configured by the gNB and / or n SCID The value of is used to generate the DMRS sequence for PDSCH.

[0196] Additionally or alternatively, in a case where the number of bits of the DCI used to indicate the initialization of the DMRS sequence is configured as a "0" bit, the UE 102 may assume that the sequence of the DMRS for the PDSCH is generated based on the scrambling identifier (scrambling ID0 or scrambling ID1 or scrambling ID2) configured by the gNB 160. As described above, the gNB 160 may transmit the information (scrambling ID0) and / or the information (scrambling ID1) by using an RRC message. Additionally or alternatively, the gNB 160 may transmit the information (scrambling ID2, the fifteenth information) by using an RRC message. Here, the fifteenth information may be included in the DMRS-DownlinkConfig IE. Additionally or alternatively, n SCID = 0 can be used to generate a sequence of DMRS for PDSCH. That is, when the number of bits of the DCI used to indicate the initialization of the DMRS sequence is configured as a "0" bit, the scrambling identifier (scrambling ID0 or scrambling ID1 or scrambling ID2) configured by the gNB 160 can be used to generate a sequence of DMRS for PDSCH.

[0197] As described above, in the case where the number of bits of the DCI used to indicate the initialization of the DMRS sequence is 0, the UE 102 may assume that the DMRS sequence is initialized based on the parameters (eg, n SCID , information (e.g., scrambling ID0), information (e.g., scrambling ID1), and / or information (e.g., scrambling ID2)) to generate a sequence of DMRS for PDSCH, the parameter being determined based on a predetermined method. Similarly, in the case where the number of bits of the DCI used to indicate DMRS sequence initialization is 0, gNB 102 may generate a sequence of DMRS for PDSCH based on parameters (e.g., n SCID , information (e.g., scrambling ID0), information (e.g., scrambling ID1), and / or information (e.g., scrambling ID2)) to generate a sequence of DMRS for PDSCH, the parameter being determined based on a predetermined manner. Here, the predetermined manner may be specified by a specification and known information between gNB 160 and UE 120.

[0198] Figure 6 An example of uplink transmission is shown. Figure 6 As shown, UE 102 may use antenna ports (i.e., uplink antenna ports) to transmit DMRS for PUSCH. Here, as described above, the antenna port for DMRS for PUSCH may be indicated by using DCI for indicating antenna ports included in DCI format 0_1 ​​and / or DCI format 0_Y. In addition, as described above, the number of bits of DCI for indicating antenna ports included in DCI format 0_1 ​​and / or DCI format 0_Y may be configurable.

[0199] As described above, for example, in the case where the number of bits of the DCI for indicating the antenna port included in the DCI format 0_1 ​​and / or the DCI format 0_Y is 2 bits (e.g., based on the fifth information, the sixth information, the seventh information, and / or the eighth information), Table 5 may be used to indicate (e.g., determine) the antenna port (i.e., the DMRS port in Table 5) (e.g., the index of the antenna port, the number of antenna ports). For example, in the case where the 2-bit (e.g., 2-bit field) DCI for indicating the antenna port is set to a value of "3", the UE 102 may use the antenna port with an index of "3" (i.e., DMRS port = 3) to transmit the DMRS for the PUSCH.

[0200] Additionally or alternatively, for example, when the number of bits of the DCI for indicating the antenna port included in the DCI format 0_1 ​​and / or the DCI format 0_Y is 5 bits (e.g., based on the fifth information, the sixth information, the seventh information, and / or the eighth information), Table 8 may be used to indicate (e.g., determine) the antenna port (i.e., the DMRS port in Table 8) (e.g., the index of the antenna port, the number of antenna ports). For example, when the 5-bit (e.g., 5-bit field) DCI for indicating the antenna port is set to a value of "16", the UE 102 may use the antenna port with an index of "4" (i.e., DMRS port = 4) to transmit the DMRS for the PUSCH.

[0201] Additionally or alternatively, as described above, 0 bits may be configured (e.g., indicated, defined) as the number of bits of DCI used to indicate antenna ports in DCI format 0_X. For example, in a case where the number of bits of DCI used to indicate antenna ports is 0 bits (e.g., DCI used to indicate antenna ports does not exist in DCI format 1_X, and there is no DCI used to indicate antenna ports in DCI format 1_X), UE 102 may use antenna ports having an index of a "third predetermined value" to transmit DMRS for PUSCH. Here, the third predetermined value may be the same as the first predetermined value. That is, with respect to the number of bits of DCI used to indicate antenna ports included in DCI formats 1_1, 1_X, 0_1, and / or 0_Y, the same predetermined value (e.g., for the first predetermined value and the third predetermined value) may be used for antenna ports for DMRS for PDSCH and antenna ports for DMRS for PUSCH. For example, the third predetermined value may be specified (e.g., defined) by the specification and known information between the gNB 160 and the UE 102. For example, the third predetermined value may be "0". That is, for example, in the case where the number of bits of the DCI used to indicate the antenna port is 0 bits, the UE 102 may use the antenna port with index "0" to transmit the DMRS for the PUSCH. Here, as an example, "0" is described as the third predetermined value, however, it is obvious that a value other than "0" may be the third predetermined value.

[0202] Additionally or alternatively, in a case where the number of bits of the DCI for indicating the antenna port included in the DCI format 0_1 ​​and / or the DCI format 0_Y is 0 bits, the UE 102 may receive the DMRS for the PDSCH using the antenna port having an index (e.g., a fourth predetermined row index) that is “a value corresponding to a fourth predetermined value in the corresponding table (e.g., Table 1, Table 2, Table 3, or Table 4)”. Here, the fourth predetermined value may be the same as the second predetermined value. That is, with respect to the number of bits of the DCI for indicating the antenna port included in the DCI format 1_1, 1_X, 0_1, and / or 0_Y, the same predetermined value (e.g., for the second predetermined value and the fourth predetermined value) may be used for the antenna port for the DMRS for the PDSCH and the antenna port for the DMRS for the PUSCH.

[0203] For example, the fourth predetermined value may be specified (e.g., defined) by the specification and known information between the gNB 160 and the UE 102. For example, the fourth predetermined value may be "0 (e.g., the value of the lowest row index)" in Table 5, Table 6, Table 7, or Table 8. In addition, for example, the fourth predetermined value may be "the value of the highest row index" in the table (e.g., the value "3" in Table 5, the value "5" in Table 6, the value "11" and / or "7" in Table 7, and / or the value "27" and / or "7" in Table 8). As described above, the table may be configured (e.g., determined, selected) based on the fifth information, the sixth information, the seventh information, and / or the eighth information.

[0204] Additionally or alternatively, in a case where the number of bits of the DCI for indicating the antenna port is 0 bits, the UE 102 may use the antenna port having an index that is “a value configured by the gNB 160” to transmit the DMRS for the PUSCH. For example, the gNB 160 may transmit information (e.g., the sixteenth information) for indicating the antenna port (e.g., the index of the antenna port, the number of antenna ports) by using an RRC message (e.g., a dedicated RRC message). That is, in a case where the number of bits of the DCI for indicating the antenna port is 0 bits, the UE 102 may use the antenna port having an index that is “a value configured by using the sixteenth information” to transmit the DMRS for the PUSCH. That is, the antenna port configured by using the sixteenth information may be used for a case where the number of bits of the DCI for indicating the antenna port is 0 bits.

[0205] As described above, in the case where the number of bits of the DCI for indicating the antenna port is 0, the UE 102 may use the antenna port with an index determined based on a predetermined manner to transmit the DMRS for the PUSCH. Similarly, in the case where the number of bits of the DCI for indicating the antenna port is 0, the gNB 160 may assume that the DMRS for the PUSCH is transmitted using the antenna port with an index determined based on a predetermined manner. Here, the predetermined manner may be specified by the specification and known information between the gNB 160 and the UE 120.

[0206] Sequence generation of DMRS for PUSCH is described herein. UE 102 may generate a sequence of DMRS for PUSCH as follows. As described below, different methods for generating a sequence of DMRS for PUSCH may be used based on whether the transform precoder is disabled or enabled.

[0207] A demodulation reference signal for PUSCH sequence generation is also described. With respect to sequence generation, when transform precoding is disabled, if transform precoding for PUSCH is not enabled, the sequence r(n) may be generated according to the following equation:

[0208]

[0209] Where the pseudo-random sequence c(i) is defined in clause 5.2.1. The pseudo-random sequence generator can be initialized using the following formula:

[0210]

[0211] Where l is the number of OFDM symbols in a time slot, is the number of time slots in a frame.

[0212] The information (e.g., scrambling ID0) and information (e.g., scrambling ID1) may be given by respectively in the DMRS-UplinkConfig IE (if provided), and the PUSCH may be scheduled by DCI format 0_1 ​​(e.g., DCI format 0_1 ​​with CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI and / or CS-RNTI).

[0213] It may be given by information (e.g., scrambling ID0) and information (e.g., scrambling ID1) respectively in the DMRS-UplinkConfig IE (if provided), and the PUSCH is scheduled by DCI format 0_Y (e.g., DCI format 0_Y with CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI and / or CS-RNTI) (e.g., if the number of bits of the DCI used to indicate DMRS sequence initialization is "1" bit (i.e., if the number of bits of the DCI used to indicate DMRS sequence initialization is not "0" bit)).

[0214] It may be given by information (e.g., scrambling ID0) respectively in the DMRS-UplinkConfig IE (if provided), and the PUSCH may be scheduled by DCI format 0_0 (e.g., DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI and / or CS-RNTI).

[0215] otherwise (For example, there may be "exceptions", as described in detail below).

[0216] Here, the number n SCID∈{0,1} may be indicated by using a DCI for indicating DMRS sequence initialization (ie, DMRS sequence initialization field) included in DCI format 0_1 ​​for scheduling PDSCH transmission (ie, DCI format 0_1 ​​associated with PDSCH transmission), otherwise n SCID =0.

[0217] Additionally or alternatively, the number n SCID ∈{0,1} may be given by a DCI for indicating DMRS sequence initialization (i.e., a DMRS sequence initialization field) included in a DCI format 0_Y for scheduling PDSCH transmission (i.e., a DCI format 0_Y associated with PDSCH transmission). Here, in this case, the number of bits of the DCI for indicating DMRS sequence initialization may be a "1" bit (i.e., may not be a "0" bit).

[0218] The sequence generation when transform precoding is enabled is also described. If transform precoding for PUSCH is enabled, the reference signal sequence r(n) can be generated according to the following formula:

[0219]

[0220] in It can be given by clause 5.2.2, where for PUSCH transmission, δ=1 and α=0.

[0221] Sequence Group in It can be given by:

[0222] · The prerequisite is Configured by the higher layer parameter nPUSCH-Identity in the DMRS-UplinkConfig IE and according to clause 8.3 in [5, TS 38.213], PUSCH is neither scheduled by RAE UL grant nor by DCI format 0_0 with CRC scrambled by TC-RNTI.

[0223] ·otherwise

[0224] where f gh and the sequence number v can be given by:

[0225] If group hopping and sequence hopping are not enabled, then

[0226] f gh =0

[0227] v=0

[0228] If group hopping is enabled and sequence hopping is disabled, then

[0229]

[0230] v=0

[0231] where the pseudo-random sequence c(i) is defined by clause 5.2.1 and shall be used at the beginning of each radio frame To initialize,

[0232] If sequence hopping is enabled and group hopping is disabled, then

[0233] f gh =0

[0234]

[0235] where the pseudo-random sequence c(i) is defined by clause 5.2.1 and shall be used at the beginning of each radio frame To initialize,

[0236] The hopping mode is controlled by high-level parameters:

[0237] For PUSCH transmissions scheduled by RAR UL grant or by DCI format 0_0 with CRC scrambled by TC-RNTI, sequence hopping is disabled and group hopping is enabled or disabled by the higher layer parameter groupHoppingEnabledTransformPrecoding;

[0238] For all other transmissions, sequence hopping and group hopping are enabled or disabled by the corresponding higher layer parameters sequenceHopping and sequenceGroupHopping (if these parameters are provided), otherwise the same hopping pattern as Msg3 should be used.

[0239] The generation of low PAPR sequences is also described. According to the following equation, the low PAPR sequence By basic sequence The cyclic shift α is defined as:

[0240]

[0241] in is the length of the sequence. Multiple sequences are defined from a single base sequence by different values ​​of α and δ.

[0242] basic sequence are divided into different groups, where u∈{0,1,…,29} is the group number and v is the base sequence number within the group, so that each group contains 1 / 2≤m / 2δ ≤5 (v=0) and each of length 6≤m / 2 δ Two basic sequences (v=0,1). The limit depends on the sequence length M ZC .

[0243] As described above, in the case where the PUSCH is scheduled by using the DCI format 0_1 ​​(e.g., the DCI format 0_1 ​​having the CRC scrambled by the C-RNTI, the MCS-C-RNTI, the first RNTI, and / or the CS-RNTI), the UE 102 may generate a sequence of DMRS for the PUSCH based on the DCI for indicating the DMRS sequence initialization (i.e., it is included in the DCI format 0_1). Here, as described above, the number of bits of the DCI for indicating the DMRS sequence initialization may always be 1 bit. That is, the DCI for indicating the DMRS sequence initialization included in the DCI format 0_1 ​​may be used to indicate n SCID =0 or n SCID =1. Here, n SCID = 0 may correspond to information (eg, scrambled ID0). SCID =1 may correspond to information (eg, scrambling ID 1). That is, UE 102 may SCID The UE 102 may determine (eg, select) a scrambling identifier value (eg, a scrambling ID0 value or a scrambling ID1 value) based on at least the scrambling identifier value and n SCID The value of is used to generate the DMRS sequence for PUSCH.

[0244] Additionally or alternatively, in the case where the PUSCH is scheduled by using DCI format 0_Y (e.g., DCI format 0_Y having a CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI, and / or CS-RNTI), the UE 102 may generate a sequence of DMRS for the PUSCH based on the DCI for indicating DMRS sequence initialization (i.e., it is included in DCI format 0_Y). Here, in this case, the number of bits of the DCI for indicating DMRS sequence initialization may be 1 bit (i.e., 1 bit is configured as the number of bits of the DCI for indicating DMRS sequence initialization included in DCI format 0_Y). That is, the DCI for indicating DMRS sequence initialization included in DCI format 0_Y may be used to indicate n SCID =0 or n SCID =1. Here, n SCID = 0 may correspond to information (eg, scrambled ID0). SCID=1 may correspond to information (eg, scrambling ID 1). That is, UE 102 may SCID The UE 102 may determine (eg, select) a scrambling identifier value (eg, a scrambling ID0 value or a scrambling ID1 value) based on at least the scrambling identifier value and / or n SCID The value of is used to generate the DMRS sequence for PUSCH.

[0245] Additionally or alternatively, in the case where the PUSCH is scheduled by using DCI format 0_0 (e.g., DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, first RNTI and / or CS-RNTI), the UE 102 may generate a sequence of DMRS for the PUSCH based on the information (e.g., scrambling ID0) (i.e., the value of scrambling ID0). Additionally or alternatively, n SCID =0 may be used to generate a sequence of DMRS for PUSCH. In addition, as described above, DCI format 0_0 may not include DCI for indicating DMRS sequence initialization (ie, a field of DCI for indicating DMRS sequence initialization).

[0246] Additionally or alternatively, in the case where the information (e.g., scrambling ID0) and / or the information (e.g., scrambling ID0) are not configured (i.e., otherwise, as described above), the UE 102 may generate a sequence of DMRS for the PUSCH based on the physical cell identity. Additionally or alternatively, n SCID = 0 may be used to generate a sequence of DMRS for PUSCH. That is, in the absence of information (e.g., scrambling ID0) and / or information (e.g., scrambling ID0) (i.e., in the absence of a value of information (e.g., scrambling ID0) and / or a value of information (e.g., scrambling ID0) not configured), UE 102 may generate a sequence of DMRS for PUSCH based on the physical cell identifier.

[0247] Additionally or alternatively, in the case where the number of bits of the DCI for indicating DMRS sequence initialization is configured as a "0" bit (ie, otherwise, as described above), the UE 102 may generate a sequence of DMRS for the PUSCH based on the physical cell identity. SCID =0 may be used to generate a sequence of DMRS for PUSCH. That is, in the case where the number of bits of DCI for indicating DMRS sequence initialization is configured as "0" bit, the physical cell identity may be used to generate a sequence of DMRS for PUSCH.

[0248] Additionally or alternatively, in the case where the number of bits of the DCI for indicating the initialization of the DMRS sequence is configured as a "0" bit, the UE 102 may configure the DMRS sequence based on the n bits configured by using the gNB 160. SCID For example, gNB 160 may transmit a sequence indicating n by using an RRC message (e.g., a dedicated RRC message). SCID (e.g., 0 or 1 (i.e., the value of the parameter related to the DMRS of the PUSCH, the value of the parameter related to the scrambling identifier)) (e.g., the seventeenth information). That is, the UE 102 may be based on the n configured by the gNB SCID The UE 102 may determine (e.g., select) a scrambling identifier value (e.g., a scrambling ID0 value or a scrambling ID1 value) based on at least the scrambling identifier value configured by the gNB and / or n SCID The value of is used to generate the DMRS sequence for PUSCH.

[0249] Additionally or alternatively, in a case where the number of bits of the DCI used to indicate the initialization of the DMRS sequence is configured as a "0" bit, the UE 102 may generate a sequence of DMRS for the PUSCH based on a scrambling identifier (scrambling ID0 or scrambling ID1 or scrambling ID2) configured by the gNB 160. As described above, the gNB 160 may transmit the information (scrambling ID0) and / or the information (scrambling ID1) by using an RRC message. Additionally or alternatively, the gNB 160 may transmit the information (scrambling ID2, eighteenth information) by using an RRC message. Here, the eighteenth information may be included in the DMRS-UplinkConfig IE. Additionally or alternatively, n SCID = 0 can be used to generate a sequence of DMRS for PUSCH. That is, when the number of bits of the DCI used to indicate the initialization of the DMRS sequence is configured as a "0" bit, the scrambling identifier (scrambling ID0 or scrambling ID1 or scrambling ID2) configured by the gNB 160 can be used to generate a sequence of DMRS for PUSCH.

[0250] As described above, when the number of bits of the DCI used to indicate the initialization of the DMRS sequence is 0, the UE 102 may select the initialization bit based on the parameters (eg, n SCID , information (e.g., scrambling ID0), information (e.g., scrambling ID1), and / or information (e.g., scrambling ID2)) to generate a sequence of DMRS for PUSCH, the parameter being determined based on a predetermined method. Similarly, in the case where the number of bits of the DCI used to indicate DMRS sequence initialization is 0, gNB 102 may assume that the number of bits of the DCI used to indicate DMRS sequence initialization is 0 based on the parameter (e.g., n SCID, information (e.g., scrambling ID0), information (e.g., scrambling ID1), and / or information (e.g., scrambling ID2)) to generate a sequence of DMRS for PUSCH, the parameter being determined based on a predetermined manner. Here, the predetermined manner may be specified by a specification and known information between gNB 160 and UE 120.

[0251] Figure 7 Various components that may be used in UE 702 are shown. Figure 7 The UE 702 described may be based on the combination of Figure 1 102 described herein. The UE 702 includes a processor 703 that controls the operation of the UE 702. The processor 703 may also be referred to as a central processing unit (CPU). The memory 705 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 707a and data 709a to the processor 703. A portion of the memory 705 may also include a non-volatile random access memory (NVRAM). The instructions 707b and data 709b may also reside in the processor 703. The instructions 707b and / or data 709b loaded into the processor 703 may also include instructions 707a and / or data 709a from the memory 705 and loaded for execution or processing by the processor 703. The instructions 707b may be executed by the processor 703 to implement the method described herein.

[0252] The UE 702 may also include a housing that houses one or more transmitters 758 and one or more receivers 720 to allow transmission and reception of data. The transmitters 758 and receivers 720 may be combined into one or more transceivers 718. One or more antennas 722a-n are attached to the housing and electrically coupled to the transceiver 718.

[0253] The various components of the UE 702 are coupled together via a bus system 711 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Figure 7 702 is shown as bus system 711. UE 702 may also include a digital signal processor (DSP) 713 for processing signals. UE 702 may also include a communication interface 715 that provides user access to the functions of UE 702. Figure 7 The UE 702 is shown as a functional block diagram rather than a listing of specific components.

[0254] Figure 8 Various components that may be used in gNB 860 are shown. Figure 8 The gNB 860 described may be configured in accordance with the Figure 1The gNB 860 described herein is implemented by the gNB 160. The gNB 860 includes a processor 803 that controls the operation of the gNB 860. The processor 803 may also be referred to as a central processing unit (CPU). The memory 805 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of the two memories, or any type of device that can store information) provides instructions 807a and data 809a to the processor 803. A portion of the memory 805 may also include a non-volatile random access memory (NVRAM). Instructions 807b and data 809b may also reside in the processor 803. The instructions 807b and / or data 809b loaded into the processor 803 may also include instructions 807a and / or data 809a from the memory 805 and loaded for execution or processing by the processor 803. The instructions 807b may be executed by the processor 803 to implement the method described herein.

[0255] The gNB 860 may also include a housing that houses one or more transmitters 817 and one or more receivers 878 to allow transmission and reception of data. The transmitters 817 and receivers 878 may be combined into one or more transceivers 876. One or more antennas 880a-n are attached to the housing and electrically coupled to the transceiver 876.

[0256] The various components of gNB 860 are coupled together via bus system 811 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Figure 8 860 is shown as bus system 811. gNB 860 may also include a digital signal processor (DSP) 813 for processing signals. gNB 860 may also include a communication interface 815 that provides user access to the functions of gNB 860. Figure 8 The gNB 860 shown is a functional block diagram rather than a listing of specific components.

[0257] Fig. 9 902 may be implemented in one or more of the systems and / or methods described herein. The UE 902 includes a transmitting device 958, a receiving device 920, and a control device 924. The transmitting device 958, the receiving device 920, and the control device 924 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Figure 7 Shows Fig. 9 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0258] Fig.10is a block diagram illustrating one specific implementation of a gNB 1060 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1060 includes a transmitting device 1017, a receiving device 1078, and a control device 1082. The transmitting device 1017, the receiving device 1078, and the control device 1082 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Figure 8 Shows Fig.10 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0259] Fig.11 is a block diagram illustrating a specific implementation of gNB 1160. gNB 1160 may be combined with Figure 1 An example of a gNB 160 is described. The gNB 1160 may include a higher layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[0260] The high-level processor 1123 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1123 may obtain a transport block from the physical layer. The high-level processor 1123 may send / obtain high-level messages such as RRC messages and MAC messages to / from the high-level layer of the UE. The high-level processor 1123 may provide a transport block to the PDSCH transmitter and provide a transmission parameter related to the transport block to the PDCCH transmitter.

[0261] The DL transmitter 1125 may multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmit antenna 1131. The UL receiver 1133 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1131. The PUCCH receiver 1135 may provide UCI to the higher layer processor 1123. The PUSCH receiver 1137 may provide the received transport block to the higher layer processor 1123.

[0262] Fig.12 1 is a block diagram showing a specific implementation of UE 1202. UE 1202 may be combined with Figure 1An example of a UE 102 is described. The UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0263] The high-layer processor 1223 can manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-layer parameters to the physical layer. The high-layer processor 1223 can obtain a transport block from the physical layer. The high-layer processor 1223 can send / obtain high-layer messages such as RRC messages and MAC messages to / from the high-layer of the UE. The high-layer processor 1223 can provide a transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0264] The DL receiver 1243 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1231. The PDCCH receiver 1245 may provide the DCI to the higher layer processor 1223. The PDSCH receiver 1247 may provide the higher layer processor 1223 with the received transport block.

[0265] As described above, some methods for DL ​​and / or UL transmission may be applied (e.g., specified). Here, a combination of one or more of some methods described herein may be applied to DL and / or UL transmission. The systems and methods may not exclude a combination of one or more of some methods described herein.

[0266] It should be noted that the names of the physical channels described herein are examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH," "new generation (G) PDCCH, GPDSCH, GPUCCH, and GPUSCH," etc.

[0267] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Optical disks, where magnetic disks usually reproduce data magnetically, optical disks reproduce data optically using lasers.

[0268] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0269] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with each other and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0270] It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

[0271] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls the CPU, etc. in a manner that implements the functions according to the system and method (a program that causes the computer to operate). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, the information is stored in various ROMs or HDDs, and is read by the CPU whenever necessary for modification or writing. As a recording medium on which the program is stored, any of a semiconductor (e.g., ROM, nonvolatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., a magnetic tape, a floppy disk, etc.), etc. is possible. In addition, in some cases, the functions according to the system and method described herein are implemented by running the loaded program, and in addition, the functions according to the system and method are implemented based on instructions from the program and in combination with an operating system or other application programs.

[0272] In addition, in the case where the program is available on the market, the program stored on a portable recording medium may be distributed, or the program may be transferred to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. In addition, some or all of the gNB 160 and UE 102 according to the systems and methods described herein may be implemented as LSI, which is a typical integrated circuit. Each functional block of the gNB 160 and UE 102 may be built into a chip separately, and some or all of the functional blocks may be integrated into a chip. In addition, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block may be implemented using a dedicated circuit or a general-purpose processor. In addition, if an integrated circuit technology that replaces LSI emerges as semiconductor technology continues to advance, an integrated circuit applying the technology may also be used.

[0273] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be realized or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices or discrete hardware components or a combination thereof. The general-purpose processor can be a microprocessor, or alternatively, the processor can be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described herein can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of making an integrated circuit replacing the current integrated circuit appears due to the progress of semiconductor technology, the integrated circuit produced by the technology can also be used.

[0274] <Cross Reference>

[0275] This nonprovisional application claims priority under 35 U.S.C. 119 to provisional application No. 62 / 931,984, filed on November 7, 2019, the entire contents of which are hereby incorporated by reference.

Claims

1. A user equipment UE, the UE comprising: a receiving circuit, the receiving circuit being configured to receive a radio resource control RRC message, the RRC message comprising first information for indicating a value of a first scrambling identity ID and second information for indicating a value of a second scrambling ID, wherein the RRC message comprises third information, The receiving circuit is configured to receive downlink control information DCI on a physical downlink control channel PDCCH, wherein the DCI is used for scheduling a physical downlink shared channel PDSCH. The receiving circuit is configured to receive a demodulation reference signal DMRS for the PDSCH, wherein a sequence of the DMRS is generated based on a first value, wherein The third information is used to configure whether the number of bits of the DCI used to indicate the initialization of the DMRS sequence is 0 bit or 1 bit, In the case where the number of bits used to indicate the initialization of the DMRS sequence is the 1 bit, a) the first value is indicated by using the 1 bit used to indicate the initialization of the DMRS sequence; and b) the first value corresponds to any one of the value of the first scrambling ID or the value of the second scrambling ID; and When the number of bits used to indicate the initialization of the DMRS sequence is the 0 bit, the first value is 0.

2. A base station device, comprising: a transmission circuit, the transmission circuit being configured to transmit a radio resource control RRC message, the RRC message comprising first information for indicating a value of a first scrambling identity ID, and second information for indicating a value of a second scrambling ID, wherein the RRC message comprises third information, The transmission circuit is configured to transmit downlink control information DCI on a physical downlink control channel PDCCH, wherein the DCI is used for scheduling a physical downlink shared channel PDSCH. The transmission circuit is configured to transmit a demodulation reference signal DMRS for the PDSCH, wherein a sequence of the DMRS is generated based on a first value, wherein The third information is used to configure whether the number of bits of the DCI used to indicate the initialization of the DMRS sequence is 0 bit or 1 bit, In the case where the number of bits used to indicate the initialization of the DMRS sequence is the 1 bit, a) the first value is indicated by using the 1 bit used to indicate the initialization of the DMRS sequence; and b) the first value corresponds to any one of the value of the first scrambling ID or the value of the second scrambling ID; and When the number of bits used to indicate the initialization of the DMRS sequence is the 0 bit, the first value is 0.

3. A communication method of a user equipment UE, the communication method comprising: receiving a radio resource control (RRC) message, the RRC message comprising first information indicating a value of a first scrambling identity (ID), second information indicating a value of a second scrambling ID, wherein the RRC message comprises third information, receiving downlink control information DCI on a physical downlink control channel PDCCH, the DCI being used for scheduling a physical downlink shared channel PDSCH, and A demodulation reference signal DMRS for the PDSCH is received, wherein a sequence of the DMRS is generated based on a first value, wherein The third information is used to configure whether the number of bits of the DCI used to indicate the initialization of the DMRS sequence is 0 bit or 1 bit, In the case where the number of bits used to indicate the initialization of the DMRS sequence is the 1 bit, a) the first value is indicated by using the 1 bit used to indicate the initialization of the DMRS sequence; and b) the first value corresponds to any one of the value of the first scrambling ID or the value of the second scrambling ID; and When the number of bits used to indicate the initialization of the DMRS sequence is the 0 bit, the first value is 0.

Images