User equipment, base station and method for uplink signal cancellation

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a radio resource control (RRC) message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format. The DCI format includes an interrupt transmission indication. The UE also includes a processing circuit configured to cancel a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interrupt transmission indication. The information is configured for each uplink bandwidth part (UL BWP). The interrupt transmission indication applies to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure. The interrupt transmission indication does not apply to a PRACH transmission associated with a contention-free random access procedure.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems and, more particularly, to user equipment (UE), base stations, and methods for uplink signal cancellation. 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, and enhanced functionality. A wireless communication system can provide communication for multiple wireless communication devices, each of which can be served by a base station. A base station is a device that communicates with wireless communication devices.

[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 use a communication structure to communicate with one or more devices. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods that improve 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 information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format, the DCI format including an interruption transmission indication; and a processing circuit configured to cancel a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interruption transmission indication, wherein the information is configured for each uplink bandwidth part (UL BWP), the interruption transmission indication is applicable to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure, and the interruption transmission indication is not applicable to a PRACH transmission associated with a contention-free random access procedure.

[0006] In one example, a base station device includes: a transmission circuit configured to transmit a radio resource control (RRC) message, the RRC message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format, the DCI format including an interruption transmission indication; and a processing circuit configured to consider that a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interruption transmission indication is canceled, wherein the information is configured for each uplink bandwidth part (UL BWP), the interruption transmission indication is applicable to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure, and the interruption transmission indication is not applicable to a PRACH transmission associated with a contention-free random access procedure.

[0007] In one example, a communication method of a user equipment (UE) includes: receiving a radio resource control (RRC) message, the RRC message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format, the DCI format including an interruption transmission indication; and canceling a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interruption transmission indication, wherein the information is configured for each uplink bandwidth part (UL BWP), the interruption transmission indication is applicable to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure, and the interruption transmission indication is not applicable to a PRACH transmission associated with a contention-free random access procedure.

[0008] In one example, a communication method of a base station device includes: transmitting a radio resource control (RRC) message, the RRC message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format, the DCI format including an interruption transmission indication; and considering that a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interruption transmission indication is canceled, wherein the information is configured for each uplink bandwidth part (UL BWP), the interruption transmission indication is applicable to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure, and the interruption transmission indication is not applicable to a PRACH transmission associated with a contention-free random access procedure. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] 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 Examples of multiple parameter sets are shown.

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

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

[0013] Figure 5 An example of a random access procedure is shown.

[0014] Figure 6 Various components that may be utilized in a UE are shown.

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

[0016] Figure 8 is a block diagram illustrating one embodiment of a UE in which one or more of the systems and / or methods described herein may be implemented.

[0017] Figure 9 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.

[0018] Figure 10 is a block diagram illustrating a specific implementation of a gNB.

[0019] Figure 11 is a block diagram illustrating a specific implementation of a UE. DETAILED DESCRIPTION

[0020] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a radio resource control (RRC) message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format. The DCI format includes an interrupt transmission indication. The UE also includes a processing circuit configured to cancel a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interrupt transmission indication. The information is configured for each uplink bandwidth part (UL BWP). The interrupt transmission indication applies to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure. The interrupt transmission indication does not apply to a PRACH transmission associated with a contention-free random access procedure.

[0021] The present invention describes a base station device. The base station device includes a transmission circuit configured to transmit a radio resource control (RRC) message, the RRC message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format. The DCI format includes an interruption transmission indication. The base station device also includes a processing circuit configured to consider that a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interruption transmission indication is canceled. The information is configured for each uplink bandwidth part (UL BWP). The interruption transmission indication applies to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure. The interruption transmission indication does not apply to a PRACH transmission associated with a contention-free random access procedure.

[0022] The present invention describes a communication method for a user equipment (UE). The communication method includes receiving a radio resource control (RRC) message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format. The DCI format includes a transmission interruption indication. The communication method also includes canceling a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the transmission interruption indication. The information is configured for each uplink bandwidth part (UL BWP). The transmission interruption indication applies to physical random access channel (PRACH) transmissions associated with a contention-based random access procedure. The transmission interruption indication does not apply to PRACH transmissions associated with a contention-free random access procedure.

[0023] The present invention describes a communication method for a base station apparatus. The communication method includes transmitting a radio resource control (RRC) message, the RRC message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format. The DCI format includes an interruption transmission indication. The communication method also includes canceling a physical uplink shared channel (PUSCH) transmission in a physical resource block and / or symbol indicated by the interruption transmission indication. The information is configured for each uplink bandwidth part (UL BWP). The interruption transmission indication applies to a physical random access channel (PRACH) transmission associated with a contention-based random access procedure. The interruption transmission indication does not apply to a PRACH transmission associated with a contention-free random access procedure.

[0024] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that develops 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.

[0025] 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 needs. 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).

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

[0027] A wireless communication device may be an electronic device that transmits 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, smartphones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, wireless communication devices are generally referred to as UEs. However, since the scope of the present disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to represent the more general term "wireless communication device." UE may also be more generally referred to as a terminal device.

[0028] In 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. Because the scope of the present disclosure should not be limited to 3GPP standards, the terms "base station," "Node B," "eNB," "gNB," and "HeNB" may be used interchangeably herein to refer to the more general term "base station." Furthermore, the term "base station" may be used to refer to 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 refer to a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.

[0029] It should be noted that, as used herein, a "cell (e.g., a serving cell)" can be any communication channel designated by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced), and all or a subset thereof, adopted by 3GPP as an authorized frequency band (e.g., a frequency band) for communication between an eNB and a UE. It should also be noted that, in the general description of E-UTRA and E-UTRAN, as used herein, a "cell (e.g., a serving cell)" can 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 can be indicated in system information transmitted on the downlink resources.

[0030] The fifth-generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions the use of 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. Furthermore, 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 receive downlink signals and / or transmit uplink signals in the BWP of the serving cell.

[0031] In order for services to efficiently use time, frequency, and / or space resources, 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.

[0032] 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 generally described and illustrated in the drawings herein can be arranged and designed in a variety of different implementations. Therefore, the following more detailed description of several implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0033] Figure 1is a block diagram illustrating one implementation 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 and receives electromagnetic signals from the gNB 160 using 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.

[0034] UE 102 and gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, UE 102 may transmit information or data to 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)). For example, one or more gNBs 160 may also transmit information or data to one or more UEs 102 using one or more downlink channels 119. 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)). Other types of channels and / or signals may also be used.

[0035] 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 operations 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.

[0036] 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 a signal 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.

[0037] 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 operations module 124 may use to perform one or more operations.

[0038] Generally speaking, the UE operations module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operations module 124 may include one or more of the UE scheduling modules 126.

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

[0040] 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 higher layers.

[0041] For example, in the uplink, a PRACH (physical random access channel) may be defined. In some methods, the PRACH (e.g., a 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).

[0042] 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 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 the PUSCH), semi-persistent CSI (e.g., transmitted on the PUSCH and / or PUCCH) and / or periodic CSI (e.g., transmitted on the PUSCH and / or 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)).

[0043] Here, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. For example, DL-SCH may be mapped to PDSCH. In addition, UL-SCH may be mapped to PUSCH. In addition, a transport block (TB) and / or 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 (for example, 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.

[0044] 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).

[0045] For example, DCI format 1_0 for scheduling the PDSCH in a cell may be defined as a DCI format for the 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.

[0046] 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, or alternatively, the DCI included in DCI format 1_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_0 may be a TPC (e.g., transmit power control) command for a scheduled PUCCH. Additionally or alternatively, the DCI included in DCI format 1_0 may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_0 may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_0 may be a priority indicator.

[0047] Additionally or alternatively, DCI format 1_1 for scheduling the PDSCH in the cell may be defined as a DCI format for the downlink. Additionally or alternatively, a C-RNTI, a CS-RNTI, an MCS-C-RNTI, and / or a 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.

[0048] For example, the DCI included in DCI format 1_1 may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a TPC command for a scheduled PUCCH. Additionally or alternatively, the DCI included in DCI format 1_1 may be a CSI request for requesting (e.g., triggering) transmission of CSI (e.g., a CSI report (e.g., an aperiodic CSI report)). Additionally or alternatively, the DCI included in DCI format 1_1 may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a priority indicator.

[0049] Additionally or alternatively, DCI format 0_0 for scheduling the PUSCH in the cell may be defined as the DCI format for the uplink. Additionally or alternatively, a C-RNTI, a CS-RNTI, a temporary C-RNTI, an MCS-C-RNTI, and / or a 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 the CSS and / or the USS. Alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0050] 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 new data indicator. Additionally or alternatively, the DCI included in DCI format 0_0 may be a redundancy version. Additionally or alternatively, the DCI included in DCI format 0_0 may be a TPC command for a scheduled PUSCH. Additionally or alternatively, the DCI included in DCI format 0_0 may be a priority indicator.

[0051] Additionally or alternatively, DCI format 0_1 ​​for scheduling the PUSCH in the cell may be defined as a DCI format for the uplink. Here, DCI format 0_1 ​​may be described as a 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., first DCI format 601). That is, the first DCI format 601 may be a DCI format 0_1 ​​having a CRC scrambled by C-RNTI, CS-RNTI, and / or MCS-C-RNTI. Here, as described below, the DCI format 0_1 ​​having a CRC scrambled by MCS-C-RNTI and / or the first RNTI may be a second DCI format 603. Additionally or alternatively, DCI format 0_1 ​​(i.e., first DCI format 601) may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0052] For example, the DCI included in DCI format 0_1 ​​may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a TPC command for a scheduled PUSCH. Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a CSI request for requesting a CSI report. Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a priority indicator.

[0053] Here, for simplicity of description, in some specific implementations, it may be assumed that the PUSCH transmission scheduled as described herein using a PDCCH (e.g., DCI format 0_0 and / or DCI format 0_1) with a CRC scrambled by C-RNTI, CS-RNTI and / or MCS-C-RNTI is included in the first PUSCH transmission.

[0054] Additionally or alternatively, DCI format 2_1 may be defined as a DCI format (e.g., a DCI format used for other purposes) for notifying UE 102 that PRBs and / or symbols (e.g., OFDM symbols and / or SC-FDMA symbols) in which no transmission is intended for the UE (e.g., from gNB 160 to UE 102 (i.e., in the downlink)) are assumed. Additionally or alternatively, DCI format 2_1 may be used to notify PRBs and / or symbols in which no transmission is performed from the UE (e.g., from UE 102 to gNB 160 (i.e., in the uplink)).

[0055] Additionally or alternatively, an interrupt RNTI (e.g., INT-RNTI) and / or a first RNTI may be used to transmit DCI format 2_1. Additionally or alternatively, DCI format 2_1 may be monitored (e.g., transmitted and / or mapped) in the CSS. For example, when an INT-RNTI is used to transmit DCI format 2_1 (e.g., when a CRC attached to DCI format 2_1 is scrambled by the INT-RNTI), DCI format 2_1 may be used to notify UE 102 that no PRBs and / or symbols are assumed for transmission by the UE. Additionally or alternatively, when a first RNTI is used to transmit DCI format 2_1 (e.g., when a CRC attached to DCI format 2_1 is scrambled by the first RNTI), DCI format 2_1 may be used to notify PRBs and / or symbols for which no transmission from the UE is performed.

[0056] For example, the DCI included in DCI format 2_1 (e.g., with a CRC scrambled by the INT-RNTI) may be indication 1 (e.g., preemption indication 1), indication 2 (e.g., preemption indication 2), ... indication N (e.g., preemption indication N) (e.g., N=14). That is, the DCI included in DCI format 2_1 (e.g., with a CRC scrambled by the INT-RNTI) may be 14 bits. For example, a bit value of "0" of the DCI included in DCI format 2_1 (e.g., with a CRC scrambled by the INT-RNTI) may be used to indicate transmission to UE 102 (e.g., in the downlink (e.g., on the PDSCH)) in the corresponding PRB and / or symbol (e.g., a group of PRBs and / or a group of symbols). Additionally or alternatively, a bit value of "1" in the DCI included in DCI format 2_1 (e.g., with a CRC scrambled by the INT-RNTI) may be used to indicate that there is no transmission to the UE 102 (e.g., in the downlink (e.g., on the PDSCH)) in the corresponding PRB and / or symbol. Here, information for configuring (e.g., determining) the corresponding PRB and / or symbol may be configured using an RRC message. That is, the gNB 160 may transmit information for configuring (e.g., determining) the PRB and / or symbol for transmission and / or non-transmission (e.g., in the downlink) using an RRC message. And, the UE 102 may determine the corresponding PRB and symbol for transmission and / or non-transmission (e.g., in the downlink).

[0057] Additionally or alternatively, DCI format 2_X may be used to signal PRBs and / or symbols in which no transmission from a UE (e.g., from UE 102 to gNB 160 (i.e., in the uplink) is performed. Additionally or alternatively, a C-RNTI, an INT-RNTI, and / or a first RNTI may be used to transmit DCI format 2_X. Additionally or alternatively, DCI format 2_X may be monitored (e.g., transmitted and / or mapped) in a USS and / or CSS.

[0058] For simplicity of description, in some embodiments, it may be assumed that DCI format 2_1 (e.g., having a CRC scrambled by the first RNTI) and / or DCI format 2_X (e.g., having a CRC scrambled by the C-RNTI, INT-RNTI, and / or the first RNTI) described herein are included in DCI format 2_Y. That is, DCI format 2_Y may be used to indicate PRBs and / or symbols in which no transmission from the UE (e.g., UL signal transmission from UE 102 to gNB 160 in the uplink) is performed. Additionally or alternatively, DCI format 2_Y may be monitored (e.g., transmitted and / or mapped) in the USS and / or CSS.

[0059] Additionally or alternatively, DCI format Y may be used to indicate PRBs and / or symbols in which UE 102 is not permitted (e.g., not authorized) to perform UL signal transmission. Additionally or alternatively, DCI format 2_1 may be used to indicate PRBs and / or symbols in which UE 102 cancels UL signal transmission (e.g., stops performing UL signal transmission). For example, (e.g., when UE 102 is scheduled (e.g., authorized) to perform UL signal transmission), DCI format 2_1 may be used to indicate PRBs and / or symbols in which UE 102 cancels corresponding (i.e., scheduled) UL signal transmission (e.g., stops performing corresponding UL signal transmission). For example, when a PRB and / or symbol (e.g., scheduled for UL signal transmission) overlaps with a specific PRB and / or specific symbol, UE 102 may cancel UL signal transmission (e.g., stop performing UL signal transmission, do not perform UL signal transmission) in the specific PRB and / or specific symbol.

[0060] For example, the DCI included in DCI format 2_Y may be indication 1 (e.g., preemption indication 1), indication 2 (e.g., preemption indication 2), ... indication N (e.g., preemption indication N) (e.g., N=14). That is, the DCI included in DCI format Y may be 14 bits. For example, a bit value of "0" of the DCI included in DCI format 2_Y may be used to indicate a transmission from UE 102 (e.g., in the uplink) in the corresponding PRB and / or symbol (e.g., a group of PRBs and / or a group of symbols). Additionally or alternatively, a bit value of "1" of the DCI included in DCI format 2_Y may be used to indicate that there is no transmission from UE 102 (e.g., in the uplink) in the corresponding PRB and / or symbol. Here, the information for configuring (e.g., determining) the corresponding PRB and / or symbol may be configured by using an RRC message. That is, the gNB 160 may transmit information for configuring (e.g., determining) PRBs and / or symbols for transmission and / or non-transmission (e.g., in the uplink) using an RRC message. Furthermore, the UE 102 may determine the corresponding PRBs and symbols for transmission and / or non-transmission (e.g., in the uplink).

[0061] Here, as described above, the RNTI (e.g., Radio Network Temporary Identifier) ​​allocated to UE 102 may be used for transmission of DCI (e.g., one or more DCI formats, one or more DL control channels (e.g., one or more PDCCHs)). That is, gNB 160 may transmit information for configuring (e.g., allocating) the RNTI to UE 102 (e.g., by using an RRC message).

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

[0063] 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), INT-RNTI (Interruption RNTI) and / or First RNTI.

[0064] 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 scheduling transmission based on configuration-based authorization. Additionally or alternatively, SI-RNTI can be used to identify a system message (SI) (e.g., an SI message) mapped on the BCCH and dynamically carried on the 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. Additionally or alternatively, INT-RNTI can be a preemption identifier in the downlink. Additionally or alternatively, the INT-RNTI may be a preemption identifier in the uplink. The first RNTI may be different from the C-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, temporary C-RNTI, MCS-C-RNTI, and / or INT-RNTI. Additionally or alternatively, the first RNTI may be a preemption identifier in the uplink.

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

[0066] Furthermore, the PDSCH and / or PUSCH may be used to transmit information from higher layers (e.g., the radio resource control (RRC) layer and / or the 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 RRC messages (RRC signals). 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 MAC control elements (MAC CEs). Herein, the RRC messages and / or MAC CEs are also referred to as higher layer signals.

[0067] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast a Master Information Block (MIB). Here, system information may be divided into a MIB and multiple System Information Blocks (SIBs). 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.

[0068] In some methods, in the downlink, an SS (synchronization signal) may be defined. The SS may be used to acquire time and / or frequency synchronization with a cell. The SS may include a PSS (primary synchronization signal). Additionally or alternatively, the SS may include an SSS (secondary synchronization signal). For example, the PSS, SSS, and / or PBCH may be used to identify a physical layer cell identifier. Additionally or alternatively, the PSS, SSS, and / or PBCH may be used to carry information identifying an SF number (system frame number), an OFDM symbol index, a time slot index in a radio frame, and / or a radio frame number. Additionally or alternatively, the PSS, SSS, PBCH, and a demodulation reference signal for the PBCH (e.g., a DM RS) may form a block of SS and / or PBCH (e.g., an SS / PBCH block). For example, in the time domain, an SS / PBCH block may have four OFDM symbols. The UE 102 may assume that the reception timing of the SS / PBCH block may be in consecutive symbols.

[0069] In radio communications for the uplink, an uplink reference signal (e.g., UL RS) may be defined as an uplink physical signal. For example, the UL RS may include a demodulation reference signal (e.g., a demodulation reference signal associated with the PUSCH and / or a demodulation reference signal associated with the PUSCH). For example, the demodulation reference signal associated with the PUSCH may be transmitted together with the PUSCH (e.g., a scheduled PUSCH). In addition, the demodulation reference signal associated with the PUCCH may be transmitted together with the PUCCH. Additionally or alternatively, the UL RS may include a sounding reference signal (e.g., SRS). Additionally or alternatively, in radio communications for the downlink, the 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 the physical layer.

[0070] Here, for simplicity of description, in some implementations, it may be assumed that the downlink physical channels and / or downlink physical signals described herein are included in downlink signals (e.g., DL signals). Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the uplink physical channels and / or uplink physical signals described herein are included in uplink signals (i.e., UL signals).

[0071] Furthermore, in carrier aggregation (CA), gNB 160 and 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, gNB 160 may transmit information for configuring one or more secondary cells to form a serving cell set together with the primary cell using an RRC message. That is, the serving cell set may include one primary cell and one or more secondary cells. Here, the primary cell may be always activated. Furthermore, gNB 160 may activate one or more secondary cells within the configured secondary cells. 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). Furthermore, 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).

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

[0073] For example, the primary cell may be a serving cell operating a primary frequency (e.g., an MCG cell), in which the UE 102 may perform an initial connection establishment procedure and / or initiate a connection re-establishment procedure. Additionally, 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., when the UE 102 performs a reconfiguration (e.g., a reconfiguration with a synchronization procedure)).

[0074] 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, PUCCH transmission may be performed (e.g., supported) only on the special cell. That is, PUCCH transmission 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.

[0075] 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).

[0076] 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) 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 the secondary cell using an RRC message. UE 102 may then identify the index of the serving cell (e.g., the secondary cell) based on this information.

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

[0078] The UE operations module 124 may provide 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.

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

[0080] 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 to expect for the transmission from the gNB 160.

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

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

[0083] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of the 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.

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

[0085] 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 operations 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.

[0086] 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 a signal 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.

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

[0088] Generally, 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 of the gNB scheduling modules 194. The gNB scheduling module 194 may perform scheduling of downlink and / or uplink transmissions as described herein.

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

[0090] 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 to be expected for transmissions from one or more UEs 102.

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

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

[0093] 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 modulation type (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.

[0094] 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 (or 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.

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

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

[0097] Figure 2 An example of multiple parameter sets 201 is shown. Figure 2As shown, multiple parameter sets 201 (e.g., multiple subcarrier spacings) may be supported. For example, μ (e.g., subcarrier spatial 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 the downlink and / or uplink. Here, 15 kHz may be a reference parameter set 201. For example, REs of the reference parameter set 201 may be defined as having a subcarrier spacing of 15 kHz 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.

[0098] Additionally or alternatively, the number of OFDM symbols per slot may be determined based on μ (eg, subcarrier spacing 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.

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

[0100] exist Figure 3 In the example, a subframe 369 may include 387 symbols.

[0101] Additionally or alternatively, a resource block 391 may include multiple resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) may be employed, 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. The region 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 indices in the frequency domain and time domain, respectively.

[0102] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) access scheme, also known as discrete Fourier transform spread OFDM (DFT-S-OFDM), may be employed. 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 region 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 indices in the frequency and time domains, respectively.

[0103] 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 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:

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

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

[0106] 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). UE 102 may monitor the set of PDCCH candidates in the search space. The 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).

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

[0108] The USS may be used to transmit 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, a CS-RNTI, an INT-RNTI, and / or a first RNTI.

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

[0110] 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, an index of a 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.

[0111] 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., the initial BWP) using an RRC message (e.g., an MIB, an SIB, and / or a dedicated RRC message). Furthermore, the index of the initial BWP (e.g., the initial DL BWP) may be "0." That is, an index of "0" (e.g., a value of "0") may be applied (e.g., defined) to the initial BWP (e.g., the initial DL BWP). For example, (e.g., for a primary cell), the initial BWP (i.e., the BWP with an index of "0") may be the BWP used for initial access. Additionally or alternatively, (e.g., for a secondary cell), the initial BWP (i.e., the BWP with an index of "0") may be the BWP configured for the UE to first operate in the secondary cell when the secondary cell is activated.

[0112] Here, the gNB 160 may transmit information for configuring the index of the DL BWP (e.g., an index other than "0") using an RRC message (e.g., an MIB, an SIB, and / or a dedicated RRC message). Furthermore, the gNB 160 may transmit information for configuring the index of the UL BWP (e.g., an index other than "0") using an RRC message (e.g., an MIB, an SIB, and / or a dedicated RRC message). That is, the index of the DL BWP may be used to identify the DL BWP. Furthermore, 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. Furthermore, the UE 102 may identify the UL BWP based on the index of the UL BWP.

[0113] As described above, CORESET #0 may be referred to as a public CORESET. Furthermore, CORESETs other than CORESET #0 may be referred to as UE-specific CORESETs. That is, CORESETs with indices "X" (e.g., X=1, 2, 3, ...) other than index "0" may be referred to as UE-specific CORESETs. 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.

[0114] 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 the CORESET. For example, the UE 102 may monitor the PDCCH (e.g., PDCCH candidates) in the CSS set associated with CORESET#0. In addition, the UE 102 may monitor the PDCCH (e.g., PDCCH candidates) in the CSS set not associated with CORESET#0. In addition, the UE may monitor the PDCCH (e.g., PDCCH candidates) in the USS (e.g., a USS not associated with the 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 the serving cell.

[0115] Additionally or alternatively, gNB 160 may transmit second information for configuring the search space set using an RRC message. For example, the second information may be configured for each search space set. For example, the second information may include information for configuring the index of the search space set. Additionally or alternatively, the second information may include information for configuring the index of the CORESET associated with the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring periodicity and / or a PDCCH monitoring offset at which UE 102 monitors PDCCHs in the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring pattern within a timeslot. For example, the information for indicating the PDCCH monitoring pattern may indicate the first symbol within the timeslot for PDCCH monitoring. For example, UE 102 may determine a PDCCH monitoring timing based on the PDCCH monitoring periodicity, the PDCCH monitoring offset, and / or the PDCCH monitoring pattern within the timeslot.

[0116] Additionally or alternatively, the second information may include information for indicating the type of the search space set (e.g., information for indicating whether the search space set is a CSS or a USS). Additionally or alternatively, the second information may include information for instructing UE 102 to monitor one or more DCI formats of 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 PDCCH (e.g., PDCCH candidates). Additionally or alternatively, if the search space set is a CSS, DCI format 2_1 and / or DCI format 2_Y may be configured to monitor PDCCH (e.g., PDCCH candidates). Here, the DCI format for monitoring the PDCCH in the CSS may be scrambled by C-RNTI, CS-RNTI, RA-RNTI, temporary C-RNTI, SI-RNTI, INT-RNTI, and / or the first RNTI. For example, if the search space set is a CSS, the UE 102 may be configured to monitor the PDCCH (e.g., candidates for the PDCCH) for DCI format 2_1 (e.g., with a CRC scrambled by an INT-RNTI) and / or DCI format 2_Y (e.g., with a CRC scrambled by a C-RNTI, an INT-RNTI, and / or a first RNTI).

[0117] Additionally or alternatively, if the search space set is a USS (e.g., if the search space set is configured as a USS), DCI format 0_0, DCI format 1_0, DCI format 0_Y, and / or DCI format 1_X may be configured to monitor a PDCCH (e.g., a PDCCH candidate). Additionally or alternatively, if the search space set is a USS, DCI format 0_1, DCI format 1_1, DCI format 0_Y, and / or DCI format 1_X may be configured to monitor a PDCCH (e.g., a PDCCH candidate). For example, if the search space set is a 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 a PDCCH (e.g., a PDCCH candidate). For example, if the search space set is a 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 the PDCCH. Additionally, if the search space set is a 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 the PDCCH. Here, the DCI format used to monitor the PDCCH in the USS may be scrambled by the C-RNTI, the CS-RNTI, and / or the first RNTI. For example, the second information may be configured for each search space set. That is, the second information may be configured for each search space set in the search space set.

[0118] Here, the search space set index "0" (i.e., the search space set value "0") can be configured using the MIB and / or SIB. For example, the search space set index "0" can be used to identify a common search space set configured in the MIB and / or SIB. That is, the index of a search space set other than the value "0" can be configured as the search space index. Furthermore, the index of a search space set with the value "0" can be configured using information related to search space-zero. Furthermore, the search space set index "0" can be configured 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) using the MIB. Additionally or alternatively, the gNB 160 can transmit information for configuring search space set #0 using the SIB. Additionally or alternatively, the gNB 160 can transmit information for configuring search space set #0 using a dedicated RRC message. Here, search space set #0 may be configured for an initial BWP (eg, initial DL BWP).

[0119] As described above, search space set #0 may be referred to as a common search space set. Furthermore, search space sets other than search space set #0 may be referred to as UE-specific search space sets. Specifically, search space sets with indices "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 the UE-specific search space set) using a dedicated RRC message.

[0120] 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) using RRC messaging (e.g., for reception by UE 102). Additionally or alternatively, gNB 160 may indicate active DL BWPs using a DCI format for the downlink. For example, for each DL BWP in a DL BWP set, gNB 160 may configure the subcarrier spacing, cyclic prefix, number of consecutive PRBs 491 (e.g., bandwidth of the PRBs), and / or index (e.g., index of the DL BWP) in the DL BWP set using RRC messaging.

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

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

[0123] Figure 5 An example of a random access procedure is shown. Figure 5 As shown, the random access procedure may take two different forms: contention-based random access (CBRA) (eg, a CBRA procedure) and contention-free random access (CFRA) (eg, a CFRA procedure).

[0124] For example, CBRA may include four steps (e.g., message 1 (e.g., Msg 1 as a first step), message 2 (e.g., Msg 2 as a second step), message 3 (e.g., Msg 3 as a third step), and message 4 (e.g., Msg 4 as a fourth step)).

[0125] For example, for CBRA, a Msg 1 transmission (e.g., in the uplink from UE 102 to gNB 160) may include a random access preamble transmission on the PRACH (e.g., a PRACH transmission). Here, for the Msg 1 transmission for CBRA, the UE 102 may randomly select a random access preamble. For example, for the Msg 1 transmission for CBRA, the UE 102 may randomly select a random access preamble with equal probability from among the random access preambles associated with the selected SS / PRB block and / or the selected random access preamble group. That is, for CBRA, the UE 102 may transmit a randomly selected random access preamble.

[0126] Additionally or alternatively, for CBRA, a Msg 2 transmission (e.g., in the downlink from gNB 160 to UE 102) may include a random access response transmission on the DL-SCH (e.g., a PDSCH transmission). As described above, the PDSCH for the random access response transmission may be scheduled using a PDCCH (e.g., DCI format 1_0) with a CRC scrambled by the RA-RNTI. Additionally or alternatively, the random access response may include a random access response grant for scheduling a PUSCH (e.g., for Msg 3 transmission). Additionally or alternatively, the random access response may include a temporary C-RNTI (e.g., a value of the temporary C-RNTI) for scheduling a retransmission on the PUSCH (e.g., for Msg 3 retransmission).

[0127] Additionally or alternatively, for CBRA, Msg 3 transmissions (e.g., in the uplink from UE 102 to gNB 160) may include scheduled transmissions on the UL-SCH (e.g., PUSCH transmissions). That is, UE 102 may perform a transmission (e.g., an initial transmission) on the PUSCH scheduled using a random access response grant. Additionally or alternatively, UE 102 may perform a transmission (e.g., a retransmission) on the PUSCH scheduled using a PDCCH (e.g., DCI format 1_0) with a CRC scrambled by a temporary C-RNTI.

[0128] Here, for CBRA, Msg 3 may include an initial transmission on the PUSCH (e.g., an initial transmission of Msg 3) and / or a retransmission on the PUSCH (e.g., a retransmission of Msg 3). As described above, the initial transmission on the PUSCH (e.g., the initial transmission of Msg 3) may be scheduled using a random access response grant. In addition, the initial transmission on the PUSCH (e.g., the initial transmission of Msg 3) may be associated with the random access response grant. In addition, the initial transmission on the PUSCH (e.g., the initial transmission of Msg 3) may be associated with a PDCCH (e.g., DCI format 1_0) having a CRC scrambled by the RA-RNTI. In addition, the retransmission on the PUSCH (e.g., the retransmission of Msg 3) may be associated with a PDCCH (e.g., DCI format 1_0) having a CRC scrambled by the Temporary C-RNTI.

[0129] Additionally or alternatively, Msg 4 (e.g., in the uplink from gNB 160 to UE 102) may include contention resolution.

[0130] Additionally or alternatively, CFRA may include three steps (eg, message 0 (eg, Msg 0 as a first step), message 1 (eg, Msg 1 as a second step), and message 2 (eg, Msg 2 as a third step).

[0131] For example, for CFRA, Msg 0 transmission (e.g., in the downlink from gNB 160 to UE 102) may include a random access preamble allocation (e.g., an RA preamble allocation). That is, for CFRA, gNB 160 may allocate (e.g., by using a PDCCH (e.g., DCI format 1_0) with a CRC scrambled by the C-RNTI) a random access preamble (e.g., for random access preamble transmission on the PRACH in Msg 1) to UE 102. For example, where the CRC of DCI format 1_0 is scrambled by the C-RNTI and the frequency domain resource allocation field is all ones, DCI format 1_0 (e.g., DCI included in DCI format 1_0 (e.g., a field of the DCI)) may be used to indicate an index of the random access preamble (e.g., a random access preamble index). That is, for CFRA, an index (e.g., a random access preamble index) corresponding to a random access preamble (e.g., for message 1 transmission) may be allocated to UE 102 (e.g., provided, indicated, configured). That is, CFRA (e.g., a CFRA procedure) may be initiated by a PDCCH order. In addition, if the CRC of DCI format 1_0 is scrambled by the C-RNTI and the frequency domain resource allocation field is all ones, DCI format 1_0 may be used for a random access procedure (e.g., CFRA, a CFRA procedure).

[0132] Additionally or alternatively, for CFRA, UE 102 may perform a random access preamble transmission (e.g., Message 1 transmission) on the PRACH (e.g., in the uplink from UE 102 to gNB 160). Here, for CFRA, UE 102 may transmit a random access preamble corresponding to an assigned index (e.g., a random access preamble index).

[0133] Additionally or alternatively, for CFRA, a Msg 2 transmission (e.g., in the downlink from gNB 160 to UE 102) may be included with a random access response transmission on the DL-SCH (e.g., a PDSCH transmission). For example, for CFRA, the PDSCH for the random access response transmission may be scheduled using a PDCCH (e.g., DCI format 1_0) with a CRC scrambled by the C-RNTI and / or RA-RNTI. Additionally or alternatively, the random access response may include a random access response grant, which is used for scheduling the PUSCH. Additionally or alternatively, the random access response may include a temporary C-RNTI (e.g., a value of the temporary C-RNTI) which is used for scheduling retransmissions on the PUSCH. Here, for CFRA, the PUSCH transmission and / or PUSCH retransmission corresponding to the random access response (e.g., the random access response grant) is not an Msg 3 transmission (e.g., for CBRA).

[0134] That is, based on the random access response (e.g., during CFRA), a PUSCH transmission may be scheduled (e.g., in the uplink from UE 102 to gNB 160). That is, UE 102 may perform a PUSCH transmission associated with CFRA. Additionally or alternatively, UE 102 may perform a PUSCH transmission associated with the random access response during CFRA. Additionally or alternatively, UE 102 may perform a PUSCH transmission associated with a PDCCH (e.g., DCI format 1_0) with a CRC scrambled by the C-RNTI. Additionally or alternatively, UE 102 may perform a PUSCH transmission associated with a preamble transmission assigned by gNB 160. Additionally or alternatively, UE 102 may perform a PUSCH transmission associated with a PDCCH order.

[0135] As described above, for CBRA (e.g., for an associated CBRA procedure), UE 102 may perform a random access preamble transmission (e.g., on a PRACH). That is, UE 102 may perform a PRACH transmission associated with CBRA. Additionally or alternatively, for CBRA (e.g., for an associated CBRA procedure), UE 102 may perform a PUSCH transmission. Here, for simplicity of description, in some embodiments, it may be assumed that the random access preamble transmission associated with CBRA described herein (i.e., a PRACH transmission associated with CBRA) and / or the PUSCH transmission associated with CBRA described herein are included in an uplink transmission associated with CBRA (e.g., a UL transmission associated with CBRA).

[0136] In addition, as described above, for CFRA (e.g., for an associated CFRA procedure), the UE 102 may perform a random access preamble transmission (e.g., on a PRACH). That is, the UE 102 may perform a PRACH transmission associated with CFRA. Additionally or alternatively, for CFRA (e.g., for an associated CFRA procedure), the UE 102 may perform a PUSCH transmission. Here, for simplicity of description, in some embodiments, it may be assumed that the random access preamble transmission associated with CFRA described herein (i.e., a PRACH transmission associated with CFRA) and / or the PUSCH transmission associated with CFRA described herein are included in an uplink transmission associated with CFRA (e.g., a UL transmission associated with CFRA).

[0137] Additionally or alternatively, a random access procedure may be performed on a special cell. Additionally or alternatively, a random access procedure may be performed on a DL BWP (e.g., an active DL BWP) and a UL BWP (e.g., an active UL BWP). For example, if PRACH resources (e.g., PRACH opportunities) are not configured for an active UL BWP, the UE 102 may switch the active UL BWP to an initial UL BWP (e.g., a UL BWP with an index of "0"). Furthermore, if the serving cell is a special cell, the UE 102 may switch the active DL BWP to the initial DL BWP. That is, the UE 102 may perform a random access procedure on an active DL BWP (e.g., an initial DL BWP (e.g., a DL BWP with an index of "0") of a special cell) and an active UL BWP (e.g., an initial UL BWP (e.g., a UL BWP with an index of "0") of a special cell).

[0138] Additionally or alternatively, when PRACH resources (e.g., PRACH opportunities) are configured for an active UL BWP, the serving cell is a special cell, and the active DL BWP does not have the same index as the UL BWP, the UE 102 may switch the active DL BWP to an active DL BWP having the same index as the active UL BWP (i.e., the active UL BWP in which the PRACH resources are configured). That is, the UE 102 may perform a random access procedure on the active DL BWP and the active UL BWP (e.g., the index of the DL BWP may be the same as the index of the UL BWP).

[0139] As described in detail above, DCI format 2_1 and / or INT-RNTI can be used for downlink transmission interruption indication (e.g., no transmission intended for the UE in the downlink). That is, for example, DCI format 2_1 (e.g., DCI included in DCI format 2_1) can correspond to downlink transmission interruption indication. In addition, INT-RNTI can correspond to downlink transmission interruption indication. Here, downlink transmission interruption indication can correspond to downlink preemption indication (e.g., downlink preemption indication).

[0140] Additionally or alternatively, as described in detail above, DCI format 2_Y and / or the first RNTI may be used for an uplink interruption transmission indication (e.g., disallowing transmission from the UE in the uplink and / or canceling transmission in the uplink). That is, for example, DCI format 2_Y (e.g., DCI included in DCI format 2_Y) may correspond to an uplink interruption transmission indication. In addition, the first RNTI may correspond to an uplink interruption transmission indication. Here, the uplink interruption transmission indication may correspond to a preemption indication for the uplink (e.g., an uplink preemption indication).

[0141] Additionally or alternatively, gNB 160 may configure third information related to the downlink interruption transmission indication by using an RRC message. For example, gNB 160 may transmit third information for configuring UE 102 to monitor the downlink interruption transmission indication by using an RRC message (e.g., a PDCCH for INT-RNTI (e.g., DCI format 2_1 with a CRC scrambled by INT-RNTI)).

[0142] For example, the third information may include information for configuring the value of INT-RNTI (e.g., the value of INT-RNTI for the downlink interruption transmission indication (e.g., indicating preemption)). Additionally or alternatively, the third information may include information for configuring the time and / or frequency resources for the downlink interruption transmission indication. Here, the time and / or frequency resources for the downlink interruption transmission indication may correspond to PRBs and / or symbols for transmission and / or no transmission (e.g., in the downlink) (e.g., as described in detail above). Additionally or alternatively, the time and / or frequency resources for the downlink interruption transmission indication may correspond to the indication granularity of the time and / or frequency resources (e.g., the granularity of the time and / or frequency resources indicated by the downlink interruption transmission indication). Additionally or alternatively, the third information may include information for configuring the total length of the DCI payload included in the DCI format 2_1 with the CRC scrambled by the INT-RNTI.

[0143] Additionally or alternatively, the third information may include information indicating the position of a bit value (e.g., a 14-bit value) within the DCI payload (e.g., included within the DCI format 2_1 with an RC scrambled by the INT-RNTI). Here, this information may be used to indicate the position of the bit value for each serving cell. That is, gNB 106 may use this information to indicate the position of the bit value for each serving cell (i.e., for each of the serving cells). Furthermore, based on this information, UE 102 may identify the position of the bit value for each serving cell (i.e., for each of the serving cells). For example, the position of the bit value may be indicated based on information indicating the index of the serving cell. Furthermore, the position of the bit value may be indicated based on information indicating the starting position (e.g., within the number of bits) of the bit value (e.g., the 14-bit value) applicable to a serving cell with an index (e.g., a serving cell with an index configured using the serving cell index).

[0144] Additionally or alternatively, gNB 160 may configure fourth information related to the interruption transmission indication for the uplink by using an RRC message. That is, gNB 160 may separately configure third information (e.g., first information for the interruption transmission indication for the downlink) and fourth information (e.g., second information for the interruption transmission indication for the uplink). For example, gNB 160 may transmit fourth information for configuring UE 102 to monitor the interruption transmission indication for the uplink by using an RRC message (e.g., a PDCCH for DCI format 2_Y (e.g., DCI format 2_1 and / or DCI format 2_X with a CRC scrambled by the first RNTI)).

[0145] For example, the fourth information may include information for configuring the value of the first RNTI (e.g., the value of the first RNTI for the uplink interruption transmission indication (e.g., indicating preemption)). Additionally or alternatively, the fourth information may include information for configuring the time and / or frequency resources for the uplink interruption transmission indication. Here, the time and / or frequency resources for the uplink interruption transmission indication may correspond to PRBs and / or symbols for transmission and / or no transmission (e.g., in the uplink) (e.g., as described in detail above). Additionally or alternatively, the time and / or frequency resources for the uplink interruption transmission indication may correspond to the indication granularity of the time and / or frequency resources (e.g., the granularity of the time and / or frequency resources indicated by the uplink interruption transmission indication). Additionally or alternatively, the second information may include information for configuring the total length of the DCI payload included in DCI format 2_Y.

[0146] Additionally or alternatively, the fourth information may include information indicating the position of a bit value (e.g., a 14-bit value) within the DCI payload (e.g., within the DCI payload, included in DCI format 2_Y). Here, this information may be used to indicate the position of the bit value for each serving cell. That is, gNB 106 may use this information to indicate the position of the bit value for each serving cell (i.e., for each of the serving cells). Furthermore, based on this information, UE 102 may identify the position of the bit value for each serving cell (i.e., for each of the serving cells). For example, the position of the bit value may be indicated based on information indicating the index of the serving cell. Furthermore, the position of the bit value may be indicated based on information indicating the starting position (e.g., within the number of bits) of the bit value (e.g., a 14-bit value) applicable to a serving cell having an index (e.g., an index configured using the serving cell index).

[0147] Additionally or alternatively, this information (i.e., information indicating the position of a bit value (e.g., a 14-bit value) within a DCI payload (e.g., included in DCI format 2_Y)) can be used to indicate the position of the bit value for each BWP (e.g., a UL BWP). That is, the gNB 106 can use this information to indicate the position of the bit value for each BWP (e.g., a UL BWP) (i.e., for each of the UL BWPs). Furthermore, based on this information, the UE 102 can identify the position of the bit value for each BWP (e.g., a UL BWP) (i.e., for each of the UL BWPs). For example, the position of the bit value can be indicated based on information indicating the index of the BWP (e.g., the index of the UL BWP). Furthermore, the position of the bit value can be indicated based on information indicating the starting position (e.g., in the number of bits) of the bit value (e.g., the 14-bit value) applicable to an indexed UL BWP (e.g., an index configured using the index of the UL BWP).

[0148] Here, the third information (e.g., and / or information included in the third information) may be configured for each serving cell. That is, the third information (e.g., and / or information included in the third information) may be configured for each serving cell (e.g., each of the primary cell, the primary and secondary cells, and / or the secondary cells). Additionally or alternatively, the fourth information (e.g., information included in the fourth information) may be configured for each serving cell. That is, the fourth information (e.g., information included in the fourth information) may be configured for each serving cell (e.g., each of the primary cell, the primary and secondary cells, and / or the secondary cells).

[0149] Additionally or alternatively, the fourth information (e.g., information included in the fourth information) may be configured for each BWP (e.g., for each UL BWP). That is, the fourth information (e.g., information included in the fourth information) may be configured for each BWP in the BWP (e.g., each UL BWP in the UL BWP).

[0150] Additionally or alternatively, the downlink interrupt transmission indication may apply to reception on the PDSCH (e.g., reception of only the PDSCH). That is, for reception on the PDSCH, the UE 102 may assume that there are no transmissions intended for the UE (e.g., on the PDSCH). That is, for reception on the PDSCH, if the UE 102 detects a downlink interrupt transmission indication for the serving cell, the UE 102 may assume (e.g., always assume) that there are no transmissions to the UE 102 (e.g., on the PDSCH) in the PRBs and / or symbols indicated by the downlink interrupt transmission indication (as described in detail above).

[0151] Additionally or alternatively, a downlink interrupted transmission indication may not apply to reception of SS / PBCH blocks. That is, for reception of SS / PBCH blocks, UE 102 may not assume that there are no transmissions intended for the UE (e.g., of the SS / PBCH blocks). That is, for reception of SS / PBCH blocks, even if UE 102 detects a downlink interrupted transmission indication (e.g., even if the interrupted transmission indication indicates a PRB and / or symbol), UE 102 may not assume that there are no transmissions to the UE (e.g., of the SS / PRB blocks) in the PRBs and / or symbols. That is, (e.g., regardless of whether a downlink interrupted transmission indication is detected), UE 102 may always assume that there are transmissions to the UE (e.g., of the SS / PBCH blocks) in the PRBs and / or symbols.

[0152] As described above, the UL signal (e.g., UL signal transmission) may include at least PRACH transmission (e.g., Msg 1 transmission associated with CBRA and / or Msg 1 transmission associated with CFRA), PUSCH transmission (e.g., the first PUSCH transmission, the PUSCH transmission associated with CBRA, and / or the PUSCH transmission associated with CFRA), PUCCH transmission, and / or SRS transmission. Here, as described above, the first PUSCH transmission is different from the PUSCH transmission associated with CBRA and the PUSCH transmission associated with CFRA.

[0153] Additionally or alternatively, the uplink interruption transmission indication may apply to PUSCH transmission (e.g., only PUSCH transmission). That is, based on the uplink interruption transmission indication, the UE 102 may not be allowed to perform PUSCH transmission (as described in detail above). That is, based on the uplink interruption transmission indication, the UE 102 may cancel PUSCH transmission (e.g., stop performing PUSCH transmission) (as described in detail above). That is, if the UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), the UE 102 may not be allowed to perform PUSCH transmission in the PRB and / or symbol indicated by the uplink interruption transmission indication (as described in detail above). In addition, if the UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), the UE 102 may cancel PUSCH transmission in the PRB and / or symbol indicated by the uplink interruption transmission indication (as described in detail above).

[0154] Here, the uplink transmission interruption indication may apply to the first PUSCH transmission (e.g., only the first PUSCH transmission). Additionally or alternatively, the uplink transmission interruption indication may apply to the first PUSCH transmission and the PUSCH transmission associated with CBRA (e.g., only the first PUSCH transmission). That is, the uplink transmission interruption indication may not apply to the PUSCH transmission associated with CFRA. In addition, the uplink transmission interruption indication may not apply to the PUSCH transmission associated with CBRA and / or the PUSCH transmission associated with CFRA.

[0155] That is, based on the uplink interruption transmission indication, the UE 102 may not be allowed to perform the first PUSCH transmission and / or the PUSCH transmission associated with the CBRA (as described in detail above). That is, based on the uplink interruption transmission indication, the UE 102 may cancel the first PUSCH transmission and / or the PUSCH transmission associated with the CBRA (e.g., stop performing the first PUSCH transmission and / or the PUSCH transmission associated with the CBRA) (as described in detail above). That is, if the UE 102 detects the uplink interruption transmission indication (e.g., for the serving cell and / or UL BWP), the UE 102 may not be allowed to perform the first PUSCH transmission (and / or the PUSCH transmission associated with the CBRA) (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication. In addition, in the event that UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may cancel the first PUSCH transmission (and / or PUSCH transmission associated with the CBRA) in the PRB and / or symbol indicated by the uplink interruption transmission indication (as described in detail above).

[0156] Additionally or alternatively, the UE 102 may be allowed (e.g., always allowed) to perform a PUSCH transmission associated with CFRA. That is, the UE 102 may not cancel (e.g., never cancel) a PUSCH transmission associated with CFRA. That is, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may be allowed (e.g., always allowed) to perform a PUSCH transmission associated with CFRA (e.g., the uplink interruption transmission indication may not apply to the PUSCH transmission associated with CFRA). Additionally, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may not cancel (e.g., never cancel) a PUSCH transmission associated with CFRA (e.g., the uplink interruption transmission indication may not apply to the PUSCH transmission associated with CFRA). For example, the UE 102 may be allowed to perform a PUSCH transmission associated with CFRA (e.g., in a PRB and / or symbol) (e.g., regardless of whether the uplink interruption transmission indication is detected). Additionally, (eg, regardless of whether an uplink discontinued transmission indication is detected) the UE 102 may not cancel PUSCH transmissions associated with the CFRA (eg, in PRBs and / or symbols).

[0157] Additionally or alternatively, the UE 102 may be allowed (e.g., always allowed) to perform PUSCH transmission associated with CFRA and / or PUSCH transmission associated with CBRA. That is, the UE 102 may not cancel (e.g., never cancel) the PUSCH transmission associated with CFRA and / or the PUSCH transmission associated with CBRA. That is, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may be allowed (e.g., always allowed) to perform PUSCH transmission associated with CFRA and / or PUSCH transmission associated with CBRA (i.e., the uplink interruption transmission indication may not apply to the PUSCH transmission associated with CFRA and / or the PUSCH transmission associated with CBRA). In addition, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may not cancel (e.g., never cancel) a PUSCH transmission associated with CFRA and / or a PUSCH transmission associated with CBRA (i.e., the uplink interruption transmission indication may not apply to the PUSCH transmission associated with CFRA and / or the PUSCH transmission associated with CBRA). For example, the UE 102 may be allowed to perform a PUSCH transmission associated with CFRA and / or a PUSCH transmission associated with CBRA (e.g., in PRBs and / or symbols) (e.g., regardless of whether the uplink interruption transmission indication is detected). In addition, the UE 102 may not cancel a PUSCH transmission associated with CFRA and / or a PUSCH transmission associated with CBRA (e.g., in PRBs and / or symbols) (e.g., regardless of whether the uplink interruption transmission indication is detected).

[0158] Additionally or alternatively, the uplink interruption transmission indication may apply to PRACH transmission. That is, based on the uplink interruption transmission indication, UE 102 may not be allowed to perform PRACH transmission (as described in detail above). That is, based on the uplink interruption transmission indication, UE 102 may cancel PRACH transmission (e.g., stop performing PRACH transmission) (as described in detail above). That is, if UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may not be allowed to perform PRACH transmission in the PRB and / or symbol indicated by the uplink interruption transmission indication (as described in detail above). In addition, if UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may cancel PRACH transmission in the PRB and / or symbol indicated by the uplink interruption transmission indication (as described in detail above).

[0159] Additionally or alternatively, the uplink interruption transmission indication may not apply to PRACH transmission. That is, UE 102 may be allowed (e.g., always allowed) to perform PRACH transmission. That is, UE 102 may not cancel (e.g., never cancel) PRACH transmission. That is, even if UE 102 detects an uplink interruption transmission indication, UE 102 may be allowed (e.g., always allowed) to perform PRACH transmission (i.e., the uplink interruption transmission indication may not apply to PRACH transmission). In addition, even if UE 102 detects an uplink interruption transmission indication, UE 102 may not cancel (e.g., never cancel) PRACH transmission (i.e., the uplink interruption transmission indication may not apply to PRACH transmission). For example, UE 102 may be allowed to perform PRACH transmission (e.g., in PRBs and / or symbols) (e.g., regardless of whether an uplink interruption transmission indication is detected). Additionally, (e.g., regardless of whether an uplink discontinued transmission indication is detected) UE 102 may not cancel PRACH transmissions (e.g., in PRBs and / or symbols).

[0160] Additionally or alternatively, the uplink discontinuation transmission indication may be applicable to PRACH transmission associated with CBRA. That is, the uplink discontinuation transmission indication may not be applicable to PRACH transmission associated with CFRA.

[0161] That is, based on the uplink interruption transmission indication, the UE 102 may not be allowed to perform PRACH transmission associated with the CBRA (as described in detail above). That is, based on the uplink interruption transmission indication, the UE 102 may cancel the PRACH transmission associated with the CBRA (e.g., stop performing the PRACH transmission associated with the CBRA) (as described in detail above). That is, if the UE 102 detects an uplink interruption transmission indication (e.g., for the serving cell and / or UL BWP), the UE 102 may not be allowed to perform the PRACH transmission associated with the CBRA (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication. In addition, if the UE 102 detects an uplink interruption transmission indication (e.g., for the serving cell and / or UL BWP), the UE 102 may cancel the PRACH transmission associated with the CBRA (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication.

[0162] Additionally or alternatively, the UE 102 may be allowed (e.g., always allowed) to perform a PRACH transmission associated with CFRA. That is, the UE 102 may not cancel (e.g., never cancel) a PRACH transmission associated with CFRA. That is, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may be allowed (e.g., always allowed) to perform a PRACH transmission associated with CFRA (e.g., the uplink interruption transmission indication may not apply to the PRACH transmission associated with CFRA). Furthermore, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may not cancel (e.g., never cancel) a PRACH transmission associated with CFRA (e.g., the uplink interruption transmission indication may not apply to the PRACH transmission associated with CFRA). For example, the UE 102 may be allowed to perform a PRACH transmission associated with CFRA (e.g., in a PRB and / or symbol) (e.g., regardless of whether the uplink interruption transmission indication is detected). Additionally, (eg, regardless of whether an uplink discontinued transmission indication is detected) the UE 102 may not cancel PRACH transmissions (eg, in PRBs and / or symbols) associated with the CFRA.

[0163] Additionally or alternatively, the uplink discontinuation transmission indication may be applicable to UL transmission associated with CBRA. That is, the uplink discontinuation transmission indication may not be applicable to UL transmission associated with CFRA.

[0164] That is, based on the uplink interruption transmission indication, the UE 102 may not be allowed to perform UL transmission associated with the CBRA (as described in detail above). That is, based on the uplink interruption transmission indication, the UE 102 may cancel the UL transmission associated with the CBRA (e.g., stop performing the UL transmission associated with the CBRA) (as described in detail above). That is, if the UE 102 detects an uplink interruption transmission indication (e.g., for the serving cell and / or UL BWP), the UE 102 may not be allowed to perform UL transmission associated with the CBRA (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication. In addition, if the UE 102 detects an uplink interruption transmission indication (e.g., for the serving cell and / or UL BWP), the UE 102 may cancel the UL transmission associated with the CBRA (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication.

[0165] Additionally or alternatively, the UE 102 may be allowed (e.g., always allowed) to perform UL transmissions associated with CFRA. That is, the UE 102 may not cancel (e.g., never cancel) the UL transmissions associated with CFRA. That is, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may be allowed (e.g., always allowed) to perform UL transmissions associated with CFRA (i.e., the uplink interruption transmission indication may not apply to the UL transmissions associated with CFRA). Furthermore, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may not cancel (e.g., never cancel) the UL transmissions associated with CFRA (i.e., the uplink interruption transmission indication may not apply to the UL transmissions associated with CFRA). For example, the UE 102 may be allowed to perform UL transmissions associated with CFRA (e.g., in PRBs and / or symbols) (e.g., regardless of whether the uplink interruption transmission indication is detected). Additionally, (eg, regardless of whether an uplink discontinued transmission indication is detected) UE 102 may not cancel UL transmissions associated with CFRA (eg, in PRBs and / or symbols).

[0166] Additionally or alternatively, the uplink interruption transmission indication may apply to PUCCH transmission. That is, based on the uplink interruption transmission indication, UE 102 may not be allowed to perform PUCCH transmission (as described in detail above). That is, based on the uplink interruption transmission indication, UE 102 may cancel PUCCH transmission (as described in detail above). That is, if UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may not be allowed to perform PUCCH transmission (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication. In addition, if UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may cancel PUCCH transmission (as described in detail above) in the PRB and / or symbol indicated by the uplink interruption transmission indication.

[0167] Additionally or alternatively, the uplink interruption transmission indication may not apply to PUCCH transmission. That is, the UE 102 may be allowed (e.g., always allowed) to perform PUCCH transmission. That is, the UE 102 may not cancel (e.g., never cancel) PUCCH transmission. That is, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may be allowed (e.g., always allowed) to perform PUCCH transmission (i.e., the uplink interruption transmission indication may not apply to PUCCH transmission). In addition, even if the UE 102 detects an uplink interruption transmission indication, the UE 102 may not cancel (e.g., never cancel) PUCCH transmission (i.e., the uplink interruption transmission indication may not apply to PUCCH transmission). For example, the UE 102 may be allowed to perform PUCCH transmission (e.g., in PRBs and / or symbols) (e.g., regardless of whether the uplink interruption transmission indication is detected). Additionally, (eg, regardless of whether an uplink interrupted transmission indication is detected) UE 102 may not cancel PUCCH transmissions (eg, in PRBs and / or symbols).

[0168] Additionally or alternatively, the uplink interruption transmission indication may apply to SRS transmission. That is, based on the uplink interruption transmission indication, UE 102 may not be allowed to perform SRS transmission (as described in detail above). That is, based on the uplink interruption transmission indication, UE 102 may cancel SRS transmission (as described in detail above). That is, if UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may not be allowed to perform SRS transmission (as described in detail above) in the PRBs and / or symbols indicated by the uplink interruption transmission indication. In addition, if UE 102 detects an uplink interruption transmission indication (e.g., for a serving cell and / or UL BWP), UE 102 may cancel SRS transmission (as described in detail above) in the PRBs and / or symbols indicated by the uplink interruption transmission indication.

[0169] Additionally or alternatively, the uplink transmission interruption indication may not apply to SRS transmission. That is, UE 102 may be allowed (e.g., always allowed) to perform SRS transmission. That is, UE 102 may not cancel (e.g., never cancel) SRS transmission. That is, even if UE 102 detects an uplink transmission interruption indication, UE 102 may be allowed (e.g., always allowed) to perform SRS transmission (i.e., the uplink transmission interruption indication may not apply to SRS transmission). In addition, even if UE 102 detects an uplink transmission interruption indication, UE 102 may not cancel (e.g., never cancel) SRS transmission (i.e., the uplink transmission interruption indication may not apply to SRS transmission). For example, UE 102 may be allowed to perform SRS transmission (e.g., in PRBs and / or symbols) (e.g., regardless of whether an uplink transmission interruption indication is detected). Additionally, (eg, regardless of whether an uplink discontinued transmission indication is detected) UE 102 may not cancel SRS transmission (eg, in PRBs and / or symbols).

[0170] Figure 6 Various components that may be used in a UE 702 are shown. Figure 6 The UE 702 described may be configured in accordance with Figure 1 10. 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). A memory 705 (which may include read-only memory (ROM), 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 non-volatile random access memory (NVRAM). 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 methods described herein.

[0171] The UE 702 may also include a housing that houses one or more transmitters 758 and one or more receivers 720 to allow for 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.

[0172] 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 not shown in FIG. Figure 6 7. The UE 702 is shown as a bus system 711. The UE 702 may also include a digital signal processor (DSP) 713 for processing signals. The UE 702 may also include a communication interface 715 that provides user access to the functions of the UE 702. Figure 6 The UE 702 is shown as a functional block diagram rather than a listing of specific components.

[0173] Figure 7 Various components that may be used in gNB 860 are shown. Figure 8 The gNB 860 described may be configured in accordance with Figure 1 The gNB 860 is implemented as described above using 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). Memory 805 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device capable of storing information) provides instructions 807a and data 809a to the processor 803. A portion of the memory 805 may also include 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 methods described herein.

[0174] The gNB 860 may also include a housing that houses one or more transmitters 817 and one or more receivers 878 to allow for 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 transceivers 876.

[0175] The various components of the gNB 860 are coupled together via a 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 not referred to in the following sections. Figure 7 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.

[0176] Figure 89 is a block diagram illustrating one embodiment of a UE 902 in which one or more of the systems and / or methods described herein may be implemented. 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 Shown Figure 9 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0177] Figure 9 is a block diagram illustrating one embodiment 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 Shown Figure 10 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0178] Figure 10 is a block diagram illustrating a specific implementation of gNB 1160. gNB 1160 may be combined with Figure 1 1. An example of a gNB 160 is depicted. 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.

[0179] The higher layer processor 1123 manages the behavior of the physical layer (DL transmitter and UL receiver) and provides higher layer parameters to the physical layer. The higher layer processor 1123 can obtain transport blocks from the physical layer. The higher layer processor 1123 can send and receive higher layer messages, such as RRC messages and MAC messages, to / from the higher layer of the UE. The higher layer processor 1123 can provide the transport blocks to the PDSCH transmitter and provide transmission parameters related to the transport blocks to the PDCCH transmitter.

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

[0181] Figure 11 1 is a block diagram illustrating a specific implementation of UE 1202. UE 1202 may be a combination of Figure 1 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.

[0182] The higher-layer processor 1223 manages the behavior of the physical layer (DL transmitter and UL receiver) and provides higher-layer parameters to the physical layer. The higher-layer processor 1223 can obtain transport blocks from the physical layer. The higher-layer processor 1223 can send and receive higher-layer messages, such as RRC messages and MAC messages, to and from the higher layers of the UE. The higher-layer processor 1223 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0183] 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 DCI to the higher layer processor 1223. The PDSCH receiver 1247 may provide the received transport block to the higher layer processor 1223.

[0184] 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 the 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 the methods described herein.

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

[0186] 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 processor-readable medium. By way of example, and not limitation, a computer-readable medium or 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.

[0187] As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Optical disks, where disks typically reproduce data magnetically, optical disks use lasers to reproduce data optically.

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

[0189] 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 one another 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.

[0190] It is to be understood that the claims are not limited to the precise configuration and components shown above, and that 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.

[0191] The program running on the gNB 160 or UE 102 according to the systems and methods described herein controls the CPU, etc., to implement the functions according to the systems and methods (a program that causes the computer to operate). Information processed by these devices is then temporarily stored in RAM while being processed. This information is then stored in various ROMs or HDDs and read by the CPU for modification or writing whenever necessary. Possible recording media on which the program is stored include semiconductors (e.g., ROMs, nonvolatile memory cards, etc.), optical storage media (e.g., DVDs, MOs, MDs, CDs, BDs, etc.), and magnetic storage media (e.g., magnetic tapes, floppy disks, etc.). In some cases, the functions according to the systems and methods described herein are implemented by executing the loaded program. Alternatively, the functions according to the systems and methods are implemented based on instructions from the program in conjunction with an operating system or other application programs.

[0192] Furthermore, if the program is commercially available, it can be distributed stored on a portable recording medium, or it can be transferred to a server computer connected via a network such as the Internet. In this case, the storage device in the server computer is also included. Furthermore, some or all of the gNB 160 and UE 102 according to the systems and methods described herein can be implemented as LSIs, which are typical integrated circuits. Each functional block of the gNB 160 and UE 102 can be individually built into a chip, and some or all functional blocks can be integrated into a chip. Furthermore, integrated circuit technology is not limited to LSIs, and integrated circuits for functional blocks can be implemented using dedicated circuits or general-purpose processors. Furthermore, if integrated circuit technology that replaces LSIs emerges as semiconductor technology continues to advance, integrated circuits using such technology can also be used.

[0193] 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 circuit (typically an integrated circuit or multiple integrated circuits). The circuit designed to perform the function 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 every kind of circuit described herein can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of the integrated circuit replacing current integrated circuit occurs due to the progress of semiconductor technology, it is also possible to use the integrated circuit produced by this technology.

[0194] <Cross Reference>

[0195] This nonprovisional patent application claims priority under 35 U.S.C. §119 to provisional patent application 62 / 910,152, filed on October 3, 2019, the entire contents of which are hereby incorporated by reference.

Claims

1. A user equipment (UE), comprising: a receiving circuit configured to receive a radio resource control (RRC) message, the RRC message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format, the DCI format including an interrupt transmission indication for an uplink, and A processing circuit configured to cancel, in a contention-based random access procedure, a Msg3 physical uplink shared channel PUSCH transmission in a physical resource block and / or symbol indicated by the transmission interruption indication for the uplink, wherein In the contention-based random access procedure, the interruption transmission indication for the uplink is applicable to a specific type of uplink transmission, and The specific type of uplink transmission includes the Msg3 PUSCH transmission, but does not include the Msg1 physical random access channel PRACH transmission, and Regardless of whether the Msg3 PUSCH transmission is an initial transmission or a retransmission of message 3, the Msg3 PUSCH transmission will be canceled in the physical resource block and / or symbol; The initial transmission is scheduled by a random access response grant; and The retransmission is scheduled by a physical downlink control channel PDCCH, and a cyclic redundancy check (CRC) of the channel is scrambled by a first radio network temporary identifier (RNTI), where the first RNTI is a temporary C-RNTI.

2. The UE according to claim 1, wherein The specific type of uplink transmission also includes a sounding reference signal (SRS) transmission, and SRS transmission in the physical resource blocks and / or symbols indicated by the uplink transmission suspension indication is cancelled.

3. A communication method for a user equipment (UE), comprising: receiving a radio resource control (RRC) message including information for configuring the UE to monitor a physical downlink control channel (PDCCH) for a downlink control information (DCI) format including an interrupt transmission indication for an uplink, and In a contention-based random access procedure, canceling the Msg3 physical uplink shared channel PUSCH transmission in the physical resource blocks and / or symbols indicated by the transmission interruption indication for the uplink, wherein In the contention-based random access procedure, the interruption transmission indication for the uplink is applicable to a specific type of uplink transmission, and The specific type of uplink transmission includes the Msg3 PUSCH transmission, but does not include the Msg1 physical random access channel PRACH transmission, and Regardless of whether the Msg3 PUSCH transmission is an initial transmission or a retransmission of message 3, the Msg3 PUSCH transmission will be canceled in the physical resource block and / or symbol; The initial transmission is scheduled by a random access response grant; and The retransmission is scheduled by a physical downlink control channel PDCCH, and a cyclic redundancy check (CRC) of the channel is scrambled by a first radio network temporary identifier (RNTI), where the first RNTI is a temporary C-RNTI.

Images