阅读说明：本技术 用户设备、基站和方法 (User equipment, base station and method ) 是由 野上智造 尹占平 生嘉 于 2018-11-13 设计创作，主要内容包括：本发明描述了一种用户设备(UE)。所述UE包括高层处理器,所述高层处理器被配置为获取包括用于指示控制资源集(CORESET)的第一信息的第一无线电资源控制(RRC)配置、获取包括用于指示一个或多个搜索空间集的第二信息的第二RRC配置并获取包括用于指示物理下行链路共享信道(PDSCH)速率匹配资源集的第三信息的第三RRC配置。所述UE还包括被配置为监视PDCCH的物理下行链路控制信道(PDCCH)接收电路。所述UE还包括被配置为在检测到PDCCH时接收PDSCH的PDSCH接收电路。(A User Equipment (UE) is described. The UE includes a higher layer processor configured to obtain a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET), obtain a second RRC configuration including second information indicating one or more search space sets, and obtain a third RRC configuration including third information indicating a Physical Downlink Shared Channel (PDSCH) rate matching resource set. The UE also includes Physical Downlink Control Channel (PDCCH) receiving circuitry configured to monitor the PDCCH. The UE also includes PDSCH receiving circuitry configured to receive PDSCH upon detection of PDCCH.)

1. A User Equipment (UE), comprising:

a higher layer processor configured to obtain a first Radio Resource Control (RRC) configuration comprising first information indicating a control resource set (CORESET), obtain a second RRC configuration comprising second information indicating one or more search space sets, and obtain a third RRC configuration comprising third information indicating a Physical Downlink Shared Channel (PDSCH) rate matching resource set;

physical Downlink Control Channel (PDCCH) receiving circuitry configured to monitor a PDCCH; and

PDSCH receive circuitry configured to receive the PDSCH upon detection of the PDCCH;

wherein

The one or more sets of search spaces are associated with the CORESET,

the third information indicates an identity of the CORESET,

the set of resources is determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the set of one or more search spaces.

2. A base station, comprising:

a higher layer processor configured to transmit a first Radio Resource Control (RRC) configuration comprising first information indicating a control resource set (CORESET), transmit a second RRC configuration comprising second information indicating one or more search space sets, and transmit a third RRC configuration comprising third information indicating a Physical Downlink Shared Channel (PDSCH) rate matching resource set;

physical Downlink Control Channel (PDCCH) transmission circuitry configured to transmit a PDCCH; and

PDSCH transmission circuitry configured to transmit the PDSCH on the PDCCH transmission;

wherein

The one or more sets of search spaces are associated with the CORESET, the third information indicates an identification of the CORESET,

the set of resources is determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the set of one or more search spaces.

3. A method for a User Equipment (UE), the method comprising:

obtaining a first Radio Resource Control (RRC) configuration comprising first information indicating a control resource set (CORESET);

obtaining a second RRC configuration comprising second information indicating one or more search space sets;

obtaining a third RRC configuration comprising third information indicating a set of Physical Downlink Shared Channel (PDSCH) rate-matched resources;

monitoring a Physical Downlink Control Channel (PDCCH); and

receiving the PDSCH when the PDCCH is detected;

wherein

The one or more sets of search spaces are associated with the CORESET, the third information indicates an identification of the CORESET,

the set of resources is determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the set of one or more search spaces.

4. A method for a base station, the method comprising:

transmitting a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET);

transmitting a second RRC configuration including second information indicating one or more search space sets;

transmitting a third RRC configuration including third information indicating a set of Physical Downlink Shared Channel (PDSCH) rate-matched resources;

transmitting a Physical Downlink Control Channel (PDCCH); and

transmitting the PDSCH upon the PDCCH transmission;

wherein

The one or more sets of search spaces are associated with the CORESET, the third information indicates an identification of the CORESET,

the set of resources is determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the set of one or more search spaces.

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 a wireless communication device.

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 gnbs and one or more User Equipments (UEs) in which systems and methods for uplink transmission may be implemented;

FIG. 2 illustrates various components that may be utilized in a UE;

fig. 3 illustrates various components that may be utilized in a gNB;

FIG. 4 is a block diagram illustrating one particular implementation of a UE in which systems and methods for performing uplink transmissions may be implemented;

fig. 5 is a block diagram illustrating one particular implementation of a gNB in which systems and methods for performing uplink transmissions may be implemented;

FIG. 6 is a diagram illustrating one example of a resource;

FIG. 7 shows an example of several parameters;

FIG. 8 shows an example of a subframe structure of the parameters shown in FIG. 7;

FIG. 9 shows an example of a subframe structure of the parameters shown in FIG. 7;

FIG. 10 shows an example of a time slot and a sub-slot;

FIG. 11 shows an example of a scheduling timeline;

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 shows an example of a control resource unit and reference signal structure;

FIG. 15 shows an example of control channel and shared channel multiplexing;

FIG. 16 shows a PDCCH monitoring event for slot-type scheduling;

FIG. 17 shows a PDCCH monitoring event for non-slotted scheduling;

FIG. 18 shows an example of a slot format for a given slot;

FIG. 19 shows an example of a downlink scheduling and hybrid automatic repeat request (HARQ) timeline;

fig. 20 shows an example of an uplink scheduling timeline;

fig. 21 shows an example of a downlink aperiodic channel state information-reference signal (CSI-RS) transmission timeline; and is

Fig. 22 shows an example of an uplink aperiodic Sounding Reference Signal (SRS) transmission timeline;

fig. 23 shows a flow chart of a method for a UE;

fig. 24 shows a flow chart of a method for a gNB;

fig. 25 shows a flow chart of a method for a UE; and is

Fig. 26 shows a flow chart of a method for a base station.

Detailed Description

A User Equipment (UE) is described. The UE includes a higher layer processor configured to obtain a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET), obtain a second RRC configuration including second information indicating one or more search space sets, and obtain a third RRC configuration including third information indicating a Physical Downlink Shared Channel (PDSCH) rate matching resource set. The UE also includes Physical Downlink Control Channel (PDCCH) receiving circuitry configured to monitor the PDCCH. The UE also includes PDSCH receiving circuitry configured to receive PDSCH upon detection of PDCCH. One or more sets of search spaces are associated with CORESET. The third information indicates an identity of CORESET. The resource sets are determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the one or more search space sets.

A base station is described. The base station includes a higher layer processor configured to transmit a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET), transmit a second RRC configuration including second information indicating one or more search space sets, and transmit a third RRC configuration including third information indicating a Physical Downlink Shared Channel (PDSCH) rate matching resource set. The base station also includes Physical Downlink Control Channel (PDCCH) transmission circuitry configured to transmit the PDCCH. The base station also includes PDSCH transmission circuitry configured to transmit PDSCH upon transmission of PDCCH. One or more sets of search spaces are associated with CORESET. The third information indicates an identity of CORESET. The resource sets are determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the one or more search space sets.

A method for a User Equipment (UE) is described. A method for a UE includes obtaining a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET). The method for the UE further includes obtaining a second RRC configuration including second information indicating one or more search space sets. The method for the UE further includes obtaining a third RRC configuration including third information indicating a set of Physical Downlink Shared Channel (PDSCH) rate matching resources. The method for the UE further includes monitoring a Physical Downlink Control Channel (PDCCH) and receiving the PDSCH upon detection of the PDCCH. One or more sets of search spaces are associated with CORESET. The third information indicates an identity of CORESET. The resource sets are determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the one or more search space sets.

A method for a base station is described. A method for a base station includes transmitting a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET). The method for the base station further includes transmitting a second RRC configuration including second information indicating one or more search space sets. The method for the base station further includes obtaining a third RRC configuration including third information indicating a set of Physical Downlink Shared Channel (PDSCH) rate matching resources. The method for the base station further includes transmitting a Physical Downlink Control Channel (PDCCH) and transmitting the PDSCH upon PDCCH transmission. One or more sets of search spaces are associated with CORESET. The third information indicates an identity of CORESET. The resource sets are determined by at least a frequency domain resource allocation of the CORESET, a time domain duration of the CORESET, and a monitoring period and offset of the one or more search space sets.

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 specify specifications for next generation mobile networks, systems, and devices.

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 conjunction with 3GPP L TE, advanced L TE (L TE-a), and other standards including a New Radio (NR), also referred to as 5g (e.g., 3GPP release 8, 9, 10, 11, 12, 13, 14, and/or 15).

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, vehicles, internet of things (IoT) devices, 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 specification, a base station is often referred to as a node B, evolved node B (eNB), home enhanced or evolved node B (HeNB), next generation node B (gNB), or some other similar term, as the scope of the present disclosure should not be limited to 3GPP standards, the terms "base station," node B, "" eNB, "" HeNB, "and" gNB "are used interchangeably herein to represent the more general term" base station.

It should be noted that as used herein, a "cell" may be any communication channel designated by a standardization or regulatory body for international mobile telecommunications Advanced (IMT-Advanced), and all or a subset thereof may be employed by 3GPP as a licensed frequency band (e.g., a frequency band) for communications 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 linking 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.

"configured cells" are those cells that the UE knows and is granted permission by the eNB to transmit or receive information. The "configured cell" may be a serving cell. The UE may receive system information and perform the required measurements on all configured cells. The "configured cell" for a radio connection may include a primary cell and/or none, one or more secondary cells. The "active cells" are those configured cells on which the UE is transmitting and receiving. That is, the active cells are those cells for which the UE monitors its Physical Downlink Control Channel (PDCCH) and, in the case of downlink transmission, decodes its Physical Downlink Shared Channel (PDSCH). "deactivated cells" are those configured cells for which the UE does not monitor the transmission PDCCH. It should be noted that a "cell" may be described in different dimensions. For example, a "cell" may have temporal, spatial (e.g., geographical), and frequency characteristics.

Fifth generation communication systems, known by the 3GPP as NR (new radio technology), envisage the use of time/frequency/space resources to allow services such as eMBB (enhanced mobile broadband) transmission, UR LL C (ultra reliable and low latency communication) transmission and eMTC (large scale machine type communication) transmission, furthermore, in NR, single beam and/or multi-beam operation is considered for downlink and/or uplink transmission.

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 uplink transmissions may be implemented. 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 one or more physical antennas 122 a-n. The gNB160 communicates with the UE102 using one or more physical antennas 180 a-n.

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 produce 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 scheduling modules 126.

The UE scheduling module 126 may perform uplink transmission. The uplink transmission includes a data transmission and/or an uplink reference signal transmission.

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, a PCCH (physical control channel) may be defined. The PCCH is 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). UCI may include a hybrid automatic repeat request (HARQ ACK), Channel State Information (CSI), and/or a Scheduling Request (SR). HARQ-ACK is used to indicate a positive Acknowledgement (ACK) or a Negative Acknowledgement (NACK) of downlink data (i.e., a transport block, a medium access control protocol data unit (MAC PDU), and/or a downlink shared channel (D L-SCH) — CSI is used to indicate a state of a downlink channel.

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 for DCI transmission on the PDCCH — for example, DCI format 1A for scheduling one Physical Shared Channel (PSCH) (e.g., PDSCH, transmission of one downlink transport block) in a cell is defined as a DCI format for the downlink.

Also, for example, DCI Format 0 for scheduling one PSCH (e.g., PUSCH, transmission of one uplink transport block) in a cell is defined as a DCI format for the uplink information associated with the PSCH (PDSCH resources, PUSCH resources) allocation, information associated with the Modulation and Coding Scheme (MCS) for the PSCH, and DCI such as Transmit Power Control (TPC) commands for the PUSCH and/or PUCCH are included in the DCI format, for example, the DCI format may include information associated with a beam index and/or antenna ports.

Further, for example, a PSCH may be defined. For example, in the case where downlink PSCH resources (e.g., PDSCH resources) are scheduled by using a DCI format, the UE102 may receive downlink data on the scheduled downlink PSCH resources. Further, in the case where uplink PSCH resources (e.g., PUSCH resources) are scheduled by using the DCI format, the UE102 transmits uplink data on the scheduled uplink PSCH resources. That is, the downlink PSCH is used to transmit downlink data. And, the uplink PSCH is used to transmit uplink data.

In addition, the downlink PSCH and the uplink PSCH are used to transmit information of a higher layer (e.g., Radio Resource Control (RRC)) layer and/or a MAC layer. For example, the downlink PSCH and the uplink PSCH are used to transmit RRC messages (RRC signals) and/or 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). Further, the RRC message transmitted from the gNB160 may be dedicated to a certain UE102 (referred to as dedicated RRC message). RRC messages and/or MAC CEs are also referred to as higher layer signals.

For example, the U L RS may include a demodulation reference signal, a UE-specific reference signal, a sounding reference signal, and/or a beam-specific reference signal.

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

UE operations module 124 may provide information 148 to one or more receivers 120. For example, the UE operations module 124 may inform the receiver 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 transmission 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 so forth. 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, this information 140 may include instructions for one or more transmitters 158, for example, UE operations module 124 may indicate when one or more transmitters 158 transmit signals to the gNB160, for example, one or more transmitters 158 may transmit during the U L sub-frame.

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. 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 operations module 182 may include one or more of the gNB scheduling modules 194. The gNB scheduling module 194 may perform scheduling of 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 the transmission from the UE 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 the UE 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 the information 101, including 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 transmission data 105 and/or other information included in information 101 may involve error detection and/or correction coding, mapping data to spatial, time, and/or frequency resources for transmission, multiplexing, 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 the modulation type (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

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

It should be noted that a D L subframe may be transmitted from a gNB160 to one or more UEs 102, and a U L subframe may be transmitted from one or more UEs 102 to a gNB160, furthermore, both a gNB160 and one or more UEs 102 may transmit data in standard special subframes.

It should also be noted that one or more of the elements or components thereof included in the gNB160 and UE102 may be implemented in hardware.

Fig. 2 illustrates various components that may be used for a UE 1002. The UE 1002 described in connection with fig. 2 may be implemented in accordance with the UE102 described in connection with fig. 1. The UE 1002 includes a processor 1003 that controls the operation of the UE 1002. 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 UE 1002 may also include a housing that houses one or more transmitters 1058 and one or more receivers 1020 to allow for the transmission and reception of data. One or more transmitters 1058 and one or more receivers 1020 may be combined into one or more transceivers 1018. One or more antennas 1022a-n are attached to the housing and electrically coupled to the transceiver 1018.

The various components of the UE 1002 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. 2 as a bus system 1011. The UE 1002 may also include a Digital Signal Processor (DSP)1013 for processing signals. The UE 1002 may also include a communication interface 1015 to provide user access to the functions of the UE 1002. The UE 1002 shown in fig. 2 is a functional block diagram rather than a listing of specific components.

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

The gNB 1160 may also include a housing that houses one or more transmitters 1117 and one or more receivers 1178 to allow transmission and reception of data. The one or more transmitters 1117 and the one or more receivers 1178 may be combined into one or more transceivers 1176. One or more antennas 1180a-n are attached to the housing and electrically coupled to the transceiver 1176.

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

Fig. 4 is a block diagram illustrating one particular implementation of a UE 1202 in which systems and methods for performing uplink transmissions may be implemented. The UE 1202 includes a transmitting means 1258, a receiving means 1220 and a control means 1224. The transmitting device 1258, the receiving device 1220, and the control device 1224 may be configured to perform one or more of the functions described in conjunction with fig. 1 above. Fig. 2 above shows an example of a specific device structure of fig. 4. 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. 5 is a block diagram illustrating one particular implementation of a gNB 1360 in which systems and methods for performing uplink transmissions may be implemented. The gNB 1360 includes a transmitting device 1317, a receiving device 1378, and a control device 1382. The transmitting means 1317, receiving means 1378 and control means 1382 may be configured to perform one or more of the functions described in connection with fig. 1 above. Fig. 3 above shows one example of a specific device structure of fig. 5. 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. 6 is a diagram illustrating one example of a resource grid. The resource grid shown in fig. 6 may be applicable to both the downlink and uplink, and may be used in some implementations of the systems and methods disclosed herein. More details regarding the resource grid are given in connection with fig. 1.

In fig. 6, one subframe 269 may include one or several slots 283. For a given parameter mu, N^μ _RBFor bandwidth configuration of serving cell, in N^RB _scIs expressed in multiples of (A), wherein N^RB _scIs the size of resource block 289 in the frequency domain, expressed as the number of subcarriers, and N^SF,μ _symbIs the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols 287 in the subframe 269. In other words, for each parameter μ and each of the downlink and uplink, N may be defined^μ _RBN^RB _scSub-carriers and N^SF,μ _symbA resource grid of OFDM symbols. There may be one resource grid per antenna port p, per subcarrier spacing configuration (i.e. parameters) μ and per transmission direction (uplink or downlink). Resource block 289 may include a plurality of Resource Elements (REs) 291.

As shown in table X1, a variety of OFDM parameters (which may also be referred to simply as parameters) are supported. Each parameter may be tied to its own subcarrier spacing Δ f.

TABLE X1

μ	Δf＝2μ·15[kHz]	Cyclic prefix
			0	15	Is normal
1	30	Is normal
			2	60	Normal, extended
3	120	Is normal
			4	240	Is normal
5	480	Is normal

For subcarrier spacing configuration mu, slots are numbered n in increasing order within a subframe^μ _s∈{0,…,N^SF,μ _slot-1} and is numbered n in increasing order within the frame^μ _s，f∈{0,...,N^frame,μ _slot-1}. With N in a time slot^slot,μ _symbA number of consecutive OFDM symbols, where N^slot,μ _SymbDepending on the subcarrier spacing used, as well as the normal cyclic prefix in table X2 and the extended cyclic prefix slot configuration in table X3. The number of continuous OFDM symbols of each sub-frame is N^SF,μ _symb＝N^slot,μ _symbN^{SF ,μ} _slot. Time slot n in a subframe^μ _sIs temporally identical to the OFDM symbol n in the same subframe^μ _sN^slot,μ _symbAre aligned. Not all UEs are capable of simultaneous transmission and reception, which means that not all OFDM symbols in a downlink slot or an uplink slot may be used.

TABLE X2

TABLE X3

For PCell, N^μFor SCell (including licensed assisted Access (L AA) SCell), N^μThe RB is configured by an RRC message dedicated to the UE 102.

For PDSCH mapping, the available RE 291 may satisfy 1 ≧ 1 in the subframe for index 1_data,startAnd/or 1_data,endRE 291 of 1 or more.

An OFDM access scheme with a Cyclic Prefix (CP), which may also be referred to as CP-OFDM, may be employed. In downlink, PDCCH, EPDCCH (enhanced physical downlink control channel), PDSCH, etc. may be transmitted. The radio frame may include a set of subframes 269 (e.g., 10 subframes). The RB is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and one or more OFDM symbols.

Resource blocks are defined as N in the frequency domain^RB _sc12 consecutive subcarriers.

For the subcarrier spacing configuration μ, the carrier resource blocks in the frequency domain are numbered 0 to N^μRB-1. Carrier resource block number n in frequency domain_CRBThe relation with the resource element (k, l) is represented by n_CRB＝floor(k/N^RBsc) where k is defined with respect to the resource grid. The physical resource blocks are defined within a carrier bandwidth part (BWP) and are numbered 0 to N^size _BWP,i-1, where i is the number of carrier bandwidth parts. The relation between physical resource blocks and absolute resource blocks in the carrier bandwidth part i is in n_CRB＝n_PRB+N^start _BWP,i-1 gives, wherein N^start _BWP,iIs the carrier resource block at the beginning of the carrier bandwidth part. The physical resource blocks are defined within a carrier bandwidth part (BWP) and are numbered 0 to N^size _BWP,i-1, where i is the number of carrier bandwidth parts.

The carrier bandwidth part is a contiguous set of physical resource blocks selected from a contiguous subset of carrier resource blocks for a given parameter mu on a given carrier. Number of resource blocks N in carrier BWP^size _BWP,iCan satisfy N^min,μ _RB,x≤N^size _BWP,i≤N^min,μ _RB,x. The UE may be configured to have a maximum of four carrier bandwidth parts in the downlink and only a single downlink carrier bandwidth part is active at a given time. The UE is not expected to receive the PDSCH or PDCCH outside the activated bandwidth part. The UE may be configured to have up to four carrier bandwidth components in the uplink and only a single uplink carrier bandwidth portion is active at a given time. The UE should not transmit PUSCH or PUCCH outside of the active bandwidth part.

An RB may include twelve subcarriers in the frequency domain and one or more 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 formed by the index pair (k, l) in the resource grid^RG) Uniquely identified, where k is 0, …, N^μ _RBN^RB _sc-1 and l^RG＝0,…,N^SF,μ _symb-1 is the index in the frequency domain and the time domain, respectively. Furthermore, REs are uniquely identified by an index pair (k, l) based on some reference point, where l is an index in the time domain. The reference point may be based on a resource grid, i.e., a Component Carrier (CC) basis. Alternatively, the reference point may be based on a certain bandwidth portion in the component carrier. Although subframes in one CC are discussed herein, subframes are defined for each CC, and subframes between CCs are substantially synchronized with each other.

In the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme, also known as discrete Fourier transform spread OFDM (DFT-S-OFDM), may be employed. In the uplink, a PUCCH, a PDSCH, a Physical Random Access Channel (PRACH), and the like may be transmitted.

For each parameter and carrier, N is defined^max,μ _RB,xN^RB _SCSub-carriers and N^SF,μ _symbResource grid of OFDM symbols, where N^max,μ _RB,xGiven by table X4 and X for downlink and uplink being D L or U L, respectively there is one resource grid per antenna port p, per subcarrier spacing configuration μ and per transmission direction (uplink or downlink).

TABLE X4

μ	Nmin,μ RB,DL	Nmax,μ RB,DL	Nmin,μ RB,UL	Nmax,μ RB,UL
					0	20	275	24	275
1	20	275	24	275
					2	20	275	24	275
3	20	275	24	275
					4	20	138	24	138
5	20	69	24	69

The UE102 may be instructed to use only a subset of the resource grid for reception or transmission. The resource block set of a UE is referred to as the carrier bandwidth part and may be configured from 0 to N in the frequency domain^μThe number of RB-1 is received or transmitted. The UE may be configured with one or more carrier bandwidth parts, each of which may have the same or different parameters.

UE102 configured for operation in a bandwidth part (BWP) of a serving cell, up to four bandwidth parts (BWPs) received by UE (D L BWP set) in a set of D L bandwidths indexed by parameters D L-BWP and up to four BWPs transmitted by UE102 (U L3 BWP set) in a set of U L bandwidths indexed by parameters U L1-BWP for the serving cell configured by higher layers for the serving cell, D L BWPs from the configured D L BWP set are linked with U L BWPs from the configured U L BWP set for unpaired spectral calculations, where D L BWP and U L BWP have the same center frequency of BWP L in the respective sets.

In the frequency domain, PRBs are the resource unit sizes of the control channels (which may or may not include DMRS.) A D L shared channel may start at a later OFDM symbol than the symbol carrying the detected D L control channel.

That is, the UE102 may have to monitor a set of PDCCH candidates in one or more control resource sets on one or more active serving cells or bandwidth parts (BWPs) according to the corresponding search spaces, wherein monitoring implies decoding each PDCCH candidate according to a monitored DCI format. Here, the PDCCH candidate may be a candidate to which a PDCCH may be allocated and/or transmitted. The PDCCH candidates are composed of one or more Control Channel Elements (CCEs). The term "monitoring" means that the UE102 attempts to decode each PDCCH in the set of PDCCH candidates according to all DCI formats to be monitored.

The set of PDCCH candidates monitored by the UE102 may also be referred to as a search space. That is, the search space is a set of resources that may be used for PDCCH transmission.

In addition, a Common Search Space (CSS) and a user equipment search space (USS) are set (or defined, configured) in the PDCCH resource region. 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, the CSS consists of CCEs with a predetermined number between the gNB160 and the UE 102. For example, the CSS is composed of CCEs with indices of 0 to 15.

Here, the CSS may be used to transmit DCI to a specific UE 102. That is, the gNB160 may transmit DCI formats intended for multiple UEs 102 and/or DCI formats for a particular UE102 in the CSS. There may be one or more types of CSS. For example, a type 0 PDCCH CSS may be defined for a DCI format scrambled by a system information-radio network temporary identifier (SI-RNTI) on a PCell. A type 1 PDCCH CSS may be defined for DCI formats scrambled by random access- (RA-) RNTI. Additionally and/or alternatively, the type 1 PDCCH CSS may be used for DCI formats scrambled by a temporary cell- (TC-) RNTI or a cell- (C-) RNTI. A type 2 PDCCH CSS may be defined for DCI formats scrambled by paging- (P-) RNTI. A type 3 PDCCH CSS may be defined for DCI formats scrambled by an interval- (INT-) RNTI, where if UE102 is configured by higher layers to decode a DCI format with a CRC scrambled by INT-RNTI, and if UE102 detects a DCI format with a CRC scrambled by INT-RNTI, UE102 may assume that there is no transmission to UE102 in the OFDM symbols and resource blocks indicated by that DCI format. Additionally and/or alternatively, type 3 PDCCH CSS may be used for DCI formats scrambled by other RNTIs (e.g., transmit power control- (TPC-) RNTI, preemption indication- (PI-) RNTI, slot format- (SF-) RNTI, semi-persistent scheduling- (SPS-) RNTI, grant-free- (GF-) RNTI).

The UE may be indicated by a system information block type 0 (SIB0) (also referred to as MIB), a set of control resources for type 0 PDCCH common search space, and a subcarrier spacing and CP length for PDCCH reception. The category 0 PDCCH common search space is defined by CCE aggregation levels and the number of candidates per CCE aggregation level. The UE may assume that DMRS antenna ports associated with PDCCH reception in a PDCCH common search space of type 0 and DMRS antenna ports associated with Physical Broadcast Channel (PBCH) reception are quasi co-located with respect to delay spread, doppler shift, mean delay, and spatial Rx parameters. The PBCH carries a Master Information Block (MIB) containing most of the important system information. PDCCH with a specific DCI format in a type 0 PDCCH common search space schedules reception of PDSCH with SIB1 type (SIB1) or other SI messages. The UE may be indicated by one or more SIB1 control resource sets for the type 1 PDCCH common search space. The subcarrier spacing and CP length for PDCCH reception with a type 1 PDCCH common search space are the same as those for PDCCH reception with a type 0 PDCCH common search space. The UE may assume that DMRS antenna ports associated with PDCCH reception in a type 1 PDCCH common search space and DMRS antenna ports associated with PBCH reception are quasi co-located with respect to delay spread, doppler shift, mean delay, and spatial Rx parameters. The monitoring periodicity of paging events for PDCCH in the type 2 PDCCH common search space may be configured to the UE by higher layer parameters. The UE may configure through higher layer signaling whether to monitor the type 3 PDCCH common search space and/or which one or several serving cells monitor the type 3 PDCCH common search space.

The USS may be used to transmit DCI to a particular UE 102. That is, the USS is defined by resources dedicated to a certain UE 102. That is, the USS may be defined independently for each UE 102. For example, the USS may consist of CCEs having a number determined based on the RNTI assigned by the gNB160, a slot number in a radio frame, an aggregation level, and the like.

Here, the RNTI may include C-RNTI (cell-RNTI), temporary C-RNTI. Further, USS (location of USS) may be configured by the gNB 160. For example, the gNB160 may configure the USS by using RRC messages. That is, the base station may transmit a DCI format intended for a particular UE102 in the USS.

Here, the RNTI allocated to the UE102 may be used for transmission of DCI (transmission of PDCCH). Specifically, CRC (cyclic redundancy check) parity bits (also simply referred to as CRC) generated based on DCI (or DCI format) are attached to DCI, and after the attachment, the CRC parity bits are scrambled by RNTI. The UE102 may attempt to decode DCI attached by CRC parity bits scrambled by the RNTI and detect PDCCH (i.e., DCI format). That is, the UE102 may decode the PDCCH with the CRC scrambled by the RNTI.

One D L control channel element may be mapped on REs defined by a single PRB and a single OFDM symbol, if more than one D L control channel element is used for a single D L control channel transmission, D L control channel element aggregation may be performed.

The number of aggregated D L control channel elements is referred to as the D L control channel element aggregation level D L control channel element aggregation level may be 1 or 2 to an integer power the gNB160 may inform the UE102 which control channel candidates are mapped to each subset of OFDM symbols in a set of control resources.

DCI formats may be classified into at least 4 types, D L regular, U L regular, D L fallback and U L fallback D L regular and U L regular DCI formats may have the same DCI payload size D L fallback and U L fallback DCI formats may have the same DCI payload size table X5, table X6, table X7 and table X8 show examples of D L regular DCI formats, U L regular DCI formats, D L fallback DCI formats and U L fallback DCI formats, respectively.

TABLE X5

TABLE X6

TABLE X7

TABLE X8

Fig. 7 shows an example of several parameters. The parameter #1(μ ═ 0) may be a basic parameter. For example, the RE of the basic parameter is defined to have a subcarrier spacing of 15kHz in the frequency domain and 2048 k in the time domain_κT_SThe length of the + CP (e.g., 512 kts, 160 kts, or 144 kts), where Ts represents a baseband sampling time unit defined as 1/(15000 x 2048) seconds. For the μ parameter, the subcarrier spacing may be equal to 15 x2^μAnd an effective OFDM symbol length NuTs 2048 x2^-μkT 8. This may result in a symbol length of 2048 x2^-μκ Ts + CP Length (e.g., 512 x 2)^-μκTs、160*2^-μKappa Ts or 144 x2^-μκ Ts). Note that k is 64, Ts is 1/(Δ f)_max-N_f)，Δf_max＝480 10³Hz (i.e. Δ f when μ ═ 5), and N_f4096. In other words, the subcarrier spacing of the μ +1 th parameter is twice the subcarrier spacing of the μ th parameter, and the symbol length of the μ +1 th parameter is half the symbol length of the μ th parameter. Fig. 7 shows four parameters, but the system may support an additional number of parameters.

Fig. 8 shows a set of examples of subframe structures for the parameters shown in fig. 7. These examples are based on the slot configuration set to 0. The slot consists of 14 symbols, the slot length of the μ +1 th parameter is half the slot length of the μ parameter, and the number of slots in the final subframe (e.g., 1ms) is doubled. It should be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

Fig. 9 shows another set of examples of subframe structures for the parameters shown in fig. 7. These examples are based on the slot configuration set to 1. The slot consists of 7 symbols, the slot length of the μ +1 th parameter is half the slot length of the μ parameter, and the number of slots in the final subframe (e.g., 1ms) is doubled.

Fig. 10 shows an example of a time slot and a sub-slot. If the sub-slots (i.e., time domain resource allocations in units of an OFDM symbol or a set of several OFDM symbols) are not configured by higher layers, UE102 and gNB160 may use only one slot as a scheduling unit. More specifically, a given transport block may be allocated to a time slot. UE102 and gNB160 may use the sub-slot as well as the slot if the sub-slot is configured by higher layers. A sub-slot may include one or more OFDM symbols. The maximum number of OFDM symbols constituting a sub-slot may be N^SF,μ _symb-1. The sub-slot length may be configured by higher layer signaling. Alternatively, the sub-slot length may be indicated by a physical layer control channel (e.g., by DCI format). A sub-slot may start from any symbol within the slot unless it collides with the control channel. There may be a limit to the micro-slot length based on the limit of the starting position. For example, of length N^{SF ,μ} _symbSub time of-1A slot may start with the second symbol in the slot. The starting position of the sub-slot may be indicated by a physical layer control channel (e.g., by a DCI format). Alternatively, the starting position of the sub-slot may be derived from information of a physical layer control channel (e.g., search space index, blind decoding candidate index, frequency and/or time resource index, PRB index, control channel element aggregation level, antenna port index, etc.) on which data in the sub-slot is scheduled. In the case of configuring a sub-slot, a given transport block may be allocated to a time slot, a sub-slot, an aggregated sub-slot, or an aggregated sub-slot and time slot. The unit may also be a unit for HARQ-ACK bit generation.

Fig. 11 shows an example of a scheduling timeline for a normal D L scheduling timeline, a D L control channel is mapped to the initial part of a slot, a D L control channel schedules a D L1 shared channel in the same slot, HARQ-ACKs for a D L shared channel (i.e. each HARQ-ACK indicating whether a transport block in each D L3 shared channel was successfully detected) are reported via a U L control channel in the following slot.

For the self-contained base D L scheduling timeline, the D L control channel is mapped to the initial portion of the slot, the D L0 control channel schedules the D L1 shared channel in the same slot, the HARQ-ACK for the D L2 shared channel is reported as a U L3 control channel mapped at the end portion of the slot, for the self-contained base U L scheduling timeline, the D L control channel is mapped to the initial portion of the slot, the D L control channel schedules the U L shared channel in the same slot, for these cases, the slot may contain a D L portion and a U L portion, and there may be a guard period between the D L transmission and the U L transmission.

The UE102 may also be able to derive the number of slots for which the SFI indicates their format.

For example, a 3-bit SFI may express a maximum of 8 combinations of "D L", "U L", "unknown", and "reserved", each combination consisting of N^slot,μ _symbBar symbol type composition. More specifically, in view of N^slot,μ _symbOne combination may be "unknown", and "unknown", another combination may be all "D", i.e., "D", "D0", "D1", "D2", "D3", "D4", "D5", "D6", "D7", "D8", "D9", "D0", "D1", another combination may be all "U2", i.e., "U3", "U4", "U5", "U6", "U7", "U8", "U9", "U0", "U1", "U2" U3 "," U4 "," U5 ", another combination may be a" D6 "," U7 "and" reserved "combination, such as" D8 "," D9 "," D "0", "D" and "reserved".

A "D L" symbol may be used for D L reception and CSI/RRM measurements at the UE102 a "U L" symbol may be used for U L transmission at the UE102 a "unknown" resource may also be referred to as a "flexible" resource and may be covered by at least a DCI indication if not covered by DCI and/or SFI indications, then "unknown" may be used to achieve the same values as "reserved" a "reserved" resource may be a "not transmitted" and "not received" resource but cannot be covered by a DCI/SFI indication.

Covering the "unknown" symbol by DCI means that the UE102 may have to assume only D L and U L transmissions (PDSCH transmissions, PUSCH transmissions, aperiodic CSI-RS transmissions, aperiodic CSI-IM resources, aperiodic SRS transmissions) indicated by the DCI indication the covering of the "unknown" symbol by SFI means that the UE102 may have to assume the symbol as "D L", "U L", or "reserved" according to the SFI indication, if the UE102 assumes aperiodic CSI-RS transmissions and/or aperiodic CSI-IM resources, the UE102 may perform CSI and/or RRM measurements based on the aperiodic CSI-RS transmissions and/or aperiodic CSI-IM resources.

If the serving cell is a TDD cell and is a D L-only cell (a serving cell with downlink component carriers but no uplink component carriers), then the UE102 may interpret the "U L" indicated by the SFI as "unknown". alternatively, if the serving cell is a TDD cell and is a D L-only cell, then the UE102 may interpret the "U L" indicated by the SFI as "reserved". if the serving cell is a TDD cell and is a U L-only cell (a serving cell with no downlink component carriers but with uplink component carriers), then the UE102 may interpret the "D L" indicated by the SFI as "unknown". alternatively, if the serving cell is a TDD cell and is a U L-only cell, then the UE102 may interpret the "D L" indicated by the SFI as "reserved".

In this case, there are several options for handling other D L transmissions (e.g., aperiodic CSI-RS transmissions, aperiodic CSI-IM resources) on the one or more "unknown" symbols, the first option is that the UE102 does not assume any other D L transmissions on the one or more "unknown" symbols in addition to the scheduled PDSCH, the second option is that the UE102 assumes other D L transmissions on the "unknown" symbols within the resources allocated for the scheduled PDSCH, the UE102 does not assume any other D L transmissions on the one or more "unknown" symbols in addition to the resources allocated for the scheduled PDSCH, the third option is that the UE102 assumes other D L transmissions on the one or more "unknown" symbols, in other words, the one or more "unknown" symbols are interpreted as D L regardless of the PDSCH resource allocation.

The UE102 may have to monitor PDCCH on certain "unknown" symbols, several options may exist for monitoring PDCCH, if all OFDM symbols allocated for a given control resource set (CORESET) are "D L," the UE102 may assume that all OFDM symbols are valid for monitoring PDCCH associated with the given CORESET.

If some of the allocated OFDM symbols for a given CORESET are "D L" and the remaining OFDM symbols are "U L" or "reserved," or if some of the allocated OFDM symbols for a given CORESET are "unknown" and the remaining OFDM symbols are "U L" or "reserved," the UE102 may assume that only "D L" or "unknown" OFDM symbols are valid for monitoring the PDCCH associated with a given CORESET.

In this case, the UE102 may assume that each PDCCH candidate in the CORESET duration is mapped to all "D L"/"unknown" OFDM symbols, and may allow a single PDCCH candidate to map across "D L" and "unknown" OFDM symbols, alternatively, if some of the OFDM symbols allocated for a given CORESET are "D L" and the remaining OFDM symbols are "unknown," the UE102 may assume that only "D L" OFDM symbols are valid for monitoring PDCCHs associated with the given ESET.

Fig. 12 is a block diagram illustrating one specific implementation of a gNB 1260, the gNB 1260 may include a higher layer processor 1223, a D L transmitter 1225, a U L receiver 1233, and antennas 1231. D L transmitter 1225 may include a PDCCH transmitter 1227 and a PDSCH transmitter 1229. U L receiver 1233 may include a PUCCH receiver 1235 and a PUSCH receiver 1237. the higher layer processor 1223 may manage the behavior of the physical layer (the behavior of the D L transmitter and the U L receiver) and provide higher layer parameters to the physical layer the higher layer processor 1223 may obtain transport blocks from the physical layer the higher layer processor 1223 may send/obtain higher layer messages such as RRC messages and MAC messages to/from the higher layer of the UE 1223 may provide a PDSCH transmitter 1229 transport block and provide PDCCH transmitter 1227 transmission parameters related to the transport block the U L receiver 1233 may receive multiplexed uplink physical channels and uplink physical signals via the receive antennas 1231 and demultiplex them the PUSCH receiver 1237.

Fig. 13 is a block diagram illustrating one specific implementation of a UE 1302, the UE 1302 may include a higher layer processor 1323, a U L transmitter 1351, a D L receiver 1343, and an antenna 1331. the D L transmitter 1351 may include a PUCCH transmitter 1353 and a PUSCH transmitter 1355. the D L 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 D L transmitter and the U L 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 send/obtain 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 provide uci to the PUCCH transmitter 1353, the uci.d L receiver 1343 may receive multiplexed downlink physical channels and downlink physical signals via the receiving antenna 1331 and demultiplex them, the PDCCH receiver 1345 may provide the dci receiver 1343 to the higher layer processor 1327.

For downlink data transmission, the UE102 may attempt blind decoding of one or more PDCCH (also referred to as control channel) candidates. This process is also referred to as monitoring of the PDCCH. The PDCCH may carry a DCI format that schedules the PDSCH (also referred to as a shared channel or a data channel). The gNB160 may transmit the PDCCH and the corresponding PDSCH in a downlink time slot. Upon detecting a PDCCH in a downlink time slot, the UE102 may receive a corresponding PDSCH in the downlink time slot. Otherwise, the UE102 may not perform PDSCH reception in the downlink time slot.

Fig. 14 shows an example of a control resource unit and reference signal structure. In the frequency domain, a set of control resources may be defined as a set of Physical Resource Blocks (PRBs). For example, the control resource set may include PRB # i through PRB # i +3 in the frequency domain. The set of control resources may also be defined in the time domain as a set of OFDM symbols. The control resource set may also be referred to as a duration of the control resource set or simply a control resource set duration. For example, the control resource set may include three OFDM symbols, i.e., OFDM symbol #0 to OFDM symbol #2, in the time domain. UE102 may monitor PDCCH in one or more control resource sets. The set of PRBs may be configured with respect to each set of control resources through dedicated RRC signaling (e.g., via dedicated RRC reconfiguration). The control resource set duration can also be configured with respect to each control resource set through dedicated RRC signaling.

In the control resource element and reference signal structure shown in fig. 14, the control resource element is defined as a set of Resource Elements (REs). Each control resource element includes all REs (i.e., 12 REs) within a single OFDM symbol and within a single PRB (i.e., 12 contiguous subcarriers). REs to which Reference Signals (RSs) are mapped may be counted as those REs, but the REs of the RSs are not available for PDCCH transmission, and the PDCCH is not mapped on the REs of the RSs.

Multiple control resource elements may be used for transmission of a single PDCCH. In other words, one PDCCH may be mapped to REs included in a plurality of control resource elements. Fig. 14 shows an example in which the UE102 performs blind decoding on PDCCH candidates assuming that one PDCCH is carried by a plurality of control resource elements located at the same frequency. However, the RS for PDCCH demodulation may be included in all resource elements to which the PDCCH is mapped. The UE102 may not be allowed to assume that the RS contained in a given resource element is available to demodulate a different resource element. This may increase the diversity gain of PDCCH transmissions because the gNB160 may apply different precoders for different resource elements. Alternatively, the UE102 may be allowed to assume that the RS contained in a given resource element is available to demodulate a different resource element within the same PRB. This may improve channel estimation accuracy, since the gNB160 may apply the same precoder for more RSs within a PRB.

Fig. 15 shows an example of control channel and shared channel multiplexing. The starting and/or ending location of the PDSCH may be indicated via the scheduling PDCCH. More specifically, a DCI format of a scheduled PDSCH may include an information field for indicating a start and/or end position of the scheduled PDSCH.

The UE102 may include a higher layer processor configured to obtain dedicated RRC messages. The dedicated RRC message may include information indicating a configuration of the control resource set. The UE102 may also include PDCCH receiving circuitry configured to monitor PDCCH based on a control resource set configuration. The PDCCH may carry a DCI format that schedules the PDSCH. UE102 may also include PDSCH receiving circuitry configured to receive PDSCH upon detection of a corresponding PDCCH.

The gNB160 may include a higher layer processor configured to send dedicated RRC messages. The dedicated RRC message may include information indicating a configuration of the control resource set. The gNB160 may also include PDCCH transmission circuitry configured to transmit PDCCH based on the control resource set configuration. The PDCCH may carry a DCI format that schedules the PDSCH. The gNB160 may also include PDSCH transmission circuitry configured to transmit PDSCH upon transmission of a corresponding PDCCH.

The UE102 may monitor PDCCH candidates in the control resource set. The PDCCH candidate set may also be referred to as a search space. The set of control resources may be defined by a set of PRBs in the frequency domain and a duration in units of OFDM symbols in the time domain.

For each serving cell, higher layer signaling (such as common RRC messages or UE-specific RRC messages) may configure the UE102 with one or more PRB sets for PDCCH monitoring. Higher layer signaling (such as common RRC messages or UE-specific RRC messages) may also configure the UE102, for each serving cell, with a control resource set duration for PDCCH monitoring.

Each control resource set may include a set of Control Channel Elements (CCEs). Each CCE may map to a set of Resource Element Groups (REGs) including multiple REs. In the control resource set, the group common PDCCH may be transmitted by the gNB 160. The UE102 may monitor the group common PDCCH if the UE102 is configured to monitor the group common PDCCH through higher layer signaling. The group common PDCCH may be a PDCCH with a CRC scrambled by some RNTI, which may be fixed or configured independently of the C-RNTI. Alternatively, the group common PDCCH may be a PDCCH having a DCI format in which an RNTI field value is set to a specific RNTI.

In the control resource set, UE-specific PDCCH may be transmitted by the gNB 160. UE102 may monitor the PDCCH. The UE-specific PDCCH may be a PDCCH having a CRC scrambled by the C-RNTI of the UE 102. Alternatively, the UE-specific PDCCH may be a PDCCH having a DCI format with an RNTI field value set to the C-RNTI of the UE 102. Monitoring of the PDCCH may mean attempting to decode each PDCCH candidate in the set according to the monitored DCI format. UE102 may monitor a common search space within a set of control resources. UE102 may also monitor a UE-specific search space within the set of control resources. UE-specific PDCCHs may be monitored in both the common search space and the UE-specific search space, while group-common PDCCHs may be monitored only in the common search space. The UE-specific PDCCH may schedule the PDSCH. The UE102 may not need to monitor the group common PDCCH in the time slot in which the UE102 will use at least the first OFDM symbol of the time slot for scheduled uplink transmissions.

Upon detecting the UE-specific PDCCH, the UE102 may receive the corresponding PDSCH. The DCI format of the UE-specific PDCCH may include one or more information fields, e.g., a field for indicating resource block allocation of the PDSCH, a field for indicating a starting position of the PDSCH (index of the first OFDM symbol carrying the PDSCH), a field for indicating a modulation order and a transport block size of the PDSCH, and the like. The group-common PDCCH, the UE-specific PDCCH, and the PDSCH may be mapped to different RE sets so that they do not collide with each other.

For each serving cell, the higher layer signaling configures P control resource sets for the UE. For a controlling resource set P, 0 ≦ P < P, the configuration includes: a first symbol index provided by a higher layer parameter CORESET-start-symb; the number of consecutive symbols provided by the high layer parameter, CORESET-time-duration; a set of resource blocks provided by a high level parameter, CORESET-freq-dom; CCE to REG mapping provided by the higher layer parameter CORESET-trans-type (also known as CORESET-CCE-to-REG-mapping); REG bundling size provided by a higher layer parameter, CORESET-REG-bundle-size, in case of interleaving CCE to REG mapping; and antenna port quasi co-location provided by the higher layer parameter CORESET-TCI StateRefld. If the UE is not configured with the higher layer parameter CORESET-TCI StateRefld, the UE may assume that the DMRS antenna port associated with PDCCH reception and the DMRS antenna port associated with PBCH reception in the USS are quasi co-located with respect to delay spread, doppler shift, mean delay, and spatial Rx parameters.

For each serving cell in which the UE is configured to monitor the PDCCH and each DCI format having a CRC scrambled by C-RNTI, SPS-RNTI, and/or license-exempt RNTI, the UE is configured to be associated with a set of control resource sets_pPDCCH of each time slot monitors periodic association; DCI and o with higher layer parameters CORESET-monitor-offset_pPDCCH monitoring offset association of each time slot, wherein 0 ≦ o_p<k_p(ii) a And associating, by a higher layer parameter, a CORESET-monitor-DCI-symbol pattern with a PDCCH monitoring pattern within the slot, the PDCCH monitoring pattern indicating one or more first symbols of a set of control resources within the slot for PDCCH monitoring. If UE102 is configured with the higher layer parameter CORESET-monitor-DCI-symbolPattern, UE102 may assume that non-slotted scheduling is configured in addition to slotted scheduling. If the UE102 is not configured with the higher layer parameter CORESET-monitor-DCI-symbolPattern, the UE102 may assume that non-slotted scheduling is not configured and only slotted scheduling is configured.

Fig. 16 shows a PDCCH monitoring event for slot-type scheduling. A set of search spaces may be identified for a combination of a set of control resources, DCI formats (or DCI format groups consisting of DCI formats having the same DCI payload size). In the example shown in fig. 16, two sets of search spaces, search space set #0 and search space set #1, are shown. Both search space set #0 and search space set #1 are associated with the same CORESET. The configuration of CORESET (such as CORESET-start-symbol, CORESET-time-duration, CORESET-freq-dom, CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-stateRefld) applies to both search space set #0 and search space set # 1. For example, a CORESET-time-duration set to 3 symbols is applied to both sets of search spaces. Search space set #0 may be associated with a particular DCI format (e.g., DCI format 1, fallback DCI format) and search space set #1 may be associated with another particular DCI format (e.g., DCI format 2, regular DCI format). For search space set #0, the high-level parameter, CORESET-monitor-period-DCI, is set to 2 slots, and for search space set #1, the high-level parameter, CORESET-monitor-period-DCI, is set to 1 slot. Thus, DCI format 1 may potentially be transmitted and/or monitored in every 2 slots, while DCI format 2 may potentially be transmitted and/or monitored in every slot.

Fig. 17 shows a PDCCH monitoring event for non-slotted type scheduling. In the example shown in fig. 16, two sets of search spaces, search space set #2 and search space set #3, are shown. Both search space set #2 and search space set #3 are associated with the same CORESET. The CORESET may or may not be the same CORESET as in fig. 16. The high-level parameters CORESET-monitor-period-DCI of search space set #2 and search space set #3 are set to 1 slot.

In addition, a high-layer parameter, CORESET-monitor-DCI-symbolPattern, is separately configured to the search space set #2 and the search space set # 3. The higher layer parameter CORESET-monitor-DCI-symbol pattern may indicate one or more OFDM symbols on which the PDCCH is monitored using a bitmap scheme. More specifically, the high layer parameter CORESET-monitor-DCI-symbolPattern of each search space set may be composed of 14 bits, and the 1 st bit to the 14 th bit correspond to OFDM symbols #0 to #13, respectively. Each bit indicates whether the PDCCH is monitored on the corresponding OFDM symbol (e.g., "0" indicates no PDCCH monitoring and "1" indicates PDCCH monitoring, or vice versa). In this example, the high layer parameter CORESET-monitor-DCI-symbol of search space set #2 indicates OFDM symbol #0 and OFDM symbol #7 for PDCCH monitoring, wherein the high layer parameter CORESET-monitor-DCI-symbol of search space set #3 indicates OFDM symbols #0, #2, #4, #6, #8, #10, #12 for PDCCH monitoring. Note that these PDCCH monitoring are applicable to the slots specified by the CORESET-monitor-period-DCI and CORESET-monitor-offset-DCI.

One control channel element may consist of 6 Resource Element Groups (REGs), where one resource element group is equal to one resource block on one OFDM symbol. And numbering the resource element groups in the control resource set in an ascending order from the first OFDM symbol in the control resource set and the resource block with the smallest number as 0 in a time-first mode. The UE may be configured with multiple sets of control resources. Each control resource set may be associated with only one CCE to REG mapping. The CCE to REG mapping of the control resource set may be interleaved or non-interleaved, configured by a higher layer parameter, CORESET-CCE-REG-mapping-type. The REG bundling size is configured by a higher layer parameter CORESET-REG-bundle-size. For non-interleaved CCE to REG mapping, the REG bundling size is 6. For interleaved CCE to REG mapping, when the core time-duration is set to 1, the REG bundling size is 2 or 6 for core set, and when core time-duration N^CORESET _symbSet to be greater than 1, the REG bundling size is N for CORESET^CORESET _symbOr 6. The UE may assume: if the high-layer parameter CORESET-precoder-granularity is equal to CORESET-REG-bundle-size, then the same precoding is used in the REG bundling in the frequency domain; and if the higher layer parameter CORESET-precoding-granularity is equal to the number of consecutive RBs in the frequency domain in CORESET, using the same precoding in the frequency domain in all REGs within consecutive RBs in CORESET.

For one or more search space sets configured with the higher layer parameter, CORESET-monitor-DCI-symbol pattern (e.g., symbol-wise bitmap), certain configurations of each CORESET may not be applicable. For example, even if the CORESET-time-duration is set to be greater than 1 OFDM symbol, UE102 may assume that each PDCCH monitoring event spans across one or more search space sets for which CORESET-monitor-DCI-symbol pattern is configured1 OFDM symbol. A CORESET-time-duration set to greater than 1 OFDM symbol may only be applicable to one or more search space sets for all unconfigured CORESET-monitor-DCI-symbol patterns. In this case, for interleaving CCE to REG mapping, the REG bundling size may depend on the core set-time-duration. Alternatively, for interleaving CCE to REG mapping, assume N^CORESET _symbThe REG bundling size may be determined as 1.

Alternatively, the CORESET duration is always configured independently, and if the CORESET duration is greater than 1 OFDM symbol, a PDCCH monitoring event configured using a symbol-wise bitmap may mean the start of the monitoring event. For example, setting the core-time-duration to 2 OFDM symbols and the third bit of the core-monitor-DCI-symbol to "1", the UE102 may have to monitor the PDCCH candidates mapped on the third and fourth OFDM symbols. In other words, each bit of the CORESET-monitor-DCI-symbol pattern set to "1" may indicate a starting symbol of one or more consecutive OFDM symbols on which one or more PDCCH candidates are mapped.

With this alternative, if the CORESET duration is greater than 1 OFDM symbol and at least if either of two adjacent bits of the CORESET-monitor-DCI-symbol pattern is set to "1", PDCCH monitoring events beginning with the OFDM symbol indicated by these two bits partially overlap. The overlap can be handled in a number of ways. The first approach is that the UE102 is not expected to be configured with a CORESET-monitor-DCI-symbolPattern that would result in overlap between adjacent PDCCH monitoring events of the same search space set. The second approach is to allow PDCCH monitoring events to overlap and the UE102 does not need to monitor PDCCH candidates that are fully/partially mapped to REs or REGs that have been used by another detected PDCCH of another PDCCH monitoring event of the CORESET. A third approach is to allow PDCCH monitoring events to overlap and the UE102 does not need to monitor PDCCH candidates if the higher layer parameter, CORESET-decoder-granularity, is equal to the number of consecutive RBs in the frequency domain within the CORESET and if another PDCCH is detected in another PDCCH monitoring event of the CORESET (i.e. an overlapping PDCCH monitoring event). Additionally and/or alternatively, if the higher layer parameter, CORESET-decoder-granularity, is equal to the number of consecutive RBs in the frequency domain within the CORESET, and if a PDCCH is detected in a PDCCH monitoring event in the CORESET, the UE102 may assume that a DMRS related to the detected PDCCH is present in all REGs in the set of consecutive RBs of the CORESET to which the detected PDCCH is mapped, and the UE102 may not desire to monitor one or more PDCCHs in another PDCCH monitoring event that overlaps with the DMRS.

Each control resource set includes a set of numbers from 0 to N_CCE,p,kpCCE of-1, where N_CCE,p,kpIs in the monitoring period k_pThe number of CCEs in a control resource set p. the PDCCH candidate set monitored by the UE is defined according to a PDCCH UE-specific search space, PDCCH UE-specific search space S of CCE aggregation level L^(L) _kpIs defined by a set of PDCCH candidates for CCE aggregation level L L may be one of 1, 2, 4 and 8.

For each serving cell, the UE102 may have to set the Slot configuration per Slot equal in number of slots to the Slot configuration per Slot over the number of slots (as indicated by the higher layer parameter Slot-assignment sib1, which may be a UE-common parameter (i.e., a cell-specific parameter)). If the UE is additionally provided with a UE-specific higher layer parameter Slot-assignment for the Slot format of each Slot over the number of slots, the parameter Slot-assignment covers only the flexible symbols (also referred to as unknown symbols) per Slot over the number of slots provided by the Slot-assignment sib 1.

For each serving cell, the UE102 may follow the following assumptions for a set of symbols of the Slot indicated as flexible (also referred to as unknown) by the higher layer parameter Slot-assignment sib1 and the higher layer parameter Slot-assignment, if provided. The UE102 may have to receive the PDCCH, PDSCH or CSI-RS in the set of symbols of the slot if the UE102 receives a corresponding indication of a DCI format with a CRC scrambled by the C-RNTI or a configuration of a higher layer. The UE102 may have to transmit the PUSCH, PUCCH, PRACH, or SRS into the set of symbols of the slot if the UE receives a corresponding indication of a DCI format with a CRC scrambled by the C-RNTI or a configuration of higher layers. If the UE does not detect a DCI format with CRC scrambled by the C-RNTI that instructs the UE102 to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot, a UE102 configured for receiving PDCCH or triggering type 0 CSI-RS (i.e., higher layer configured CSI-RS, also referred to as semi-statically configured periodic CSI-RS) may have to receive PDCCH or trigger type 0 CSI-RS in the set of symbols of the slot; otherwise, the UE102 may not receive the PDCCH or trigger a class 0 CSI-RS in the set of symbols of the slot and may have to transmit the PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot. If the UE does not detect a DCI format with a CRC scrambled by a C-RNTI that instructs the UE to transmit PDSCH or CSI-RS in the set of symbols of the slot, then a UE102 configured for transmitting a triggered class 0 SRS (i.e., a higher layer configured SRS, also referred to as a semi-statically configured periodic SRS) or a PUCCH configured by a higher layer in the set of symbols of the slot may have to transmit the triggered class 0 SRS or the PUCCH configured by the higher layer in the set of symbols of the slot; otherwise, the UE may not transmit the trigger class 0 SRS or PUCCH in the set of symbols of the slot.

For a set of symbols of the Slot indicated as uplink by the higher layer parameter Slot-assignment sib1 or the higher layer parameter Slot-assignment, if provided, the UE102 may not expect to be indicated by a DCI format with a CRC scrambled by a C-RNTI or be configured by the higher layer to receive a PDCCH, PDSCH or CSI-RS in the set of symbols of the Slot. For a set of symbols of a Slot indicated as downlink by a higher layer parameter Slot-assignment sib1 or a higher layer parameter Slot-assignment, if provided, the UE102 may not expect a DCI format indication with a CRC scrambled by a C-RNTI or be configured by the higher layer to transmit a PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the Slot.

If the UE102 is configured by higher layers with the parameter SFI-applicable-cells (i.e., if the UE102 is configured with monitoring for DCI format STI, or if the UE102 is configured with any parameters related to monitoring for DCI format STI), the UE102 may follow the above procedure to determine the slot format for each slot. If the UE102 is configured by higher layers with the parameter SFI-applicable-cells, and for a serving cell for which the UE102 is not configured with the parameter SFI-applicable-cells, the UE102 may follow the above procedure to determine the slot format for each slot. If the UE102 is configured to monitor a DCI format with a CRC scrambled by an SFI-RNTI for the serving cell, and if the UE102 does not detect a DCI format with a CRC scrambled by an SFI-RNTI that may indicate a slot format for a given slot, the UE102 may also follow the above procedure to determine the slot format for that slot. Alternatively, if the UE102 is configured to monitor the DCI format with the CRC scrambled by the SFI-RNTI for the serving cell, and if the UE102 does not detect a DCI format with the CRC scrambled by the SFI-RNTI that may indicate the slot format of a given slot, the UE102 may also follow the above process to determine the slot format of the slot (except PDCCH reception, triggered type 0 CSI-RS reception, SPS PDSCH reception, triggered type 0 SRS transmission, PUCCH transmission, SPS/unlicensed PUSCH transmission, or any combination thereof).

If the UE102 is configured by the higher layer with the parameter SFI-applicable-cells, the UE102 is configured with a SFI-RNTI provided by the higher layer parameter SFI-RNTI and a set of serving cells provided by the higher layer parameter SFI-monitoring-cells for monitoring the PDCCH for delivery of a DCI format with a CRC scrambled by the SFI-RNTI (e.g., a specific DCI format for SFI, also referred to as DCI format STI). In each serving cell of the set of serving cells, the UE configured parameters include: a set of control resources configured by a high-layer parameter SFI-to-CORESET-map for monitoring PDCCH delivery DCI format SFI; the payload size of the DCI format SFI configured by a high-level parameter SFI-DCI-payload-length; a group of cells which can apply DCI format SFI and are configured by high-level parameters SFI-applicable-cells; a location of a field in a DCI format SFI for each cell from the set of cells configured by a high-layer parameter SFI-cell-to-SFI for the corresponding cell; the number of PDCCH candidates for each CCE aggregation level of the DCI form SFI configured by a high-layer parameter SFI-Num-PDCCH-cand; monitoring periodicity for PDCCH with DCI format SFI configured by higher layer parameter SFI-monitoring-periodicity.

If the UE102 is in the time slot mT_SFIDetection of DCI format with CRC scrambled by SFI-RNTI, time slot { mT_SFI,mT_SFI+1,…(m+1)T_SFI-1} time slot configuration by having scrambling by SFI-RNTIThe slot configuration of DCI format indication of CRC is given, where T_SFIIs the value of the parameter SFI-monitoring-periodicity for DCI formats with CRC scrambled by SFI-RNTI configured by higher layers to the UE 102.

For each serving cell for which the UE102 is configured by higher layers with the parameter SFI-applicable-cells, the UE102 may assume some or all of the following (1) to (4).

(1) For a set of symbols of a slot, the UE102 may not desire to detect a DCI format with a CRC scrambled by an SFI-RNTI indicating the set of symbols of the slot as uplink and a DCI format with a CRC scrambled by a C-RNTI indicating that the UE102 receives a DCI format for a PDSCH or CSI-RS in the set of symbols of the slot.

(2) For a set of symbols of a slot, it is not desirable for the UE102 to detect a DCI format with a CRC scrambled by an SFI-RNTI that indicates the set of symbols of the slot as a DCI format for the downlink, and to detect a DCI format with a CRC scrambled by a C-RNTI that indicates the UE102 to transmit a PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot.

(3) For a set of symbols of a Slot indicated as downlink/uplink by a higher layer parameter Slot-assignment sib1 or a higher layer parameter Slot-assignment, if provided, the UE102 may not expect to detect a DCI format with a CRC scrambled by an SFI-RNTI indicating the set of symbols of the Slot as uplink/downlink, or flexible, respectively.

(4) For a set of symbols of a Slot indicated as flexible by the higher layer parameter Slot-assignment sib1 or the higher layer parameter Slot-assignment, if provided, the UE102 may follow all or part of the following procedure: if the UE102 detects a DCI format with a CRC scrambled by an SFI-RNTI and the DCI format indicates the set of symbols of the slot as flexible and the UE102 detects a DCI format with a CRC scrambled by a C-RNTI and the DCI format indicates the UE receives a PDSCH or CSI-RS in the set of symbols of the slot, the UE102 may follow the indication of the DCI format with the CRC scrambled by the C-RNTI; if the UE102 detects a DCI format with a CRC scrambled by an SFI-RNTI and the DCI format indicates the set of symbols of the slot as flexible and the UE102 detects a DCI format with a CRC scrambled by a C-RNTI and the DCI format indicates the UE102 transmits a PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot, the UE102 may follow the indication of the DCI format with the CRC scrambled by the C-RNTI; if UE102 detects a DCI format with a CRC scrambled by an SFI-RNTI and the DCI format indicates the set of symbols of the Slot as flexible, and the set of symbols of the Slot is also indicated as flexible by the higher layer parameter Slot-assignment sib1 or the higher layer parameter Slot-assignment (if provided), UE102 may treat the set of symbols as reserved; if the UE102 is configured by the higher layer to receive the PDCCH or trigger a type 0 CSI-RS or SPS PDSCH in the set of symbols of the slot, the UE102 may have to receive the PDCCH or trigger a type 0 CSI-RS or SPS PDSCH in the set of symbols of the slot only when the UE detects a DCI format with a CRC scrambled by the SFI-RNTI, the DCI format indicating that the set of symbols of the slot are downlink; if the UE102 is configured by the higher layer to transmit the trigger class 0 SRS or PUCCH or SPS/grant-free PUSCH in the set of symbols of the slot, the UE102 may have to transmit the trigger class 0 SRS or PUCCH or SPS/unlicensed PUSCH in the set of symbols of the slot only when the UE102 detects a DCI format with a CRC scrambled by the SFI-RNTI, which indicates that the set of symbols of the slot is downlink.

Slot format #0 may specify that all symbols in a Slot are D L symbols Slot format #1 to Slot format #13 may specify that a Slot is filled up to 13D L symbols from the earliest symbol, then one or more flexible symbols, then one or more U L symbols Slot format #15 to Slot format #104 may specify that a Slot is filled up to 12D L symbols from the earliest symbol, then one or more U L symbols, Slot format #107 may specify that all symbols in a Slot are D L symbols UE-specific Slot-assignment may be able to be set with any of these indices, alternatively one or more common segment index fields with a segment index indicated by the i-segment index may be set by a segment index (e.g. a segment index) in a Slot format # 64.

The timing between a D L allocation and a corresponding D L data transmission may be indicated by a field in the DCI from a set of values, the timing between a U L allocation and a corresponding U L data transmission may be indicated by a field in the DCI from a set of values, and the timing between a D L data reception and a corresponding acknowledgement may be indicated by a field in the DCI from a set of values.

Fig. 19 shows an example of a downlink scheduling and HARQ timeline. The PDCCH transmitted by the gNB160 in slot n may carry a DCI format for scheduling PDSCH, which includes at least two fields, a first field may indicate k₁The second field may indicate k₂。

A UE102 detecting PDCCH in slot n may be in slot n + k₁Receives the scheduled PDSCH and then transmits it in time slot n + k₁+k₂UE102 may report HARQ-ACKs corresponding to the PDSCH. Alternatively, the second field may indicate m, and the UE102 may report HARQ-ACK in slot n + m. In other words, upon detection of time slot i-k₁UE102 may receive PDSCH in time slot i, and UE102 may transmit HARQ ACK in time slot j for time slot j-k₂Is transmitted. Alternatively, the UE102 may transmit HARQ-ACKs in time slot j for PDSCH transmissions scheduled by the corresponding PDCCH in time slot j-m.

Fig. 20 shows an example of an uplink scheduling timeline. The PDCCH transmitted by the gNB160 in slot n may carry a DCI format for scheduling PUSCH including at least one indicatable k₃A field of (1). Detecting U of PDCCH in slot nE102 may be in time slot n + k₃And transmitting the scheduled PUSCH. In other words, in time slots i-k₃Upon detecting the corresponding PDCCH, the UE102 may transmit PUSCH in slot i,

fig. 21 shows an example of a downlink aperiodic CSI-RS transmission timeline. The PDCCH transmitted by the gNB160 in slot n may carry a DCI format indicating the presence of an aperiodic CSI-RS, including at least one indicatable k₄A field of (1). A UE102 detecting PDCCH in slot n may assume slot n + k₄There is an aperiodic CSI-RS for CSI measurements and/or Radio Resource Management (RRM) measurements.

Fig. 22 shows an example of an uplink aperiodic SRS transmission timeline. The PDCCH transmitted by the gNB160 in slot n may carry a DCI format scheduling aperiodic SRS, including at least an indicatable k₅A field of (1). A UE102 detecting PDCCH in time slot n may be in time slot n + k₅To transmit the scheduled aperiodic SRS. In other words, in time slots i-k₅Upon detecting the corresponding PDCCH, the UE102 may transmit an aperiodic SRS in slot i,

the presence/disabling of each of the above fields may be configured by higher layer signaling. The configuration of presence/disable may be common in those fields. Alternatively, presence/disable may be configured separately. A default value (e.g., a predefined fixed value or a value included in the system information) may alternatively be used if at least one of the fields is not present or disabled. E.g. k₁May be 0, and k₂Or k₃May be 4.

If the field is present, the UE102 may be configured through higher layer signaling to have a plurality of values (e.g., a first value through a fourth value). Each of the possible values of this field (e.g., a 2-bit field) may correspond to a different one of the configured values. The UE102 may use a value as the value of k, which corresponds to a set of field values in an associated field in the detected PDCCH.

The UE102 may be configured to have a plurality of values (e.g., a first value through a third value) through higher layer signaling. At least one possible value of this field (e.g., a 2-bit field) may correspond to a predefined fixed value. Each of the remaining values (e.g., 2-bit fields) of the possible values for this field may correspond to a different one of the configured values.

The UE102 may use a value as the value of k, which corresponds to a set of field values in an associated field in the detected PDCCH. In this case, in the event that the presence of this field is not configurable, the gNB160 may use a predefined fixed value such that the gNB160 and the UE102 share the same value of k even during RRC (re) configuration of values for those higher layer configurations. The predefined fixed value may depend on the timing offset type. E.g. k₁May be 0, and k₂Or k₃May be 4. Alternatively, a value indicated by system information may be used instead of a predefined fixed value.

PDSCH and/or PUSCH RE mapping may be affected by higher layer signaling and/or layer 1 signaling, such as PDCCH with DCI formats 1 and 2. For PDSCH, the modulated complex-valued symbols may be mapped into REs that satisfy all of the following conditions: in resource blocks allocated for transmission; considering to be available for PDSCH according to rate matching resource set configuration and/or indication; unused for CSI-RS; unused for phase tracking RS (PT-RS); not reserved for SS/PBCH; not considered "reserved".

In order to decode the PDSCH based on the detected PDCCH, the UE may be configured with any higher layer parameters, rate-match-PDSCH-resource-RBs consisting of one or more pairs of reserved RBs (higher layer parameter rate-match-PDSCH-resource-RBs, also referred to as bitmap-1) and reserved symbols (higher layer parameter rate-match-PDSCH-resource-symbols, also referred to as bitmap-2) applicable to reserved RBs, rate-match-resource-v-shift consisting of one or more of L TE-CRS-vshifts, rate-match-resource-v-shift consisting of 1, 2, or 4 ports of L TE-CRS antenna ports, core-match-core-antenna-port consisting of one or more ESET-IDs configured to UE102 for monitoring, UE102 may determine that the UE matches the rate around the decoding rate set of one or multiple ESET-PDSCH-resource-RE mapping RE, if UE102 and PDSCH-SR 102 match the UE-decode rate, there may be an indication that there is no overlap of the UE-decode rate-resource-set.

More specifically, at the RB symbol level, the UE102 may be an RRC configured with one or more pairs (e.g., up to 16 pairs) of bitmap-1 and bitmap-2, each pair determining a set of time-frequency resources, i.e., kronecker (transpose-l), bitmap-2.

bitmap-1 has at least RB granularity (at most 275 bits, one bit for each RB). bitmap-2 has 14 symbols (one bit per symbol) for the time that bitmap-1 applies (e.g., always 14 bits for 1 slot). Further, on the RB symbol level, the UE102 can be an RRC configured with one bitmap-3 for each pair of bitmap-1 and bitmap-2 for one or more rate-matched resource sets. Each bit in bitmap-3 corresponds to a cell of equal duration to bitmap-2 and indicates whether the pair is present in that cell. bitmap-3 may consist of {1, 5, 10, 20, or 40 units }, but has a duration of at most 20ms or 40 ms. If bitmap-3 is configured, the UE102 rate matches the union of the set of resources, each represented by a set of bitmap-1, bitmap-2, and bitmap-3.

The layer 1 signaling may indicate a PDSCH rate matched resource set. The DCI format scheduled PDSCH may include an information field (if configured) indicating PDSCH rate matching resources joined to the configured set of resources. There are a number of options. The first option is that bit 1 opens or closes a single resource set. In this option, the information field carries N bits, and each bit corresponds to a different resource set (i.e., a different combination of bitmap-1 and bitmap-2). The second option is that bit 1 opens or closes all resource sets. In this option, the information field carries 1 bit. A third option is that N bits open or close a subset of the resource set. In this option, the information field carries N bits, and each bit corresponds to a different subset of the resource set (i.e., a different subset of all combinations of bitmap-1 and bitmap-2). For example, using this option, 2 represented by the information field^NEach item of the itemsSpecifying the on/off status of all configured resource sets. The presence of this bit field of the DCI format is configured by higher layer signaling. Herein, "on" may indicate that a resource set is not available for PDSCH transmission, and the PDSCH is rate matched around the resource set. Meanwhile, "off" may indicate that a resource set is available for PDSCH transmission and that the PDSCH is not rate matched around, but is mapped on, the resource set. Or vice versa.

To decode PUSCH from detected PDCCH, the UE may be configured with any higher layer parameters: and the rate-match-PUSCH-resource-set consists of one or more pairs of reserved RBs (high-layer parameter rate-match-PUSCH-resource-RBs) and reserved symbols (high-layer parameter rate-match-PUSCH-resource-symbols) applicable to the reserved RBs. Alternatively, the rate-match-PUSCH-resource-set may consist of reserved symbols (higher layer parameter rate-match-PUSCH-resource-symbols), but may not include RB configuration. Still alternatively, rate-match-PUSCH-resource-set may not be allowed to be configured. In this case, the resource set for rate matching can only be configured for PDSCH, not PUSCH. In other words, the frequency domain granularity of the resource set is always equal to the maximum number of RBs of CC or BWP.

The presence of bit fields for indicating DCI formats for one or more resource sets for rate matching may be configured for PDSCH and PUSCH, respectively. Alternatively, a single configuration of the presence of the bit field may be applicable to both DCI format scheduled PDSCH and DCI format scheduled PUSCH. Still alternatively, the presence of a bit field and/or the number of bits of a bit field may be determined by how many resource sets are tied to an entry for layer 1 signaling. The one or more fallback DCI formats may not include the information field regardless of whether the configuration of the information field exists. The configuration of the presence of this information field may be applicable to one or more conventional (i.e., non-fallback) DCI formats. One or more DCI formats in the CSS may not include the information field, regardless of whether the configuration of the information field exists. The configuration of the presence of this information field may be applicable to one or more DCI formats in the USS. When decoding PDSCH scheduled by a fallback DCI format or PDCCH in CSS (e.g., type 0 CSS), there are multiple options for PDSCH rate matching. The first option is that PDSCH may be rate matched around resources of core set configured by PBCH only, but may not be rate matched around the set of resources specifically configured by UE for PDSCH rate matching. The second option is that the PDSCH may not be rate matched around any CORESET related resources. A third option is whether PDSCH is rate matched around PBCH configured CORESET resources is configured by PBCH.

If configured, the information field for indicating PDSCH rate-matching resources in a DCI format scheduling a PDSCH may indicate one or more resource sets that the UE102 assumes are not available for PDSCH transmission. Each entry of the information field for indicating PDSCH rate-matching resources in the DCI format for scheduling PDSCH may indicate a subset of all resource sets specified by the rate-match-PDSCH-resource-set or CORESET configuration, but the subset may not allow any resource set specified by the rate-match-PUSCH-resource-set to be included. If configured, the information field for indicating PUSCH rate-matched resources in the DCI format for scheduling PUSCH may indicate one or more resource sets that the UE102 assumes are not available for PUSCH transmission. Each entry of the information field for indicating PUSCH rate-matched resources in the DCI format for scheduling PUSCH may indicate a subset of all resource sets specified by rate-match-PUSCH-resource-set, but the subset may not allow the inclusion of any resource set specified by rate-match-PDSCH-resource-set or core set configuration.

If the UE-specific parameter, rate-match-core, includes the core set-ID for the given core set, (or, if the UE-specific parameter, rate-match-core, includes the core set-ID for the given core set and layer 1 signaling (if configured) turns on the core set), the UE102 may perform PDSCH rate matching around resources indicated by the time-frequency resource configuration of the core set (e.g., core set-start-symbol, core set-time-duration, core set-frequency-dom). This principle may be applicable regardless of whether the UE102 is configured to monitor layer 1 signaling for indicating PDSCH rate matching resources. Alternatively, if the UE-specific parameter, rate-match-core, includes the core-ID of a given core, and if the bit field indicating PDSCH rate matching resources is not present in the DCI format monitored by the UE102, the UE102 may perform PDSCH rate matching around the resources indicated by the time-frequency resource configuration of the core. If the UE-specific parameter, rate-match-core, includes the core set-ID of a given core set, and if the UE is configured to monitor the PDCCH using a DCI format (where there is a bit field to indicate PDSCH rate matching resources), the UE102 may perform PDSCH rate matching around resources indicated by the core set's time-frequency resource configuration only if the bit field indicates that the core set is an unavailable resource for the PDSCH. Otherwise, UE102 may not perform PDSCH rate matching around resources indicated by the time-frequency resource configuration of CORESET, but may consider these resources available for PDSCH transmissions.

If the rate-match-core includes the core set-ID for a given core set, (or if the UE-specific parameters rate-match-core include the core set-ID for the given core set, and layer 1 signaling (if configured) turns on the core set), then the time-frequency resources specified by all of the search space set configurations in the core set configuration (e.g., core-monitor-period-DCI, core-monitor-offset-DCI) and the time-frequency resource configuration of the core set (e.g., core-start-symbol, core-time-duration, core-frequency-dom) may be used to determine the resources that are not used for PDSCH transmission. More specifically, the resources identified by the time-frequency resource configuration of CORESET are not used for PDSCH transmission only in the slots identified by the slot configuration of any search space set in the CORESET configuration (e.g., CORESET-monitor-period-DCI, CORESET-monitor-offset-DCI). Resources identified by the time-frequency resource configuration of CORESET, in slots not identified by the slot configuration of any search space set in the CORESET configuration, for PDSCH transmission.

Alternatively, regardless of one or more of the core set configurations (e.g., core-monitor-period-DCI, core-monitor-offset-DCI), if the rate-match-core includes the core-ID of a given core set, (or if the UE-specific parameters rate-match-core include the core-ID of a given core set, and layer 1 signaling (if configured) turns on the core set), the time-frequency resource configuration of the core set (e.g., core-start-symbol, core-time-duration, core-freq-dom) may be used to determine that there are no resources in each slot for PDSCH transmission.

If the PDCCH monitoring event is configured by using the CORESET-monitor-DCI-symbolPattern, and if the CORESET is configured to serve as the PDSCH rate matching resource set, the PDSCH rate matching resource set consists of all OFDM symbols indicated by the CORESET-monitor-DCI-symbolPattern. More specifically, if the rate-match-core includes the core set-ID of a given core set, and if the core set-monitor-DCI-symbol pattern is configured for at least one search space in the core set, the time-frequency resources specified by the configuration of all search space sets in the core set configuration (e.g., core set-monitor-DCI-symbolPattern) and the core set configuration (e.g., core set-start-symbol, core set-time-rate, core set-frequency-dom) may be used to determine that there are no resources for PDSCH transmission. Only among the symbols identified by the CORESET-monitor-DCTsymbolPattern of any search space set in the CORESET configuration, the resources identified by the time-frequency resource configuration of CORESET are not used for PDSCH transmission. In symbols not identified by the CORESET-monitor-DCTsymbolPattern of any set of search spaces in the CORESET configuration, the resources identified by the time-frequency resource configuration of CORESET are used for PDSCH transmission.

Alternatively, regardless of the core set-monitor-DCI-symbol pattern of one or more search space sets in the core set configuration, if the rate-match-core set includes the core set-ID of a given core set, (or if the UE-specific parameters rate-match-core include the core set-ID of a given core set, and layer 1 signaling (if configured) turns on the core set), the time-frequency resource configuration of the core set (e.g., core-start-symbol, core-time-duration, core-freq-dom) may be used to determine that there are no resources in each symbol for PDSCH transmission.

As another example, the CORESET configuration may also include per search space set information indicating whether the configuration associated with the search space set (e.g., CORESET-monitor-period-DCI, CORESET-monitor-offset-DCI, CORESET-monitor-DCTsymbolPattern) is used to determine that there are no resources for PDSCH transmission. In this case, each resource indicated by CORESET-monitor-period-DCI, CORESET-monitor-offset-DCI, CORESET-monitor-DCI-symbolPattern will be considered separately for PDSCH rate matching.

The present invention describes a UE 102. UE102 may include a higher layer processor configured to obtain a dedicated Radio Resource Control (RRC) configuration including information indicating one or more resource sets for Physical Downlink Shared Channel (PDSCH) rate matching. The UE102 may also include Physical Downlink Control Channel (PDCCH) receiving circuitry configured to monitor a first PDCCH and a second PDCCH. The first PDCCH is a PDCCH having a regular Downlink Control Information (DCI) format. The second PDCCH is a PDCCH having a fallback DCI format. The UE102 may also include PDSCH receiving circuitry configured to receive PDSCH upon detection of the first PDCCH or the second PDCCH. The PDSCH is rate matched around one or more resource sets if scheduled by the first PDCCH. The PDSCH is not rate matched around one or more resource sets if scheduled by the second PDCCH.

The present disclosure describes a gNB 160. The gNB160 may include a higher layer processor configured to transmit a dedicated Radio Resource Control (RRC) configuration including information indicating one or more resource sets for Physical Downlink Shared Channel (PDSCH) rate matching. The gNB160 may also include Physical Downlink Control Channel (PDCCH) transmission circuitry configured to transmit a first PDCCH and a second PDCCH. The first PDCCH is a PDCCH having a regular Downlink Control Information (DCI) format. The second PDCCH is a PDCCH having a fallback DCI format. The gNB160 may also include PDSCH transmission circuitry configured to transmit PDSCH on the first PDCCH or the second PDCCH transmission. The PDSCH is rate matched around one or more resource sets if scheduled by the first PDCCH. The PDSCH is not rate matched around one or more resource sets if scheduled by the second PDCCH.

Fig. 23 shows a flow chart of a method for a UE. A method for a UE102 is described. The method may include obtaining 2310 a dedicated Radio Resource Control (RRC) configuration including information indicating one or more resource sets for Physical Downlink Shared Channel (PDSCH) rate matching. The method may also include monitoring 2311 the first PDCCH. The method may also include monitoring 2312 the second PDCCH. The first PDCCH is a PDCCH having a regular Downlink Control Information (DCI) format. The second PDCCH is a PDCCH having a fallback DCI format. The method may also include receiving 2313 the PDSCH upon detection of the first PDCCH or the second PDCCH. The PDSCH is rate matched around one or more resource sets if scheduled by the first PDCCH. The PDSCH is not rate matched around one or more resource sets if scheduled by the second PDCCH.

Fig. 24 shows a flow chart of a method for a gNB. The present invention describes a method for the gNB 160. The method may include sending 2420 a dedicated Radio Resource Control (RRC) configuration including information indicating one or more resource sets for Physical Downlink Shared Channel (PDSCH) rate matching. The method may also include transmitting 2421 the first PDCCH. The method may also include transmitting 2422 a second PDCCH. The first PDCCH is a PDCCH having a regular Downlink Control Information (DCI) format. The second PDCCH is a PDCCH having a fallback DCI format. The method may also include transmitting 2423 the PDSCH on the first PDCCH or the second PDCCH transmission. The PDSCH is rate matched around one or more resource sets if scheduled by the first PDCCH. The PDSCH is not rate matched around one or more resource sets if scheduled by the second PDCCH.

Fig. 25 shows a flow chart of a method for a UE. The method may include obtaining 2530 a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET). The method may also include obtaining 2531 a second RRC configuration including second information indicating one or more search space sets. The method may also include obtaining 2532 a third RRC configuration including third information indicating a set of Physical Downlink Shared Channel (PDSCH) rate matching resources. The method may also include monitoring 2533 a Physical Downlink Control Channel (PDCCH). The method may also include receiving 2534 the PDSCH upon detection of the PDCCH. One or more sets of search spaces may be associated with CORESET. The third information may indicate an identity of CORESET. The resource set may be determined by at least a frequency domain resource allocation of CORESET, a time domain duration of CORESET, and a monitoring period and offset of one or more search space sets.

Fig. 26 shows a flow chart of a method for a base station. The method may include sending 2640 a first Radio Resource Control (RRC) configuration including first information indicating a control resource set (CORESET). The method may also include sending 2641 a second RRC configuration including second information indicating one or more search space sets. The method may also include sending 2642 a third RRC configuration including third information indicating a set of Physical Downlink Shared Channel (PDSCH) rate matching resources. The method may also include transmitting 2643 a Physical Downlink Control Channel (PDCCH). The method may also include transmitting 2644 the PDSCH at the time of PDCCH transmission. One or more sets of search spaces may be associated with CORESET. The third information may indicate an identity of CORESET. The resource set may be determined by at least a frequency domain resource allocation of CORESET, a time domain duration of CORESET, and a monitoring period and offset of one or more search space sets.

It should be noted that various modifications are possible within the scope of the present invention defined by the claims, and embodiments obtained by appropriately combining technical means disclosed according to different embodiments are also included in the technical scope of the present invention.

It should be noted that in most cases, UE102 and gNB160 may have to assume the same procedure. For example, when UE102 follows a given procedure (e.g., the procedure described above), gNB160 may also have to assume that UE102 follows the procedure. In addition, the gNB160 may also have to perform corresponding procedures. Similarly, when gNB160 follows a given procedure, UE102 may also have to assume that gNB160 follows the procedure. In addition, the UE102 may also have to perform corresponding procedures. Physical signals and/or channels received by UE102 may be transmitted by gNB 160. The physical signals and/or channels transmitted by UE102 may be received by gNB 160. Higher layer signals and/or channels (e.g., dedicated RRC configuration messages) acquired by UE102 may be transmitted by gNB 160. Higher layer signals and/or channels (e.g., dedicated RRC configuration messages) transmitted by UE102 may be acquired by gNB 160.

It should be noted that the names of physical channels and/or signals described herein are examples.

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.

For example, one or more of the methods described herein may be implemented in and/or using a chipset, an Application Specific Integrated Circuit (ASIC), a large scale integrated circuit (L SI), an integrated circuit, or the like.

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 UE102 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, some or all of the gNB160 and the UE102 according to the above-described system and method may be implemented as typical integrated circuits, each of the functional blocks of the gNB160 and the UE102 may be separately built into a chip, and some or all of the functional blocks may be integrated into a chip.

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.