User Equipment, Base Station, and Method for Transmission Configuration Indication for PDSCH

Abstract

The UE includes a high-layer circuit configured to receive information including more than one Transmission Configuration Indication (TCI) state. The UE further includes a Medium Access Control (MAC) circuit configured to receive a first MAC Control Element (CE) and a second MAC CE. The UE further includes a receiving circuit configured to receive a first Downlink Control Information (DCI) on a Physical Downlink Control Channel (PDCCH) and a second DCI on the PDCCH. The first MAC CE selects one or more TCI states from the more than one TCI states and maps the selected one or more TCI states to code points of a TCI field in the second DCI. The second MAC CE selects one or more TCI states from the more than one TCI states and maps the selected one or more TCI states to the code points of the TCI field in the second DCI.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to new signaling, procedures, user equipment, and base stations for configuring user equipment (UE), base stations, and methods for uplink control information on a micro-slot physical uplink shared channel (PUSCH). 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 services, expanded coverage areas, and enhanced functionality. A wireless communication system can provide communication for multiple wireless communication devices, and each wireless communication device can be served by a base station. A base station can be a device that communicates with wireless communication devices.

[0003] With the development of wireless communication devices, there has been a continuous search for ways to improve communication capacity, speed, flexibility, and / or efficiency. However, improving communication capacity, speed, flexibility, and / or efficiency may pose certain problems.

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

[0005] In one example, a user equipment includes: a high-layer circuit configured to receive information including more than one transmission configuration indication (TCI) state; a media access control (MAC) circuit configured to receive a first MAC control element (CE) and a second MAC CE; and a receiving circuit configured to receive a first downlink control information (DCI) on a physical downlink control channel (PDCCH) and a second DCI on the PDCCH, wherein the first MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to code points of a TCI field in the second DCI, and the second MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to the code points of the TCI field in the second DCI.

[0006] In one example, a base station device includes: a high-layer circuit configured to transmit information including more than one transmission configuration indication (TCI) state; a media access control (MAC) circuit configured to transmit a first MAC control element (CE) and a second MAC CE; and a transmission circuit configured to transmit first downlink control information (DCI) on a physical downlink control channel (PDCCH) and second DCI on the PDCCH, wherein the first MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to code points of a TCI field in the second DCI, and the second MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to the code points of the TCI field in the second DCI.

[0007] In one example, a communication method of a user equipment includes: receiving information including more than one transmission configuration indication (TCI) state; receiving a first MAC control element (CE) and a second MAC CE; and receiving first downlink control information (DCI) on a physical downlink control channel (PDCCH) and second DCI on the PDCCH, wherein the first MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to code points of a TCI field in the second DCI, and the second MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to the code points of the TCI field in the second DCI.

[0008] In one example, a communication method of a base station device includes: transmitting information including more than one transmission configuration indication (TCI) state; transmitting a first MAC control element (CE) and a second MAC CE; and transmitting first downlink control information (DCI) on a physical downlink control channel (PDCCH) and second DCI on the PDCCH, wherein the first MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to code points of a TCI field in the second DCI, and the second MAC CE selects one or more TCI states from the more than one TCI state and maps the selected one or more TCI states to the code points of the TCI field in the second DCI. Description of the Drawings

[0009] Figure 1 Figure 1 ​​is a block diagram showing a specific implementation of one or more base station devices (gNBs) and one or more user equipments (UEs) in which a system and method for signaling can be implemented.

[0010] Figure 2 Figure 2 Shows examples of multiple parameters.

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

[0012] Figure 4 Figure 4 Shows examples of resource regions.

[0013] Figure 5 Figure 5 Shows an example of TCI state configuration.

[0014] Figure 6 Figure 6 is a diagram showing the TCI state and the TCI fields in DCI format 1_1 and DCI format 1_2.

[0015] Figure 7 Figure 7 Shows various components that can be utilized in a UE.

[0016] Figure 8 Figure 8 Shows various components that can be utilized in a gNB.

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

[0018] Figure 10 Figure 10 is a block diagram showing a specific implementation of a gNB in which one or more of the systems and / or methods described herein can be implemented.

[0019] Figure 11 Figure 11 is a block diagram showing a specific implementation of a gNB.

[0020] Figure 12 Figure 12 is a block diagram showing a specific implementation of a UE.

[0021] Figure 13 Figure 13 is a flowchart showing a communication method performed by a UE.

[0022] ​​​​​​​​​​​​​​​​​​​​​​​​​Figure 14 Figure 14 is a flowchart showing a communication method performed by a gNB. Detailed implementation

[0023] The UE includes a receiving circuit configured to receive first information, second information, first downlink control information (DCI) on a physical downlink control channel (PDCCH), and second DCI on the PDCCH. The UE further includes a transmitting circuit configured to transmit a channel state information (CSI) report on a physical uplink shared channel (PUSCH). The CSI request field in the first DCI is configured by the first information. The CSI request field in the second DCI is configured by the second information. The first information includes a trigger status for an aperiodic CSI report for the first DCI. The CSI request field in the second DCI is configured by the second information.

[0024] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a radio resource control (RRC) message, the RRC message including information for configuring a priority indication present in a downlink control information (DCI) format. The DCI format is used to schedule a physical downlink shared channel (PDSCH). The priority indication is used to indicate a priority for hybrid automatic repeat request - acknowledgement (HARQ-ACK) transmission for the PDSCH. The UE further includes a transmitting circuit configured to perform HARQ-ACK transmission for the PDSCH based on the priority. The information is configured for each control resource set (CORESET), except for the CORESET having an index of "0".

[0025] The present invention also describes a base station device. The base station device includes a transmitting circuit configured to transmit an RRC message, the RRC message including information for configuring a priority indication present in a DCI format. The DCI format is used to schedule the PDSCH. The priority indication is used to indicate a priority for HARQ-ACK transmission for the PDSCH. The base station device further includes a receiving circuit configured to perform HARQ-ACK reception for the PDSCH based on the priority. The information is configured for each CORESET, except for the CORESET having an index of "0".

[0026] ​The present invention also describes a communication method for a UE. The communication method includes receiving an RRC message, the RRC message including information for configuring a priority indication present in a DCI format. The DCI format is used for scheduling a PDSCH. The priority indication is used to indicate the priority for HARQ-ACK transmission for the PDSCH. The communication method further includes performing HARQ-ACK transmission for the PDSCH based on the priority. The information is configured for each CORESET, except for the CORESET with index "0".

[0027] The present invention also describes a communication method for a base station device. The communication method includes transmitting an RRC message, the RRC message including information for configuring a priority indication present in a DCI format. The DCI format is used for scheduling a PDSCH. The priority indication is used to indicate the priority for HARQ-ACK transmission for the PDSCH. The communication method further includes performing HARQ-ACK reception for the PDSCH based on the priority. The information is configured for each CORESET, except for the CORESET with index "0".

[0028] The 3rd Generation Partnership Project (also known as "3GPP") is a cooperation agreement aimed at formulating globally applicable technical specifications and technical reports for third-generation and fourth-generation wireless communication systems. 3GPP can formulate specifications for next-generation mobile networks, systems, and devices.

[0029] 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 meet future requirements. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0030] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, LTE-Advanced (LTE-A), 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.

[0031] A wireless communication device can be an electronic device that is used to transmit voice and / or data to a base station, which in turn can communicate with the device's network (e.g., the public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, the wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. 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 denote the more general term "wireless communication device". A UE may also more generally be referred to as a terminal device.

[0032] In 3GPP specifications, a base station is typically referred to as a Node B, evolved Node B (eNB), Home eNode B (HeNB), or some other similar term. Since 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 denote the more general term "base station". Additionally, the term "base station" may be used to denote an access point. An access point can be an electronic device that provides access to a network (e.g., a local area network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to denote a wireless communication device and / or a base station. An eNB may also more generally be referred to as a base station device.

[0033] It should be noted that, as used herein, a "cell" can be any such communication channel: which is designated by a standardization or regulatory body for use in International Mobile Telecommunications - Advanced (IMT - Advanced) and all or a subset thereof, such that it is 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 pointed out that, in the overall description of E - UTRA and E - UTRAN, as used herein, a "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 the system information that can be transmitted on the downlink resources.

[0034] The fifth-generation communication system, which is referred to as NR (New Radio) by 3GPP, is envisioned to use time / frequency / spatial resources to enable services such as eMBB (Enhanced Mobile Broadband) transmission, URLLC (Ultra-Reliable and Low-Latency Communication) transmission, and eMTC (Massive Machine-Type Communication) transmission. Also, in NR, transmission for different services can be specified (e.g., configured) for one or more bandwidth parts (BWPs) in a serving cell and / or for one or more serving cells. A user equipment (UE) can receive downlink signals and / or transmit uplink signals in the BWP(s) of one and / or more serving cells.

[0035] To enable services to effectively use time, frequency, and / or spatial resources, it would be useful to be able to effectively control downlink and / or uplink transmission. Accordingly, a process for effectively controlling downlink and / or uplink transmission should be designed. Thus, a detailed design of the process for downlink and / or uplink transmission may be beneficial.

[0036] Various examples of the systems and methods disclosed herein will now be described with reference to the drawings, where 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 specific implementations. Accordingly, the more detailed description of several specific implementations presented below of the drawings is not intended to limit the scope of the claimed subject matter, but merely to represent the systems and methods.

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

[0038] 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 use one or more uplink channels 121 to transmit information or data to gNB 160. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)), etc. For example, the one or more gNB 160 may also use one or more downlink channels 119 to transmit information or data to the one or more UE 102. Examples of downlink channels 119 include physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel) and / or physical control channels (PDCCH (Physical Downlink Control Channel)), etc.). Other kinds of channels and / or signals may be used.

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

[0040] Transceiver 118 may include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 may receive signals from gNB 160 using one or more antennas 122a-n. For example, receiver 120 may receive and down-convert the signals to generate one or more received signals 116. The one or more received signals 116 may be provided to demodulator 114. One or more transmitters 158 may transmit signals to gNB 160 using one or more physical antennas 122a-n. For example, one or more transmitters 158 may up-convert and transmit one or more modulated signals 156.

[0041] 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 signals. The decoder 108 may generate a decoded signal 110, which may include the UE decoded signal 106 (also referred to as the first UE decoded signal 106). For example, the first UE decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as the second UE decoded signal 110) may include overhead data and / or control data. For example, the second UE decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

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

[0043] The UE scheduling module 126 may perform downlink reception and uplink transmission. The one or more downlink receptions include the reception of data, the reception of downlink control information, and / or the reception of downlink reference signals. Additionally, the uplink transmission includes the transmission of data, the transmission of uplink control information, and / or the transmission of uplink reference signals.

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

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

[0046] 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 Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ - ACK is used to indicate an acknowledgement (ACK) or negative acknowledgement (NACK) of downlink data (e.g., transport block, Medium Access Control Protocol Data Unit (MAC PDU), and / or Downlink Shared Channel (DL - SCH)). The CSI is used to indicate the state of a downlink channel (e.g., a downlink signal). Additionally, the SR is used to request resources for uplink data (e.g., transport block, MAC PDU, and / or Uplink Shared Channel (UL - SCH)).

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

[0048] 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, a DCI format may define fields and map the fields to information bits (e.g., DCI bits).

[0049] For example, DCI format 1_0 for scheduling the Physical Downlink Shared Channel (PDSCH) in a cell may be defined as a DCI format for the downlink. Additionally, as described herein, one or more Radio Network Temporary Identifiers (e.g., Cell Radio Network Temporary Identifier (C - RNTI), Configured Scheduling RNTI (CS - RNTI), System Information RNTI (SI - RNTI), Random Access RNTI (RA - RNTI), and / or First RNTI) may be used to transmit DCI format 1_0. Moreover, 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.

[0050] 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., transmission power control) command for scheduling 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 indication (e.g., for PDSCH transmission and / or for PDSCH reception). Additionally or alternatively, the DCI included in DCI format 1_0 may be a priority indication (e.g., for HARQ-ACK transmission for PDSCH and / or for HARQ-ACK reception for PDSCH).

[0051] Here, the priority indication can be used to indicate the priority of PDSCH transmission and / or PDSCH reception (e.g., 2-bit information, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, in the case where UE 102 detects (e.g., decodes, receives) a DCI format including a priority indication for the downlink, UE 102 can identify that PDSCH transmission and / or PDSCH reception is prioritized (e.g., PDSCH transmission and / or PDSCH reception has a higher priority, highest priority, lower priority, and / or lowest priority).

[0052] Additionally or alternatively, the priority indication can be used to indicate the priority of HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH (e.g., 2-bit information, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, in the case where UE 102 detects a DCI format including a priority indication for the downlink, UE 102 can identify that HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH is prioritized (e.g., HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH has a higher priority, highest priority, lower priority, and / or lowest priority).

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

[0054] For example, the DCI included in DCI format 1_1 may be a BWP indicator (e.g., for the PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a frequency-domain resource allocation (e.g., for the PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a time-domain resource allocation (e.g., for the PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a modulation and coding scheme (e.g., for the 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 scheduling the PUCCH. Additionally or alternatively, the DCI included in DCI format 1_1 may be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., CSI report (e.g., 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 (e.g., for PDSCH transmission and / or for PDSCH reception). Additionally or alternatively, the DCI included in DCI format 1_1 may be a priority indication (e.g., for HARQ-ACK transmission of the PDSCH and / or for HARQ-ACK reception of the PDSCH).

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

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

[0057] Here, DCI format 1_X (and / or DCI format 1_X including a priority indication) may be used to indicate the priority of PDSCH transmission and / or PDSCH reception (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, in the case where UE 102 detects DCI format 1_X (and / or DCI format 1_X including a priority indication), UE 102 may identify that PDSCH transmission and / or PDSCH reception is prioritized (e.g., PDSCH transmission and / or PDSCH reception has a higher priority, highest priority, lower priority, and / or lowest priority).

[0058] Additionally or alternatively, DCI format 1_X (and / or DCI format 1_X including a priority indication, and / or DCI format 1_X having a CRC scrambled by a first RNTI, and / or DCI format 1_X having a CRC scrambled by a first RNTI including a priority indication) may be used to indicate the priority for HARQ-ACK transmission for the PDSCH and / or for HARQ-ACK reception for the PDSCH (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, in the case where the UE 102 detects DCI format 1_X (and / or DCI format 1_X including a priority indication, and / or DCI format 1_X having a CRC scrambled by a first RNTI, and / or DCI format 1_X having a CRC scrambled by a first RNTI including a priority indication), the UE 102 may identify that the HARQ-ACK transmission for the PDSCH and / or the HARQ-ACK reception for the PDSCH is prioritized (e.g., the HARQ-ACK transmission for the PDSCH and / or the HARQ-ACK reception for the PDSCH has a higher priority, highest priority, lower priority, and / or lowest priority).

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

[0060] For example, the DCI included in DCI format 0_0 may be a frequency domain resource allocation (e.g., for the PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a time domain resource allocation (e.g., for the PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a modulation and coding scheme (e.g., for the 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 the scheduled PUSCH. Additionally or alternatively, the DCI included in DCI format 0_0 may be a priority indication (e.g., for PUSCH transmission and / or for PUSCH reception).

[0061] Here, a priority indication can be used to indicate the priority of PUSCH transmission and / or PUSCH reception (e.g., 2-bit information, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, in the case where UE 102 detects a DCI format including a priority indication for the uplink, UE 102 can identify that the PUSCH transmission and / or PUSCH reception is prioritized (e.g., the PUSCH transmission and / or PUSCH reception has a higher priority, highest priority, lower priority, and / or lowest priority).

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

[0063] For example, the DCI included in DCI format 0_1 can be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 can be a frequency-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 can be a time-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 can be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_1 can be a TPC command for the scheduled PUSCH. Additionally or alternatively, the DCI included in DCI format 0_1 can be a CSI request for requesting a CSI report. Additionally or alternatively, as described below, the DCI included in DCI format 0_1 can be information indicating an index of a configured grant configuration. Additionally or alternatively, the DCI included in DCI format 0_0 can be a priority indication (e.g., for PUSCH transmission and / or for PUSCH reception).

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

[0065] For example, the DCI included in DCI format 0_Y may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a frequency-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a time-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_Y may be a TPC command for scheduling PUSCH. Additionally or alternatively, the DCI included in DCI format 0_Y may be a CSI request for requesting a CSI report. Additionally or alternatively, as described below, the DCI included in DCI format 0_Y may be information indicating an index of a configuration for configured grant. Additionally or alternatively, the DCI included in DCI format 0_Y may be a priority indication (e.g., for PUSCH transmission and / or for PUSCH reception).

[0066] Here, DCI format 0_Y (and / or DCI format 0_Y including a priority indication, and / or DCI format 0_Y having a CRC scrambled by a first RNTI, and / or DCI format 0_Y having a CRC scrambled by a first RNTI including a priority indication) may be used to indicate a priority for PUSCH transmission and / or for PUSCH reception (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, in the case where UE 102 detects DCI format 0_Y (and / or DCI format 0_Y including a priority indication, and / or DCI format 0_Y having a CRC scrambled by a first RNTI, and / or DCI format 0_Y having a CRC scrambled by a first RNTI including a priority indication), UE 102 may identify that PUSCH transmission and / or PUSCH reception is prioritized (e.g., PUSCH transmission and / or PUSCH reception has a higher priority, highest priority, lower priority, and / or lowest priority).

[0067] Additionally or alternatively, upon receiving DCI format 1_0, DCI format 1_1, and / or DCI format 1_X (e.g., based on detecting DCI format 1_0, DCI format 1_1, DCI format 1_X), UE 102 may perform PDSCH reception. Additionally or alternatively, upon receiving DCI format 0_0, DCI format 0_1, and / or DCI format 0_Y (e.g., based on detecting DCI format 0_0, DCI format 0_1, DCI format 0_Y), UE 102 may perform PUSCH transmission.

[0068] Here, as described above, the RNTI (e.g., Radio Network Temporary Identifier) assigned to UE 102 can be used for the 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 can transmit (e.g., by using an RRC message) information for configuring (e.g., allocating) the RNTI to UE 102.

[0069] For example, CRC (Cyclic Redundancy Check) parity bits generated based on DCI (also simply referred to as CRC) are appended to the DCI, and after the appending, the CRC parity bits are scrambled by the RNTI. UE 102 may attempt to decode (e.g., blind decode, monitor, detect) the DCI to which the CRC parity bits scrambled by the RNTI are appended. For example, UE 102 detects a DL control channel (e.g., PDCCH, DCI, DCI format) based on blind decoding. That is, UE 102 can use the CRC scrambled by the RNTI to decode the DL control channel. In other words, UE 102 can use the RNTI to monitor the DL control channel. For example, UE 102 can use the RNTI to detect a DCI format.

[0070] 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, and / or First RNTI.

[0071] For example, a C-RNTI can be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, a CS-RNTI can be a unique identifier for scheduling transmissions based on configured grants. Additionally or alternatively, an SI-RNTI can be used to identify system information (SI) (e.g., SI messages) mapped on the BCCH and dynamically carried on the DL-SCH. Additionally or alternatively, an SI-RNTI can be used for the broadcasting of SI. Additionally or alternatively, an 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 scheduling random access procedures (e.g., (re)transmission of Msg.3 (e.g., (re)transmission of Msg.3 PUSCH)).

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

[0073] Additionally or alternatively, a first RNTI can be an identifier for indicating the priority of PDSCH transmission and / or PDSCH reception (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, in the case where UE 102 detects a PDCCH with a CRC scrambled by the first RNTI, UE 102 can identify that the corresponding PDSCH is prioritized (e.g., the corresponding PDSCH transmission / reception has a higher priority, highest priority, lower priority, and / or lowest priority).

[0074] Additionally or alternatively, a first RNTI can be an identifier for indicating the priority of PDSCH HARQ-ACK transmission and / or PDSCH HARQ-ACK reception (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, in the case where UE 102 detects a PDCCH with a CRC scrambled by the first RNTI, UE 102 can identify that the HARQ-ACK of the corresponding PDSCH is prioritized (e.g., the HARQ-ACK transmission / reception of the corresponding PDSCH has a higher priority, highest priority, lower priority, and / or lowest priority).

[0075] Additionally or alternatively, the first RNTI may be an identifier for indicating the priority of PUSCH transmission and / or PUSCH reception (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, in the case where UE 102 detects a PDCCH with a CRC scrambled by the first RNTI, UE 102 may identify that the corresponding PUSCH is prioritized (e.g., the corresponding PUSCH transmission / reception has a higher priority, highest priority, lower priority, and / or lowest priority).

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

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

[0078] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast the MIB (master information block). Here, the system information may be divided into the MIB and a plurality of SIBs (system information blocks). For example, the MIB may be used to carry the minimum system information. Additionally or alternatively, the SIB may be used to carry system information messages.

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

[0080] In radio communication for the uplink, the UL RS can be used as an uplink physical signal. Additionally or alternatively, in radio communication for the downlink, the DL RS can 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 by the higher layer, but are used by the physical layer.

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

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

[0083] The UE operation module 124 can provide the information 148 to one or more receivers 120. For example, the UE operation module 124 can notify one or more receivers 120 when to receive a retransmission.

[0084] The UE operation module 124 can provide the information 138 to the demodulator 114. For example, the UE operation module 124 can notify the demodulator 114 of the modulation pattern expected for the transmission from the gNB 160.

[0085] The UE operation module 124 may provide information 136 to the decoder 108. For example, the UE operation module 124 may notify the decoder 108 of the encoding expected for transmissions from the gNB 160.

[0086] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include the 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.

[0087] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operation 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, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to the modulator 154.

[0088] The UE operation module 124 may provide information 144 to the modulator 154. For example, the UE operation module 124 may notify the modulator 154 of the modulation type (e.g., constellation mapping) for transmission to the gNB 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

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

[0090] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive paths and / or transmission 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.

[0091] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. 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 down-convert the signals to generate one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. One or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

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

[0093] Generally, the gNB operation module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operation 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.

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

[0095] The gNB operation module 182 may provide information 186 to the decoder 166. For example, the gNB operation module 182 may notify the decoder 166 of the coding expected for transmissions from one or more UEs 102.

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

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

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

[0099] The gNB operation module 182 may provide the information 192 to one or more transmitters 117. The information 192 may include instructions for one or more transmitters 117. For example, the gNB operation module 182 may indicate to one or more transmitters 117 when (when not) to transmit signals to one or more UEs 102. One or more transmitters 117 may up-convert one or more modulated signals 115 and transmit the one or more modulated signals to one or more UEs 102.

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

[0101] It should also be noted that one or more of the elements or their components 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 their components may be implemented as chips, circuits, or hardware components, 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 using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc., and / or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0102] Figure 2 An example of a plurality of parameters 201 is shown. AsFigure 2 As shown, multiple parameters 201 (e.g., multiple sub - carrier intervals) can be supported. For example, μ (e.g., sub - carrier spacing configuration) and cyclic prefix (e.g., μ and cyclic prefix of the carrier bandwidth part) can be configured by high - layer parameters (e.g., RRC messages) for downlink and / or uplink. Here, 15 kHz can be a reference parameter 201. For example, the RE of the reference parameter 201 can be defined to have a sub - carrier interval of 15 kHz in the frequency domain and a length of 2048Ts + CP (e.g., 160Ts or 144Ts) in the time domain, where Ts represents the base - band sampling time unit defined as 1 / (15000 * 2048) seconds.

[0103] Additionally or alternatively, the number of OFDM symbols per time slot can be determined based on u (e.g., sub - carrier spacing configuration). Here, for example, time - slot configuration 0 (e.g., the number of OFDM symbols 203 per time slot can be 14) and / or time - slot configuration (e.g., the number of OFDM symbols 203 per time slot can be 7) can be defined.

[0104] Figure 3 is a diagram showing an example of a resource grid 301 and resource blocks 391 (e.g., for downlink and / or uplink). Figure 3 The resource grid 301 and resource blocks 391 shown can be used in some specific implementations of the systems and methods disclosed herein.

[0105] In Figure 3 a sub - frame 369 can include symbols 387. Additionally or alternatively, a resource block 391 can include multiple resource elements (RE) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) can be adopted, which can also be referred to as CP - OFDM. A downlink radio frame can include multiple pairs of downlink resource blocks (RB) 391, and the downlink RB is also referred to as a physical resource block (PRB). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slot. A downlink RB pair can include two consecutive downlink RBs 391 in the time domain. Additionally or alternatively, a downlink RB 391 can include twelve sub - carriers 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 sub - carrier in the frequency domain and one OFDM symbol in the time domain is called 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.

[0106] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme may also be employed, which is also referred to as discrete Fourier transform spread OFDM (DFT-S-OFDM). The 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 referred to as a resource element (RE) 389, and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indices in the frequency domain and time domain, respectively.

[0107] Each element and subcarrier configuration u in the resource grid 301 (e.g., antenna port p) is referred to as a resource element 389, and is uniquely identified by an index pair (k, l), where k is the 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,μ . A physical resource block 391 is defined as consecutive subcarriers in the frequency domain. The physical resource block 391 is numbered from 0 to in the frequency domain. The physical resource block number n PRB in the frequency domain and the relationship between the resource element (k, l) are given by:

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

[0109] UE 102 can monitor a candidate set of PDCCHs in one or more control resource sets (e.g., CORESET) on the active DL bandwidth part (BWP) of each active serving cell according to the corresponding set of search spaces. Here, the term "monitor" may imply that UE 102 attempts to decode each PDCCH (e.g., the candidate set of PDCCHs) according to the monitored DCI format. Additionally, a candidate of PDCCH can be a candidate where the DL control channel may be mapped, allocated, and / or transmitted.

[0110] The candidate set of PDCCHs to be monitored by UE 102 can be defined according to a set of search spaces (e.g., also simply referred to as search space). UE 102 can monitor the candidate set of PDCCHs in the search space. The set of search spaces can include a common search space (CSS, UE common search space) and / or a user equipment-specific search space (USS, UE-specific search space).

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

[0112] USS can be used to transmit DCI to a specific UE 102. For example, USS can be determined based on a radio network temporary identifier (RNTI) (e.g., C-RNTI). For example, a USS can be defined for DCI formats with CRC scrambled by C-RNTI and / or CS-RNTI.

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

[0114] Here, the index “0” of the CORESET (i.e., the value “0” of the CORESET) can be configured by using the MIB and / or SIB. For example, the index “0” of the CORESET can be used to identify the common CORESET configured in the MIB and / or SIB. That is, the indexes of the CORESET other than the value “0” can be configured as the indexes of the CORESET. Additionally, the index of the CORESET with the value “0” can be configured by using the information of CORESET-zero. Additionally, the index “0” of the CORESET can be configured by using a dedicated RRC message (i.e., an RRC message specific to the UE and / or an RRC message specific to the serving cell). That is, the gNB 160 can transmit the 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 the information for configuring CORESET#0 by using the SIB. Additionally or alternatively, the gNB 160 can transmit the information for configuring CORESET#0 by using a dedicated RRC message.

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

[0116] Here, the gNB 106 can transmit the information for configuring the index of the DL BWP (e.g., an index other than the index “0”) by using an RRC message (e.g., the MIB, SIB, and / or a dedicated RRC message). Additionally, the gNB 106 can transmit the information for configuring the index of the UL BWP (e.g., an index other than the index “0”) by using an RRC message (e.g., the MIB, SIB, and / or a dedicated RRC message).

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

[0118] Additionally or alternatively, for each of the one or more CORESETs, a search space set (e.g., a set of CSS and / or USS) can be configured. For example, first information can be configured for a DL BWP. That is, the first information can be configured for each DL BWP in the DL BWP of a serving cell.

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

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

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

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

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

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

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

[0126] Additionally or alternatively, 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, UE 102 may perform reception based on the configuration for the UL BWP.

[0127] Here, DCI format 1_Y (e.g., DCI format 1_2) may include a transmission configuration indication (TCI) field for PDSCH reception. When tci-PresentInDCI is configured, the TCI state may have 3 bits in DCI format 1_1, and the TCI status field may have 1, 2, or 3 bits in DCI format 1_2.

[0128] Figure 5 An example of TCI state configuration is shown. The TCI state can be configured by a higher layer (e.g., the RRC layer). The UE 102 can be configured with up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode the PDSCH according to the detected PDCCH with DCI intended for the UE 102 and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring the quasi-co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS ports of the PDCCH, or the CSI-RS ports of the CSI-RS resources. For the first DL RS, the quasi-co-location relationship is configured by the higher layer parameter qcl-Type1, and for the second DL RS (if configured), by qcl-Type2. For the case of two DL RSs, the QCL types should not be the same, regardless of whether the same or different DL RSs are referred to. The quasi-co-location type corresponding to each DL RS is given by qcl-Type in the higher layer parameter QCL-Info and can take one of the following values.

[0129] - "QCL-TypeA": {Doppler shift, Doppler spread, average delay, delay spread}

[0130] - "QCL-TypeB": {Doppler shift, Doppler spread}

[0131] - "QCL-TypeC": {Doppler shift, average delay}

[0132] - "QCL-TypeD": {Spatial Rx parameter}

[0133] The UE 102 receives an activation command in the MAC layer, which is used to map up to L TCI states to the code points (TCI fields) of the DCI field. For example, for DCI format 1_1, L can be 8, and for DCI format 1_2, L is 2, 4, or 8. When the HARQ-ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n, it should be from the slot Starting from the first time slot after that, an indication mapping between the TCI state and the code point of the DCI field (TCI field) is applied. If tci-PresentInDCI is set to "enabled" for the CORESET used for scheduling the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL (if applicable), after the UE 102 receives the initial high-layer configuration of the TCI state and before receiving the activation command, the UE 102 may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the SS / PBCH block determined during the initial access procedure with respect to "QCL-TypeA", and also with respect to "QCL-TypeD" when applicable.

[0134] If the UE 102 is configured with the high-layer parameter tci-PresentInDCI, which is set to "enabled" for the CORESET scheduling the PDSCH, the UE 102 assumes that there is a TCI field in the DCI format 1_1 of the PDCCH transmitted on the CORESET. If tci-PresentInDCI is not configured for the CORESET scheduling the PDSCH, or the PDSCH is scheduled by the DCI format 1_0, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than the threshold timeDurationForQCL (if applicable), where the threshold is based on the reported UE capabilities, for determining the PDSCH antenna port quasi-co-location, the UE 102 assumes that the TCI state or the QCL assumption of the PDSCH is the same as the TCI state or the QCL assumption applied for the CORESET used for PDCCH transmission. The tci-PresentInDCI indicates the presence or absence of the TCI field in the DL-related DCI. When this field is absent, the UE 102 considers that the TCI is absent / disabled. In the case of cross-carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross-carrier scheduling in the scheduling cell. The ControlResourceSet is the configuration that applies the configured CORESET.

[0135] If TCI-PresentInDCI is set to "enabled", the TCI field in the DCI in the scheduled component carrier points to the active TCI state in the scheduled component carrier or DL BWP, and when the PDSCH is scheduled by DCI format 1_1, UE 102 shall use the TCI state according to the value of the "transmission configuration indication" field in the detected PDCCH with the DCI for determining the PDSCH antenna port quasi-co-location. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than the threshold timeDurationForQCL, where the threshold is based on the reported UE capabilities, UE 102 may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS in the TCI state with respect to the QCL type parameters given by the indicated TCI state. When UE 102 is configured with a single-slot PDSCH, the indicated TCI state shall be based on the active TCI state in the slot with the scheduled PDSCH. When UE 102 is configured with a multi-slot PDSCH, the indicated TCI state shall be based on the active TCI state in the first slot with the scheduled PDSCH, and UE 102 shall expect the active TCI state to be the same on the slots with the scheduled PDSCH. When UE 102 is configured with a CORESET associated with a search space set for cross-carrier scheduling, UE 102 expects tci-PresentInDci to be set to "enabled" for the CORESET, and if one or more of the TCI states in the TCI state configured for the serving cell scheduled by the search space set contain "QCL-TypeD", UE 102 expects the time offset between the reception of the PDCCH detected in the search space set and the corresponding PDSCH to be greater than or equal to the threshold timeDurationForQCL.

[0136] For both cases where tci-PresentInDCI is set to "enabled" and where tci-PresentInDCI is not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, UE 102 may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the QCL parameters of the RS with respect to the QCL indication of the PDCCH for the CORESET associated with the monitored search space having the lowest CORESET-ID in the latest time slot, in which one or more CORESETs in the active BWP of the serving cell are monitored by UE 102. In this case, if the "QCL-TypeD" of the PDSCH DM-RS is different from the "QCL-TypeD" of the PDCCH DM-RS overlapping in at least one symbol, UE 102 is expected to prioritize the reception of the PDCCH associated with this CORESET. This also applies to the in-band CA case (when the PDSCH and CORESET are in different component carriers). If none of the configured TCI states of the serving cell of the scheduled PDSCH contain "QCL-TypeD", UE 102 shall obtain other QCL assumptions from the indicated TCI state for its scheduled PDSCH, regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0137] Here, for DCI format 1_2, separate parameters / messages, such as tci-PresentInDCI-ForDCI1_2, can be configured by the RRC layer. When the parameter tci-PresentInDCI is configured or enabled, 3 bits of the TCI field can be configured for DCI format 1_1. When the parameter tci-PresentInDCI-ForDCI1_2 is configured or enabled, 1, 2, or 3 bits of the TCI field can be configured for DCI format 1_2.

[0138] Alternatively or in addition, when the parameter tci-PresentInDCI is configured or enabled, 3 bits of the TCI field can be configured for DCI format 1_1, and 1, 2, or 3 bits of the TCI field can be configured for DCI format 1_2.

[0139] Separate parameters such as TCIsize from tci-PresentInDCI or tci-PresentInDCI-ForDCI1_2 can be configured to indicate the number of bits of the TCI field in DCI format 1_2.

[0140] Here, the TCI state in the higher layer can be configured for the PDSCH in pdsch-Config. This can be configured for each BWP or for each serving cell. For each CORESET, the subset of the TCI states defined in the pdsch-Config included in BWP-DownlinkDedicated corresponds to the serving cell or DL BWP to which the ControlResourceSet belongs. They are used to provide the QCL relationship between the DL RS in a reference signal set (TCI-State) and the PDCCH DMRS ports. The network configures at most maxNrofTCI-StatesPDCCH entries.

[0141] When a 3-bit TCI field is configured for DCI format 1_1 and 0, 1, or 2-bit TCI fields are configured for DCI format 1_2, any of the following configurations can be configured.

[0142] 1) Each code point of the TCI field in DCI format 1_2 can be a subset of the code points of the TCI field in DCI format 1_1.

[0143] 2) The code points of the TCI field in DCI format 1_1 and the code points of the TCI field in DCI format 1_2 can be configured separately or selected from the configured TCI states in the higher layer (e.g., RRC).

[0144] If a 0-bit TCI field is configured, or tci-PresentInDCI-ForDCI1_2 is disabled for DCI format 1_2, and a 3-bit TCI field is configured, or tci-PresentInDCI is enabled, the value of the code point in DCI format 1_1 can be assumed to be 0 for the PDSCH scheduled by DCI format 1_2. UE 102 can assume that the QCL assumption of the PDSCH scheduled by DCI format 1_2 is the QCL assumption indicated by the value of the code point in the TCI field in DCI format 1_1 being 0. This value may not have 0 as a predefined value. Alternatively, if a 0-bit TCI field is configured, or tci-PresentInDCI-ForDCI1_2 is disabled for DCI format 1_2, and a 3-bit TCI field is configured, or tci-PresentInDCI is enabled, the QCL assumption can be assumed to be a predefined assumption. For example, UE 102 can assume the QCL assumption of the CORESET with the lowest index of the monitored search space or the QCL assumption of the CORESET including the PDCCH that schedules the PDSCH.

[0145] Figure 6 is a diagram showing the TCI state and the TCI fields in DCI format 1_1 and DCI format 1_2. AsFigure 6 As shown, the value of the TCI state for DCI format 1_1 can be mapped to each code point of DCI format 1_2. The TCI state ID is an identifier that identifies the TCI state. Here, the code points of DCI format 1_1 with the same value can be mapped to the corresponding coding points of DCI format 1_2.

[0146] Alternatively, the code points of DCI format 1_2 can be activated by the MAC layer based on the number of bits of the TCI field. When the number of bits of the TCI field is 1 bit, 2 TCI states can be activated by the MAC layer. When the number of bits of the TCI field is 2 bits, 4 TCI states can be activated by the MAC layer. The MAC CE can be used for the activation of DCI format 1_2. Separate MAC CEs can be used for the activation of the TCI states of DCI format 1_1 and DCI format 1_2 respectively.

[0147] Optionally, the MAC CE can be used for the activation of the TCI states of DCI format 1_1 and DCI format 1_2 respectively.

[0148] When 0-bit TCI field is configured for DCI format 1_1 and 1 or 2-bit TCI field is configured for DCI format 1_2, any of the following configurations can be configured.

[0149] 1) Each code point of the TCI field in DCI format 1_1 can be a subset of the code points of the TCI field in DCI format 1_2.

[0150] 2) The code points of the TCI field in DCI format 1_1 and the code points of the TCI field in DCI format 1_2 can be configured separately or selected from the configured TCI states in the higher layer (e.g., RRC).

[0151] If the 0-bit TCI field is configured, or tci-PresentInDCI is disabled for DCI format 1_1, and the 1-bit, 2-bit, or 3-bit TCI field is configured, or tci-PresentInDCI-ForDCI1_2 is enabled, then for a PDSCH scheduled by DCI format 1_1, the value of the code point in DCI format 1_2 can be assumed to be 0. UE 102 can assume that the QCL assumption of the PDSCH scheduled by DCI format 1_1 is the QCL assumption indicated by the value of the code point in the TCI field in DCI format 1_2 being 0. This value may not have 0 as a predefined value. Alternatively, if the 0-bit TCI field is configured, or tci-PresentInDCI is disabled for DCI format 1_1, and the 1-bit, 2-bit, or 3-bit TCI field is configured, or tci-PresentInDCI-ForDCI1_2 is enabled, then the QCL assumption can be assumed to be a predefined assumption. For example, UE 102 can assume the QCL assumption of the CORESET with the lowest index of the monitoring search space or the QCL assumption of the CORESET that includes the PDCCH scheduling the PDSCH.

[0152] Figure 7 Illustrates various components that can be used for UE 802. In combination with Figure 7 The UE 802 described can be implemented according to the UE 102 described in combination with Figure 1 The UE 802 includes a processor 803 that controls the operation of the UE 802. The processor 803 may also be referred to as a central processing unit (CPU). A memory 805 (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 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 that are loaded for the processor 803 to execute or process. The instructions 807b can be executed by the processor 803 to implement the methods described herein.

[0153] UE 802 may also include a housing that houses one or more transmitters 858 and one or more receivers 820 to allow for the transmission and reception of data. The transmitter 858 and the receiver 820 may be combined into one or more transceivers 818. One or more antennas 822a-n are attached to the housing and electrically coupled to the transceivers 818.

[0154] The various components of the UE 802 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 clarity, the various buses are shown as the bus system 811 in Figure 7 The UE 802 may also include a digital signal processor (DSP) 813 for processing signals. The UE 802 may also include a communication interface 815 that provides user access to the functions of the UE 802. Figure 7 The UE 802 shown is a functional block diagram rather than a list of specific components.

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

[0156] The gNB 960 may also include a housing that houses one or more transmitters 917 and one or more receivers 978 to allow for the transmission and reception of data. The transmitters 917 and receivers 978 may be combined into one or more transceivers 976. One or more antennas 980a-n are attached to the housing and electrically coupled to the transceivers 976.

[0157] The various components of the gNB 960 are coupled together via a bus system 911 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for clarity, the various buses are shown as the bus system 911 in Figure 8 The gNB 960 may also include a digital signal processor (DSP) 913 for processing signals. The gNB 960 may also include a communication interface 915 that provides access to the functions of the gNB 960 to a user. Figure 8 The gNB 960 shown is a functional block diagram rather than a list of specific components.

[0158] Figure 9 is a block diagram showing an embodiment of a UE 1002 in which one or more of the systems and / or methods described herein may be implemented. The UE 1002 includes a transmitting device 1058, a receiving device 1020, and a control device 1024. The transmitting device 1058, the receiving device 1020, and the control device 1024 may be configured to perform one or more of the functions associated with the above Figure 1 described functions. The above Figure 7 shows Figure 9 an example of a specific device structure. Various other structures may be implemented to achieve Figure 1 one or more of the functions. For example, a DSP may be implemented by software.

[0159] Figure 10 is a block diagram showing an embodiment of a gNB 1160 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1160 includes a transmitting device 1117, a receiving device 1178, and a control device 1182. The transmitting device 1117, the receiving device 1178, and the control device 1182 may be configured to perform one or more of the functions associated with the above Figure 1 described functions. The above Figure 8 shows Figure 10 an example of a specific device structure. Various other structures may be implemented to achieve Figure 1 one or more of the functions. For example, a DSP may be implemented by software.

[0160] Figure 11 is a block diagram showing a specific implementation of a gNB 1260. The gNB 1260 may be an example of the gNB160 described in conjunction with Figure 1 The gNB 1260 may include a high-layer processor 1223, a DL transmitter 1225, a UL receiver 1233, and one or more antennas 1231. The DL transmitter 1225 may include a PDCCH transmitter 1227 and a PDSCH transmitter 1229. The UL receiver 1233 may include a PUCCH receiver 1235 and a PUSCH receiver 1237.

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

[0162] The DL transmitter 1225 can multiplex downlink physical channels and downlink physical signals (including reservation signals), and transmit them via the transmit antenna 1231. The UL receiver 1233 can receive the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1231 and demultiplex them. The PUCCH receiver 1235 can provide UCI to the higher layer processor 1223. The PUSCH receiver 1237 can provide the received transport block to the higher layer processor 1223.

[0163] Figure 12 is a block diagram showing a specific implementation of the UE 1302. The UE 1302 can be an example of the UE102 described in conjunction with Figure 1 The UE 1302 can include a higher layer processor 1323, a UL transmitter 1351, a DL receiver 1343, and one or more antennas 1331. The UL transmitter 1351 can include a PUCCH transmitter 1353 and a PUSCH transmitter 1355. The DL receiver 1343 can include a PDCCH receiver 1345 and a PDSCH receiver 1347.

[0164] The higher layer processor 1323 can manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide higher layer parameters to the physical layer. The higher layer processor 1323 can obtain transport blocks from the physical layer. The higher layer processor 1323 can send to / receive from the higher layer of the UE higher layer messages, such as RRC messages and MAC messages. The higher layer processor 1323 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1353.

[0165] The DL receiver 1343 can receive the multiplexed downlink physical channels and downlink physical signals via the receive antenna 1331 and demultiplex them. The PDCCH receiver 1345 can provide DCI to the higher layer processor 1323. The PDSCH receiver 1347 can provide the received transport block to the higher layer processor 1323.

[0166] Figure 13 is a flowchart showing a communication method 1400 performed by the UE 102. The UE 102 can receive 1402 a radio resource control (RRC) message, which includes information for configuring a priority indication present in a downlink control information (DCI) format. The DCI format can be used to schedule a physical downlink shared channel (PDSCH). The priority indication can be used to indicate the priority for hybrid automatic repeat request - acknowledgement (HARQ - ACK) transmission for the PDSCH.

[0167] UE 102 may perform 1404 HARQ-ACK transmission for PDSCH based on this priority. This information may be configured for each control resource set (CORESET), except for the CORESET with index "0".

[0168] Figure 14 FIG. is a flowchart showing a communication method 1500 performed by a base station device (gNB) 160. The gNB 160 may transmit 1502 an RRC message that includes information for configuring a priority indication present in a DCI format. This DCI format may be used for scheduling PDSCH. This priority indication may be used to indicate the priority for HARQ-ACK transmission for PDSCH.

[0169] The gNB 160 may perform 1504 HARQ-ACK reception for PDSCH based on this priority. This information may be configured for each CORESET, except for the CORESET with index "0".

[0170] As described above, some methods for UL transmission may be applied (e.g., specified). Here, a combination of one or more of the methods described herein may be applied to UL transmission. A combination of one or more of the methods described herein may not be excluded in the systems and methods.

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

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

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

[0174] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, these method steps and / or actions can be interchanged with each other and / or combined into a single step. In other words, unless the correct operation of the method requires steps or actions in a specific order, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims.

[0175] It should be understood that the claims are not limited to the exact configurations and components shown above. Without departing from the scope of the claims, various modifications, changes, and alterations can be made to the arrangements, operations, and details of the systems, methods, and apparatuses described herein.

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

[0177] In addition, when the program is commercially available, the program stored on a portable recording medium can be distributed, or the program can be transmitted to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. Further, some or all of the gNB 160 and the 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 the UE 102 can be individually built into a chip, and some or all of the functional blocks can be integrated into a chip. Further, the technology of the integrated circuit is not limited to LSIs, and the integrated circuit for the functional blocks can be implemented using a dedicated circuit or a general-purpose processor. Further, if an integrated circuit technology alternative to LSIs emerges as semiconductor technology continues to advance, the integrated circuit applying that technology can also be used.

[0178] In addition, each functional block or various features of the base station device and the terminal device used in each of the above embodiments can be implemented or executed by a circuit (usually one integrated circuit or a plurality of integrated circuits). The circuit designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each circuit described herein may be configured by a digital circuit or may be configured by an analog circuit. Further, when an integrated circuit technology for fabricating an integrated circuit that replaces the current integrated circuit emerges due to the advancement of semiconductor technology, the integrated circuit produced by that technology can also be used.

[0179] As used herein, the term "and / or" shall be construed to mean one or more items. For example, the phrase "A, B, and / or C" shall be construed to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" should be construed to mean one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" shall be construed to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" shall be understood to mean one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" shall be construed to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.

[0180] <Cross-reference>

[0181] This non-provisional application claims priority under 35 U.S.C. § 119 to Provisional Application No. 62 / 932,178, filed on November 7, 2019, the entire content of which is hereby incorporated by reference.

Claims

1. A user equipment, the user equipment comprising: a receiver configured to receive information from a higher layer, the information including one or more transmission configuration indication (TCI) states, first information, and second information; receive a media access control (MAC) control element (CE); and receive downlink control information (DCI); wherein the first information indicates the presence or absence of a first TCI field in a first DCI format, the second information indicates the number of bits of a second TCI field in a second DCI format different from the first DCI format, when the first information indicates the presence of the first TCI field in the first DCI format, predetermined bits of the first TCI field are configured, the number of bits of the second TCI field in the second DCI format is configured by the second information, and the MAC CE activates TCI states from the one or more TCI states, and at least some of the activated TCI states are mapped to code points in the first TCI field and the second TCI field.

2. A base station apparatus, the base station apparatus comprising: a transmitter configured to transmit information from a higher layer, the information including one or more transmission configuration indication (TCI) states, first information, and second information; transmit a media access control (MAC) control element (CE); and transmit downlink control information (DCI); wherein the first information indicates the presence or absence of a first TCI field in a first DCI format, the second information indicates the number of bits of a second TCI field in a second DCI format different from the first DCI format, when the first information indicates the presence of the first TCI field in the first DCI format, predetermined bits of the first TCI field are configured, the number of bits of the second TCI field in the second DCI format is configured by the second information, and the MAC CE activates TCI states from the one or more TCI states, and at least some of the activated TCI states are mapped to code points in the first TCI field and the second TCI field.

3. A communication method of a user equipment, the communication method comprising: receiving information from a higher layer, the information including one or more transmission configuration indication (TCI) states, first information, and second information; receiving a media access control (MAC) control element (CE); and receiving downlink control information (DCI); wherein the first information indicates the presence or absence of a first TCI field in a first DCI format, the second information indicates the number of bits of a second TCI field in a second DCI format different from the first DCI format, when the first information indicates the presence of the first TCI field in the first DCI format, predetermined bits of the first TCI field are configured, the number of bits of the second TCI field in the second DCI format is configured by the second information, and The MAC CE activates TCI states from the one or more TCI states, and at least some of the activated TCI states are mapped to code points in the first TCI field and the second TCI field.

Images