阅读说明：本技术 用户设备、基站和方法 (User equipment, base station and method ) 是由 相羽立志 尹占平 于 2018-11-14 设计创作，主要内容包括：本发明描述了在服务小区中的一个或多个下行链路带宽部分(DLBWP)上与基站装置进行通信的用户设备(UE)。接收电路被配置为接收包括第一信息的无线电资源控制(RRC)消息。所述接收电路还被配置为接收包括第二信息的RRC消息。所述接收电路还被配置为基于所述第一信息监视PDCCH。所述接收电路还被配置为在所述PDCCH上接收包括第三信息和第四信息的下行链路控制信息(DCI)格式。传输电路被配置为基于对包括所述第三信息和所述第四信息的所述DCI的检测,在时隙中执行所述PUSCH上的非周期性CSI报告,基于所述第四信息来确定所述时隙。(User Equipment (UE) communicating with a base station apparatus over one or more downlink bandwidth portions (DLBWPs) in a serving cell is described. The receive circuitry is configured to receive a Radio Resource Control (RRC) message including the first information. The receiving circuit is further configured to receive an RRC message including the second information. The receive circuitry is further configured to monitor the PDCCH based on the first information. The receive circuitry is further configured to receive a Downlink Control Information (DCI) format including third information and fourth information on the PDCCH. The transmission circuitry is configured to perform aperiodic CSI reporting on the PUSCH in a slot based on detection of the DCI comprising the third information and the fourth information, the slot being determined based on the fourth information.)

1. A User Equipment (UE) in communication with a base station apparatus on one or more downlink bandwidth portions (DL BWPs) in a serving cell, the UE comprising:

receive circuitry configured to receive a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity,

the receive circuitry is configured to receive an RRC message including second information for configuring more than one offset value,

the receive circuitry is configured to monitor a PDCCH based on the first information,

the receive circuitry is configured to receive, on the PDCCH, a Downlink Control Information (DCI) format comprising third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset value, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH), and

a transmission circuit configured to perform aperiodic CSI reporting on PUSCH in a slot based on detection of the DCI including the third information and the fourth information, the slot being determined based on the fourth information, wherein

The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell, and

the second information is configured for the serving cell.

2. The UE of claim 1, wherein

The receive circuitry is configured to receive an RRC message including fifth information for configuring DCI formats, wherein the UE correspondingly monitors the PDCCH in search spaces, the DCI formats including the DCI format for scheduling the PUSCH and a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH).

3. The UE of claim 1, wherein

The RRC message is a dedicated RRC message.

4. A base station apparatus that communicates with a User Equipment (UE) on one or more downlink bandwidth portions (DLBWPs) in a serving cell, the base station apparatus comprising:

transmit circuitry configured to transmit a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity, the first information used by the UE to monitor the PDCCH,

the transmission circuit is configured to transmit an RRC message including second information for configuring more than one offset value,

the transmission circuitry is configured to transmit, on the PDCCH, a Downlink Control Information (DCI) format including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset values, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH), and

a reception circuit configured to receive an aperiodic CSI report on the PUSCH in a slot based on the transmission of the DCI including the third information and the fourth information, the slot being given based on the fourth information, wherein

The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell, and

the second information is configured for the serving cell.

5. The base station apparatus according to claim 4, wherein

The transmission circuitry is configured to transmit an RRC message including fifth information for configuring DCI formats, wherein the UE correspondingly monitors the PDCCH in search spaces, the DCI formats including the DCI format for scheduling the PUSCH and a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH).

6. The base station apparatus according to claim 4, wherein the base station apparatus

The RRC message is a dedicated RRC message.

7. A communication method of a User Equipment (UE) communicating with a base station apparatus on one or more downlink bandwidth parts (DL BWPs) in a serving cell, the communication method comprising:

receiving a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity,

receiving an RRC message including second information for configuring more than one offset value,

monitoring a PDCCH based on the first information,

receiving a Downlink Control Information (DCI) format on the PDCCH including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset value, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH), and

performing aperiodic CSI reporting on the PUSCH in a slot based on detection of the DCI including the third information and the fourth information, the slot being determined based on the fourth information, wherein

The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell, and

the second information is configured for the serving cell.

8. The communication method according to claim 7, wherein

The receive circuitry is configured to receive an RRC message including fifth information for configuring DCI formats, wherein the UE correspondingly monitors the PDCCH in search spaces, the DCI formats including the DCI format for scheduling the PUSCH and a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH).

9. The communication method according to claim 7, wherein

The RRC message is a dedicated RRC message.

10. A communication method of a base station apparatus that communicates with a User Equipment (UE) on one or more downlink bandwidth parts (DL BWPs) in a serving cell, the communication method comprising:

transmitting a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity, the first information being used by the UE to monitor the PDCCH,

transmitting an RRC message including second information for configuring more than one offset value,

transmitting a Downlink Control Information (DCI) format on the PDCCH including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset values, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH), and

receiving an aperiodic CSI report on the PUSCH in a slot based on the transmission of the DCI including the third information and the fourth information, the slot being given based on the fourth information, wherein

The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell, and

the second information is configured for the serving cell.

11. The communication method according to claim 10, wherein

The transmission circuitry is configured to transmit an RRC message including fifth information for configuring DCI formats, wherein the UE correspondingly monitors the PDCCH in search spaces, the DCI formats including the DCI format for scheduling the PUSCH and a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH).

12. The communication method according to claim 10, wherein

The RRC message is a dedicated RRC message.

Technical Field

The present disclosure relates generally to communication systems. More particularly, the present disclosure relates to new signaling, procedures, User Equipment (UE) and base stations for user equipment, base stations and methods.

Background

Wireless communication devices have become smaller and more powerful in order to meet consumer needs and improve portability and convenience. Consumers have become dependent on wireless communication devices and desire reliable service, expanded coverage areas, and enhanced functionality. A wireless communication system may provide communication for a plurality of wireless communication devices, each of which may be served by a base station. A base station may be a device that communicates with wireless communication devices.

With the development of wireless communication devices, methods of improving communication capacity, speed, flexibility, and/or efficiency are continually being sought. However, improving communication capacity, speed, flexibility, and/or efficiency may present certain problems.

For example, a wireless communication device may communicate with one or more devices using a communication structure. However, the communication structure used may provide only limited flexibility and/or efficiency. As the present discussion illustrates, systems and methods that improve communication flexibility and/or efficiency may be advantageous.

Drawings

Fig. 1 is a block diagram illustrating one particular implementation of one or more base stations (gnbs) and one or more User Equipments (UEs) in which systems and methods for downlink and/or uplink (re) transmission may be implemented;

FIG. 2 illustrates an example of a plurality of parameters;

fig. 3 is a diagram illustrating one example of a resource grid and resource blocks for the downlink and/or uplink;

FIG. 4 illustrates an example of a resource region;

fig. 5 shows an example of downlink and/or uplink transmission;

fig. 6 illustrates another example of downlink and/or uplink transmissions;

fig. 7 shows an example of a Channel State Information (CSI) request field;

FIG. 8 illustrates various components that may be used in a UE;

fig. 9 illustrates various components that may be used in a gNB;

fig. 10 is a block diagram illustrating one particular implementation of a UE in which systems and methods for downlink and/or uplink (re) transmission may be implemented;

fig. 11 is a block diagram illustrating one particular implementation of a gNB in which systems and methods for downlink and/or uplink (re) transmission may be implemented;

fig. 12 is a block diagram illustrating one implementation of a gNB;

fig. 13 is a block diagram illustrating one implementation of a UE;

fig. 14 is a flowchart of a communication method of a User Equipment (UE) communicating with a base station apparatus on one or more downlink bandwidth parts (DL BWPs) in a serving cell; and

fig. 15 is a flowchart illustrating a communication method of a base station apparatus communicating with a User Equipment (UE) on one or more downlink bandwidth parts (DL BWPs) in a serving cell.

Detailed Description

User Equipment (UE) communicating with a base station apparatus over one or more downlink bandwidth portions (DL BWPs) in a serving cell is described. The receive circuitry is configured to receive a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity. The receiving circuit is further configured to receive an RRC message including second information for configuring more than one offset value. The receive circuitry is further configured to monitor the PDCCH based on the first information and receive a Downlink Control Information (DCI) format on the PDCCH including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset value, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH). The transmission circuit is configured to perform aperiodic CSI reporting on PUSCH in a slot based on detection of DCI including third information and fourth information, the slot being determined based on the fourth information. The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell. The second information is configured for a serving cell.

The reception circuitry may be further configured to receive an RRC message including fifth information for configuring a DCI format, wherein the UE monitors the PDCCH in the search space accordingly. The DCI format may include a DCI format for scheduling a PUSCH and a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH). The RRC message may be a dedicated RRC message.

A base station apparatus is described that communicates with User Equipments (UEs) on one or more downlink bandwidth portions (DL BWPs) in a serving cell. The transmission circuitry is configured to transmit a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity, the first information being used by the UE to monitor the PDCCH. The transmission circuit is further configured to transmit an RRC message including second information for configuring more than one offset value. The transmission circuitry is configured to transmit, on the PDCCH, a Downlink Control Information (DCI) format including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset value, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH). The reception circuitry is further configured to receive an aperiodic CSI report on a PUSCH in a slot based on a transmission of DCI including third information and fourth information, the slot being given based on the fourth information. The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell. The second information is configured for a serving cell.

The transmission circuitry may be configured to transmit an RRC message including fifth information for configuring a DCI format, wherein the UE monitors the PDCCH in the search space accordingly. The DCI format may include a DCI format for scheduling a PUSCH and a DCI format for scheduling a Physical Downlink Shared Channel (PDSCH). The RRC message may be a dedicated RRC message.

A communication method of a User Equipment (UE) communicating with a base station apparatus on one or more downlink bandwidth parts (DL BWPs) in a serving cell is described. The method includes receiving a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity. The method also includes receiving an RRC message including second information for configuring more than one offset value. The method also includes monitoring the PDCCH based on the first information. The method also includes receiving, on the PDCCH, a Downlink Control Information (DCI) format including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset values, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH). The method also includes performing aperiodic CSI reporting on PUSCH in a slot based on the detection of DCI including third information and fourth information, the slot being determined based on the fourth information. The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell. The second information is configured for a serving cell.

A communication method of a base station apparatus communicating with a User Equipment (UE) on one or more downlink bandwidth parts (DL BWPs) in a serving cell is described. The method includes transmitting a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity, the first information being used by the UE to monitor the PDCCH. The method also includes transmitting an RRC message including second information for configuring more than one offset value. The method also includes transmitting, on the PDCCH, a Downlink Control Information (DCI) format including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset values, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH). The method also includes receiving an aperiodic CSI report on a PUSCH in a slot based on transmission of DCI including third information and fourth information, the slot being given based on the fourth information. The first information is configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell. The second information is configured for a serving cell.

The 3 rd generation partnership project (also referred to as "3 GPP") is a partnership protocol intended to establish globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems, and devices.

The 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or equipment standard to cope with future demands. In one aspect, UMTS has been modified to provide support and specification for evolved Universal terrestrial radio Access (E-UTRA) and evolved Universal terrestrial radio Access network (E-UTRAN).

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 release 8, 9, 10, 11, and/or 12). However, the scope of the present disclosure should not be limited in this respect. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

A wireless communication device may be an electronic device that communicates voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., the Public Switched Telephone Network (PSTN), the internet, etc.). In describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a subscriber unit, a mobile device, or the like. Examples of wireless communication devices include cellular phones, smart phones, Personal Digital Assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, and so forth. In the 3GPP specifications, the wireless communication device is commonly referred to as a UE. However, as the scope of the present disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device". The UE may also be referred to more generally as a terminal device.

In the 3GPP specifications, a base station is often referred to as a node B, an evolved node B (enb), a home enhanced or evolved node B (henb), or some other similar terminology. As the scope of the present disclosure should not be limited to 3GPP standards, the terms "base station," node B, "" eNB, "" gNB, "and" HeNB "are used interchangeably herein to represent the more general term" base station. Moreover, the term "base station" can be utilized to represent 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 wireless communication devices. The term "communication device" may be used to refer to a wireless communication device and/or a base station. The eNB may also be referred to more generally as a base station device.

It should be noted that as used herein, a "cell" may be any such communication channel: specified by a standardization or regulatory body for Advanced international mobile telecommunications (IMT-Advanced) and all or a subset thereof, to be adopted by 3GPP as a licensed frequency band (e.g., a frequency band) for communication between an eNB and a UE. It should also be noted that in the general description of E-UTRA and E-UTRAN, "cell" may be defined as a "combination of downlink resources and optionally uplink resources" as used herein. The link between the carrier frequency of the downlink resource and the carrier frequency of the uplink resource may be indicated in system information transmitted on the downlink resource.

A fifth generation communication system called NR (new radio technology) by 3GPP envisages the use of time/frequency/space resources to allow services such as eMBB (enhanced mobile broadband) transmission, URLLC (ultra-reliable and low-delay communication) transmission and eMTC (large-scale machine type communication) transmission. In addition, in NR, one or more bandwidth parts (BWPs) may be specified (e.g., configured) for the serving cell. A User Equipment (UE) may receive one or more downlink signals in one or more BWPs of a serving cell. In addition, the UE may transmit one or more uplink signals in one or more BWPs of the serving cell.

In order for a service to efficiently use time, frequency and/or spatial resources, it would be useful to be able to efficiently control downlink and/or uplink transmissions. Therefore, a procedure for efficiently controlling downlink and/or uplink transmission should be designed. However, the detailed design of the procedure for downlink and/or uplink transmission has not been studied.

In some methods, a UE may receive a Radio Resource Control (RRC) message including information for configuring a value of a timer associated with a bandwidth part (BWP). In addition, the UE may perform reception on a Physical Downlink Shared Channel (PDSCH) in BWP based on detection of a Downlink Control Information (DCI) format for the BWP. Here, in case a DCI format for BWP is detected and the value of the timer associated with BWP expires before reception on PDSCH, the value of the timer associated with BWP is increased.

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

Fig. 1 is a block diagram illustrating one particular implementation of one or more gnbs 160 and one or more UEs 102 in which systems and methods for downlink and/or uplink (re) transmission may be implemented. The one or more UEs 102 communicate with one or more gnbs 160 using one or more physical antennas 122 a-n. For example, UE102 transmits electromagnetic signals to gNB160 and receives electromagnetic signals from gNB160 using the one or more physical antennas 122 a-n. The gNB160 communicates with the UE102 using one or more physical antennas 180 a-n. In some implementations, the terms "base station," "eNB," and/or "gNB" may refer to and/or be replaced by the term "Transmission Reception Point (TRP)". For example, in some implementations, the gNB160 described in connection with fig. 1 may be a TRP.

UE102 and gNB160 may communicate with each other using one or more channels and/or one or more signals 119, 121. For example, UE102 may transmit information or data to gNB160 using one or more uplink channels 121. 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)) and the like. For example, one or more gnbs 160 may also transmit information or data to one or more UEs 102 using one or more downlink channels 119. Examples of physical shared channels (e.g., PDSCH (physical downlink shared channel)) and/or physical control channels (PDCCH (physical downlink control channel)) of the downlink channels 119 may use other kinds of channels and/or signals.

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

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

Demodulator 114 may demodulate one or more received signals 116 to produce one or more demodulated signals 112. One or more demodulated signals 112 may be provided to decoder 108. The UE102 may decode the signal using the decoder 108. 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 of the decoded signals 110 (also referred to as second UE decoded signal 110) may include overhead data and/or control data. For example, the second UE decoded signal 110 may provide data that the UE operations module 124 may use to perform one or more operations.

In general, UE operations module 124 may enable UE102 to communicate with one or more gnbs 160. The UE operations module 124 may include one or more of the UE scheduling modules 126.

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

In a radio communication system, physical channels (uplink physical channels and/or downlink physical channels) may be defined. Physical channels (uplink physical channels and/or downlink physical channels) may be used to transport information delivered from higher layers.

For example, in the uplink, a PRACH (physical random access channel) may be defined. For example, PRACH may be used for a random access preamble (e.g., message 1 (msg.1)). In some approaches, the PRACH may be used for initial access connection establishment procedures, handover procedures, connection re-establishment, timing adjustment (e.g., synchronization of uplink transmissions), and/or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink PSCH (e.g., PUSCH) resources).

As another example, a PCCH (physical control channel) may be defined. The PCCH may be used to transmit control information. In the uplink, a PCCH (e.g., a Physical Uplink Control Channel (PUCCH)) is used to transmit Uplink Control Information (UCI). The UCI may include a hybrid automatic repeat request (HARQ-ACK), Channel State Information (CSI), and/or a Scheduling Request (SR). The HARQ-ACK is used to indicate a positive Acknowledgement (ACK) or a Negative Acknowledgement (NACK) of downlink data, e.g., one or more transport blocks, a medium access control protocol data unit (MAC PDU), and/or a downlink shared channel (DL-SCH). The CSI is used to indicate the status of the downlink channel. Here, the CSI reports may be periodic and/or aperiodic. In addition, the SR is used to request resources for uplink data, e.g., one or more transport blocks, MAC PDUs, and/or uplink shared channel (UL-SCH).

Here, the DL-SCH and/or UL-SCH may be a transport channel used in the MAC layer. In addition, a Transport Block (TB) and/or a MAC PDU may be defined as a unit of a transport channel used in the MAC layer. For example, the control, management, and/or processing of HARQ may be performed for each transport block in the MAC layer. A transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver the transport blocks to the physical layer (i.e., the MAC layer delivers the data to the physical layer as transport blocks). In the physical layer, a transport block may be mapped to one or more codewords.

In the downlink, a PCCH (e.g., a Physical Downlink Control Channel (PDCCH)) may be used to transmit Downlink Control Information (DCI). Here, more than one DCI format may be defined (e.g., configured) for DCI transmission on the PCCH. That is, a field may be defined in a DCI format and mapped to information bits (e.g., DCI bits).

For example, DCI format 1A, DCI format 2, and/or DCI format 2A for scheduling one or more downlink physical shared channels in a cell may be defined as DCI formats for downlink. Here, to simplify the description, in some implementations, it may be assumed that DCI format 1, DCI format 1A, DCI format 2, and/or DCI format 2A described herein are included in DCI format a. In addition, DCI format X and/or DCI format Y for scheduling one or more downlink physical channels in a cell may be defined as a DCI format for downlink (e.g., a fallback DCI format). Here, to simplify the description, in some implementations, it may be assumed that DCI format X and/or DCI format Y described herein are included in DCI format B. In addition, DCI formats Z and/or DCI formats K for activating, deactivating, and/or switching one or more serving cells (e.g., one or more secondary cells, one or more downlink secondary cells, and/or one or more secondary downlink component carriers) and/or one or more bandwidth parts (e.g., one or more BWPs, one or more DL BWPs) may be defined as DCI formats for downlink. Here, to simplify the description, in some implementations, it may be assumed that DCI format Z and/or DCI format K described herein are included in DCI format C.

In addition, DCI format 0 and/or DCI format 4 for scheduling one or more uplink physical shared channels in a cell may be defined as a DCI format for uplink. Here, to simplify the description, in some implementations, it may be assumed that DCI format 0 and/or DCI format 4 described herein are included in DCI format D. In addition, DCI format L and/or DCI format M for scheduling one or more uplink physical channels in a cell may be defined as a DCI format for the uplink (e.g., a fallback DCI format). Here, to simplify the description, in some implementations, it may be assumed that DCI format L and/or DCI format M described herein are included in DCI format E. In addition, DCI formats O and/or DCI formats P for activating, deactivating, and/or switching one or more serving cells (e.g., one or more secondary cells, one or more uplink secondary cells, and/or one or more secondary uplink component carriers) and/or one or more bandwidth parts (e.g., one or more BWPs, one or more UL BWPs) may be defined as DCI formats for uplink. Here, to simplify the description, in some implementations, it may be assumed that DCI format O and/or DCI format P described herein are included in DCI format F.

Here, as described above, one or more RNTIs assigned (e.g., by the gNB160) to the UE102 may be used for transmission of DCI (e.g., one or more DCI formats, one or more DL control channels (e.g., one or more PDCCHs)). That is, a CRC (cyclic redundancy check) parity bit (also simply referred to as CRC) generated based on DCI is attached to DCI, and after the attachment, the CRC parity bit is scrambled by one or more RNTIs. The UE102 may attempt to decode (e.g., blind decode, monitor, detect) the DCI to which the CRC parity bits scrambled by the one or more RNTIs are appended. That is, the UE102 detects the DL control channel (e.g., PDCCH, DCI, one or more DCI formats) based on blind decoding. That is, the UE102 may decode one or more DL control channels using a CRC scrambled by one or more RNTIs. In other words, the UE102 may utilize one or more RNTIs to monitor one or more DL control channels. Additionally, as described below, the UE102 may detect one or more DCI formats in the USS (i.e., the CORESET of the USS (i.e., UE-specific search space)) and/or the CSS (i.e., the CORESET of the CSS (i.e., common search space, UE-common search space)). Here, the UE102 may detect one or more DCI formats only in the USS (i.e., USS-only core set). In addition, UE102 may detect one or more DCI formats only in CSS. That is, the UE102 may utilize one or more RNTIs to detect one or more DCI formats.

Here, the one or more RNTIs may include a C-RNTI (cell-RNTI, first C-RNTI), an SPS C-RNTI (semi-persistent scheduling C-RNTI, second C-RNTI), a GF C-RNTI (grant-free C-RNTI), a C-RNTI for one or more fallback DCI formats (e.g., a third C-RNTI for DCI format B and/or DCI format E), a C-RNTI for activating/deactivating/toggling one or more DCI formats (a fourth C-RNTI for DCI format C and/or DCI format F), a SI-RNTI (system information), a P-RNTI (paging RNTI), a RA-RNTI (random access-RNTI), and/or a temporary C-RNTI.

For example, the C-RNTI may be a unique identity used to identify RRC connection and/or scheduling. In addition, the SPS C-RNTI may be a unique identity for semi-persistent scheduling. In addition, the GF C-RNTI may be a unique identity for unlicensed scheduling. Additionally, the C-RNTI for the one or more fallback DCI formats may be a unique identification used by the one or more fallback DCI formats for scheduling. In addition, the C-RNTI used to activate/deactivate/switch one or more DCI formats may be a unique identity used by one or more fallback DCI formats for scheduling. In addition, the SI-RNTI may be used to identify the SI (i.e., SI message) mapped on the BCCH and dynamically carried on the DL-SCH. In addition, the SI-RNTI may be used for broadcasting of the SI. In addition, the P-RNTI may be used to transmit paging and/or SI change notifications. In addition, the RA-RNTI may be an identity used for a random access procedure. In addition, the temporary C-RNTI may be used for a random access procedure.

In addition, for example, a PSCH may be defined. For example, in the case where downlink PSCH resources (e.g., PDSCH resources) are scheduled by using one or more DCI formats, UE102 may receive downlink data on the scheduled downlink PSCH resources (e.g., PDSCH resources). In addition, in the case where uplink PSCH resources (e.g., PUSCH resources) are scheduled by using one or more DCI formats, the UE102 transmits uplink data on the scheduled uplink PSCH resources (e.g., PUSCH resources). That is, the downlink PSCH may be used to transmit downlink data (i.e., DL-SCH, one or more downlink transport blocks). Also, the uplink PSCH may be used to transmit uplink data (i.e., UL-SCH, one or more uplink transport blocks).

Further, the downlink PSCH (e.g., PDSCH) and/or uplink PSCH (e.g., PUSCH) may be used to transmit information of higher layers (e.g., Radio Resource Control (RRC) layer and/or MAC layer). For example, a downlink PSCH (i.e., from gNB160 to UE 102) and/or an uplink PSCH (i.e., from UE102 to gNB160) may be used to transmit RRC messages (RRC signals). In addition, downlink PSCH (i.e., from gNB160 to UE 102) and/or uplink PSCH (i.e., from UE102 to gNB160) may be used to transmit MAC control elements (MAC CEs). Here, the RRC message transmitted in the downlink from the gNB160 is common to a plurality of UEs 102 within the cell (referred to as a common RRC message). In addition, RRC messages transmitted from the gNB160 may be dedicated to a certain UE102 (referred to as dedicated RRC messages). RRC messages and/or MAC CEs are also referred to as higher layer signals.

In some approaches, a downlink PSCH (e.g., PDSCH) may be used to transmit (e.g., notify, specify, identify, etc.) a random access response. For example, a downlink PSCH (e.g., PDSCH) may be scheduled by using a downlink PCH (e.g., PDCCH) with an RA-RNTI (random access RNTI (radio network temporary identifier)). For example, the random access response grant may be used to schedule an uplink PSCH (e.g., PUSCH, message 3 in a random access procedure (e.g., contention-based random access procedure)). Random access response grants may be delivered from higher layers (e.g., the MAC layer) to the physical layer.

In some approaches, a PBCH (physical broadcast channel (e.g., primary PBCH)) may be defined. For example, PBCH may be used to broadcast MIB (master information block). For example, the MIB may be used by multiple UEs 102 and may include system information transmitted on BCH (broadcast channel). In addition, the MIB may include information (e.g., information blocks) for configuring the secondary PBCH. In addition, the MIB may include information (e.g., information blocks) for configuring a downlink PSCH (e.g., PDSCH). For example, PBCH (e.g., MIB) may be used to carry at least information indicating SFN (system frame number).

Here, the system information may be divided into MIB and a plurality of SIBs (one or more system information blocks). The MIB may include a limited amount of the most important and/or most frequently transmitted information (e.g., one or more parameters) needed to obtain other information from the cell. That is, the PBCH (e.g., MIB) may include minimum system information. In addition, one or more SIBs may be carried in the system information message. For example, one or more SIBs may be transmitted on the secondary PBCH and/or the downlink PSCH (e.g., PDSCH). One or more SIBs (e.g., system information block 2 type) may include the least system information remaining (i.e., RMSI). For example, one or more SIBs (e.g., system information block 2 type) may contain radio resource configuration information that is common to multiple UEs 102.

In some approaches, one or more SIBs may contain information for a random access channel configuration (e.g., a random access configuration for a preamble format) used for a random access procedure (e.g., a random access preamble transmission (msg.1 transmission)). For example, the information for the random access configuration may include a preamble format, an SFN, a subframe number (e.g., a subframe number, a slot number, and/or a symbol number). In addition, a part of information for random access configuration may be included in the MIB (e.g., PBCH).

In some methods, in downlink, an SS (synchronization signal) may be defined. An SS may be used to synchronize downlink time-frequency (time and/or frequency) channels. The SS may include PSS (primary synchronization signal). Additionally or alternatively, the SS may include an SSs (secondary synchronization signal). Additionally or alternatively, the SS may include a TSS (third synchronization signal). For example, PSS, SSS, TSS, and/or PBCH may be used to identify physical layer cell identification. Additionally or alternatively, PSS, SSS, TSS, and/or PBCH may be used to identify the identity of one or more beams, one or more TRPs, and/or one or more antenna ports. Additionally or alternatively, PSS, SSS, TSS, and/or PBCH may be used to identify an OFDM symbol index, a slot index in a radio frame, and/or a radio frame number.

In radio communication for uplink, one or more UL RSs may be used as one or more uplink physical signals. The uplink physical signal may not be used to transmit information provided from a higher layer but used by the physical layer. For example, the one or more UL RSs may include one or more demodulation reference signals, one or more UE-specific reference signals, one or more sounding reference signals (one or more SRSs), and/or one or more beam-specific reference signals. The one or more demodulation reference signals may include one or more demodulation reference signals associated with transmission of an uplink physical channel (e.g., PUSCH and/or PUCCH).

Additionally, the one or more UE-specific reference signals may include one or more reference signals associated with transmission of an uplink physical channel (e.g., PUSCH and/or PUCCH). For example, one or more demodulation reference signals and/or one or more UE-specific reference signals may be valid references for demodulating uplink physical channels only when the uplink physical channel transmissions are associated with corresponding antenna ports. The gNB160 may perform (re) configuration of uplink physical channels using one or more demodulation reference signals and/or one or more UE-specific reference signals. The sounding reference signal may be used to measure an uplink channel state.

In addition, in radio communication for downlink, one or more DL RSs may be used as one or more downlink physical signals. The downlink physical signal may not be used to transmit information provided from a higher layer but used by the physical layer. For example, the one or more DL RSs may include one or more cell-specific reference signals, one or more UE-specific reference signals, one or more demodulation reference signals, and/or one or more channel state information reference signals (CSI-RSs). The UE-specific reference signals may include one or more UE-specific reference signals associated with transmission of a downlink physical channel (e.g., PDSCH and/or PDCCH). In addition, the one or more demodulation reference signals may include one or more demodulation reference signals associated with transmission of a downlink physical channel (e.g., PDSCH and/or PDCCH). In addition, the CSI-RS may include one or more non-zero power channel state information reference signals (NZP CSI-RS) and/or zero power channel state information reference signals (ZP CSI-RS).

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

UE operations module 124 may provide information 148 to one or more receivers 120. For example, the UE operations module 124 may notify one or more receivers 120 when to receive the retransmission.

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

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

UE operations module 124 may provide information 142 to encoder 150. Information 142 may include data to be encoded and/or instructions for encoding. For example, UE operations module 124 may instruct encoder 150 to encode transmission data 146 and/or other information 142. Other information 142 may include PDSCH HARQ-ACK information.

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

UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of the modulation type (e.g., constellation mapping) to be used for transmission to 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.

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

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, data buffers 162, and a gNB operations module 182. For example, one or more receive paths and/or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. One or more receivers 178 may receive signals from UE102 using one or more physical antennas 180 a-n. For example, receiver 178 may receive and down-convert a signal to generate one or more received signals 174. The one or more received signals 174 may be provided to a demodulator 172. One or more transmitters 117 may transmit signals to UE102 using one or more physical antennas 180 a-n. For example, one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

Demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. One or more demodulated signals 170 may be provided to decoder 166. The gNB160 may use the decoder 166 to decode the signal. 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.

In general, the gNB operations module 182 may enable the gNB160 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.

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

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

The gNB operation module 182 may provide the information 101 to the encoder 109. 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 information 101, which includes the transmission data 105.

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

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

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

It should be noted that DL subframes may be transmitted from gNB160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to gNB 160. Further, the gNB160 and one or more UEs 102 may each transmit data in standard special subframes.

It should also be noted that one or more of the elements or components thereof included in one or more enbs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, or a hardware component, among others. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or implemented using a chipset, an Application Specific Integrated Circuit (ASIC), a large scale integrated circuit (ESI), an integrated circuit, or the like.

Fig. 2 shows an example of a number of parameters. As shown in fig. 2, a variety of parameters (i.e., a plurality of subcarrier spacings) may be supported. For example, μ (e.g., subcarrier space configuration) and cyclic prefix (e.g., μ and cyclic prefix of a carrier bandwidth portion) may be configured by higher layer parameters for downlink and/or uplink (i.e., RRC messages). Here, 15kHz may be a reference parameter. For example, the RE of the reference parameter may be defined to have a subcarrier spacing of 15kHz in the frequency domain and a 2048Ts + CP length (e.g., 160Ts or 144Ts) in the time domain, where Ts represents a baseband sampling time unit defined as 1/(15000 x 2048) seconds.

In addition, each time slot may be determined based on μ (e.g., subcarrier spacing configuration)The number of one or more OFDM symbols. Here, for example, a slot configuration of 0 (i.e., the number of OFDM symbols per slot may be 14) and/or a slot configuration (i.e., the number of OFDM symbols per slot may be 7) may be defined.

Fig. 3 is a diagram illustrating one example of a resource grid and resource blocks (e.g., for the downlink and/or uplink). The resource grid shown in fig. 3 may be used in some implementations of the systems and methods disclosed herein.

In fig. 3, one subframe may includeAnd (4) a symbol. In addition, a resource block may include a plurality of Resource Elements (REs). Here, in downlink, an OFDM access scheme with a Cyclic Prefix (CP), which may also be referred to as CP-OFDM, may be employed. The downlink radio frame may include multiple pairs of downlink Resource Blocks (RBs), which are also referred to as Physical Resource Blocks (PRBs). The downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a slot. The downlink RB pair may include two downlink RBs consecutive in a time domain. And, the downlink RB may include twelve subcarriers in the frequency domain and seven (for the normal CP) or six (for the extended CP) OFDM symbols in the time domain. A region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a Resource Element (RE) and is uniquely identified by an index pair (k, l), where k and l are indexes in the frequency domain and the time domain, respectively.

In addition, in the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme, also referred to as discrete Fourier transform spread OFDM (DFT-S-OFDM), may be employed. The uplink radio frame may include multiple pairs of uplink resource blocks. The uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and slots. The uplink RB pair may include two uplink RBs consecutive in a time domain. The uplink RB may include twelve subcarriers in the frequency domain to provide seven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in the time domain. A region defined by one subcarrier in the frequency domain and one OFDM/DFT-S-OFDM symbol in the time domain is called a Resource Element (RE) and is uniquely identified by an index pair (k, l) in a slot, where k and l are indexes in the frequency domain and the time domain, respectively.

Each element and subcarrier configuration μ in a resource grid (e.g., antenna port p) is referred to as a resource element and is uniquely identified by an index pair (k, l), whereIs an index in the frequency domain and/refers to a symbol position in the time domain. The resource element (k, l) and subcarrier spacing configuration μ on antenna port p is denoted as (k, l)_p,μ. Physical resource blocks are defined as in the frequency domainConsecutive subcarriers. Physical resource blocks from 0 toAnd (6) numbering. Physical resource block numbers in the frequency domainⁿThe relationship between PRBs and resource elements (k, l) is given by:

fig. 4 shows an example of a resource region (e.g., a resource region for the downlink). One or more PRB sets (e.g., control resource sets (i.e., CORESET)) may be configured for DL control channel monitoring (e.g., PDCCH monitoring). For example, a control resource set (e.g., CORESET) is a set of PRBs in the frequency and/or time domain within which the UE102 attempts to decode DCI (e.g., one or more DCI formats, one or more PDCCHs), where a PRB may or may not be frequency-contiguous and/or time-contiguous, the UE102 may be configured with one or more control resource sets (i.e., CORESET), and one DCI message may be mapped within one control resource set. In the frequency domain, a PRB is a resource unit size of a DL control channel (which may or may not include a DM-RS). The DL shared channel may start at a later OFDM symbol than the one or more symbols carrying the detected DL control channel. Alternatively, the DL shared channel may start at the last OFDM symbol carrying the detected DL control channel (or at an earlier symbol than the last OFDM symbol). In other words, dynamic reuse of at least a portion of resources in a control resource set for data of the same or different UEs 102, at least in the frequency domain, may be supported.

UE102 may monitor a candidate set of one or more DL control channels in a control resource set (i.e., CORESET). Here, the candidates for the one or more DL control channels may be candidates for possible mapping, allocation and/or transmission of the one or more DL control channels. For example, the one or more DL control channel candidates are composed of one or more Control Channel Elements (CCEs). Here, the term "monitoring" means that the UE102 attempts to decode each DL control channel in the candidate set of one or more DL control channels according to all DCI formats to be monitored.

The candidate set of one or more DL control channels (e.g., CORESET) monitored by the UE102 may also be referred to as a search space (e.g., a set of DL control channels, etc.). That is, the search space is a set of resources (e.g., CORESET) that may be available for transmission of one or more DL control channels. UE102 may monitor a candidate set of one or more DL control channels in a control resource set (i.e., CORESET) according to the search space, where monitoring means attempting to detect each DL control channel candidate in the control resource set (i.e., CORESET) according to the monitored DCI format. That is, a set of control resources (i.e., CORESET) may be used for scheduling of PDSCH. In addition, the set of control resources may be used for scheduling of PUSCH.

Here, a common search space (CSS, UE-common search space) and/or a user equipment-specific search space (USS, UE-specific search space) is set (or defined, configured) in one or more regions (e.g., DL control channel monitoring region, CORESET) of one or more DL control channels. For example, CSS may be used to transmit DCI to multiple UEs 102. That is, the CSS may be defined by resources that are common to multiple UEs 102. For example, CSS consists of having a predetermined number of CCEs between gNB160 and UE 102. For example, the CSS is composed of CCEs with indices of 0 to 15. In addition, the gNB160 may configure (by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages) CSS (e.g., region of CSS, control resource set of CSS). Additionally, the gNB160 may transmit one or more DCI formats in CSS to multiple UEs 102. The candidate set of one or more DL control channels monitored by the UE102 may be defined according to the DL control channel CSS. The DL control channels CSS of a CCE aggregation level may be defined by a candidate set of one or more DL control channels.

Here, CSS may be used to transmit DCI to a particular UE 102. That is, the gNB160 may transmit one or more DCI formats intended for multiple UEs 102 and/or one or more DCI formats for a particular UE102 in the CSS.

The USS may be used to transmit DCI to a particular UE 102. That is, USS is defined by resources dedicated to a certain UE 102. The USS may be defined independently for each UE 102. For example, the USS may consist of CCEs having a number determined based on a Radio Network Temporary Identifier (RNTI) (e.g., C-RNTI), a slot number in a radio frame, an aggregation level, and the like. One or more RNTIs may be allocated by the gNB 160. That is, each of the USSs corresponding to each of one or more RNTIs described below may be defined. In addition, for example, the gNB160 may configure (using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages) USS (e.g., region of USS, control resource set of USS). In addition, the gNB160 may transmit one or more DCI formats intended for a particular UE102 in the USS. The candidate set of one or more DL control channels that the UE102 monitors may be defined in terms of DL control channels USS. The DL control channel USS of a CCE aggregation level may be defined by a candidate set of one or more DL control channels.

That is, in CORESET (e.g., in a given CORESET), at least two types of search spaces, i.e., CSS and USS (e.g., CSS set and USS set), may be configured for UE 102. For example, the gNB160 may transmit (using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages) information for configuring one or more control resource sets (i.e., one or more CORESET) of the CSS. In addition, the gNB160 may transmit (using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages) information for configuring one or more control resource sets (i.e., one or more CORESET) of the USS. In addition, for example, the gNB160 may transmit information for configuring one or more occasions for one or more DL control channel monitoring (control resource set monitoring). Here, the one or more DL control channels may be one or more PCCHs (e.g., one or more PDCCHs). Additionally, the one or more occasions may correspond to a subframe, a slot, a sub-slot, and/or a symbol. That is, one or more occasions may correspond to one or more locations (e.g., timing, time resources, time locations, time indices, indices of one or more subframes, one or more slots, one or more sub-slots, and/or one or more symbols). Additionally, for example, the one or more occasions may correspond to a periodicity at which the UE102 monitors the PDCCH (e.g., a periodicity of a subframe, slot, sub-slot, and/or symbol). That is, the gNB160 may configure the UE102 with periodicity for monitoring PDCCH (i.e., PDCCH monitoring periodicity, one or more PDCCH monitoring occasions).

For example, the gNB160 may transmit information for configuring one or more occasions (i.e., PDCCH monitoring periodicity, one or more PDCCH monitoring occasions), e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type (i.e., RMSI)), and/or dedicated RRC messages. Also, the UE102 may monitor the PDCCH based on information for configuring one or more occasions.

Here, information for configuring one or more occasions may be configured for each serving cell. That is, the information for configuring the one or more occasions may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring one or more occasions may be configured for each BWP (e.g., each BWP in the serving cell). That is, information for configuring one or more occasions may be configured for each BWP in the serving cell. In addition, information for configuring one or more occasions may be configured for each DCI format. For example, information for configuring one or more occasions may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). Here, for example, the gNB160 may transmit information for configuring one or more occasions for DCI format B and/or DCI format E, e.g., by using PBCH (e.g., MIB) and/or PDSCH (e.g., SIB2 type (i.e., RMSI)). That is, PBCH (e.g., MIB) and/or PDSCH (e.g., SIB2 type (i.e., RMSI)) may be used to configure one or more occasions for DCI format B and/or DCI format E. Additionally, the gNB160 may transmit information for configuring one or more occasions for DCI format A, DCI format C, DCI format D and/or DCI format F, e.g., by using a dedicated RRC message. That is, the dedicated RRC message may be used to configure one or more occasions for DCI format A, DCI format C, DCI format D and/or DCI format F. In addition, information for configuring one or more occasions may be configured for each search space (e.g., CSS and/or USS). For example, information for configuring one or more occasions may be configured for each type of search space. For example, in CORESET (e.g., in a given CORESET), each of the opportunities (e.g., different periodicities) may be configured (e.g., independently configured) for each type of search space (e.g., CSS and/or USS). In addition, the gNB160 may configure one or more DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F) where the UE102 monitors in each type of search space (e.g., CSS and/or USS). For example, each of the occasions (e.g., different periodicities) may be configured (e.g., independently configured) for each of one or more DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F). In addition, information for configuring one or more occasions may be configured for each RNTI. For example, information for configuring the occasion may be configured for each RNTI (e.g., C-RNTI (first C-RNTI), SPS C-RNTI (second C-RNTI), C-RNTI for one or more fallback DCI formats, GF C-RNTI, SI-RNTI, P-RNTI, RA-RNTI, and/or temporary C-RNTI). For example, each of the occasions may be configured (e.g., independently configured) for each of the RNTIs (e.g., C-RNTI (first C-RNTI), SPS C-RNTI (second C-RNTI), C-RNTI for one or more fallback DCI formats, GF C-RNTI, SI-RNTI, P-RNTI, RA-RNTI, and/or temporary C-RNTI). That is, the information for configuring the one or more occasions may be configured for each of the serving cells, each of the BWPs, each of the DCI formats, each of the search spaces (e.g., CSS and/or USS), and/or each of the RNTIs.

Here, a search space (e.g., CSS and/or USS (e.g., set of CSSs and/or USSs)) may be defined based on a number of PDCCH candidates for each aggregation level (e.g., 1, 2, 4, 8, 16), one or more PDCCH monitoring occasions for a set of one or more search spaces, and/or each search space set associated with CORESET. For example, the gNB160 may configure the number of PDCCH candidates for each aggregation level. In addition, the gNB160 may configure one or more PDCCH monitoring occasions for a set of one or more search spaces. In addition, the gNB160 may configure each set of search spaces associated with the CORESET. That is, for example, an index of a search space may be defined (e.g., calculated) based on a number of PDCCH candidates for each aggregation level (e.g., 1, 2, 4, 8, 16), one or more PDCCH monitoring occasions for a set of one or more search spaces, and/or each search space set associated with CORESET.

As described above, for example, DCI format 1A, DCI format 2, and/or DCI format 2A for scheduling one or more downlink physical shared channels in a cell may be defined as DCI formats for downlink. For example, DCI format 1 and/or DCI format 1A may be used to schedule one downlink physical shared channel (e.g., transmission of one PDSCH, one PDSCH codeword, one downlink transport block) in a cell. In addition, DCI format 2 and/or DCI format 2A may be used to schedule one downlink physical shared channel (e.g., transmission of one PDSCH, at most two PDSCH codewords, at most two downlink transport blocks). Here, to simplify the description, in some implementations, it may be assumed that DCI format 1, DCI format 1A, DCI format 2, and/or DCI format 2A described herein are included in DCI format a. As described above, DCI format a may be used to schedule a downlink PSCH (e.g., PDSCH). That is, DCI format a may be a scheduling DCI. In addition, the downlink PSCH (e.g., PDSCH) may be scheduled using a set of control resources (i.e., CORESET) in which the search spaces (e.g., UE-specific search spaces, common search spaces, and/or PDCCH) of DCI format a are monitored.

Here, DCI format a may be used to activate and/or deactivate one or more serving cells (e.g., one or more secondary cells, one or more downlink secondary cells, and/or one or more secondary downlink component carriers), as described below. In addition, DCI format a may be used to activate and/or deactivate one or more bandwidth parts (e.g., one or more BWPs in one or more serving cells, one or more DL BWPs in one or more serving cells). In addition, C-RNTI (i.e., first C-RNTI), SPS C-RNTI (i.e., second C-RNTI), and/or GF C-RNTI may be used for transmission of DCI format A. That is, the UE102 may decode (detect, monitor) the DCI format a to which CRC parity bits scrambled by the C-RNTI and/or SPS C-RNTI are appended.

For example, DCI format a may include resource block allocation information (i.e., resource allocation information, one or more resource block allocation fields). That is, DCI format a may include information indicating one or more physical resource blocks of the PDSCH (e.g., an index of the one or more physical resource blocks, a size of the one or more physical resource blocks). In addition, the DCI format a may include information indicating a modulation and coding scheme (i.e., MCS information, one or more MCS fields). In addition, DCI format a may include information (i.e., a flag, an identifier for one or more DCI format distinctions) for identifying a DCI format among a plurality of DCI formats having the same DCI size (i.e., the same DCI format size). For example, for multiple DCI formats of the same DCI size with the same RNTI, this information (i.e., flags, identifiers for one or more DCI format distinctions) may be included in the corresponding DCI format (e.g., DCI format a, DCI format B described below, DCI format C described below, DCI format D described below, DCI format E described below, and/or DCI format F described below) to distinguish the multiple DCI formats (i.e., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F). In addition, DCI format a may include information (e.g., a new data indicator) indicating whether the transmission is a new transmission (e.g., whether the transmission is a new transmission or a retransmission). In addition, DCI format a may include information (i.e., CSI request, one or more CSI request fields)) for requesting transmission of CSI (i.e., CSI report, aperiodic CSI report (i.e., aperiodic CSI reporting)) on PUSCH and/or PUCCH. In addition, DCI format a may include information (e.g., one or more 3-bit information fields, carrier indicators and/or BWP indicators, carrier and/or BWP indicators, one or more carrier indicator fields and/or one or more BWP indicator fields, carrier and/or one or more BWP indicator fields) for indicating a serving cell (e.g., carrier) and/or BWP. That is, DCI format a may include information (e.g., one or more 3-bit information fields, a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PDSCH is scheduled). In addition, DCI format a may include information (e.g., one or more 3-bit information fields, a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PDSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell. In addition, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more BWPs in which the PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more BWPs may be used to indicate an initial active BWP (e.g., an initial active DL BWP) and/or a default BWP (e.g., a default DL BWP). In addition, DCI format a may include information (e.g., one or more 3-bit information fields, a carrier, and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PDSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells and one or more BWPs may be used to indicate a primary cell and an initial active DL BWP (or a default DL BWP). In addition, DCI format a may include information (SRS request, one or more SRS request fields) for requesting transmission of SRS (i.e., aperiodic SRS transmission). In addition, the DCI format a may include information indicating a Transmission Power Control (TPC) command for the PCCH (e.g., a TPC command field for the PUCCH).

In addition, DCI format X and/or DCI format Y for scheduling one or more downlink physical channels in a cell may be defined as a DCI format for downlink (e.g., a fallback DCI format). For example, DCI format X and/or DCI format Y may be used to schedule one downlink physical shared channel (e.g., transmission of one PDSCH, one PDSCH codeword, one downlink transport block). Here, to simplify the description, in some implementations, it may be assumed that DCI format X and/or DCI format Y described herein are included in DCI format B. As described above, DCI format B may be used to schedule a downlink PSCH (e.g., PDSCH). That is, DCI format B may be a scheduling DCI. In addition, the downlink PSCH (e.g., PDSCH) may be scheduled using a set of control resources (i.e., CORESET) in which the search spaces (e.g., UE-specific search spaces, common search spaces, and/or PDCCH) of DCI format B are monitored.

Here, DCI format B may be used to activate and/or deactivate one or more serving cells (e.g., one or more secondary cells, one or more uplink secondary cells, and/or one or more uplink component carriers), as described below. In addition, DCI format B may be used to activate and/or deactivate one or more bandwidth parts (e.g., one or more BWPs in one or more serving cells, one or more DL BWPs in one or more serving cells). In addition, C-RNTI (i.e., first C-RNTI), SPS C-RNTI (i.e., second C-RNTI), and/or GF C-RNTI may be used for transmission of DCI Format B. That is, the UE102 may decode (detect, monitor) the DCI format B to which CRC parity bits scrambled by the C-RNTI (i.e., the first C-RNTI), the SPS C-RNTI (i.e., the second C-RNTI), and/or the GFC-RNTI are appended. Here, a C-RNTI (i.e., a third C-RNTI, e.g., a C-RNTI for a fallback DCI format), an SPS C-RNTI (i.e., a second C-RNTI), and a GF C-RNTI that is different from the C-RNTI (i.e., the first C-RNTI) may be used for transmission of DCI format B. That is, the UE102 may decode (detect, monitor) the DCI format B to which the CRC parity bits scrambled by the third C-RNTI are appended.

For example, DCI format B may include resource block allocation information (i.e., resource allocation information, one or more resource block allocation fields). That is, DCI format B may include information indicating one or more physical resource blocks of the PDSCH (e.g., an index of the one or more physical resource blocks, a size of the one or more physical resource blocks). In addition, DCI format B may include information indicating a modulation and coding scheme (i.e., MCS information, one or more MCS fields). In addition, DCI format B may include information (i.e., flags, identifiers for one or more DCI format distinctions) for identifying a DCI format among a plurality of DCI formats having the same DCI size (i.e., the same DCI format size). For example, for multiple DCI formats of the same DCI size with the same RNTI, this information (i.e., flags, identifiers for one or more DCI format distinctions) may be included in the corresponding DCI format (e.g., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F) to distinguish the multiple DCI formats (i.e., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F). In addition, DCI format B may include information (e.g., a new data indicator) indicating whether the transmission is a new transmission (e.g., whether the transmission is a new transmission or a retransmission). In addition, DCI format B may include information (i.e., CSI request, one or more CSI request fields)) for requesting transmission of CSI (i.e., CSI report, aperiodic CSI report (i.e., aperiodic CSI reporting)) on PUSCH and/or PUCCH. In addition, DCI format B may include information (e.g., one or more 3-bit information fields, carrier indicators and/or BWP indicators, carrier and/or BWP indicators, one or more carrier indicator fields and/or one or more BWP indicator fields, carrier and/or one or more BWP indicator fields) for indicating a serving cell (e.g., carrier) and/or BWP. That is, DCI format B may include information (e.g., one or more 3-bit information fields, a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PDSCH is scheduled). In addition, DCI format B may include information (e.g., one or more 3-bit information fields, a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PDSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell. In addition, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more BWPs in which the PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more BWPs may be used to indicate an initial active BWP (e.g., an initial active DL BWP) and/or a default BWP (e.g., a default DL BWP). In addition, DCI format B may include information (i.e., a carrier and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PDSCH is scheduled). Here, for example, in case that information (e.g., one or more 3-bit information fields) indicating one or more serving cells and one or more BWPs is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell and an initial active DL BWP (or a default DL BWP). In addition, DCI format B may include information (SRS request, one or more SRS request fields) for requesting transmission of SRS (i.e., aperiodic SRS transmission). In addition, DCI format B may include information indicating a Transmit Power Control (TPC) command for a PCCH (e.g., a TPC command field for a PUCCH).

Here, DCI format B may not include information indicating a serving cell (e.g., carrier) and/or BWP (i.e., a carrier indicator and/or BWP indicator, a carrier and/or BWP indicator, one or more carrier indicator fields and/or one or more BWP indicator fields, a carrier and/or one or more BWP indicator fields). That is, DCI format B may not include information (i.e., a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PDSCH is scheduled). In addition, DCI format B may not include information (i.e., a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PDSCH is scheduled). In addition, DCI format B may not include information (i.e., a carrier and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PDSCH is scheduled).

In addition, DCI format B may be used to schedule a PDSCH smaller in size than the size of a PDSCH scheduled by using DCI format a. That is, for example, DCI format B may be used to schedule a PDSCH with a narrower bandwidth than a PDSCH scheduled by using DCI format a. For example, the number of one or more PRBs allocated by using DCI format a (e.g., total number of allocated one or more PRBs of PDSCH, N_PRB) May be 100(PRB), 110(PRB), 270(PRB), 273(PRB), and/or 276 (PRB). Here, 100(PRB) may correspond to 20MHz, 110(PRB) may correspond to 20MHz, 270(PRB) may correspond to 50MHz, 273(PRB) may correspond to 100MHz, and/or 276(PRB) may correspond to 100 MHz. That is, the maximum number of one or more PRBs allocated by using DCI format a may be 100(PRB), 110(PRB), 270(PRB), 273(PRB), and/or 276 (PRB). Also, DCI format a may be used to schedule PDSCH of up to 100(PRB), 110(PRB), 270(PRB), 273(PRB), and/or 276 (PRB). In addition, the number of one or more PRBs allocated by using DCI format B may be 6(PRB), 24(PRB), 25(PRB), 50(PRB), and/or 52 (PRB). Here, 6(PRB) may correspond to 1.4MHz, 25(PRB) may correspond to 5MHz, 50(PRB) may correspond to 10MHz, and/or 52(PRB) may correspond to 10 MHz. In addition, 24 (PRBs) may correspond to a bandwidth for PSS, SSS, and/or PBCH (e.g., one or more SS blocks). In addition, 24(PRB) may correspond to a bandwidth for RMSI (e.g., SIB2) and CORESET including PDCCH scheduling RMSI. That is, DCI format B may be used to schedule a PDSCH of a bandwidth corresponding to (e.g., the same as) a bandwidth in which a random access procedure is performed.

That is, the maximum number of one or more PRBs allocated by using DCI format B may be 6(PRB), 24(PRB), 25(PRB), 50(PRB), and/or 52 (PRB). And, DCI format B may be used to schedule PDSCH of at most 6(PRB), 24(PRB), 25(PRB), 50(PRB), and/or 52 (PRB). That is, for example, one or more transport blocks having a larger size (i.e., a larger number) may be transmitted on the PUSCH scheduled by using DCI format a than the size (i.e., the number) of one or more transport blocks transmitted on the PDSCH scheduled by using DCI format B. That is, for example, one or more transport blocks having a smaller size may be transmitted on a PDSCH scheduled by using DCI format B than the size of one or more transport blocks transmitted on a PDSCH scheduled by using DCI format a. For example, a first table for determining the size of one or more transport blocks may be defined (e.g., specified) for DCI format a. In addition, a second table (i.e., a second table different from the first table) for determining the size of one or more transport blocks may be defined (e.g., specified) for DCI format B. Also, the maximum size (i.e., the maximum number) of the one or more transport blocks for DCI format a (i.e., the maximum size of the one or more transport blocks transmitted on the PDSCH scheduled by using DCI format a) may be greater than the maximum size (i.e., the maximum number) of the one or more transport blocks for DCI format B (i.e., the maximum size of the one or more transport blocks transmitted on the PUSCH scheduled by using DCI format B).

Here, the number of allocated one or more PRBs (i.e., the maximum number of allocated one or more PRBs) may depend on each of a plurality of parameters (i.e., multi-subcarrier spacing). That is, for a certain parameter (i.e., a given parameter, a configured parameter), as described above, the number of allocated one or more PRBs that can be scheduled by using DCI format B is smaller than the number of allocated one or more PRBs that can be scheduled by using DCI format a. In addition, the number of one or more PRBs allocated by using DCI format B (i.e., the maximum number of allocated one or more PRBs) may be determined based on the bandwidth of the default DL BWP (e.g., the number of one or more PRBs of the default DL BWP). For example, the gNB160 may configure the bandwidth of the default DL BWP (e.g., the number of one or more PRBs of the default DL BWP), e.g., by using RRC messages. In addition, the number of one or more PRBs allocated by using the DCI format B (i.e., the maximum number of allocated one or more PRBs) may be determined based on a bandwidth of the active DL BWP (e.g., an initial active DL BWP, the number of one or more PRBs of the initial active DL BWP; an active DL BWP, the number of one or more PRBs of the active DL BWP). For example, gNB160 may configure the bandwidth of the active DL BWP (e.g., the initial active DL BWP, number of one or more PRBs of the initial active DL BWP; the active DL BWP, number of one or more PRBs of the active DL BWP), e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. In addition, the gNB160 may configure the bandwidth of the RMSI core, e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. And, the bandwidth of the active DL BWP (e.g., the number of the initial active DL BWP, the one or more PRBs of the initial active DL BWP; the number of the activated DL BWP, the one or more PRBs of the activated DL BWP) may be determined based on (e.g., the same as) the bandwidth of the RMSI core set. Here, the initial active DL BWP is defined as the frequency location and bandwidth of the RMSI CORESET and the parameters of the RMSI (i.e., the RMSI CORESET, e.g., the parameters for transmitting the PDSCH of the RMSI (e.g., SIB 2)).

In addition, for example, the parameter of the PDSCH scheduled by using DCI format a may be 15kHz (e.g., a first parameter), 30kHz (e.g., a second parameter), and/or 60kHz (e.g., a third parameter). That is, DCI format a may be used to schedule PDSCH of various parameters (i.e., first, second, and/or third parameters). In addition, the parameter of the PDSCH scheduled by using DCI format B may be 15kHz (e.g., a first parameter), 30kHz (e.g., a second parameter), and/or 60kHz (e.g., a third parameter). That is, DCI format B may be used to schedule PDSCH of various parameters (i.e., first, second, and/or third parameters). Here, for example, the parameter of the PDSCH scheduled by using DCI format B may be only one of 15kHz (i.e., a first parameter), 30kHz (i.e., a second parameter), and 60kHz (i.e., a third parameter). For example, only 15kHz SCS is available for PDSCH scheduled by using DCI format B. Here, parameters for PDSCH scheduled by using DCI format B may be specified in advance through specifications and known information between the gNB160 and the UE 102. That is, upon receiving (e.g., detecting) DCI format B, UE102 may assume 15kHz SCS (e.g., first parameter) for the scheduled PDSCH. Also, the UE102 may perform (e.g., decode, detect) PDSCH reception based on 15kHz SCS (e.g., assumption of PDSCH based on 15kHz SCS (e.g., first parameter) even if 30kHz SCS (e.g., second parameter) and/or 60kHz SCS (e.g., third parameter) is configured).

In addition, the parameter of the PDSCH scheduled by using DCI format B may be determined based on the parameter of the default DL BWP. For example, the gNB160 may configure the parameters of the default DL BWP, e.g., by using RRC messages. In addition, parameters of PDSCH scheduled by using DCI format B may be determined based on parameters of active DL BWP (e.g., initial active DL BWP, activated DL BWP). For example, the gNB160 may configure parameters of the active DL BWP (e.g., initial active DL BWP, active DL BWP), e.g., by using RRC messages. In addition, the gNB160 may configure parameters of RMSI core, for example, by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. Also, parameters of the active DL BWP (e.g., initial active DL BWP, active DL BWP) may be determined based on (e.g., same as) the parameters of the RMSI CORESET. That is, the parameter of the PDSCH scheduled by using DCI format B may be determined based on the parameter of the RMSICORESET. Additionally, the gNB160 may configure parameters for RMSI (e.g., PDSCH for transmitting RMSI), msg.2 (e.g., PDSCH for transmitting msg.2 in a random access procedure), and/or msg.4 (e.g., PDSCH for transmitting msg.4 in a random access procedure), e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. Also, parameters of the active DL BWP (e.g., initial active DL BWP, active DL BWP) may be determined based on (e.g., the same as) the parameters for RMSI, msg.2, and/or msg.4. That is, the parameters of the PDSCH scheduled by using DCI format B may be determined based on the parameters for RMSI, msg.2, and/or msg.4.

In addition, DCI formats Z and/or DCI formats K used to activate, deactivate, and/or handover one or more serving cells (e.g., one or more secondary cells, one or more downlink secondary cells, and/or one or more secondary downlink component carriers) may be defined as DCI formats for downlink. Here, DCI format Z and/or DCI format K may be used to activate, deactivate, and/or handover one or more BWPs (e.g., one or more BWPs in one or more serving cells, one or more DL BWPs in one or more serving cells). That is, DCI format Z and/or DCI format K are used to activate, deactivate, and/or handover one or more serving cells and/or one or more BWPs. Here, to simplify the description, in some implementations, it may be assumed that DCI format Z and/or DCI format K described herein are included in DCI format C. As described above, DCI format C may be used to activate, deactivate, and/or handover one or more serving cells and/or one or more BWPs. That is, DCI format B may be an activation/deactivation/handover DCI. In addition, one or more serving cells and/or one or more BWPs may be activated, deactivated, and/or handed over using a control resource set (i.e., CORESET) in which a search space (e.g., UE-specific search space, common search space, and/or PDCCH) of DCI format C is monitored.

Here, C-RNTI (i.e., first C-RNTI), SPS C-RNTI (i.e., second C-RNTI), and/or GF C-RNTI may be used for transmission of DCI format C. That is, the UE102 may decode (detect, monitor) the DCI format C to which CRC parity bits scrambled by the C-RNTI (i.e., first C-RNTI), SPSC-RNTI (i.e., second C-RNTI), and/or GF C-RNTI are appended. Here, a C-RNTI (i.e., a fourth C-RNTI, e.g., a C-RNTI for activating/deactivating/switching DCI formats) different from the C-RNTI (i.e., the first C-RNTI), the SPS C-RNTI (i.e., the second C-RNTI), the GF C-RNTI, and the third C-RNTI may be used to transmit DCI format C. That is, the UE102 may decode (detect, monitor) the DCI format C to which the CRC parity bits scrambled by the fourth C-RNTI are appended.

Here, DCI format C may be identified by (re) using DCI format a (i.e., scheduling DCI). For example, DCI format C may be identified by setting each of one or more fields (i.e., one or more predetermined fields) included in DCI format a to each of certain values (i.e., one or more predetermined values). For example, DCI format C may be identified by (re) using DCI format a by setting each of one or more resource block allocation fields, one or more MCS fields, one or more new data indicator fields, and/or TPC commands for one or more PUCCH fields to each of certain values. For example, all (i.e., each) of the one or more resource clock allocation fields may be set to "0" or "1" (i.e., one or more predetermined values). In addition, all (i.e., each) of the one or more MCS fields may be set to all of "0" or "1" (i.e., one or more predetermined values). Additionally, all (i.e., each) of the one or more new data indicator fields may be set to all of "0" or "1" (i.e., one or more predetermined values). In addition, all (i.e., each) of the TPC commands for the one or more PUCCH fields may be set to all of "0" or "1" (i.e., one or more predetermined values). Here, which information fields (i.e., one or more predetermined fields) included in DCI format a are used to identify DCI format C may be specified in advance by the specification and known information between the gNB160 and the UE 102. In addition, which values are set to one or more predetermined fields for identifying DCI format C may be specified in advance by the specification and known information between the gNB160 and the UE 102.

That is, DCI format C may be DCI format a including one or more predetermined fields set to one or more predetermined values. As described above, for example, DCI format C may be DCI format a including one or more resource block allocation fields set to "0". Also, DCI format C may include resource block allocation information (i.e., resource allocation information, one or more resource block allocation fields). In addition, the DCI format C may include information indicating a modulation and coding scheme (i.e., MCS information, one or more MCS fields). In addition, the DCI format C may include information (i.e., a flag, an identifier for one or more DCI format distinctions) for identifying a DCI format among a plurality of DCI formats having the same DCI size (i.e., the same DCI format size). In addition, DCI format C may include information (e.g., a new data indicator) indicating whether the transmission is a new transmission (e.g., whether the transmission is a new transmission or a retransmission). In addition, DCI format C may include information (i.e., CSI request, one or more CSI request fields)) for requesting transmission of CSI (i.e., CSI report, aperiodic CSI report (i.e., aperiodic CSI reporting)) on PUSCH and/or PUCCH. In addition, DCI format C may include information (e.g., one or more 3-bit information fields, carrier indicators and/or BWP indicators, carrier and/or BWP indicators, one or more carrier indicator fields and/or one or more BWP indicator fields, carrier and/or one or more BWP indicator fields) for indicating a serving cell (e.g., carrier) and/or BWP. That is, DCI format C may include information (e.g., one or more 3-bit information fields, a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PDSCH is scheduled). In addition, the DCI format C may include information (i.e., a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., one or more 3-bit information fields, BWP in which a corresponding PDSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell. In addition, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more BWPs in which the PDSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more BWPs may be used to indicate an initial active BWP (e.g., an initial active DL BWP) and/or a default BWP (e.g., a default DL BWP). In addition, the DCI format C may include information (e.g., one or more 3-bit information fields, a carrier, and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PDSCH is scheduled). Here, for example, in case that information (e.g., one or more 3-bit information fields) indicating one or more serving cells and one or more BWPs is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells and one or more BWPs may be used to indicate a primary cell and an initial active DL BWP (or a default DL BWP). In addition, DCI format C may include information (SRS request, one or more SRS request fields) for requesting transmission of SRS (i.e., aperiodic SRS transmission). In addition, the DCI format C may include information indicating a Transmission Power Control (TPC) command for the PCCH (e.g., a TPC command field for the PUCCH).

Also, upon receiving DCI format a (i.e., based on detecting DCI format a), UE102 may receive (i.e., decode, detect) the scheduled PDSCH. In addition, upon receiving DCI format B (i.e., based on detecting DCI format B), UE102 may receive (i.e., decode, detect) the scheduled PDSCH. Additionally, upon receiving DCI format C (i.e., based on detecting DCI format C), UE102 may perform activation, deactivation, and/or handover for the indicated one or more serving cells (e.g., one or more serving cells for receiving downlink signals and/or downlink communications). That is, the UE102 may perform activation, deactivation, handover for one or more serving cells based on the information included in DCI format C as described above. Additionally, upon receiving DCI format C (i.e., based on detecting DCI format C), UE102 may perform activation, deactivation, and/or handover for one or more BWPs (e.g., one or more DL BWPs for receiving downlink signals and/or downlink communications). That is, the UE102 may perform activation, deactivation, handover for one or more BWPs based on the information included in the DCI format C as described above.

In addition, DCI format 0 and/or DCI format 4 for scheduling one or more uplink physical shared channels in a cell may be defined as a DCI format for uplink. For example, DCI format 0 may be used to schedule the transmission of one uplink physical shared channel (e.g., one PUSCH codeword, one uplink transport block) in a cell. In addition, DCI format 4 may be used to schedule one uplink physical shared channel (e.g., transmission of one PUSCH, at most two PUSCH codewords, at most two uplink transport blocks). Here, to simplify the description, in some implementations, it may be assumed that DCI format 0 and/or DCI format 4 described herein are included in DCI format D. As described above, DCI format D may be used to schedule an uplink PSCH (e.g., PUSCH). That is, DCI format D may be a scheduling DCI. In addition, the uplink PSCH (e.g., PUSCH) may be scheduled using a set of control resources (i.e., CORESET) in which the search space (e.g., UE-specific search space, common search space, and/or PDCCH) of DCI format D is monitored.

Here, DCI format D may be used to activate and/or deactivate one or more serving cells (e.g., one or more secondary cells, one or more uplink secondary cells, and/or one or more uplink component carriers), as described below. In addition, DCI format D may be used to activate and/or deactivate one or more bandwidth parts (e.g., one or more BWPs in one or more serving cells, one or more UL BWPs in one or more serving cells). In addition, C-RNTI (i.e., first C-RNTI), SPS C-RNTI (i.e., second C-RNTI), and/or GF C-RNTI may be used for transmission of DCI format D. That is, the UE102 may decode (detect, monitor) the DCI format D to which the CRC parity bits scrambled by the C-RNTI, SPS C-RNTI, and/or GF C-RNTI are appended.

For example, DCI format D may include resource block allocation information (i.e., resource allocation information, one or more resource block allocation fields). That is, DCI format D may include information indicating one or more physical resource blocks of a PUSCH (e.g., an index of one or more physical resource blocks, a size of one or more physical resource blocks). In addition, the DCI format D may include information indicating a modulation and coding scheme (i.e., MCS information, one or more MCS fields). In addition, the DCI format D may include information (i.e., a flag, an identifier for one or more DCI format distinctions) for identifying a DCI format among a plurality of DCI formats having the same DCI size (i.e., the same DCI format size). For example, for multiple DCI formats of the same DCI size with the same RNTI, this information (i.e., flags, identifiers for one or more DCI format distinctions) may be included in the corresponding DCI format (e.g., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F) to distinguish the multiple DCI formats (i.e., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F). In addition, DCI format D may include information (e.g., a new data indicator) indicating whether the transmission is a new transmission (e.g., whether the transmission is a new transmission or a retransmission). In addition, DCI format D may include information (i.e., CSI request, one or more CSI request fields)) for requesting transmission of CSI (i.e., CSI report, aperiodic CSI report (i.e., aperiodic CSI reporting)) on PUSCH and/or PUCCH. In addition, DCI format D may include information (e.g., one or more 3-bit information fields, carrier indicators and/or BWP indicators, carrier and/or BWP indicators, one or more carrier indicator fields and/or one or more BWP indicator fields, carrier and/or one or more BWP indicator fields) for indicating a serving cell (e.g., carrier) and/or BWP. That is, DCI format D may include information (e.g., one or more 3-bit information fields, a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PUSCH is scheduled). In addition, DCI format D may include information (e.g., one or more 3-bit information fields, a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PUSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PUSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell. In addition, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more BWPs in which the PUSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more BWPs may be used to indicate an initial active BWP (e.g., an initial active UL BWP) and/or a default BWP (e.g., a default UL BWP). In addition, the DCI format D may include information (i.e., a carrier and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PUSCH is scheduled). Here, for example, in case that information (e.g., one or more 3-bit information fields) indicating one or more serving cells and one or more BWPs is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells and one or more BWPs may be used to indicate a primary cell and an initial active UL BWP (or a default UL BWP). In addition, DCI format D may include information (SRS request, one or more SRS request fields) for requesting transmission of SRS (i.e., aperiodic SRS transmission). In addition, the DCI format D may include information indicating a Transmission Power Control (TPC) command for the PSCH (e.g., a TPC command field for the PUSCH).

In addition, DCI format L and/or DCI format M for scheduling one or more uplink physical channels in a cell may be defined as a DCI format for the uplink (e.g., a fallback DCI format). For example, DCI format L and/or DCI format M may be used to schedule one uplink physical shared channel (e.g., transmission of one PUSCH, one PUSCH codeword, one uplink transport block). Here, to simplify the description, in some implementations, it may be assumed that DCI format L and/or DCI format M described herein are included in DCI format E. As described above, DCI format E may be used to schedule an uplink PSCH (e.g., PUSCH). That is, DCI format E may be a scheduling DCI. In addition, the uplink PSCH (e.g., PUSCH) may be scheduled using a set of control resources (i.e., CORESET) in which the search space (e.g., UE-specific search space, common search space, and/or PDCCH) of DCI format E is monitored.

Here, DCI format E may be used to activate and/or deactivate one or more serving cells (e.g., one or more secondary cells, one or more uplink secondary cells, and/or one or more uplink component carriers), as described below. In addition, DCI format E may be used to activate and/or deactivate one or more bandwidth parts (e.g., one or more BWPs in one or more serving cells, one or more UL BWPs in one or more serving cells). In addition, the C-RNTI (i.e., the first C-RNTI) and/or the SPS C-RNTI (i.e., the second C-RNTI) may be used for transmission of the DCI format E. That is, the UE102 may decode (detect, monitor) the DCI format E to which CRC parity bits scrambled by the C-RNTI (i.e., the first C-RNTI), the SPS C-RNTI (i.e., the second C-RNTI), and/or the GF C-RNTI are appended. Here, a C-RNTI (i.e., a third C-RNTI, e.g., a C-RNTI for a fallback DCI format) and an SPS C-RNTI (i.e., a second C-RNTI) that is different from the C-RNTI (i.e., the first C-RNTI) may be used for transmission of DCI format E. That is, the UE102 may decode (detect, monitor) the DCI format E to which the CRC parity bits scrambled by the third C-RNTI are appended.

For example, DCI format E may include resource block allocation information (i.e., resource allocation information, one or more resource block allocation fields). That is, DCI format E may include information indicating one or more physical resource blocks of a PUSCH (e.g., an index of one or more physical resource blocks, a size of one or more physical resource blocks). In addition, DCI format E may include information indicating a modulation and coding scheme (i.e., MCS information, one or more MCS fields). In addition, DCI format E may include information (i.e., flags, identifiers for one or more DCI format distinctions) for identifying a DCI format among a plurality of DCI formats having the same DCI size (i.e., the same DCI format size). For example, for multiple DCI formats of the same DCI size with the same RNTI, this information (i.e., flags, identifiers for one or more DCI format distinctions) may be included in the corresponding DCI format (e.g., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F) to distinguish the multiple DCI formats (i.e., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F). In addition, DCI format E may include information (e.g., a new data indicator) indicating whether the transmission is a new transmission (e.g., whether the transmission is a new transmission or a retransmission). In addition, DCI format E may include information (i.e., CSI request, one or more CSI request fields) for requesting transmission of CSI (i.e., CSI reporting, aperiodic CSI reporting (i.e., aperiodic CSI reporting)) on PUSCH and/or PUCCH. In addition, DCI format E may include information (e.g., one or more 3-bit information fields, carrier indicators and/or BWP indicators, carrier and/or BWP indicators, one or more carrier indicator fields and/or one or more BWP indicator fields, carrier and/or one or more BWP indicator fields) for indicating a serving cell (e.g., carrier) and/or BWP. That is, DCI format E may include information (e.g., one or more 3-bit information fields, a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PUSCH is scheduled). In addition, DCI format B may include information (e.g., one or more 3-bit information fields, a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PUSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PUSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell. In addition, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more BWPs in which the PUSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more BWPs may be used to indicate an initial active BWP (e.g., an initial active UL BWP) and/or a default BWP (e.g., a default UL BWP). In addition, DCI format B may include information (i.e., a carrier and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PUSCH is scheduled). Here, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more serving cells and one or more BWPs is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell and an initial active UL BWP (or a default UL BWP). In addition, DCI format B may include information (SRS request, one or more SRS request fields) for requesting transmission of SRS (i.e., aperiodic SRS transmission). In addition, DCI format B may include information indicating a Transmission Power Control (TPC) command for PSCH (e.g., a TPC command field for PUSCH).

Here, DCI format E may not include information indicating a serving cell (e.g., carrier) and/or BWP (i.e., a carrier indicator and/or BWP indicator, a carrier and/or BWP indicator, one or more carrier indicator fields and/or one or more BWP indicator fields, a carrier and/or one or more BWP indicator fields). That is, DCI format E may not include information (i.e., a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PUSCH is scheduled). In addition, DCI format E may not include information (i.e., a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PUSCH is scheduled). In addition, DCI format E may not include information (i.e., a carrier and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PUSCH is scheduled).

In addition, DCI format E may be used to schedule a PUSCH having a smaller size than that of a PUSCH scheduled by using DCI format D. That is, for example, DCI format E may be used to schedule a PUSCH whose bandwidth is narrower than that of a PUSCH scheduled by using DCI format D. For example, the number of one or more PRBs allocated by using DCI format D (e.g., the total number of allocated one or more PRBs of PDSCH, Nprb) may be 100(PRB), 110(PRB), 270(PRB), 273(PRB), and/or 276 (PRB). Here, 100(PRB) may correspond to 20MHz, 110(PRB) may correspond to 20MHz, 270(PRB) may correspond to 50MHz, 273(PRB) may correspond to 100MHz, and/or 276(PRB) may correspond to 100 MHz. That is, the maximum number of one or more PRBs allocated by using DCI format D may be 100(PRB), 110(PRB), 270(PRB), 273(PRB), and/or 276 (PRB). Also, DCI format D may be used to schedule PUSCH of up to 100(PRB), 110(PRB), 270(PRB), 273(PRB), and/or 276 (PRB). In addition, the number of one or more PRBs allocated by using the DCI format E may be 6(PRB), 24(PRB), 25(PRB), 50(PRB), and/or 52 (PRB). Here, 6(PRB) may correspond to 1.4MHz, 25(PRB) may correspond to 5MHz, 50(PRB) may correspond to 10MHz, and/or 52(PRB) may correspond to 10 MHz. In addition, 24 (PRBs) may correspond to a bandwidth for PSS, SSS, and/or PBCH (e.g., one or more SS blocks). In addition, 24(PRB) may correspond to a bandwidth for RMSI (e.g., SIB2) and CORESET including PDCCH scheduling RMSE. In addition, 24(PRB) may correspond to the bandwidth used for msg.3 transmission on UL-SCH in random access procedure (i.e., PUSCH transmission). That is, DCI format E may be used to schedule a PUSCH of a bandwidth corresponding to (e.g., the same as) a bandwidth in which a random access procedure is performed.

That is, the maximum number of one or more PRBs allocated by using the DCI format E may be 6(PRB), 24(PRB), 25(PRB), 50(PRB), and/or 52 (PRB). And, DCI format E may be used to schedule PDSCH of at most 6(PRB), 24(PRB), 25(PRB), 50(PRB), and/or 52 (PRB). That is, for example, one or more transport blocks having a larger size (i.e., a larger number) may be transmitted on the PUSCH scheduled by using DCI format D than the size (i.e., the number) of one or more transport blocks transmitted on the PUSCH scheduled by using DCI format E. That is, for example, one or more transport blocks having a smaller size may be transmitted on a PUSCH scheduled by using DCI format E than the size of one or more transport blocks transmitted on a PUSCH scheduled by using DCI format D. For example, a third table for determining the size of one or more transport blocks may be defined (e.g., specified) for DCI format D. In addition, a fourth table (i.e., a fourth table different from the third table) for determining the size of one or more transport blocks may be defined (e.g., specified) for DCI format E. Also, the maximum size (i.e., the maximum number) of the one or more transport blocks for DCI format D (i.e., the maximum size of the one or more transport blocks transmitted on the PUSCH scheduled by using DCI format D) may be greater than the maximum size (i.e., the maximum number) of the one or more transport blocks for DCI format E (i.e., the maximum size of the one or more transport blocks transmitted on the PUSCH scheduled by using DCI format E).

Here, the number of allocated one or more PRBs (i.e., the maximum number of allocated one or more PRBs) may depend on each of a plurality of parameters (i.e., multi-subcarrier spacing). That is, for a certain parameter (i.e., a given parameter, a configured parameter), as described above, the number of allocated one or more PRBs that can be scheduled by using DCI format E is smaller than the number of allocated one or more PRBs that can be scheduled by using DCI format D. In addition, the number of one or more PRBs allocated by using DCI format E (i.e., the maximum number of allocated one or more PRBs) may be determined based on the bandwidth of the default DL BWP (e.g., the number of one or more PRBs of the default DL BWP). In addition, the number of one or more PRBs allocated by using DCI format E (i.e., the maximum number of allocated one or more PRBs) may be determined based on a bandwidth of the default UL BWP (e.g., the number of one or more PRBs of the default UL BWP). As described above, for example, the gNB160 may configure the bandwidth of the default DL BWP (e.g., the number of one or more PRBs of the default DL BWP), e.g., by using RRC messages. In addition, for example, gNB160 may configure the bandwidth of the default UL BWP (e.g., the number of one or more PRBs of the default UL BWP), e.g., by using RRC messages. In addition, the number of one or more PRBs allocated by using the DCI format E (i.e., the maximum number of allocated one or more PRBs) may be determined based on a bandwidth of the active DL BWP (e.g., the initial active DL BWP, the number of one or more PRBs of the initial active DL BWP; the number of active DL BWP, the number of one or more PRBs of the active DL BWP). In addition, the number of one or more PRBs allocated by using the DCI format E (i.e., the maximum number of allocated one or more PRBs) may be determined based on a bandwidth of the active UL BWP (e.g., the initial active UL BWP, the number of one or more PRBs of the initial active UL BWP; the activated UL BWP, the number of one or more PRBs of the activated UL BWP). As described above, for example, gNB160 may configure the bandwidth of the active DL BWP (e.g., the initial active DL BWP, number of one or more PRBs of the initial active DL BWP; the active DL BWP, number of one or more PRBs of the active DL BWP), e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. In addition, for example, gNB160 may configure the bandwidth of the active UL BWP (e.g., the number of one or more PRBs of the initial active UL BWP; the number of the activated UL BWP, the number of one or more PRBs of the activated UL BWP), e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. In addition, the gNB160 may configure the bandwidth of the RMSI core, e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. And, a bandwidth of the active DL BWP (e.g., the number of the initial active DL BWP's one or more PRBs; the number of the activated DL BWP's one or more PRBs) and/or a bandwidth of the active UL BWP (e.g., the number of the initial active UL BWP's one or more PRBs; the number of the activated UL BWP's one or more PRBs) may be determined based on (e.g., the same as) the bandwidth of the RMSI core set.

In addition, for example, the parameter of the PUSCH scheduled by using the DCI format D may be 15kHz (e.g., a first parameter), 30kHz (e.g., a second parameter), and/or 60kHz (e.g., a third parameter). That is, DCI format D may be used to schedule PUSCH of various parameters (i.e., first, second, and/or third parameters). In addition, the parameter of the PUSCH scheduled by using the DCI format E may be 15kHz (e.g., a first parameter), 30kHz (e.g., a second parameter), and/or 60kHz (e.g., a third parameter). That is, DCI format E may be used to schedule PDSCH of various parameters (i.e., first, second, and/or third parameters). Here, for example, the parameter of the PDSCH scheduled by using the DCI format E may be only one of 15kHz (i.e., a first parameter), 30kHz (i.e., a second parameter), and 60kHz (i.e., a third parameter). For example, only 15kHz SCS is available for PUSCH scheduled by using DCI format E. Here, parameters for PUSCH scheduled by using DCI format E may be specified in advance by specification and known information between the gNB160 and the UE 102. That is, upon receiving (e.g., detecting) DCI format E, UE102 may assume 15kHz SCS (e.g., first parameter) for the scheduled PDSCH. Also, the UE102 may perform PUSCH transmission based on 15kHz SCS (e.g., assumption of PUSCH based on 15kHz SCS (e.g., first parameter) even if 30kHz SCS (e.g., second parameter) and/or 60kHz SCS (e.g., third parameter) is configured).

In addition, the parameter of the PUSCH scheduled by using DCI format E may be determined based on the parameter of the default DL BWP. For example, the gNB160 may configure the parameters of the default DL BWP, e.g., by using RRC messages. In addition, the parameter of the PUSCH scheduled by using DCI format E may be determined based on the parameter of the default UL BWP. For example, the gNB160 may configure the parameters of the default UL BWP, e.g., by using RRC messages. In addition, parameters of PUSCH scheduled by using DCI format E may be determined based on parameters of active DL BWP (e.g., initial active DL BWP, active DL BWP). For example, the gNB160 may configure parameters of the active DL BWP (e.g., initial active DL BWP, active DL BWP), e.g., by using RRC messages. In addition, parameters of the PUSCH scheduled by using DCI format E may be determined based on parameters of active UL BWP (e.g., initial active UL BWP, activated UL BWP). For example, the gNB160 may configure parameters of the active UL BWP (e.g., initial active UL BWP, active UL BWP), e.g., by using RRC messages. In addition, the gNB160 may configure parameters of RMSI core, for example, by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. Also, parameters of active DL BWPs (e.g., initially active DL BWP, activated DL BWP) and/or active UL BWPs (e.g., initially active UL BWP, activated UL BWP) may be determined based on (e.g., the same as) the parameters of RMSI CORESET. That is, the parameter of the PUSCH scheduled by using DCI format E may be determined based on the parameter of RMSI core set. Additionally, the gNB160 may configure parameters for RMSI (e.g., PDSCH for transmitting RMSI), msg.2 (e.g., PDSCH for transmitting msg.2 in a random access procedure), and/or msg.4 (e.g., PDSCH for transmitting msg.4 in a random access procedure), e.g., by using PBCH (e.g., MIB), RMSI (e.g., SIB2), and/or RRC messages. Also, parameters of the active DL BWP (e.g., initial active DL BWP, active DL BWP) and/or the active UL BWP (e.g., initial active UL BWP, active UL BWP) may be determined based on (e.g., the same as) the parameters for RMSI, msg.2, and/or msg.4. That is, the parameters of the PUSCH scheduled by using DCI format E may be determined based on the parameters for RMSI, msg.2, and/or msg.4.

In addition, DCI formats O and/or DCI formats P for activating, deactivating, and/or switching one or more serving cells (e.g., one or more secondary cells, one or more uplink secondary cells, and/or one or more secondary uplink component carriers) may be defined as DCI formats for uplink. Here, DCI format Z and/or DCI format K may be used to activate, deactivate, and/or handover one or more BWPs (e.g., one or more BWPs in one or more serving cells, one or more UL BWPs in one or more serving cells). That is, DCI format O and/or DCI format P are used to activate, deactivate, and/or handover one or more serving cells and/or one or more BWPs. Here, to simplify the description, in some implementations, it may be assumed that DCI format O and/or DCI format P described herein are included in DCI format F. As described above, DCI format F may be used to activate, deactivate, and/or handover one or more serving cells and/or one or more BWPs. That is, DCI format F may be an activation/deactivation/handover DCI. In addition, one or more serving cells and/or one or more BWPs may be activated, deactivated, and/or handed over using a control resource set (i.e., CORESET) in which the search space (e.g., UE-specific search space, common search space, and/or PDCCH) of DCI format F is monitored.

Here, C-RNTI (i.e., first C-RNTI), SPS C-RNTI (i.e., second C-RNTI), and/or GF C-RNTI may be used for transmission of DCI format F. That is, the UE102 may decode (detect, monitor) the DCI format F to which CRC parity bits scrambled by the C-RNTI (i.e., the first C-RNTI), the SPSC-RNTI (i.e., the second C-RNTI), and/or the GF C-RNTI are appended. Here, a C-RNTI (i.e., a fourth C-RNTI, e.g., a C-RNTI used to activate/deactivate/switch DCI formats), an SPS C-RNTI (i.e., a second C-RNTI), a GF C-RNTI, and a third C-RNTI that is different from the C-RNTI (i.e., the first C-RNTI) may be used for transmission of DCI format F. That is, the UE102 may decode (detect, monitor) the DCI format F to which the CRC parity bits scrambled by the fourth C-RNTI are appended.

Here, DCI format F may be identified by (re) using DCI format D (i.e., scheduling DCI). For example, DCI format F may be identified by setting each of one or more fields (i.e., one or more predetermined fields) included in DCI format D to each of certain values (i.e., one or more predetermined values). For example, DCI format F may be identified by (re) using DCI format D by setting each of one or more resource block allocation fields, one or more MCS fields, one or more new data indicator fields, and/or TPC commands for one or more PUSCH fields to each of certain values. For example, all (i.e., each) of the one or more resource clock allocation fields may be set to "0" or "1" (i.e., one or more predetermined values). In addition, all (i.e., each) of the one or more MCS fields may be set to all of "0" or "1" (i.e., one or more predetermined values). Additionally, all (i.e., each) of the one or more new data indicator fields may be set to all of "0" or "1" (i.e., one or more predetermined values). In addition, all (i.e., each) of the TPC commands for the PUSCH field(s) may be set to all of "0" or "1" (i.e., one or more predetermined values). Here, which information fields (i.e., one or more predetermined fields) included in DCI format D are used to identify DCI format F may be specified in advance by the specification and known information between the gNB160 and the UE 102. In addition, which values are set to one or more predetermined fields for identifying DCI format F may be specified in advance by the specification and known information between the gNB160 and the UE 102.

That is, the DCI format F may be a DCI format D including one or more predetermined fields set to one or more predetermined values. As described above, for example, DCI format F may be DCI format D including one or more resource block allocation fields set to "0". Also, DCI format F may include resource block allocation information (i.e., resource allocation information, one or more resource block allocation fields). In addition, the DCI format F may include information indicating a modulation and coding scheme (i.e., MCS information, one or more MCS fields). In addition, the DCI format F may include information (i.e., a flag, an identifier for one or more DCI format distinctions) for identifying a DCI format among a plurality of DCI formats having the same DCI size (i.e., the same DCI format size). In addition, DCI format F may include information (e.g., a new data indicator) indicating whether the transmission is a new transmission (e.g., whether the transmission is a new transmission or a retransmission). In addition, DCI format F may include information (i.e., CSI request, one or more CSI request fields) for requesting transmission of CSI (i.e., CSI reporting, aperiodic CSI reporting (i.e., aperiodic CSI reporting)) on PUSCH and/or PUCCH. In addition, DCI format F may include information (e.g., one or more 3-bit information fields, carrier indicators and/or BWP indicators, carrier and/or BWP indicators, one or more carrier indicator fields and/or one or more BWP indicator fields, carrier and/or one or more BWP indicator fields) for indicating a serving cell (e.g., carrier) and/or BWP. That is, DCI format F may include information (e.g., one or more 3-bit information fields, a carrier indicator, one or more carrier indicator fields) for indicating a serving cell (e.g., a carrier in which a corresponding PDSCH is scheduled). In addition, DCI format F may include information (e.g., a BWP indicator, one or more BWP indicator fields) for indicating BWP (e.g., BWP in which a corresponding PDSCH is scheduled). Here, for example, in the case where information (e.g., one or more 3-bit information fields) indicating one or more serving cells in which a PUSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell. In addition, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more BWPs in which the PUSCH is scheduled is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more BWPs may be used to indicate an initial active BWP (e.g., an initial active UL BWP) and/or a default BWP (e.g., a default UL BWP). In addition, the DCI format F may include information (i.e., a carrier and a BWP indicator) for indicating a serving cell and BWP (e.g., a serving cell and BWP in which a corresponding PDSCH is scheduled). Here, for example, in case information (e.g., one or more 3-bit information fields) indicating one or more serving cells and one or more BWPs is set to "0" (e.g., all 3-bit information fields are set to "0"), the information indicating one or more serving cells may be used to indicate a primary cell and an initial active UL BWP (or a default UL BWP). In addition, DCI format F may include information (SRS request, one or more SRS request fields) for requesting transmission of SRS (i.e., aperiodic SRS transmission). In addition, the DCI format F may include information indicating a Transmission Power Control (TPC) command for the PCCH (e.g., a TPC command field for the PUCCH).

Also, upon receiving DCI format D (i.e., based on detecting DCI format D), UE102 may perform PUSCH transmission. In addition, upon receiving DCI format E (i.e., based on detecting DCI format E), UE102 may perform PUSCH transmission. Additionally, upon receiving DCI format F (i.e., based on detecting DCI format F), UE102 may perform activation, deactivation, and/or handover for the indicated one or more serving cells (e.g., one or more serving cells for receiving downlink signals and/or downlink communications, and/or one or more serving cells for transmitting uplink signals and/or uplink communications). That is, the UE102 may perform activation, deactivation, handover for one or more serving cells based on the information included in the DCI format F as described above. Additionally, upon receiving DCI format F (i.e., based on detecting DCI format F), UE102 may perform activation, deactivation, and/or handover for one or more BWPs (e.g., one or more DL BWPs for receiving downlink signals and/or downlink communications, and/or one or more UL BWPs for transmitting uplink signals and/or uplink communications). That is, the UE102 may perform activation, deactivation, handover for one or more BWPs based on the information included in the DCI format C as described above.

Fig. 5 shows an example of downlink and/or uplink transmission. As shown in fig. 5, one or more serving cells may be configured for UE 102. In Carrier Aggregation (CA), the gNB160 and the UE102 may communicate with each other using one or more serving cells. Here, the configured one or more serving cells may include one primary cell and one or more secondary cells. For example, the primary cell may be a serving cell on which an initial connection establishment procedure is performed. In addition, the primary cell may be a serving cell on which a connection re-establishment procedure is performed. Additionally, the primary cell may be a serving cell indicated as a primary cell (e.g., indicated as a primary cell during a handover procedure). For example, the gNB160 may transmit information configuring the primary cell, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages. In addition, the gNB160 may transmit information for configuring one or more secondary cells to form a serving cell set with the primary cell, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages. Here, in downlink, a carrier corresponding to a primary cell may be a downlink primary component carrier, and a carrier corresponding to a secondary cell may be a downlink secondary component carrier. In addition, in the uplink, the carrier corresponding to the primary cell may be an uplink primary component carrier, and the carrier corresponding to the secondary cell may be an uplink secondary component carrier.

Here, the primary cell may be used for transmission on PUCCH. That is, UE102 may perform transmission on the PUCCH in the primary cell. In addition, the primary cell may not be deactivated. In addition, cross-carrier scheduling may not be applied to the primary cell. That is, the primary cell may always be scheduled via the PDCCH (i.e., the PDCCH of the primary cell). In addition, in the case where a PDCCH of the secondary cell is configured (e.g., PDCCH monitoring, one or more PDCCH monitoring occasions), cross-carrier scheduling may not be applied to the secondary cell. That is, in the case where the PDCCH of the secondary cell is configured, the secondary cell can be always scheduled via the PDCCH (i.e., the PDCCH of the secondary cell). In addition, in case that a PDCCH of a secondary cell is not configured (e.g., PDCCH monitoring, one or more PDCCH monitoring occasions), cross-carrier scheduling may be applied to the secondary cell. That is, in the case where the PDCCH of the secondary cell is not configured, the secondary cell may be scheduled via the PDCCH of another serving cell. Here, as described above, the carrier indicator (i.e., the one or more carrier indicator fields) may be included in one or more DCI formats for indicating a serving cell (e.g., a serving cell on which a corresponding PDSCH and/or a corresponding PUSCH is scheduled).

Here, a link (i.e., connection, pairing, correspondence) may be defined between an uplink (e.g., uplink component carrier) and a downlink (e.g., downlink component carrier). For example, the gNB160 may transmit information for configuring a link between uplink and downlink, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages. That is, a serving cell in which transmission on the PDSCH is performed based on scheduling by using one or more DCI formats (i.e., one or more DCI formats for downlink, downlink allocation) may be identified based on the linking. In addition, a serving cell in which transmission on the PUSCH is performed based on scheduling by using one or more DCI formats (i.e., one or more DCI formats for uplink, an uplink grant) may be identified based on the linking. Here, in this case, the one or more carrier indicator fields may not be included in the one or more DCI formats (i.e., one or more DCI formats for downlink, one or more DCI formats for uplink). That is, the one or more DCI formats received on the primary cell may correspond to downlink transmissions (e.g., PDSCH transmissions) on the primary cell. Additionally, the one or more DCI formats received on the secondary cell may correspond to an uplink transmission (e.g., a PUSCH transmission) on the secondary cell.

Additionally, as described above, activation and/or deactivation mechanisms for one or more serving cells may be supported. Here, the primary cell may be always activated. For example, the gNB160 may transmit information indicating activation, deactivation, and/or handover of one or more serving cells, e.g., by using higher layer signals (e.g., MAC CEs) and/or one or more DCI formats. Additionally, the gNB160 may transmit information for configuring one or more values of a timer (e.g., a first timer) associated with deactivation and/or handover of one or more serving cells, e.g., by using higher layer signals (e.g., RRC messages). For example, the UE102 may maintain a first timer for each configured secondary cell. In addition, the UE102 may deactivate the secondary cell (i.e., the associated secondary cell) based on the timer expiring. That is, the UE102 may activate one or more serving cells (e.g., one or more secondary cells) based on the information indicating activation and/or handover of the one or more serving cells (e.g., one or more secondary cells). Also, the UE102 may perform SRS transmission (e.g., aperiodic SRS transmission) on one or more serving cells if the one or more serving cells are activated. Additionally, the UE102 may perform CSI reporting (e.g., aperiodic CSI reporting) for one or more serving cells if the one or more serving cells are activated. In addition, the UE102 may perform PDCCH monitoring on one or more serving cells with the one or more serving cells activated. In addition, the UE102 may perform PDCCH monitoring for one or more serving cells in the event that one or more serving cells are activated. Additionally, the UE102 may start (or restart) a first timer associated with one or more serving cells in the event that the one or more serving cells are activated. In addition, the UE102 may deactivate one or more serving cells (e.g., one or more secondary cells) based on the information for deactivating the one or more serving cells (e.g., one or more secondary cells). Also, the UE102 may stop the first timer associated with the one or more serving cells in the event that the one or more serving cells are activated. Additionally, in the event that one or more DCI formats on the activated one or more serving cells are used to schedule PDSCH and/or PUSCH, UE102 may restart the first timer associated with the one or more serving cells. Additionally, where one or more DCI formats of one or more serving cells on one or more serving cells for scheduling activation are used to schedule PDSCH and/or PUSCH for the activated one or more serving cells, UE102 may restart the first timer associated with the one or more serving cells. Additionally, the UE102 may not perform SRS transmission (e.g., aperiodic SRS transmission) on the one or more serving cells in the event that the one or more serving cells are deactivated. Additionally, the UE102 may not perform CSI reporting (e.g., perform aperiodic CSI reporting) for one or more serving cells in the event that the one or more serving cells are deactivated. Additionally, the UE102 may not transmit the UL-SCH on the one or more serving cells in the event that the one or more serving cells are deactivated. Additionally, the UE102 may not monitor PDCCH on one or more serving cells in the event that one or more serving cells are deactivated. Additionally, the UE102 may not monitor PDCCH for one or more serving cells in the event that one or more serving cells are deactivated.

In addition, for example, one or more serving BWPs (e.g., four DL BWPs and/or four UL BWPs) may be configured to the UE 102. Here, the configured one or more serving cells may include one or more initially active BWPs (e.g., initially active DL BWPs and/or initially active UL BWPs). Additionally, the configured one or more serving cells may include one or more default BWPs (e.g., default DL BWPs and/or default UL BWPs). For example, the initial active BWP may be a BWP (e.g., DL BWP and/or UL BWP) on which the initial connection establishment procedure is performed. Additionally, the initial active BWP may be a BWP (e.g., DL BWP and/or UL BWP) on which the connection re-establishment procedure is performed. Additionally, the initial active BWP may be a BWP (e.g., DL BWP and/or UL BWP) indicated as the initial active BWP (e.g., indicated as the initial active BWP during the handover procedure). Additionally, for example, the default BWP may be the BWP (e.g., DL BWP and/or UL BWP) on which the initial connection establishment procedure is performed. Additionally, the default BWP may be the BWP (e.g., DL BWP and/or UL BWP) on which the connection re-establishment procedure is performed. Additionally, the default BWP may be a BWP (e.g., DL BWP and/or UL BWP) indicated as an initial active BWP (e.g., indicated as the default BWP during the handover procedure). That is, the default BWP may be the initial active BWP. For example, the gNB160 may transmit information configuring one or more initial BWPs, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages. Here, the gNB160 may independently configure the initial DL BWP and the initial UL BWP. In addition, the gNB160 may transmit information for configuring one or more default BWPs, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages. Here, the gNB160 may independently configure a default DL BWP and a default UL BWP. Additionally, for example, the gNB160 may transmit information for configuring one or more BWPs in one or more serving cells, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type), and/or dedicated RRC messages. Here, the gNB160 may independently configure one or more DL BWPs (e.g., four DL BWPs) and one or more UL BWPs (e.g., four UL BWPs) in the serving cell.

Here, the initial active BWP and/or the default BWP may be used for transmission on PUCCH. That is, the UE102 may perform transmissions on the PUCCH in the initial active BWP and/or the default BWP. Additionally, the initial active BWP and/or the default BWP may not be deactivated. In addition, cross-carrier scheduling may not be applied to the initial active BWP and/or the default BWP. That is, the initial active BWP and/or the default BWP may always be scheduled via PDCCH (i.e., PDCCH of the initial active BWP and/or the default BWP). In addition, in case of PDCCH configured with one or more BWPs (e.g., PDCCH monitoring, one or more PDCCH monitoring occasions), cross-carrier scheduling may not be applied to one or more BWPs. That is, in the case of a PDCCH on which one or more BWPs are configured, one or more BWPs may always be scheduled via the PDCCH (i.e., the PDCCH of one or more BWPs). In addition, cross-carrier scheduling may be applied to one or more BWPs without configuring a PDCCH for the one or more BWPs (e.g., PDCCH monitoring, one or more PDCCH monitoring occasions). That is, in case that the PDCCH of one or more BWPs is not configured, one or more BWPs may be scheduled via the PDCCH of another BWP. Here, as described above, the BWP indicator (i.e., the one or more BWP indicator fields) may be included in one or more DCI formats for indicating one or more BWPs (e.g., one or more BWPs on which a corresponding PDSCH and/or a corresponding PUSCH are scheduled).

Here, a link (i.e., connection, pairing, correspondence) may be defined between the UL BWP and the DL BWP. For example, the gNB160 may transmit information for configuring a link between one or more UL BWPs and one or more DL BWPs, e.g., by using PBCH (e.g., MIB), PDSCH (e.g., SIB2 type) and/or dedicated RRC messages. That is, one or more BWPs in which transmission on the PDSCH is performed based on scheduling by using one or more DCI formats (i.e., one or more DCI formats for downlink, downlink allocation) may be identified based on the linking. In addition, one or more BWPs in which transmission on the PUSCH is performed based on scheduling by using one or more DCI formats (i.e., one or more DCI formats for uplink, uplink grant) may be identified based on the linking. Here, in this case, the BWP indicator field(s) may not be included in the DCI format(s) (i.e., DCI format(s) for downlink, DCI format(s) for uplink). That is, one or more DCI formats received on one or more DL BWPs may correspond to downlink transmissions (e.g., PDSCH transmissions) on the one or more DL BWPs. Additionally, the one or more DCI formats received on the one or more BWPs may correspond to uplink transmissions (e.g., PUSCH transmissions) on the one or more BWPs.

Additionally, as described above, one or more mechanisms for activation and/or deactivation of BWPs may be supported. Here, the initial active BWP and/or the default BWP may be activated all the time. For example, the gNB160 may transmit information indicating activation, deactivation, and/or handover of one or more BWPs, e.g., by using higher layer signals (e.g., MAC CEs) and/or one or more DCI formats. Additionally, the gNB160 may transmit information for configuring one or more values of a timer (e.g., a second timer) associated with deactivation and/or handover of one or more BWPs, e.g., by using higher layer signals (e.g., RRC messages). For example, UE102 may maintain a second timer for each configured BWP. In addition, the UE102 may maintain a second timer for each configured serving cell. Additionally, the UE102 may deactivate one or more BWPs (i.e., associated one or more BWPs) based on expiration of the timer. That is, the UE102 may activate one or more BWPs based on the information indicating activation and/or handover of the one or more BWPs. Also, the UE102 may perform SRS transmission (e.g., aperiodic SRS transmission) on one or more BWPs if the one or more BWPs are activated. Additionally, the UE102 may perform CSI reporting (e.g., aperiodic CSI reporting) for one or more BWPs if the one or more BWPs are activated. Additionally, UE102 may perform PDCCH monitoring on one or more BWPs with the one or more BWPs activated. Additionally, UE102 may perform PDCCH monitoring for one or more BWPs in the event that one or more BWPs are activated. Additionally, in the event that one or more BWPs are activated, UE102 may start (or restart) a second timer associated with the one or more BWPs. In addition, UE102 may deactivate one or more BWPs based on the information for deactivating the one or more BWPs. Also, in the event that one or more BWPs are deactivated, UE102 may stop the second timer associated with the one or more BWPs. Additionally, in the event that one or more DCI formats on the activated one or more BWPs are used to schedule PDSCH and/or PUSCH, UE102 may restart a second timer associated with the one or more BWPs. Additionally, where one or more DCI formats scheduling the activated one or more BWPs over the one or more BWPs are used to schedule PDSCH and/or PUSCH for the activated one or more BWPs, the UE102 may restart the second timer associated with the one or more BWPs. Additionally, the UE102 may not perform SRS transmission (e.g., aperiodic SRS transmission) on the one or more BWPs if the one or more BWPs are deactivated. Additionally, the UE102 may not perform CSI reporting (e.g., aperiodic CSI reporting) for the one or more BWPs if the one or more BWPs are deactivated. Additionally, UE102 may not transmit the UL-SCH on one or more BWPs if the one or more BWPs are deactivated. Additionally, UE102 may not monitor PDCCH on one or more BWPs with one or more BWPs deactivated. Additionally, UE102 may not monitor PDCCH for one or more BWPs if the one or more BWPs are deactivated.

Here, information for configuring one or more values of the second timer may be configured for each serving cell. That is, the information for configuring the one or more values of the second timer may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). That is, the gNB160 may configure one or more values of the second timer (e.g., a single value of the second timer) for one or more BWPs in one or more serving cells. In addition, information for configuring one or more values of the second timer may be configured for each BWP (e.g., for each BWP in the serving cell). That is, information for configuring one or more values of the second timer may be configured for each BWP in the serving cell. That is, the gNB160 may configure one or more values of the second timer (e.g., a single value of the second timer) for each BWP in one or more serving cells. In addition, information for configuring one or more values of the second timer may be configured for each DCI format. For example, information for configuring one or more values of the second timer may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, the information for configuring the one or more values of the second timer may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats. That is, in the event that UE102 receives DCI format a and/or DCI format D, the second timer for the one or more first values may be (re) started. Additionally, in case the UE102 receives DCI format B and/or DCI format E, the second timer of the one or more second values may be (re-) started. In addition, in case the UE102 receives DCI format C and/or DCI format F, the second timer of the one or more third values may be (re-) started. Here, the one or more values of the second timer (i.e., the second timer) may not be applied to the one or more predetermined DCI formats. Here, one or more predetermined DCI formats may be pre-specified by the specification and known information between the gNB160 and the UE 102.

In addition, one or more values of the second timer (i.e., the second timer) may be independently configured for one or more DL BWPs and one or more UL BWPs. For example, the gNB160 may configure one or more fourth values of the second timer (i.e., the second timer) for one or more DL BWPs. Also, in the event that one or more DL BWPs are activated, the UE102 may start (or restart) a second timer for the one or more DL BWPs. In addition, where one or more DCI formats on the activated DL BWP(s) are used to schedule PDSCH, UE102 may start (or restart) a second timer for the DL BWP(s). In addition, the UE102 may start (or restart) a second timer for the one or more DL BWPs in case one or more DCI formats of the one or more DL BWPs on the one or more DL BWPs are used for scheduling PDSCH for the activated one or more DL BWPs. Additionally, the gNB160 may configure one or more fifth values of the second timer (i.e., the second timer) for one or more UL BWPs. Also, in the event that one or more UL BWPs are activated, the UE102 may start (or restart) a second timer for the one or more UL BWPs. In addition, in the event that one or more DCI formats on the activated one or more UL BWPs are used to schedule PUSCH, UE102 may start (or restart) a second timer for the one or more UL BWPs. In addition, the UE102 may start (or restart) a second timer for the one or more UL BWPs in case one or more DCI formats of the one or more UL BWPs on the one or more UL BWPs are used for scheduling PUSCH for the activated one or more UL BWPs.

For example, a UE102 configured for operation in a BWP of a serving cell may be configured (e.g., by using PBCH (e.g., MIB, PDSCH (SIB 2 type (i.e., RMSI)), and/or dedicated RRC messages) for the serving cell) with a set of one or more BWPs (e.g., a set of DL BWPs) for one or more receptions by the UE102 in a DL bandwidth of the serving cell. In addition, a UE102 configured for operation in a BWP of a serving cell may be configured (e.g., by using PBCH (e.g., MIB, PDSCH (SIB 2 type (i.e., RMSI)), and/or dedicated RRC messages) for the serving cell) with a set of one or more BWPs (e.g., a set of UL BWPs) for one or more transmissions by the UE102 in the UL bandwidth of the serving cell. For example, for unpaired spectrum operation (i.e., linked spectrum operation), DL BWPs from a set of configured one or more DL BWPs may be linked to UL BWPs from a set of configured one or more UL BWPs, where the DL BWPs and the UL BWPs may have the same index in the respective sets. Here, the index may be configured by using PBCH (e.g., MIB, PDSCH (SIB 2 type (i.e., RMSI)) and/or dedicated RRC messages.

Here, for example, for each DL BWP or UL BWP in the DL BWP set or UL BWP set, respectively, the gNB160 may configure one or more parameters (e.g., subcarrier spacing (i.e., parameters), cyclic prefix, number of consecutive PRBs, offset of the first PRB of the DL BWP in the DL bandwidth and/or offset of the first PRB of the UL BWP in the UL bandwidth), for example, by using higher layer signals. That is, the gNB160 may transmit information for configuring the one or more parameters, e.g., by using higher layer signals. That is, for example, each DL BWP in the DL BWP set may have a different bandwidth (i.e., a different number of consecutive PRBs). In addition, each UL BWP in the UL BWP set may have a different bandwidth (i.e., a different number of consecutive PRBs). In addition, as described above, a search space (e.g., CSS and/or USS) may be configured (e.g., defined) for each DL BWP in the set of DL BWPs. In addition, for each UL BWP in the set of UL BWPs, the resources of the PUCCH (e.g., the set of resources for PUCCH transmission) may be configured and/or indicated as described in the systems and methods herein. In addition, for each UL BWP in the set of UL BWPs, the resources of the PUSCH (e.g., the set of resources for PUSCH transmission) may be configured and/or indicated as described in the systems and methods herein.

That is, for example, the UE102 may perform reception on the PDCCH and/or PDSCH in DL BWP based on the one or more parameters. Additionally, the UE102 may perform transmission on PUSCH and/or PUCCH in UL BWP based on the one or more parameters. That is, DLBWPs from a configured set of DL BWPs for DL reception (i.e., reception on PDCCH and/or PDSCH) may be configured (e.g., by using higher layer signals) and/or indicated (e.g., by using one or more DCI formats). In addition, UL BWPs for UL transmissions (i.e., transmissions on PUSCH and/or PUCCH) from the configured UL BWP set may be configured (e.g., by using higher layer signals) and/or indicated (e.g., by using one or more DCI formats). Here, as described above, the set of control resources (i.e., CSS and/or USS) of the search space may be configured (e.g., defined) for the initially activated DL BWP(s) and/or the default DL BWP(s). For example, the initially activated DL BWP defined by the location and number of one or more consecutive PRBs, the subcarrier spacing, and/or the cyclic prefix may be a DL BWP for a control resource set of the common search space. In addition, as described above, in the case where the BWP indicator is configured in (e.g., exists in) one or more DCI formats that schedule PDSCH (e.g., PDSCH reception), one or more values of the BWP indicator may be used to indicate activated DL BWP for DL reception from the configured DL BWP. In addition, where the BWP indicator is configured in (e.g., exists in) one or more DCI formats that schedule PUSCH (e.g., PUSCH transmissions), one or more values of the BWP indicator may be used to indicate activated UL BWP for UL transmissions from the configured UL BWP.

Additionally, for example, where a default BWP is configured (e.g., a default BWP for one or more serving cells (e.g., primary and/or secondary cells)) and a second timer is configured (e.g., a second timer indicating one or more values for one or more serving cells (e.g., primary and/or secondary cells)), for unpaired spectrum, if the UE102 detects one or more DCI formats indicating an activated DL BWP(s), the UE102 may initialize (e.g., start, restart) the second timer (e.g., one or more values for the second timer). In addition, where a default BWP (e.g., the default BWP for the primary cell) is configured and a second timer (e.g., a second timer indicating one or more values for the primary cell) is configured, for the paired spectrum, the UE102 may initialize the second timer (e.g., one or more values for the second timer) if the UE102 detects one or more DCI formats indicating one or more DL BWPs that are activated or one or more DCI formats indicating one or more UL BWPs that are activated. Additionally, in the event that UE102 does not detect one or more DCI formats, UE102 may increment a second timer (e.g., one or more values of the second timer) for the one or more DCI formats every PDCCH monitoring period. In addition, for one or more serving cells (e.g., a primary cell and/or a secondary cell), in the event that the UE102 does not detect one or more DCI formats indicating one or more active DL BWPs for the unpaired spectrum operation (e.g., for all corresponding consecutive PDCCH monitoring periods in all control resource sets the UE is configured to monitor PDCCH in the active DL BWPs, the period being equal to one or more values of the second timer), the UE102 may switch from the active DL BWP to the default DL BWP. That is, the second timer expires (i.e., the second timer is considered expired) if one or more values of the second timer are equal to the configured values (i.e., one or more values of the second timer configured by the gNB 160). In addition, for one or more serving cells (e.g., a primary cell and/or a secondary cell), the UE102 may switch from the active DL BWP to the default DL BWP if the UE102 does not detect one or more DCI formats indicative of one or more DL BWPs and/or one or more DCI formats indicative of one or more UL BWPs for the paired spectrum operation (e.g., for all corresponding consecutive PDCCH monitoring periods in all control resource sets the UE is configured to monitor PDCCH in the active DL BWP, the period being equal to one or more values of the second timer). In addition, in the event that the first activated DL BWP(s) are configured on one or more serving cells (i.e., primary and/or secondary cells), the UE102 may use the indicated DL BWP on the one or more serving cells as the first activated DL BWP on the one or more serving cells. Additionally, in the case where the UE102 is not performing measurements on a bandwidth within the DL BWP for the UE102, it may not be desirable for the UE102 to monitor the PDCCH.

That is, in the event that the UE102 detects one or more DCI formats indicating activated one or more BWPs (e.g., one or more DL BWPs and/or one or more UL BWPs), the UE102 may initialize (e.g., start, (re) start) a second timer (e.g., one or more values of the second timer). For example, in the event that UE102 detects one or more DCI formats indicating activated BWPs within a second timer (e.g., the running of the second timer), UE102 may initialize the second timer. For example, in the event that UE102 detects one or more DCI formats within the second timer indicating activation of one or more BWPs, UE102 may initialize a second timer associated with the one or more BWPs (e.g., one or more DL BWPs activated by using the one or more DCI formats, one or more UL BWPs activated by using the one or more DCI formats, and/or one or more UL BWPs paired with the one or more DL BWPs activated by the one or more DCI formats). In addition, in the event that UE102 detects one or more DCI formats for scheduling PDSCH in the one or more BWPs (i.e., one or more DCI formats for the one or more BWPs) within the timer, UE102 may initialize a second timer associated with the one or more BWPs (e.g., the one or more DL BWPs in which PDSCH is scheduled and/or the one or more UL BWPs paired with the one or more DL BWPs in which PDSCH is scheduled). In addition, in the event that UE102 detects one or more DCI formats for scheduling PUSCH in one or more BWPs (i.e., one or more DCI formats for one or more BWPs) within a timer, UE102 may initialize a second timer associated with the one or more BWPs (e.g., one or more UL BWPs in which PUSCH is scheduled).

Here, the one or more DCI formats detected by the UE102 to initialize the second timer may be only one or more scheduling DCI formats (i.e., DCI format A, DCI format B, DCI format D and/or DCI format E). That is, UE102 may initialize a second timer associated with one or more BWPs only if UE102 detects one or more scheduling DCI formats for the one or more BWPs within the second timer. That is, in the event that UE102 detects one or more DCI formats other than one or more scheduling DCI formats for one or more BWPs, UE102 may not initialize the second timer associated with the one or more BWPs. Additionally, in the event that UE102 detects one or more fallback DCI formats (i.e., DCI format B and/or DCI format E) for one or more BWPs, UE102 may not initialize the second timer associated with the one or more BWPs. That is, UE102 may initialize the second timer associated with the one or more BWPs only if UE102 detects DCI format a and/or DCI format D for the one or more BWPs.

In addition, in the event that the UE102 does not detect one or more DCI formats indicating the activated one or more BWPs (e.g., one or more DL BWPs and/or one or more UL BWPs) within the second timer (e.g., in the event that the second timer expires, assuming the second timer expires), the UE102 may switch from the activated one or more BWPs to the one or more default BWPs. For example, in the event that the UE102 does not detect one or more DCI formats for scheduling PDSCH in one or more BWPs (i.e., one or more DCI formats for one or more BWPs), the UE102 may switch from the activated one or more BWPs to one or more default BWPs. In addition, in the event that the UE102 does not detect one or more DCI formats for scheduling PUSCH in one or more BWPs (i.e., one or more DCI formats for one or more BWPs), the UE102 may switch from the activated one or more BWPs to one or more default BWPs. That is, in the event that the second timer expires (i.e., in the event that the second timer is deemed to have expired), the UE102 may switch from the active BWP(s) (DL BWP(s) active and/or UL BWP(s) active) to the default BWP(s) (default DL BWP(s) and/or default UL BWP (s)).

Fig. 6 illustrates another example of downlink and/or uplink transmissions. Here, in the event that UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs, UE102 may extend (e.g., increase) the second timer associated with the one or more BWPs. For example, in the event that the UE102 detects one or more DCI formats for scheduling PDSCH in the one or more DL BWPs (i.e., one or more DCI formats for the one or more DL BWPs) and a second timer associated with the one or more DL BWPs expires before reception on PDSCH in the one or more DL BWPs, the UE102 may extend the second timer associated with the one or more DL BWPs. In addition, in the event that the UE102 detects one or more DCI formats for scheduling PDSCH in one or more DL BWPs (i.e., one or more DCI formats for one or more DL BWPs) and a second timer associated with one or more DL BWPs and/or one or more UL BWPs (e.g., one or more UL BWPs linked to the one or more DL BWPs) expires prior to reception on PDSCH in the one or more DL BWPs, the UE102 may extend the second timer associated with the one or more DL BWPs and/or one or more UL BWPs (e.g., one or more UL BWPs linked to the one or more DL BWPs). In addition, in the event that the UE102 detects one or more DCI formats for scheduling PUSCH in one or more UL BWPs (i.e., one or more DCI formats for one or more UL BWPs) and a second timer associated with the one or more UL BWPs expires before transmission on PUSCH in the one or more UL BWPs, the UE102 may extend the second timer associated with the one or more UL BWPs.

Here, the one or more DCI formats detected by the UE102 to extend the second timer may be only one or more scheduling DCI formats (i.e., DCI format A, DCI format B, DCI format D and/or DCI format E). That is, UE102 may extend the second timer associated with the one or more BWPs only if UE102 detects the one or more scheduling DCI formats for the one or more BWPs and the second timer expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs. That is, in the event that UE102 detects one or more DCI formats other than one or more scheduling DCI formats (as described above) for one or more BWPs and a second timer expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs, UE102 may not extend the second timer associated with the one or more BWPs. Additionally, in the event that UE102 detects one or more fallback DCI formats (i.e., DCI format B and/or DCI format E) for one or more BWPs and a second timer expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs, UE102 may not extend the second timer associated with the one or more BWPs. That is, UE102 may extend the second timer associated with the one or more BWPs only if UE102 detects DCI format a and/or DCI format D for the one or more BWPs and the second timer expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs.

That is, in the event that the UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs, the UE102 may not switch from the activated one or more BWPs to the one or more default BWPs. That is, in the event that the UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs, the UE102 may initialize (e.g., reset, restart) the second timer associated with the one or more BWPs. That is, in the event that the UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before corresponding reception in the one or more BWPs and/or corresponding transmission in the one or more BWPs, the UE102 may initialize (e.g., reset, restart) the second timer associated with the one or more BWPs and perform corresponding reception in the one or more BWPs and/or corresponding transmission in the one or more BWPs. For example, in the event that the UE102 detects one or more DCI formats for one or more DL BWPs and a second timer associated with the one or more DL BWPs expires before reception on PDSCH in the one or more DL BWPs, the UE102 may initialize (e.g., reset, restart) the second timer associated with the one or more DL BWPs and perform reception on PDSCH in the DL BWPs. In addition, in the event that the UE102 detects one or more DCI formats for one or more UL BWPs and a second timer associated with one or more DL BWPs expires before transmission on the PUSCH in the one or more UL BWPs, the UE102 may initialize (e.g., reset, restart) the second timer associated with the one or more UL BWPs and perform transmission on the PUSCH in the UL BWPs.

Additionally, for example, in the event that UE102 detects (e.g., decodes) a PDSCH in one or more BWPs and a second timer associated with the one or more BWPs expires prior to transmission of HARQ-ACK in the one or more BWPs (i.e., HARQ-ACK for the PDSCH), UE102 may extend (e.g., extend) the second timer associated with the one or more BWPs. Here, in the event that UE102 detects (e.g., decodes) PDSCH in one or more BWPs and the second timer associated with the one or more BWPs expires prior to transmission of HARQ-ACK in the one or more BWPs (i.e., HARQ-ACK for PDSCH), UE102 may initialize (e.g., reset, restart) the second timer associated with the one or more BWPs. For example, in the event that the UE102 detects (e.g., decodes) the PDSCH in the one or more DL BWPs and the second timer associated with the one or more UL BWPs expires before transmission of HARQ-ACK (i.e., HARQ-ACK for PDSCH) in the one or more UL BWPs, the UE102 may initialize (e.g., reset, restart) the second timer associated with the one or more UL BWPs and perform transmission of HARQ-ACK in the one or more UL BWPs.

Here, in the event that the UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before corresponding reception in the one or more BWPs and/or corresponding transmission in the one or more BWPs, the UE102 may switch from the one or more BWPs (e.g., the activated one or more BWPs) to the one or more default BWPs after performing the corresponding reception in the one or more BWPs and/or corresponding transmission in the one or more BWPs. That is, in this case, the UE102 may switch from one or more BWPs (e.g., the activated one or more BWPs) to one or more default BWPs immediately after performing corresponding reception in the one or more BWPs and/or corresponding transmission in the one or more BWPs. For example, in this case, the UE102 may switch from one or more DL BWPs (e.g., activated one or more BWPs) to one or more default DL BWPs immediately after performing PDSCH reception in the one or more BWPs. Additionally, in this case, the UE102 may switch from one or more DL BWPs (e.g., activated one or more DL BWPs) and one or more UL BWPs (e.g., activated one or more UL BWPs) to one or more default DL BWPs and one or more default UL BWPs immediately after performing PDSCH reception in the one or more DL BWPs and the one or more UL BWPs. In addition, in this case, the UE102 may switch from one or more UL BWPs (e.g., activated one or more UL BWPs) to one or more default UL BWPs immediately after performing PUSCH transmission in the one or more UL BWPs.

In addition, in the event that UE102 detects (e.g., decodes) PDSCH in one or more BWPs (e.g., one or more active BWPs) and a second timer associated with the one or more BWPs expires before transmission of HARQ-ACK in the one or more BWPs (i.e., HARQ-ACK for PDSCH), UE102 may switch from the one or more BWPs to one or more default BWPs immediately after performing transmission of HARQ-ACK.

In addition, in the event that the UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before corresponding reception in the one or more BWPs and/or corresponding transmission in the one or more BWPs, the UE102 may perform corresponding reception in the one or more default BWPs and/or corresponding transmission on the one or more default BWPs. For example, in the event that UE102 detects one or more DCI formats used to schedule PDSCH in one or more DL BWPs (i.e., one or more DCI formats for one or more DL BWPs) and a second timer associated with the one or more DL BWPs expires prior to reception on PDSCH in the one or more DL BWPs, UE102 may perform corresponding reception on PDSCH in one or more default DL BWPs. In addition, in the event that UE102 detects one or more DCI formats used to schedule PDSCH in one or more DL BWPs (i.e., one or more DCI formats for one or more DL BWPs) and a second timer associated with one or more DL BWPs and/or one or more UL BWPs (e.g., one or more UL BWPs linked to the one or more DL BWPs) expires prior to corresponding reception on PDSCH in the one or more DL BWPs, UE102 may perform reception on PDSCH in the one or more default DL BWPs. In addition, in the event that the UE102 detects one or more DCI formats for scheduling a PUSCH in one or more UL BWPs (i.e., one or more DCI formats for one or more UL BWPs) and a second timer associated with the one or more UL BWPs expires before transmission on a PUSCH in the one or more UL BWPs, the UE102 may perform a corresponding transmission on a PUSCH in one or more default UL BWPs. Here, one or more default BWPs (e.g., one or more default DL BWPs and/or one or more default UL BWPs) may be activated. That is, one or more default BWPs (e.g., one or more default DL BWPs and/or one or more default UL BWPs) may be activated based on (e.g., for performing) reception on PDSCH (e.g., by reception on PDSCH scheduled using one or more DCI formats received in activated BWPs (e.g., activated BWP(s) other than default BWP (s)), etc.). In addition, one or more default BWPs (e.g., one or more default ul BWPs) may be activated based on (e.g., for performing) transmission on PUSCH (e.g., by using transmission on PUSCH scheduled using one or more DCI formats received in an activated BWP (e.g., activated BWP(s), DL BWP(s) activated in addition to the default BWP (s)).

In addition, where UE102 detects (e.g., decodes) PDSCH in one or more BWPs (e.g., one or more active BWPs) and a second timer associated with the one or more BWPs expires prior to transmission of HARQ-ACK in the one or more BWPs (i.e., HARQ-ACK for PDSCH), UE102 may perform corresponding transmission of HARQ-ACK in one or more default UL BWPs. That is, one or more default BWPs (e.g., one or more default UL BWPs) may be activated based on (e.g., for performing) transmission of HARQ-ACKs (e.g., transmission of HARQ-ACKs for PDSCH received in activated BWP(s) (e.g., activated BWP(s), DL BWP(s) activated in addition to default BWP (s)).

Here, as described above, each of the BWPs may have a different bandwidth. That is, for example, the one or more default BWPs and the activated one or more BWPs (e.g., the activated one or more BWPs in addition to the one or more default BWPs) may have different bandwidths. That is, in the case where the UE102 switches from the activated one or more BWPs to the one or more default BWPs and the UE102 performs reception on the PDSCH in the one or more default BWPs, a re-interpretation for resource block allocation (i.e., one or more values of one or more resource block allocation fields, an index of resources indicated by using one or more DCI formats) may be required. For example, in case that the bandwidth of one or more default BWPs is 50MHz (e.g., the number of PRBs is 50) and the bandwidth of the activated BWP is 100MHz (e.g., the number of PRBs is 100), the resource block allocation indicating the index 80 for the activated BWP may not be applied to the one or more default BWPs. Here, for example, as described above, in the event that the UE102 detects one or more DCI formats for one or more BWPs and a second timer associated with the one or more BWPs expires before a corresponding reception in the one or more BWPs and/or a corresponding transmission in the one or more BWPs, the UE102 may reinterpret the index for the resource indicated by using the one or more DCI formats.

For example, in a case where the UE102 performs reception on a PDSCH in DL BWP1 (e.g., bandwidth of DL BWP1 is 50MHz, default DL BWP) scheduled by using one or more DCI formats received in DL BWP2 (e.g., bandwidth of DL BWP2 is 100MHz), the UE102 may determine a resource of a PDSCH (e.g., an index of the resource of the PDSCH) indicated by using the one or more DCI formats based on the bandwidth of DL BWP1 and/or the bandwidth of DL BWP 2. That is, UE102 may determine resources of PDSCH in DL BWP1 based on the number of PRBs of DL BWP1 (e.g., 50) and/or the number of PRBs of DL BWP2 (e.g., 100). For example, in case that the bandwidth of DL BWP1 is 50MHz (e.g., the number of PRBs is 50) and the bandwidth of DL BWP2 is 100MHz (e.g., the number of PRBs is 100), the resource block allocation indicating the index 80 for DL BWP2 may be interpreted as the index 40 in DL BWP 1. That is, for example, a ratio of a bandwidth of DL BWP1 to a bandwidth of DL BWP2 may be used to determine resources of PDSCH (e.g., an index of the resources of PDSCH).

In addition, for example, in a case where the UE102 performs transmission on a PUSCH in UL BWP1 (e.g., bandwidth of UL BWP1 is 50MHz, default UL BWP) scheduled by using one or more DCI formats for scheduling the PUSCH in UL BWP2 (e.g., bandwidth of UL BWP2 is 100MHz), the UE102 may determine resources of the PUSCH (e.g., index of resources of the PUSCH) indicated by using the one or more DCI formats based on the bandwidth of UL BWP1 and/or the bandwidth of UL BWP 2. That is, the UE102 may determine the resources of the PUSCH in UL BWP1 based on the number of PRBs of UL BWP1 (e.g., 50) and/or the number of PRBs of UL BWP2 (e.g., 100). For example, in case that the bandwidth of UL BWP1 is 50MHz (e.g., the number of PRBs is 50) and the bandwidth of UL BWP2 is 100MHz (e.g., the number of PRBs is 100), the resource block allocation indicating the index 80 for UL BWP2 may be interpreted as the index 40 in UL BWP 1. That is, for example, a ratio of the bandwidth of UL BWP1 to the bandwidth of UL BWP2 may be used to determine resources of PUSCH (e.g., an index of the resources of PUSCH).

Additionally, for example, UE102 may perform transmission of HARQ-ACKs in UL BWP1 (e.g., UL BWP1 with a bandwidth of 50MHz, default UL BWP) for PDSCH received in UL BWP2 (e.g., UL BWP2 with a bandwidth of 100 MHz). In addition, in this case, the UE102 may determine resources of the PUSCH in UL BWP1 and/or PUCCH in UL BWP1 (e.g., an index of the resources of the PUSCH in UL BWP1 and/or PUCCH in BWP 1) based on the bandwidth of UL BWP1 and/or the bandwidth of UL BWP2 for transmitting HARQ-ACKs. That is, the UE102 may determine the resources of the PUSCH and/or the resources of the PUCCH in UL BWP1 based on the number of PRBs of UL BWP1 (e.g., 50) and/or the number of PRBs of UL BWP2 (e.g., 100). For example, in case that the bandwidth of UL BWP1 is 50MHz (e.g., the number of PRBs is 50) and the bandwidth of UL BWP2 is 100MHz (e.g., the number of PRBs is 100), the resource block allocation indicating the index 80 for UL BWP2 may be interpreted as the index 40 in UL BWP 1. That is, for example, a ratio of a bandwidth of UL BWP1 to a bandwidth of UL BWP2 may be used to determine resources of PUSCH and/or PUCCH (e.g., indices of the resources of PUSCH and/or PUCCH).

Here, as uplink transmission (e.g., transmission on PUSCH), a configuration-based grant transmission and a dynamic scheduling-based transmission may be defined. Here, the transmission based on the configured grant may include a transmission on a PUSCH that is semi-persistently scheduled (i.e., semi-persistent scheduling, UL SPS). In addition, the transmission based on the configured grant may include transmission on PUSCH without UL grant (i.e., grant-free scheduling, GF). Here, the transmission on PUSCH without UL grant may include type 1 GF transmission and/or type 2 GF transmission. In addition, type 1 GF transmissions and/or type 2 GF transmissions may support repetition (i.e., repetition of transmissions). That is, the transmissions based on the configured grant may include UL SPS transmissions, GF transmissions (e.g., type 1 GF transmissions and/or type 2 GF transmissions).

For example, UL SPS transmissions may be supported based on RRC configuration and activation by using one or more DCI formats with SPS C-RNTI. For example, the gNB160 may configure the periodicity for UL SPS transmissions by using RRC signals. Additionally, the gNB 16-may indicate activation for UL SPS transmission by using one or more DCI formats with SPS C-RNTI. Also, the UE102 may perform UL SPS transmission on the PUSCH. In addition, type 1 GF transmission may be supported based on RRC configuration. For example, the gNB160 may configure the periodicity for type 1 GF transmissions by using RRC signals. Also, the UE102 may perform type 1 GF transmission (e.g., one or more repetitions) on the PUSCH. In addition, type 2 GF transmission may be supported based on RRC configuration and activation by using one or more DCI formats with GF C-RNTI. For example, the gNB160 may configure the periodicity for type 2 GF transmissions by using RRC signals. Additionally, the gNB 16-may indicate activation for UL SPS transmission by using one or more DCI formats with GF C-RNTI. Also, the UE102 may perform type 2 GF transmission on PUSCH. In addition, dynamic scheduling based transmission may be supported based on one or more DCI formats with C-RNTI. As described above, the UE102 may perform transmission on a PUSCH scheduled by using one or more DCI formats with a C-RNTI.

Here, the transmission of the configuration-based grant may be performed in one or more slots and/or one or more symbols. Additionally, the transmission based on the dynamic scheduling may be performed in one or more time slots and/or one or more symbols. Here, the same timing may include coincidence between transmission based on the configured grant in one or more slots and/or one or more symbols and transmission based on dynamic scheduling in one or more slots and/or one or more symbols. That is, transmission based on a configured grant in one or more slots and/or one or more symbols may partially overlap with transmission based on dynamic scheduling in one or more slots and/or one or more symbols. In addition, transmission based on the configured grant in one or more time slots and/or one or more symbols may partially overlap with transmission based on dynamic scheduling in one or more time slots and/or one or more symbols.

Also, in the event that the configuration-based grant transmission is in the active BWP1 (e.g., the default BWP) and the dynamic grant-based transmission is in the active BWP2, the UE102 may perform the dynamic grant-based transmission in the active BWP 2. That is, in the event that the configuration-based grant transmission is in the active BWP1 (e.g., the default BWP) and the dynamic grant-based transmission is in the active BWP2, the UE102 may discard the dynamic grant-based transmission in the active BWP 1. That is, transmissions based on dynamic grants may be prioritized over transmissions based on configuration-based grants. Additionally, the UE102 may perform the transmission of the configuration-based grant in the active BWP1 with the transmission of the configuration-based grant in the active BWP1 (e.g., the default BWP) and the transmission of the dynamic grant in the active BWP 2. That is, in the event that the configuration-based grant transmission is in the active BWP1 (e.g., the default BWP) and the dynamic grant-based transmission is in the active BWP2, the UE102 may discard the dynamic grant-based transmission in the active BWP 2. That is, transmissions based on the configuration based grant may be prioritized over transmissions based on the dynamic grant.

Here, as described above, the gNB160 may configure one or more information as described above by using the first message, e.g., PBCH (e.g., MIB) and/or PDSCH (e.g., SIB2 type (i.e., RMSI)). In addition, the gNB160 may configure the one or more information (i.e., the same one or more information) by using a second message (e.g., a dedicated RRC message). For example, as described above, the one or more information may include information for configuring the CSS (e.g., a region of the CSS, one or more CORESETs of the CSS). Additionally, the one or more information may include information for configuring the USS (e.g., region of the USS, one or more CORESET of the USS). In addition, the one or more information may include information for configuring one or more occasions (e.g., PDCCH monitoring periodicity, one or more PDCCH monitoring occasions). Additionally, the one or more information may include information for configuring one or more serving cells. In addition, the one or more information may include information for configuring one or more BWPs. Additionally, the one or more information may include information for configuring one or more default BWPs and/or one or more initial active BWPs. In addition, the one or more information may include information for configuring one or more BWPs in one or more serving cells. In addition, information for configuring a link between one or more UL BWPs and one or more DL BWPs.

Here, in the case where one or more information (e.g., one or more first values of the one or more information) are configured by using the first message and one or more information (e.g., one or more second values of the one or more information) are configured by using the second message, the UE102 may use the one or more information (e.g., one or more second values of the one or more information) configured by using the second message. That is, one or more first values of one or more information configured by using the first message may be overwritten by one or more second values of one or more information configured by using the second message. Here, in the case where information (e.g., one or more first values of one or more information) is configured by using the first message and information is not configured by using the second message (e.g., one or more second values without one or more information), the UE102 may use the one or more information (e.g., one or more first values of one or more information) configured by using the first message. In addition, the UE102 may use the one or more information (e.g., the one or more second values of the one or more information) configured by using the first message without configuring the information (e.g., the one or more first values of the one or more information) by using the first message and without configuring the information (e.g., the one or more second values of the one or more information) by using the second message. In addition, where one or more information (e.g., one or more first values of the one or more information) is configured by using the first message and one or more information (e.g., one or more second values of the one or more information) is configured by using the second message, the UE102 may use the one or more information (e.g., the one or more first values of the information) configured by using the first message. That is, one or more second values of one or more information configured by using the second message may be overwritten by one or more first values of one or more information configured by using the first message.

Fig. 7 shows an example of a CSI request field. As described above, the CSI request (i.e., the one or more CSI request fields) may be included in one or more DCI formats. Here, the CSI request may be used to request (e.g., direct, indicate, trigger) transmission of CSI on PUSCH and/or PUCCH. Herein, transmission of CSI requested by using one or more DCI formats may be referred to as aperiodic CSI reporting (i.e., making aperiodic CSI reports). For example, CSI requests included in one or more DCI formats for downlink may be used to request transmission of CSI on PUCCH. In addition, CSI requests included in one or more DCI formats for uplink may be used to request transmission of CSI on PUCCH. In addition, CSI requests included in one or more DCI formats for the uplink may be used to request transmission of CSI on the PUSCH. For example, in the case where a CSI request (i.e., one or more CSI request fields) is set to trigger (e.g., set to a positive CSI request) aperiodic CSI reporting, the UE102 may perform aperiodic CSI reporting using PUSCH and/or PUCCH. For example, based on detecting one or more DCI formats in slot n, UE102 may perform aperiodic CSI reporting in slot n + Y using PUSCH and/or PUCCH. Here, one or more values of Y may be indicated by using one or more DCI formats. That is, information indicating a value of Y may be included in one or more DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format D, DCI format E and/or DCI format F). Here, for DCI format B, DCI format C, DCI format E and/or DCI format F, the value of Y may be defined as one or more predetermined values (i.e., Y-4). Here, one or more predetermined values for Y may be pre-specified by specifications and known information between the gNB160 and the UE 102.

Here, the gNB160 may configure more than one value (e.g., more than one value for Y) by using higher layer signals and indicate one value of Y from the more than one value by using one or more DCI formats. For example, the gNB160 may transmit a higher layer signal (e.g., an RRC message) that includes information to configure more than one value (e.g., four values for Y). Further, the gNB160 may transmit one or more DCI formats including information indicating one Y value of the more than one values (e.g., four values for Y) (i.e., one or more DCI formats including one or more CSI request fields set to trigger aperiodic CSI reporting). Also, the UE102 may perform aperiodic CSI reporting in slot n + Y using PUSCH and/or PUCCH based on one Y value indicated from the more than one values.

Here, information for configuring the more than one value (e.g., more than one value for Y) may be configured for each serving cell. That is, the information for configuring the more than one value (e.g., more than one value for Y) may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring the more than one value (e.g., more than one value for Y) may be configured for each BWP (e.g., each BWP in the serving cell). That is, information for configuring the more than one value (e.g., more than one value for Y) may be configured for each BWP in the serving cell. In addition, information for configuring the more than one value (e.g., more than one value for Y) may be configured for the DCI format. For example, information for configuring the more than one value (e.g., more than one value for Y) may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, information for configuring more than one value (e.g., more than one value for Y) may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats.

Here, upon receiving (e.g., decoding, detecting) one or more DCI formats for the serving cell (i.e., one or more DCI formats including one or more CSI request fields set to trigger aperiodic reporting), the UE102 may perform aperiodic CSI reporting on the serving cell using PUSCH and/or PUCCH. In addition, upon receiving one or more DCI formats (i.e., one or more DCI formats including one or more CSI request fields set to trigger aperiodic reporting) for BWP (e.g., DL BWP in serving cell and/or UL BWP in serving cell), the UE102 may perform aperiodic CSI reporting on BWP (e.g., UL BWP in serving cell) using PUSCH and/or PUCCH. Here, CSI (e.g., aperiodic CSI reports and/or periodic CSI reports) may be transmitted only on one or more active BWPs (e.g., one or more active UL BWPs in one or more active serving cells). For example, upon receiving DCI format D for BWP (e.g., DL BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on BWP (e.g., UL BWP) in the serving cell using PUSCH. In addition, upon receiving DCI format a and/or DCI format D for BWP (e.g., dl BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on BWP (e.g., UL BWP) in the serving cell using PUCCH.

In addition, upon receiving one or more DCI formats (i.e., one or more DCI formats including one or more CSI request fields set to trigger aperiodic reporting) for BWP (e.g., DL BWP in serving cell and/or UL BWP in serving cell), the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP in serving cell) using PUSCH and/or PUCCH. For example, in the case of receiving DCI format D for BWP (e.g., DL BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP) in the serving cell using PUSCH. In addition, upon receiving DCI format a and/or DCI format D for BWP (e.g., DL BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP) in the serving cell using PUCCH. In addition, upon receiving DCI format E for BWP (e.g., dl BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP) in the serving cell using PUSCH. In addition, upon receiving DCI format B and/or DCI format E for BWP (e.g., DL BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP) in the serving cell using PUCCH. In addition, upon receiving DCI format F for BWP (e.g., DL BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP) in the serving cell using PUSCH. In addition, upon receiving DCI format C and/or DCI format F for BWP (e.g., DL BWP and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the default BWP (e.g., default UL BWP b) in the serving cell using PUCCH.

In addition, upon receiving one or more DCI formats (i.e., including one or more DCI formats set to one or more CSI request fields that trigger aperiodic reporting) for BWP (e.g., initial active DL BWP in serving cell, initial active UL BWP in serving cell, and/or UL BWP in serving cell), UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP in serving cell) using PUSCH and/or PUCCH. For example, upon receiving DCI format D for BWP (e.g., initial active DL BWP, initial active UL BWP, and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP) in the serving cell using PUSCH. For example, upon receiving DCI format a and/or DCI format D for BWP (e.g., initial active DL BWP, initial active UL BWP, and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP) in the serving cell using PUCCH. In addition, upon receiving DCI format E for BWP (e.g., initial active DL BWP, initial active UL BWP, and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP) in the serving cell using PUSCH. In addition, upon receiving DCI format B and/or DCI format E for BWP (e.g., initial active DL BWP, initial active UL BWP, and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP) in the serving cell using PUCCH. In addition, upon receiving DCI format F for BWP (e.g., initial active DL BWP, initial active UL BWP, and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP) in the serving cell using PUSCH. In addition, upon receiving DCI format C and/or DCI format F for BWP (e.g., initial active DL BWP, initial active UL BWP, and/or UL BWP) in the serving cell, the UE102 may perform aperiodic CSI reporting on the initial active BWP (e.g., initial active UL BWP) in the serving cell using PUCCH.

As described above, aperiodic CSI (i.e., aperiodic CSI report) may be transmitted on the serving cell using PUSCH and/or PUCCH. In addition, the aperiodic CSI may be transmitted on BWPs (e.g., active BWPs, default BWPs, and/or initial active BWPs) in the serving cell using PUSCH and/or PUCCH. In addition, the aperiodic CSI may be transmitted using the scheduling resources of the PUSCH and/or the scheduling resources of the PUCCH, for example. That is, the UE102 may perform aperiodic CSI reporting using resources of PUSCH scheduled by using one or more DCI formats (i.e., corresponding one or more DCI formats including one or more CSI request fields set to trigger aperiodic reporting). In addition, UE102 may perform aperiodic CSI reporting using resources of PUCCH scheduled by using one or more DCI formats (i.e., corresponding DCI formats including one or more CSI request fields set to trigger aperiodic reporting).

For example, upon receiving DCI format D (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the scheduled resources of PUSCH. In addition, upon receiving DCI format a and/or DCI format D (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the scheduled resource of PUCCH. In addition, upon receiving DCI format E (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the scheduled resource of PUSCH. In addition, upon receiving DCI format B and/or DCI format E (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the scheduled resource of PUCCH. Here, as described above, the BWP may include an activated BWP (e.g., an activated UL BWP), a default BWP (e.g., a default UL BWP), and/or an initially active BWP (e.g., an initially active UL BWP).

In addition, the aperiodic CSI may be transmitted using the configured resources of the PUSCH and/or the configured resources of the PUCCH, for example. That is, for example, the UE102 may perform aperiodic CSI reporting using resources of the PUSCH configured by using a higher layer signal (e.g., RRC message). In addition, the UE102 may perform aperiodic CSI reporting using resources of the PUCCH configured by using a higher layer signal (e.g., RRC message). That is, the gNB160 may transmit a higher layer signal (e.g., RRC message) including information for configuring resources of the PUSCH for transmitting aperiodic CSI (i.e., for aperiodic CSI reporting).

Here, information for configuring resources of the PUSCH may be configured for each serving cell. That is, the information for configuring resources of the PUSCH may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring resources of the PUSCH may be configured for each BWP (e.g., for each BWP in the serving cell). That is, information for configuring resources of the PUSCH may be configured for each BWP in the serving cell. In addition, information for configuring resources of PUSCH may be configured for each DCI format. For example, information for configuring resources of PUSCH may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, the information for configuring the resources of the PUSCH may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats.

In addition, the gNB160 may transmit a higher layer signal (e.g., RRC message) including information for configuring resources of a PUCCH for transmitting aperiodic CSI (i.e., for aperiodic CSI reporting). Here, information for configuring resources of the PUCCH may be configured for each serving cell. That is, information for configuring resources of the PUCCH may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring resources of the PUCCH may be configured for each BWP (e.g., for each BWP in the serving cell). That is, information for configuring resources of the PUCCH may be configured for each BWP in the serving cell. In addition, information for configuring resources of the PUCCH may be configured for each DCI format. For example, information for configuring resources of the PUCCH may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, information for configuring resources of the PUCCH may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats.

For example, upon receiving DCI format D (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using configured resources of PUSCH. In addition, upon receiving DCI format a and/or DCI format D (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the configured resources of PUCCH. In addition, upon receiving DCI format E (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using configured resources of PUSCH. In addition, upon receiving DCI format B and/or DCI format E (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the configured resources of PUCCH. In addition, upon receiving DCI format F (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using configured resources of PUSCH. In addition, upon receiving DCI format C and/or DCI format F (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using the configured resources of PUCCH. Here, as described above, the BWPs may include an active BWP (e.g., an active UL BWP), a default BWP (e.g., a default UL BWP), and/or an initially active BWP (e.g., an initially active UL BWP).

In addition, the gNB160 may configure more than one resource by using higher layer signals and indicate one of the more than one resource by using one or more DCI formats. For example, the gNB160 may transmit a higher layer signal (e.g., RRC message) that includes information for configuring more than one resource of the PUSCH (e.g., four resources of the PUSCH). Further, the gNB 106 may transmit one or more DCI formats including information indicating one resource of PUSCH out of more than one resource of PUSCH (e.g., four resources of PUSCH). Also, the UE102 may perform aperiodic CSI reporting using one resource of PUSCH indicated by using one or more DCI formats. That is, the one or more DCI formats may include information indicating one resource of the PUSCH from among more than one resource of the PUSCH.

Here, information for configuring more than one resource of the PUSCH (e.g., four resources of the PUSCH) may be configured for each serving cell. That is, information for configuring more than one resource of PUSCH (e.g., four resources of PUSCH) may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring more than one resource (e.g., four resources of PUSCH) of the PUSCH may be configured for each BWP (e.g., each BWP in the serving cell). That is, information for configuring more than one resource of the PUSCH (e.g., four resources of the PUSCH) may be configured for each BWP in the serving cell. In addition, information for configuring more than one resource of the PUSCH (e.g., four resources of the PUSCH) may be configured for each DCI format. For example, information for configuring more than one resource of PUSCH (e.g., four resources of PUSCH) may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, information for configuring more than one resource of PUSCH (e.g., four resources of PUSCH) may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats.

In addition, for example, the gNB160 may transmit a higher layer signal (e.g., RRC message) including information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH). Further, the gNB 106 may transmit one or more DCI formats including information indicating one resource of the PUCCH of more than one resource of the PUCCH (e.g., four resources of the PUCCH). Also, the UE102 may perform aperiodic CSI reporting using one resource of PUCCH indicated by using one or more DCI formats. That is, the one or more DCI formats may include information indicating one resource of the PUCCH from among more than one resource of the PUCCH.

Here, information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH) may be configured for each serving cell. That is, information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH) may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring more than one resource (e.g., four resources of the PUCCH) of the PUCCH may be configured for each BWP (e.g., each BWP in the serving cell). That is, information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH) may be configured for each BWP in the serving cell. In addition, information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH) may be configured for each DCI format. For example, information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH) may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, information for configuring more than one resource of the PUCCH (e.g., four resources of the PUCCH) may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats.

For example, upon receiving DCI format D (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using one resource of PUSCH (i.e., one resource of PUSCH indicated from more than one resource of PUSCH). In addition, upon receiving DCI format a and/or DCI format D (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using one resource of PUCCH (i.e., one resource of PUCCH indicated from more than one resource of PUCCH). In addition, upon receiving DCI format E (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using one resource of PUSCH (i.e., one resource of PUSCH indicated from more than one resource of PUSCH). In addition, upon receiving DCI format B and/or DCI format E (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using one resource of PUCCH (i.e., one resource of PUCCH indicated from more than one resource of PUCCH). In addition, upon receiving DCI format F (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using one resource of PUSCH (i.e., one resource of PUSCH indicated from more than one resource of PUSCH). In addition, upon receiving DCI format C and/or DCI format F (i.e., including a CSI request field set to trigger aperiodic reporting), UE102 may perform aperiodic CSI reporting on BWP in the serving cell using one resource of PUCCH (i.e., one resource of PUCCH indicated from more than one resource of PUCCH). Here, as described above, the BWP may include an activated BWP (e.g., an activated UL BWP), a default BWP (e.g., a default UL BWP), and/or an initially active BWP (e.g., an initially active UL BWP).

In addition, for example, aperiodic CSI may be transmitted using resources of PUSCH determined based on the CORESET of PDCCH (e.g., index of CORESET of PDCCH (e.g., number of CORESETs), minimum index of CORESET of PDCCH (e.g., minimum number of CORESETs, number of first CORESETs), one or more locations of CORESET of PDCCH). In addition, the aperiodic CSI may be transmitted using a resource of the PUCCH determined based on the CORESET of the PDCCH (e.g., an index of the CORESET of the PDCCH (e.g., the number of CORESETs), a minimum index of the CORESET of the PDCCH (e.g., the minimum number of CORESETs, the number of first CORESETs), one or more locations of the CORESET of the PDCCH).

In addition, the aperiodic CSI may be transmitted using resources of the PUSCH determined based on one or more control channel elements of the PDCCH (e.g., an index of the one or more control channel elements of the PDCCH (e.g., a number of the control channel elements), a minimum index of the one or more control channel elements of the PDCCH (e.g., a minimum number of the one or more control channel elements, a number of the one or more first control channel elements), one or more locations of the one or more control channel elements of the PDCCH). In addition, the aperiodic CSI may be transmitted using resources of the PUCCH determined based on one or more control channel elements of the PDCCH (e.g., an index of one or more control channel elements of the PDCCH (e.g., a number of one or more control channel elements), a minimum index of one or more control channel elements of the PDCCH (e.g., a minimum number of one or more control channel elements, a number of one or more first control channel elements), one or more locations of one or more control channel elements of the PDCCH).

In addition, aperiodic CSI may be transmitted using resources of PUSCH determined based on one or more search spaces of PDCCH (e.g., an index of the one or more search spaces of PDCCH (e.g., a number of the one or more search spaces), a minimum index of the one or more search spaces of PDCCH (e.g., a minimum number of the one or more search spaces, a number of the one or more first search spaces), one or more locations of the one or more search spaces of PDCCH). In addition, aperiodic CSI may be transmitted using resources of the PUCCH determined based on one or more search spaces of the PDCCH (e.g., an index of the one or more search spaces of the PDCCH (e.g., a number of the one or more search spaces), a minimum index of the one or more search spaces of the PDCCH (e.g., a minimum number of the one or more search spaces, a number of the one or more first search spaces), one or more locations of the one or more search spaces of the PDCCH). Here, the PDCCH may include a PDDCH for transmitting one or more DCI formats (i.e., including one or more DCI formats set to trigger a CSI request for aperiodic CSI reporting). In addition, the search space may include a UE-specific search space and/or a common search space (i.e., a search space common to UEs).

That is, resources for PUSCH for aperiodic CSI reporting may be determined based on PDCCH (e.g., core of PDCCH, one or more control channel elements of PDCCH, and/or search space of PDCCH). Here, resources for PUSCH for aperiodic CSI reporting may be determined based on PDCCH and information configured by using a higher layer signal (e.g., RRC message). For example, the gNB160 may transmit a higher layer signal including information for configuring one or more values for determining resources of the PUSCH. Also, the UE102 may determine the resources of the PUSCH based on the PDCCH and by using one or more values configured by higher layer signals. That is, the resource of the PUSCH for aperiodic CSI reporting may be determined based on the PDCCH and by using one or more values configured by a higher layer signal.

Here, information for configuring one or more values may be configured for each serving cell. That is, the information for configuring the one or more values may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring one or more values may be configured for each BWP (e.g., each BWP in the serving cell). That is, information for configuring one or more values may be configured for each BWP in the serving cell. In addition, information for configuring one or more values may be configured for each DCI format. For example, information for configuring one or more values may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, the information for configuring the one or more values may be configured for each of the serving cells, each of the BWPs, and/or each of the DCI formats.

In addition, resources of the PUCCH for aperiodic CSI reporting may be determined based on the PDCCH (e.g., the core set of the PDCCH, one or more control channel elements of the PDCCH, and/or a search space of the PDCCH). Here, the resource of the PUCCH for aperiodic CSI reporting may be determined based on the PDCCH and information configured by using a higher layer signal (e.g., RRC message). For example, the gNB160 may transmit a higher layer signal including information for configuring one or more values for determining resources of the PUCCH. Also, the UE102 may determine the resources of the PUCCH based on the PDCCH and one or more values configured by using higher layer signals. That is, a resource of the PUCCH for aperiodic CSI reporting may be determined based on the PDCCH and one or more values configured by using a higher layer signal.

Here, information for configuring one or more values may be configured for each serving cell. That is, the information for configuring the one or more values may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring one or more values may be configured for each BWP (e.g., each BWP in the serving cell). That is, information for configuring one or more values may be configured for each BWP in the serving cell. In addition, information for configuring one or more values may be configured for each DCI format. For example, information for configuring one or more values may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E).

Here, the size of the one or more CSI request fields included in the one or more DCI formats may be 1 bit, 2 bits, and/or 3 bits. In the following, a 1-bit CSI request field, a 2-bit CSI request field, and/or a 3-bit CSI request field are described as examples of the size of one or more CSI request fields, although one or more different sizes of one or more CSI request fields are not excluded from the systems and methods herein.

For example, the size of the one or more CSI request fields included in the one or more DCI formats may be determined based on the number of configured serving cells or cells, the number of configured BWPs or cells, the DCI format or formats (i.e., DCI formats including the one or more CSI request fields), and/or the search space in which the DCI format or formats are detected (e.g., decoded to, received, mapped to). For example, a 2-bit field may be applied in the case where no more than five DL serving cells are configured, more than one DL serving cell is configured, and one or more DCI formats are mapped onto a UE-specific search space. In addition, in case that more than five DL serving cells are configured and one or more DCI formats are mapped onto the UE-specific search space, a 3-bit field may be applied. In addition, in case one DL serving cell is configured and/or one or more DCI formats are mapped on a common search space (i.e., a search space common to UEs), a 1-bit field may be applied. Here, the UE-specific search space can be given by using the C-RNTI.

In addition, for example, a 2-bit field may be applied in case more than one BWP is configured (e.g., more than one DL BWP) and/or one or more DCI formats are mapped onto the UE-specific search space. In addition, in case one BWP (e.g., one DL BWP) is configured and/or one or more DCI formats are mapped onto a common search space (i.e., a search space common to UEs), a 1-bit field may be applied. In addition, in case that the detected DCI format including one or more CSI request fields set to trigger aperiodic CSI reporting is DCI format a and/or DCI format D, a 1-bit field, a 2-bit field, and/or a 3-bit field may be applied. In addition, in case that the detected DCI format including one or more CSI request fields set to trigger aperiodic CSI reporting is DCI format B and/or DCI format E, only the 1-bit field and/or the 2-bit field may be applied. In addition, in case that the detected DCI format including one or more CSI request fields set to trigger aperiodic CSI reporting is DCI format C and/or DCI format F, only the 1-bit field and/or the 2-bit field may be applied.

Here, in case the size of the one or more CSI request fields is 1 bit, an aperiodic CSI report may be triggered for the serving cell. Here, triggering aperiodic CSI reporting for a serving cell may trigger aperiodic CSI reporting for a serving cell in which PDSCH and/or PUSCH is scheduled. For example, in the case where one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), the UE 102 may perform aperiodic CSI reporting for the DL serving cell in which the PDSCH is scheduled. In addition, in the case where one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), the UE 102 may perform aperiodic CSI reporting for the DL serving cell corresponding to the UL serving cell in which PUSCH is scheduled.

In addition, in case one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), aperiodic CSI reporting may be triggered for BWP. Here, triggering aperiodic CSI reporting for BWP may be triggering aperiodic CSI reporting for BWP in which PDSCH and/or PUSCH is scheduled. For example, in the case where one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), the UE 102 may perform aperiodic CSI reporting for DL BWPs in which PDSCH is scheduled. In addition, in case one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), the UE 102 may perform aperiodic CSI reporting for dl BWPs corresponding to (paired with, linked with) UL BWPs in which PUSCH is scheduled. Here, triggering aperiodic CSI reporting for one or more BWPs may be triggering aperiodic CSI reporting for one or more BWPs for which activation, deactivation, and/or handover is indicated. As described above, one or more DCI formats (e.g., one or more DCI formats including one or more CSI request fields set to trigger aperiodic CSI reporting) may be used for activation, deactivation, and/or switching of one or more BWPs. That is, for example, in the case where one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), the UE 102 may perform aperiodic CSI reporting for one or more DL BWPs for which activation, deactivation, and/or handover is indicated. In addition, in the case where one or more CSI request fields are set to trigger aperiodic CSI reporting (e.g., one or more 1-bit CSI request fields are set to trigger aperiodic CSI reporting), the UE 102 may perform aperiodic CSI reporting for one or more DL BWPs corresponding to (paired with, linked to) one or more UL BWPs for which activation, deactivation, and/or handover is indicated.

An example of a 2-bit CSI request field is shown in fig. 7 (a). In the case where the size of the one or more CSI request fields is 2 bits, the aperiodic CSI report may be triggered based on one or more values corresponding to the aperiodic CSI report (i.e., one or more values of the one or more CSI request fields). For example, in the case where one or more values of the one or more CSI request fields are "00" (e.g., the one or more CSI request fields are set to one or more first values), an aperiodic CSI report may not be triggered. In addition, where the one or more values of the one or more CSI request fields are "01" (e.g., the one or more CSI request fields are set to one or more second values), an aperiodic CSI report may be triggered for the serving cell. In addition, where the one or more values of the one or more CSI request fields are "10" (e.g., the one or more CSI request fields are set to one or more third values), aperiodic CSI reporting may be triggered for a first set of one or more serving cells configured by using higher layer signals (e.g., RRC messages). In addition, where the one or more values of the one or more CSI request fields are "11" (e.g., the one or more CSI request fields are set to one or more fourth values), aperiodic CSI reporting may be triggered for a second set of one or more serving cells configured by using higher layer signals (e.g., RRC messages). That is, the UE 102 may perform aperiodic CSI reporting for a set of one or more serving cells based on information configured by using higher layers and one or more values of one or more CSI request fields. In addition, in the event that one or more values of the one or more CSI request fields are "01" (e.g., the one or more CSI request fields are set to one or more second values), an aperiodic CSI report may be triggered for BWP. In addition, in case that one or more values of the one or more CSI request fields are "10" (e.g., the one or more CSI request fields are set to one or more third values), an aperiodic CSI report may be triggered for a first set of one or more BWPs in a serving cell c (e.g., a first set of one or more DL BWPs in the serving cell c (i.e., a single serving cell c)) configured by using a higher layer signal (e.g., an RRC message). In addition, in case that one or more values of the one or more CSI request fields are "11" (e.g., the one or more CSI request fields are set to one or more fourth values), aperiodic CSI reporting may be triggered for a second set of one or more BWPs in the serving cell c (e.g., a first set of one or more DL BWPs in the serving cell c (i.e., the same single serving cell c)) configured by using a higher layer signal (e.g., an RRC message). That is, the UE 102 may perform aperiodic CSI reporting for a set of one or more BWPs based on information configured by using a higher layer and one or more values of one or more CSI request fields.

That is, the UE 102 may perform aperiodic CSI reporting for one or more serving cells and/or a set of one or more BWPs based on information configured by using higher layers and one or more values of one or more CSI request fields. That is, the gNB160 may configure the first set of one or more serving cells and/or the second set of one or more serving cells. For example, the gNB160 may transmit a higher layer signal (e.g., an RRC message) that includes information for configuring a first set of one or more serving cells. In addition, the gNB160 may transmit a higher layer signal (e.g., an RRC message) that includes information for configuring the second set of one or more serving cells. That is, the gNB160 may transmit a higher layer signal including information indicating for which serving cell to trigger the aperiodic CSI report (e.g., in the case where the aperiodic CSI report is triggered by one or more values of a 2-bit CSI request field).

In addition, the gNB160 may configure a first set of one or more BWPs in the serving cell c (e.g., a first set of one or more DL BWPs) and/or a second set of one or more BWPs in the serving cell c (e.g., a second set of one or more DL BWPs). For example, the gNB160 may transmit a higher layer signal (e.g., an RRC message) including information for configuring a first set of one or more BWPs in the serving cell c. In addition, the gNB160 may transmit a higher layer signal (e.g., an RRC message) that includes a second set of one or more BWPs in the serving cell c. That is, the gNB160 may transmit a higher layer signal including information indicating for which BWP an aperiodic CSI report is triggered (e.g., in the case where the aperiodic CSI report is triggered by one or more values of a 2-bit CSI request field).

Here, for example, information for configuring a first set of one or more serving cells and/or information for configuring a second set of one or more serving cells may be configured for each serving cell. That is, the information for configuring the first set of one or more serving cells and/or the information for configuring the second set of one or more serving cells may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring a first set of one or more serving cells and/or information for configuring a second set of one or more serving cells may be configured for each BWP (e.g., each BWP in a serving cell). That is, the information for configuring the first set of one or more serving cells and/or the information for configuring the second set of one or more serving cells may be configured for each BWP in the serving cell. In addition, information for configuring a first set of one or more serving cells and/or information for configuring a second set of one or more serving cells may be configured for each DCI format. For example, information for configuring a first set of one or more serving cells and/or information for configuring a second set of one or more serving cells may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E).

In addition, for example, information for configuring a first set of one or more BWPs and/or information for configuring a second set of one or more BWPs may be configured for each serving cell. That is, the information for configuring the first set of one or more BWPs and/or the information for configuring the second set of one or more BWPs may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, information for configuring a first set of one or more BWPs and/or information for configuring a second set of one or more BWPs may be configured for each BWP (e.g., each BWP in the serving cell). That is, the information for configuring the first set of one or more BWPs and/or the information for configuring the second set of one or more BWPs may be configured for each BWP in the serving cell. In addition, information for configuring a first set of one or more BWPs and/or information for configuring a second set of one or more BWPs may be configured for each DCI format. For example, information for configuring a first set of one or more BWPs and/or information for configuring a second set of one or more BWPs may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, the information for configuring the first set of one or more serving cells and/or the information for configuring the second set of one or more serving cells may be configured for each of the serving cells, each of the BWPs, and each of the DCI formats.

An example of a 3-bit CSI request field is shown in fig. 7 (b). In the case where the size of the one or more CSI request fields is 3 bits, the aperiodic CSI report may be triggered based on one or more values corresponding to the aperiodic CSI report (i.e., one or more values of the one or more CSI request fields). For example, in the case where one or more values of the one or more CSI request fields are "000" (e.g., the one or more CSI request fields are set to one or more first values), an aperiodic CSI report may not be triggered. In addition, where the one or more values of the one or more CSI request fields are "001" (e.g., the one or more CSI request fields are set to one or more second values), an aperiodic CSI report may be triggered for the serving cell and/or BWP. In addition, in the case where one or more values of the one or more CSI request fields are "010" (e.g., the one or more CSI request fields are set to one or more third values), an aperiodic CSI report may be triggered for a third set of one or more serving cells and/or one or more BWPs configured by using a higher layer signal (e.g., an RRC message). In addition, in case that the one or more values of the one or more CSI request fields are "011" (e.g., the one or more CSI request fields are set to one or more fourth values), aperiodic CSI reporting may be triggered for a fourth set of one or more serving cells and/or one or more BWPs configured by using a higher layer signal (e.g., an RRC message). In addition, in case that one or more values of the one or more CSI request fields are "100" (e.g., the one or more CSI request fields are set to one or more fifth values), aperiodic CSI reporting may be triggered for a fifth set of one or more serving cells and/or one or more BWPs configured by using a higher layer signal (e.g., RRC message). In addition, in case that one or more values of the one or more CSI request fields are "101" (e.g., the one or more CSI request fields are set to one or more sixth values), aperiodic CSI reporting may be triggered for a sixth set of one or more serving cells and/or one or more BWPs configured by using a higher layer signal (e.g., an RRC message). In addition, in case that one or more values of the one or more CSI request fields are "110" (e.g., the one or more CSI request fields are set to one or more seventh values), aperiodic CSI reporting may be triggered for a seventh set of one or more serving cells and/or one or more BWPs configured by using a higher layer signal (e.g., RRC message). In addition, in case that one or more values of the one or more CSI request fields are "110" (e.g., the one or more CSI request fields are set to one or more eighth values), the aperiodic CSI report may be triggered for an eighth set of one or more serving cells and/or one or more BWPs configured by using a higher layer signal (e.g., an RRC message).

That is, the UE 102 may perform aperiodic CSI reporting for one or more serving cells and/or a set of one or more BWPs based on information configured by using higher layers and one or more values of one or more CSI request fields. That is, the gNB160 may configure a third set of one or more serving cells and/or one or more BWPs. For example, the gNB160 may transmit a higher layer signal (e.g., an RRC message) that includes information for configuring the third set of one or more serving cells and/or one or more BWPs. Additionally, the gNB160 may configure a fourth set of one or more serving cells and/or one or more BWPs. For example, the gNB160 may transmit a higher layer signal (e.g., an RRC message) that includes information for configuring the fourth set of one or more serving cells. Similar to the third and fourth sets, the fifth, sixth, seventh, and eighth sets may be configured by the gNB160 using higher layer signals (e.g., RRC messages). That is, the gNB160 may transmit a higher layer signal including information indicating for which serving cell and/or BWP an aperiodic CSI report is triggered (e.g., in the case where the aperiodic CSI report is triggered by one or more values of a 3-bit CSI request field).

Here, for example, information for configuring one or more sets (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) of one or more serving cells and/or one or more BWPs may be configured for each serving cell. That is, information for configuring one or more serving cells and/or one or more sets (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) of one or more BWPs may be configured for each of the serving cells (e.g., each of the primary cell and the one or more secondary cells). In addition, one or more serving cells and/or one or more sets (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) of one or more BWPs may be configured for each BWP (e.g., each BWP in a serving cell). That is, one or more sets (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) of one or more serving cells and/or one or more BWPs may be configured for each BWP in the serving cell. In addition, one or more sets (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) of one or more serving cells and/or one or more BWPs may be configured for each DCI format. For example, one or more sets of one or more serving cells and/or one or more BWPs (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) may be configured for each of the DCI formats (e.g., DCI format A, DCI format B, DCI format C, DCI format E and/or DCI format E). That is, one or more sets (e.g., a third set, a fourth set, a fifth set, a sixth set, a seventh set, and/or an eighth set) of one or more serving cells and/or one or more BWPs may be configured for each of the serving cells, each of the BWPs, and each of the DCI formats.

As described above, aperiodic CSI reporting may be triggered for one or more serving cells and/or BWPs. Here, aperiodic CSI reporting may be triggered for one or more activated serving cells. In addition, aperiodic CSI reporting may be triggered for one or more deactivated serving cells. In addition, aperiodic CSI reporting may be triggered for one or more active BWPs. In addition, aperiodic CSI reporting may be triggered for one or more deactivated BWPs. Here, aperiodic CSI reporting may be triggered for one or more active BWPs in one or more active serving cells. In addition, aperiodic CSI reporting may be triggered for one or more deactivated BWPs in one or more activated serving cells. That is, the aperiodic CSI report may not be triggered for one or more activated BWPs in one or more deactivated serving cells. In addition, the aperiodic CSI report may not be triggered for one or more deactivated BWPs in the one or more deactivated serving cells. That is, aperiodic CSI reporting may not be triggered for deactivated serving cells.

Fig. 8 illustrates various components that may be used in a UE 902. The UE902 described in connection with fig. 8 may be implemented in accordance with the UE 102 described in connection with fig. 1. The UE902 includes a processor 903 that controls the operation of the UE 902. The processor 903 may also be referred to as a Central Processing Unit (CPU). Memory 905 (which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination of the two, or any type of device that may store information) provides instructions 907a and data 909a to processor 903. A portion of the memory 905 may also include non-volatile random access memory (NVRAM). Instructions 907b and data 909b may also reside in the processor 903. The instructions 907b and/or data 909b loaded into the processor 903 may also include instructions 907a and/or data 909a from the memory 905 that are loaded for execution or processing by the processor 903. The instructions 907b may be executable by the processor 903 to implement the methods described above.

The UE902 may also include a housing that houses one or more transmitters 958 and one or more receivers 920 to allow transmission and reception of data. The one or more transmitters 958 and the one or more receivers 920 may be combined into one or more transceivers 918. One or more antennas 922a-n are attached to the housing and electrically coupled to the transceiver 918.

The various components of the UE902 are coupled together by a bus system 911 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for clarity, the various buses are illustrated in FIG. 8 as the bus system 911. The UE902 may also include a Digital Signal Processor (DSP)913 for processing signals. The UE902 may also include a communication interface 915 that provides user access to the functions of the UE 902. The UE902 shown in fig. 8 is a functional block diagram rather than a listing of specific components.

Fig. 9 shows various components that may be used in the gNB 1060. The gNB1060 described in connection with fig. 9 may be implemented in accordance with the gNB160 described in connection with fig. 1. The gNB1060 includes a processor 1003 that controls operation of the gNB 1060. The processor 1003 may also be referred to as a Central Processing Unit (CPU). Memory 1005 (which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination of the two, or any type of device that can store information) provides instructions 1007a and data 1009a to processor 1003. A portion of the memory 1005 may also include non-volatile random access memory (NVRAM). Instructions 1007b and data 1009b may also reside in the processor 1003. The instructions 1007b and/or data 1009b loaded into the processor 1003 may also include instructions 1007a and/or data 1009a from the memory 1005 that are loaded for execution or processing by the processor 1003. The instructions 1007b may be executed by the processor 1003 to implement the methods described above.

The gNB1060 may also include a housing that houses one or more transmitters 1017 and one or more receivers 1078 to allow transmission and reception of data. One or more transmitters 1017 and one or more receivers 1078 may be combined into one or more transceivers 1076. One or more antennas 1080a-n are attached to the housing and electrically coupled to the transceiver 1076.

The various components of the gNB1060 are coupled together by a bus system 1011 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are illustrated in FIG. 9 as bus system 1011. The gNB1060 may also include a Digital Signal Processor (DSP)1013 for processing signals. The gNB1060 may also include a communication interface 1015 that provides user access to the functionality of the gNB 1060. The gNB1060 shown in fig. 9 is a functional block diagram rather than a listing of specific components.

Fig. 10 is a block diagram illustrating one particular implementation of a UE 1102 in which systems and methods for downlink and/or uplink (re) transmission may be implemented. The UE 1102 comprises a transmitting means 1158, a receiving means 1120, and a controlling means 1124. The transmitting means 1158, receiving means 1120, and controlling means 1124 may be configured to perform one or more of the functions described in connection with fig. 1 above. Fig. 8 above shows an example of a specific device structure of fig. 10. Various other structures may be implemented to achieve one or more of the functions of fig. 1. For example, the DSP may be implemented by software.

Fig. 11 is a block diagram illustrating one particular implementation of a gNB 1260 in which systems and methods for downlink and/or uplink (re) transmission may be implemented. The gNB 1260 includes a transmitting device 1217, a receiving device 1278, and a control device 1282. The transmitting device 1217, receiving device 1278 and control device 1282 may be configured to perform one or more of the functions described in connection with fig. 1 above. Fig. 10 above shows an example of a specific device structure of fig. 11. Various other structures may be implemented to achieve one or more of the functions of fig. 1. For example, the DSP may be implemented by software.

Fig. 12 is a block diagram illustrating one implementation of a gNB 1260. The gNB 1260 may include a higher layer processor 1223, DL transmitter 1225, UL receiver 1233, and antennas 1231. The DL transmitter 1225 may include a PDCCH transmitter 1227 and a PDSCH transmitter 1229. UL receiver 1233 may include PUCCH receiver 1235 and PUSCH receiver 1237. The higher layer processor 1223 may manage the behavior of the physical layer (the behavior of the DL transmitter and UL receiver) and provide higher layer parameters to the physical layer. The higher layer processor 1223 may obtain the transport block from the physical layer. The higher layer processor 1223 may transmit/acquire higher layer messages, such as RRC messages and MAC messages, to/from the higher layer of the UE. The higher layer processor 1223 may provide a PDSCH transmitter 1229 transport block and provide PDCCH transmitter 1227 transmission parameters related to the transport block. The UL receiver 1233 may receive and demultiplex the multiplexed uplink physical channel and uplink physical signal via the reception antenna 1231. The PUCCH receiver 1235 may provide a higher layer processor UCI. The PUSCH receiver 1237 may provide the received transport block to a higher layer processor.

Fig. 13 is a block diagram illustrating one implementation of a UE 1302. The UE 1302 may include a higher layer processor 1323, an UL transmitter 1351, a DL receiver 1343, and an antenna 1331. UL transmitter 1351 may include a PUCCH transmitter 1353 and a PUSCH transmitter 1355. The DL receiver 1343 may include a PDCCH receiver 1345 and a PDSCH receiver 1347. The higher layer processor 1323 may manage the behavior of the physical layer (the behavior of the DL transmitter and UL receiver) and provide higher layer parameters to the physical layer. The higher layer processor 1323 may obtain transport blocks from the physical layer. The higher layer processor 1323 may transmit/acquire higher layer messages, such as RRC messages and MAC messages, to/from the higher layer of the UE. The higher layer processor 1323 may provide transport blocks to the PUSCH transmitter 1355 and UCI to the PUCCH transmitter 1353. The DL receiver 1343 may receive and demultiplex the multiplexed downlink physical channel and downlink physical signal via a reception antenna 1331. PDCCH receiver 1345 may provide higher layer processor 1323 DCI. The PDSCH receiver 1347 may provide the received transport blocks to the higher layer processor 1323.

Fig. 14 is a flowchart of a communication method of a User Equipment (UE) communicating with a base station apparatus on one or more downlink bandwidth parts (DL BWPs) in a serving cell. The method can include receiving 1402 a Radio Resource Control (RRC) message having first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity. The method can also include receiving 1404 an RRC message including second information for configuring more than one offset value. The method may also include 1406 monitoring the PDCCH based on the first information. The method may also include 1408 receiving a Downlink Control Information (DCI) format on the PDCCH including third information triggering an aperiodic Channel State Information (CSI) report and fourth information indicating one of the more than one offset value, the DCI format being for scheduling a Physical Uplink Shared Channel (PUSCH). The method may further include 1410 performing aperiodic CSI reporting on PUSCH in a slot based on the detection of DCI including the third information and the fourth information, the slot being determined based on the fourth information. The first information may be configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell. The second information may be configured for a serving cell.

Fig. 15 is a flowchart illustrating a communication method of a base station apparatus communicating with a User Equipment (UE) on one or more downlink bandwidth parts (DL BWPs) in a serving cell. The method may include 1510 transmitting a Radio Resource Control (RRC) message including first information for configuring a Physical Downlink Control Channel (PDCCH) monitoring periodicity, the first information being used by the UE to monitor the PDCCH. The method may also include 1512 transmitting an RRC message including second information for configuring more than one offset value. The method may also include 1514 transmitting on the PDCCH a Downlink Control Information (DCI) format including third information triggering aperiodic Channel State Information (CSI) reporting and fourth information indicating one of the more than one offset value, the DCI format being used to schedule a Physical Uplink Shared Channel (PUSCH). The method may also include 1516 receiving an aperiodic CSI report on a PUSCH in a slot based on the transmission of the DCI including the third information and the fourth information, the slot being given based on the fourth information. The first information may be configured for each of one or more search spaces configured for each of the one or more DL BWPs in the serving cell. The second information may be configured for a serving cell.

As described above, some methods for DL and/or UL transmissions (e.g., PDSCH transmissions and/or PUSCH transmissions) may be applied (e.g., specified). Here, a combination of one or more of the above some approaches may be applied to DL and/or UL transmissions (e.g., PDSCH transmissions and/or PUSCH transmissions). Combinations of one or more of the above methods may not be excluded from the systems and methods.

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

The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may represent a non-transitory and tangible computer-readable medium and/or processor-readable medium. By way of example, and not limitation, computer-readable media or processor-readable media can comprise 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 desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk andoptical disks, in which disks usually reproduce data magnetically, and optical disks reproduce data optically with lasers.

It should be noted that one or more of the methods described herein may be implemented in hardware and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or using a chipset, Application Specific Integrated Circuit (ASIC), large scale integrated circuit (LSI), or integrated circuit, etc.

Each of the methods disclosed herein includes one or more steps or actions for achieving the method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

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

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

Further, in the case where the program is commercially available, the program stored on the portable recording medium may be distributed, or the program may be transmitted to a server computer connected through a network such as the internet. In this case, a storage device in the server computer is also included. Further, some or all of the gNB160 and UE 102 in accordance with the above-described systems and methods may be implemented as ESIs as typical integrated circuits. Each of the functional blocks of the gNB160 and the UE 102 may be separately built into a chip, and some or all of the functional blocks may be integrated into a chip. Further, the technique of the integrated circuit is not limited to the LSI, and the integrated circuit for the functional block may be implemented with a dedicated circuit or a general-purpose processor. Further, if an integrated circuit technology that replaces LSI appears as the semiconductor technology advances, an integrated circuit to which the technology is applied may also be used.

Further, each of the functional blocks or various features of the base station device and the terminal device used in each of the above-described embodiments may be implemented or executed by a circuit (typically, one integrated circuit or a plurality of integrated circuits). Circuitry designed to perform 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 device, discrete gate or transistor logic, or discrete hardware components, or a combination thereof. A general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general purpose processor or each of the circuits described above may be configured by digital circuitry or may be configured by analog circuitry. Further, when a technology for making an integrated circuit that replaces a current integrated circuit appears due to the advancement of semiconductor technology, an integrated circuit produced by the technology can also be used.