RU2771959C2 - User equipment, base stations and methods - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: method for communication for user equipment (UE) includes stages of: by means of radio resource control (RRC) configuration messages, receiving a first information for indicating the slot format, a second information for configuring downlink reception(s), and a third information for configuring uplink transmission(s); wherein for a set of slot characters indicated as flexible by means of the first information, the UE does not expect to receive neither the second information configuring downlink reception(s) by the user equipment in the set of slot characters, nor the third information configuring uplink transmission(s) from the user equipment in the set of slot characters, the first information is included in the general RRC configuration message, and the second information and the third information are included in one or more special RRC configuration messages.

EFFECT: increase in the flexibility and/or efficiency of data exchange.

8 cl, 9 tbl, 24 dwg

Description

RELATED APPLICATIONS

[0001] This application relates to U.S. Provisional Application No. 62/616,337 entitled USER EQUIPMENTS, BASE STATIONS AND METHODS, filed January 11, 2018, the contents of which are hereby incorporated by reference in their entirety and claims priority thereon.

FIELD OF TECHNOLOGY

[0002] The present description relates essentially to communication systems. More specifically, the present disclosure relates to novel signaling systems, procedures, user equipment (UE) and user equipment base stations, base stations and methods.

BACKGROUND OF THE INVENTION

[0003] Wireless communication devices are now available in smaller sizes and higher power to meet consumer needs and improve portability and convenience. Consumers have become addicted to wireless devices and have come to expect reliable service, extended coverage areas and enhanced functionality. A wireless communication system may communicate with a number of wireless communication devices, each of which is served by a base station. A base station may be a device that communicates with wireless communication devices.

[0004] As wireless communication devices have evolved, it has been possible to improve throughput, speed, flexibility, and/or efficiency. However, improvements in throughput, speed, flexibility and/or efficiency may be associated with certain problems.

[0005] For example, wireless communication devices 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 illustrated herein, systems and methods that increase the flexibility and/or efficiency of communication can be advantageous.

BRIEF DESCRIPTION OF GRAPHICS

[0006] In FIG. 1 is a block diagram illustrating one embodiment of one or more gNBs and one or more user equipments (UEs) in which systems and methods for downlink and uplink transmission may be implemented.

[0007] In FIG. 2 shows various components that can be used in a UE.

[0008] In FIG. 3 shows various components that can be used in gNB.

[0009] In FIG. 4 is a block diagram illustrating one embodiment of a UE in which systems and methods for downlink and uplink transmission may be implemented.

[0010] In FIG. 5 is a block diagram illustrating one embodiment of a gNB in which systems and methods for downlink and uplink transmission can be implemented.

[0011] In FIG. 6 is a diagram illustrating one example of a resource.

[0012] In FIG. 7 shows examples of several numerologies.

[0013] In FIG. 8 shows examples of subframe structures for the numerologies shown in FIG. 7.

[0014] In FIG. 9 shows examples of subframe structures for the numerologies shown in FIG. 7.

[0015] In FIG. 10 shows examples of slots and subslots.

[0016] In FIG. 11 shows examples of the planning timeline.

[0017] In FIG. 12 is a block diagram illustrating one implementation of gNB.

[0018] In FIG. 13 is a block diagram illustrating one embodiment of a UE.

[0019] In FIG. 14 shows an example of a control resource unit and a reference signal structure.

[0020] In FIG. 15 shows an example of multiplexing a control channel and a shared channel.

[0021] In FIG. 16 shows PDCCH tracking events for slot-based scheduling.

[0022] In FIG. 17 shows PDCCH tracking events for non-slot-based scheduling.

[0023] In FIG. 18 shows an example of slot formats for this slot.

[0024] In FIG. 19 shows an example of a downlink scheduling and hybrid automatic repeat request (HARQ) timeline.

[0025] In FIG. 20 shows an example of an uplink scheduling timeline.

[0026] In FIG. 21 shows an example timeline of aperiodic downlink channel status information reference signal (CSI-RS) transmission.

[0027] In FIG. 22 shows an example timeline of an aperiodic uplink sounding reference signal (SRS) transmission.

[0028] In FIG. 23 shows a flowchart of a method for a UE.

[0029] In FIG. 24 is a flow diagram for gNB.

DETAILED DESCRIPTION

[0001] A description of the user equipment (UE) is provided. The UE may include a high-level processor configured to obtain, via radio resource control (RRC) configuration messages, first information for specifying a slot format, second information for configuring downlink reception(s), and third information for configuring transmission(s) uplink. The UE may also include a reception circuit configured to perform downlink reception(s). The UE may further include a transmission scheme configured to perform transmission(s) on the uplink. For the slot symbol set that is designated as flexible in the first information, the UE may not expect to receive both the second information configuring the downlink reception(s) of the UE in the slot symbol set and the third information configuring the transmission(s) on the uplink from the UE in the slot symbol set. If the downlink reception(s) and uplink transmission(s) are configured for the same character set in a slot, the slot format in the first information may indicate the same character set as the characters for downlink transmission or uplink but not as flexible.

[0002] A base station capable of communicating with a user equipment (UE) has been described. The base station may include a high-level processor configured to transmit, via radio resource control (RRC) configuration messages, first information for specifying a slot format, second information for configuring downlink reception(s) by the UE, and third information for configuring transmission ( transmissions) on the uplink from the UE. The base station may also include a transmission scheme configured to perform downlink transmission(s) corresponding to downlink reception(s) by the UE. The base station may further include a reception circuit configured to perform uplink reception(s) corresponding to uplink transmission(s) from the UE. For the slot symbol set that is designated as flexible in the first information, the UE may not expect to receive both the second information configuring the downlink reception(s) of the UE in the slot symbol set and the third information configuring the transmission(s) on the uplink from the UE in the slot symbol set. If the downlink reception(s) and uplink transmission(s) are configured for the same character set in a slot, the slot format in the first information may indicate the same character set as the characters for downlink transmission or uplink but not as flexible.

[0003] A method for user equipment (UE) is described. The method may include receiving, via radio resource control (RRC) configuration messages, first information for specifying a slot format, second information for configuring downlink reception(s), and third information for configuring uplink transmission(s). The method may also include performing the receive(s) on the downlink. The method may further include performing uplink transmission(s). For the slot symbol set that is designated as flexible in the first information, the UE may not expect to receive both the second information configuring the downlink reception(s) of the UE in the slot symbol set and the third information configuring the transmission(s) on the uplink from the UE in the slot symbol set. If the downlink reception(s) and uplink transmission(s) are configured for the same character set in a slot, the slot format in the first information may indicate the same character set as the characters for downlink transmission or uplink but not as flexible.

[0004] A method is described for a base station configured to communicate with a user equipment (UE). The method may include sending, via radio resource control (RRC) configuration messages, first information for specifying a slot format, second information for configuring downlink reception(s) by the UE, and third information for configuring uplink transmission(s) from the UE. . The method may also include performing downlink transmission(s) corresponding to downlink reception(s) by the UE. The method may further include performing the uplink reception(s) corresponding to the uplink transmission(s) from the UE. For the slot symbol set that is designated as flexible in the first information, the UE may not expect to receive both the second information configuring the downlink reception(s) of the UE in the slot symbol set and the third information configuring the transmission(s) on the uplink from the UE in the slot symbol set. If the downlink reception(s) and uplink transmission(s) are configured for the same character set in a slot, the slot format in the first information may indicate the same character set as the characters for downlink transmission or uplink but not as flexible.

[0005] A description of the user equipment (UE) is provided. The UE may include a higher level processor configured to receive a generic and/or specific Radio Resource Control (RRC) configuration message and one or more specific RRC configuration messages. The general RRC message may include first information for indicating a slot format. The one or more specific RRC configuration messages include second information for configuring the semi-static downlink and third information for configuring the semi-static uplink. The UE may also include a reception scheme configured to receive a semi-static downlink. The UE may further include a transmission scheme configured for semi-static uplink transmission. If semi-static downlink and semi-static uplink are configured for the same character set, the slot format designates the same character set as the characters for downlink or uplink transmission, but not as flexible.

[0006] In addition, a description of gNB is provided. The gNB may include a higher level processor configured to send a generic and/or specific Radio Resource Control (RRC) configuration message and one or more specific RRC configuration messages. The general RRC message may include first information for indicating a slot format. The one or more specific RRC configuration messages include second information for configuring the semi-static downlink and third information for configuring the semi-static uplink. The gNB may also include a transmission scheme capable of semi-static downlink. The gNB may further include a receive circuit configured to receive a semi-static uplink. If semi-static downlink and semi-static uplink are configured for the same character set, the slot format designates the same character set as the characters for downlink or uplink transmission, but not as flexible.

[0007] The 3rd Generation Partnership Project, also referred to as 3GPP, is a collaborative agreement to define globally applicable specifications and technical reports for 3rd and 4th generation wireless communication systems. 3GPP may define characteristics for next generation mobile communication networks, systems and devices.

[0008] The 3GPP Long Term Telecommunications Evolution (LTE) standard is a name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile device or telephone standard to meet future requirements. In one aspect, the UMTS system is modified to provide support and specification for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0009] At least some aspects of the systems and methods described herein may be described in connection with 3GPP LTE, LTE-Advanced (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15), including the new radio network (NR), also known as 5G. However, the scope of the present description should not be limited in this regard. At least some aspects of the systems and methods described herein can be used in other types of wireless communication systems.

[0010] A wireless communications device may be an electronic device used to transmit voice and/or data to a base station, which may in turn communicate with a network of devices (e.g., the public switched telephone network (PSTN), the Internet, etc.). .d.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, user equipment, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, electronic readers, wireless modems, vehicles, Internet of Physical Object (IoT) devices, and so on. In the 3GPP specifications, a wireless communication device is usually referred to as a UE. However, since the scope of the present description should not be limited by the 3GPP standards, the terms UE and "wireless device" can be used interchangeably herein, with the more general term "wireless device" being understood. A UE may also be referred to more generally as a terminal device.

[0011] In the 3GPP specification, a base station is commonly referred to as Node B, Evolved Node B (eNB), Home Enhanced or Evolved Node B (HeNB), Next Generation Node B (gNB), or some other similar terminology. Since the scope of the description should not be limited by the 3GPP standards, the terms "base station", "Node B", eNB, HeNB and gNB can be used interchangeably herein, with the more general term "base station" being understood. In addition, the term "base station" may be used to refer to an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (eg, a local area network (LAN), the Internet, etc.). The term "communication device" may be used to refer to a wireless communication device and/or a base station. eNB and gNB may also be referred to more generally as a base station device.

[0012] It should be noted that, as used herein, the term "cell" can be any set of communication channels that are specified through standardization or regulated by regulatory bodies for use as an International Mobile Telecommunications Advanced (IMT-Advanced) standard, with the entire set or a subset of it may be accepted by 3GPP as licensed frequency bands (eg, frequency bands) to be used for communication between the eNB and the UE. It should also be noted that in the general description of E-UTRA and E-UTRAN herein, the term "cell" may be defined as "a combination of downlink and optionally uplink resources". The relationship between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

[0013] "Configured cells" are cells that are known to the UE and have permission from the eNB to transmit or receive information. "Configured cells" may be serving cells. The UE may receive system information and perform the required measurements on all configured cells. "Configured(s) cell(s)" for radio communication may (may) contain one primary cell and/or none, one or more secondary cells. By "activated cells" is meant those configured cells over which the UE transmits and receives. Thus, activated cells are those cells for which the UE monitors the Physical Downlink Control Channel (PDCCH) and, in downlink transmission, those cells for which the UE decodes the Physical Shared Channel for downlink data transmission ( PDSCH). "Deactivated cells" are those configured cells for which the UE does not control the transmission PDCCH. It should be noted that "cell" can be described by various indicators. For example, a "cell" may have temporal, spatial (eg, geographic), and frequency characteristics.

[0014] 5th generation communication systems, named NR (New Radio Network) in 3GPP, use time/frequency/space resources to provide services such as data transmission using advanced mobile broadband (eMBB), ultra reliable communication with low latency (URLLC) and streaming machine-to-machine communication (eMTC). In addition, NR uses single-path and/or multi-path operations for downlink and/or uplink transmissions.

[0015] Various examples of the systems and methods described herein are described below with reference to the drawings, where like reference numerals may indicate similar functional elements. The systems and methods that are essentially described and illustrated in the figures herein may be arranged and developed in a wide variety of different implementations. Thus, the following more detailed description of the several embodiments that are presented in the figures is not intended to limit the scope of the claimed invention, but merely represents systems and methods.

[0016] In FIG. 1 is a block diagram illustrating one embodiment of one or more gNBs 160 and one or more UEs 102 in which systems and methods for downlink and uplink transmission may be applied. One or more UEs 102 communicate with one or more gNBs 160 using one or more physical antennas 122a-n. For example, UE 102 transmits electromagnetic signals to gNB 160 and receives electromagnetic signals from gNB 160 using one or more physical antennas 122a-n. gNB 160 communicates with UE 102 using one or more physical antennas 180a-n.

[0017] UE 102 and gNB 160 may use one or more channels and/or one or more signals 119, 121 to communicate. For example, UE 102 may transmit information or data to gNB 160 using one or more uplink channels 121. communication lines. Examples of uplink channels 121 include a physical shared data channel (eg, PUSCH (Physical Uplink Data Shared Channel)) and/or a physical control channel (eg, PUCCH (Physical Uplink Control Channel). one or more gNBs 160 may also transmit information or data to one or more UEs 102 using, for example, one or more downlink channels 119. Examples of downlink channels 119 include a physical shared channel (e.g., PDSCH (Physical Downlink Data Shared Channel)) and/or a physical control channel (PDCCH (Physical Downlink Control Channel)) and so on. .d. Other types of channels and/or signals may also be used.

[0018] Each of 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 module 124 UE operations. For example, UE 102 may implement one or more receive and/or transmit paths. For convenience, only one transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown at UE 102, although many parallel elements (eg, transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0019] Transceiver 118 may include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 may receive signals from gNB 160 using one or more antennas 122a-n. For example, receiver 120 may receive and downconvert signals 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 signal to gNB 160 using one or more physical antennas 122a-n. For example, one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.

[0020] Demodulator 114 may demodulate one or more received signals 116 to create one or more demodulated signals 112. One or more demodulated signals 112 may be provided to decoder 108. To decode signals, UE 102 may use decoder 108. Decoder 108 may generate decoded signals 110, which may include UE decoded signal 106 (also referred to as first UE decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in decoded signals 110 (also referred to as second UE-decoded signal 110) may include overhead 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.

[0021] Typically, UE operations module 124 may enable UE 102 to communicate with one or more gNBs 160. UE operations module 124 may include one or more UE scheduling modules 126 .

[0022] UE scheduling module 126 may perform uplink transmissions. Uplink transmissions include data transmission and/or transmission of a reference signal on the uplink.

[0023] Physical channels (uplink physical channels and/or downlink physical channels) may be defined in a radio communication system. Physical channels (uplink physical channels and/or downlink physical channels) may be used to carry information coming from a higher layer. For example, a physical control channel (PCCH) may be defined. The PCCH is used to transmit control information.

[0024] In the uplink, the PCCH (eg, Physical Uplink Control Channel (PUCCH)) is used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request (HARQ-ACK), channel state information (CSI), and/or a scheduling request (SR). HARQ-ACK is used to indicate a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for downlink data (i.e., transport unit(s), a media access control protocol data unit (MAC PDU), and /or Downlink Shared Channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel. The SR is also used to request uplink data resources (ie, transport unit(s), MAC PDUs, and/or uplink shared channel (UL-SCH)).

[0025] In the downlink, a PCCH (eg, a physical downlink control channel (PDCCH)) can be used to transmit downlink control information (DCI). In this case, more than one DCI format may be defined for DCI transmission on the PDCCH. In particular, fields can be defined in the DCI format and the fields are mapped to (mapped to) information bits (ie, DCI bits). For example, the DCI format 1A used for scheduling one physical shared channel (PSCH) (eg, PDSCH, one downlink transport block transmission) in a cell is defined as the downlink DCI format. The DCI format(s) for PDSCH scheduling may include a plurality of information fields, such as a carrier indicator field, a frequency domain PDSCH resource allocation field, a time domain PDSCH resource allocation field, a pooling size field, an MCS field, an indicator field new data, redundancy version field, HARQ process number field, code block reset indicator (CBGFI) field, code block transmission indicator (CBGTI) field, PUCCH power control field, PUCCH resource indicator field, antenna port field, layer number field, a quasi-collocation indication (QCL) field, an SRS trigger request field, and an RNTI field. More than one piece of the above information may be jointly encoded, in which case the jointly encoded information may be indicated in one information field.

[0026] For example, DCI format 0 used for scheduling one PSCH (eg, PUSCH, transmission of one uplink transport block) in one cell is defined as the uplink DCI format. For example, the DCI format includes information related to PSCH allocation (PDSCH resource, PUSCH resource), modulation and coding scheme (MCS) related information for PSCH, and DCI, such as a transmit power control (TPC) command for PUSCH and/or PUCCH. In addition, the DCI format may include information associated with the beam index and/or antenna port. The beam index may indicate a beam used for downlink transmissions and uplink transmissions. The antenna port may include a DL antenna port and/or a UL antenna port. The DCI format(s) for PUSCH scheduling may include a plurality of information fields, e.g., a carrier indicator field, a PUSCH resource allocation field in the frequency domain, a PUSCH resource allocation field in the time domain, a pooling size field, an MCS field, an indicator field new data, redundancy version field, HARQ process number field, code block reset indicator (CBGFI) field, code block transmission indicator (CBGTI) field, PUSCH power control field, SRS resource indicator (SRI) field, precoding matrix indicator field transmission over band and/or subband (TPMI), an antenna port field, a scrambling identification data field, a layer number field, a CSI report trigger request field, a CSI measurement request field, an SRS trigger request field, and an RNTI field. More than one piece of the above information may be jointly encoded, in which case the jointly encoded information may be indicated in one information field.

[0027] For example, PSCH can also be defined. For example, in the event that a downlink PSCH resource (eg, a PDSCH resource) is scheduled using the DCI format, UE 102 may receive downlink data on the scheduled downlink PSCH resource. In addition, in the event that an uplink PSCH resource (eg, a PUSCH resource) is scheduled using the DCI format, the UE 102 transmits uplink data on the scheduled uplink PSCH resource. Thus, the downlink PSCH is used to transmit downlink data. And the uplink PSCH is used to transmit uplink data.

[0028] Moreover, the downlink PSCH and the uplink PSCH are used to transmit higher layer information (eg, Radio Resource Control (RRC) layer and/or MAC layer). For example, the downlink PSCH and the uplink PSCH are used to transmit an RRC message (RRC signal) and/or a MAC control element (MAC CE). Here, the RRC message transmitted from gNB 160 on the downlink may be common to multiple UEs 102 in a cell (referred to as a common RRC message). In addition, an RRC message sent from gNB 160 may be allocated to a specific UE 102 (referred to as a custom RRC message). The RRC message and/or MAC CE is also referred to as the higher layer signal.

[0029] In addition, in uplink radio communication, UL RS is used as uplink physical signal(s). The uplink physical signal is not used to convey the information provided by the higher layer, however, it can be used in the physical layer. For example, the UL RS may include demodulation reference(s), UE-specific reference(s), reference(s) ) sounding and/or individual(s) for the beam reference(s) signal(s). The demodulation reference signal(s) may include the demodulation reference signal(s) associated with the uplink physical channel transmission (e.g., PUSCH and/or PUCCH ).

[0030] In addition, the UE-specific reference signal(s) may include the reference signal(s) associated with the uplink physical channel transmission. (eg PUSCH and/or PUCCH). For example, the demodulation reference(s) and/or the UE-specific reference(s) may be valid reference(s) ) to demodulate the uplink physical channel only if the uplink physical channel transmission is associated with the corresponding antenna port. gNB 160 may use demodulation reference(s) and/or UE-specific reference(s) to perform configuration (reconfiguration) of uplink physical channels. The sounding reference signal can be used to measure the state of the uplink channel.

[0031] UE operations module 124 may provide information 148 to one or more receivers 120. For example, UE operations module 124 may inform receiver(s) 120 of when a transmission was received.

[0032] UE operations unit 124 may provide information 138 to demodulator 114. For example, UE operations unit 124 may inform demodulator 114 of a modulation scheme intended for transmissions from gNB 160.

[0033] UE operations module 124 may provide information 136 to decoder 108. For example, UE operations module 124 may inform decoder 108 of the intended encoding of transmissions from gNB 160.

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

[0035] Encoder 150 may encode transmission data 146 and/or other information 142 provided by UE operations module 124. For example, encoding of transmission data 146 and/or other information 142 may include error detection and/or correction coding, mapping of data to space, time, and/or frequency resources for transmission, multiplexing, and so on. Encoder 150 may provide encoded data 152 to modulator 154.

[0036] UE operations unit 124 may provide information 144 to modulator 154. For example, UE operations unit 124 may inform modulator 154 of the modulation type (eg, constellation mapping) to be used for gNB 160 transmissions. Modulator 154 may modulate encoded data 152 to feed one or more modulated signals 156 to one or more transmitters 158.

[0037] 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 instruct one or more transmitters 158 when to transmit the signal. on gNB 160. For example, one or more transmitters 158 may transmit during a UL subframe. One or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.

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

[0039] Transceiver 176 may include one or more receivers 178 and one or more transmitters 117. One or more receivers 178 may receive signals from UE 102 using one or more physical antennas 180a-n. For example, receiver 178 may receive and downconvert signals to generate one or more received signals 174. One or more received signals 174 may be provided to demodulator 172. One or more transmitters 117 may signal to UE 102 using one or more physical antennas 180a-n. For example, one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

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

[0041] Typically, gNB operations module 182 may provide gNB 160 with the ability to communicate with one or more UE 102. gNB operations module 182 may include one or more gNB scheduling modules 194. gNB scheduling module 194 may perform uplink transmission scheduling as described herein.

[0042] gNB operations module 182 may provide information 188 to demodulator 172. For example, gNB operations module 182 may inform demodulator 172 of a modulation scheme intended for transmissions from one or more UEs 102.

[0043] gNB station operations module 182 may provide information 186 to decoder 166. For example, gNB station operations module 182 may inform decoder 166 of the expected coding of transmissions from one or more UEs 102.

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

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

[0046] gNB operations module 182 may provide information 103 to modulator 113. This information 103 may include instructions for modulator 113. For example, gNB station operations module 182 may inform modulator 113 of the modulation type (eg, constellation mapping) to be used for transmissions from one or more UEs 102. Modulator 113 may modulate encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0047] gNB station operations module 182 may provide information 192 to one or more transmitters 117. This information 192 may include instructions for one or more transmitters 117. For example, gNB station operations module 182 may instruct one or more transmitters 117 about the time transmission (or non-transmission time) of the signal to one or more UEs 102. One or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.

[0048] It should be noted that a DL subframe may be transmitted from gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to gNBs 160. Moreover, both gNBs 160 and one or more UE 102 may transmit data in a standard dedicated subframe.

[0049] It should also be noted that one or more elements or parts thereof included in one or more gNBs 160 and one or more UEs 102 may be implemented as hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuit, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and/or accomplished through its use. For example, one or more of the methods described herein may be implemented and/or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0050] In FIG. 2 illustrates various components that can be used in UE 202. UE 202 described in connection with FIG. 2 may be implemented in accordance with UE 22 described in connection with FIG. 1. UE 202 includes a processor 203 that controls the operation of UE 202. Processor 203 may also be referred to as a central processing unit (CPU). Memory 205, which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination thereof, or any type of device that can store information, provides processor 203 with instructions 207a and data 209a. The memory portion 205 may also include a non-volatile random access memory (NRAM). Instructions 207b or data 209b may also reside in processor 203. Instructions 207b and/or data 209b loaded into processor 203 may also include instructions 207a and/or data 209a from memory 205 that have been loaded for execution or processing by the processor. 203. Processor 203 may execute instructions 207b to implement the methods described above.

[0051] UE 202 may also include a housing that contains one or more transmitters 258 and one or more receivers 220 to enable data transmission and reception. Transmitter(s) 258 and receiver(s) 220 may be combined into one or more transceivers 218. Attached to the housing are one or more antennas 222a-n that are electrically coupled to transceiver 218.

[0052] The various components of the UE 202 are connected to each other by a bus system 211, which, in addition to a data bus, may include a power bus, a control signal bus, and a status signal bus. However, for clarity, various tires are illustrated in FIG. 2 as a bus system 211. UE 202 may also include a digital signal processor (DSP) 213 for use in signal processing. UE 202 may also include a communication interface 215 that provides user access to functions of UE 202. UE 202 illustrated in FIG. 2 is a functional block diagram, not a list of specific components.

[0053] In FIG. 3 illustrates various components that can be used in gNB 360. gNB 360 described in connection with FIG. 3 may be implemented in accordance with gNB 160 described in connection with FIG. 1. gNB 360 includes a processor 303 that controls the operation of gNB 360. Processor 303 may also be referred to as a central processing unit (CPU). Memory 305, which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination thereof, or any type of device that can store information, provides processor 303 with instructions 307a and data 309a. The memory portion 305 may also include a non-volatile random access memory (NRAM). Instructions 307b or data 309b may also reside in processor 303. Instructions 307b and/or data 309b loaded into processor 303 may also include instructions 307a and/or data 309a from memory 305 that have been loaded for execution or processing by the processor. 303. The processor 303 may execute instructions 307b to implement the methods described above.

[0054] gNB 360 may also include a housing that contains one or more transmitters 317 and one or more receivers 378 to enable data transmission and reception. The transmitter(s) 317 and receiver(s) 378 may be combined into one or more transceivers 376. Attached to the housing are one or more antennas 380a-n that are electrically coupled to the transceiver 376.

[0055] The various components of the gNB 360 are connected to each other via a bus system 311, which, in addition to a data bus, may include a power bus, a control signal bus, and a status signal bus. However, for clarity, various tires are illustrated in FIG. 3 as a bus system 311. gNB 360 may also include a digital signal processor (DSP) 313 for use in signal processing. gNB 360 may also include a communications interface 315 that provides user access to the functions of gNB 360. gNB 360 illustrated in FIG. 3 is a functional block diagram, not a list of specific components.

[0056] In FIG. 4 is a block diagram illustrating one embodiment of UE 402 in which systems and methods for performing downlink and uplink transmissions may be implemented. UE 402 includes a transmit means 458, a receive means 420, and a control means 424. Transmit means 458, receive means 420, and control means 424 may be configured to perform one or more of the functions described in connection with FIG. 1. In FIG. 2 above illustrates one example of a specific structure of the device shown in FIG. 4. To perform one or more of the functions shown in FIG. 1, various other structures may be implemented. For example, a DSP may be implemented in software.

[0057] In FIG. 5 is a block diagram illustrating one embodiment of gNB 560 in which systems and methods for performing downlink and uplink transmissions may be implemented. gNB 560 includes a transmit means 517, a receive means 578, and a control means 582. The transmit means 517, the receive means 578, and the control means 582 may be configured to perform one or more of the functions described in connection with FIG. 1. In FIG. 3 above illustrates one example of a specific structure of the device shown in FIG. 5. To perform one or more of the functions shown in FIG. 1, various other structures may be implemented. For example, a DSP may be implemented in software.

[0058] In FIG. 6 is a diagram illustrating one example of a resource grid. The resource grid shown in Fig. 6 can be applied to both downlink and uplink, and can also be used in some embodiments of the systems and methods described herein. More details regarding the resource grid are given in connection with FIG. one.

[0059] In FIG. 6, one subframe 669 may include one or more slots 683. For a given numerology µ, N ^µ _RB is the serving cell downlink bandwidth configuration expressed in multiples of N ^RB _SC , where N ^RB _SC is the resource block size 689 in the frequency domain, expressed in terms of the number of subcarriers, and N ^SF,µ _symb is the number of orthogonal frequency division multiplexing (OFDM) symbols 687 in subframe 669. In other words, for each numerology µ and for each of the uplink and downlink connection, a resource grid of N ^µ _RB N ^RB _SC subcarriers and N ^SF,µ symb OFDM symbols can be defined. One resource grid may be defined per antenna port p, per subcarrier spacing pattern µ (ie numerology), and per transmission direction (uplink or downlink). Resource block 689 may include a number of resource elements (REs) 691.

[0060] A variety of OFDM numerologies (also referred to simply as numerologies) are supported, as shown in Table X1. Each of the numerologies can be tied to its own subcarrier spacing Δƒ.

Table X1

µ Δƒ=2 ^µ 15 [kHz] Cyclic prefix 0 fifteen Normal one thirty Normal 2 60 normal, extended 3 120 Normal 4 240 Normal 5 480 Normal

[0061] For the subcarrier spacing configuration µ, the slots are numbered n ^µ _S ϵ {0,..., N ^SF,µ _slot - l} in ascending order within one subframe and n ^µ _s,f ϵ {0,..., N ^{frame ,µ} _slot - 1} in ascending order within one frame. A total of one slot contains N ^slot,µ _symb consecutive OFDM symbols, where N ^slot,µ _symb depends on the used subcarrier spacing and slot configuration as specified in table X2 for normal cyclic prefix and table X3 for extended cyclic prefix. The number of consecutive OFDM symbols in a subframe is N ^SF,µ _symb= N ^slot,µ _symb .N ^SF,µ _slot . The start of slot n ^µ _s in a subframe is timed to the start of symbol n ^µ _s N ^slot,µ _symb OFDM in the same subframe. Not all UEs may be configured to transmit and receive simultaneously, i. e. not all OFDM symbols in a downlink slot or uplink slot may be used.

Table X2

µ Slot Configuration 0 one N ^slot,µ _symb N ^frame,µ _slot N ^SF,µ _slot N ^slot,µ _symb N ^frame,µ _slot N ^SF,µ _slot 0 fourteen ten one 7 20 2 one fourteen 20 2 7 40 4 2 fourteen 40 4 7 80 eight 3 fourteen 80 eight - - - 4 fourteen 160 sixteen - - - 5 fourteen 320 32 - - -

Table X3

µ Slot Configuration 0 one N ^slot,µ _symb N ^frame,µ _slot N ^SF,µ _slot N ^slot,µ _symb N ^frame,µ _slot N ^SF,µ _slot 2 12 40 4 6 80 eight

[0062] For PCell N ^µ _RB is a broadcast as part of the system information. For SCell (including _Scell with Licensed Bandwidth Access (LAA)) N ^µ _RB is configured by UE 102 specific RRC message. _,start and/or 1 _data,end ≥ l in a subframe.

[0063] A cyclic prefix (CP) OFDM access scheme may be used, which may also be referred to as CP-OFDM. In the downlink, PDCCH, EPDCCH (Enhanced Physical Downlink Control Channel), PDSCH, and the like may be transmitted. One radio frame may include a set of subframes 669 (eg, 10 subframes). The RB is a block for assigning downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and one or more OFDM symbols.

[0064] A resource block is a block defined as N ^RB _SC= 12 consecutive subcarriers in the frequency domain.

[0065] The carrier resource blocks are numbered from 0 to N ^µ _RB - 1 in the frequency domain for the subcarrier spacing configuration µ. The relationship between the number n _CRBs of carrier resource blocks in the frequency domain and the resource elements (k, l) is expressed as n _CRB= floor(k/N ^RB _SC ), where the value of k is determined depending on the resource grid. The physical resource blocks are formed in a carrier bandwidth fraction (BWP) and are numbered from 0 to N ^size _BWP,i - 1 where i is the carrier bandwidth fraction number. The relationship between physical and absolute resource blocks in the carrier bandwidth portion i is expressed as n _CRB =n _PRB +N ^start _BWP,i – 1, where N ^start _BWP,i is the carrier resource block from which the carrier bandwidth portion begins. The virtual resource blocks are formed in a portion of the carrier bandwidth and are numbered from 0 to N ^size _BWP,i - 1, where i is the number of the portion of the carrier bandwidth.

[0066] The carrier bandwidth portion is a contiguous set of physical resource blocks selected from a contiguous subset of carrier resource blocks for a given numerology µ on a given carrier. The number of resource blocks N ^size _BWP,i in a BWP carrier may satisfy the condition N ^min,µ _RB,x <= N ^size _BWP,i <= N ^max,µ _RB,x . The UE may be configured with up to four downlink carrier bandwidth fractions, with any one downlink carrier bandwidth fraction active at any given time. The UE is not designed to receive the PDSCH or PDCCH outside of the active portion of the bandwidth. The UE may be configured with up to four uplink carrier bandwidth fractions, with any one uplink carrier bandwidth fraction active at any given time. The UE shall not transmit PUSCH or PUCCH outside the active portion of the bandwidth.

[0067] An RB may comprise twelve subcarriers in the frequency domain and one or more OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is uniquely identified by a pair of indices (k, l ^RG ) in the resource grid, where k=0,…,N ^µ _RB N ^RB _sc - 1 and l ^RG= 0,…,N ^SF,µ _symb - 1 are indices in the frequency and time domains, respectively. Moreover, the RE is uniquely identified by a pair of indices (k, l) based on a certain reference point, where l are indices in the time domain. The reference point can be linked to the resource grid, i.e. to the carrier component (CC). In an alternative embodiment, the reference point may be tied to some portion of the bandwidth in the carrier component. Although the present document describes subframes in one CC, subframes are defined for each CC, and these subframes are essentially synchronized with each other among CCs.

[0068] In the uplink, in addition to CP-OFDM, a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme, which is also referred to as Discrete Fourier Transform Extended OFDM (DFT-S-OFDM), can be used. In the uplink, PUCCH, PDSCH, Physical Random Access Channel (PRACH), etc. may be transmitted.

[0069] For each numerology and carrier, a resource grid of N ^max,µ _RB,x N ^RB _sc subcarriers and N ^SF,µ _symb OFDM symbols is specified, where the value of N ^max,µ _RB,x is taken from table X4 and x is DL or UL, i.e. downlink or uplink, respectively. One resource grid may be defined per antenna port p, per subcarrier spacing configuration µ, and per transmission direction (downlink or uplink).

Table X4

µ ^Nmin,µ _RB,DL ^Nmax,µ _RB,DL ^Nmin,µ _RB,UL ^Nmax,µ _RB,UL 0 20 275 24 275 one 20 275 24 275 2 20 275 24 275 3 20 275 24 275 4 20 138 24 138 5 20 69 24 69

[0070] UE 102 may be instructed to perform reception or transmission using only a subset of the resource grid. The set of resource blocks that the UE considers to be part of the carrier bandwidth and that can be configured to receive or transmit data is numbered from 0 to N ^µ _RB - 1 in the frequency domain. The UE may be configured with one or more carrier band portions, each of which may have the same or different numerologies.

[0071] Transmissions across multiple cells can be aggregated, with up to fifteen secondary cells in addition to the primary cell. UE 102 configured to operate in portions of bandwidth (BWP) of the serving cell is configured with higher levels for the serving cell with a set of up to four portions of bandwidth (BWP) for UE receptions (DL BWP set) in DL bandwidth per parameter DL-BWP-index and a set of up to four BWP parts for UE 102 transmissions (UL BWP set) in the UL bandwidth of the UL-BWP-index parameter for the serving cell. For example, for operation in unpaired spectrum, a DL BWP part from a set of configured DL BWP parts may be associated with a UL BWP part from a set of configured UL BWP parts, and the DLBWP and UL BWP may have the same index in the respective sets. For unpaired spectrum operation, UE 102 may expect the center frequency for BWP DL to be the same as the center frequency for BWP UL.

[0072] One or more sets of PRBs may be configured to monitor a DL control channel. In other words, the frequency domain control resource set is a set of PRBs in which the UE 102 attempts to blindly decode the downlink control information (i.e., track the downlink control information (DCI)), wherein the PRBs may or may not occupy adjacent frequencies, UE 102 may have one or more control resource sets, and one DCI message may be in one control resource set. In the frequency domain, the PRB is the size of the resource unit (which may or may not include DMRS) for the control channel. The shared DL channel may start with a later OFDM symbol than the one(s) that transmit(s) the detected DL control channel. In an alternative embodiment, the shared DL channel may start with (or earlier) an OFDM symbol that is the last OFDM symbol carrying the detected DL control channel. In other words, dynamic reuse of at least a portion of resources in control resource sets for data of the same or different UE 102 can be supported, at least in the frequency domain.

[0073] Thus, UE 102 may need to monitor a set of potentially suitable PDCCHs (PDCCH candidates) in one or more control resource sets on one or more activated serving cells or portions of bandwidth (BWP) in accordance with the respective search spaces, where tracking means decoding each PDCCH candidate in accordance with the monitored DCI formats. Here, the PDCCH candidates may be candidates for which a PDCCH may be assigned and/or transmitted. A PDCCH candidate consists of one or more Control Channel Elements (CCEs). The term "snoops" means that the UE 102 attempts to decode each of the PDCCHs in the PDCCH candidate set according to all of the DCI formats being tracked.

[0074] The set of PDCCH candidates that UE 102 monitors may also be referred to as a search space. Thus, the search space is a set of resources that can be used to transmit the PDCCH.

[0075] Moreover, a common search space (CSS) and a user equipment specific search space (USS) are set (or defined, configured) in the resource area of the PDCCH. For example, a CSS may be used to convey DCI to a plurality of UEs 102. Thus, a CSS may be defined as a resource shared by a plurality of UEs 102. For example, a CSS consists of CCEs with numbers given between gNB 160 and UE 102. from CCE with indices from 0 to 15.

[0076] In this case, CSS can be used to transmit DCI to a specific UE 102. Thus, gNB 160 can transmit DCI format(s) intended for multiple UE 102 and/or format(s) ) UE 102 specific DCI. One or more CSS types are available. For example, PDCCH CSS type 0 may be defined for the DCI format scrambled using system information Radio Network Temporary Identifier (SI-RNTI) in PCell. CSS PDCCH Type 1 may be defined for DCI format scrambled using RA-RNTI (Random Access). In a further and/or alternative embodiment, CSS PDCCH Type 1 may be used for DCI format scrambled using a TC-RNTI (temporary cell) or C-RNTI (cell). Type 2 PDCCH CSS can be defined for the DCI format scrambled using the P-RNTI (paging). PDCCH CSS Type 3 can be defined for DCI format scrambled using interval (INT)-RNTI, where if the UE 102 is configured by higher layers to decode the DCI format with CRC scrambled using INT-RNTI, and also if the device UE 102 detects a DCI format with a CRC scrambled using the INT-RNTI, UE 102 may assume that UE 102 is not transmitting in the OFDM symbols and resource blocks specified in the DCI format. In a further and/or alternative embodiment, CSS PDCCH Type 3 may be used for a DCI format scrambled using another RNTI (e.g., transmit power control, TPC-RNTI, presentation indicator, PI-RNTI, slot format, SF-RNTI, semi-persistent scheduling , SPS-RNTI, no provision, GF-RNTI).

[0077] UE 102 may be assigned a Type 0 System Information Block (SIB0), also referred to as MIB, a control resource set for a PDCCH Type 0 common search space, and a subcarrier spacing and CP length for PDCCH reception. The total PDCCH type 0 search space is defined by the CCE aggregation levels and the number of candidates per CCE aggregation level. The UE may assume that the DMRS antenna port associated with PDCCH reception in the common PDCCH type 0 search space and the DMRS antenna port associated with Physical Broadcast Channel (PBCH) reception are co-located with respect to delay spread, Doppler spread, Doppler offset, average delay time, and spatial reception parameters. The PBCH carries a Service Information Block (MIB) that contains the most important pieces of system information. PDCCH with specific DCI format in common search space Type 0 The PDCCH schedules the reception of PDSCH with SIB Type 1 (SIB1) or other SI messages. The UE may be assigned the SIB1 control resource set(s) for the PDCCH type 1 common search space. The subcarrier spacing and CP length for receiving PDCCH with PDCCH type 1 common search space are the same for receiving PDCCH with PDCCH type 0 common search space. The UE may assume that the DMRS antenna port associated with PDCCH reception in the common PDCCH type 1 search space and the DMRS antenna port associated with PBCH reception are co-located with respect to delay spread, Doppler spread, Doppler shift, average delay time and spatial reception parameters. The frequency of monitoring paging events for the PDCCH in the common PDCCH type 2 search space can be configured for the UE with a higher layer parameter. The UE may be configured with higher layer signaling regardless of whether PDCCH type 3 common search space tracking is performed and/or which serving cell(s) performs such tracking.

[0078] The USS may be used to transmit DCI to a particular UE 102. In other words, the USS is determined by the resource allocated to the particular UE 102. In other words, the USS may be determined independently for each UE 102. For example, the USS may consist of CCEs with numbers which are determined based on the RNTI assigned to the gNB 160, the slot number in the radio frame, the level of aggregation, or the like.

[0079] Here, the RNTI(s) may include C-RNTI (cell-RNTI), temporary C-RNTI. In addition, the USS (position(s) USS) can be configured using gNB 160. For example, gNB 160 can configure the USS using an RRC message. In other words, the base station may send to the USS the DCI format(s) intended for a particular UE 102.

[0080] In this case, the RNTI assigned to UE 102 may be used for DCI transmission (PDCCH transmission). Specifically, CRC (cyclic redundant parity check, also simply referred to as simply CRC) parity bits generated based on DCI (or DCI format) are attached to DCI, and after attachment, the CRC parity bits are scrambled using RNTI. UE 102 may attempt to decode a DCI to which RNTI-scrambled CRC parity bits are attached and detects a PDCCH (ie, DCI, DCI format). Thus, UE 102 can decode the PDCCH with the CRC scrambled using the RNTI.

[0081] If the control resource set spans multiple OFDM symbols, a potentially suitable control channel may be associated with multiple OFDM symbols, or may be associated with a single OFDM symbol. One DL control channel element may be associated with REs defined by one PRB and one OFDM symbol. If more than one DL control channel element is used to transmit one DL control channel, aggregation of DL control channel elements can be performed.

[0082] The number of aggregated DL control channel elements is called the DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to the power of an integer. gNB 160 may inform UE 102 which potentially suitable control channels are associated with each subset of OFDM symbols in the control resource set. If one DL control channel is associated with one OFDM symbol and does not cover a plurality of OFDM symbols, the DL control channel elements are aggregated within the OFDM symbol, namely, the plurality of DL control channel elements in the OFDM symbol are aggregated. Otherwise, DL control channel elements in different OFDM symbols may be aggregated.

[0083] DCI formats can be divided into at least 4 types: regular DL, regular UL, reserved DL, and reserved UL. DCI Regular DL format and DCI Regular UL format can have the same DCI payload size. The DCI Reserved DL format and the DCI Reserved UL format may have the same DCI payload size. Tables X5, X6, X7 and X8 show examples of DCI Regular DL, DCI Regular UL, DCI Reserve DL, and DCI Reserve UL, respectively. "Required" may mean that the information field is always present regardless of the configuration (changed configuration) of the RRC. "Optional" may mean that the information field may or may not be present depending on the configuration (configuration changed) of the RRC. In DCI "DL Reserved" format and in DCI "UL Reserved" format, all information fields are mandatory so that the DCI payload size is fixed regardless of the (reconfigured) RRC configuration.

Table X5

Information field Number of bits Necessarily/
not necessary Notes header 2 Necessarily The header is used to distinguish between different DCI formats with the same DCI size. carrier indicator 0 or 3 Not necessary PDSCH resources in the frequency domain 25 Necessarily VRBs specified using resource allocation type 0 or type 1 Time Domain PDSCH Resources 2 Necessarily Index in a table configured with RRC and providing the set of OFDM symbols used for PDSCH transmission Mapping VRB to PRB one Not necessary Flag to control the mapping of VRB to PRB Reserved Resources one Not necessary Specify whether reserved resources should be excluded from PDSCH allocation Union Size one Not necessary Must choose from two pool sizes configured for PDSCH with RRC Modulation and coding scheme 5 Necessarily MCS New data indicator one Necessarily Redundancy version 2 Necessarily Modulation and coding scheme, second CW 0 or 5 Not necessary New data indicator, second CW 0 or 1 Not necessary Redundancy version, second CW 0 or 2 Not necessary HARQ process number 3 Necessarily CBGFI one Not necessary Reset code block group (CBG) indication. Consists of 1 bit if CBG retransmission is configured. CBGTI 4 Not necessary Denotes transmitted (retransmitted) CBGs. Consists of an N-bit raster if CBG is configured. TPC command for PUCCH 2 Necessarily ACK/NAK resource index (ARI) 2 Necessarily HARQ transmission timing indicator 2 To indicate ACK timing in connection with PDSCH reception Downlink allocation index 4 Not necessary DAI (DAI meter reading and DAI total) Antenna port(s) 2 Not necessary Antenna ports used (and number of levels) Transfer Configuration Indication (TCI) 2 Not necessary Provides a beam indication to indicate the estimated QCL between the DL RS antenna port(s) and the DL data link DMRS antenna port(s) with respect to at least the QCL spatial parameter CSI Request 4 Not necessary CSI Measurement Request and CSI Report Trigger for CSI on PUCCH

Table X6

Information field Number of bits Mandatory / optional Notes header 2 Necessarily The header is used to distinguish between different DCI formats with the same DCI size. carrier indicator 0 Not necessary PDSCH resources in the frequency domain 25 Necessarily VRBs specified using resource allocation type 0 or type 1 Time Domain PDSCH Resources 2 Necessarily Index in a table configured with RRC and providing the set of OFDM symbols used for PDSCH transmission Mapping VRB to PRB one Necessarily Flag to control the mapping of VRB to PRB UCI transmission information on PUSCH 2 Not necessary Beta value indication for UCI transmission on PUSCH, possibly also with other information related to UCI transmission on PUSCH Modulation and coding scheme 5 Necessarily MCS New data indicator one Necessarily Redundancy version 2 Necessarily HARQ process number 3 Necessarily HARQ process number. 3 or 4 bits CBGT1 4 Not necessary Denotes transmitted (retransmitted) CBGs. Consists of an N-bit raster if CBG is configured. TPC command for PUSCH 2 Necessarily SRI/TRI/TPMI 4 Not necessary SRS resource indicator. Jointly encoded TPMI and transmission rank index. With 1 SRS resource, at least 4 bits are used. Antenna ports 2 Not necessary Antenna ports, scrambling identification SRS Request 4 Not necessary To initiate SRS transmission on the uplink. CSI request 4 Necessarily CSI Measurement Request and CSI Reporting Trigger for CSI on PUSCH

Table X7

Information field Number of bits Mandatory / optional Notes header 2 Necessarily The header is used to distinguish between different DCI formats with the same DCI size. PDSCH resources in the frequency domain fifteen Necessarily VRBs are specified using type 1. BW is fixed or depends on some BW provided with system information (cannot be reconfigured for fallback format) Time Domain PDSCH Resources 2 Necessarily Index in a pre-built table providing the set of OFDM symbols used for PDSCH transmission Mapping VRB to PRB one Necessarily Flag to control the mapping of VRB to PRB Reserved Resources one Necessarily Specify whether reserved resources should be excluded from PDSCH allocation Modulation and coding scheme 5 Necessarily Single layer transmission only in standby mode New data indicator one Necessarily Redundancy version 2 Necessarily HARQ process number 3 Necessarily TPC command for PUCCH 2 Necessarily ACK/NAK resource index (ARI) 2 Necessarily Downlink allocation index 2 Necessarily Antenna port(s) 2 Necessarily Transmission Configuration Information (TCI) 2

Table X8

Information field Number of bits Mandatory / optional Notes header 2 Necessarily The header is used to distinguish between different DCI formats with the same DCI size. PUSCH resources in the frequency domain fifteen Necessarily VRBs are specified using type 1. BW is fixed or depends on some BW provided with system information (cannot be reconfigured for fallback format) PUSCH resources in the time domain 2 Necessarily Index in a pre-built table providing the set of OFDM symbols used for PDSCH transmission Mapping VRB to PRB one Necessarily Flag to control the mapping of VRB to PRB Modulation and coding scheme 5 Necessarily Single layer transmission only in standby mode New data indicator one Necessarily Redundancy version 2 Necessarily HARQ process number 3 Necessarily TPC command for PUSCH 2 Necessarily SRI/TRI/TPMI 4 Necessarily AP/ID/levels 2 Necessarily

[0084] In FIG. 7 shows examples of several numerologies. Numerology #1 (μ=0) can represent basic numerology. For example, a basic numerology RE is defined with a subcarrier spacing of 15 kHz in the frequency domain and a length of 2048κTS+CP (e.g., 512κTs, 160κTs, or 144κTs) in the time domain, where Ts denotes the unit of baseband sampling time, defined as 1/(15000 * 2048 ) seconds. For the m-th numerology, the subcarrier spacing may be 15 * 2 ^µ and the effective OFDM symbol length may be NuTs=2048 * 2- ^µ κTS. This may provide a character length of 2048 * 2- ^µ κTS + CP length (eg 512 * 2- ^µ κTS, 160 * 2- ^µ κTS or 144 * 2- ^µ κTS). It should be noted that κ=64, Ts=l / (Δƒ _max ^. N _f ), Δƒ _max =480·10 ³ Hz (ie Δƒ for µ=5) and N _f =4096. In other words, the subcarrier spacing of the µ+1th numerology is twice that of the µth numerology, and the symbol length of the µ+1st numerology is half that of the µth numerology symbol. On FIG. 7 shows four numerologies, but the system may support a different number of numerologies.

[0085] In FIG. 8 shows a set of example subframe structures for the numerologies shown in FIG. 7. These examples are based on the slot configuration set to 0. A slot includes 14 symbols, the slot length of the μ+1th numerology is half the slot of the μth numerology, and ultimately the number of slots in a subframe (i.e. .1 ms) is doubled. It may be noted that the radio frame may include 10 subframes, and the length of the radio frame may be 10 ms.

[0086] In FIG. 9 shows another set of example subframe structures for the numerologies shown in FIG. 7. These examples are based on the slot configuration set to 1. The slot includes 7 symbols, the slot length of the μ+1th numerology is half the slot of the μth numerology, and ultimately the number of slots in a subframe (i.e. .1 ms) is doubled.

[0087] In FIG. 10 shows examples of slots and subslots. If a subslot (ie, time domain resource allocation in units of OFDM symbols or as a set of multiple OFDM symbols) is not configured by a higher layer, UE 102 and gNB 160 may use only one slot as a scheduling unit. More specifically, a given transport block may be allocated to a slot. If the subslot is configured by a higher layer, UE 102 and gNB 160 can use the subslot as well as the slot. A subslot may include one or more OFDM symbols. The maximum number of OFDM symbols that make up a subslot may be N ^SF,µ _symb - 1. The length of the subslot may be configured through higher layer signaling. In an alternative embodiment, the subslot length may be indicated by a physical layer control channel (eg, DCI format). A subslot may start with any character in the slot, as long as it does not conflict with a control channel. There may be restrictions on the length of the mini-slot depending on the restrictions on the initial position. For example, a subslot with length N ^SF,µ _symb - 1 may start on the second symbol in the slot. The starting position of the subslot may be indicated by a physical layer control channel (eg, DCI format). In an alternative embodiment, the starting position of the subslot may be determined from information (e.g., search space index, blind decode candidate index, frequency and/or time resource indices, physical RB (PRB) index, control channel element index, control channel element aggregation level , antenna port index, etc.) of the physical layer control channel that performs data scheduling in the corresponding subslot. In cases where a subslot is configured, a given transport block may be allocated to a slot, subslot, aggregated subslots, or aggregated subslot(s) and slot. This block may also be a block for generating HARQ-ACK bits.

[0088] In FIG. 11 shows examples of the planning timeline. For the normal DL scheduling timeline, the DL control channels are assigned to the initial part of the slot. DL control channels schedule shared DL channels in the same slot. HARQ-ACKs for shared DL channels (ie, HARQ-ACKs each indicating whether a transport block was successfully detected on each shared DL channel) are reported on the UL control channels in a later slot. In this case, this slot may contain a DL transmission or a UL transmission. For the normal UL scheduling timeline, the DL control channels are associated with the slot start portion. The DL control channels schedule shared UL channels in a later slot. In these cases, the timing (time offset) between the DL slot and the UL slot may be fixed or configured through higher layer signaling. In an alternative embodiment, this may be indicated by a physical layer control channel (eg, a DL assignment DCI format, a UL grant DCI format, or another DCI format such as a common UE signaling DCI format that can be monitored in a common search space).

[0089] For the stand-alone baseline DL scheduling timeline, DL control channels are associated with the slot start portion. DL control channels schedule shared DL channels in the same slot. HARQ-ACKs for shared DL channels are reported on the UL control channels that are associated with the end of the slot. For the offline UL basic scheduling timeline, the DL control channels are associated with the slot start portion. DL control channels schedule shared UL channels in the same slot. In these cases, the slot may contain DL and UL portions, and a guard slot may be provided between DL and UL transmissions. The use of the standalone slot can be done by configuring the standalone slot. In an alternative embodiment, the use of a stand-alone slot can be done with a sub-slot configuration. In yet another alternative embodiment, the use of a standalone slot may be implemented in a shortened physical channel configuration (eg, PDSCH, PUSCH, PUCCH, etc.).

[0090] To indicate the format for one or more slots, a slot format indicator (SFI) may be specified. When using SFI, UE 102 may set at least those symbols in a given slot that are "DL", "UL", and "unknown", respectively. In addition, it may also indicate which characters in a given slot are "reserved". When using the SFI, the UE 102 may also set the number of slots for which the SFI specifies their formats. SFI can be configured with a special RRC configuration message. In an alternative and/or additional embodiment, the SFI may receive signaling over a group-wide PDCCH (eg, PDCCH with SF-RNTI). In yet another alternative and/or additional embodiment, the SFI may be broadcast on a broadcast channel via a Service Information Block (MIB) or Remaining Minimum System Information (RMSI).

[0091] For example, a 3-bit SFI can express up to 8 combinations of "DL", "UL", "unknown", and "reserved" type symbols, with each combination including N ^slot,µ _symb symbol type fragments. More specifically, given that N ^slot,µ _symb =14, one combination can be "unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown". Another combination can only consist of characters of type "DL", i.e. "DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL". Another combination can only consist of characters like "UL", i.e. "UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL". Another combination may be a combination of characters like "DL", "UL" and "reserved", such as "DL""DL""DL""DL""DL""DL""DL""DL""reserved""reserved""reserved""reserved""UL".

[0092] "DL" symbols may be available for DL receptions and CSI/RRM measurements at the UE 102 side. "UL" symbols may be available for UL transmissions at the UE 102 side. The "unknown" resource may also be referred to as "flexible" and may be overridden by at least a DCI indication. Characters of type "unknown" may be used to achieve the same purposes as characters of type "reserved", unless they have been redefined by specifying DCI and/or SFI. A "reserved" resource can be of type "do not send" and "do not receive", but cannot be overridden by a DCI/SFI indication. On unknown symbols, UE 102 may not be allowed to receive any DL and UL transmissions that are configured by a higher layer but not indicated by DCI/SFI guidelines, e.g., periodic CSI-RS, periodic CSI-IM, scheduled semi-persistent CSI- RS, Periodic CSI Report, Scheduled Semi-Persistent CSI Report, Periodic SRS, Higher-configured Primary Synchronization Signal (PSS) / Secondary SS (SSS) / PBCH.

[0093] Redefining characters of type "unknown" by DCI means that UE 102 can only receive DL and UL transmissions (PDSCH transmission, PUSCH transmission, CSI-RS aperiodic transmission, CSI-IM aperiodic resource, SRS aperiodic transmission) that are designated DCI guidelines. The "unknown" type override by SFI means that the UE 102 should consider the character type to be "DL", "UL", or "reserved" as directed by the SFI. If UE 102 receives the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource, the UE 102 may perform CSI and/or RRM measurement based on the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource. If UE 102 does not receive the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource, the UE 102 cannot use the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource to measure CSI and/or RRM.

[0094] If the serving cell is a TDD cell and is a DL-only cell (a serving cell with a downlink carrier component but no uplink carrier component), the UE 102 may interpret the "UL" type indicated by the SFI as " unknown". In an alternative embodiment, in case the serving cell is a TDD cell and is a DL-only cell, the UE 102 may interpret the UL type indicated by the SFI as "reserved". If the serving cell is a TDD cell and is a UL-only cell (a serving cell without a downlink carrier component but with an uplink carrier component), the UE 102 may interpret the "DL" type indicated by the SFI as "unknown". In an alternative embodiment, in case the serving cell is a TDD cell and is a "UL only" cell, the UE 102 may interpret the "DL" type indicated by the SFI as "reserved".

[0095] If UE 102 determines a PDCCH that indicates that the time domain resource allocation for the scheduled PDSCH includes symbol(s) of type "unknown", UE 102 may assume that the PDSCH is associated with symbol(s) of type " unknown". In this case, there are several options for handling another DL transmission (eg, aperiodic CSI-RS transmission, aperiodic CSI-IM resource) on the symbol(s) of type "unknown". The first option is that UE 102 does not receive any other DL transmissions on symbol(s) of type "unknown" except for the scheduled PDSCH. The second option is that UE 102 receives other DL transmissions on symbol(s) of type "unknown" within the resource boundaries that are allocated for the scheduled PDSCH. UE 102 does not receive any other DL transmissions on symbol(s) of type "unknown" outside of the resource boundaries that are allocated for the scheduled PDSCH. A third option is that UE 102 receives other DL transmissions on symbol(s) of type "unknown" regardless of the resource allocation for the PDSCH. In other words, character(s) of type "unknown" is interpreted as "DL".

[0096] UE 102 may monitor the PDCCH on some unknown symbols. There are several options for PDCCH tracking. If all OFDM symbols that are assigned to a given control resource set (CORESET) are of type "DL", UE 102 may consider all OFDM symbols to be valid for tracking the PDCCH associated with the given CORESET. In this case, UE 102 may consider that each CORESET PDCCH candidate is mapped to all of the OFDM symbols to map the first time REG (REG) to a Control Channel Element (CCE). If all OFDM symbols that are assigned to a given CORESET are of type "unknown", UE 102 may consider all OFDM symbols to be valid for tracking the PDCCH associated with the given CORESET. In this case, UE 102 may consider that each CORESET PDCCH candidate is mapped to all of the OFDM symbols to map the first temporally REG to the CCE.

[0097] If each OFDM symbol that is assigned to a given CORESET is of type "UL" or "reserved", UE 102 may consider these OFDM symbols invalid for tracking the PDCCH associated with the given CORESET. If some of the OFDM symbols that are assigned to this CORESET are of type "DL" and others are of type "UL" or "Reserved", or if some of the OFDM symbols that are assigned to this CORESET are of type "unknown ' and others to 'UL' or 'Reserved', the UE 102 may consider that only 'DL' or 'Unknown' OFDM symbols are valid for tracking the PDCCH associated with the CORESET. In this case, UE 102 may consider that each PDCCH candidate in the CORESET duration is associated with all of the "DL" type OFDM symbols, but is not associated with the "UL" or "Reserved" type symbols. In other words, UE 102 may receive a shorter CORESET duration compared to the CORESET duration that is configured by the higher layer.

[0098] If some of the OFDM symbols that are assigned to a given CORESET are of type "DL" and others are of type "unknown", UE 102 may consider all OFDM symbols of type "DL"/"unknown" to be valid for PDCCH tracking. The associated with this CORESET. In this case, UE 102 may consider that each PDCCH candidate in the CORESET duration is mapped to all of the DL/Unknown OFDM symbols, and one PDCCH candidate may be allowed to map on the DL and Unknown OFDM symbols. . In an alternative embodiment, in case some of the OFDM symbols that are assigned to a given CORESET are of type "DL" and others are of type "unknown", UE 102 may consider only OFDM symbols of type "DL" to be valid for PDCCH tracking. The associated with this CORESET. In this case, UE 102 may consider that each PDCCH candidate in the CORESET duration is only associated with DL OFDM symbols, not unknown symbols. In other words, UE 102 may not consider that one PDCCH candidate is mapped to OFDM symbols of type "DL" and "unknown". In another alternative embodiment, it is contemplated that a UE 102 action may be set for each CORESET. In an alternative and/or additional embodiment, in the event that symbols of type "DL" are split into more than one character set of type "unknown" within a given CORESET, UE 102 may assume that only the first (i.e., earliest) set OFDM symbols of type "DL" is valid for tracking the PDCCH associated with this CORESET.

[0099] In FIG. 12 is a block diagram illustrating one implementation of gNB 1260. gNB 1260 may include a higher level processor, a DL transmitter, a UL receiver, and antennas. The DL transmitter may include a PDCCH transmitter and a PDSCH transmitter. The UL receiver may include a PUCCH receiver and a PUSCH receiver. The high level processor can control the behavior of the physical layer (DL transmitter and UL receiver) and provide higher layer parameters to the physical layer. The higher level processor may receive transport blocks from the physical layer. The higher level processor may send/receive higher level messages, such as general and specific RRC messages and/or MAC messages, to or from the higher level UE. The higher level processor may also set and/or store higher level parameters conveyed via higher level messages. The higher level processor may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks. The UL receiver may receive the multiplexed uplink physical channels and uplink physical signals via the receive antennas and demultiplex them. The PUCCH receiver may provide a high level UCI processor. The PUSCH receiver may provide transport blocks received by the higher level processor.

[00100] In Fig. 13 is a block diagram illustrating one implementation of UE 1302. UE 1302 may include a higher level processor, a UL transmitter, a DL receiver, and antennas. The UL transmitter may include a PUCCH transmitter and a PUSCH transmitter. The DL receiver may include a PDCCH receiver and a PDSCH receiver. The high level processor can control the behavior of the physical layer (UL transmitter and DL receiver) and provide higher layer parameters to the physical layer. The higher level processor may receive transport blocks from the physical layer. The higher level processor may send/receive higher level messages, such as general and specific RRC messages and/or MAC messages, to or from the higher level UE. The higher level processor may also set and/or store higher level parameters conveyed via higher level messages. The higher level processor may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter UCI. The DL receiver may receive the multiplexed downlink physical channels and downlink physical signals via the receive antennas and demultiplex them. The PDCCH receiver may provide a high level UCI processor. The PDSCH receiver may provide the transport blocks received by the higher level processor.

[00101] For downlink data transmission, UE 1302 may attempt to blindly decode one or more PDCCH candidates (also referred to simply as control channels). This procedure is also referred to as PDCCH snooping. The PDCCH may carry the DCI format that the PDSCH (also referred to as the shared channel or data channel) schedules. gNB 160 may transmit a PDCCH and a corresponding PDSCH in a downlink slot. Upon detecting a PDCCH in a downlink slot, UE 1302 may receive the corresponding PDSCH in the downlink slot. Otherwise, UE 1302 may fail to receive the PDSCH in the downlink slot.

[00102] In Fig. 14 shows an example of a control resource unit and a reference signal structure. A control resource set may be defined in the frequency domain 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 control resource set may also be defined in the time domain as an OFDM symbol set. It may also be referred to simply as the duration of the control resource set. For example, the control resource set may include three OFDM symbols, from OFDM symbol #0 to OFDM symbol #2, in the time domain. UE 102 may monitor the PDCCH on one or more control resource sets. The PRB set may be configured with respect to each control resource set specified by the dedicated RRC signaling (eg, by reconfiguring the dedicated RRC). The duration of the control resource set can also be configured with respect to each control resource set with dedicated RRC signaling.

[00103] In the control resource unit and the reference signal structure shown in FIG. 14, control resource units are defined as a set of resource elements (REs). Each control resource block includes all REs (ie 12 REs) within one OFDM symbol and within one PRB (eg 12 consecutive subcarriers). REs to which reference signals (RS) are associated can be taken as such REs, but REs for RSs are not available for PDCCH transmission, and PDCCHs are not mapped to REs for RSs.

[00104] Multiple control resource units may be used to transmit a single PDCCH. In other words, one PDCCH can be mapped to REs that are included in a plurality of control resource units. On FIG. 14 shows an example that a UE 102 performing blind decoding of PDCCH candidates assumes that multiple control resource units located on the same frequency carry one PDCCH. However, the RS signals for PDCCH demodulation may be contained in all resource units with which the PDCCH is associated. UE 102 may not be allowed to assume that the RS signals contained in a given resource unit can be used to demodulate another resource unit. This can increase the diversity gain for PDCCH transmission because gNB 160 can apply different precoders for different resource units. In an alternative embodiment, UE 102 may be allowed to consider that the RS signals contained in a given resource unit can be used to demodulate another resource unit in the same PRB. This can improve the accuracy of the channel estimate because gNB 160 can use the same precoders for more RSs within the same PRB.

[00105] In FIG. 15 shows an example of multiplexing a control channel and a shared channel. The start(s) and/or end(s) position(s) of the PDSCH can be specified using PDCCH scheduling. More specifically, the DCI format in which the PDSCH is scheduled may include information field(s) to indicate the start(s) and/or end(s) position(s) of the scheduled PDSCH.

[00106] UE 102 may include a high level processor that is configured to receive a special RRC message. The specific RRC message may contain information indicating the configuration of the control resource set. UE 102 may also comprise a PDCCH receiving scheme that is configured to track the PDCCH based on the configuration of the control resource set. The PDCCH may be in the DCI format that the PDSCH schedules. UE 102 may also comprise a PDSCH receiving scheme configured to receive a PDSCH after detecting a corresponding PDCCH.

[00107] gNB 160 may include a high level processor that is configured to send a special RRC message. The specific RRC message may contain information indicating the configuration of the control resource set. gNB 160 may also include a PDCCH transmission scheme that is configured to transmit the PDCCH based on the control resource set configuration. The PDCCH may be in the DCI format that the PDSCH schedules. gNB 160 may also include a PDSCH transmission scheme that is configured to transmit a PDSCH in the event that a corresponding PDCCH is transmitted.

[00108] UE 102 may track PDCCH candidates in the control resource set. The set of PDCCH candidates 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 an OFDM symbol in the time domain.

[00109] For each serving cell, higher layer signaling, such as generic RRC messages or UE specific RRC messages, may configure the UE 102 with one or more PRB sets for PDCCH tracking. For each serving cell, higher layer signaling, such as generic RRC messages or UE specific RRC messages, may also configure the UE 102 with the control resource set duration for PDCCH tracking.

[00110] Each set of control resources may contain a set of control channel elements (CCE). Each CCE may be associated with a Resource Element Group (REG) set, which includes a plurality of REs. In the control resource set, gNB 160 may transmit a group-wide PDCCH. If UE 102 is configured to monitor a group-wide PDCCH via higher layer signaling, UE 102 may monitor a group-wide PDCCH. The group-wide PDCCH may be a PDCCH with a CRC scrambled with a specific RNTI, which may be fixed or configured independently of the C-RNTI. In an alternative embodiment, the group-wide PDCCH may be a DCI-formatted PDCCH whose RNTI field value is set to a specific RNTI.

[00111] In a control resource set, a UE-specific PDCCH may be transmitted by gNB 160. UE 102 may monitor the PDCCH. The UE-specific PDCCH may be a PDCCH with CRC scrambled with the C-RNTI of the UE 102. In an alternative embodiment, the UE-specific PDCCH may be a DCI-formatted PDCCH whose RNTI field value is set to the C-RNTI of the UE 102 PDCCH snooping may mean trying to decode each of the PDCCH candidates in the set according to the DCI snooping formats. UE 102 may keep track of the total search space within the control resource set. UE 102 may also keep track of the UE-specific search space within the boundaries of the control resource set. A UE-specific PDCCH can be tracked in both common and UE-specific search spaces, while a group-wide PDCCH can only be tracked in a common search space. The UE-specific PDCCH may schedule the PDSCH. UE 102 may not be required to monitor a group-wide PDCCH in a slot in which UE 102 will have a scheduled uplink transmission using at least the first OFDM symbol of the slot.

[00112] After detecting a UE-specific PDCCH, UE 102 may receive the corresponding PDSCH. The DCI format of the UE-specific PDCCH may include one or more fields of information, for example, a field for specifying a resource block assignment for the PDSCH, a field for specifying a start position (index of the first OFDM symbol that the PDSCH carries) of the PDSCH, a field for specifying a modulation order, and the transport block size for the PDSCH, and the like. The PDCCH group-wide, UE-specific PDCCH, and PDSCH can be mapped to different RE sets so that they do not conflict with each other.

[00113] For each serving cell, the higher layer signaling configures the UE with P sets of control resources. For a control resource set p, 0 <= p < P, the configuration includes the index of the first symbol provided by the higher level parameter CORESET-start-symb; the number of consecutive characters provided by the CORESET-time-duration higher-level option; the set of resource blocks provided by the CORESET-freq-dom higher-level option; CCE to REG mapping provided by the higher level parameter CORESET-trans-type (also called CORESET-CCE-to-REG-mapping); REG bundle size in case of CCE to REG interleaved mapping, provided by the CORESET-REG-bundle-size higher-level parameter; and quasi-co-location of the antenna port provided by the higher layer parameter CORESET-TCI-StateRefId. If the UE is not configured with the CORESET-TCI-StateRefId higher layer parameter, the UE may assume that the DMRS antenna port associated with PDCCH reception in the USS and the DMRS antenna port associated with PBCH reception are co-located with respect to delay spread, Doppler distribution, Doppler shift, average delay time, and spatial reception parameters.

[00114] For each serving cell and for each DCI format with CRC scrambled with C-RNTI, SPS-RNTI and/or RNTI without provision for which the UE is configured to monitor PDCCH, the UE is configured in association with control resource sets. Relationships may include relationships with a set of control resource sets over a higher-level parameter DCI-to-CORESET-map. For each control resource set in the control resource set set, the relationships may include the number of PDCCH candidates per CCE aggregation layer L by the higher layer parameter CORESET-candidates-DCI; the PDCCH tracking slot periodicity k _p on the CORESET-monitor-period-DCI higher layer parameter, the PDCCH tracking slot offset o _p where 0 <= o _p < k _p on the CORESET-monitor-offset-DCI higher layer parameter, and a slot-bound PDCCH tracking scheme indicating the first slot-bound control resource set symbol(s) for monitoring the PDCCH by the higher-level parameter CORESET-monitor-DCI-symbolPattern. If UE 102 is configured with the CORESET-monitor-DCI-symbolPattern higher-level parameter, UE 102 may assume that non-slot-based scheduling is configured in addition to slot-based scheduling. If UE 102 is not configured with the CORESET-monitor-DCI-symbolPattern higher-level parameter, UE 102 may assume that non-slot-based scheduling is not configured, only slot-based scheduling is available.

[00115] In FIG. 16 shows PDCCH tracking events for slot-based scheduling. A search space set may be identified for a combination of a control resource set, a DCI format (or a DCI format group including a DCI format with the same DCI payload size). In the example shown in FIG. 16, there are two sets of search spaces, set #0 and #1 of search spaces. Both sets #0 and #1 of search spaces are associated with the same CORESET. CORESET configuration such as CORESET-start-symb, CORESET-time-duration, CORESET-freq-dom, CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-StateRefld applies to both bundle #0 and No. 1 search spaces. For example, a CORESET-time-duration value set to 3 characters is applied to each of them. Search space set #0 may be associated with a specific DCI format (eg, DCI format 1, DCI fallback format), and search space set #1 may be associated with another specific DCI format (eg, DCI format 2, normal DCI format). The higher level parameter CORESET-monitor-period-DCI is set to 2 slots for search space set #0, while the higher level parameter CORESET-monitor-period-DCI is set to 1 slot for search space set #1. Thus, DCI format 1 can potentially be transmitted and/or monitored in every 2 slots, and DCI format 2 can potentially be transmitted and/or monitored in every slot.

[00116] In Fig. 17 shows PDCCH tracking events for non-slot-based scheduling. In the example shown in FIG. 16, there are two sets of search spaces, set #2 and #3 of search spaces. Both sets #2 and #3 of search spaces are associated with the same CORESET. This CORESET may or may not be the same as in FIG. 16. The higher level parameters CORESET-monitor-period-DCI for both sets #2 and #3 of search spaces are set to 1 slot.

[00117] In addition, the higher level parameters CORESET-monitor-DCI-symbolPattern are individually configured for sets #2 and #3 of search spaces. The higher level parameter CORESET-monitor-DCI-symbolPattern may indicate, using a bitmap, the OFDM symbol(s) over which the PDCCH is monitored. More specifically, the higher-level parameter CORESET-monitor-DCI- ^{symbolPattern} per search space set may include 14 bits ^, bit 1 to bit 14, which correspond to OFDM symbols #0 to #13, respectively. Each bit indicates whether the PDCCH is being monitored on the corresponding OFDM symbol (eg, 0 indicates no PDCCH tracking and 1 indicates PDCCH tracking, or vice versa). In this example, the higher-level parameter CORESET-monitor-DCI-symbolPattern for search space set #2 specifies OFDM symbols #0 and #7 for PDCCH tracking, and the CORESET-monitor-DCT symbolPattern parameter for search space set #3 specifies OFDM symbols # 0, #2, #4, #6, #8, #10, #12 for PDCCH tracking. It should be noted that the specified PDCCH snoops refer to the slot indicated by CORESET-monitor-period-DCI and CORESET-monitor-offset-DCI.

[00118] The control channel element may include 6 resource element groups (REGs), where one resource element group is equal to one resource block within the duration of one OFDM symbol. The groups of resource elements in the control resource set may be numbered in ascending order in a first time manner, starting from 0 for the first OFDM symbol and the lowest numbered resource block in the control resource set. The UE may be configured with multiple resource sets. Each control resource set can only be associated with one CCE-to-REG mapping. The mapping of CCE to REG for a control resource set may be interleaved or non-interleaved, configured with the CORESET-CCE-REG-mapping-type higher level parameter. The size of the REG bundle is configured with the higher-level parameter CORESET-REG-bundle-size. For a non-interleaved CCE to REG mapping, the REG concatenation size is 6. For an interleaved CCE to REG mapping, the REG concatenation size is 2 or 6 for CORESET, with the CORESET-time-duration parameter set to 1, and the REG concatenation size is N ^CORESET _symb or 6 for CORESET, with the CORESET-time-duration N ^CORESET _{symb parameter} set to greater than 1. The UE may assume that in case the higher-level CORESET-precoder-granularity parameter is CORESET-REG-bundle-size, REG is used within the bundle boundaries the same precoding in the frequency domain; and if the higher layer parameter CORESET-precoder-granularity is equal to the number of contiguous RBs in the frequency domain within the CORESET boundaries, the same frequency domain precoding is used in all contiguous RBs within the CORESET boundaries.

[00119] The configuration part of individual CORESETs may not apply to the set(s) of search spaces, in this case the higher level parameter CORESET-monitor-DCTsymbolPattern (eg, character bitmap) is configured. For example, even if CORESET-time-duration is set to more than 1 OFDM symbol, UE 102 may assume that each PDCCH snooping event spans 1 OFDM symbol for the search space set(s) that is configured with using CORESET-monitor-DCTsymbolPattern. The CORESET-time-duration parameter set to more than 1 OFDM symbol can be applied to all and only search space sets that have not been configured with CORESET-monitor-DCTsymbolPattern. In this case, for the interleaved mapping of CCE to REG, the REG merging size may be determined depending on the CORESET-time-duration. In an alternative embodiment, for an interleaved mapping of CCE to REG, the REG pool size can be determined by taking N ^CORESET _symb =1.

[00120] In an alternative embodiment, the CORESET duration is always independently configured, and a PDCCH snooping event configured with a character raster may indicate the start of a snooping event if the CORESET duration is more than 1 OFDM symbol. For example, if CORESET-time-duration is set to 2 OFDM symbols and the third bit of CORESET-monitor-DCI-symbolPattern is set to 1, UE 102 may need to monitor PDCCH candidates that correspond to the third and fourth OFDM symbols. In other words, if each bit of the CORESET-monitor-DCI-symbolPattern is set to 1, this may indicate a start symbol from one or more consecutive OFDM symbols to which the PDCCH candidate(s) maps.

[00121] In this alternative embodiment, if the CORESET duration is more than 1 OFDM symbol and at least if any of two adjacent CORESET-monitor-DCI-symbolPattern bits is set to 1, PDCCH tracking events starting from the OFDM symbols specified these two bits partially overlap. There are several ways to control said overlay. The first approach is that UE 102 should not be configured with CORESET-monitor-DCI-symbolPattern overlaying adjacent PDCCH snooping events for the same set of search spaces. The second approach is to allow PDCCH tracking events to overlap so that UE 102 does not have to track full/partial matching of PDCCH candidates and RE or REG for those candidates that have already been used by another discovered PDCCH in another PDCCH tracking event in CORESET. A third approach is to allow overlapping PDCCH tracking events, then UE 102 will not have to track PDCCH candidates if the higher layer parameter CORESET-precoder-granularity is equal to the number of contiguous RBs in the frequency domain within the CORESET boundaries and if another PDCCH has been detected in another PDCCH tracking event (ie, PDCCH tracking event overlay) in CORESET. In a further and/or alternative embodiment, if the higher layer parameter CORESET-precoder-granularity is equal to the number of contiguous RBs in the frequency domain within the CORESET boundaries, and if any PDCCH was detected in any PDCCH snooping event in the CORESET, The UE 102 may assume that the DMRS associated with the detected PDCCH is present in all REGs in the adjacent RB set in the CORESET where and when the detected PDCCH is associated, and the UE 102 should not monitor the PDCCH channel(s) in another PDCCH snooping event. with DMRS overlay.

[00122] Each control resource set contains a set of CCEs numbered from 0 to N _CCE,p,kp - 1, where NCCE, p _p,kp is the number of CCEs in control resource set p in tracking period k _p . The PDCCH candidate sets that the UE monitors are defined in terms of UE-specific PDCCH search spaces. The UE-specific PDCCH search space S ^(L) _kp at the CCE aggregation layer L is determined by the PDCCH candidate set for the CCE aggregation layer L. L can be one of the values 1, 2, 4, and 8.

[00123] For each serving cell, the UE 102 may need to set the slot configuration for each slot in the total number of slots equal to the slot configuration for each slot in the total number of slots, as indicated by the higher level parameter Slot-assignmentSIB 1, which can be a UE-wide parameter (eg, a cell-specific parameter). If the UE is further provided with a UE-specific Slot-assignment higher-level parameter for the slot format for each slot in the total number of slots, the Slot-assignment parameter overrides only soft symbols (also called unknown symbols) for each slot in the total number of slots, as this is provided by the Slot-assignmentSIB 1 parameter.

[00124] In each serving cell, for the slot symbol set that is designated as flexible (also referred to as unknown) with the Slot-assignmentSIB 1 higher layer parameter and, if present, with the Slot-assignment higher layer parameter, the UE 102 may follow the following assumptions. UE 102 may receive SS/PBCH, PDCCH, PDSCH, or CSI-RS in the slot symbol set if UE 102 receives an appropriate indication using the DCI format with CRC scrambled by C-RNTI or through configuration given by higher layers. UE 102 may transmit PUSCH, PUCCH, PRACH, or SRS in the slot symbol set if the UE is instructed to do so by a DCI format with a CRC scrambled by C-RNTI or by configuration given by higher layers. UE 102 configured to receive PDCCH or CSI-RS trigger type 0 (i.e., higher layer configured CSI-RS, also known as semi-statically configured periodic CSI-RS) in slot symbol set may need to receive PDCCH or CSI-RS of trigger type 0 if the UE does not detect a DCI format with CRC scrambled by C-RNTI indicating to UE 102 to transmit PUSCH, PUCCH, PRACH, or SRS in the slot symbol set; otherwise, UE 102 may not receive the PDCCH or CSI-RS of origin type 0 in the slot symbol set and may need to transmit PUSCH, PUCCH, PRACH, or SRS in the slot symbol set. A UE 102 configured to send a Type 0 trigger SRS (i.e., a higher layer configured SRS, also known as a semi-statically configured periodic SRS) or a higher layer configured PUSCH in the slot symbol set may need to receive the SRS trigger type 0 or PUSCH configured by higher layers if the UE does not detect a DCI format with CRC scrambled by C-RNTI indicating to the UE to transmit PDSCH or CSI-RS in the slot symbol set; otherwise, the UE cannot receive a Type 0 Trigger SRS or a PUSCH configured by higher layers in the slot symbol set.

[00125] For unpaired spectrum operation, direction (ie, DL/UL/flexible) may be applied to all portions of the DL/UL bandwidth of the serving cell for unpaired carrier operation. For unpaired spectrum operation, if UE 102 receives a configuration from higher layers that indicates the presence of an SS/PBCH in a slot symbol set in a serving cell BWP, UE 102 may consider the symbol set to be a downlink in any BWP of the same serving cell. DL processing is performed for these downlink symbols. For paired spectrum operation, if UE 102 receives a configuration from higher layers that indicates the presence of an SS/PBCH in a slot symbol set in a serving cell BWP, UE 102 may assume that this symbol set represents a downlink in any BWP DL the same serving cell. Similarly, for unpaired spectrum operation, if UE 102 receives a configuration from higher layers that indicates the presence of some common PDCCH search space (eg, CSS type 0-PDCCH, CSS type 1-PDCCH, or CSS type 2-PDCCH) in the set slot characters in the BWP of the serving cell, the UE 102 may consider that the character set is a downlink in any BWP of the same serving cell. For pairwise spectrum operation, if UE 102 receives a configuration from higher layers that indicates the presence of some common PDCCH search space in the slot symbol set in the serving cell BWP, UE 102 may consider the symbol set to be a downlink in any BWP DL of the same serving cell.

[00126] When operating in an unpaired spectrum, a PDCCH is detected on a slot symbol set, all REs on the symbol set in any serving cell BWP can be recognized as DL. When operating in unpaired spectrum, PDSCH and/or aperiodic CSI-RS transmission is scheduled on a slot symbol set with a UE-specific DCI, all REs on the symbol set in any serving cell BWP may be recognized as DL. If a PDCCH is detected on a slot symbol set during paired spectrum operation, all REs on the symbol set in any BWP DL of the serving cell may be recognized as a DL. If, in paired spectrum operation, PDSCH and/or aperiodic CSI-RS transmission is scheduled on a slot symbol set with a UE-specific DCI, all REs on the symbol set in any serving cell DL BWP may be recognized as DL.

[00127] For unpaired spectrum operation, if UE 102 receives a configuration from higher layers that indicates the presence of PRACH resources in a slot symbol set in a serving cell BWP, UE 102 may consider the symbol set to be an uplink in any BWP the same serving cell. For paired spectrum operation, if UE 102 receives a configuration from higher layers that indicates the presence of PRACH resources in a slot symbol set in a serving cell BWP, UE 102 may consider the symbol set to be an uplink in any UL BWP of the same serving cell.

[00128] When operating in an unpaired spectrum, PUSCH and/or aperiodic SRS transmission is scheduled on a slot symbol set with UE-specific DCI, all REs on the symbol set in any serving cell BWP can be recognized as UL. If, in paired spectrum operation, PUSCH and/or aperiodic SRS transmission is scheduled on the slot symbol set with UE-specific DCI, all REs on the symbol set in any serving cell UL BWP may be recognized as UL. If a PUCCH is transmitted with a HARQ-ACK on the slot symbol set in accordance with the associated PDSCH reception while operating in an unpaired spectrum, all REs on the symbol set in any serving cell BWP can be recognized as UL. If a PUCCH transmission with a HARQ-ACK on the slot symbol set according to the associated PDSCH reception is performed in paired spectrum operation, all REs on the symbol set in any serving cell UL BWP can be recognized as UL.

[00129] In an alternative embodiment, regardless of the type of spectrum operation, the direction (ie, DL/UL/flexible) may be applied to one portion of the DL/UL bandwidth of the serving cell for unpaired carrier operation. If UE 102 receives a configuration from higher layers that indicates the presence of an SS/PBCH in a slot character set in a serving cell BWP, UE 102 may consider the character set to be a downlink in that BWP, but this may not affect the other bwp. If UE 102 receives a configuration from higher layers that indicates the presence of PRACH resources in a slot character set in a serving cell BWP, UE 102 may consider the character set to be an uplink in that BWP, but this may not affect the other BWP. .

[00130] For a slot symbol set that is designated as uplink by the Slot-assignmentSIB1 higher layer parameter, or if provided by the Slot-assignment higher layer parameter, it is possible that the UE 102 need not be indicated by the DCI format with CRC scrambled by C-RNTI or configured with higher layers to receive PDCCH, PDSCH or CSI-RS in slot symbol set. For a slot character set that is designated as downlink by the Slot-assignmentSIB1 higher layer parameter, or if provided by the Slot-assignment higher layer parameter, it is possible that the UE 102 need not be indicated by the DCI format with CRC scrambled C-RNTI, or configured with higher layers to transmit PUSCH, PUCCH, PRACH, or SRS in the slot's character set.

[00131] Semi-static transmission (eg, PDCCH, periodic/semi-persistent CSI-RS, SPS PDSCH) is performed on a generic/semi-static SFI of the flexible type. At the same time, semi-static reception (eg, SRS trigger type 0, PUCCH configured with higher layers, PUSCH without UL grant) is performed on a generic/semi-static SFI of flexible type. When working in an unpaired spectrum, a conflict may occur between them. There are several options to avoid conflict.

[00132] The first option is to not configure the UE 102 to semi-static transmission and semi-static reception on the same symbol. When using this option with UE 102, no special procedures need to be performed. It may be necessary to avoid invalid combinations of values between semi-static transmit and semi-static receive configurations in the network. In other words, some restrictions need to be applied to the network configuration. Although this is not always a problem, in some cases the restrictions can be excessive. For example, if PUSCH is configured without provisioning with a 2 ms interval, the periodic CSI-RS with a time of 5 ms will not be available.

[00133] The first option is to not configure UE 102 for semi-static transmission and semi-static reception on soft/generic/semi-static SFI symbols. If the UE 102 is configured with semi-static transmission and semi-static reception on soft/semi-static DL SFI symbols, the UE 102 may perform semi-static reception and reset the semi-static transmission. If the UE 102 is configured with semi-static transmission and semi-static reception on generic/semi-static UE SFI soft type symbols, the UE 102 may reset the semi-static reception and perform the semi-static transmission. This option may not require such restriction in semi-static transmit and semi-static receive configurations. On the other hand, the network may not be allowed to configure semi-static flexible resource sets where semi-static transmit and semi-static receive may conflict. The network may need to configure DL or UL for resources where semi-static transmit and semi-static receive may conflict.

[00134] A third option is that UE 102 performs either semi-static transmission or semi-static reception based on a prioritization rule. For example, a semi-static receive takes precedence over a semi-static send. In other words, if the UE 102 is configured with semi-static reception on DL (eg, PDCCH, periodic/semi-persistent CSI-RS, SPS PDSCH) and semi-static transmission on UL (eg, SRS trigger type 0, PUCCH configured by higher layers, PUSCH without granting UL) on the same symbol(s) and if the symbol(s) are specified with type "flexible" via the higher-level parameter Slot-assignmentSIB 1 or if provided via the higher-level parameter Slot- assignment, UE 102 may have to drop UL semi-static transmission and perform DL semi-static receive. In another example, semi-static transmission takes precedence over semi-static reception. In other words, if the UE 102 is configured with DL semi-static reception and UL semi-static transmission on the same symbol(s) and if the symbol(s) are specified with type "flexible" via the higher layer parameter Slot -assignmentSIB 1 or if provided by a higher Slot-assignment parameter, it is possible that the UE 102 will have to perform UL semi-static transmission and reset DL semi-static reception. In another example, if the UE 102 is configured with a type 0 trigger PDCCH and SRS snooping event on one(s) and that (same) symbol(s) and if that (these) symbol(s) is specified(s) ) as "flexible(s)" via the Slot-assignmentSIB 1 higher layer parameter, or if provided via the Slot-assignment higher layer parameter, it is possible that the UE 102 will have to reset the SRS origination signal type 0 and perform PDCCH snooping, or vice versa. In another example, if UE 102 is configured with periodic/semi-persistent CSI-RS and PUSCH without providing UL on one(s) and that (same) symbol(s) and if this (these) symbol(s) is specified( -s) as "flexible(s)" via the Slot-assignmentSIB 1 higher layer parameter, or if provided via the Slot-assignment higher layer parameter, it is possible that the UE 102 may have to reset the periodic/semi-persistent CSI-RS reception and perform PUSCH transmission without UL grant, or vice versa. In yet another example, relative priorities among these semi-static transmissions and receptions can be defined, e.g., PUSCH without providing UL > PUCCH configured by higher layers > SRS, trigger type 0 > PDCCH > periodic/semi-persistent CSI-RS > SPS PDSCH.

[00135] If UE 102 is not configured by higher layers with the SFI-applicable-cells parameter (i.e., if UE 102 is configured with DCI STI format snooping, or if UE 102 is configured with any parameter related to DCI STI format snooping ), UE 102 may follow the above procedure to determine the slot format for each slot. If UE 102 is configured with higher layers with SFI-applicable-cells, and for the serving cell that UE 102 is not configured with SFI-applicable-cells, UE 102 may follow the above procedure to determine the slot format for each slot. If the UE 102 is configured to monitor the DCI format with SFI-RNTI scrambled CRC for the serving cell, and if the UE 102 does not detect the DCI format with SFI-RNTI scrambled CRC indicating the slot format for that slot, the UE 102 may also follow the described above procedure to determine the slot format for a given slot. In an alternative embodiment, if the UE 102 is configured to monitor the DCI format with SFI-RNTI scrambled CRC for the serving cell, and if the UE 102 does not detect the DCI format with SFI-RNTI scrambled CRC, which indicates the slot format for that slot , the UE 102 may also follow the above procedure to determine the slot format for a given slot, except for receiving PDCCH, receiving CSI-RS trigger type 0, receiving SSC PDSCH, transmitting SRS trigger type 0, transmitting PUCCH, transmitting SPS/PUSCH without provision or any combination thereof.

[00136] If the UE 102 is configured with the higher layers with the SFI-applicable-cells parameter, the UE 102 is configured with the SFI-RNTI provided by the higher layer SFI-RNTI parameter as well as the serving cell set set by the higher layer parameter SFI- monitoring-cells to monitor a PDCCH carrying a DCI format (eg, a specific DCI format for SFI, also referred to as DCI STI format hereinafter), with a CRC scrambled by the SFI-RNTI. For each serving cell in the serving cell set, the UE 102 configures parameters including control resource sets via an SFI-to-CORESET-map higher layer parameter for tracking a PDCCH transmitting the DCI SFI format; the payload size of the DCI SFI format via the higher layer parameter SFI-DCI-payload-length; a set of cells for which the DCI SFI format is applicable, through the higher layer parameter SFI-applicable-cells; the location of the field in DCI SFI format for the corresponding cell for each cell of the set of cells through the higher parameter SFI-cell-to-SFI; the number of PDCCH candidates per CCE aggregation layer for the DCI SFI format by the higher layer parameter SFI-Num-PDCCH-cand; monitoring periodicity for PDCCH with DCI SFI format via higher layer parameter SFI-monitoring-periodicity.

[00137] If UE 102 detects a DCI format with CRC scrambled by SFI-RNTI in an mT _SFI slot, the slot configuration for slots {mT _SFI , mT _SFI+ 1, ... (m+1)T _SFI - 1} is given by the slot configuration, indicated by the DCI format with SFI-RNTI scrambled CRC, where T _SFI is the value of the SFI-monitoring-periodicity parameter configured for the UE 102 by higher layers for the DCI format with SFI-RNTI scrambled CRC.

[00138] In an alternative and/or additional embodiment, if the UE 102 detects a DCI format with CRC scrambled by SFI-RNTI (also referred to as SFI-PDCCH) in an mT _SFI slot and if the DCI format indicates SFI values for nT _SFI slots , the configuration for slots {mT _SFI , mT _SFI+ 1,... (m+n)T _SFI - 1} can be given by the slot configuration specified in DCI format with CRC scrambled by SFI-RNTI. If n is greater than 1, UE 102 may not need to monitor DCI PDCCH with CRC scrambled by SFI-RNTI in slot(s) {(m+1)T _SFI , (m+2)T _SFI , ... ( m+n - 1)T _SFI }. In an alternative embodiment, if n is greater than 1, UE 102 may continue to monitor the PDCCH using the DCI format with CRC scrambled by the SFI-RNTI in slot(s) {(m+1)T _SFI , (m+2)T _SFI , ... (m+n - 1)T _SFI }. In this case, in these slots, the UE 102 may detect a PDCCH SFI indicating the SFI value of the slot for which the SFI value was indicated by the previous SFI-PDCCH. UE 102 may assume that the last SFI value always indicates the same format as the previous value, or UE 102 may use the SFI value(s) indicated by the last PDCCH SFI.

[00139] For each serving cell for which UE 102 is configured with higher layers using the SFI-applicable-cells parameter, UE 102 may make some or all of the following assumptions (1)-(4).

[00140] (1) For slot character set, it is not assumed that UE 102 can detect DCI format with CRC scrambled by SFI-RNTI indicating slot character set as uplink and detect DCI format with CRC scrambled by C-RNTI indicating UE 102 receive PDSCH or CSI-RS in slot symbol set.

[00141] (2) For slot character set, UE 102 is not expected to detect DCI format with CRC scrambled by SFI-RNTI indicating character set in slot as downlink, and detect DCI format with CRC scrambled by C-RNTI, indicating to UE 102 to send PUSCH, PUCCH, PRACH, or SRS in the slot character set.

[00142] (3) For a slot symbol set that is designated as downlink/uplink by the Slot-assignmentSIB 1 higher layer parameter or, if present, by the Slot-assignment higher layer parameter, it is not assumed that the UE 102 determines the format DCI with CRC scrambled by SFI-RNTI indicating the character set in the slot as uplink/downlink, respectively, or as a flexible type.

[00143] (4) For a slot symbol set that is designated as flexible by the Slot-assignmentSIB 1 higher-level parameter and, if present, by the Slot-assignment higher-level parameter, UE 102 may follow the procedures below in whole or in part: if UE 102 detects a DCI format with CRC scrambled by SFI-RNTI indicating slot character set as flexible, and UE 102 detects DCI format with CRC scrambled by C-RNTI indicating UE to receive PDSCH or CSI-RS in slot character set, UE 102 may follow the DCI format indication with CRC scrambled by C-RNTI; if UE 102 detects a DCI format with CRC scrambled by SFI-RNTI indicating slot character set as flexible and UE 102 detects DCI format with CRC scrambled by C-RNTI indicating UE 102 to send PUSCH, PUCCH, PRACH or SRS in slot character set , UE 102 may follow the DCI format indication with CRC scrambled by C-RNTI; if the UE 102 detects a DCI format with a CRC scrambled by the SFI-RNTI indicating the slot's character set as flexible, and the slot's character set is also specified as flexible through the Slot-assignmentSIB 1 higher level parameter or, if present, through the Slot- higher level parameter assignment, UE 102 may consider the character set as reserved; if UE 102 is configured by higher layers to receive a PDCCH, or CSI-RS trigger type 0, or SPS PDSCH in the slot symbol set, UE 102 may be forced to receive the PDCCH, or CSI-RS trigger type 0, or SPS PDSCH in the slot symbol set. slot symbols only if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI indicating the slot symbol set as the downlink; if the UE 102 is configured by higher layers to transmit a type 0 trigger SRS or PUCCH or SPS/PUSCH without granting a slot in the character set, the UE 102 may be forced to transmit a type 0 trigger SRS or PUCCH or SPS/PUSCH without granting in the slot character set only if the UE 102 detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot character set as uplink.

[00144] The fourth procedure of (4) may be replaced by a procedure in which, in case the UE 102 is configured by higher layers to receive a PDCCH, CSI-RS trigger type 0, SPS PDSCH, or some of them in the slot symbol set, the UE 102 may be forced to receive a PDCCH, CSI-RS Type 0 origin, SPS PDSCH, or some of them in the slot character set only if the UE 102 detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot character set as the downlink , or if UE 102 detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PDSCH to at least the slot character set. With this option, even if the UE 102 detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot's character set as flexible, the UE 102 may be forced to receive a PDCCH, CSI-RS Type 0 Trigger, SPS PDSCH, or some of them. in the slot character set if the UE detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PDSCH to the slot character set. In other words, if UE 102 detects a DCI format with a CRC scrambled by SFI-RNTI that indicates the slot's character set as flexible or as uplink, UE 102 will not be able to receive the PDCCH, CSI-RS Type 0 Trigger, SPS PDSCH, or some of the them in the slot character set until the UE detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PDSCH to the slot character set. Moreover, if UE 102 detects a DCI format with CRC scrambled by SFI-RNTI that indicates a slot character set subset as a downlink, and if UE 102 detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI , which plans to map the PDSCH to at least the rest of the set, UE 102 may be forced to receive the PDCCH, CSI-RS Type 0 trigger, SPS PDSCH, or some of them in the symbol set.

[00145] Similarly, the fifth procedure of (4) may be replaced by a procedure in which, in case the UE 102 is configured by higher layers to transmit SRS trigger type 0, PUCCH, SPS/PUSCH without granting, or some of them in the slot character set , the UE 102 may be forced to transmit the Type 0 Trigger SRS, PUCCH, SPS/PUSCH without grant, or some of them in the slot character set only if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot character set as downstream link, or if the UE 102 detects a DCI format with a CRC scrambled by a C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PUSCH to the slot character set. With this option, even if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot's character set as flexible, the UE 102 may be forced to send a Trigger Type 0 SRS, PUCCH, SPS/PUSCH without provision, or some of them. in the slot character set if UE 102 detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PUSCH to at least the slot character set. In other words, if the UE 102 detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot's character set as flexible or as a downlink, the UE 102 will not be able to receive the Type 0 Trigger SRS, PUCCH, SPS/PUSCH without providing or some of them in the slot character set until the UE detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PUSCH to the slot character set. Moreover, if UE 102 detects a DCI format with CRC scrambled by SFI-RNTI that indicates a slot character set subset as uplink, and if UE 102 detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PUSCH to at least the rest of the set, the UE 102 may be forced to receive the Type 0 Trigger SRS, PUCCH, SPS/PUSCH without granting, or some of them in the character set.

[00146] For each serving cell for which the UE 102 is configured by higher layers with the SFI-applicable-cells parameter, if the UE 102 does not detect a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot format for that slot, the UE 102 may assume that the DCI format with CRC scrambled by the SFI-RNTI specifies for a given slot the same slot format (also referred to as the slot assignment) as the format configured by the Slot-assignmentSIB1 higher-level parameter or, if present, the higher-level parameter slot assignment. PDCCH snooping may not be performed on soft symbols in a slot until the CRC-scrambled DCI format scrambled by C-RNTI/TC-RNTI/SPS-RNTI schedules to map PUSCH to these soft symbols, since UE 102 cannot perform PDCCH snooping on soft symbols. , which are indicated by the DCI format with CRC scrambled by the SFI-RNTI.

[00147] The fourth procedure of (4) may be replaced by a procedure in which the UE 102 is configured by higher layers to receive a PDCCH, CSI-RS trigger type 0, SPS PDSCH, or some of them in the slot symbol set, UE 102 may be forced to receive a PDCCH, CSI-RS of Type 0 Trigger, SPS PDSCH, or some of them in the slot character set only if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot character set as downlink, or if the UE does not will detect any DCI format with a CRC scrambled by the SFI-RNTI indicating the slot format of the slot in question.

[00148] Similarly, the fifth procedure of (4) can be replaced by a procedure in which, in case the UE 102 is configured by higher layers to transmit SRS trigger type 0, PUCCH, SPS/PUSCH without providing or some of them in the character set slot, the UE 102 may be forced to transmit the Type 0 Trigger SRS, PUCCH, SPS/PUSCH without grant, or some of them in the slot character set, only if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI that specifies the slot character set as downlink, or if the UE does not detect any DCI format with a CRC scrambled by the SFI-RNTI indicating the slot format of the slot in question.

[00149] The fourth procedure of (4) may be replaced by a procedure in which, in case the UE 102 is configured by higher layers to receive a PDCCH, CSI-RS trigger type 0, SPS PDSCH, or some of them in the slot symbol set, the UE 102 may be forced to receive a PDCCH, CSI-RS Type 0 Trigger, SPS PDSCH, or some of them in the slot character set only if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI that indicates the slot character set as downlink, or if the UE detects a DCI format with a CRC scrambled by a C-RNTI/TC-RNTI/SPS-RNTI that plans to map the PDSCH to the slot character set.

[00150] Similarly, the fifth procedure of (4) can be replaced by a procedure in which, in case the UE 102 is configured by higher layers to transmit SRS trigger type 0, PUCCH, SPS/PUSCH without providing or some of them in the character set slot, the UE 102 may be forced to send a Type 0 Trigger SRS, PUCCH, SPS/PUSCH without grant, or some of them in the slot character set only if the UE detects a DCI format with a CRC scrambled by the SFI-RNTI that specifies the slot character set as downlink, or if the UE does not detect any DCI format with CRC scrambled by SFI-RNTI indicating the slot format of the slot in question, or if the UE 102 detects a DCI format with CRC scrambled by C-RNTI/TC-RNTI/SPS-RNTI , which plans to map PUSCH to the slot's character set.

[00151] If a dynamic SFI of the "flexible" type has been received (not overwritten) for at least one symbol configured for the PDCCH, it is not expected that the UE 102 will monitor the PDCCH. Similarly, UE 102 may completely discard (ie, not perform) semi-static reception (eg, periodic/semi-persistent CSI-RS, SPS PDSCH) that covers DL and soft-type dynamic SFI symbols. Moreover, UE 102 may completely discard (i.e., not perform) semi-static transmission (e.g., Trigger Type 0 SRS, PUCCH configured by higher layers, PUSCH without UL grant) that covers UL and dynamic SFI symbols of "flexible" type. ". In an alternative embodiment, in the event that UE 102 is configured for semi-static reception (eg, periodic/semi-persistent CSI-RS, SPS PDSCH) that spans DL and soft type dynamic SFI symbols, UE 102 may perform semi-static reception on symbol( -ax) DL. If UE 102 is configured for semi-static transmission (eg, periodic/semi-persistent CSI-RS, SPS PDSCH) that spans UL and soft-type dynamic SFI symbols, UE 102 may only perform semi-static transmission on the UL symbol(s). In these cases, UE 102 may assume that the part on the dynamic SFI symbol(s) of type "flexible" has been "punctured".

[00152] A description is provided of UE 102. UE 102 may include a high-level processor configured to receive a generic and/or specific Radio Resource Control (RRC) configuration message and one or more specific RRC configuration messages. The general RRC message may include first information for indicating a slot format. The one or more specific RRC configuration messages include second information for configuring the semi-static downlink and third information for configuring the semi-static uplink. UE 102 may also also include a receiving circuit configured to receive a semi-static downlink. UE 102 may further include a transmission scheme configured for semi-static uplink transmission. If semi-static downlink and semi-static uplink are configured for the same character set, the slot format denotes the same character set as the characters for downlink or uplink transmission, but not as flexible.

[00153] A description is provided of gNB 160. gNB 160 may include a high-level processor configured to transmit a generic and/or specific Radio Resource Control (RRC) configuration message and one or more specific RRC configuration messages. The general RRC message may include first information for indicating a slot format. The one or more specific RRC configuration messages include second information for configuring the semi-static downlink and third information for configuring the semi-static uplink. gNB 160 may also include a transmission scheme capable of semi-static downlink. gNB 160 may further include a receive circuit configured to receive a semi-static uplink. If semi-static downlink and semi-static uplink are configured for the same character set, the slot format denotes the same character set as the characters for downlink or uplink transmission, but not as flexible.

[00154] In FIG. 18 shows an example of slot formats for this slot. Slot format #0 may indicate that all symbols in the slot are DL symbols. Slot formats #1-13 may indicate that the slot is filled from the earliest symbol to 13 with DL symbol(s) followed by flexible symbol(s). Slot Format #14 may indicate that all symbols in the slot are flexible symbols. Slot formats #15-104 may indicate that the slot is filled from the earliest symbol to 12 with DL symbol(s) followed by flex type symbol(s). Slot formats #105-106 may indicate that the slot is filled from the earliest character to 2 with flexible character(s) followed by UL character(s). Slot format #107 may indicate that all symbols in the slot are UL symbols. The UE-specific Slot-assignment may be set using any of these indexes. On the other hand, perhaps the UE-wide parameter Slot-assignmentSIB1 and the SFI field indicated by the DCI format with CRC scrambled by SFI-RNTI cannot be set using each index. The UE-wide parameter Slot-assignmentSIB1 may be set using one of the predefined subsets (eg, a subset including 8 slot format indexes) of these indexes. The SFI field indicated by the DCI format with CRC scrambled by the SFI-RNTI may be specified with one of the subsets (eg, a subset including 8 slot format indexes) configured by a higher layer of those indexes.

[00155] Table X9 shows another example of slot formats. D, U, and X stand for downlink, uplink, and flexible type, respectively. Slot format #0 may indicate that all symbols in the slot are DL symbols. Slot Format #1 may indicate that all symbols in the slot are UL symbols. Slot Format #2 may indicate that all symbols in the slot are flexible symbols. Slot formats #3-7 and #17-18 may indicate that the slot is filled from the earliest symbol with the DL symbol(s) followed by the flexible type symbol(s). Slot Formats No. 8-15 may indicate that the slot is filled from the earliest character with flexible character(s) followed by UL character(s). Other slot formats may indicate that the slot is filled from the earliest symbol with DL symbol(s) followed by UL symbol(s).

Table X9

Format Symbol number in the slot 0 one 2 3 4 5 6 7 eight nine ten eleven 12 thirteen 0 D D D D D D D D D D D D D D one U U U U U U U U U U U U U U 2 X X X X X X X X X X X X X X 3 D D D D D D D D D D D D D X 4 D D D D D D D D D D D D X X 5 D D D D D D D D D D D X X X 6 D D D D D D D D D D X X X X 7 D D D D D D D D D X X X X X eight X X X X X X X X X X X X X U nine X X X X X X X X X X X X U U ten X U U U U U U U U U U U U U eleven X X U U U U U U U U U U U U 12 X X X U U U U U U U U U U U thirteen X X X X U U U U U U U U U U fourteen X X X X X U U U U U U U U U fifteen X X X X X X U U U U U U U U sixteen D X X X X X X X X X X X X X 17 D D X X X X X X X X X X X X eighteen D D D X X X X X X X X X X X nineteen D X X X X X X X X X X X X U 20 D D X X X X X X X X X X X U 21 D D D X X X X X X X X X X U 22 D X X X X X X X X X X X U U 23 D D X X X X X X X X X X U U 24 D D D X X X X X X X X X U U 25 D X X X X X X X X X X U U U 26 D D X X X X X X X X X U U U 27 D D D X X X X X X X X U U U 28 D D D D D D D D D D D D X U 29 D D D D D D D D D D D X X U thirty D D D D D D D D D D X X X U 31 D D D D D D D D D D D X U U 32 D D D D D D D D D D X X U U 33 D D D D D D D D D X X X U U 34 D X U U U U U U U U U U U U 35 D D X U U U U U U U U U U U 36 D D D X U U U U U U U U U U 37 D X X U U U U U U U U U U U 38 D D X X U U U U U U U U U U 39 D D D X X U U U U U U U U U 40 D X X X U U U U U U U U U U 41 D D X X X U U U U U U U U U 42 D D D X X X U U U U U U U U 43 D D D D D D D D D X X X X U 44 D D D D D D X X X X X X U U 45 D D D D D D X X U U U U U U 46 D D D D D D X D D D D D D X 47 D D D D D X X D D D D D X X 48 D D X X X X X D D X X X X X 49 D X X X X X X D X X X X X X fifty X U U U U U U X U U U U U U 51 X X U U U U U X X U U U U U 52 X X X U U U U X X X U U U U 53 X X X X U U U X X X X U U U 54 D D D D D X U D D D D D X U 55 D D X U U U U D D X U U U U 56 D X U U U U U D X U U U U U 57 D D D D X X U D D D D X X U 58 D D X X U U U D D X X U U U 59 D X X U U U U D X X U U U U 60 D X X X X X U D X X X X X U 61 D D X X X X U D D X X X X U 62–255 reserved

[00156] The time periods between a DL assignment and the corresponding DL data transmission may be indicated by a field in the DCI from the value set, the time periods between the UL assignment and the corresponding UL data transmission may be indicated by a field in the DCI from the value set, and the time periods between the receipt of DL data and the corresponding confirmation may be indicated by a field in the DCI from the value set. Value sets can be configured via higher layer signaling. The default time period(s) may (may) be predefined(s) at least if the UE 102 does not (are) aware of this (these) time period(s).

[00157] In FIG. 19 shows an example downlink scheduling and HARQ timeline. The PDCCH transmitted by gNB 1960 in slot n may carry the DCI format that the PDSCH schedules, the DCI format including at least two fields, the first field may indicate k ₁ and the second field may indicate k ₂ .

[00158] UE 1902 detecting a PDCCH in slot n may receive the scheduled PDSCH in slot n+k ₁ and then in slot n+k ₁ +k ₂ UE 1902 may send a HARQ-ACK report corresponding to the PDSCH. In an alternative embodiment, the second field may indicate m and have UE 1902 send a HARQ-ACK report in slot n+m. In other words, after detecting the corresponding PDCCH in slot i - k ₁ , UE 1902 may receive the PDSCH in slot i, UE 1902 may send a HARQ-ACK in slot j to transmit the PDSCH in slot j - k ₂ . In an alternative embodiment, UE 1902 may send a HARQ-ACK in slot j for PDSCH transmission scheduled by the corresponding PDCCH in slot j through m.

[00159] In FIG. 20 shows an example of an uplink scheduling timeline. The PDCCH transmitted by gNB 2060 in slot n may carry the DCI format that the PUSCH schedules, the DCI format including at least one field that may indicate k ₃ . The UE 2002 detecting the PDCCH in slot n may transmit the scheduled PUSCH in slot n+k ₃ . In other words, upon detecting a corresponding PDCCH in slot i - k ₃ UE 2002 may send a PUSCH in slot i.

[00160] In Fig. 21 shows an example of downlink aperiodic CSI-RS transmission. The PDCCH transmitted by gNB 2160 in slot n may carry a DCI format that indicates the presence of an aperiodic CSI-RS, the DCI format including at least one field that may indicate k ₄ . UE 2102 detecting a PDCCH in slot n may assume an aperiodic CSI-RS in slot n+k ₄ for CSI measurement and/or radio resource management (RRM).

[00161] In Fig. 22 shows an example of aperiodic SRS transmission on the uplink. The PDCCH transmitted by gNB 2260 in slot n may carry a DCI format that schedules aperiodic SRS, the DCI format including at least one field that may denote k ₅ . UE 2202 detecting a PDCCH in slot n may transmit a scheduled aperiodic SRS in slot n+k5. In other words, upon detecting a corresponding PDCCH in slot i - k ₅ UE 2202 may transmit an aperiodic SRS in slot i.

[00162] The presence/disabling of each of the fields described above can be configured using higher level signaling. The presence/disconnect configurations can be shared in the case of these fields. In an alternative embodiment, the presence/deactivation can be configured individually. If at least one of the fields is missing or disabled, a default value (eg, a predefined fixed value or a value included in system information) can be used instead. For example, the default value of k ₁ may be 0, and the default value of k ₂ or k ₃ may be 4.

[00163] If the field is present, UE 2202 may be configured with multiple values (eg, a first value to a fourth value) via higher layer signaling. Each of the possible field values (eg, a 2-bit field) may correspond to a different value among the configured values. UE 2202 may use as the value of k a value that corresponds to the field value specified in the associated field in the detected PDCCH.

[00164] UE 2202 may be configured with multiple values (eg, a first value to a third value) via higher layer signaling. At least one possible field value (eg, a 2-bit field) may correspond to a predefined fixed value. Each of the other possible field values (eg, a 2-bit field) may correspond to a different value among the configured values.

[00165] UE 2202 may use as the value of k a value that corresponds to the field value specified in the associated field in the detected PDCCH. In this case, without the ability to change the field presence configuration, gNB 2260 may use a predefined fixed value so that gNB 2260 and UE 2202 share the same value of k even if the RRC configuration for these configured higher layer values is changed. The preset fixed value may depend on the type of timing offset. For example, the value of k ₁ may be 0, and the value of k ₂ or k ₃ may be 4. In an alternative embodiment, instead of a predetermined fixed value, a value indicated by system information may be used.

[00166] PDSCH and/or PUSCH RE mapping may depend on higher layer signaling and/or layer 1 signaling such as DCI format 1 and 2 PDCCH. the following criteria: they are in resource blocks allocated for transmission; they are advertised as available to the PDSCH according to the configuration and/or indication of the rate negotiation resource set; they are not used for CSI-RS; they are not used for RS phase tracking (PT-RS); they are not reserved for SS/PBCH; they are not declared "reserved".

[00167] To decode the PDSCH according to the detected PDCCH, the UE may be configured with any of the higher layer parameters: rate-match-PDSCH-resource-set, including one or more reserved pairs of RBs (the higher layer parameter rate- match-PDSCH-resource-RBs, also called bitmap-1) and reserved symbols (higher-level parameters of rate-match-PDSCH-resource-symbols, also called bitmap-2), for which reserved RBs are used; rate-match-resources-v-shift including LTE-CRS-vshift(s); rate-match-resources-antenna-port, including LTE-CRS antenna ports, 1, 2, or 4 ports; rate-match-CORESET including the CORESET identifier(s) of the CORESET configured for the UE 2202 to track. UE 2202 may need to determine the PDSCH RE mapping according to the association of the provided rate matching patterns. For PDSCH decoding, UE 2202 negotiates rates between REs corresponding to the detected PDCCH that the PDSCH has scheduled. The UE 2202 is not expected to handle the case where the PDSCH DMRS REs overlap, even partially, on any of the REs indicated by the rate-match-PDSCH-resource-set and rate-match-resources-v rate negotiation configuration. -shift and rate-match-resources-antenna-port and rate-match-CORESET.

[00168] More specifically, at the RB symbol level, UE 2202 may represent an RRC configured with one or multiple pairs (e.g., up to 16 pairs) of bitmap-1 and bitmap-2 parameters, with each pair defining a set of time-frequency resources, i.e., e. kronecker(transpose(bitmap-1), bitmap-2). The bitmap-1 parameter has at least RB granularity (up to 275 bits, one bit corresponds to one RB). The bitmap-2 parameter consists of 14 characters (for example, always 14 bits for 1 slot) in time to which bitmap-1 applies (one bit per character). In addition, at the RB symbol level for the rate negotiation resource set(s), the UE 2202 may represent an RRC configured with one bitmap-3 parameter per bitmap-1 and bitmap-2 pair. Each bit in bitmap-3 corresponds to a one, equal to the duration of bitmap-2, and indicates the presence or absence of this pair in the one. The bitmap-3 parameter can be {1, 5, 10, 20, or 40 units}, but its duration does not exceed 20 or 40 ms. If bitmap-3 is configured, UE 2202 negotiates the rates in a pool of resource sets, with each resource being expressed by a set of bitmap-1, bitmap-2, and bitmap-3.

[00169] Layer 1 signaling may indicate resource sets for PDSCH rate negotiation. The DCI format for PDSCH scheduling may include, if configured, an information field for indicating PDSCH rate matching resources that are associated with the configured resource sets. There are several options. In the first case, 1 bit enables or disables one set of resources. In this embodiment, the information field contains N bits, and each bit corresponds to a different set of resources (ie, a different combination of bitmap-1 and bitmap-2). In the second option, 1 bit turns on or off all resource sets. In this embodiment, the information field contains 1 bit. In a third variant, the N bit enables or disables subsets of resource sets. In this embodiment, the information field contains N bits, and each bit corresponds to a different subset of the resource set (ie, a different subset of all combinations of bitmap-1 and bitmap-2). For example, in this embodiment, each entry of 2 ^N entries expressed in the information field indicates an on/off state for all configured resource sets. The presence of this bit field in DCI format is configured by higher layer signaling. In this case, "on" may mean that the resource set is not available for PDSCH transmission, and the PDSCH is rate-matched between the resource set. Here, "off" may mean that the resource set is available for PDSCH transmission, and the PDSCH is not rate-matched between the resource set, but is related to it; or vice versa.

[00170] In FIG. 23 shows a flowchart of a method for UE 102. A method for UE 102 is described. The method may include receiving a generic and/or specific Radio Resource Control (RRC) configuration message S10. The general RRC message may include first information for indicating a slot format. The method may also include receiving S11 one or more special RRC configuration messages. The one or more specific RRC configuration messages include second information for configuring the semi-static downlink and third information for configuring the semi-static uplink. The method may also include receiving the S12 semi-static downlink. The method may further include a semi-static uplink S13. If semi-static downlink and semi-static uplink are configured for the same character set, the slot format denotes the same character set as the characters for downlink or uplink transmission, but not as flexible.

[00171] In FIG. 24 is a flow diagram of a method for gNB 160. A method for gNB 160 is described. The method may include sending a generic and/or specific Radio Resource Control (RRC) configuration message to S20. The general RRC message may include first information for indicating a slot format. The method may also include sending S21 one or more specific RRC configuration messages. The one or more specific RRC configuration messages include second information for configuring the semi-static downlink and third information for configuring the semi-static uplink. The method may also include a semi-static downlink S22. The method may further include semi-static uplink reception S23. If semi-static downlink and semi-static uplink are configured for the same character set, the slot format denotes the same character set as the characters for downlink or uplink transmission, but not as flexible.

[00172] It should be noted that various changes are possible within the scope of the present invention defined by the claims, and embodiments that are developed by appropriate combination of the technical means described in accordance with different embodiments are also included in the technical scope of the present invention.

[00173] It should be noted that in most cases, UE 102 and gNB 160 may need to perform the same procedures. For example, when UE 102 performs a specified procedure (eg, the procedure described above), gNB 160 may also consider that UE 102 follows this procedure. In addition, in the case of gNB 160, it may also be necessary to perform appropriate procedures. Similarly, in the case where gNB 160 performs the specified procedure, UE 102 may also consider that gNB 160 follows this procedure. In addition, in the case of UE 102, it may also be necessary to perform appropriate procedures. Physical signals and/or channels that UE 102 receives may be transmitted by gNB 160. Physical signals and/or channels that UE 102 transmits may be received by gNB 160. Higher layer signals and/or channels (e.g., special messages about RRC Configuration) that UE 102 receives may be sent by gNB 160. Higher layer signals and/or channels (e.g., special RRC Configuration messages) that UE 102 sends may be received by gNB 160.

[00174] It should be noted that the names of the physical channels and/or signals described herein are given as examples.

[00175] The term "computer-readable media" refers to any available media that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a computer and/or processor-readable medium that is non-volatile and tangible. By way of example, and not limitation, computer-readable or processor-readable media may include RAM, ROM, EEPROM, CD-ROM, or other optical disk drive, magnetic disk drive, or other magnetic storage devices, or any other medium that can be be used to carry or store the required program code in the form of instructions or data structures that can be accessed by a computer or processor. In this document, the term "disc" refers to a disc that reproduces data optically using lasers (for example, compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-ray® disc), and to a disk that normally reproduces data magnetically (such as a floppy disk).

[00176] It should be noted that one or more of the methods described herein may be implemented and/or performed using equipment. For example, one or more of the methods described herein may be implemented and/or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[00177] Each of the methods described herein includes one or more steps or steps to carry out the described method. The steps and/or steps of the method can be interchanged with each other and/or combined into one step within the scope defined by the claims. In other words, if a particular order of steps or actions is not required for proper operation of the described method, the order and/or use of certain steps and/or actions can be changed without deviating from the scope defined by the claims.

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

[00179] The program executable in gNB 160 or UE 102 in accordance with the described systems and methods is a program (program assuming operation of a computer) that controls a CPU and the like. so as to perform the function in accordance with the described systems and methods. At the same time, the information that these devices process is temporarily stored in RAM during processing. The information is then stored on various ROMs or HDDs and read by the CPU as needed to be modified or written. The recording medium on which the program is stored can be any of semiconductor devices (for example, ROM, non-volatile memory card, etc.), optical storage devices (for example, DVD, MO, MD, CD, BD, etc. .), magnetic storage devices (eg magnetic tape, floppy disk, etc.) and the like. Moreover, in some cases, the function according to the systems and methods described above is implemented by executing a downloadable program, and, in addition, the function according to the systems and methods described is implemented in cooperation with an operating system or other application programs based on an instruction from the program.

[00180] Moreover, if programs are available on the market, a program stored on a portable storage medium can be distributed, or a program can be transferred to a server computer that is connected via a network such as the Internet. In this case, the storage device on the server computer is also included in the system. Moreover, some or all of the gNB 160 and UE 102 in accordance with the systems and methods described above may be implemented as an LSI, which is a typical integrated circuit. Each functional block of gNB 160 and UE 102 may be individually embedded on a chip, and some or all of the functional blocks may be combined on a chip. Moreover, the technique for implementing integrated circuits is not limited to LSI, and an integrated circuit for a functional block may be implemented with a dedicated circuit or a general purpose processor. In addition, when a technology embodied in an integrated circuit replacing existing LSIs appears in the field of semiconductors, an integrated circuit to which such technology has been applied can also be used.

[00181] Moreover, each functional block or various elements of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is usually an integrated circuit or a plurality of integrated circuits. Circuit capable of performing the functions described in this data sheet may include a general purpose processor, digital signal processor (DSP), custom or application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, circuits on discrete components or transistorized logic circuits, a discrete hardware component, or a combination of both. A general purpose processor may be a microprocessor, or in an alternative embodiment, the processor may be a conventional processor, controller, microcontroller, or state machine. The general purpose processor, or each circuit described above, may be implemented as a digital circuit, or may be implemented as an analog circuit. Additionally, when a technology embodied in an integrated circuit appears in the field of semiconductors, replacing existing integrated circuits, an integrated circuit according to this technology can also be used.

Claims (32)

1. User equipment (UE) containing: a high-level processor configured to receive, via radio resource control (RRC) configuration messages, first information for specifying a slot format, second information for configuring downlink reception(s), and third information for configuring uplink transmission(s); a reception scheme configured to perform the reception(s) on the downlink; and a transmission scheme configured to perform uplink transmission(s); and for the slot symbol set that is indicated as flexible by the first information, the UE waits to receive neither the second information configuring the downlink reception(s) by the user equipment in the slot symbol set nor the third information configuring the uplink transmission(s) communication lines from the user equipment in the character set of the slot, the first information is included in the general RRC configuration message, and the second information and the third information are included in one or more specific RRC configuration messages. 2. The UE according to claim 1, wherein in case the downlink reception(s) and uplink transmission(s) are configured for the same set of symbol(s) in a slot, the format slot, according to the first information, indicates this same set of symbol(s) as for downlink or uplink, but not as flexible. 3. A base station configured to communicate with a user equipment (UE), the base station comprising: a high-level processor configured to send, via radio resource control (RRC) configuration messages, first information for specifying the slot format, second information for configuring the downlink reception(s) by the user equipment, and third information for configuring the uplink transmission(s) from user equipment; a transmission scheme configured to perform downlink transmission(s) corresponding to the downlink reception(s) by the user equipment; and a reception circuit configured to perform uplink reception(s) corresponding to the uplink transmission(s) from the user equipment; and for the slot character set that is indicated as flexible by the first information, the base station sends neither the second information configuring the downlink reception(s) by the user equipment in the slot character set nor the third information configuring the uplink transmission(s) communication lines from the user equipment in the character set of the slot, the first information is included in the general RRC configuration message, and the second information and the third information are included in one or more specific RRC configuration messages. 4. The base station according to claim 3, wherein in case the downlink reception(s) and uplink transmission(s) are configured for the same set of symbol(s) in the slot, the slot format, according to the first information, indicates this same set of symbol(s) as for downlink or uplink, but not as flexible. 5. A communication method for a user equipment (UE), comprising the steps of: receiving, by radio resource control (RRC) configuration messages, first information for specifying a slot format, second information for configuring downlink reception(s), and third information for configuring uplink transmission(s); perform reception(s) on the downlink; and performing transmission(s) on the uplink; and for the slot symbol set that is indicated as flexible by the first information, the UE waits to receive neither the second information configuring the downlink reception(s) by the user equipment in the slot symbol set nor the third information configuring the uplink transmission(s) communication lines from the user equipment in the character set of the slot, the first information is included in the general RRC configuration message, and the second information and the third information are included in one or more specific RRC configuration messages. 6. The method of claim 5, wherein if the downlink reception(s) and uplink transmission(s) are configured for the same set of symbol(s) in the slot, the format slot, according to the first information, indicates this same set of symbol(s) as for downlink or uplink, but not as flexible. 7. A communication method for a base station configured to communicate with a user equipment (UE), the method comprising: sending by radio resource control (RRC) configuration messages first information for specifying the slot format, second information for configuring downlink reception(s) by the user equipment, and third information for configuring uplink transmission(s) from the UE; performing downlink transmission(s) corresponding to downlink reception(s) by the user equipment; and performing uplink reception(s) corresponding to uplink transmission(s) from the user equipment; and for the slot character set that is indicated as flexible by the first information, the base station sends neither the second information configuring the downlink reception(s) by the user equipment in the slot character set nor the third information configuring the uplink transmission(s) communication lines from the user equipment in the character set of the slot, the first information is included in the general RRC configuration message, and the second information and the third information are included in one or more specific RRC configuration messages. 8. The method of claim 7, wherein if the downlink reception(s) and uplink transmission(s) are configured for the same set of symbol(s) in the slot, the format slot, according to the first information, indicates this same set of symbol(s) as for downlink or uplink, but not as flexible.

Images