User Equipment, Base Station, and Method for Downlink Control Information (DCI) of DCI Format

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive first information, second information, and a downlink control information (DCI) format including a value of a carrier indicator field. The UE further includes a transmitting circuit configured to perform transmission of a physical uplink shared channel on a serving cell based on the DCI format. A maximum value of the second information is determined based on a number of serving cells having a downlink bandwidth part (DL BWP), where a search space set for PDCCH monitoring for the DCI format is configured at the DL BWP.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to a user equipment (UE), a base station, and a method for downlink control information (DCI) of DCI formats. 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 bring certain problems.

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

[0005] In one example, a user equipment (UE) includes: a receiving circuit configured to: receive a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format for scheduling a physical uplink shared channel (PUSCH); receive an RRC message including second information for indicating a value of a carrier indicator field to indicate the DCI format applicable to a serving cell; receive the DCI format including the value of the carrier indicator field; and a transmitting circuit configured to perform transmission of a physical uplink shared channel on the serving cell based on detection of the DCI format, wherein a maximum value of the second information is determined based on a number of serving cells having a downlink bandwidth part (DLBWP) where the search space set for the PDCCH monitoring for the DCI format is configured.

[0006] In one example, a base station apparatus includes: a transmission circuit configured to: transmit a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format for scheduling a physical uplink shared channel (PUSCH); transmit an RRC message including second information for indicating a value of a carrier indicator field indicating the DCI format applicable to a serving cell; transmit the DCI format including the value of the carrier indicator field; and a reception circuit configured to perform reception of a physical uplink shared channel on the serving cell based on the transmission of the DCI format, wherein a maximum value of the second information is determined based on the number of serving cells having a downlink bandwidth part (DL BWP) where a search space set for the PDCCH monitoring for the DCI format is configured.

[0007] In one example, a communication method of a user equipment (UE) includes: receiving a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format for scheduling a physical uplink shared channel (PUSCH); receiving an RRC message including second information for indicating a value of a carrier indicator field indicating the DCI format applicable to a serving cell; receiving the DCI format including the value of the carrier indicator field; and performing transmission of a physical uplink shared channel on the serving cell based on detection of the DCI format, wherein a maximum value of the second information is determined based on the number of serving cells having a downlink bandwidth part (DL BWP) where a search space set for the PDCCH monitoring for the DCI format is configured.

[0008] In one example, a communication method of a base station device includes: sending a Radio Resource Control (RRC) message including first information for configuring a search space set for monitoring a Physical Downlink Control Channel (PDCCH) for a Downlink Control Information (DCI) format for scheduling a Physical Uplink Shared Channel (PUSCH); sending an RRC message including second information for indicating a value of a Carrier Indicator Field to indicate the DCI format applicable to a serving cell; sending the DCI format including the value of the Carrier Indicator Field; and performing reception of a Physical Uplink Shared Channel on the serving cell based on the sending of the DCI format, wherein a maximum value of the second information is determined based on the number of serving cells having a Downlink Bandwidth Part (DL BWP), and a search space set for monitoring the PDCCH for the DCI format is configured at the DL BWP. Description of the Drawings

[0009] Figure 1 is a block diagram showing one particular implementation of one or more gNBs and one or more UEs in which a system and method for signaling can be implemented.

[0010] Figure 2 Shows examples of multiple parameters.

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

[0012] Figure 4 Shows examples of resource regions.

[0013] Figure 5 Shows an example of cross-carrier scheduling.

[0014] Figure 6 Shows an example of cross-carrier scheduling.

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

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

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

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

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

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

[0021] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format. The DCI format is used to schedule a physical uplink shared channel (PUSCH). The receiving circuit is further configured to receive an RRC message including second information for indicating a value of a carrier indicator field to indicate the DCI format applicable to a serving cell. The receiving circuit is further configured to receive a DCI format including a value of the carrier indicator field. The UE further includes a transmitting circuit configured to perform transmission of a physical uplink shared channel on a serving cell based on detection of the DCI format. The maximum value of the second information is determined based on the number of serving cells having a downlink bandwidth part (DL BWP) where the search space set for the PDCCH monitoring for the DCI format is configured.

[0022] The present invention also describes a base station device. The base station includes a transmitting circuit configured to transmit a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format. The DCI format is used to schedule a physical uplink shared channel (PUSCH). The transmitting circuit is further configured to transmit an RRC message including second information for indicating a value of a carrier indicator field to indicate the DCI format applicable to a serving cell. The transmitting circuit is further configured to transmit a DCI format including a value of the carrier indicator field. The base station device further includes a receiving circuit configured to perform reception of a physical uplink shared channel on a serving cell based on transmission of the DCI format. The maximum value of the second information is determined based on the number of serving cells having a downlink bandwidth part (DL BWP) where the search space set for the PDCCH monitoring for the DCI format is configured.

[0023] The present invention also describes a communication method for a UE. The method includes receiving a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format, where the DCI format is used for scheduling a physical uplink shared channel (PUSCH). The method also includes receiving an RRC message including second information for indicating a value of a carrier indicator field to indicate a DCI format applicable to a serving cell. The method also includes receiving a DCI format including a value of the carrier indicator field. The method also includes performing transmission of a physical uplink shared channel on the serving cell based on detecting the DCI format. A maximum value of the second information is determined based on the number of serving cells having a downlink bandwidth part (DL BWP) where the search space set for the PDCCH monitoring for the DCI format is configured.

[0024] The present invention also describes a communication method for a base station device. The method includes transmitting a radio resource control (RRC) message including first information for configuring a search space set for physical downlink control channel (PDCCH) monitoring for a downlink control information (DCI) format, where the DCI format is used for scheduling a physical uplink shared channel (PUSCH). The method also includes transmitting an RRC message including second information for indicating a value of a carrier indicator field to indicate a DCI format applicable to a serving cell. The method also includes transmitting a DCI format including a value of the carrier indicator field. The method also includes performing reception of a physical uplink shared channel on the serving cell based on the transmission of the DCI format. A maximum value of the second information is determined based on the number of serving cells having a downlink bandwidth part (DL BWP) where the search space set for the PDCCH monitoring for the DCI format is configured.

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

[0026] 3GPP Long-Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to 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).

[0027] At least some aspects of the systems and methods disclosed herein may be described in connection 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.

[0028] A wireless communication device may be an electronic device that is configured to transmit voice and / or data to a base station, which in turn may communicate with the device's network (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular telephones, smartphones, 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 represent the more general term "wireless communication device". A UE may also more generally be referred to as a terminal device.

[0029] 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 represent the more general term "base station". In addition, the term "base station" may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., a local area network (LAN), the Internet, etc.) for a wireless communication device. 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.

[0030] It should be noted that, as used herein, a "cell" may be any such communication channel that 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 noted that, in the overall description of E-UTRA and E-UTRAN, as used herein, a "cell" may be defined as "a combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information that is transmitted on the downlink resources.

[0031] The fifth-generation communication system, which is called NR (New Radio) by 3GPP, is envisioned to use time / frequency / spatial resources to allow 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, transmissions 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 perform reception of downlink signals and / or transmission of uplink signals in a BWP of a serving cell.

[0032] 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 transmissions. Accordingly, a process for effectively controlling downlink and / or uplink transmissions should be designed. Thus, a detailed design of the process for downlink and / or uplink transmissions may be beneficial.

[0033] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, where like reference numerals may indicate functionally similar elements. The systems and methods generally described and illustrated in the accompanying 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 in the drawings is not intended to limit the scope of the claimed subject matter, but merely represents the described systems and methods.

[0034] Figure 1 is a block diagram showing one implementation of one or more gNBs 160 and one or more UEs 102 in which a system and method 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 send 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.

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

[0036] Each of the one or more UE 102 can 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 can 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) can be implemented.

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

[0038] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the 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 can use to perform one or more operations.

[0039] Generally speaking, 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 of the UE scheduling modules 126.

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

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

[0042] For example, in the uplink, a PRACH (Physical Random Access Channel) may be defined. In some methods, the PRACH (e.g., random access procedure) may be used for an initial access connection establishment process, a handover process, 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).

[0043] In another example, a Physical Uplink Control Channel (PUCCH) can be defined. The PUCCH can be used to transmit uplink control information (UCI). The UCI can include Hybrid Automatic Repeat reQuest - ACKnowledgment (HARQ - ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ - ACK is used to indicate a positive acknowledgment (ACK) or negative acknowledgment (NACK) of downlink data (e.g., transport block, Media 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., 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)).

[0044] Here, the DL - SCH and / or UL - SCH can be transport channels used in the MAC layer. Additionally, a transport block (TB) and / or MAC PDU can be defined as units of a transport channel used in the MAC layer. The transport block can be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer can deliver the 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, the transport block can be mapped to one or more codewords.

[0045] In the downlink, a Physical Downlink Control Channel (PDCCH) can be defined. The PDCCH can be used to transmit downlink control information (DCI). Here, more than one DCI format can be defined for DCI transmission on the PDCCH. That is, a DCI format can be defined with fields, and the fields can be mapped to information bits (e.g., DCI bits).

[0046] For example, DCI format 1_0 for scheduling the Physical Downlink Shared Channel (PDSCH) in a cell can 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 a first RNTI) can be used to transmit DCI format 1_0. Moreover, DCI format 1_0 can 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 can be monitored (e.g., transmitted, mapped) only in the CSS.

[0047] For example, the DCI included in DCI format 1_0 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, or alternatively, the DCI included in DCI format 1_0 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_0 can be a TPC (e.g., transmit power control) command for the PUCCH used for scheduling. Additionally or alternatively, the DCI included in DCI format 1_0 can be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_0 can be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_0 can 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 can be a priority indication (e.g., for HARQ-ACK transmission of PDSCH and / or for HARQ-ACK reception of PDSCH). That is, the β-offset indicator may not be included in DCI format 1_0.

[0048] 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, the highest priority, a lower priority, and / or the lowest priority).

[0049] Additionally or alternatively, 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., 2-bit information, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, in the case where the UE 102 detects a DCI format including a priority indication for the downlink, 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). Additionally or alternatively, in the case where the UE 102 detects a DCI format including a priority indication for the downlink, the UE 102 may generate two HARQ-ACK codebooks for two PDSCH transmissions. For example, in the case where the UE 102 detects a DCI format including a priority indication for the downlink, a first HARQ-ACK codebook for the first PDSCH transmission is generated, and a second HARQ-ACK codebook for the second PDSCH transmission is generated. Additionally or alternatively, the UE 102 may transmit two HARQ-ACK codebooks simultaneously (e.g., in symbols and / or time slots). That is, the UE 102 may transmit a first HARQ-ACK corresponding to the first HARQ-ACK codebook and a second HARQ-ACK corresponding to the second HARQ-ACK codebook simultaneously (e.g., in symbols and / or time slots).

[0050] 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, a 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.

[0051] For example, the DCI included in DCI format 1_1 can be a carrier indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 can be a TPC command for the PUCCH used for scheduling. Additionally or alternatively, the DCI included in DCI format 1_1 can 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 can be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_1 can be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_1 can 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 can be a priority indication (e.g., for HARQ-ACK transmission of PDSCH and / or for HARQ-ACK reception of PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a β-offset indicator.

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

[0053] For example, the DCI included in DCI format 1_X may be a carrier indicator (e.g., for PDSCH). Additionally or alternatively, 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 for PDSCH and / or for HARQ-ACK reception for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_X may be a β offset indicator.

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

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

[0056] Additionally or alternatively, 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 can generate two HARQ-ACK codebooks for two PDSCH transmissions. For example, in the case where the UE 102 detects a DCI format including a priority indication for the downlink, a first HARQ-ACK codebook for the first PDSCH transmission is generated, and a second HARQ-ACK codebook for the second PDSCH transmission is generated. Additionally or alternatively, the UE 102 can transmit two HARQ-ACK codebooks simultaneously (e.g., in symbols and / or time slots). That is, the UE 102 can transmit a first HARQ-ACK corresponding to the first HARQ-ACK codebook and a second HARQ-ACK corresponding to the second HARQ-ACK codebook simultaneously (e.g., in symbols and / or time slots).

[0057] Additionally or alternatively, DCI format 0_0 for scheduling PUSCH in a cell may be defined as a DCI format for the uplink. Additionally or alternatively, C-RNTI, CS-RNTI, temporary C-RNTI, and / or the 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.

[0058] For example, the DCI included in DCI format 0_0 may be a frequency-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a time-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_0 may be a redundancy version. Additionally or alternatively, the DCI included in DCI format 0_0 may be a TPC command for scheduling 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).

[0059] 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 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). Additionally or alternatively, in the case where UE 102 detects a DCI format including a priority indication for the uplink, UE 102 can generate two PUSCHs for two UL-SCH transmissions. For example, in the case where UE 102 detects a DCI format including a priority indication for the uplink, a first transmission is performed on a first PUSCH (e.g., for a first UL-SCH, the first UL-SCH is mapped to the first PUSCH), and a second transmission is performed on a second PUSCH (e.g., for a second UL-SCH, the second UL-SCH is mapped to the second PUSCH). Additionally or alternatively, UE 102 can perform simultaneous transmission of two PUSCHs (e.g., in symbols and / or time slots). For example, UE 102 can perform simultaneous transmission of a first PUSCH corresponding to a first UL-SCH and a second PUSCH corresponding to a second UL-SCH (e.g., in symbols and / or time slots).

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

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

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

[0063] For example, the DCI included in DCI format 0_1 may be a carrier indicator (e.g., for PDSCH). Additionally or alternatively, 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 a 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). Additionally or alternatively, the DCI included in DCI format 0_1 may be a β-offset indicator. Additionally or alternatively, the DCI included in DCI format 0_1 may be a UL-SCH indicator.

[0064] 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., a higher priority, a highest priority, a lower priority, and / or a lowest priority). For example, in a 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 recognize that PUSCH transmission and / or PUSCH reception is prioritized (e.g., PUSCH transmission and / or PUSCH reception has a higher priority, a highest priority, a lower priority, and / or a lowest priority).

[0065] Additionally or alternatively, when the 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), the UE 102 may generate two PUSCHs for two UL-SCH transmissions. For example, when the UE 102 detects a DCI format including a priority indication for uplink, a first transmission is performed on a first PUSCH (e.g., for a first UL-SCH, the first UL-SCH is mapped to the first PUSCH), and a second transmission is performed on a second PUSCH (e.g., for a second UL-SCH, the second UL-SCH is mapped to the second PUSCH). Additionally or alternatively, the UE 102 may perform simultaneous transmission of the two PUSCHs (e.g., in symbols and / or time slots). For example, the UE 102 may perform simultaneous transmission of a first PUSCH corresponding to a first UL-SCH and a second PUSCH corresponding to a second UL-SCH (e.g., in symbols and / or time slots).

[0066] Additionally or alternatively, when 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), the UE 102 may perform PDSCH reception. Additionally or alternatively, when 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), the UE 102 may perform PUSCH transmission.

[0067] Here, the number of bits of the carrier indicator (i.e., the carrier indicator field) included in DCI format 1_1 and / or DCI format 0_1 may be 0 or 3 bits. That is, the number of bits of the carrier indicator included in DCI format 1_1 and / or DCI format 0_1 may always be 0 or 3 bits.

[0068] For example, gNB 160 may send, by using an RRC message, first information for configuring (e.g., indicating) whether a carrier indicator (e.g., a carrier indicator field) exists in DCI format 1_1 and / or DCI format 0_1. For example, in a case where a value (e.g., true) is configured based on the first information, the carrier indicator exists in DCI format 1_1 and / or DCI format 0_1 (i.e., a 3-bit carrier indicator field exists in DCI format 1_1 and / or DCI format 0_1). Additionally, in a case where a value (e.g., false) is configured based on the first information, the carrier indicator does not exist in DCI format 1_1 and / or DCI format 0_1 (i.e., a 0-bit carrier indicator field exists in DCI format 1_1 and DCI format 0_1).

[0069] That is, the first information may be configured commonly for DCI format 1_1 and DCI format 0_1. For example, in a case where a value (e.g., true) is configured based on the first information, the carrier indicator exists for both DCI format 1_1 and DCI format 0_1. Additionally, in a case where a value (e.g., false) is configured based on the first information, the carrier indicator exists for both DCI format 1_1 and DCI format 0_1.

[0070] Additionally or alternatively, the number of bits of the carrier indicator (i.e., the carrier indicator field) included in DCI format 1_X and / or DCI format 0_Y may be 0 or 1 or 2 or 3 bits. That is, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 0 bits (e.g., configurable). Additionally, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 1 bit (e.g., configurable). Additionally, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 2 bits (e.g., configurable). That is, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 3 bits (e.g., configurable).

[0071] For example, the gNB 160 may send second information for configuring (e.g., indicating, determining) the number of bits of a carrier indicator (e.g., carrier indicator field) included in DCI format 1_X and / or DCI format 0_Y by using an RRC message. For example, in the case of configuring (e.g., determining) 1 bit based on the second information, a 1-bit carrier indicator exists in DCI format 1_X and / or DCI format 0_Y. Additionally, in the case of configuring (e.g., determining) 2 bits based on the second information, a 2-bit carrier indicator exists in DCI format 1_X and / or DCI format 0_Y. Additionally, in the case of configuring (e.g., determining) 3 bits based on the second information, a 3-bit carrier indicator exists in DCI format 1_X and / or DCI format 0_Y. Additionally, in the case of configuring (e.g., determining) 0 bits (e.g., no value) based on the second information, a 0-bit carrier indicator exists in DCI format 1_X and / or DCI format 0_Y (i.e., no carrier indicator exists).

[0072] That is, the second information can be configured commonly for DCI format 1_X and DCI format 0_Y. For example, in the case of configuring 1 (or 2 or 3) bits based on the second information, a 1 (or 2 or 3)-bit carrier indicator exists in both DCI format 1_X and DCI format 0_Y. That is, based on the second information, the same number of bits of the carrier indicator is configured (e.g., determined) for DCI format 1_X and DCI format 0_Y.

[0073] Additionally or alternatively, the number of bits of the carrier indicator field can be configured (e.g., determined separately) for DCI format 1_X and DCI format 0_Y. For example, the gNB 160 may send third information for configuring (e.g., indicating, determining) the number of bits of the carrier indicator included in DCI format 1_X by using an RRC message. That is, the UE 102 can determine the number of bits of the carrier indicator included in DCI format 1_X based on the third information. Additionally, the gNB 160 may send fourth information for configuring (e.g., indicating, determining) the number of bits of the carrier indicator included in DCI format 0_Y by using an RRC message. That is, the UE 102 can determine the number of bits of the carrier indicator included in DCI format 0_Y based on the fourth information.

[0074] Here, as described above, the RNTI (e.g., radio network temporary identifier) assigned to the 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, the gNB 160 can send information for configuring (e.g., allocating) the RNTI to the UE 102 (e.g., by using an RRC message).

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

[0076] Here, the RNTI may include a C-RNTI (Cell-RNTI), a CS-RNTI (Configured Scheduling C-RNTI), an SI-RNTI (System Information RNTI), an RA-RNTI (Random Access RNTI), a temporary C-RNTI, and / or a first RNTI.

[0077] For example, the C-RNTI may be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, the CS-RNTI may be a unique identifier for scheduling transmissions based on configured grants. Additionally or alternatively, the SI-RNTI may be used to identify system messages (e.g., SI messages) mapped on the BCCH and dynamically carried on the DL-SCH. Additionally or alternatively, the SI-RNTI may be used for the broadcast of SI. Additionally or alternatively, the RA-RNTI may be an identifier for a random access process (e.g., Msg.2 transmission). Additionally or alternatively, the temporary C-RNTI may be used for the scheduling of a random access process (e.g., Msg.3 (re)transmission (e.g., Msg.3 PUSCH (re)transmission)).

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

[0079] Additionally or alternatively, as described above, the first RNTI may 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). Additionally or alternatively, as described above, 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).

[0080] Additionally or alternatively, a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH) may be defined. For example, in the case of scheduling the PDSCH (e.g., PDSCH resources) by using a DCI format for the downlink, UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Additionally or alternatively, in the case of scheduling the PUSCH (e.g., PUSCH resources) by using a DCI format for the downlink, UE 102 may transmit uplink data on the scheduled PUSCH (e.g., PUSCH resources). For example, the PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport block). Additionally or alternatively, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport block).

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

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

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

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

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

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

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

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

[0089] 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 coding expected for a transmission from gNB 160.

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

[0091] 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 error 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.

[0092] 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) to be used 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.

[0093] 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 send a signal 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 one or more modulated signals 156 and transmit the one or more modulated signals to one or more gNBs 160.

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

[0095] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and 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. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

[0096] The demodulator 172 may demodulate the 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.

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

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

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

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

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

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

[0103] 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 send signals to one or more UEs 102. One or more transmitters 117 may up-convert one or more modulated signals 115 and send the one or more modulated signals to one or more UEs 102.

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

[0105] 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 executed using hardware. For example, one or more of the methods described herein may be implemented in a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc., and / or implemented using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0106] Figure 2 An example of a plurality of parameters 201 is shown. As Figure 2As shown, multiple parameters 201 (e.g., multiple subcarrier spacings) can be supported. For example, μ (e.g., subcarrier spacing configuration) and cyclic prefix (e.g., μ and cyclic prefix for 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 subcarrier spacing of 15 kHz in the frequency domain and a 2048Ts + CP length (e.g., 160Ts or 144Ts) in the time domain, where Ts represents the baseband sampling time unit defined as 1 / (15000*2048) seconds.

[0107] Additionally or alternatively, the number of OFDM symbols 203 per time slot can be determined based on μ (e.g., subcarrier 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.

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

[0109] In Figure 3 one subframe 369 can include symbols 387. Additionally or alternatively, a resource block 391 can include multiple resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) can be employed, which can also be referred to as CP - OFDM. A downlink radio frame can include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and 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 subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l), where k and l are the indices in the frequency domain and time domain, respectively.

[0110] 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 adopted, which is also known as discrete Fourier transform spread-spectrum 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 area defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389, and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and the time domain, respectively.

[0111] Each element and subcarrier configuration μ in the resource grid 301 (e.g., antenna port p) is called a resource element 389, and is uniquely identified by an index pair (k, l), where is the index in the frequency domain, and l refers to the symbol position in the time domain. The resource element (k, l) 389 and subcarrier spacing configuration μ on antenna port p 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 relationship between the physical resource block number n in the frequency domain PRB and the resource element (k, l) is given by .

[0112] Figure 4 FIG. shows an example of a resource area (e.g., the resource area for the downlink). One or more sets 401 of PRBs 491 (e.g., control resource sets (i.e., CORESETs)) 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 the 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-continuous and / or time-continuous, the UE 102 may be configured with one or more control resource sets (e.g., CORESETs), 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 the DL control channel (which may or may not include DM-RS).

[0113] 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 DL control channel (e.g., the candidate set of PDCCHs) according to the monitored DCI format. Additionally, the candidates of PDCCH can be candidates where the DL control channel may be mapped, allocated, and / or transmitted.

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

[0115] That is, CSS and / or USS can be defined (e.g., configured) in the area of the DL control channel. For example, CSS can be used to send 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.

[0116] USS can be used to send 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.

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

[0118] 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 send 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 send the information for configuring CORESET#0 by using the SIB. Additionally or alternatively, the gNB 160 can send the information for configuring CORESET#0 by using a dedicated RRC message.

[0119] Here, CORESET#0 can be configured for the initial BWP (e.g., the initial DL BWP). Here, the gNB 160 can send the information for the initial BWP (e.g., the initial BWP) by using an RRC message (e.g., the MIB, the 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.

[0120] Here, the gNB 160 can send 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, the SIB, and / or a dedicated RRC message). Additionally, the gNB 160 can send 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, the SIB, and / or a dedicated RRC message).

[0121] As described above, CORESET #0 may be referred to as a common CORESET. Additionally, CORESETs other than CORESET #0 may 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" may be referred to as a UE-specific CORESET. For example, gNB 160 may send information for configuring a UE-specific CORESET (e.g., the index of the UE-specific CORESET) by using a dedicated RRC message.

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

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

[0124] Additionally or alternatively, the sixth information may 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 sixth information may include information for indicating one or more DCI formats in which UE 102 monitors the 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 may be configured to monitor the PDCCH (e.g., PDCCH candidates). Here, the DCI format for monitoring the PDCCH in CSS may be scrambled by C-RNTI, CS-RNTI, RA-RNTI, temporary C-RNTI, SI-RNTI, and / or the first RNTI.

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

[0126] 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., a UE-specific RRC message and / or a serving cell-specific RRC message). That is, the gNB 160 can send 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 send the information for configuring the search space set #0 by using the SIB. Additionally or alternatively, the gNB 160 can send 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).

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

[0128] Here, for example, for a serving cell, the gNB 160 can configure four DL BWP sets (e.g., up to four DL BWPs, one DL BWP set) (e.g., for reception by the UE 102) by using an RRC message. Additionally or alternatively, the gNB 160 can indicate the active DL BWP by using the DCI format for the downlink. For example, for each DL BWP in the DL BWP set, the gNB 160 can 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) of the DL BWP set by using an RRC message.

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

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

[0131] Figure 5 An example of cross-carrier scheduling is shown. For example, DCI format 1_0 on a specific serving cell (e.g., index "2" of a specific serving cell) may be used to schedule the PDSCH on the specific serving cell (e.g., index "2" of a specific serving cell) (i.e., referred to as self-carrier scheduling). Here, as described above, the carrier indicator may not be present in DCI format 1_0.

[0132] In addition, DCI format 1_1 on a specific serving cell (e.g., index "5" of a specific serving cell) may be used to schedule the PDSCH on the specific serving cell (e.g., index "5" of a specific serving cell) (i.e., referred to as self-carrier scheduling). Additionally or alternatively, DCI format 1_1 on a specific serving cell (e.g., index "5" of a certain serving cell) may be used to schedule the PDSCH on another serving cell (e.g., index "8" of another serving cell) (i.e., referred to as cross-carrier scheduling). Here, as described above, the gNB 160 may configure the presence of the carrier indicator for DCI format 1_1 and / or DCI format 0_1 by using RRC messages. That is, in the case where the presence of the carrier indicator is not configured (e.g., false), DCI format 1_1 may be used for self-carrier scheduling of the PDSCH. Additionally or alternatively, in the case where the presence of the carrier indicator is configured (e.g., true), DCI format 1_1 may be used for cross-carrier scheduling of the PDSCH.

[0133] Additionally or alternatively, DCI format 0_0 on a particular serving cell (e.g., index "2" of a particular serving cell) can be used to schedule PUSCH on the particular serving cell (e.g., index "2" of a particular serving cell) (i.e., referred to as self-carrier scheduling). Here, as described above, the carrier indicator may not be present in DCI format 0_0.

[0134] In addition, DCI format 0_1 on a particular serving cell (e.g., index "5" of a particular serving cell) can be used to schedule PUSCH on the particular serving cell (e.g., index "5" of a particular serving cell) (i.e., referred to as self-carrier scheduling). Additionally or alternatively, DCI format 0_1 on a particular serving cell (e.g., index "5" of a certain serving cell) can be used to schedule PUSCH on another serving cell (e.g., index "8" of another serving cell) (i.e., referred to as cross-carrier scheduling). Here, as described above, gNB 160 can configure the presence of the carrier indicator for DCI format 1_1 and / or DCI format 0_1 by using RRC messages. That is, in the case where the presence of the carrier indicator is not configured (e.g., false), DCI format 0_1 can be used for self-carrier scheduling of PDSCH. Additionally or alternatively, in the case where the presence of the carrier indicator is configured (e.g., true), DCI format 0_1 can be used for cross-carrier scheduling of PDSCH.

[0135] Here, for the primary cell, only self-carrier scheduling may be supported. That is, PDSCH and / or PUSCH on the primary cell can be scheduled by using DCI format 1_1 and / or DCI format 0_0 on the primary cell. Additionally or alternatively, for the secondary cell, self-carrier scheduling and cross-carrier scheduling are supported. That is, cross-carrier scheduling can be applied only to the secondary cell. Here, the index of the primary cell can be defined as "0". That is, the index of the primary cell can always be "0". Additionally or alternatively, the index of the secondary cell can be "1", or "2", or "3", or "4", or "5", or "6", or "7".

[0136] For example, gNB 160 can send the seventh information for configuring the index of a serving cell (e.g., secondary cell) by using RRC messages. And UE 102 can identify the index of the serving cell (e.g., secondary cell) based on the seventh information. Here, the seventh information can be configured for each serving cell. For example, the seventh information can be configured for each of the primary cell and / or secondary cell. Additionally or alternatively, the seventh information can be configured only for the secondary cell. That is, the primary cell may not be configured with the seventh information.

[0137] Here, as described above, the carrier indicator included in DCI format 1_1 and / or DCI format 0_1 can always be 0 bits (i.e., not configured to exist) or 3 bits (i.e., configured to exist). Additionally or alternatively, gNB 160 can send the eighth information and the ninth information by using an RRC message.

[0138] For example, the eighth information can be used to indicate which serving cells signal DCI format 1_1 and / or DCI format 0_1. That is, the eighth information can be used to indicate the serving cells for sending and / or receiving DCI format 1_1 and / or DCI format 0_1. That is, the eighth information can be used to indicate the serving cells on which UE 102 monitors the PDCCH for DCI format 1_1 and / or DCI format 0_1.

[0139] For example, for the active DL BWP of a specific serving cell on which UE 102 monitors PDCCH candidates in the USS (e.g., for DCI format 1_1 and / or DCI format 0_1), in the case where UE 102 is not configured with a carrier indicator (i.e., carrier indicator field), UE 102 can monitor PDCCH candidates (for DCI format 1_1 and / or DCI format 0_1) that do not have a carrier indicator (i.e., carrier indicator field). Additionally or alternatively, for the active DL BWP of a specific serving cell on which UE 102 monitors PDCCH candidates in the USS (e.g., for DCI format 1_1 and / or DCI format 0_1), in the case where UE 102 is configured with a carrier indicator (i.e., carrier indicator field), UE 102 can monitor PDCCH candidates with a carrier indicator (for DCI format 1_1 and / or DCI format 0_1).

[0140] For example, gNB 160 can configure the index of the serving cell (i.e., serving cell index) as the eighth information by using an RRC message. For example, as Figure 5 shown, gNB 160 can configure the serving cell index "5" (i.e., the index "5" of a specific serving cell) as the eighth information. And, in the case where the serving cell index "5" is configured, UE 102 can determine (e.g., recognize) that the serving cell with index "5" is used for sending and / or receiving DCI format 1_1 and / or DCI format 0_1. That is, in the case where the serving cell index "5" is configured, UE 102 can monitor the PDCCH for DCI format 1_1 and / or DCI format 0_1 on the serving cell with index "5".

[0141] Additionally or alternatively, the ninth information may be used to indicate the value of the carrier indicator (i.e., the carrier indicator field) used in the scheduling cell, to indicate the DCI format 1_1 and / or DCI format 0_1 applicable to the serving cell. That is, the ninth information may be used to indicate the value of the carrier indicator of the serving cell on which the PDSCH and / or PUSCH is scheduled (e.g., by using the DCI format 1_1 and / or DCI format 0_1).

[0142] For example, the gNB 160 may configure a value (e.g., 1, or 2, or 3, or 4, or 5, or 6, or 7) as the ninth information by using an RRC message. For example, as Figure 5 shown, for the serving cell with the index "8" (i.e., the index of the specific serving cell "8"), the gNB 160 may configure the value "6" as the ninth information. And, in the case where the value "6" is configured, the UE 102 may determine (e.g., recognize) that the serving cell with the index "8" is scheduled by using the value "6" of the carrier indicator field (i.e., the 3-bit information field "110"). That is, the PDSCH on the serving cell with the index "8" may be scheduled by using the carrier indicator field set to the value "6" (i.e., the 3-bit information field set to "110"), and this value is included in the DCI format 1_1. Additionally or alternatively, the PUSCH on the serving cell with the index "8" may be scheduled by using the carrier indicator field set to the value "6" (i.e., the 3-bit information field set to "110"), and this value is included in the DCI format 0_1. Here, as described above, the DCI format 1_1 and / or DCI format 0_1 may be transmitted and / or received on the serving cell with the index "5" (i.e., the serving cell index "5") based on the eighth information.

[0143] Here, the first information and / or the eighth information and / or the ninth information may be configured for each serving cell. That is, the first information and / or the eighth information and / or the ninth information may be configured for each of the primary cell and / or the secondary cell. Additionally or alternatively, the first information and / or the eighth information and / or the ninth information may be configured only for the secondary cell. That is, the first information and / or the eighth information and / or the ninth information may not be configured for the primary cell.

[0144] As described above, in the case where there is a carrier indicator in DCI format 1_1 and / or DCI format 0_1, a value (e.g., 1, or 2, or 3, or 4, or 5, or 6, or 7) is configured as the ninth information. That is, in the case where there is a 3-bit carrier indicator in DCI format 1_1 and / or DCI format 0_1, a value (e.g., 1, or 2, or 3, or 4, or 5, or 6, or 7) is configured as the ninth information. That is, in the case where there is a 3-bit carrier indicator in DCI format 1_1 and / or DCI format 0_1, the maximum value of the ninth information can be "7". That is, in the case where the presence of the carrier indicator is configured (e.g., for DCI format 1_1 and / or for DCI format 0_1), the maximum value of the ninth information can always be "7". That is, in the case where the presence of the carrier indicator is configured (e.g., for DCI format 1_1 and / or for DCI format 0_1), up to "7" serving cells corresponding to the 3-bit carrier indicator can be scheduled by using DCI format 1_1 and / or DCI format 0_1 (e.g., up to "7" serving cells). That is, the maximum number "7" can correspond to the 3-bit carrier indicator included in DCI format 1_1 and / or DCI format 0_1.

[0145] Figure 6 An example of cross-carrier scheduling is shown. For example, DCI format 1_X on a specific serving cell (e.g., the index "5" of a specific serving cell) can be used to schedule PDSCH on the specific serving cell (e.g., the index "5" of a specific serving cell) (i.e., referred to as self-carrier scheduling). Additionally or alternatively, DCI format 1_X on a specific serving cell (e.g., the index "5" of a certain serving cell) can be used to schedule PDSCH on another serving cell (e.g., the index "3" of another serving cell) (i.e., referred to as cross-carrier scheduling).

[0146] Additionally or alternatively, DCI format 0_Y on a specific serving cell (e.g., the index "5" of a specific serving cell) can be used to schedule PUSCH on the specific serving cell (e.g., the index "5" of a specific serving cell) (i.e., referred to as self-carrier scheduling). Additionally or alternatively, DCI format 0_Y on a specific serving cell (e.g., the index "5" of a certain serving cell) can be used to schedule PUSCH on another serving cell (e.g., the index "3" of another serving cell) (i.e., referred to as cross-carrier scheduling).

[0147] Here, as described above, for the primary cell, only self-carrier scheduling can be supported. That is, PDSCH and / or PUSCH on the primary cell can be scheduled by using DCI format 1_X and / or DCI format 0_Y on the primary cell. Additionally or alternatively, for the secondary cell, self-carrier scheduling and cross-carrier scheduling are supported. That is, cross-carrier scheduling can only be applied to the secondary cell.

[0148] For example, the gNB 160 may send tenth information (e.g., the tenth information may be the seventh information) for configuring an index of a serving cell (e.g., a secondary cell) by using an RRC message. Also, the UE 102 may identify the index of the serving cell (e.g., the secondary cell) based on the tenth information. Here, the tenth information may be configured for each serving cell. For example, the tenth information may be configured for each of the primary cell and / or the secondary cell. Additionally or alternatively, the tenth information may be configured only for the secondary cell. That is, the primary cell may not be configured with the tenth information.

[0149] Here, as described above, the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 0 bit, or 1 bit, or 2 bits, or 3 bits. Additionally or alternatively, the gNB 160 may send eleventh information (e.g., the eleventh information may be the eighth information) and twelfth information (e.g., the twelfth information may be the ninth information) by using an RRC message.

[0150] For example, the eleventh information may be used to indicate which serving cells signal DCI format 1_X and / or DCI format 0_Y. That is, the eleventh information may be used to indicate the serving cells for transmitting and / or receiving DCI format 1_X and / or DCI format 0_Y. That is, the eleventh information may be used to indicate the serving cells on which the UE 102 monitors the PDCCH for DCI format 1_X and / or DCI format 0_Y.

[0151] For example, for an active DL BWP of a specific serving cell on which the UE 102 monitors PDCCH candidates (e.g., for DCI format 1_X and / or DCI format 0_Y) in the USS, in a case where the UE 102 is not configured with a carrier indicator (i.e., a carrier indicator field), the UE 102 may monitor PDCCH candidates (for DCI format 1_X and / or DCI format 0_Y) that do not have a carrier indicator (i.e., a carrier indicator field). Additionally or alternatively, for an active DL BWP of a specific serving cell on which the UE 102 monitors PDCCH candidates (e.g., for DCI format 1_X and / or DCI format 0_Y) in the USS, in a case where the UE 102 is configured with a carrier indicator (i.e., a carrier indicator field), the UE 102 may monitor PDCCH candidates (for DCI format 1_X and / or DCI format 0_Y) that have a carrier indicator (i.e., a carrier indicator field).

[0152] For example, the gNB 160 may configure the index of the serving cell (i.e., the serving cell index) as the eleventh information by using an RRC message. For example, as Figure 6As shown, gNB 160 may configure the serving cell index "5" (i.e., the index "5" of a specific serving cell) as the eleventh information. And, when the serving cell index "5" is configured, UE 102 may determine (e.g., recognize) that the serving cell with index "5" is used for transmitting and / or receiving DCI format 1_X and / or DCI format 0_Y. That is, when the serving cell index "5" is configured, UE 102 may monitor the PDCCH of DCI format 1_X and / or DCI format 0_Y on the serving cell with index "5".

[0153] Additionally or alternatively, the twelfth information may be used to indicate the value of the carrier indicator (i.e., the carrier indicator field) used in the scheduling cell to indicate the DCI format 1_X and / or DCI format 0_Y applicable to the serving cell. That is, the twelfth information may be used to indicate the value of the carrier indicator to indicate the DCI format 1_X and / or DCI format 0_Y for scheduling the PDSCH and / or PUSCH of the serving cell (e.g., the PDSCH and / or PUSCH on the serving cell). That is, the twelfth information may be used to indicate the value of the carrier indicator corresponding to the serving cell on which the PDSCH and / or PUSCH is scheduled (e.g., by using DCI format 1_X and / or DCI format 0_Y).

[0154] For example, gNB 160 may configure the value (e.g., 1 or 2,..., or K) as the twelfth information by using an RRC message. Here, as described below, the maximum value (i.e., the K value) of the twelfth information may be determined (e.g., changed) based on the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y.

[0155] For example, as Figure 6As shown, for a serving cell with an index of "3" (i.e., the index of a specific serving cell "3"), the gNB 160 may configure the value "2" as the twelfth piece of information. And, in the case where the value "2" is configured, the UE 102 may determine (e.g., recognize) that the serving cell with the index "3" is scheduled by using the value "2" of the carrier indicator field (e.g., if a 2-bit carrier indicator field is configured, the 2-bit information field "10"). That is, the PDSCH on the serving cell with the index "3" may be scheduled by using the carrier indicator field set to the value "2", and this value is included in DCI format 1_X. Additionally or alternatively, the PDSCH on the serving cell with the index "3" may be scheduled by using the carrier indicator field set to the value "2", and this value is included in DCI format 0_Y. Here, as described above, DCI format 1_X and / or DCI format 0_Y may be transmitted and / or received on the serving cell with the index "5" (i.e., serving cell index "5") based on the eleventh piece of information.

[0156] Here, the second, third, fourth, eleventh, and / or twelfth pieces of information may be configured for each serving cell. That is, the second, third, fourth, eleventh, and / or twelfth pieces of information may be configured for each of the primary cell and / or secondary cells. Additionally or alternatively, the second, third, fourth, eleventh, and / or twelfth pieces of information may be configured only for the secondary cells. That is, the second, third, fourth, eleventh, and / or twelfth pieces of information may not be configured for the primary cell.

[0157] Additionally or alternatively, the second, third, fourth, eleventh, and / or twelfth pieces of information may be configured jointly for DCI format 1_X and DCI format 0_Y. Additionally or alternatively, the second, third, fourth, eleventh, and / or twelfth pieces of information may be configured (e.g., determined separately) separately for DCI format 1_X and DCI format 0_Y.

[0158] Additionally or alternatively, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for each DL BWP. For example, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for each of the DL BWPs. Additionally or alternatively, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for each CORESET. For example, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for each of the CORESETs. Here, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for CORESETs other than CORESET #0. That is, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may not be configured for CORESET #0.

[0159] Additionally or alternatively, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for each search space set. For example, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for each of the search space sets. Here, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may be configured for search space sets other than search space set #0. That is, the second information, the third information, the fourth information, the eleventh information, and / or the twelfth information may not be configured for search space set #0.

[0160] As described above, when there is a carrier indicator in DCI format 1_X and / or DCI format 0_Y, a value (e.g., 1 or 2,..., or K) is configured as the twelfth information. Here, when there is a 3-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y, the maximum value of the twelfth information may be "7 (i.e., K = 7)". Additionally or alternatively, when there is a 2-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y, the maximum value of the twelfth information may be "3 (i.e., K = 3)". Additionally or alternatively, when there is a 1-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y, the maximum value of the twelfth information may be "1 (i.e., K = 1)".

[0161] That is, in the case where a carrier indicator exists in DCI format 1_X and / or DCI format 0_Y, the maximum value (i.e., the K value) can be determined based on the number of bits of the carrier indicator (i.e., included in DCI format 1_X and / or DCI format 0_Y). That is, in the case where a carrier indicator exists in DCI format 1_X and / or DCI format 0_Y, up to "K" serving cells corresponding to the number of bits of the carrier indicator can be scheduled by using DCI format 1_X and / or DCI format 0_Y (e.g., up to "K" serving cells). That is, the maximum number "K" can correspond to the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y.

[0162] Additionally or alternatively, the twelfth information can be configured only when the number of bits of the carrier indicator (i.e., included in DCI format 1_X and / or DCI format 0_Y) is "3". That is, the twelfth information can be configured only for the case where there is a 3-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y. That is, gNB 160 can configure the twelfth information only for the case where there is a 3-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y. That is, for the case where there is a 1-bit and / or 2-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y, gNB 160 may not configure the twelfth information.

[0163] Additionally or alternatively, the twelfth information can be configured only when the number of bits of the carrier indicator (i.e., included in DCI format 1_X and / or DCI format 0_Y) is "2" and / or "3". That is, the twelfth information can be configured only for the case where there are 2-bit and / or 3-bit carrier indicators in DCI format 1_X and / or DCI format 0_Y. That is, gNB 160 can configure the twelfth information only for the case where there are 2-bit and / or 3-bit carrier indicators in DCI format 1_X and / or DCI format 0_Y. That is, for the case where there is a 1-bit carrier indicator in DCI format 1_X and / or DCI format 0_Y, gNB 160 may not configure the twelfth information.

[0164] Additionally or alternatively, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y can be determined based on the number of serving cells having a DL BWP where a CORESET for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is configured. That is, UE 102 can determine the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y based on the number of serving cells having a DL BWP that includes a CORESET configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y.

[0165] For example, when the number of serving cells of a DL BWP having a CORESET configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is "2", the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 1 bit. Additionally or alternatively, when the number of serving cells of a DL BWP having a CORESET configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is "4", the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 2 bits. Additionally or alternatively, when the number of serving cells of a DL BWP having a CORESET configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is "8", the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 3 bits.

[0166] Additionally or alternatively, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be determined based on the number of serving cells of a DL BWP where a search space set for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is configured. That is, UE 102 may determine the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y based on the number of serving cells of a DL BWP that includes a search space set configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y.

[0167] For example, when the number of serving cells of a DL BWP having a search space set configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is "2", the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be 1 bit. Additionally or alternatively, when the number of serving cells of a DL BWP having a search space set configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is 4, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be "2" bits. Additionally or alternatively, when the number of serving cells of a DL BWP having a search space set configured for PDCCH monitoring for DCI format 1_X and / or DCI format 0_Y is 8, the number of bits of the carrier indicator included in DCI format 1_X and / or DCI format 0_Y may be "3" bits.

[0168] As described above, the maximum value of the twelfth information (i.e., the K value) can be determined based on the number of bits of the carrier indicator (i.e., DCI format 1_X and / or DCI format 0_Y). That is, the maximum value of the twelfth information (i.e., the K value) can be determined based on the second information. Additionally or alternatively, the maximum value of the twelfth information (i.e., the K value) can be determined based on the third information (e.g., for DCI format 1_X). Additionally or alternatively, the maximum value of the twelfth information (i.e., the K value) can be determined based on the fourth information (e.g., for DCI format 0_Y). Additionally or alternatively, the maximum value of the twelfth information (i.e., the K value) can be determined based on the number of serving cells having a DL BWP where a CORESET for PDCCH monitoring of DCI format 1_X and / or DCI format 0_Y is configured. Additionally or alternatively, the maximum value of the twelfth information (i.e., the K value) can be determined based on the number of serving cells having a DL BWP where a search space set for PDCCH monitoring of DCI format 1_X and / or DCI format 0_Y is configured.

[0169] Additionally or alternatively, the maximum value of the twelfth information (i.e., the K value) can be determined based on the number of serving cells (e.g., the number of configured serving cells and / or the number of active cells). For example, gNB 160 can send information for configuring serving cells by using an RRC message. And, UE 102 can determine (e.g., recognize) the number of configured serving cells based on the information for configuring serving cells. Additionally or alternatively, gNB 160 can send information for activating serving cells (e.g., within the configured serving cells) by using a MAC CE (e.g., a MAC message). And, UE 102 can determine (e.g., recognize) the number of active serving cells based on the information for activating serving cells.

[0170] Here, the number of serving cells can be the number of serving cells including the primary cell and the secondary cells. Additionally or alternatively, the number of serving cells can be the number of secondary cells. That is, the maximum value of the twelfth information (i.e., the K value) can be determined based on the number of serving cells including the primary cell and the secondary cells. Additionally or alternatively, the maximum value of the twelfth information (i.e., the K value) can be determined based on the number of secondary cells.

[0171] Additionally or alternatively, the maximum value (i.e., the K value) of the twelfth piece of information may be defined (e.g., determined, configured) jointly for DCI format 1_X and DCI format 0_Y. As described above, the number of bits of the carrier indicator may be configured (e.g., determined) jointly for DCI format 1_X and DCI format 0_Y. And based on the number of bits of the carrier indicator configured (e.g., determined, defined) jointly for DCI format 1_X and DCI format 0_Y, the maximum value (i.e., the K value) of the twelfth piece of information may be defined (e.g., determined, configured) jointly for DCI format 1_X and DCI format 0_Y.

[0172] Additionally or alternatively, the maximum value (i.e., the K value) of the twelfth piece of information may be defined (e.g., determined, configured) separately for DCI format 1_X and DCI format 0_Y. As described above, the number of bits of the carrier indicator may be configured (e.g., determined) separately for DCI format 1_X and DCI format 0_Y. And based on the number of bits of the carrier indicator configured (e.g., determined, defined) separately for DCI format 1_X and DCI format 0_Y, the maximum value (i.e., the K value) of the twelfth piece of information may be defined (e.g., determined, configured) separately for DCI format 1_X and DCI format 0_Y.

[0173] Figure 7 Shows various components that can be used in UE 702. In conjunction with Figure 7 The UE 702 described can be implemented according to the UE 102 described in conjunction with Figure 1 The UE 702 includes a processor 703 that controls the operation of the UE 702. The processor 703 may also be referred to as a central processing unit (CPU). A memory 705 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store information) provides instructions 707a and data 709a to the processor 703. A portion of the memory 705 may also include non-volatile random access memory (NVRAM). Instructions 707b and data 709b may also reside in the processor 703. The instructions 707b and / or data 709b loaded into the processor 703 may also include instructions 707a and / or data 709a from the memory 705 that are loaded for execution or processing by the processor 703. The instructions 707b may be executed by the processor 703 to implement the methods described herein.

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

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

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

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

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

[0179] Figure 9 is a block diagram showing an implementation of the UE 902 in which one or more of the systems and / or methods described herein may be implemented. The UE 902 includes a transmitting device 958, a receiving device 920, and a control device 924. The transmitting device 958, the receiving device 920, and the control device 924 may be configured to perform one or more of the functions described in conjunction with the above Figure 1 above Figure 7 shows Figure 9 an example of the specific device structure of Figure 1 One or more of the functions of

[0180] Figure 10 is a block diagram showing an implementation of the gNB 1060 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1060 includes a transmitting device 1017, a receiving device 1078, and a control device 1082. The transmitting device 1017, the receiving device 1078, and the control device 1082 may be configured to perform one or more of the functions described in conjunction with the above Figure 1 above Figure 8 shows Figure 10 an example of the specific device structure of Figure 1 One or more of the functions of

[0181] Figure 11 is a block diagram showing a specific implementation of the gNB 1160. The gNB 1160 may be an example of the gNB160 described in conjunction with Figure 1 above. The gNB 1160 may include a high-layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[0182] The high-layer processor 1123 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 1123 may obtain transport blocks from the physical layer. The high-layer processor 1123 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 1123 may provide a transport block to the PDSCH transmitter and provide transport parameters related to the transport block to the PDCCH transmitter.

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

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

[0185] The higher layer processor 1223 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 1223 can obtain the transport block from the physical layer. The higher layer processor 1223 can send to / obtain from the higher layer of the UE higher layer messages, such as RRC messages and MAC messages. The higher layer processor 1223 can provide the transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0186] The DL receiver 1243 can receive and demultiplex the multiplexed downlink physical channels and downlink physical signals via the receive antenna 1231. The PDCCH receiver 1245 can provide DCI to the higher layer processor 1223. The PDSCH receiver 1247 can provide the received transport block to the higher layer processor 1223.

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

[0188] It should be noted that the names of the physical channels described herein are examples. Other names can be used, such as "NR PDCCH, NR PDSCH, NR PUCCH, and NR PUSCH", "New Generation (G) PDCCH, G PDSCH, G PUCCH, and G PUSCH", etc.

[0189] 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" can 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 can include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or a processor. As used herein, disk and optical disks 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 reproduce data optically using lasers.

[0190] 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 in a chipset, an application specific integrated circuit (ASIC), a large scale integration (LSI), or an integrated circuit, etc., and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integration (LSI), or an integrated circuit, etc.

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

[0192] 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 devices described herein.

[0193] The program running on the gNB 160 or the 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. Additionally, 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.

[0194] Furthermore, in the case where the program is commercially available, the program stored on a portable recording medium can be distributed, or the program can be sent 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. Additionally, some or all of the gNB 160 and the UE 102 according to the system and method described herein can be implemented as an LSI, which is a typical integrated circuit. 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. Furthermore, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block can be implemented using a dedicated circuit or a general-purpose processor. Additionally, if with the continuous progress of semiconductor technology, an integrated circuit technology alternative to LSI emerges, then the integrated circuit applying this technology can also be used.

[0195] Moreover, 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 multiple 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 can be configured by a digital circuit or can be configured by an analog circuit. Additionally, when due to the progress of semiconductor technology, an integrated circuit technology for manufacturing an integrated circuit to replace the current integrated circuit emerges, it is also possible to use the integrated circuit produced by this technology.

[0196] <Cross-reference>

[0197] This non-provisional patent application claims the benefit of priority under 35 U.S.C. § 119 to Provisional Application No. 62 / 864,969, filed on June 21, 2019, the entire content of which is hereby incorporated by reference.

Claims

1. A user equipment UE, comprising: a receiver configured to: receive a radio resource control RRC message, wherein the RRC message includes first information for configuring a search space set for monitoring a physical downlink control channel PDCCH for a first downlink control information DCI format, the first DCI format being used for scheduling a physical downlink shared channel PDSCH; the RRC message includes second information for indicating a value of a carrier indicator field, the value being used in a scheduling cell to indicate the first DCI format applicable to a secondary cell; the RRC message includes third information for indicating whether the first DCI format includes the carrier indicator field; the RRC message includes fourth information for configuring one or more secondary cells to form a serving cell set together with a primary cell; perform reception of the PDSCH on the secondary cell corresponding to the value of the carrier indicator field based on detection of the first DCI format including the carrier indicator field; and a processor configured to determine, based on the third information, that the number of bits of the carrier indicator field in the first DCI format is 0 bit, 1 bit, 2 bits or 3 bits, wherein the first DCI format is one of a plurality of DCI formats, the other DCI formats in the plurality of DCI formats are DCI format 1_0 and DCI format 1_1, each of the plurality of DCI formats is used for PDSCH scheduling, the third information is information specific to the first DCI format in the plurality of DCI formats, and the third information is used to indicate whether the number of bits of the carrier indicator field in the first DCI format is 0 bit, 1 bit, 2 bits or 3 bits.

2. A method performed by a user equipment UE, the method comprising: receiving a radio resource control RRC message, wherein the RRC message includes first information for configuring a search space set for monitoring a physical downlink control channel PDCCH for a first downlink control information DCI format, the first DCI format being used for scheduling a physical downlink shared channel PDSCH; the RRC message includes second information for indicating a value of a carrier indicator field, the value being used in a scheduling cell to indicate the first DCI format applicable to a secondary cell; the RRC message includes third information for indicating whether the first DCI format includes the carrier indicator field; the RRC message includes fourth information for configuring one or more secondary cells to form a serving cell set together with a primary cell; perform reception of the PDSCH on the secondary cell corresponding to the value of the carrier indicator field based on detection of the first DCI format including the carrier indicator field; and Based on the third piece of information, determine that the number of bits of the carrier indicator field in the first DCI format is 0 bit, 1 bit, 2 bits, or 3 bits, where the first DCI format is one of multiple DCI formats, the other DCI formats among the multiple DCI formats are DCI format 1_0 and DCI format 1_1, each of the multiple DCI formats is used for PDSCH scheduling, the third piece of information is information specific to the first DCI format among the multiple DCI formats, and the third piece of information is used to indicate whether the number of bits of the carrier indicator field in the first DCI format is 0 bit, 1 bit, 2 bits, or 3 bits.

3. A base station device, comprising: a transmitter configured to: send a radio resource control (RRC) message to a user equipment (UE), the RRC message includes first information for configuring a search space set for a physical downlink control channel (PDCCH) for monitoring a first downlink control information (DCI) format, and the first DCI format is used for scheduling a physical downlink shared channel (PDSCH); the RRC message includes second information for indicating a value of a carrier indicator field, and the value is used in a scheduling cell to indicate the first DCI format applicable to a secondary cell, the RRC message includes third information for indicating whether the first DCI format includes the carrier indicator field, the RRC message includes fourth information for configuring one or more secondary cells to form a serving cell set together with a primary cell, and send the first DCI format including the carrier indicator field to the UE, such that the UE performs reception of the PDSCH on the secondary cell corresponding to the value of the carrier indicator field based on detection of the first DCI format, where the first DCI format is one of multiple DCI formats, the other DCI formats among the multiple DCI formats are DCI format 1_0 and DCI format 1_1, each of the multiple DCI formats is used for PDSCH scheduling, the third piece of information is information specific to the first DCI format among the multiple DCI formats, and the third piece of information is used to indicate whether the number of bits of the carrier indicator field in the first DCI format is 0 bit, 1 bit, 2 bits, or 3 bits.

Images