User Equipment, Base Station, and Method for Configurable Downlink Control Information Format

Abstract

The present invention describes a user equipment (UE). The UE includes a high-layer processor configured to monitor an uplink (UL) downlink control information (DCI) format that includes first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH). The high-layer processor is further configured to monitor a downlink (DL) DCI format that includes second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to user equipment, base stations, and methods for configurable downlink control information (DCI) formats. Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable services, expanded coverage areas, and enhanced functionality. A wireless communication system can provide communication for multiple wireless communication devices, and each wireless communication device can be served by a base station. A base station can be a device that communicates with wireless communication devices.

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

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

[0005] In one example, a user equipment (UE) includes: a receiving circuit configured to receive a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation, the receiving circuit configured to receive an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; a transmitting circuit configured to perform the first PUSCH transmission based on detecting the first DCI format according to the first information, the transmitting circuit configured to perform the second PUSCH transmission based on detecting the second DCI format according to the second information, wherein the first DCI format and the second DCI format are monitored in different search spaces.

[0006] A base station apparatus, comprising: a transmission circuit configured to transmit a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation, the transmission circuit being configured to transmit an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; a receiving circuit configured to receive the first PUSCH transmission based on the transmission of the first DCI format according to the first information, the receiving circuit being configured to receive the second PUSCH transmission based on the transmission of the second DCI format according to the second information, wherein the first DCI format and the second DCI format are monitored in different search spaces.

[0007] In one example, a communication method of a user equipment (UE) includes: receiving a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation; receiving an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; transmitting the first PUSCH transmission based on detecting the first DCI format according to the first information; transmitting the second PUSCH transmission based on detecting the second DCI format according to the second information, wherein the first DCI format and the second DCI format are monitored in different search spaces.

[0008] In one example, a communication method of a base station device includes: transmitting a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation; transmitting an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; receiving a first PUSCH transmission based on the first information according to the transmission of the first DCI format; and receiving the second PUSCH transmission based on the second information according to the transmission of the second DCI format, wherein the first DCI format and the second DCI format are monitored in different search spaces. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 Figure 1 is a block diagram illustrating one particular implementation of one or more base stations (gNBs) and one or more user equipments (UEs) in which systems and methods for configurable downlink control information (DCI) formats may be implemented.

[0010] Figure 2 Figure 2 is a diagram illustrating an example of a resource grid for the downlink.

[0011] Figure 3 Figure 3 is a diagram illustrating an example of a resource grid for the uplink.

[0012] Figure 4 Figure 4 illustrates examples of several parameters.

[0013] Figure 5 Figure 5 illustrates for Figure 4 an example of a subframe structure of the parameters shown in

[0014] Figure 6 Figure 6 illustrates examples of time slots and sub - slots.

[0015] Figure 7 Figure 7 illustrates an example of a scheduling timeline.

[0016] Figure 8 Figure 8 ​​​​​​​​​​​​​​​​Shows an example of a DL control channel monitoring area.

[0017] Figure 9 Figure 9 Shows an example of a DL control channel including more than one control channel element.

[0018] Figure 10 Figure 10 Shows an example of a UL control channel structure.

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

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

[0021] Figure 13 Figure 13 Shows various components that can be utilized in a UE.

[0022] Figure 14 Figure 14 Shows various components that can be utilized in a gNB.

[0023] Figure 15 Figure 15 Is a block diagram showing an implementation of a UE in which the systems and methods described herein can be implemented.

[0024] Figure 16 Figure 16 Is a block diagram showing an implementation of a gNB in which the systems and methods described herein can be implemented.

[0025] Figure 17 Figure 17 Is a flowchart showing a method performed by a UE.

[0026] Figure 18 Figure 18 Is a flowchart showing a method performed by a gNB. Detailed implementation

[0027] ​​​​​​​​​​​​​​​​​​​​The present invention describes a user equipment (UE). The UE includes a higher layer processor configured to monitor an uplink (UL) downlink control information (DCI) format, the uplink DCI format including first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH). The higher layer processor is further configured to monitor a downlink (DL) DCI format, the downlink DCI format including second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

[0028] The first information of the UL DCI format may include at least one of antenna port information, transmission configuration indication, sounding reference signal (SRS) request, carrier indication, channel state information (CSI) request, beta_offset indicator, SRS resource indicator, repetition factor, priority indication, or time domain resource allocation.

[0029] The second information of the DL DCI format may include antenna port information, transmission configuration indication, SRS request, carrier indication, repetition factor, priority indication, rate matching indicator, physical resource block (PRB) bundling size indicator, zero power (ZP) channel state information reference signal (CSI-RS) trigger, or time domain resource allocation.

[0030] In one method, the UL DCI format and the DL DCI format are new DCI formats. In another method, the first information of the UL DCI format and the second information of the DL DCI format modify the 3GPP Release-15 DCI format. Fields in the 3GPP Release-15 DCI format may be reinterpreted to determine the first information and the second information.

[0031] The present invention also describes a base station (gNB). The gNB includes a higher layer processor configured to generate a UL DCI format, the UL DCI format including first information for scheduling enhanced URLLC services on a PUSCH. The higher layer processor is further configured to generate a DL DCI format, the DL DCI format including second information for scheduling enhanced URLLC services on a PDSCH.

[0032] A method performed by a UE is also described. The method includes monitoring a UL DCI format, the UL DCI format including first information for scheduling enhanced URLLC services on a PUSCH. The method further includes monitoring a DL DCI format, the DL DCI format including second information for scheduling enhanced URLLC services on a PDSCH.

[0033] A method performed by a gNB is also described. The method includes generating an UL DCI format that includes first information for scheduling enhanced URLLC services on a PUSCH. The method also includes generating a DL DCI format that includes second information for scheduling enhanced URLLC services on a PDSCH.

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

[0035] 3GPP Long-Term Evolution (LTE) is the name given to a project that was awarded to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to meet future requirements. In one aspect, UMTS has been modified to provide support and specifications for the Evolved Universal Terrestrial Radio Access (E-UTRA) and the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0036] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0037] A wireless communication device can be an electronic device that is used to transmit voice and / or data to a base station, which in turn can communicate with the device's network (e.g., a Public Switched Telephone Network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, since the scope of the present disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to represent the more general term "wireless communication device". A UE may also be more generally referred to as a terminal device.

[0038] In 3GPP specifications, a base station is typically referred to as Node B, evolved Node B (eNB), Home eNode B (HeNB), or some other similar terms. Since the scope of this disclosure should not be limited to 3GPP standards, the terms "base station", "Node B", "eNB", "gNB", and / or "HeNB" may be used interchangeably herein to represent the more general term "base station". Additionally, the term "base station" may be used to represent an access point. An access point can be an electronic device that provides access to a network (e.g., a local area network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to represent wireless communication devices and / or base stations. An eNB may also be more generally referred to as a base station device.

[0039] It should be noted that as used herein, a "cell" can be any such communication channel: which is designated by a standardization or regulatory body for use in Advanced International Mobile Telecommunications (IMT-Advanced) and all or a subset thereof, such that it is adopted by 3GPP as an authorized frequency band (e.g., a frequency band) for communication between an eNB and a UE. It should also be pointed out that in the overall description of E-UTRA and E-UTRAN, as used herein, a "cell" can be defined as "a combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in the system information that can be transmitted on the downlink resources.

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

[0041] The fifth generation (5G) cellular communication (also known as "New Radio", "New Radio Access Technology", or "NR" by 3GPP) envisions the use of time, frequency, and / or spatial resources to enable services such as enhanced mobile broadband (eMBB) communication, ultra-reliable low-latency communication (URLLC), and massive machine-type communication (MMTC). A New Radio (NR) base station may be referred to as a gNB. A gNB may also be more generally referred to as base station equipment.

[0042] For enhanced URLLC services and / or other services in future releases, the current DCI formats in Release 15 of 3GPP (e.g., DCI format 0_0, DCI format 0_1) may not be supportive. More information may need to be included in the DCI (e.g., antenna port, transmission configuration indicator, rate matching indicator, SRS request, PRB bundling size indicator, carrier indicator, CSI request, ZP CSI-RS trigger, β-offset indicator, SRS resource indicator, repetition factor, priority indicator, etc.). In such cases, new DCI formats and / or modified current DCI formats may be introduced.

[0043] Some configurations of the systems and methods described herein teach methods for URLLC transmission and / or retransmission management to meet latency and / or reliability requirements. Some requirements for URLLC relate to user (U)-plane latency and reliability. For URLLC, for both UL and DL, the target user plane latency is 0.5 milliseconds (ms). For X bytes within 1 millisecond (ms), the target reliability is 1 - 10 5 。

[0044] These URLLC-specific constraints make the design of hybrid automatic repeat request (HARQ) and retransmission mechanisms difficult. For example, the receiver must respond with a fast acknowledgement (ACK) or negative acknowledgement (NACK) or uplink grant to meet the latency requirement, or the transmitter can retransmit immediately without waiting for ACK / NACK to improve reliability. On the other hand, support for grant-based or grant-free repetition is provided to further improve reliability. How to terminate the repetition is also an important issue. The systems and methods teach URLLC HARQ and / or retransmission design in different scenarios.

[0045] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, where like reference numerals may indicate functionally similar elements. The systems and methods generally described and illustrated in the accompanying drawings herein can be arranged and designed in a variety of different specific embodiments. Accordingly, the more detailed description of several specific embodiments presented below in the drawings is not intended to limit the scope of the claimed subject matter, but merely represents the systems and methods.

[0046] Figure 1FIG. 0 is a block diagram illustrating a particular implementation of one or more base stations (gNBs) 160 and one or more user equipments (UEs) 102 in which a system and method for configurable downlink control information (DCI) formats may be implemented. One or more UEs 102 communicate with one or more gNBs 160 using one or more antennas 122a-n. For example, UE 102 uses one or more antennas 122a-n to transmit electromagnetic signals to gNB 160 and receive electromagnetic signals from gNB 160. gNB 160 communicates with UE 102 using one or more antennas 180a-n.

[0047] UE 102 and gNB 160 may communicate with each other using one or more channels 119, 121. For example, UE 102 may use one or more uplink channels 121 to transmit information or data to gNB 160. Examples of uplink channel 121 include PUCCH (Physical Uplink Control Channel) and PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channel 121 (e.g., PUSCH) may be used to transmit UL data (i.e., transport block), MAC PDU, and / or UL-SCH (uplink shared channel)).

[0048] Here, UL data may include URLLC data. URLLC data may be UL-SCH data. Here, URLLC-PUSCH (i.e., a different physical uplink shared channel from PUSCH) may be defined to transmit URLLC data. For simplicity of description, the term "PUSCH" may represent any one of the following: (1) only PUSCH (e.g., conventional PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not conventional PUSCH).

[0049] Moreover, for example, uplink channel 121 may be used to transmit hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI), and / or scheduling request (SR). HARQ-ACK may include information indicating an acknowledgement (ACK) or negative acknowledgement (NACK) of DL data (i.e., transport block), media access control protocol data unit (MAC PDU), and / or DL-SCH (downlink shared channel).

[0050] CSI may include information indicating the channel quality of the downlink. SR may be used to request UL-SCH (uplink shared channel) resources for new transmissions and / or retransmissions. That is, SR may be used to request UL resources for transmitting UL data.

[0051] For example, one or more gNBs 160 may also transmit information or data to one or more UEs 102 using one or more downlink channels 119. Examples of the downlink channel 119 include PDCCH, PDSCH, etc. Other types of channels may be used. The PDCCH may be used to transmit downlink control information (DCI).

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

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

[0054] The demodulator 114 may demodulate the one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signals. The decoder 108 may generate a decoded signal 110, which may include a UE decoded signal 106 (also referred to as a first UE decoded signal 106). For example, the first UE decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as a second UE decoded signal 110) may include overhead data and / or control data. For example, the second UE decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0055] Generally speaking, the UE operation module 124 enables the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include a UE scheduling module 126.

[0056] The UE scheduling module 126 may perform operations on configurable downlink control information (DCI) formats. In New Radio (NR), the UE 102 may support multiple types of UL transmissions (PUSCH transmissions). UL transmissions may include grant-based UL transmissions (e.g., UL transmissions with grants, dynamic grants, PUSCH transmissions with grants, PUSCH transmissions scheduled by DCI (e.g., DCI format 0_0, DCI format 0_1)) and grant-free UL transmissions (e.g., UL transmissions without grants or configured grants, PUSCH transmissions with configured grants).

[0057] There may be two types of grant-free UL transmissions (e.g., UL transmissions without grants, with configured grants, PUSCH transmissions with configured grants). One type of grant-free UL transmission is configured grant type 1, and the other is configured grant type 2.

[0058] For type 1 PUSCH transmissions with configured grants, the relevant parameters may be fully RRC-configured (e.g., configured using RRC signaling). For example, parameters for resource allocation provided by an RRC message (rrc-ConfiguredUplinkGrant), such as time domain resource allocation (timeDomainOffset, timeDomainAllocation), frequency domain resource allocation (frequencyDomainAllocation), modulation and coding scheme (MCS) (e.g., mcsAndTBS), antenna port values, bit values for DMRS sequence initialization, precoding information and number of layers, SRS resource indicator (provided by antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator respectively), frequency offset between two frequency hops (frequencyHoppingOffset), etc.

[0059] Activation (e.g., PDCCH, DCI activation) may not be used for type 1 configured grants. That is, for configured grant type 1, the uplink grant is provided by RRC and stored as a configured uplink grant. Retransmissions of configured grant type 1 may be scheduled by a PDCCH with a CRC scrambled by CS-RNTI (configured scheduling RNTI).

[0060] For type 2 PUSCH transmissions with configured grants, the relevant parameters follow the higher layer configuration (e.g., periodicity, number of repetitions, etc.) and the UL grant received on a DCI addressed to the CS-RNTI (PDCCH with CRC scrambled by the CS-RNTI, L1 activation and / or reactivation). That is, for configured grant type 2, the uplink grant can be provided by the PDCCH and stored or cleared as the configured uplink grant based on L1 signaling indicating the activation or deactivation of the configured uplink grant.

[0061] Retransmissions of configured grant type 2 can be scheduled by a PDCCH with CRC scrambled by the CS-RNTI. That is, retransmissions other than repeating the configured uplink grant can use the uplink grant addressed to the CS-RNTI. If the higher layer does not deliver a transport block for transmission on the resources allocated for uplink transmission without a grant, UE 102 may not transmit anything on the resources configured for PUSCH transmission with a configured grant.

[0062] Thus, in NR, UE 102 may support multiple types of uplink transmissions without a grant (also referred to as grant-free (GF) uplink transmissions or GF transmissions or transmissions using a configured grant). The first type (type 1) of GF transmission can be a grant-free UL data transmission, which can be based only on RRC (re)configuration without any L1 signaling. In the second type (type 2) of GF transmission, the grant-free UL data transmission is based on RRC configuration and L1 signaling for the activation and / or deactivation of the grant-free UL data transmission. An example of an RRC configuration is shown in List 1.

[0063]

[0064]

[0065]

[0066] List 1

[0067] For type 2, PDCCH activation is required. Lists 2 and 3 show examples of DCI format 0_0 (e.g., fallback DCI) and format 0_1, which can be used to activate type 2 configured grants, and / or retransmit type 2 configured grants and / or type 1 configured grants.

[0068]

[0069]

[0070] List 2

[0071]

[0072]

[0073] List 3

[0074] For both type 1 and type 2 PUSCH transmissions with configured grants, when UE 102 is configured with repK > 1, UE 102 may repeat the TB across repK consecutive time slots, thus applying the same symbol allocation in each time slot. The parameter repK may be referred to as the number of configured transmission occasions for the repetition (including the initial transmission) of the TB. If the UE procedure for determining the time slot configuration determines that the symbols of the time slot allocated for PUSCH are downlink symbols, then for multi-time slot PUSCH transmission, the transmission on that time slot may be omitted.

[0075] For grant-based transmissions, PUSCH transmissions are scheduled by DCI (e.g., DCI format 0_0 and DCI format 0_1 shown above). PUSCH may be allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with a CRC scrambled by C-RNTI, new-RNTI (e.g., the first RNTI), TC-RNTI, or SP-CSI-RNTI. In the specification, new-RNTI may be referred to as MCS-C-RNTI. Some UE-specific PUSCH parameters may be configured by RRC. An example of RRC configuration is shown in List 4. For example, pusch-AggregationFactor in PUSCH-Config indicates the number of repetitions of the data. When UE 102 is configured with pusch-AggregationFactor > 1, the same symbol allocation may be applied across pusch-AggregationFactor consecutive time slots, and PUSCH may be limited to a single transmission layer. UE 102 may repeat the transport block (TB) across pusch-AggregationFactor consecutive time slots, thus applying the same symbol allocation in each time slot. If the UE procedure for determining the time slot configuration determines that the symbols of the time slot allocated for PUSCH are downlink symbols, then for multi-time slot PUSCH transmission, the transmission on that time slot may be omitted.

[0076] For a PUSCH retransmission with a CRC scrambled by a CS-RNTI having a new data indicator (NDI) equal to 1 (i.e., NDI = 1) and scheduled by a PDCCH, if UE 102 is configured with pusch-AggregationFactor, the same symbol allocation may be applied across consecutive time slots of pusch-AggregationFactor, and the PUSCH may be limited to a single transport layer. UE 102 may repeat the TB across consecutive time slots of pusch-AggregationFactor, thereby applying the same symbol allocation in each time slot.

[0077]

[0078]

[0079]

[0080] List 4

[0081] For enhanced URLLC services and / or other services in future releases, the current DCI formats in 3GPP Release 15 (also known as Rel-15) (e.g., DCI format 0_0, DCI format 0_1) may not be supportive. More information may need to be included in the DCI (e.g., antenna port, transmission configuration indicator, rate matching indicator, SRS request, PRB bundling size indicator, carrier indicator, CSI request, ZP CSI-RS trigger, β-offset indicator, SRS resource indicator, repetition factor, priority indicator, etc.). In such cases, new DCI formats and / or modified / enhanced current DCI formats may be introduced.

[0082] In the design, a new DCI format (e.g., DCI format 0_2, the specification may use a different name) may be introduced. DCI format 0_2 may be used to schedule PUSCH in a cell. The following information may be transmitted via DCI format 0_2.

[0083] DCI format 0_2 may include an identifier of the DCI format. The value of this field may be set to a predefined and / or default value (e.g., 0 or 1) to indicate the new / different DCI format (compared to DCI format 0_0 and / or DCI format 0_1) for enhanced URLLC and / or other services.

[0084] DCI format 0_2 may include an identifier of the UL / DL DCI format. The value of this field may be set to a predefined and / or default value indicating the UL DCI format (e.g., 0 or 1).

[0085] DCI format 0_2 may include antenna ports. The number of bits in the bit field may be 0 - 2 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the configured waveform (e.g., whether transform precoder is enabled). The number of bits in the bit field may be determined by the DMRS type, rank, codebook, and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in the field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters for determining the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0086] DCI format 0_2 may include transmission configuration indication. The number of bits in the bit field may be 0 - 3 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the number of configured transmission configurations. For example, if multiple configurations are not enabled, the number of bits in the field is 0, or the bit field does not exist in the DCI. If the number of transmission configurations is 8, the number of bits in the field may be 3. If multiple transmission configurations are enabled and / or configured, DCI format 0_2 may be used only to activate and / or deactivate the corresponding configuration grants.

[0087] DCI format 0_2 may include SRS request. The number of bits in the bit field may be 0 - 2 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the configured carrier (e.g., whether SUL is configured). The number of bits in the bit field may be determined by a configured and / or predefined table and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in the field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters and / or tables configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters for determining the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0088] DCI format 0_2 may include a carrier indication. The number of bits in this bit field may be 0 - 3 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the number of configured carriers. For example, if multiple carriers are not enabled and / or configured, the number of bits in this field is 0, or this bit field does not exist in the DCI. If the number of carriers is greater than 4, the number of bits in this field may be 3. Any one of the higher layer parameters used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters and / or tables configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters for determining the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0089] DCI format 0_2 may include a CSI request. The number of bits in this bit field may be 0 - 3 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the CSI configuration. The number of bits in this bit field may be determined by a configured and / or predefined table, and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters and / or tables configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters for determining the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0090] DCI format 0_2 may include a beta_offset indicator. The number of bits in this bit field may be 0 - 2 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the beta_offset configuration type (e.g., whether beta_offset is semi-static or dynamic). The number of bits in this bit field may be determined by the configured beta_offset set. The number of bits in this bit field may be determined by a configured and / or predefined table, and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters and / or tables configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters for determining the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0091] DCI format 0_2 may include an SRS resource indicator. The number of bits in the bit field may be 0 - 4 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the number of SRS resources configured in the SRS resource set. The number of bits in the bit field may be determined by the maximum number of supported layers of PUSCH, codebook, and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters used to determine the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0092] DCI format 0_2 may include a repetition factor. The number of bits in the bit field may be 0 - 2 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the configured and / or predefined set of repetition factors. For example, if the dynamic indication of the repetition factor is not enabled, configured, and / or supported, the number of bits in this field is 0, or the bit field does not exist in the DCI. If the dynamic indication of the repetition factor is enabled, configured, and / or supported, and / or the number of repetition factors in the configured and / or predefined set is 4 (e.g., {1, 2, 4, 8}), the number of bits in this field may be 2. Any one of the higher layer parameters, sets, and / or tables used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or be configured separately for DCI format 0_2. In other words, the parameters, tables, and / or sets configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters, tables, and / or sets used to determine the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0093] DCI format 0_2 may include a priority indication. The number of bits in this bit field may be 0 - 3 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by a configured and / or predefined set of priorities and / or the number of configured and / or predefined priorities. For example, if PUSCH priority is not enabled, configured, and / or supported, the number of bits in this field is 0, or this bit field does not exist in the DCI. If the number of configured and / or predefined PUSCH priorities is 4 (e.g., {1, 2, 4, 8}), the number of bits in this field may be 2. Any one of the higher layer parameters, sets, and / or tables used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or may be configured separately for DCI format 0_2. In other words, the parameters, tables, and / or sets configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 0_2, or the parameters, tables, and / or sets used to determine the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0094] DCI format 0_2 may include a time domain resource allocation. The number of bits in this bit field may be 0 - 6 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the number of entries in a time domain resource allocation table configured by a higher layer (e.g., RRC configuration) or a default time domain resource allocation table. Any one of the higher layer parameters (e.g., configured time domain resource allocation table, default and / or predefined time domain resource allocation table) used to determine the number of bits in this field may generally be configured for DCI format 0_2 and other DCI formats, or may be configured separately for DCI format 0_2. In other words, the parameters (e.g., time domain resource allocation table configured by a higher layer) configured for Rel-15 DCI format field size determination may also be applied to the corresponding bit field of DCI format 0_2, or the parameters and / or tables used to determine the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0095] For example, a first parameter (e.g., PUSCH-TimeDomainResourceAllocation) is used to configure the time domain relationship between a PDCCH (e.g., DCI format 0_0, DCI format 0_1, and / or DCI format 0_2) and a PUSCH (e.g., PUSCH transmission). For example, the first parameter may include information indicating an offset (e.g., slot offset) to be applied to the PUSCH transmission. Additionally, the first parameter may include information indicating an index that gives a valid combination of a starting symbol and a length to be applied to the PUSCH transmission (also referred to as a starting and length indicator (SLIV)). Additionally, the first parameter may include information indicating the PUSCH mapping type to be applied to the PUSCH transmission.

[0096] Here, the gNB 160 may transmit one or more sets of first parameters (e.g., PUSCH-TimeDomainResourceAllocationList) by using an RRC message. Also, the gNB 160 may indicate one set of first parameters from one or more sets of first parameters by using a value of a time domain resource allocation field (e.g., value “M”). That is, the gNB 160 may indicate which of the configured first parameters applied to the PUSCH transmission by the UE 102 by using the value of the time domain resource allocation field.

[0097] That is, in the case where the UE 102 detects DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2, an offset (e.g., slot offset), an index of a starting symbol and a length, and / or a PUSCH mapping type may be determined based on the value of the time domain resource allocation field included in DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2. For example, the value of the time domain resource allocation field (e.g., value “m”) may be used to indicate a row index of a first resource allocation table (e.g., row index “m + 1”), and the first resource allocation table may be used to define one or more sets of first parameters (e.g., an offset (e.g., slot offset), an index of a starting symbol and a length, and / or a PUSCH mapping type). That is, an index row of the first resource allocation table may be used to define one or more sets of first parameters (e.g., an offset (e.g., slot offset), an index of a starting symbol and a length, and / or a PUSCH mapping type). Here, one or more sets of first parameters (e.g., an offset (e.g., slot offset), an index of a starting symbol and a length, and / or a PUSCH mapping type) may be applied to the PUSCH transmission scheduled by using DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2.

[0098] In addition, the number of bits (e.g., size and / or bit width) of the time domain resource allocation field (e.g., DCI field) can be determined based on the number of entries in the first resource allocation table (i.e., the number of entries in PUSCH-TimeDomainResourceAllocationList). For example, the maximum number of the first allocation table (i.e., the maximum number of the first parameter (i.e., PUSCH-TimeDomainResourceAllocation) in PUSCH-TimeDomainResourceAllocationList) can be a first value (e.g., 16). That is, the maximum number of bits of the time domain resource allocation field included in DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 can be 4 bits (i.e., corresponding to the first value). For example, in the case where 5 groups of the first parameters (i.e., 5 entries of the first resource allocation table) are configured, UE 102 can consider the number of bits of the time domain resource allocation field included in DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 to be 3 bits. In addition, for example, in the case where 14 groups of the first parameters (i.e., 14 entries of the first resource allocation table) are configured, UE 102 can consider the number of bits of the time domain resource allocation field included in DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 to be 4 bits.

[0099] Here, one or more groups of the first parameters (e.g., PUSCH-TimeDomainResourceAllocationList) can be included in the third information (e.g., PUSCH-ConfigCommon). For example, the third information can be used to configure cell-specific PUSCH parameters. For example, the system information (e.g., system information block 1) can include the third information. In addition, one or more groups of the first parameters (e.g., PUSCH-TimeDomainResourceAllocationList) can be included in the fourth information (e.g., PUSCH-Config). For example, the fourth information can be used to configure UE-specific parameters. For example, the dedicated RRC message can include the fourth information. For example, the first set of values of the first parameter can be included in the third information, and the second set of values of the first parameter can be included in the fourth information.

[0100] Also, when the UE 102 detects a PDCCH of DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 in a common search space (e.g., a set of common search spaces) associated with CORESET 0, one or more sets of first parameters included in the third information can be used (e.g., applied to PUSCH transmission). Additionally, when the UE 102 detects a PDCCH of DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 in a common search space (e.g., a set of common search spaces) not associated with CORESET 0, one or more sets of first parameters included in the fourth information can be used (e.g., applied to PUSCH transmission). Additionally, when the UE 102 detects a PDCCH of DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 in a UE-specific search space (e.g., a set of UE-specific search spaces), one or more sets of first parameters included in the fourth information can be used (e.g., applied to PUSCH transmission).

[0101] Additionally, when one or more sets of first parameters included in the third information and one or more sets of first parameters included in the fourth information are not configured, the default value of the first parameter (e.g., default time-domain resource allocation) can be used (e.g., applied to PUSCH transmission). Here, the default value of the first parameter can be predefined in advance through the specifications and known information between the gNB 160 and the UE 102. For example, when one or more sets of first parameters included in the third information and one or more sets of second parameters included in the fourth information are not configured, and when the UE 102 (e.g., in a UE-specific search space, in a common search space associated with and / or not associated with CORESET 0) detects a PDCCH for DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2, the default value of the first parameter can be used (e.g., applied to PUSCH transmission).

[0102] Additionally, a second parameter (e.g., PUSCH-TimeDomainResourceAllocation2) is used to configure the time-domain relationship between the PDCCH (e.g., DCI format 0_2) and the PUSCH (e.g., PUSCH transmission). For example, the second parameter can include information indicating an offset (e.g., a slot offset and / or a symbol offset) to be applied to the PUSCH transmission. Additionally, the second parameter can include information indicating an index that gives a valid combination of a starting symbol and a length to be applied to the PUSCH transmission (also referred to as a starting and length indicator (SLIV)). Additionally, the second parameter can include information indicating the PUSCH mapping type to be applied to the PUSCH transmission.

[0103] Here, the gNB 160 can transmit one or more sets of second parameters (e.g., PUSCH-TimeDomainResourceAllocationList2) by using an RRC message. Also, the gNB 160 can indicate one set of first parameters from one or more sets of first parameters by using the value of a time domain resource allocation field (e.g., the value "M"). That is, the gNB 160 can indicate which of the configured first parameters applied by the UE 102 to PUSCH transmission by using the value of the time domain resource allocation field.

[0104] That is, in the case where the UE 102 detects DCI format 0_2, the offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PUSCH mapping type can be determined based on the value of the time domain resource allocation field included in DCI format 0_2. For example, the value of the time domain resource allocation field (e.g., the value "m") can be used to indicate the row index of a second resource allocation table (e.g., row index "m + 1"), and the second resource allocation table can be used to define one or more sets of second parameters (e.g., offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PUSCH mapping type). That is, the index row of the second resource allocation table can be used to define one or more sets of second parameters (e.g., offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PUSCH mapping type). Here, one or more sets of second parameters (e.g., offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PUSCH mapping type) can be applied to the PUSCH transmission scheduled by using DCI format 0_2.

[0105] Additionally, the number of bits (e.g., size and / or bit width) of the time domain resource allocation field (e.g., the DCI field) can be determined based on the number of entries in the second resource allocation table (i.e., the number of entries in PUSCH-TimeDomainResourceAllocationList2). For example, the maximum number of the second allocation table (i.e., the maximum number of the second parameter (i.e., PUSCH-TimeDomainResourceAllocation2) in PUSCH-TimeDomainResourceAllocationList2) can be a second value (e.g., 64). That is, the maximum number of bits of the time domain resource allocation field included in DCI format 0_2 can be 6 bits (i.e., corresponding to the first value). For example, in the case where 5 groups of second parameters (i.e., 5 entries of the second resource allocation table) are configured, UE 102 can consider the number of bits of the time domain resource allocation field included in DCI format 0_2 to be 3 bits. Additionally, for example, in the case where 50 groups of second parameters (i.e., 50 entries of the second resource allocation table) are configured, UE 102 can consider the number of bits of the time domain resource allocation field included in DCI format 0_2 to be 6 bits.

[0106] Here, the number of bits of the time domain resource allocation field can be fixed (e.g., 5 bits). That is, UE 102 can consider the number of bits of the time domain resource allocation field to always be fixed (e.g., 5 bits). That is, the number of entries in the second resource allocation table can be fixed (e.g., 32 entries corresponding to 5 bits). For example, in the case where the number of entries in the second resource allocation is fixed (e.g., in the case where the number of bits of the time domain resource allocation field is fixed), one or more groups of second parameters can be predefined by the specification. Additionally, in the case where the number of entries in the second resource allocation is fixed (e.g., in the case where the number of bits of the time domain resource allocation field is fixed), gNB 160 can always configure a fixed number of groups of second parameters in PUSCH-TimeDomainResourceAllocationList2 (e.g., a fixed number (e.g., 32) of PUSCH-TimeDomainResourceAllocation2).

[0107] Here, one or more sets of second parameters (e.g., PUSCH-TimeDomainResourceAllocationList2) may be included in the third information (e.g., PUSCH-ConfigCommon). Additionally, one or more sets of second parameters (e.g., PUSCH-TimeDomainResourceAllocationList2) may be included in the fourth information (e.g., PUSCH-Config). For example, the first set of values of the second parameters may be included in the third information, and the second set of values of the second parameters may be included in the fourth information.

[0108] Also, in the case where the UE 102 detects a PDCCH of DCI format 0_2 in the common search space associated with CORESET 0, one or more sets of second parameters included in the third information may be used (e.g., applied to PUSCH transmission). Additionally, in the case where the UE 102 detects a PDCCH of DCI format 0_2 in the common search space not associated with CORESET 0, one or more sets of second parameters included in the fourth information may be used (e.g., applied to PUSCH transmission). Additionally, in the case where the UE 102 detects a PDCCH of DCI format 0_2 in the UE-specific search space, one or more sets of second parameters included in the fourth information may be used (e.g., applied to PUSCH transmission).

[0109] Furthermore, in the case where one or more sets of second parameters included in the third information and one or more sets of second parameters included in the fourth information are not configured, the default value of the second parameters (e.g., default time-domain resource allocation) may be used (e.g., applied to PUSCH transmission). Here, the default value of the second parameters may be predefined through the specifications and known information between the gNB 160 and the UE 102. For example, in the case where one or more sets of second parameters included in the third information and one or more sets of second parameters included in the fourth information are not configured, and in the case where the UE 102 detects a PDCCH of DCI format 0_2 (e.g., in the UE-specific search space, in the common search space associated with and / or not associated with CORESET 0), the default value of the second parameters may be used (e.g., applied to PUSCH transmission).

[0110] In yet another design, a new DCI format may not be introduced, but modifications and / or enhancements of the current DCI format may be used to schedule PUSCH for enhanced URLLC or other services in future releases. Reinterpretation of fields in the current DCI format (e.g., DCI format 0_0 or DCI format 0_1) may be applied to provide the necessary information to schedule PUSCH for enhanced URLLC or other services in future releases.

[0111] If reinterpreted as RRC-configured, explicitly or implicitly indicated, some bit fields or parts of bits in DCI format 0_0 (or DCI format 0_1) (e.g., frequency domain resource allocation, time domain resource allocation, hopping flag, modulation and coding scheme, new data indicator, redundancy version, HARQ process number, TPC command for PUSCH for scheduling, UL / SUL indicator, etc.) can be reinterpreted as different bit fields (e.g., antenna port, transmission configuration indicator, SRS request, carrier indicator, CSI request, β-offset indicator, SRS resource indicator, repetition factor, priority indicator, etc.).

[0112] For example, if multiple configurations are configured and DCI format 0_0 (or DCI format 0_1) is used to activate and / or deactivate one or more configurations, the bit field HARQ process number (or new data indicator, redundancy version) can be used to indicate the transmission configuration indicator and / or identifier.

[0113] If PUSCH priority is enabled, configured, and / or supported, the bit field HARQ process number (or new data indicator, redundancy version) in DCI format 0_0 or (DCI format 0_1) can be used to indicate the priority of the scheduled PUSCH.

[0114] Similarly, for the downlink, in order to support enhanced URLLC services and / or other services in future releases, new DCI formats and / or current DCI formats with modifications and / or enhancements can also be introduced. The DL DCI can use the same and / or common structure and / or design as the above UL DCI, or the DL DCI can be designed separately.

[0115] In the design, a new DL DCI format (e.g., DCI format 1_2, the specification may use a different name) can be introduced. DCI format 1_2 can be used for PDSCH scheduling in a cell. The following information can be transmitted through DCI format 1_2.

[0116] DCI format 1_2 can include an identifier of the DCI format. The value of this field can be set to a predefined and / or default value (e.g., 0 or 1), thereby indicating a new and / or different DCI format for enhanced URLLC and / or other services (compared with DCI format 1_0 and / or DCI format 1_1).

[0117] DCI format 1_2 can include an identifier of the UL / DL DCI format. The value of this field can be set to a predefined and / or default value indicating the DL DCI format (e.g., 0 or 1).

[0118] DCI format 1_2 may include antenna ports. The number of bits in the bit field may be 1-2 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by a set of antenna ports or the number of antenna ports. The number of bits in the bit field may be determined by the DMRS type, rank, codebook, and / or any other relevant higher layer parameter and / or table. Any one of the higher layer parameters used to determine the number of bits in the field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0119] DCI format 1_2 may include a transmission configuration indicator. The number of bits in the bit field may be 0-3 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the number of configured transmission configurations. For example, if multiple configurations are not enabled, the number of bits in the field is 0, or the bit field does not exist in the DCI. If the number of transmission configurations is 8, the number of bits in the field may be 3. If multiple transmission configurations are enabled and / or configured, only DCI format 1_2 may be used to activate and / or deactivate the corresponding configurations.

[0120] DCI format 1_2 may include an SRS request. The number of bits in the bit field may be 0-2 bits. The number of bits in the bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in the bit field may be determined by the configured carrier. The number of bits in the bit field may be determined by a configured and / or predefined table, and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in the field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters and / or tables configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters used to determine the number of bits in the corresponding bit field of DCI format 0_2 may be configured separately.

[0121] DCI format 1_2 may include carrier indication. The number of bits in this bit field may be 0 - 3 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the number of configured carriers. For example, if multiple carriers are not enabled and / or configured, the number of bits in this field is 0, or this bit field does not exist in the DCI. If the number of carriers is greater than 4, the number of bits in this field may be 3. Any of the higher layer parameters used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters and / or tables configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0122] DCI format 1_2 may include a repetition factor. The number of bits in this bit field may be 0 - 2 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by a configured and / or predefined set of repetition factors. For example, if dynamic indication of the repetition factor is not enabled, configured, and / or supported, the number of bits in this field is 0, or this bit field does not exist in the DCI. If dynamic indication of the repetition factor is enabled, configured, and / or supported, and / or the number of repetition factors in the configured and / or predefined set is 4 (e.g., {1, 2, 4, 8}), the number of bits in this field may be 2. Any of the higher layer parameters, sets, and / or tables used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters, tables, and / or sets configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters, tables, and / or sets used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0123] DCI format 1_2 may include a priority indication. The number of bits in this bit field may be 0 - 3 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by a configured and / or predefined set of priorities and / or the number of configured and / or predefined priorities. For example, if PDSCH priority is not enabled, configured, and / or supported, the number of bits in this field is 0, or this bit field does not exist in the DCI. If the number of configured and / or predefined PDSCH priorities is 4 (e.g., {1, 2, 4, 8}), the number of bits in this field may be 2. Any one of the higher layer parameters, sets, and / or tables used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or be configured separately for DCI format 1_2. In other words, the parameters, tables, and / or sets configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters, tables, and / or sets used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0124] DCI format 1_2 may include a rate matching indicator. The number of bits in this bit field may be 0 - 2 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by a configured set of rate matching patterns and / or any relevant higher layer parameter. Any one of the higher layer parameters, sets, and / or tables used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or be configured separately for DCI format 1_2. In other words, the parameters, tables, and / or sets configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters, tables, and / or sets used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0125] DCI format 1_2 may include a PRB bundling size indicator. The number of bits in this bit field may be 0 - 1 bit. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the configured PRB bundling type (e.g., whether PRB bundling is configured, and whether the PRB bundling type is configured as static or dynamic). If PRB bundling is not configured or is set to static, the number of bits in this field is 0, or this bit field does not exist in the DCI. Any one of the higher layer parameters, sets, and / or tables used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters, tables, and / or sets configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters, tables, and / or sets used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0126] DCI format 1_2 may include ZP CSI-RS triggering. The number of bits in this bit field may be 0 - 2 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the number of ZP CSI-RS resource sets configured in the higher layer parameter and / or any other relevant higher layer parameter. Any one of the higher layer parameters used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters configured for Rel-15 DCI format field size determination may also be used to determine the number of bits in the corresponding bit field of DCI format 1_2, or the parameters used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0127] DCI format 1_2 may include time domain resource allocation. The number of bits in this bit field may be 0 - 6 bits. The number of bits in this bit field may be determined by a higher layer (e.g., RRC configuration, explicit higher layer parameter). The number of bits in this bit field may be determined by the number of entries in the time domain resource allocation table configured by a higher layer (e.g., RRC configuration) or the default time domain resource allocation table. Any one of the higher layer parameters (e.g., the configured time domain resource allocation table, default and / or predefined time domain resource allocation table) used to determine the number of bits in this field may generally be configured for DCI format 1_2 and other DCI formats, or may be configured separately for DCI format 1_2. In other words, the parameters (e.g., the time domain resource allocation table configured by a higher layer) configured for Rel-15 DCI format field size determination may also be applied to the corresponding bit field of DCI format 1_2, or the parameters and / or tables used to determine the number of bits in the corresponding bit field of DCI format 1_2 may be configured separately.

[0128] For example, a first parameter (e.g., PDSCH-TimeDomainResourceAllocation) is used to configure the time-domain relationship between a PDCCH (e.g., DCI format 1_0, DCI format 1_1, and / or DCI format 1_2) and a PDSCH (e.g., PDSCH transmission). For example, the first parameter may include information indicating an offset (e.g., a slot offset) to be applied to the PDSCH transmission. Additionally, the first parameter may include information indicating an index that gives a valid combination of a starting symbol and a length to be applied to the PDSCH transmission (also referred to as a starting and length indicator (SLIV)). Additionally, the first parameter may include information indicating the PDSCH mapping type to be applied to the PDSCH transmission.

[0129] Here, the gNB 160 may transmit one or more sets of first parameters (e.g., PDSCH-TimeDomainResourceAllocationList) by using an RRC message. Also, the gNB 160 may indicate one set of first parameters from one or more sets of first parameters by using the value of a time-domain resource allocation field (e.g., the value "M"). That is, the gNB 160 may indicate which of the configured first parameters applied to the PDSCH transmission by the UE 102 by using the value of the time-domain resource allocation field.

[0130] That is, in the case where the UE 102 detects DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2, an offset (e.g., a slot offset), an index of a starting symbol and a length, and / or a PDSCH mapping type may be determined based on the value of the time-domain resource allocation field included in DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2. For example, the value of the time-domain resource allocation field (e.g., the value "m") may be used to indicate a row index of a first resource allocation table (e.g., the row index "m + 1"), and the first resource allocation table may be used to define one or more sets of first parameters (e.g., an offset (e.g., a slot offset), an index of a starting symbol and a length, and / or a PDSCH mapping type). That is, the index row of the first resource allocation table may be used to define one or more sets of first parameters (e.g., an offset (e.g., a slot offset), an index of a starting symbol and a length, and / or a PDSCH mapping type). Here, one or more sets of first parameters (e.g., an offset (e.g., a slot offset), an index of a starting symbol and a length, and / or a PDSCH mapping type) may be applied to a PDSCH transmission scheduled by using DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2.

[0131] In addition, the number of bits (e.g., size and / or bit width) of a time domain resource allocation field (e.g., a DCI field) may be determined based on the number of entries in a first resource allocation table (i.e., the number of entries in PDSCH-TimeDomainResourceAllocationList). For example, the maximum number of the first allocation table (i.e., the maximum number of the first parameter (i.e., PDSCH-TimeDomainResourceAllocation) in PDSCH-TimeDomainResourceAllocationList) may be a first value (e.g., 16). That is, the maximum number of bits of the time domain resource allocation field included in DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 may be 4 bits (i.e., corresponding to the first value). For example, in the case where 5 groups of the first parameters (i.e., 5 entries of the first resource allocation table) are configured, UE 102 may consider the number of bits of the time domain resource allocation field included in DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 to be 3 bits. In addition, for example, in the case where 14 groups of the first parameters (i.e., 14 entries of the first resource allocation table) are configured, UE 102 may consider the number of bits of the time domain resource allocation field included in DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 to be 4 bits.

[0132] Here, one or more groups of the first parameters (e.g., PDSCH-TimeDomainResourceAllocationList) may be included in the third information (e.g., PDSCH-ConfigCommon). For example, the third information may be used to configure cell-specific PDSCH parameters. For example, the system information (e.g., system information block 1) may include the third information. In addition, one or more groups of the first parameters (e.g., PDSCH-TimeDomainResourceAllocationList) may be included in the fourth information (e.g., PDSCH-Config). For example, the fourth information may be used to configure UE-specific parameters. For example, a dedicated RRC message may include the fourth information. For example, the first set of values of the first parameter may be included in the third information, and the second set of values of the first parameter may be included in the fourth information.

[0133] Also, in the case where the UE 102 detects a PDCCH of DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 in a common search space (e.g., a set of common search spaces) associated with CORESET 0, one or more sets of first parameters included in the third information can be used (e.g., applied to PDSCH transmission). Additionally, in the case where the UE 102 detects a PDCCH of DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 in a common search space (e.g., a set of common search spaces) not associated with CORESET 0, one or more sets of first parameters included in the fourth information can be used (e.g., applied to PDSCH transmission). Additionally, in the case where the UE 102 detects a PDCCH of DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 in a UE-specific search space (e.g., a set of UE-specific search spaces), one or more sets of first parameters included in the fourth information can be used (e.g., applied to PDSCH transmission).

[0134] Additionally, in the case where one or more sets of first parameters included in the third information and one or more sets of first parameters included in the fourth information are not configured, a default value of the first parameter (e.g., default time-domain resource allocation) can be used (e.g., applied to PDSCH transmission). Here, the default value of the first parameter can be predefined in advance through the specifications and known information between the gNB 160 and the UE 102. For example, in the case where one or more sets of first parameters included in the third information and one or more sets of second parameters included in the fourth information are not configured, and in the case where the UE 102 (e.g., in a UE-specific search space, in a common search space associated with and / or not associated with CORESET 0) detects a PDCCH for DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2, a default value of the first parameter can be used (e.g., applied to PDSCH transmission).

[0135] Additionally, a second parameter (e.g., PDSCH-TimeDomainResourceAllocation2) is used to configure the time-domain relationship between a PDCCH (e.g., DCI format 0_2) and a PDSCH (e.g., PDSCH transmission). For example, the second parameter can include information indicating an offset (e.g., slot offset and / or symbol offset) to be applied to PDSCH transmission. Additionally, the second parameter can include information indicating an index that gives a valid combination of a starting symbol and a length to be applied to PDSCH transmission (also referred to as a starting and length indicator (SLIV)). Additionally, the second parameter can include information indicating the PDSCH mapping type to be applied to PDSCH transmission.

[0136] Here, the gNB 160 may transmit one or more sets of second parameters (e.g., PDSCH-TimeDomainResourceAllocationList2) by using an RRC message. Also, the gNB 160 may indicate one set of first parameters from one or more sets of first parameters by using the value of the time domain resource allocation field (e.g., the value "M"). That is, the gNB 160 may indicate which of the configured first parameters applied by the UE 102 to PDSCH transmission by using the value of the time domain resource allocation field.

[0137] That is, when the UE 102 detects DCI format 1_2, the offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PDSCH mapping type may be determined based on the value of the time domain resource allocation field included in DCI format 1_2. For example, the value of the time domain resource allocation field (e.g., the value "m") may be used to indicate the row index of the second resource allocation table (e.g., the row index "m + 1"), and the second resource allocation table may be used to define one or more sets of second parameters (e.g., the offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PDSCH mapping type). That is, the index row of the second resource allocation table may be used to define one or more sets of second parameters (e.g., the offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PDSCH mapping type). Here, one or more sets of second parameters (e.g., the offset (e.g., slot offset and / or symbol offset), the index of the starting symbol and the length, and / or the PDSCH mapping type) may be applied to the PDSCH transmission scheduled by using DCI format 1_2.

[0138] In addition, the number of bits (e.g., size and / or bit width) of the time domain resource allocation field (e.g., DCI field) can be determined based on the number of entries in the second resource allocation table (i.e., the number of entries in PDSCH-TimeDomainResourceAllocationList2). For example, the maximum number of the second allocation table (i.e., the maximum number of the second parameter (i.e., PDSCH-TimeDomainResourceAllocation2) in PDSCH-TimeDomainResourceAllocationList2) can be a second value (e.g., 64). That is, the maximum number of bits of the time domain resource allocation field included in DCI format 1_2 can be 6 bits (i.e., corresponding to the first value). For example, in the case where 5 groups of second parameters (i.e., 5 entries of the second resource allocation table) are configured, UE 102 can consider the number of bits of the time domain resource allocation field included in DCI format 1_2 to be 3 bits. In addition, for example, in the case where 50 groups of second parameters (i.e., 50 entries of the second resource allocation table) are configured, UE 102 can consider the number of bits of the time domain resource allocation field included in DCI format 1_2 to be 6 bits.

[0139] Here, the number of bits of the time domain resource allocation field can be fixed (e.g., 5 bits). That is, UE 102 can consider the number of bits of the time domain resource allocation field to be always fixed (e.g., 5 bits). That is, the number of entries in the second resource allocation table can be fixed (e.g., 32 entries corresponding to 5 bits). For example, in the case where the number of entries in the second resource allocation is fixed (e.g., in the case where the number of bits of the time domain resource allocation field is fixed), one or more groups of second parameters can be predefined by the specification. In addition, in the case where the number of entries in the second resource allocation is fixed (e.g., in the case where the number of bits of the time domain resource allocation field is fixed), gNB 160 can always configure a fixed number of groups of second parameters in PDSCH-TimeDomainResourceAllocationList2 (e.g., a fixed number (e.g., 32) of PDSCH-TimeDomainResourceAllocation2).

[0140] Here, one or more sets of second parameters (e.g., PDSCH-TimeDomainResourceAllocationList2) may be included in the third information (e.g., PDSCH-ConfigCommon). Additionally, one or more sets of second parameters (e.g., PDSCH-TimeDomainResourceAllocationList2) may be included in the fourth information (e.g., PDSCH-Config). For example, the first set of values of the second parameters may be included in the third information, and the second set of values of the second parameters may be included in the fourth information.

[0141] Also, in the case where the UE 102 detects a PDCCH of DCI format 1_2 in the common search space associated with CORESET 0, one or more sets of second parameters included in the third information may be used (e.g., applied to PDSCH transmission). Additionally, in the case where the UE 102 detects a PDCCH of DCI format 1_2 in the common search space not associated with CORESET 0, one or more sets of second parameters included in the fourth information may be used (e.g., applied to PDSCH transmission). Additionally, in the case where the UE 102 detects a PDCCH of DCI format 1_2 in the UE-specific search space, one or more sets of second parameters included in the fourth information may be used (e.g., applied to PDSCH transmission).

[0142] Furthermore, in the case where one or more sets of second parameters included in the third information and one or more sets of second parameters included in the fourth information are not configured, the default value of the second parameters (e.g., default time-domain resource allocation) may be used (e.g., applied to PDSCH transmission). Here, the default value of the second parameters may be predefined in advance through the specifications and known information between the gNB 160 and the UE 102. For example, in the case where one or more sets of second parameters included in the third information and one or more sets of second parameters included in the fourth information are not configured, and in the case where the UE 102 detects a PDCCH of DCI format 1_2 (e.g., in the UE-specific search space, in the common search space associated with and / or not associated with CORESET 0), the default value of the second parameters may be used (e.g., applied to PDSCH transmission).

[0143] In yet another design, no new DL DCI format may be introduced, but modifications and / or enhancements to the current DCI format may be required to schedule the PDSCH for enhanced URLLC or other services in future releases. Reinterpretation of the fields in the current DCI format (e.g., DCI format 1_0 or DCI format 1_1) may be applied to provide the necessary information to schedule the PDSCH for enhanced URLLC or other services in future releases.

[0144] If reinterpreted as RRC-configured, explicitly or implicitly indicated, some bit fields or parts of bits in DCI format 1_0 (or DCI format 1_1) (e.g., frequency domain resource allocation, time domain resource allocation, VRB-to-PRB mapping, modulation and coding scheme, new data indicator, redundancy version, HARQ process number, downlink allocation index, TPC command for PUCCH used for scheduling, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator, etc.) can be reinterpreted as different bit fields (e.g., antenna port, transmission configuration indicator, PRB bundling size indicator, carrier indicator, rate matching indicator, ZP CSI-RS trigger, SRS request, repetition factor, priority indicator, etc.).

[0145] For example, if multiple configurations are configured and DCI format 1_0 or (DCI format 1_1) is used to activate and / or deactivate one or more configurations, the bit field HARQ process number (or new data indicator, redundancy version) can be used to indicate the transmission configuration indicator / identifier.

[0146] If PDSCH priority is enabled, configured, and / or supported, the bit field HARQ process number (or new data indicator, redundancy version) in DCI format 1_0 or (DCI format 1_1) can be used to indicate the priority of the scheduled PDSCH.

[0147] New DCI formats and / or enhanced / modified DCI formats for enhanced URLLC services and / or other services in future releases are referred to herein as URLLC DCI formats. Methods for differentiating URLLC DCI formats from Rel-15 DCI formats are described herein. A new RNTI can be used to scramble the CRC of the URLLC DCI format. If parameters for the URLLC DCI format are configured and / or the URLLC DCI format size is configured, UE 102 can monitor the URLLC DCI format using the CRC scrambled by the new RNTI. In yet another design, an explicit DCI field can be used for differentiation (e.g., if a parameter for the DCI format size is configured, UE 102 monitors the URLLC DCI format including 1-bit information (i.e., UE 102 assumes the presence of 1-bit information in the URLLC DCI format). In yet another design, the URLLC DCI format and the Rel-15 DCI format can be monitored in different search spaces.

[0148] The parameters for configuring the DCI format size can be configured per serving cell, per DL BWP, per CORESET, and / or per search space. For example, if the parameter is configured for the first DL BWP, UE 102 monitors the configurable DCI formats of the PDCCH on the first DL BWP (i.e., if the parameter is not configured for the second DL BWP, UE 102 does not monitor the configurable DCI formats of the PDCCH on the second DL BWP). If the parameter is configured for the first search space, UE 102 monitors the configurable DCI formats of the PDCCH in the first search space (i.e., if the parameter is not configured for the second search space, the UE does not monitor the configurable DCI formats of the PDCCH on the second search space).

[0149] For the configuration of the DCI format size, generally only one parameter can be used to configure the sizes of all configurable fields. In another example, the total DCI format size can be configured. The presence and / or the size of each field in the DCI format can be derived / determined based on the configured total DCI format size. In another example, separate parameters can be used to configure the sizes of each configurable field.

[0150] Generally, only one parameter can be used to configure the DL DCI format size and the UL DCI format size, or generally only one parameter can be used to configure the sizes of specific DCI fields in the DL DCI format and the UL DCI format. In another example, separate parameters are used to configure the size of the DL DCI format and the UL DCI format, or separate parameters are used to configure the sizes of each specific DCI field in the DL DCI format and the UL DCI format respectively.

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

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

[0153] The UE operation module 124 can provide the information 136 to the decoder 108. For example, the UE operation module 124 can notify the decoder 108 of the coding expected for the transmission from the gNB 160.

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

[0155] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operation module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or error correction coding, mapping the data to spatial, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to the modulator 154.

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

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

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

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

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

[0161] Generally, the gNB operation module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operation module 182 may include a gNB scheduling module 194. The gNB scheduling module 194 may perform operations of configurable downlink control information (DCI) formats as described herein.

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

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

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

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

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

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

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

[0169] It should also be noted that one or more of the elements or their components included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or their components may be implemented as chips, circuits, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or executed using hardware. For example, one or more of the methods described herein may be implemented in a chipset, application-specific integrated circuit (ASIC), large-scale integration (LSI), or integrated circuit, etc., and / or implemented using a chipset, application-specific integrated circuit (ASIC), large-scale integration (LSI), or integrated circuit, etc.

[0170] URLLC can coexist with other services (e.g., eMBB). Due to latency requirements, in some methods, URLLC may have the highest priority. Some examples of URLLC coexisting with other services are given herein (e.g., in one or more of the following figure descriptions).

[0171] Figure 2 is a diagram showing an example of a resource grid for the downlink. Figure 2 The shown resource grid can be used in some specific implementations of the systems and methods disclosed herein. More details about the resource grid are given in conjunction with Figure 1 More details about the resource grid are given.

[0172] In Figure 2 a downlink subframe 269 may include two downlink time slots 283. N DL RB is the downlink bandwidth configuration for the serving cell, represented as a multiple of N RB sc where N RB sc is the size of a resource block 289 in the frequency domain, represented as the number of subcarriers, and N DL symb is the number of OFDM symbols 287 in the downlink time slot 283. A resource block 289 may include multiple resource elements (REs) 291.

[0173] For the PCell, N DL RB is broadcast as part of the system information. For the SCell (including the licensed-assisted access (LAA) SCell), N DL RB is configured through an RRC message dedicated to the UE 102. For PDSCH mapping, the available REs 291 may be the REs 291 whose index l satisfies l ≧ l 数据，开始 and / or l 数据，结束 ≧ l.

[0174] In the downlink, an OFDM access scheme with a cyclic prefix (CP) can be adopted, which can also be referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH, etc. can be transmitted. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs), which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair includes two downlink RBs that are consecutive in the time domain.

[0175] A downlink RB includes twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is uniquely identified by the index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and time domain respectively. Although the downlink subframe in one component carrier (CC) is discussed herein, the downlink subframe is defined for each CC and the downlink subframes are substantially synchronized with each other among the CCs.

[0176] Figure 3 is a diagram illustrating an example of a resource grid for the uplink. Figure 3 The resource grid shown can be used in some specific implementations of the systems and methods disclosed herein. In conjunction with Figure 1 more details about the resource grid are given.

[0177] In Figure 3 an uplink subframe 369 may include two uplink time slots 383. N UL RB is the uplink bandwidth configuration for the serving cell, expressed as a multiple of N RB sc where N RB sc is the size of the resource block 389 in the frequency domain, expressed as the number of subcarriers, and N UL symb is the number of SC-FDMA symbols 393 in the uplink time slot 383. The resource block 389 may include a plurality of resource elements (REs) 391.

[0178] For the PCell, N UL RB is broadcast as part of the system information. For the SCell (including the LAA SCell), N UL RB is configured through an RRC message dedicated to the UE 102.

[0179] In the uplink, in addition to CP-OFDM, a single-carrier frequency-division multiple access (SC-FDMA) access scheme may also be employed, which is also referred to as discrete Fourier transform spread OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH, etc. may be transmitted. The uplink radio frame may include multiple pairs of uplink resource blocks. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair includes two uplink RBs that are consecutive in the time domain.

[0180] An uplink RB may include twelve sub - carriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM and / or DFT - S - OFDM symbols in the time domain. The region defined by one sub - carrier in the frequency domain and one OFDM and / or DFT - S - OFDM symbol in the time domain is called a RE and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and time domain respectively. Although the uplink sub - frame in one component carrier (CC) is discussed herein, the uplink sub - frame is defined for each CC.

[0181] Figure 4 An example of several parameters 401 is shown. Parameter #1 401a may be a basic parameter (e.g., a reference parameter). For example, the RE 495a of the basic parameter 401a may be defined to have a sub - carrier spacing 405a of 15 kHz in the frequency domain and a length of 2048Ts + CP (e.g., 160Ts or 144Ts) in the time domain (i.e., symbol length #1 403a), where Ts represents the base - band sampling time unit defined as 1 / (15000*2048) seconds. For the i - th parameter, the sub - carrier spacing 405 may be equal to 15*2 i and the effective OFDM symbol length 2048*2 -i *Ts. This may result in a symbol length of 2048*2 -i *Ts + CP length (e.g., 160*2 -i *Ts or 144*2 -i *Ts). In other words, the sub - carrier spacing of the i + 1 - th parameter is twice that of the i - th parameter, and the symbol length of the i + 1 - th parameter is half that of the i - th parameter. Figure 4 Four parameters are shown, but the system may support another number of parameters. In addition, the system does not have to support all of the 0 - th parameter to the I - th parameter (i = 0, 1,..., I).

[0182] For example, the first UL transmission on the first SPS resource as described above may be performed only on parameter #1 (e.g., with a sub - carrier spacing of 15 kHz). Here, the UE 102 may obtain (detect) parameter #1 based on the synchronization signal. In addition, the UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) configuring parameter #1. The dedicated RRC signal may be a UE - specific signal. Here, the first UL transmission on the first SPS resource may be performed on parameter #1, parameter #2 (sub - carrier spacing of 30 kHz), and / or parameter #3 (sub - carrier spacing of 60 kHz).

[0183] In addition, the second UL transmission on the second SPS resource as described above may be performed only on Parameter #3. Here, for example, UE 102 may receive system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB)) including information on Configuration Parameter #2 and / or Parameter #3.

[0184] In addition, UE 102 may receive a dedicated RRC signal including information on Configuration Parameter #2 and / or Parameter #3 (e.g., handover command). System information (e.g., MIB) may be transmitted on the BCH (Broadcast Channel) and / or the dedicated RRC signal. System information (e.g., SIB) may contain information on when to evaluate whether UE 102 is allowed to access the cell and / or information when defining the scheduling of other system information. The system information (SIB) may contain radio resource configuration information shared by multiple UEs 102. That is, the dedicated RRC signal may include each of multiple parameter configurations (first parameter, second parameter, and / or third parameter) for each UL transmission (e.g., each UL-SCH transmission, each PUSCH transmission). In addition, the dedicated RRC signal may include each of multiple parameter configurations (first parameter, second parameter, and / or third parameter) for each DL transmission (e.g., each PDCCH transmission).

[0185] Figure 5 shows Figure 4 An example of the subframe structure of Parameter 501 shown in. Considering that Slot 283 includes N DL Symb (or N UL Symb ) = 7 symbols, the slot length of the (i + 1)-th Parameter 501 is half of the slot length of the i-th Parameter 501, and the number of Slot 283 in a subframe (e.g., 1 ms) will eventually double. It should be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

[0186] Figure 6 An example of Slot 683 and Subslot 607 is shown. If Subslot 607 is not configured by a higher layer, UE 102 and eNB and / or gNB 160 may use only Slot 683 as a scheduling unit. More specifically, a given transport block may be assigned to Slot 683. If Subslot 607 is configured by a higher layer, UE 102 and eNB and / or gNB 160 may use Subslot 607 as well as Slot 683. Subslot 607 may include one or more OFDM symbols. The maximum number of OFDM symbols constituting Subslot 607 may be N DL symb -1 (or N UL symb -1).

[0187] The sub - slot length can be configured by higher - layer signaling. Alternatively, the sub - slot length can be indicated by a physical - layer control channel (e.g., via a DCI format).

[0188] The sub - slot 607 can start from any symbol within the slot 683, unless it conflicts with a control channel. Based on the restrictions on the starting position, there may be restrictions on the micro - slot length. For example, a sub - slot 607 of length N DL symb - 1 (or N UL symb - 1) can start from the second symbol in the slot 683. The starting position of the sub - slot 607 can be indicated by a physical - layer control channel (e.g., via a DCI format). Alternatively, the starting position of the sub - slot 607 can be derived from the information of the physical - layer control channel that schedules the data in the sub - slot 607 (e.g., search - space index, blind - decoding candidate index, frequency and / or time - resource index, PRB index, control - channel - element index, control - channel - element aggregation level, antenna - port index, etc.).

[0189] In the case of configuring the sub - slot 607, a given transport block can be allocated to the slot 683, the sub - slot 607, the aggregated sub - slots 607, or the aggregated sub - slots 607 and the slot 683. This unit can also be a unit for HARQ - ACK bit generation.

[0190] Figure 7 An example of a scheduling timeline 709 is shown. For a normal DL scheduling timeline 709a, the DL control channel is mapped to the initial part of the slot 783a. The DL control channel 711 schedules the DL shared channel 713a in the same slot 783a. The HARQ - ACK for the DL shared channel 713a (i.e., each HARQ - ACK indicating whether the transport block in each DL shared channel 713a is successfully detected) is reported via the UL control channel 715a in the subsequent slot 783b. In this case, a given slot 783 can contain either a DL transmission or a UL transmission.

[0191] For a normal UL scheduling timeline 709b, the DL control channel 711b is mapped to the initial part of the slot 783c. The DL control channel 711b schedules the UL shared channel 717a in the subsequent slot 783d. For these cases, the associated timing (time offset) between the DL slot 783c and the UL slot 783d can be fixed or configured by higher - layer signaling. Alternatively, it can be indicated by a physical - layer control channel (e.g., a DL - allocation DCI format, a UL - grant DCI format, or another DCI format, such as a UE - common - signaling DCI format that can be monitored in a common search space).

[0192] For the self - contained base DL scheduling timeline 709c, the DL control channel 711c is mapped to the initial part of the time slot 783e. The DL control channel 711c schedules the DL shared channel 713b in the same time slot 783e. The HARQ - ACK for the DL shared channel 713b is reported in the UL control channel 715b, which is mapped to the end part of the time slot 783e.

[0193] For the self - contained base UL scheduling timeline 709d, the DL control channel 711d is mapped to the initial part of the time slot 783f. The DL control channel 711d schedules the UL shared channel 717b in the same time slot 783f. For these cases, the time slot 783f may include a DL part and a UL part, and there may be a guard period between the DL transmission and the UL transmission.

[0194] The use of self - contained time slots may be based on the configuration of self - contained time slots. Alternatively, the use of self - contained time slots may be based on the configuration of sub - time slots. Still alternatively, the use of self - contained time slots may be based on the configuration of shortened physical channels (e.g., PDSCH, PUSCH, PUCCH, etc.).

[0195] Figure 8 An example of a DL control channel monitoring area is shown. One or more groups of PRBs may be configured for DL control channel monitoring. In other words, a control resource set is a group of PRBs in the frequency domain, within which the UE 102 attempts to blindly decode downlink control information, where the PRBs may or may not be frequency - continuous, the UE 102 may have one or more control resource sets, and one DCI message may be located in one control resource set. In the frequency domain, a PRB is the resource unit size for a control channel (which may or may not include a demodulation reference signal (DMRS)). The DL shared channel may start at an OFDM symbol later than the symbol carrying the detected DL control channel. Alternatively, the DL shared channel may start at the last OFDM symbol carrying the detected DL control channel (or at a symbol earlier than the last OFDM symbol). In other words, at least dynamic reuse of at least a part of the resources in the control resource set for data of the same or different UEs 102 is supported at least in the frequency domain.

[0196] Figure 9 An example of a DL control channel including more than one control channel element is shown. When a control resource set spans multiple OFDM symbols, a control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element may be mapped to a RE defined by a single PRB and a single OFDM symbol. If more than one DL control channel element is used for a single DL control channel transmission, DL control channel element aggregation may be performed.

[0197] The number of aggregated DL control channel elements is referred to as the DL control channel element aggregation level. The DL control channel element aggregation level can be 1 or a power of 2 up to an integer. gNB 160 may notify UE 102 which control channel candidates are mapped to each subset of OFDM symbols in the control resource set. If a DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, DL control channel element aggregation is performed within one OFDM symbol, i.e., multiple DL control channel elements are aggregated within one OFDM symbol. Otherwise, DL control channel elements may be aggregated in different OFDM symbols.

[0198] Figure 10 An example of the UL control channel structure is shown. The UL control channel may be mapped on the REs defined by PRBs and time slots in the frequency domain and time domain, respectively. This UL control channel may be referred to as the long format (or simply the first format). The UL control channel may be mapped on the REs on a limited number of OFDM symbols in the time domain. This may be referred to as the short format (or simply the second format). The UL control channel with the short format may be mapped on the REs within a single PRB. Alternatively, the UL control channel with the short format may be mapped on the REs within multiple PRBs. For example, an interleaved mapping may be applied, i.e., the UL control channel may be mapped to every Nth PRB (e.g., 5 or 10) within the system bandwidth.

[0199] Figure 11 FIG. is a block diagram showing a specific implementation of gNB 1160. gNB 1160 may include a high-layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

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

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

[0202] Figure 12 is a block diagram showing a specific implementation of the UE 1202. The UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0203] The higher layer processor 1223 can manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide higher layer parameters to the physical layer. The higher layer processor 1223 can obtain the transport block from the physical layer. The higher layer processor 1223 can send and / or obtain higher layer messages such as RRC messages and MAC messages to and / or from the higher layer of the gNB. The higher layer processor 1223 can provide the transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

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

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

[0206] Figure 13 shows various components that can be utilized in the UE 1302. In combination with Figure 13 The UE 1302 described in combination with Figure 1Implemented by the described UE 102. The UE 1302 includes a processor 1303 that controls the operation of the UE 1302. The processor 1303 may also be referred to as a central processing unit (CPU). A memory 1305 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store information) provides instructions 1307a and data 1309a to the processor 1303. A portion of the memory 1305 may also include non-volatile random access memory (NVRAM). Instructions 1307b and data 1309b may also reside in the processor 1303. The instructions 1307b and / or data 1309b loaded into the processor 1303 may also include instructions 1307a and / or data 1309a from the memory 1305, which are loaded for the processor 1303 to execute or process. The instructions 1307b may be executed by the processor 1303 to implement the above-described method.

[0207] The UE 1302 may also include a housing that houses one or more transmitters 1358 and one or more receivers 1320 to allow for the transmission and reception of data. The transmitter 1358 and the receiver 1320 may be combined into one or more transceivers 1318. One or more antennas 1322a-n are attached to the housing and electrically coupled to the transceivers 1318.

[0208] The various components of the UE 1302 are coupled together by a bus system 1311 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for clarity, the various buses are shown as the bus system 1311 in Figure 13 The UE 1302 may also include a digital signal processor (DSP) 1313 for processing signals. The UE 1302 may also include a communication interface 1315 that provides a user with access to the functions of the UE 1302. Figure 13 The illustrated UE 1302 is a functional block diagram rather than a list of specific components.

[0209] Figure 14 Shows the various components that can be utilized in the gNB 1460. The gNB 1460 described in conjunction with Figure 14 May be in accordance with that described in conjunction with Figure 1Implemented by the described gNB 160. gNB 1460 includes a processor 1403 that controls the operation of gNB 1460. The processor 1403 may also be referred to as a central processing unit (CPU). A memory 1405 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store information) provides instructions 1407a and data 1409a to the processor 1403. A portion of the memory 1405 may also include non-volatile random access memory (NVRAM). Instructions 1407b and data 1409b may also reside in the processor 1403. The instructions 1407b and / or data 1409b loaded into the processor 1403 may also include instructions 1407a and / or data 1409a from the memory 1405, which are loaded for the processor 1403 to execute or process. The instructions 1407b may be executed by the processor 1403 to implement the above-described method.

[0210] gNB 1460 may also include a housing that houses one or more transmitters 1417 and one or more receivers 1478 to allow for the transmission and reception of data. The transmitter 1417 and the receiver 1478 may be combined into one or more transceivers 1476. One or more antennas 1480a-n are attached to the housing and electrically coupled to the transceivers 1476.

[0211] The various components of gNB 1460 are coupled together by a bus system 1411 (in addition to the data bus, the bus system may also include a power bus, a control signal bus, and a status signal bus). However, for clarity, the various buses are shown as the bus system 1411 in Figure 14 gNB 1460 may also include a digital signal processor (DSP) 1413 for processing signals. gNB 1460 may also include a communication interface 1415 that provides the function of allowing users to access gNB 1460. Figure 14 The gNB1460 shown is a functional block diagram rather than a list of specific components.

[0212] Figure 15 is a block diagram showing an implementation of a UE 1502 in which the systems and methods described herein may be implemented. The UE 1502 includes a transmitting device 1558, a receiving device 1520, and a control device 1524. The transmitting device 1558, the receiving device 1520, and the control device 1524 may be configured to perform one or more of the functions described above Figure 1 above. Figure 13 Shows Figure 15 an example of the specific device structure of Figure 1 One or more of the functions of. For example, the DSP may be implemented by software.

[0213] Figure 16 is a block diagram showing an embodiment of gNB 1660 in which the systems and methods described herein may be implemented. gNB 1660 includes a transmitting device 1623, a receiving device 1678, and a control device 1682. The transmitting device 1623, the receiving device 1678, and the control device 1682 may be configured to perform one or more of the functions described above Figure 1 above Figure 14 shows Figure 16 an example of the specific device structure of. Various other structures may be implemented to achieve Figure 1 one or more of the functions of. For example, the DSP may be implemented by software.

[0214] Figure 17 is a flowchart showing a method 1700 performed by a user equipment (UE) 102. The UE 102 may monitor 1702 an uplink (UL) downlink control information (DCI) format, the uplink DCI format including first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH). The first information of the UL DCI format may include at least one of the following: antenna port information, transmission configuration indication, sounding reference signal (SRS) request, carrier indication, channel state information (CSI) request, beta_offset indicator, SRS resource indicator, repetition factor, priority indicator, or time-domain resource allocation.

[0215] The UE 102 may monitor 1704 a downlink (DL) DCI format, the downlink DCI format including second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH). The second information of the DL DCI format may include at least one of the following: antenna port information, transmission configuration indication, SRS request, carrier indication, repetition factor, priority indication, rate matching indicator, physical resource block (PRB) bundling size indicator, zero-power (ZP) channel state information reference signal (CSI-RS) trigger, or time-domain resource allocation.

[0216] In one method, the UL DCI format and the DL DCI format may be new DCI formats. In another method, the first information of the UL DCI format and the second information of the DL DCI format modify the 3GPP Release-15 DCI format. The fields in the 3GPP Release-15 DCI format may be reinterpreted to determine the first information and the second information.

[0217] Figure 18FIG. 1800 is a flowchart showing a method 1800 performed by a base station (gNB) 160. The gNB 160 may generate 1802 an uplink (UL) downlink control information (DCI) format that includes first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH). The gNB 160 may generate 1804 a downlink (DL) DCI format that includes second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

[0218] The term “computer-readable medium” refers to any available medium that can be accessed by a computer or a processor. The term “computer-readable medium,” as used herein, may denote a computer- and / or processor-readable medium that is non-transitory and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu- A disc is where disks usually reproduce data magnetically, while a disc reproduces data optically with lasers.

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

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

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

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

[0223] In addition, when the program is commercially available, the program stored on a portable recording medium can be distributed, or the program can be transmitted to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. Further, some or all of the gNB 160 and the UE 102 according to the above-described system and method can be implemented as an LSI which is a typical integrated circuit. Each functional block of the gNB 160 and the UE 102 can be individually built into a chip, and some or all of the functional blocks can be integrated into a chip. Further, the technology of the integrated circuit is not limited to the LSI, and the integrated circuit for the functional block can be implemented using a dedicated circuit or a general-purpose processor. Further, if an integrated circuit technology alternative to the LSI appears with the continuous progress of semiconductor technology, the integrated circuit applying that technology can also be used.

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

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

[0226] <Summary of the Invention>

[0227] In one example, a user equipment (UE) includes: a higher layer processor configured to monitor an uplink (UL) downlink control information (DCI) format, the UL DCI format including first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH); and the higher layer processor is configured to monitor a downlink (DL) DCI format, the DL DCI format including second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

[0228] In one example, for the UE, the first information of the UL DCI format includes at least one of antenna port information, transmission configuration indication, sounding reference signal (SRS) request, carrier indication, channel state information (CSI) request, beta_offset indicator, SRS resource indicator, repetition factor, priority indication, or time domain resource allocation.

[0229] In one example, for the UE, the second information of the DL DCI format includes antenna port information, transmission configuration indication, SRS request, carrier indication, repetition factor, priority indication, rate matching indicator, physical resource block (PRB) bundling size indicator, zero power (ZP) channel state information reference signal (CSI-RS) trigger, or time domain resource allocation.

[0230] In one example, for the UE, the UL DCI format and the DL DCI format are new DCI formats.

[0231] In one example, for the UE, the first information of the UL DCI format and the second information of the DL DCI format modify the 3GPP Release-15 DCI format.

[0232] In one example, for the UE, fields in the 3GPP Release-15 DCI format can be reinterpreted to determine the first information and the second information.

[0233] In one example, a base station (gNB) includes: a high-layer processor configured to generate an uplink (UL) downlink control information (DCI) format, the uplink DCI format including first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH); and the high-layer processor is configured to generate a downlink (DL) DCI format, the downlink DCI format including second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

[0234] In one example, for the gNB, the first information of the UL DCI format includes at least one of antenna port information, transmission configuration indication, sounding reference signal (SRS) request, carrier indication, channel state information (CSI) request, beta_offset indicator, SRS resource indicator, repetition factor, priority indication, or time-domain resource allocation.

[0235] In one example, for the gNB, the second information of the DL DCI format includes antenna port information, transmission configuration indication, SRS request, carrier indication, repetition factor, priority indication, rate matching indicator, physical resource block (PRB) bundling size indicator, zero-power (ZP) channel state information reference signal (CSI-RS) trigger, or time-domain resource allocation.

[0236] In one example, for the gNB, the first information of the UL DCI format and the second information of the DL DCI format are new DCI formats.

[0237] In one example, for the gNB, the first information of the UL DCI format and the second information of the DL DCI format modify the 3GPP Release-15 DCI format.

[0238] In one example, for the gNB, fields in the 3GPP Release-15 DCI format can be reinterpreted to determine the first information and the second information.

[0239] In one example, a method performed by a user equipment (UE) includes: monitoring an uplink (UL) downlink control information (DCI) format, the uplink DCI format including first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH); and monitoring a downlink (DL) DCI format, the downlink DCI format including second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

[0240] In one example, a method performed by a base station (gNB) includes: generating an uplink (UL) downlink control information (DCI) format, where the uplink DCI format includes first information for scheduling enhanced ultra-reliable low-latency communication (URLLC) services on a physical uplink shared channel (PUSCH); and generating a downlink (DL) DCI format, where the downlink DCI format includes second information for scheduling enhanced URLLC services on a physical downlink shared channel (PDSCH).

[0241] In one example, a user equipment (UE) includes: a receiving circuit configured to receive a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, where the first information includes a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time-domain allocation, the receiving circuit being configured to receive an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, where the second information includes a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time-domain allocation; a transmitting circuit configured to perform the first PUSCH transmission based on detecting the first DCI format according to the first information, the transmitting circuit being configured to perform the second PUSCH transmission based on detecting the second DCI format according to the second information, where the first DCI format and the second DCI format are monitored in different search spaces.

[0242] A base station apparatus, comprising: a transmission circuit configured to transmit a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation, the transmission circuit being configured to transmit an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; a receiving circuit configured to receive the first PUSCH transmission based on the first information according to the transmission of the first DCI format, the receiving circuit being configured to receive the second PUSCH transmission based on the second information according to the transmission of the second DCI format, wherein the first DCI format and the second DCI format are monitored in different search spaces.

[0243] In one example, a communication method of a user equipment (UE) includes: receiving a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation; receiving an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; transmitting the first PUSCH transmission based on the first information according to the detection of the first DCI format; transmitting the second PUSCH transmission based on the second information according to the detection of the second DCI format, wherein the first DCI format and the second DCI format are monitored in different search spaces.

[0244] In one example, a communication method of a base station device includes: transmitting a radio resource control (RRC) message including first information for a first physical uplink shared channel (PUSCH) transmission scheduled by a first downlink control information (DCI) format, the first information including a first parameter for defining an antenna port, a second parameter for defining a carrier, a third parameter for defining a priority, and a first allocation table for defining a time domain allocation; transmitting an RRC message including second information for a second PUSCH transmission scheduled by a second DCI format, the second information including a fourth parameter for defining an antenna port, a fifth parameter for defining a carrier, a sixth parameter for defining a priority, and a second allocation table for defining a time domain allocation; receiving a first PUSCH transmission according to the first information based on the transmission of the first DCI format; receiving the second PUSCH transmission according to the second information based on the transmission of the second DCI format, wherein the first DCI format and the second DCI format are monitored in different search spaces.

[0245] <Cross-reference>

[0246] This non-provisional application claims priority under 35 U.S.C. § 119 to Provisional Application No. 62 / 825,538, filed on Mar. 28, 2019, the entire content of which is hereby incorporated by reference.

Claims

1. A user equipment UE, characterized in that, Comprising: A receiver configured to receive a Radio Resource Control (RRC) configuration, the RRC configuration including a first parameter for defining a bit field size of an antenna port field in a first Downlink Control Information (DCI) format, a second parameter for defining a bit field size of a carrier indicator field in the first DCI format, and a third parameter indicating a first allocation table for defining a bit field size of a time domain resource allocation in the first DCI format, wherein the first DCI format includes a 4-bit Hybrid Automatic Repeat reQuest (HARQ) process number field; And A transmitter configured to perform a first Physical Uplink Shared Channel (PUSCH) transmission based on detection of the first DCI format, wherein In the case where the first PUSCH transmission is scheduled by the first DCI format, the first PUSCH transmission is performed according to the first parameter, the second parameter, and the third parameter, and In the case where the first PUSCH transmission is a configured PUSCH transmission with multiple configurations, the first PUSCH transmission is performed according to one of the multiple configurations, wherein The HARQ process number field indicates that one of the multiple configurations is activated, wherein The receiver is further configured to receive an RRC configuration, the RRC configuration including a fourth parameter for defining a bit field size of an antenna port field in a second DCI format, a fifth parameter for defining a bit field size of a carrier indicator field in the second DCI format, a sixth parameter for defining a bit field size of a priority indicator field in the second DCI format, and a seventh parameter indicating a second allocation table for defining a bit field size of a time domain resource allocation in the second DCI format, and The transmitter is further configured to perform a second PUSCH transmission based on detection of the second DCI format according to the fourth parameter, the fifth parameter, the sixth parameter, and the seventh parameter.

2. The UE according to claim 1, wherein The receiver is further configured to monitor the first DCI format and the second DCI format in different search spaces.

3. A method performed by a user equipment UE, characterized in that, The method includes: Receiving a Radio Resource Control (RRC) configuration, the RRC configuration including a first parameter for defining a bit field size of an antenna port field in a first Downlink Control Information (DCI) format, a second parameter for defining a bit field size of a carrier indicator field in the first DCI format, and a third parameter indicating a first allocation table for defining a bit field size of a time domain resource allocation in the first DCI format, wherein the first DCI format includes a 4-bit Hybrid Automatic Repeat reQuest (HARQ) process number field; Performing a first Physical Uplink Shared Channel (PUSCH) transmission based on detection of the first DCI format, wherein In the case where the first PUSCH transmission is scheduled by the first DCI format, the first PUSCH transmission is performed according to the first parameter, the second parameter, and the third parameter, and In the case where the first PUSCH transmission is a PUSCH transmission configured with multiple configurations, the first PUSCH transmission is performed according to one of the multiple configurations, where the HARQ process digit field indicates that the one of the multiple configurations is activated, receive an RRC configuration, the RRC configuration including a fourth parameter for defining the bit field size of the antenna port field in a second DCI format, a fifth parameter for defining the bit field size of the carrier indicator field in the second DCI format, a sixth parameter for defining the bit field size of the priority indicator field in the second DCI format, and a seventh parameter indicating a second allocation table for defining the bit field size of the time domain resource allocation in the second DCI format, and perform a second PUSCH transmission based on the detection of the second DCI format according to the fourth parameter, the fifth parameter, the sixth parameter, and the seventh parameter.

4. A base station, characterized in that, Comprising: a transmitter configured to transmit a radio resource control (RRC) configuration, the RRC configuration including a first parameter for defining the bit field size of the antenna port field in a first downlink control information (DCI) format, a second parameter for defining the bit field size of the carrier indicator field in the first DCI format, and a third parameter indicating a first allocation table for defining the bit field size of the time domain resource allocation in the first DCI format, where the first DCI format includes a 4-bit HARQ process digit field; and a receiver configured to receive a first physical uplink shared channel (PUSCH) transmission, where in the case where the first PUSCH transmission is scheduled by the first DCI format, receive the first PUSCH transmission according to the first parameter, the second parameter, and the third parameter, and in the case where the first PUSCH transmission is a PUSCH transmission configured with multiple configurations, receive the first PUSCH transmission according to one of the multiple configurations, where the HARQ process digit field indicates that the one of the multiple configurations is activated, where the transmitter is further configured to transmit an RRC configuration, the RRC configuration including a fourth parameter for defining the bit field size of the antenna port field in a second DCI format, a fifth parameter for defining the bit field size of the carrier indicator field in the second DCI format, a sixth parameter for defining the bit field size of the priority indicator field in the second DCI format, and a seventh parameter indicating a second allocation table for defining the bit field size of the time domain resource allocation in the second DCI format, and the receiver is further configured to receive a second PUSCH transmission scheduled by the second DCI format according to the fourth parameter, the fifth parameter, the sixth parameter, and the seventh parameter.

5. The base station according to claim 4, wherein the transmitter is further configured to transmit the first DCI format and the second DCI format in different search spaces.

Images