User Equipment, Base Station, and Method

Abstract

The present invention describes a UE communicating with a base station. The UE may include: a receiving circuit configured to monitor a PDCCH having a DCI format; a transmitting circuit configured to transmit a PUSCH subject to a channel access procedure, the starting position of an initial symbol of the PUSCH being adjusted by x; wherein the DCI format includes a 4-bit information field, the 4 bits being characterized by at least one or more of the following values.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to new signaling, procedures, user equipment (UE), base stations, and methods. 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 beneficial. Brief Description of the Drawings

[0005] Figure 1 is a block diagram illustrating a particular implementation of one or more gNBs and one or more user equipments (UEs) in which systems and methods for downlink and uplink transmissions can be implemented;

[0006] Figure 2 illustrates various components that can be utilized in a UE;

[0007] Figure 3 illustrates various components that can be utilized in a gNB;

[0008] Figure 4 is a block diagram illustrating a particular implementation of a UE in which systems and methods for downlink and uplink (re)transmissions can be implemented;

[0009] Figure 5 is a block diagram illustrating a particular implementation of a gNB in which systems and methods for downlink and uplink (re)transmissions can be implemented;

[0010] Figure 6 is a diagram illustrating an example of a resource grid;

[0011] Figure 7 illustrates examples of several parameters;

[0012] Figure 8 shows an example of a subframe structure for the Figure 7 parameters shown in

[0013] Figure 9 shows an example of a subframe structure for the Figure 7 parameters shown in

[0014] Figure 10 is a block diagram showing a specific implementation of a gNB;

[0015] Figure 11 is a block diagram showing a specific implementation of a UE;

[0016] Figure 12 shows an example of a control resource element and a reference signal structure;

[0017] Figure 13 shows an example of control channel and shared channel multiplexing;

[0018] Figure 14 shows PDCCH monitoring events for slot-based scheduling;

[0019] Figure 15 shows PDCCH monitoring occasions for non-slot-based scheduling;

[0020] Figure 16 shows an example of a channel access procedure;

[0021] Figure 17 shows an example of transmission delay;

[0022] Figure 18 shows an example of channel access priority levels for downlink transmission;

[0023] Figure 19 shows an example of channel access priority levels for uplink transmission;

[0024] Figure 20 shows an example of a channel access procedure;

[0025] Figure 21 shows an example of a channel access procedure;

[0026] Figure 22 shows an example of a channel access procedure;

[0027] Figure 23 shows an example of CW size adjustment;

[0028] Figure 24 shows an example of LBT for transmission using directional beams;

[0029] Figure 25 An example of LBT for transmission using a directional beam is shown;

[0030] Figure 26 An example of sub - band configuration is shown;

[0031] Figure 27 A typical scenario for PUSCH transmission is shown;

[0032] Figure 28 A typical scenario for PUSCH transmission is shown;

[0033] Figure 29 A typical scenario for PUSCH transmission is shown;

[0034] Figure 30 A typical scenario for PUSCH transmission is shown;

[0035] Figure 31 A typical scenario for PUSCH transmission is shown;

[0036] Figure 32 A typical scenario for PUSCH transmission is shown;

[0037] Figure 33 A typical scenario for PUSCH transmission is shown;

[0038] Figure 34 A method for a UE communicating with a gNB is shown; and

[0039] Figure 35 A method for a gNB communicating with a UE is shown. Detailed Description of the Invention

[0040] The present invention describes a user equipment (UE) communicating with a base station. The UE may include a receiving circuit configured to monitor the reception of a physical downlink control channel (PDCCH) having a downlink control information (DCI) format. The UE may also include a transmitting circuit configured to transmit a physical uplink shared channel (PUSCH) subject to a channel access procedure. The starting position of the PUSCH may be x microseconds after the initial boundary of the initial symbol allocated to the PUSCH. The DCI format may include a 4 - bit information field. The 4 - bit information may be characterized by at least one or more of the following values: a first value of the 4 - bit information field indicates that the channel access procedure type is Category - 1 Listen - Before - Talk (Cat - 1 LBT), and (N TA +N TA _offset)*T c ≤x<(N TA +N TA _offset)*T c+16; The second value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and x = (N TA +N TA _offset)*T c +16; The third value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; The fourth value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 25; The fifth value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = (N TA +N TA_offset )*T c +25; The sixth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0; The seventh value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; The eighth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; And the ninth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0. N TA can be a timing adjustment value. N TA _ offset can be a timing advance offset value. T c can be 1 / (480*10 3 *4096).

[0041] The 4-bit information can be characterized by at least one or more of the following values: The tenth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority for Cat-4 LBT is level 1, and x = N TA _ offset *T c ; The eleventh value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = N TA _ offset *T c; The twelfth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = N TA _ offset *T c ; And the thirteenth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = N TA _ offset *T c 。

[0042] The present invention describes a base station communicating with a user equipment (UE). The base station may include a transmission circuit configured to transmit a physical downlink control channel (PDCCH) having a downlink control (DCI) format. The base station may also include a receiving circuit configured to receive a physical uplink shared channel (PUSCH) transmitted subject to a channel access process. The starting position of the PUSCH may be x microseconds after the initial boundary of the initial symbol allocated to the PUSCH. The DCI format may include a 4-bit information field. The 4-bit information may be characterized by at least one or more of the following values: The first value of the 4-bit information field indicates that the channel access process type is Category-1 Listen Before Talk (Cat-1 LBT), and (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offsett )*T c +16; The second value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and x = (N TA +N TA_offset )*T c +16; The third value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; The fourth value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 25; The fifth value of the 4-bit information field indicates that the channel access process type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = (N TA +N TA_offset )*T c+25; The sixth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0; The seventh value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; The eighth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; And the ninth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0. N TA May be a timing adjustment value. N TA_offset May be a timing advance offset value. T c May be 1 / (480 * 10 3 * 4096).

[0043] The 4-bit information may be characterized by at least one or more of the following values: The tenth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority for Cat-4 LBT is level 1, and x = N TA_offset * T c ; The eleventh value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = N TA_offset * T c ; The twelfth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = N TA_offset * T c ; And the thirteenth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = N TA_offset * T c .

[0044] The present invention describes a method for a user equipment (UE) to communicate with a base station. The method may include monitoring a physical downlink control channel (PDCCH) having a downlink control information (DCI) format. The method may further include transmitting a physical uplink shared channel (PUSCH) subject to a channel access procedure. The starting position of the PUSCH may be x microseconds after the initial boundary of the initial symbol allocated to the PUSCH. The DCI format may include a 4-bit information field. The 4-bit information may be characterized by at least one or more of the following values: a first value of the 4-bit information field indicates that the channel access procedure type is Category-1 listen-before-talk (Cat-1 LBT), and (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offset )*T c +16; a second value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and x = (N TA +N TA_offset )*T c +16; a third value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; a fourth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 25; a fifth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = (N TA +N TA_offset )*T c +25; a sixth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0; a seventh value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; an eighth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; and a ninth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0. NTA may be a timing adjustment value. N TA_offset may be a timing advance offset value. T c may be 1 / (480*10 3 *4096).

[0045] The present invention describes a method for a base station to communicate with a user equipment (UE). The method may include transmitting a physical downlink control channel (PDCCH) with a downlink control (DCI) format. The method may also include receiving a physical uplink shared channel (PUSCH) transmitted subject to a channel access procedure. The starting position of the PUSCH may be x microseconds after the initial boundary of the initial symbol allocated to the PUSCH. The DCI format may include a 4-bit information field. The 4-bit information may be characterized by at least one or more of the following values: the first value of the 4-bit information field indicates that the channel access procedure type is Category-1 listen-before-talk (Cat-1 LBT), and (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offset )*T c +16; the second value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and x = (N TA +N TA_offset )*T c +16; the third value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; the fourth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 25; the fifth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = (N TA +N TA_offset )*T c +25; the sixth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0; the seventh value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; the eighth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; and the ninth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0. N TA may be a timing adjustment value. N TA_offset may be a timing advance offset value. T cIt can be 1 / (480 * 10 3 * 4096).

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

[0047] 3GPP Long-Term Evolution (LTE) is the name given to a project that awards the improvement of 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).

[0048] At least some aspects of the systems and methods disclosed herein can be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), and other standards including New Radio (NR) (e.g., 3GPP Release 8, Release 9, Release 10, Release 11, Release 12, Release 13, Release 14, and / or Release 15), and New Radio (NR) is also known as 3rd Generation NR (5G NR). 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 can be used in other types of wireless communication systems.

[0049] 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., the Public Switched Telephone Network (PSTN), the Internet, etc.). When describing the systems and methods herein, the wireless communication device can 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, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, vehicles, Internet of Things (IoT) devices, 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" can be used interchangeably herein to represent the more general term "wireless communication device". A UE can also more generally be referred to as a terminal device.

[0050] In 3GPP specifications, a base station is commonly referred to as Node B, evolved Node B (eNB), Home eNode B (HeNB), next-generation Node B (gNB), or some other similar terms. Since the scope of the present disclosure should not be limited to 3GPP standards, the terms "base station", "Node B", "eNB", "HeNB", and "gNB" 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 may be an electronic device that provides access to a network (e.g., a local area network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to represent wireless communication devices and / or base stations. eNBs and gNBs may also more generally be referred to as base station equipment.

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

[0052] 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" may be a serving cell. The UE may receive system information and perform required measurements on all configured cells. The "configured cells" for a radio connection may 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, the 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 "cells" may be described in different dimensions. For example, a "cell" may have time, space (e.g., geographical), and frequency characteristics.

[0053] The fifth-generation communication system, which is referred to as NR (New Radio) by 3GPP, envisions using time / frequency / spatial resources to permit services such as eMBB (Enhanced Mobile Broadband) transmission, URLLC (Ultra-Reliable and Low-Latency Communication) transmission, and eMTC (Massive Machine-Type Communication) transmission. Also, in NR, single-beam and / or multi-beam operations are considered for downlink and / or uplink transmission.

[0054] 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. Thus, 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 described systems and methods.

[0055] Figure 1 is a block diagram showing one specific embodiment of one or more gNBs 160 and one or more UEs 102 in which the systems and methods for downlink and uplink transmission can be implemented. One or more UEs 102 communicate with one or more gNBs 160 using one or more physical antennas 122a-n. For example, UE 102 uses one or more physical 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 physical antennas 180a-n.

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

[0057] Each of one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a 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.

[0058] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 may receive signals from 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. One or more receivers 120 may also sense the channels to be used for uplink transmission. One or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, one or more transmitters 158 may up-convert and transmit one or more modulated signals 156.

[0059] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signals. The decoder 108 may generate a decoded signal 110, which may include 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 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.

[0060] Generally, the UE operation module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include one or more of the UE scheduling modules 126.

[0061] The UE scheduling module 126 may also be referred to as a UE-side higher-layer processing module that performs higher-layer processing. Other units in the UE 102 except the UE scheduling module 126 may perform physical-layer processing.

[0062] In a radio communication system, physical channels (uplink physical channels and / or downlink physical channels) can be defined. The physical channels (uplink physical channels and / or downlink physical channels) can be used to transmit information delivered from a higher layer. For example, a PCCH (Physical Control Channel) can be defined. The PCCH is used to transmit control information.

[0063] In the uplink, the PCCH (e.g., Physical Uplink Control Channel (PUCCH)) is used to transmit uplink control information (UCI). The UCI can include Hybrid Automatic Repeat reQuest (HARQ ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ-ACK is used to indicate an affirmative acknowledgement (ACK) or a negative acknowledgement (NACK) of downlink data (i.e., a transport block carrying a Medium Access Control Control Element (MAC CE) and / or a MAC Protocol Data Unit (MAC PDU) that may include a Downlink Shared Channel (DL-SCH)). The CSI is used to indicate the state of the downlink channel. Also, the SR is used to request resources for uplink data (i.e., a transport block carrying a MAC CE and / or a MAC PDU that may include an Uplink Shared Channel (UL-SCH)).

[0064] For DL, the UE 102 can be configured to receive code block group (CBG)-based transmissions, where retransmissions can be scheduled for one or more subgroups of all the code blocks carrying a transport block. The UE 102 can be configured to transmit CBG-based transmissions, where retransmissions can be scheduled for one or more subgroups of all the code blocks carrying a transport block.

[0065] In the downlink, a PCCH (e.g., a Physical Downlink Control Channel (PDCCH)) can be used to transmit downlink control information (DCI). Here, more than one DCI format can be defined for DCI transmission on the PDCCH. That is, a DCI format defining field can be provided, and the field can be mapped to information bits (i.e., DCI bits). For example, DCI format 1A, which is used to schedule a Physical Shared Channel (PSCH) (e.g., PDSCH, transmission of a downlink transport block) in a cell, is defined as a DCI format for the downlink. The DCI format for PDSCH scheduling can include multiple information fields, such as a carrier indicator field, a frequency-domain PDSCH resource allocation field, a time-domain PDSCH resource allocation field, a bundling size field, an MCS field, a new data indicator field, a redundancy version field, a HARQ process number field, a Code Block Group Flush Indicator (CBGFI) field, a Code Block Group Transmission Indicator (CBGTI) field, a PUCCH power control field, a PUCCH resource indicator field, an antenna port field, a layer number field, a Quasi-Co-Location (QCL) indicator field, an SRS trigger request field, and an RNTI field. More than one of the above information can be jointly coded, and in this case, the jointly coded information can be indicated in a single information field.

[0066] Moreover, for example, DCI format 0, which is used to schedule a PSCH (e.g., PUSCH, transmission of an uplink transport block) in a cell, is defined as a DCI format for the uplink. For example, information associated with PSCH (PDSCH resource, PUSCH resource) allocation, information associated with the modulation and coding scheme (MCS) for the PSCH, and DCI such as the transmission power control (TPC) commands for PUSCH and / or PUCCH are all included in the DCI format. Moreover, the DCI format may include information associated with a beam index and / or an antenna port. The beam index may indicate the beams for downlink transmission and uplink transmission. The antenna port may include a DL antenna port and / or a UL antenna port. The DCI format for PUSCH scheduling may include multiple information fields, for example, a carrier indicator field, a frequency-domain PUSCH resource allocation field, a time-domain PUSCH resource allocation field, an MCS field, a new data indicator field, a redundancy version field, a HARQ process number field, a code block group flush indicator (CBGFI) field, a code block group transmission indicator (CBGTI) field, a PUSCH power control field, an SRS resource indicator (SRI) field, a wideband and / or sub-band transmission precoding matrix indicator (TPMI) field, an antenna port field, a scrambling identity field, a layer number field, a CSI report trigger request field, a CSI management request field, an SRS trigger request field, and an RNTI field. More than one of the above information may be jointly coded, and in this case, the jointly coded information may be indicated in a single information field.

[0067] Moreover, for example, a PSCH may be defined, For example, in the case of scheduling a downlink PSCH resource (e.g., PDSCH resource) by using DCI format, the UE 102 may receive downlink data on the scheduled downlink PSCH resource. Moreover, in the case of scheduling an uplink PSCH resource (e.g., PUSCH resource) by using DCI format, the UE 102 transmits uplink data on the scheduled uplink PSCH resource. That is, the downlink PSCH is used to transmit downlink data. And the uplink PSCH is used to transmit uplink data.

[0068] In addition, the downlink PSCH and the uplink PSCH are used to transmit information of higher layers (e.g., the radio resource control (RRC) layer) and / or the MAC layer. For example, the downlink PSCH and the uplink PSCH are used to transmit RRC messages (RRC signals) and / or MAC control elements (MAC CEs). Here, the RRC messages transmitted from the gNB 160 in the downlink are shared among multiple UEs 102 within the cell (referred to as common RRC messages). Moreover, the RRC messages transmitted from the gNB 160 can be dedicated to a certain UE 102 (referred to as dedicated RRC messages). The RRC messages and / or MAC CEs are also referred to as higher layer signals.

[0069] 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 the receivers 120 when to receive retransmissions.

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

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

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

[0073] The encoder 150 can encode the transmission data 146 and / or other information 142 provided by the UE operation module 124. For example, encoding the transmission data 146 and / or other information 142 can 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 can provide the encoded data 152 to the modulator 154.

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

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

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

[0077] 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 physical antennas 180a-n. For example, the receiver 178 may receive and down-convert the signal 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 receivers 178 may also sense the channel to be used for downlink transmission. One or more transmitters 117 may use one or more physical antennas 180a-n to send signals to the UE 102. For example, one or more transmitters 117 may up-convert and send one or more modulated signals 115.

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

[0079] Generally speaking, the gNB operation module 182 can enable the gNB 160 to communicate with one or more UEs 102. The gNB operation module 182 can include one or more of the gNB scheduling modules 194. The gNB scheduling module 194 can also be referred to as the gNB side high-layer processing module that performs high-layer processing. Other units in the gNB 160 except the gNB scheduling module 194 can perform physical layer processing.

[0080] The gNB operation module 182 can provide information 188 to the demodulator 172. For example, the gNB operation module 182 can notify the demodulator 172 of the modulation pattern expected for the transmission from the UE 102.

[0081] The gNB operation module 182 can provide information 186 to the decoder 166. For example, the gNB operation module 182 can notify the decoder 166 of the coding expected for the transmission from the UE 102.

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

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

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

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

[0086] It should be noted that DL subframes can be transmitted from the gNB 160 to one or more UEs 102, and UL subframes can be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 can transmit data in standard special time slots.

[0087] It should also be noted that one or more of the elements or their components included in the gNB 160 and the UE 102 can be implemented in hardware. For example, one or more of these elements or their components can 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 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, application-specific integrated circuit (ASIC), large-scale integrated circuit (LSI), or integrated circuit, etc., and / or implemented using a chipset, application-specific integrated circuit (ASIC), large-scale integrated circuit (LSI), or integrated circuit, etc.

[0088] The downlink physical layer processing of the transport channel can include: transport block CRC attachment; code block segmentation and code block CRC attachment; channel coding (LDPC coding); physical layer hybrid ARQ processing; rate matching; scrambling; modulation (EE, 16QAM, 64QAM, and 256QAM); layer mapping; and mapping to allocated resources and antenna ports.

[0089] Figure 2 Shows various components that can be used for the UE 202. In combination with Figure 2 The UE 202 described in combination with Figure 1Implemented by the described UE 22. The UE 202 includes a processor 203 that controls the operation of the UE 202. The processor 203 may also be referred to as a central processing unit (CPU). A memory 205 (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 207a and data 209a to the processor 203. A portion of the memory 205 may also include non-volatile random access memory (NVRAM). Instructions 207b and data 209b may also reside in the processor 203. The instructions 207b and / or data 209b loaded into the processor 203 may also include instructions 207a and / or data 209a from the memory 205 that are loaded for execution or processing by the processor 203. The instructions 207b may be executed by the processor 203 to implement the above method.

[0090] The UE 202 may also include a housing that houses one or more transmitters 258 and one or more receivers 220 to allow for sending and receiving data. The transmitter 258 and receiver 220 may be combined into one or more transceivers 218. One or more antennas 222a-n are attached to the housing and electrically coupled to the transceivers 218.

[0091] The various components of the UE 202 are coupled together by a bus system 211 (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 211 in Figure 2 The UE 202 may also include a digital signal processor (DSP) 213 for processing signals. The UE 202 may also include a communication interface 215 that provides user access to the functions of the UE 202. Figure 2 The illustrated UE 202 is a functional block diagram rather than a list of specific components.

[0092] Figure 3 Various components that can be used for the gNB 360 are shown. The gNB 360 described in conjunction with Figure 3 may be in accordance with that described in conjunction with Figure 1Implemented by the described gNB 160. gNB 360 includes a processor 303 that controls the operation of gNB 360. The processor 303 may also be referred to as a central processing unit (CPU). A memory 305 (which may include read-only memory (ROM), random access memory (RAM), a combination of both memories, or any type of device that can store information) provides instructions 307a and data 309a to the processor 303. A portion of the memory 305 may also include non-volatile random access memory (NVRAM). Instructions 307b and data 309b may also reside in the processor 303. The instructions 307b and / or data 309b loaded into the processor 303 may also include instructions 307a and / or data 309a from the memory 305 and loaded for execution or processing by the processor 303. The instructions 307b may be executed by the processor 303 to implement the above method.

[0093] gNB 360 may also include a housing that houses one or more transmitters 317 and one or more receivers 378 to allow for the transmission and reception of data. The transmitters 317 and receivers 378 may be combined into one or more transceivers 376. One or more antennas 380a-n are attached to the housing and electrically coupled to the transceivers 376.

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

[0095] Figure 4 is a block diagram showing a specific implementation of a UE 402 in which a system and method for downlink and uplink transmission may be implemented. The UE 402 includes a transmitting device 458, a receiving device 420, and a control device 424. The transmitting device 458, the receiving device 420, and the control device 424 may be configured to perform one or more of the functions described above Figure 1 above Figure 2 shows Figure 4 an example of the specific device structure of Figure 1 One or more of the functions of. Various other structures may be implemented to achieve

[0096] Figure 5It is a block diagram showing a specific implementation of the gNB 560 in which systems and methods for downlink and uplink transmissions can be implemented. The gNB 560 includes a transmitting device 517, a receiving device 578, and a control device 582. The transmitting device 517, the receiving device 578, and the control device 582 can be configured to perform one or more of the functions described above Figure 1 above Figure 3 shows Figure 5 an example of the specific device structure. Various other structures can be implemented to achieve Figure 1 one or more of the functions

[0097] Figure 6 is a diagram showing an example of a resource grid Figure 6 The resource grid shown can be applicable to both the downlink and the uplink and 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 below

[0098] In Figure 6 , one or several time slots 683 can be used to transmit / receive physical channels and physical signals. For a given parameter μ, N μ RB is the bandwidth configuration of the bandwidth part (BWP) in the serving cell, expressed as a multiple of N RB SC where N RB SC is the size of the resource block 689 in the frequency domain, expressed as the number of subcarriers, and N SF,μ 符号 is the number of orthogonal frequency division multiplexing (OFDM) symbols 687 in the subframe 669. In other words, for each parameter μ and for each of the downlink and the uplink, a resource grid of N μ RB N RB SC subcarriers and N SF，μ 符号 OFDM symbols can be defined. There can be a resource grid for each antenna port p, each subcarrier spacing configuration (SCS, also referred to as a parameter) μ, and each transmission direction (uplink or downlink). The resource block 689 can include a plurality of resource elements (RE) 691

[0099] As shown in Table 1, multiple OFDM parameters (which can also be simply referred to as parameters) are supported. Each parameter can be bound to its corresponding subcarrier spacing Δf

[0100] [Table 1]

[0101] μ <![CDATA[Δf = 2 μ ·15 [kHz]]]> Cyclic Prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

[0102] For a subcarrier spacing configuration μ, within a subframe, the time slots are numbered n in ascending order μ s ∈ {0, ···, N SF ,μ 时隙 −1}, and within a frame, the time slots are numbered n in ascending order μ s,f ∈ {0, ···, N 帧,μ 时隙 −1}. There are N 时隙,μ 符号 consecutive OFDM symbols in a time slot, where N 时隙,μ 符号 depends on the subcarrier spacing used and is given in Table 2 for normal cyclic prefix and Table 3 for extended cyclic prefix. The number of consecutive OFDM symbols per subframe is N SF,μ symbols = N 时隙,μ 符号 .N SF,μ time slots. The start of time slot n μ s in a subframe is aligned in time with the start of OFDM symbol n μ s N 时隙,μ 符号 in the same subframe. Not all UEs can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink time slot or an uplink time slot can be used.

[0103] [Table 2]

[0104] μ <![CDATA[N 时隙,μ 符号 > <![CDATA[N 帧,μ 时隙 > <![CDATA[N SF,μ 时隙 > 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0105] [Table 3]

[0106] μ <![CDATA[N 时隙,μ 符号 > <![CDATA[N 帧,μ 时隙 > <![CDATA[N SF,μ 时隙 > 2 12 40 4

[0107] For the initial BWP, N μ RB can be broadcast as part of system information (e.g., Master Information Block (MIB), System Information Block type 1 (SIB1)). For SCell (including Licensed-Assisted Access (LAA) SCell), N μ RB is configured via an RRC message dedicated to UE102. For PDSCH mapping, the available RE 691 can be the RE 691 whose index l satisfies l ≥ l 数据,开始 and / or l 数据,结束 ≥ l in a subframe.

[0108] An OFDM access scheme with a cyclic prefix (CP) can be adopted, and this scheme can also be referred to as CP-OFDM. In the downlink, PDCCH, EPDCCH (Enhanced Physical Downlink Control Channel), PDSCH, etc. can be transmitted. A radio frame can include a set of time slots 683 (e.g., 10 time slots when μ = 1). An RB is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot.

[0109] The resource block is defined as N RB sc = 12 consecutive subcarriers in the frequency domain and one time slot (which consists of 14 symbols with normal CP and 12 symbols with extended CP).

[0110] For the subcarrier spacing configuration μ, the carrier resource blocks in the frequency domain are numbered from 0 to N μ RB -1. The relationship between the carrier resource block number n CRB in the frequency domain and the resource element (k, l) is given by n CRB = floor(k / N RB sc ), where k is defined relative to the resource grid. The physical resource block is defined within the carrier bandwidth part (BWP) and is numbered from 0 to N 大小 BWP,i -1, where i is the number of carrier bandwidth parts. The relationship between the physical resource block and the absolute resource block in carrier bandwidth part i is given by n CRB = n PRB + N 开始 BWP,i -1, where N 开始 BWP,i is the carrier resource block at the start of the carrier bandwidth part. The virtual resource block is defined within the carrier bandwidth part and is numbered from 0 to N 大小 BWP,i -1, where i is the number of carrier bandwidth parts.

[0111] The carrier bandwidth part is a continuous set of physical resource blocks selected from a continuous subset of the carrier resource blocks with a given parameter μ on a given carrier. The number of resource blocks N 大小 BWP,i in the carrier BWP can satisfy N 最小，μ RB,x <= N 大小 BWP,i <= N 最大,μ RB,xThe UE can be configured to have a maximum of four carrier bandwidth parts in the downlink, and only a single downlink carrier bandwidth part is active at a given time. It is not expected that the UE receives PDSCH or PDCCH outside the active bandwidth part. The UE can be configured to have a maximum of four carrier bandwidth parts in the uplink, and only a single uplink carrier bandwidth part is active at a given time. The UE shall not transmit PUSCH or PUCCH outside the active bandwidth part.

[0112] An RB can include twelve subcarriers in the frequency domain and one or more 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 RG ) where k = 0, …, N μ RB N RB sc −1 and l RG = 0, …, N SF,μ 符号 −1 are the indices in the frequency domain and time domain respectively. In addition, the RE is uniquely identified by the index pair (k, l) based on a certain reference point, where l is the index in the time domain. The reference point can be based on the resource grid, i.e., on a component carrier (CC) basis. Alternatively, the reference point can be based on a certain bandwidth part within a component carrier. Although subframes in one CC are discussed herein, subframes are defined for each CC, and the subframes between CCs are substantially synchronized with each other.

[0113] In the uplink, in addition to CP - OFDM, a single - carrier frequency - division multiple access (SC - FDMA) access scheme can also be adopted, which is also known as discrete Fourier transform - spread OFDM (DFT - S - OFDM). In the uplink, PUCCH, PDSCH, physical random access channel (PRACH), etc. can be transmitted.

[0114] For each parameter and carrier, a resource grid of N 最大,μ RB,x N RB sc subcarriers and N SF,μ 符号 OFDM symbols is defined, where N 最大,μ RB,x is given in Table 4 and x for the downlink and uplink is DL or UL respectively. There is a resource grid for each antenna port p, each subcarrier spacing configuration μ, and each transmission direction (uplink or downlink).

[0115] [Table 4]

[0116] μ <![CDATA[N 最小,μ RB,DL > <![CDATA[N 最大,μ RB,DL > <![CDATA[N 最小,μ RB,UL > <![CDATA[N 最大,μ RB,UL > 0 20 275 24 275 1 20 275 24 275 2 20 275 24 275 3 20 275 24 275 4 20 138 24 138

[0117] It may indicate that the UE 102 uses only a subset of the resource grid for reception or transmission. The set of resource blocks of the UE is referred to as the carrier bandwidth part and may be configured to receive or transmit in the frequency domain when numbered from 0 to N μ RB -1. The UE may be configured to have one or more carrier bandwidth parts, and each carrier bandwidth part may have the same or different parameters.

[0118] Transmissions in multiple cells can be aggregated, and up to fifteen secondary cells can be used in addition to the primary cell. The UE 102 configured to operate in the bandwidth part (BWP) of the serving cell is configured by the higher layer for the serving cell with a set of up to four bandwidth parts (BWPs) received by the UE (DL BWP set) in the DL bandwidth indexed by the parameter DL-BWP and a set of up to four BWPs transmitted by the UE 102 (UL BWP set) in the UL bandwidth indexed by the parameter UL-BWP. For unpaired spectrum operations, the DL BWP from the configured DL BWP set is linked to the UL BWP from the configured UL BWP set, where the DL BWP and the UL BWP have the same index in the respective sets. For unpaired spectrum operations, the UE 102 may expect the center frequency of the DL BWP to be the same as the center frequency of the UL BWP.

[0119] The physical downlink control channel (PDCCH) can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH, where the downlink control information (DCI) on the PDCCH includes: downlink allocations that contain at least the modulation and coding format, resource allocation, and HARQ information related to the DL-SCH; and uplink scheduling authorizations that contain at least the modulation and coding format, resource allocation, and HARQ information related to the UL-SCH. In addition to scheduling, the PDCCH can be used for: activating and deactivating configured PUSCH transmissions with configured grants; activating and deactivating semi-persistent PDSCH transmissions; notifying one or more UEs of the slot format; notifying one or more UEs of the PRB and OFDM symbols, where the UE may assume that no transmission is intended for the UE; transmitting TPC commands for the PUCCH and PUSCH; transmitting one or more TPC commands for SRS transmissions by one or more UEs; switching the active bandwidth part of the UE; and initiating a random access procedure.

[0120] During the random access procedure, the UE 102 may transmit a PRACH with a random access preamble in a PRACH opportunity selected from the PRACH opportunities corresponding to the indices of the detected SS / PBCH block candidates. The gNB 160 may receive the PRACH in the selected PRACH opportunity. Message 2 is the procedure in which the UE 102 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled by a RA-RNTI (Random Access - Radio Network Temporary Identifier). The UE 102 may attempt to detect DCI format 1_0 in the search space set. Message 3 is the procedure for transmitting a PUSCH scheduled by a random access response (RAR) grant included in the DCI format 1_0 detected during the Message 2 procedure. The random access response grant is indicated by a MAC CE, which is included in the PDSCH scheduled by the DCI format 1_0. The PUSCH scheduled based on the random access response grant is a Message 3 PUSCH or a PUSCH. The Message 3 PUSCH contains a contention resolution identifier MAC CE. The contention resolution ID MAC CE includes a contention resolution ID. The retransmission of the Message 3 PUSCH is scheduled by DCI format 0_0 with a CRC scrambled by a TC-RNTI (Temporary Cell - Radio Network Temporary Identifier). Message 4 is the procedure for attempting to detect DCI format 1_0 with a CRC scrambled by a C-RNTI (Cell - Radio Network Temporary Identifier) or a TC-RNTI. The UE 102 may receive a PDSCH scheduled based on the DCI format 1_0. The PDSCH may include a conflict resolution ID.

[0121] One or more sets of PRBs may be configured for DL control channel monitoring. In other words, a control resource set is a set of PRBs in the frequency domain within which the UE 102 attempts blind decoding of downlink control information (i.e., monitors downlink control information (DCI)), where the PRBs may or may not be frequency - contiguous, 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 of a control channel (which may or may not include 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 portion of the resources in the control resource sets for data of the same or different UEs 102 is supported, at least in the frequency domain.

[0122] That is, the UE 102 may have to monitor a set of PDCCH candidates in one or more control resource sets on one or more active serving cells or bandwidth parts (BWPs) according to the corresponding search space, where monitoring means decoding each PDCCH candidate according to the monitored DCI format. Here, a PDCCH candidate can be a candidate on which a PDCCH may be allocated and / or transmitted. A PDCCH candidate consists of one or more control channel elements (CCEs). The term "monitoring" means that the UE 102 attempts to decode each PDCCH in this set of PDCCH candidates according to all DCI formats to be monitored.

[0123] The set of PDCCH candidates monitored by the UE 102 may also be referred to as a search space or a search space set. That is, a search space (or a search space set) is a set of resources that may be used for PDCCH transmission.

[0124] In addition, a common search space (CSS) and a user equipment search space (USS) are set (or defined, configured). For example, the CSS can be used to transmit PDCCHs with DCI formats to multiple UEs 102. That is, the CSS can be defined by resources shared by multiple UEs 102. For example, the CSS consists of a predetermined number of CCEs between the gNB 160 and the UE 102. For example, the CSS consists of CCEs with indices from 0 to 15.

[0125] Here, CSS can be used to transmit PDCCH with DCI format to a specific UE 102. That is, gNB 160 can transmit DCI formats intended for multiple UEs 102 and / or DCI formats intended for a specific UE 102 in CSS. There can be one or more types of CSS. For example, type 0 PDCCH CSS can be defined for DCI formats scrambled by a system information - radio network temporary identifier (SI-RNTI) on the primary cell (PCell). Type 1 PDCCH CSS can be defined for DCI formats scrambled by a random access - (RA-)RNTI. In addition and / or alternatively, type 1 PDCCH CSS can be used for DCI formats scrambled by a temporary cell - (TC-)RNTI or a cell - (C-)RNTI. Type 2 PDCCH CSS can be defined for DCI formats scrambled by a paging - (P-)RNTI. Type 3 PDCCH CSS can be defined for DCI formats scrambled by an interference - (INT-)RNTI, where if UE102 is configured by a higher layer to decode a DCI format with a CRC scrambled by INT-RNTI, and if UE 102 detects a DCI format with a CRC scrambled by INT-RNTI, UE 102 can assume that there is no transmission to UE 102 in the OFDM symbols and resource blocks indicated by this DCI format. In addition and / or alternatively, type 3 PDCCH CSS can be used for DCI formats scrambled by other RNTIs (e.g., transmission power control - (TPC-)RNTI, preemption indicator - (PI-)RNTI, slot format indicator - (SFI-)RNTI, semi-persistent scheduling - (SPS-)RNTI, grant-free - (GF-)RNTI, configured scheduling - (CS-)RNTI, URLLC - (U-)RNTI), MCS-RNTI, auto uplink - (AUL-)RNTI, downlink feedback information - (DFI-)RNTI).

[0126] The UE 102 can be indicated by the System Information Block type 0 (SIB0) (also known as the MIB), the control resource set for the type 0 PDCCH common search space, and the subcarrier spacing and CP length for PDCCH reception. The type 0 PDCCH common search space is defined by the CCE aggregation level and the number of candidates for each CCE aggregation level. The UE may assume that the DMRS antenna port associated with PDCCH reception in the type 0 PDCCH common search space and the DMRS antenna port associated with Physical Broadcast Channel (PBCH) reception are quasi-co-located with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. The PBCH carries the Master Information Block (MIB) containing most of the important system information. The PDCCH with a specific DCI format in the type 0 PDCCH common search space schedules the reception of the PDSCH carrying SIB type 1 (SIB1) or other SI messages. The UE can be indicated by the SIB 1 control resource set for the type 1 PDCCH common search space. The subcarrier spacing and CP length for PDCCH reception with a type 1 PDCCH common search space are the same as those for PDCCH reception with a type 0 PDCCH common search space. The UE may assume that the DMRS antenna port associated with PDCCH reception in the type 1 PDCCH common search space and the DMRS antenna port associated with PBCH reception are quasi-co-located with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. The monitoring periodicity of the paging occasion of the PDCCH in the type 2 PDCCH common search space can be configured for the UE by a higher layer parameter. The UE can be configured by higher layer signaling whether to monitor the type 3 PDCCH common search space and / or which serving cell monitors the type 3 PDCCH common search space.

[0127] The USS can be used to transmit a PDCCH with a DCI format to a specific UE 102. That is, the USS is defined by resources dedicated to a certain UE 102. That is, the USS can be defined independently for each UE 102. For example, the USS can consist of a number of CCEs determined based on the RNTI allocated by the gNB 160, the slot number in the radio frame, the aggregation level, etc.

[0128] Here, the RNTI may include C-RNTI (Cell-RNTI), temporary C-RNTI. Also, the USS (the location of the USS) can be configured by the gNB 160. For example, the gNB 160 can configure the USS by using an RRC message. That is, the base station can transmit a DCI format intended for a specific UE 102 in the USS.

[0129] Here, the RNTI assigned to UE 102 can be used for the transmission of DCI (transmission of PDCCH). Specifically, the CRC (Cyclic Redundancy Check) parity bits (also simply referred to as CRC) generated based on the DCI (or DCI format) are attached to the DCI, and after attachment, the CRC parity bits are scrambled by the RNTI. UE 102 can attempt to decode the DCI to which the CRC parity bits scrambled by the RNTI are attached and detect the PDCCH (i.e., DCI, DCI format). That is to say, UE 102 can use the CRC scrambled by the RNTI to decode the PDCCH.

[0130] When the control resource set spans multiple OFDM symbols, the control channel candidates can be mapped to multiple OFDM symbols or can be mapped to a single OFDM symbol. One DL control channel element can be mapped to the 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 can be performed.

[0131] 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 to an integer. gNB 160 can notify UE 102 which control channel candidates are mapped to each subset of the 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, that is, multiple DL control channel elements are aggregated within one OFDM symbol. Otherwise, DL control channel elements can be aggregated in different OFDM symbols.

[0132] The DCI format can be classified into at least the following 4 types for PDSCH and PUSCH scheduling: DL regular (also called DCI format 1_1), UL regular (also called DCI format 0_1), DL fallback (also called DCI format 1_0), and UL fallback (also called DCI format 0_0). In addition, there may be some other types for control signaling. Furthermore, some more types (e.g., DCI format 0_2, 0_3, 1_2, and 1_3) can be defined for scheduling one or more PUSCHs and one or more PDSCHs, which can be applicable to NR-based unlicensed access (NR-U) cells. Table 5 shows an example of a set of DCI format types.

[0133] [Table 5]

[0134]

[0135] The DL normal DCI format and the UL normal DCI format may have the same DCI payload size. The DL fallback DCI format and the UL fallback DCI format may have the same DCI payload size. Tables 6, 7, 8, and 9 respectively show examples of DCI formats 0_0, 0_1, 1_0, and 1_1. "Mandatory" may mean that the information field always exists, regardless of RRC (re)configuration. "Optional" may mean that the information field may or may not exist according to RRC (re)configuration. In the DL fallback DCI format and the UL fallback DCI format, all information fields are mandatory, so that their DCI payload sizes are fixed, regardless of RRC (re)configuration.

[0136] [Table 6]

[0137]

[0138]

[0139] [Table 7]

[0140]

[0141]

[0142] [Table 8]

[0143]

[0144]

[0145] [Table 9]

[0146]

[0147]

[0148] Figure 7 Shows examples of several parameters. Parameter #1 (μ = 0) can be a basic parameter. For example, the RE of this basic parameter is defined to have a subcarrier spacing of 15 kHz in the frequency domain and a length of 2048κTS + CP in the time domain (e.g., 512κTS, 160κTs, or 144κTs), where Ts represents the baseband sampling time unit defined as 1 / (15000*2048) seconds. For the μ-th parameter, the subcarrier spacing can be equal to 15*2 μ , and the effective OFDM symbol length NuTs = 2048*2 -μ κTs. This can make the symbol length 2048*2 -μ κTs + CP length (e.g., 512*2 -μ κTs, 160*2-μ κTs or 144 * 2 -μ κTs). Note that κ = 64 and Ts = 1 / (Δf_max · N f ), Δf 最大 = 480 · 10 3 Hz (i.e., Δf when μ = 5), and N f = 4096. In other words, the subcarrier spacing of the μ + 1-th parameter is twice that of the μ-th parameter, and the symbol length of the μ + 1-th parameter is half that of the μ-th parameter. Figure 7 Four parameters are shown, but the system can support another number of parameters.

[0149] Figure 8 Shows Figure 7 A set of examples of the subframe structure of the parameters shown in. These examples are based on a slot configuration set to 0. One slot includes 14 symbols, the slot length of the μ + 1-th parameter is half that of the μ-th parameter, and the number of slots in the final subframe (e.g., 1 ms) doubles. It should be noted that a radio frame can include 10 subframes, and the radio frame length can be equal to 10 ms.

[0150] Figure 9 Shows Figure 7 Another set of examples of the subframe structure of the parameters shown in. These examples are based on a slot configuration set to 1. One slot includes 7 symbols, the slot length of the μ + 1-th parameter is half that of the μ-th parameter, and the number of slots in the final subframe (e.g., 1 ms) doubles.

[0151] The downlink physical channel can correspond to a set of resource elements carrying information from the higher layers. The downlink physical channel can include the Physical Downlink Shared Channel (PDSCH), the Physical Broadcast Channel (PBCH), and the Physical Downlink Control Channel (PDCCH). The downlink physical signal corresponds to a set of resource elements used by the physical layer but does not carry information from the higher layers. The downlink physical signal can include the Demodulation Reference Signal (DM-RS), the Phase Tracking Reference Signal (PT-RS), the Channel State Information Reference Signal (CSI-RS), the Primary Synchronization Signal (PSS), and the Secondary Synchronization Signal (SSS).

[0152] The uplink physical channel may correspond to a set of resource elements carrying information from higher layers. The uplink physical channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), and a Physical Random Access Channel (PRACH). The uplink physical signal may be used by the physical layer but may not carry information from higher layers. The uplink physical signal may include a Demodulation Reference Signal (DM-RS), a Phase Tracking Reference Signal (PT-RS), and a Sounding Reference Signal (SRS).

[0153] The Synchronization Signal and Physical Broadcast Channel block (SSB) may consist of a Primary Synchronization Signal and a Secondary Synchronization Signal (PSS, SSS), where each primary synchronization signal and secondary synchronization signal occupies 1 symbol and 127 subcarriers, and the PBCH spans 3 OFDM symbols and 240 subcarriers, but leaves an unused portion in the middle for the SSS on one symbol. For conventional NR operation, the PSS and SSS may be in different OFDM symbols separated by an OFDM symbol gap, where the PSS comes first and then the SSS. The periodicity of the SSB may be configured by the network, and the time position at which the SSB can be transmitted is determined by the subcarrier spacing. Multiple SSBs may be transmitted within the frequency span of a carrier. The Physical Cell Identifiers (PCIs) of these SSBs may not have to be unique, i.e., different SSBs may have different PCIs. However, when an SSB is associated with SIB1 (also known as the Remaining Minimum System Information (RMSI)), the SSB may correspond to a single cell with a unique NR Cell Global Identifier (NCGI). Such an SSB may be referred to as a Cell Definition SSB (CD-SSB). The PCell may always be associated with a CD-SSB located on the synchronization raster.

[0154] A Slot Format Indicator (SFI) may be defined to specify the format of one or more slots. Using the SFI, UE 102 may be able to derive, respectively, those symbols in a given slot that are at least "DL", "UL", and "unknown". Additionally, it may also indicate those symbols in a given slot that are "reserved". Using the SFI, UE 102 may also be able to derive the number of slots whose format is indicated by the SFI. The SFI may be configured via a dedicated RRC configuration message. Alternatively and / or in addition, the SFI may be signaled by a group common PDCCH (e.g., a PDCCH with an SFI-RNTI). Still alternatively and / or in addition, the SFI may be broadcast via the Master Information Block (MIB) or the Remaining Minimum System Information (RMSI).

[0155] For example, each SFI may express a combination of up to 8 of "DL", "UL", "unknown", and "reserved", with each combination including N 时隙,μ 符号 symbol types. More specifically, given N 时隙,μ符号 = 14, one combination can be "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown" "unknown". Another combination can be all "DL", i.e., "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL". Another combination can be all "UL", i.e., "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL" "UL". Another combination can be a combination of "DL", "UL", and "reserved", such as "DL" "DL" "DL" "DL" "DL" "DL" "DL" "DL" "reserved" "reserved" "reserved" "reserved" "UL".

[0156] The "DL" symbol can be used for DL reception and CSI / RRM measurement at the UE 102. The "UL" symbol can be used for UL transmission at the UE 102. The "unknown" resource can also be referred to as a "flexible" resource and can be covered by at least DCI indication. If not covered by DCI and / or SFI indication, then "unknown" can be used to achieve the same value as "reserved". On the "unknown" symbol, the UE 102 can be allowed to perform any DL and UL transmission configured by the higher layer, except when the "unknown" symbol is covered by DCI indicating the other direction and any DL and UL transmission indicated by DCI. For example, periodic CSI-RS, periodic CSI-IM, semi-persistent scheduled CSI-RS, periodic CSI reporting, semi-persistent scheduled CSI reporting, periodic SRS transmission, higher layer configured primary synchronization signal (PSS) / secondary synchronization signal (SSS) / PBCH can be assumed (i.e., for DL, it is assumed to exist and be able to perform reception, and for UL, it is assumed to be able to perform transmission).

[0157] The coverage of the "unknown" symbol by DCI means that the UE 102 may have to assume only the DL and UL transmissions (PDSCH transmission, PUSCH transmission, aperiodic CSI-RS transmission, aperiodic CSI-IM resource, aperiodic SRS transmission) indicated by the DCI indication. The coverage of the "unknown" symbol by SFI means that the UE 102 may have to assume the symbol as "DL", "UL", or "reserved" according to the SFI indication. If the UE 102 assumes an aperiodic CSI-RS transmission and / or an aperiodic CSI-IM resource, the UE 102 can perform CSI and / or RRM measurement based on the aperiodic CSI-RS transmission and / or the aperiodic CSI-IM resource.

[0158] If the UE 102 does not assume non-periodic CSI-RS transmissions and / or non-periodic CSI-IM resources, the UE 102 may not use non-periodic CSI-RS transmissions and / or non-periodic CSI-IM resources for CSI and / or RRM measurements.

[0159] The UE 102 may have to monitor the PDCCH on certain "DL" or "unknown" symbols. There may be several options for monitoring the PDCCH. If all the OFDM symbols allocated for a given control resource set (CORESET) are "DL", the UE 102 may assume that all the OFDM symbols are valid for monitoring the PDCCH associated with the given CORESET. In this case, the UE 102 may assume that each PDCCH candidate in the CORESET is mapped to all the OFDM symbols for time-first resource element group (REG) to control channel element (CCE) mapping. If all the OFDM symbols allocated for a given CORESET are "unknown", the UE 102 may assume that all the OFDM symbols are valid for monitoring the PDCCH associated with the given CORESET. In this case, the UE 102 may assume that each PDCCH candidate in the CORESET is mapped to all the OFDM symbols for time-first REG to CCE mapping.

[0160] If each of the OFDM symbols allocated for a given combination of CORESET and search space set is "UL" or "reserved", the UE 102 may assume that those OFDM symbols are invalid for monitoring the PDCCH associated with the given combination of CORESET and search space set. If some of the OFDM symbols allocated for a given combination of CORESET and search space set are "DL" and others are "UL" or "reserved", or if some of the OFDM symbols allocated for a given combination of CORESET and search space set are "unknown" and others are "UL" or "reserved", the UE 102 may not monitor the PDCCH in the CORESET.

[0161] NR-U may not support the dedicated RRC configuration of RMSI and / or slot format. In this case, all symbols are considered to be flexible by default.

[0162] Figure 10It is a block diagram showing a specific implementation of gNB 1060 (an example of gNB 160). gNB 1060 may include a high-layer processor 1001 (also referred to as high-layer processing circuitry), a DL transmitter 1002, a UL receiver 1003, and an antenna 1004. The DL transmitter 1002 may include a PDCCH transmitter 1005 and a PDSCH transmitter 1006. The UL receiver 1003 may include a PUCCH receiver 1007 and a PUSCH receiver 1008. The high-layer processor 1001 may manage the behavior of the physical layer (the behavior of the DL transmitter and UL receiver, LBT, etc.) and provide high-layer parameters to the physical layer. The high-layer processor 1001 may obtain transport blocks from the physical layer. The high-layer processor 1001 may send to / obtain from the high layer of the UE high-layer messages such as common and dedicated RRC messages and / or MAC messages. The high-layer processor 1001 may also set and / or store high-layer parameters carried by high-layer messages. The high-layer processor 1001 may provide the transport block to the PDSCH transmitter 1006 and provide the transmission parameters of the PDCCH transmitter 1005 related to the transport block. The UL receiver 1003 may receive and demultiplex multiplexed uplink physical channels and uplink physical signals via the receiving antenna. The PUCCH receiver 1007 may provide the UCI to the high-layer processor. The PUSCH receiver 1008 may provide the received transport block to the high-layer processor 1001. The UL receiver 1003 may also sense the downlink channel on which the DL transmitter 1002 will perform downlink transmission.

[0163] Figure 11FIG. 0 is a block diagram illustrating a particular implementation of UE 1102 (an example of UE 102). UE 1102 may include a high layer processor 1111, a UL transmitter 1113, a DL receiver 1112, and an antenna 1114. The UL transmitter 1113 may include a PUCCH transmitter 1117 and a PUSCH transmitter 1118. The DL receiver 1112 may include a PDCCH receiver 1115 and a PDSCH receiver 1116. The high layer processor 1111 may manage the behavior of the physical layer (the behavior of the UL transmitter and the DL receiver, LBT, etc.) and provide high layer parameters to the physical layer. The high layer processor 1111 may obtain transport blocks from the physical layer. The high layer processor 1111 may send to / obtain from the high layer of the UE high layer messages such as common and dedicated RRC messages and / or MAC messages. The high layer processor 1111 may also set and / or store high layer parameters carried by the high layer messages. The high layer processor 1111 may provide a transport block to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1117. The Dl receiver 1112 may receive multiplexed downlink physical channels and downlink physical signals via a receiving antenna and demultiplex them. The PDCCH receiver 1115 may provide DCI to the high layer processor. The PDSCH receiver 1116 may provide the received transport block to the high layer processor 1111. The DL receiver 1112 may also sense an uplink channel on which the UL transmitter 1113 will perform an uplink transmission.

[0164] For downlink data transmission, UE 1102 may attempt blind decoding of one or more PDCCH (also referred to as control channel) candidates. This process is also referred to as monitoring of the PDCCH. The PDCCH may carry DCI formats for scheduling the PDSCH (also referred to as the shared channel or data channel). gNB 1060 may transmit the PDCCH and the corresponding PDSCH in a downlink time slot. When a PDCCH is detected in a downlink time slot, UE 1102 may receive the corresponding PDSCH in the downlink time slot. Otherwise, UE 1102 may not perform PDSCH reception in the downlink time slot.

[0165] Figure 12An example of a control resource element and a reference signal structure is shown. In the frequency domain, a control resource set can be defined as a set of physical resource blocks (PRBs). For example, a control resource set can include PRBs #i to PRB #i+3 in the frequency domain. A control resource set can also be defined as a set of OFDM symbols in the time domain. A control resource set can also be referred to as the duration of the control resource set or simply as the control resource set duration. For example, a control resource set can include three OFDM symbols in the time domain, i.e., OFDM symbol #0 to OFDM symbol #2. The UE 102 can monitor the PDCCH in one or more control resource sets. The PRB set can be configured for each control resource set via dedicated RRC signaling (e.g., via dedicated RRC reconfiguration). The control resource set duration can also be configured for each control resource set via dedicated RRC signaling.

[0166] In Figure 12 In the shown control resource element and reference signal structure, a control resource element is defined as a set of resource elements (REs). Each control resource element includes all the REs (i.e., 12 REs) within a single OFDM symbol and within a single PRB (i.e., 12 consecutive subcarriers). The REs to which the reference signal (RS) is mapped can be counted as those REs, but the REs of the RS are not available for PDCCH transmission, and the PDCCH is not mapped on the REs of the RS.

[0167] Multiple control resource elements can be used for the transmission of a single PDCCH. In other words, a PDCCH can be mapped to the REs included in multiple control resource elements. Figure 12 An example of the UE 102 performing blind decoding on PDCCH candidates when multiple control resource elements located at the same frequency carry a PDCCH is shown. The RS for PDCCH demodulation can be included in all the resource elements to which the PDCCH is mapped. The REs for the RS may not be available for PDCCH transmission or the corresponding PDSCH transmission.

[0168] Figure 13 An example of the multiplexing of a control channel and a shared channel is shown. The start and / or end position of the PDSCH can be indicated via the scheduling PDCCH. More specifically, the DCI format of the scheduled PDSCH can include an information field for indicating the start and / or end position of the scheduled PDSCH.

[0169] UE 102 may include a high-layer processor configured to obtain common and / or dedicated high-layer messages. The common and / or dedicated high-layer messages may include system information and / or high-layer configuration / reconfiguration information. Based on the system information and / or high-layer configuration, UE 102 performs physical layer reception and / or transmission procedures. UE 102 may also include a PDCCH reception circuit configured to monitor the PDCCH. The PDCCH may carry a DCI format for scheduling the PDSCH. In addition and / or alternatively, the PDCCH may carry a DCI format for scheduling the PUSCH. UE 102 may also include a PDSCH reception circuit configured to receive the PDSCH when a corresponding PDCCH is detected. UE 102 may also include a PUCCH transmission circuit configured to transmit a PUCCH carrying HARQ-ACK feedback related to the PDSCH. In addition and / or alternatively, UE 102 may also include a PUSCH transmission circuit configured to transmit the PUSCH when a corresponding PDCCH is detected.

[0170] gNB 160 may include a high-layer processor configured to send common and / or dedicated high-layer messages. The common and / or dedicated high-layer messages may include system information and / or high-layer configuration / reconfiguration information. Based on the system information and / or high-layer configuration, gNB 160 performs physical layer reception and / or transmission procedures. gNB 160 may also include a PDCCH transmission circuit configured to transmit the PDCCH. The PDCCH may carry a DCI format for scheduling the PDSCH. In addition and / or alternatively, the PDCCH may carry a DCI format for scheduling the PUSCH. gNB 160 may also include a PDSCH transmission circuit configured to transmit the PDSCH when transmitting the corresponding PDCCH. gNB 160 may also include a PUCCH reception circuit configured to receive a PUCCH carrying HARQ-ACK feedback related to the PDSCH. In addition and / or alternatively, gNB 160 may also include a PUSCH reception circuit configured to receive the PUSCH when a corresponding PDCCH is detected.

[0171] UE 102 may monitor PDCCH candidates in a control resource set. The PDCCH candidate set may also be referred to as a search space. The control resource set may be defined by a set of PRBs in the frequency domain and a duration in terms of OFDM symbols in the time domain.

[0172] For each serving cell, higher layer signaling (such as a common RRC message or a UE-specific RRC message) may configure one or more PRB sets for PDCCH monitoring for UE 102. For each serving cell, higher layer signaling (such as a common RRC message or a UE-specific RRC message) may also configure the control resource set duration for PDCCH monitoring for UE 102.

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

[0174] For each serving cell for which the UE is configured to monitor the PDCCH and for each DCI format having a CRC scrambled by a C-RNTI, SPS-RNTI, and / or grant-free RNTI, the UE is configured to be associated with a control resource set. These associations may include an association with a set of control resource sets via the higher layer parameter DCI-to-CORESET-map. For each control resource set in the set of control resource sets, these associations may include: an association with the number of PDCCH candidates for each CCE aggregation level L via the higher layer parameter CORESET-candidates-DCI; an association with the PDCCH monitoring periodicity for k p time slots via the higher layer parameter CORESET-monitor-period-DCI; an association with the PDCCH monitoring offset for o p time slots via the higher layer parameter CORESET-monitor-offset-DCI, where 0 <= o p < k p; and the association of the PDCCH monitoring pattern in a time slot with the high-layer parameter CORESET-monitor-DCI-symbolPattern, where the PDCCH monitoring pattern indicates the first symbol of the control resource set in the time slot for PDCCH monitoring. If UE 102 is configured with the high-layer parameter CORESET-monitor-DCI-symbolPatten, UE 102 may assume that non-time-slot-based scheduling is configured in addition to time-slot-based scheduling. If UE 102 is not configured with the high-layer parameter CORESET-monitor-DCI-symbolPatten, UE 102 may assume that non-time-slot-based scheduling is not configured and only time-slot-based scheduling is configured.

[0175] Figure 14 shows the PDCCH monitoring occasion for time-slot-based scheduling (also referred to as type A resource allocation). The PDCCH monitoring occasion can be the OFDM symbol for configuring PDCCH monitoring through search space configuration. A search space set can be identified for a combination of a control resource set, DCI format (or a group of DCI formats including DCI formats with the same DCI payload size). In Figure 14 the example shown, two search space sets are shown - search space set #0 and search space set #1. Both search space set #0 and search space set #1 are associated with the same CORESET. The configuration of the CORESET (such as CORESET-start-symb, CORESET-time-duration, CORESET-freq-dom, CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-StateRefld) applies to both search space set #0 and search space set #1. For example, the CORESET-time-duration set to 3 symbols applies to both of these search space sets. Search space set #0 can be associated with a specific DCI format (such as DCI format 1, fallback DCI format), and search space set #1 can be associated with another specific DCI format (such as DCI format 2, regular DCI format). For search space set #0, the high-layer parameter CORESET-monitor-period-DCI is set to 2 time slots, and for search space set #1, the high-layer parameter CORESET-monitor-period-DCI is set to 1 time slot. Thus, DCI format 1 can be potentially transmitted and / or monitored every 2 time slots, while DCI format 2 can be potentially transmitted and / or monitored every time slot.

[0176] Figure 15Shows the PDCCH monitoring occasion for non-slotted scheduling. In Figure 15 the example shown, two search space sets are shown - search space set #2 and search space set #3. Both search space set #2 and search space set #3 are associated with the same CORESET. This CORESET may or may not be the same CORESET as Figure 15 in. The higher layer parameter CORESET-monitor-period-DCI for search space set #2 and search space set #3 is set to 1 slot.

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

[0178] A control channel element may include 6 resource element groups (REGs), where one resource element group is equal to one resource block on one OFDM symbol. In a time-first manner, starting from the first OFDM symbol in the control resource set and with the resource block numbered 0 being the smallest, the resource element groups within the control resource set are numbered in ascending order. The UE may be configured with multiple control resource sets. Each control resource set may be associated with only one CCE-to-REG mapping. The CCE-to-REG mapping of the control resource set may be interleaved or non-interleaved, configured by the higher layer parameter CORESET-CCE-REG-mapping-type. The REG bundle size is configured by the higher layer parameter CORESET-REG-bundle-size. For non-interleaved CCE-to-REG mapping, the REG bundle size is 6. For interleaved CCE-to-REG mapping, when CORESET-time-duration is set to 1, for the CORESET, the REG bundle size is 2 or 6, and when CORESET-time-duration N CORESET 符号 is set to be greater than 1, for the CORESET, the REG bundle size is N CORESET 符号 or 6. The UE may assume that: if the higher layer parameter CORESET-precoder-granularity is equal to the CORESET-REG-bundle-size, the same precoding is used in the frequency domain within the REG bundle; and if the higher layer parameter CORESET-precoder-granularity is equal to the number of consecutive RBs in the frequency domain within the CORESET, the same precoding is used in the frequency domain for all REGs within the consecutive RBs in the CORESET.

[0179] Each control resource set includes a set of CCEs numbered from 0 to N CCE,p,kp -1, where N CCE,p,kp is the number of CCEs in control resource set p within monitoring period k p . The set of PDCCH candidates monitored by the UE is defined according to the PDCCH UE-specific search space. The PDCCH UE-specific search space S (L) kp for CCE aggregation level L is defined by a set of PDCCH candidates for CCE aggregation level L. L may be one of 1, 2, 4, and 8.

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

[0181] In order to decode the PDSCH based on the detected PDCCH, the UE can be configured with any of the higher layer parameters: rate-match-PDSCH-resource-set including one or more pairs of reserved RBs (higher layer parameter rate-match-PDSCH-resource-RBs, which is also referred to as bitmap-1) and the reserved symbols applicable to the reserved RBs (higher layer parameter rate-match-PDSCH-resource-symbols, which is also referred to as bitmap-2); rate-match-resources-v-shift including LTE-CRS-vshift; rate-match-resources-antenna-port including 1, 2, or 4 ports of the LTE-CRS antenna port;

[0182] rate-match-CORESET including the CORESET-ID of the CORESET configured for the UE 102 to monitor. The UE 102 may have to determine the PDSCH RE mapping according to the provided set of rate matching configurations. To decode the PDSCH, the UE 102 rates match the REs around the detected PDCCH corresponding to the scheduled PDSCH. The UE 102 may not expect to handle the case where there is an overlap (even partial overlap) of the PDSCH DMRS REs, where any RE is indicated by the rate matching configurations rate-match-PDSCH-resource-set and rate-match-resources-v-shift and rate-match-resources-antenna-port and rate-match-CORESET.

[0183] If the UE 102 receives a PDSCH without receiving the corresponding PDCCH, or if the UE 102 receives a PDCCH indicating the release of an SPS PDSCH, the UE 102 may generate a corresponding HARQ-ACK information bit. If the higher layer parameter PDSCH-CodeBlockGroupTransmission is not provided to the UE 102, the UE 102 may generate one HARQ-ACK information bit for each transport block. It is expected that the UE 102 will not be instructed to transmit HARQ-ACK information for more than two SPS PDSCH receptions in the same PUCCH. For each physical cell group, the UE 102 may be configured with a higher layer parameter pdsch-HARQ-ACK-Codebook indicating the type of PDSCH HARQ-ACK codebook. The PDSCH HARQ-ACK codebook may be semi-static (also referred to as type 1 HARQ-ACK codebook) or dynamic (also referred to as type 2 HARQ-ACK codebook). This may apply to both CA and non-CA operations and may correspond to the L1 parameter "HARQ-ACK codebook".

[0184] The UE 102 may report HARQ-ACK information for the corresponding PDSCH reception or SPS PDSCH release only in the HARQ-ACK codebook, and the UE transmits the HARQ-ACK information in a time slot indicated by the value of the PDSCH-to-HARQ feedback timing indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1). If the UE 102 successfully receives the PDCCH or SPS PDSCH release, the value of the corresponding HARQ-ACK information bit may be set to ACK substantially. If the UE 102 does not successfully receive (i.e., fails to receive) the PDCCH or SPS PDSCH release, the value of the corresponding HARQ-ACK information bit may be set to NACK substantially. The UE 102 may report the NACK value of the HARQ-ACK information bit in the HARQ-ACK codebook, and the UE transmits the NACK value in a time slot not indicated by the value of the PDSCH-to-HARQ feedback timing indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1). If the higher layer parameter pdsch-AggregationFactor is provided to the UE 102, is the value of pdsch-AggregationFactor, otherwise, the UE 102 may report HARQ-ACK information only for the last time slot among

[0185] If the UE reports HARQ-ACK information only for SPS PDSCH release or only for PDSCH reception in the PUSCH or PUCCH within the M A,C timing for candidate PDSCH reception (scheduled by DCI format 1_0 and having a counter DAI field value of 1 on the PCell), the UE may determine a HARQ-ACK codebook for only SPS PDSCH release or only for PDSCH reception, e.g., a 1-bit HARQ-ACK codebook. Otherwise, the HARQ-ACK codebook may be more than 1 bit.

[0186] In some cases, the HARQ-ACK information bit may be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception. For example, if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static, the UE 102 may report a NACK value for the HARQ-ACK information bit in the HARQ-ACK codebook, and the UE transmits this NACK value in a time slot not indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1).

[0187] Another case where the HARQ-ACK information bit may be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception is: if the timing for candidate PDSCH reception is in response to a PDCCH with a DCI format (e.g., DCI format 1_1), and if the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates reception of two transport blocks, when the UE receives a PDSCH with one transport block, the HARQ-ACK information is associated with the first transport block, and if the higher layer parameter harq-ACK-SpatialBundlingPUCCH is not provided, the UE 102 may generate a NACK for the second transport block, and if the higher layer parameter hharq-ACK-SpatialBundlingPUCCH is provided, HARQ-ACK information with an ACK value for the second transport block may be generated.

[0188] Another case where the HARQ-ACK information bit can be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception is as follows: If UE 102 is configured by a higher layer parameter maxNrofCodeWordsScheduledByDCI to receive two transport blocks for the active DL BWP of serving cell c, and if UE 102 receives one transport block, then UE 102 can assume an ACK for the second transport block.

[0189] Another case where the HARQ-ACK information bit can be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception is that UE 102 can be set to the NACK value of any HARQ-ACK information corresponding to PDSCH reception or SPS PDSCH release scheduled by a DCI format (e.g., DCI format 1_0 or DCI format 1_1) in the HARQ-ACK codebook, and UE 102 detects this NACK value in a PDCCH monitoring occasion that is after the PDCCH monitoring occasion in which UE detects the DCI format (e.g., DCI format 1_0 or DCI format 1_1) scheduling PUSCH transmission.

[0190] NR can support code block group-based transmission for PDSCH and PUSCH. If a higher layer parameter PDSCH-CodeBlockGroupTransmission for the serving cell is provided to UE 102, UE 102 can receive a PDSCH including code block groups (CBGs) of a transport block, and UE 102 can be provided with a higher layer parameter maxCodeBlockGroupsPerTransportBlock, which indicates the maximum number of CBGs for generating corresponding HARQ-ACK information bits for the reception of the transport block for the serving cell, where for the number of C code blocks (CBs) in the transport block, UE 102 can determine the number of CHGs as

[0191] For CBG-based PDSCH reception, if UE 102 successfully decodes all the CGs in a given CBG of a TB, the value of the HARQ-ACK information bit corresponding to the CBG can be substantially set to ACK. If UE 102 fails to successfully decode (i.e., fails to decode) at least one CG in a given CBG of a TB, the value of the HARQ-ACK information bit corresponding to the CBG can be substantially set to NACK. Additionally, in some cases, the HARQ-ACK information bit for a given CBG can be automatically set to a fixed value (e.g., NACK or ACK) without involving the reception of the associated CB.

[0192] For example, the HARQ-ACK codebook includes HARQ-ACK information bits, and if for a transport block UE 102 can generate a NACK value for the last HARQ-ACK information bit of the transport block in the HARQ-ACK codebook.

[0193] Another case where the HARQ-ACK information bit for a CBG is automatically set to ACK without involving the reception of the associated CB is that if UE 102 generates a HARQ-ACK codebook in response to a retransmission of a transport block that corresponds to the same HARQ process as the previous transmission of the transport block, UE 102 can generate an ACK for each CBG that UE 102 correctly decoded in the previous transmission of the transport block.

[0194] Yet another case where the HARQ-ACK information bit for a CBG is automatically set to a certain value without involving the reception of the associated CB is that if UE 102 receives a PDSCH or SPS PDSCH scheduled by a PDCCH with a DCI format (e.g., DCI format 1_0), or UE detects an SPS PDSCH release, and if UE is configured with a higher layer parameter pdsch-HARQ-ACK-Codebook = semi-static, UE can repeat times the HARQ-ACK information for the transport block in the PDSCH or for the SPS PDSCH release, respectively, for generating HARQ-ACK information bits.

[0195] The 5G NR system can be the operationally licensed spectrum owned by cellular operators. In addition and / or alternatively, the 5G NR system can operate in the unlicensed spectrum as a supplementary tool for the operator to enhance the services provided by the operator. NR-based unlicensed access (NR-U) can be applicable to unlicensed bands below 6 GHz and above 6 GHz (e.g., 5 GHz, 37 GHz, 60 GHz). The NR-U cell can operate in the TDD band together with an LTE-based anchor cell or an NR-based anchor cell (i.e., a stand-alone NR cell). In addition, independent operation of NR-U in the unlicensed spectrum is also possible.

[0196] To ensure fair coexistence with another NR-U node and / or another radio access technology (RAT) node such as a wireless LAN node, the gNB 160 and / or the UE 102 may have to perform a listen-before-talk (LBT) process before its transmission. The LBT process is also referred to as a channel access process. There can be several types of channel access (CA) processes.

[0197] Figure 16 A first type of channel access process is shown. The first type of channel access process can be used for downlink transmissions including PDSCH and PDCCH. After first sensing that the channel is idle during the CA slot duration of the deferral duration T d , the gNB 160 can transmit a transmission including PDSCH and PDCCH on the carrier on which it has performed an NR-U cell transmission; and after the counter N is zero in step 4. Adjust the counter N by sensing the channel according to steps S1 to S6 to obtain an additional CA slot duration. In step S1, the gNB 160 can set N = N 初始 , where N 初始 is a random number uniformly distributed between 0 and CW p and go to step S4. In step 2, if N > 0 and the gNB 160 selects to decrement the counter, the gNB160 can set N = N - 1. In step S3, the gNB 160 can sense the channel within the additional CA slot duration, and if the channel is idle within the additional CA slot duration, go to step S4, otherwise go to step S5. In step S4, if N = 0, the gNB 160 can stop, otherwise go to step S2. In step S5, the gNB 160 can sense the channel until a busy CA slot is detected within the additional delay duration T d or all slots within the additional delay time T d are idle. In step S6, if within the additional delay duration T dIf the channel is sensed to be idle during all CA time slot durations in , gNB 160 may proceed to step S4; otherwise, it proceeds to step S5.

[0198] Figure 17 illustrates an example of the transmission delay. If gNB 160 does not transmit a transmission including PDSCH / PDCCH on the carrier on which it performs NR-U cell transmission after step 4 in this process, then if when gNB 160 is ready to transmit PDSCH / PDCCH, at least during the CA time slot duration T sl the channel is sensed to be idle, and if during all CA time slot durations in the delay duration T d immediately preceding this transmission the channel has been sensed to be idle, then gNB160 may transmit a transmission including PDSCH / PDCCH on the carrier. If when gNB160 senses the channel for the first time after being ready to transmit, the channel is not sensed to be idle during the CA time slot duration T sl or if the channel is not sensed to be idle during any CA time slot duration in the delay duration T d immediately preceding this expected transmission, then after the channel is sensed to be about to be idle during the CA time slot duration in the delay duration T d gNB 160 enters step S1. The delay duration T d may include a duration T f = 16 us, followed by m p consecutive CA time slot durations, where each time slot duration is T sl = 9 us, and T f includes an idle CA time slot duration T f at the start of T sl . If gNB 160 senses the channel during the CA time slot duration and the power detected by gNB 160 within the CA time slot duration is less than the energy detection threshold X 阈值 for at least 4 us, then the time slot duration T sl may be considered idle.

[0199] Otherwise, the CA time slot duration T sl may be considered busy. By using the above transmission delay, more than one cell whose locations are geometrically separated can successfully obtain channel access simultaneously, and thus frequency reuse between cells can be achieved.

[0200] is the contention window. CW p adjustment may be performed by gNB 160. CW 最小,p and CW最大,p m may be derived based on a channel access priority level associated with gNB transmission p and CW 最小,p and CW 最大,p .

[0201] Figure 18 An example of a channel access priority level for downlink transmission is shown. In this example, there are 4 levels, and a smaller index may correspond to a higher priority. For each level, a set of parameters for the channel access process is defined. The parameter set for level p may include m p and CW 最小,p and CW mcot,p , T mcot,p and the allowed CW p size, where T mcot,p is referred to as the maximum channel occupancy time (MCOT).

[0202] gNB 160 that may not be allowed to obtain channel access with priority level p may not continuously transmit on the carrier on which it performs NR-U cell transmission for a period exceeding T mcot,p .

[0203] Similarly, UE 102 may use a first type of channel access process for uplink transmission including PUSCH and / or PUCCH. The above channel access process including steps S1 to S6 may be used together with "gNB 160" replaced by "UE 102", "PDSCH / PDCCH" replaced by "PUSCH / PUCCH / SRS", and the uplink channel access priority level. Figure 19 An example of a channel access priority level for uplink transmission is shown. When the first type of channel access process is used for uplink transmission, it may also be referred to as a type 1 UL channel access process.

[0204] Figure 20 A second type of channel access process is shown. The second type of channel access process may be used for downlink transmission including discovery signal transmission and not including PDSCH. The discovery signal may include SS / PBCH, CSI-RS, and / or control resource set. Compared with the first type of channel access process, the second type of channel access process may make channel access easier because the discovery signal may not occupy a long transmission duration compared with PDSCH transmission. gNB 160 may transmit a transmission including the discovery signal but not including PDSCH on the carrier on which it has performed NR-U cell transmission immediately after sensing that the channel is idle for at least a sensing interval of T drs = 25 us and if the transmission duration is less than 1 ms. T drs may include a duration T f= 16 us, followed by a CA slot duration T sl = 9 us, and T f includes an idle CA slot duration T f at the start of T sl . If the carrier is sensed idle during the slot duration of T drs , the carrier is considered idle for T drs .

[0205] Figure 21 shows a third type of channel access procedure. The channel sensing scheme of the third type of channel access procedure is almost the same as that of the second type of channel access procedure. The third type of channel access procedure can be used for uplink transmission, and this uplink transmission will be transmitted within the COT obtained on the gNB 160 side through the first type of channel access procedure. In this example, the gNB160 performs the first type of channel access procedure just before the common control PDCCH (CC-PDCCH) transmission. The CC-PDCCH can also be referred to as a PDCCH with a CRC scrambled by a common control RNTI (CC-RNTI). In the DCI format carried by the CC-PDCCH, several bit fields can be included, and the several bit fields include bit fields for indicating "UL offset" and "UL duration". If the UL offset l and duration d are indicated by the CC-PDCCH of subframe n, the UE 102 does not need to receive any downlink physical channels and / or physical signals in slots n + l + i, where i = 0, 1,.., d - 1, and those slots may have to be covered by the MCOT obtained on the gNB160 side through the channel access for CC-PDCCH transmission. If the UE uses the type 2 channel access procedure for transmission including PUSCH, the UE may be allowed to transmit the transmission including PUSCH immediately after sensing the channel idle for at least T = short_ul 25 us or T = short_ul 16 us sensing intervals. They can be considered the same type of channel access procedure but with different durations. Alternatively, the type 2 channel access procedure where T short_ul = 25 us can also be referred to as the uplink type 2A channel access procedure, and the type 2 channel access procedure where T short_ul = 16 us can also be referred to as the uplink type 2B channel access procedure. In this case, they can be considered two different types of channel access procedures. T short_ul can include a duration T f = 16 us, followed by a CA slot duration T sl = 9 us, and T f includes in T fIdle CA slot duration T at the start sl If the carrier is sensed idle during the slot duration of T short_ul then the carrier is considered idle for T short_ul . The third type of channel access procedure may also be referred to as a type 2 UL channel access procedure. Note that another type of PDCCH for slot n (e.g., PDCCH with DCI formats 0_0, 0_1, 0_2, 0_3, 1_0, 1_1, 1_2, 1_3) may also indicate "UL offset" and "UL duration". In this case, if configured, the UE may also be allowed to use the third type of channel access procedure.

[0206] Figure 22 FIG. shows a fourth type of channel access procedure. The channel sensing scheme of the fourth type of channel access procedure is almost the same as that of the second type of channel access procedure and the third type of channel access procedure. The fourth type of channel access procedure can be used for downlink transmission that includes PUSCH but does not include PDSCH and will be transmitted within the COT obtained at the UE 102 side through the first type of channel access procedure. If the PUSCH transmission indicates COT sharing, the gNB 160 may be allowed to transmit a transmission that includes PDCCH but does not include PDSCH on the same carrier immediately after sensing the channel idle for a sensing interval of at least T = pdcch 25 us. If the duration of the PDCCH is less than or equal to two OFDM symbol lengths, it should contain at least downlink feedback information (DFI) and a UL grant for the UE that received the PUSCH transmission indicating COT sharing from it. T pdcch includes a duration T f = 16 us, followed immediately by a slot duration T sl = 9 us, and T f includes an idle slot duration T f at the start of T sl . If the channel is sensed idle during the slot duration of T pdcch then the channel is considered idle within T pdcch .

[0207] To avoid collisions with transmissions from other nodes, the size of the contention window (CW) may be changed according to the number of collisions or equivalent occurrences. If a collision is observed at a node, the node may have to increase the CW size. If no collision is observed, the node may be allowed to decrease the CW size. Figure 23Shows an example of CW size adjustment. This example assumes that the number of available CW sizes is 7, i.e., CW#0 to CW#6. If a collision is observed, the CW size is increased to the CW size with the next higher index, except for CW size 最大 , in which case the CW size remains as CW 最大 . If no collision is observed, the CW size can be backed off to CW 最小 , regardless of the previous CW size.

[0208] A possible metric for the gNB's decision on whether a collision has occurred for the PDSCH can be the HARQ-ACK feedback from the UE 102. Another possible metric for the gNB's decision on whether a collision has occurred in the PDCCH can be the PUSCH from the UE 102. For the uplink, a possible metric for the UE's decision on whether a collision has occurred for the PUSCH can be whether an uplink retransmission is requested.

[0209] Figure 24 Shows an example of LBT for transmission using directional beams. The gNB 160 can perform transmission beam scanning using multiple narrow Tx beams (e.g., Tx beam #1, #2, and #3). Immediately before transmitting a signal using any Tx beam, the gNB 160 may have to perform LBT. In this example, the gNB 160 performs channel sensing by using a wider beam (Rx beam #0) in the horizontal plane (e.g., an omnidirectional Rx beam). LBT parameters (counters, CWS, channel access classes, COT, etc.) can be managed for each node. For example, counters and CWS can be managed for each node. In this case, once the counter reaches zero, the gNB 160 can be allowed to perform transmission using any one of the Tx beams, and a single CWS is maintained by referring to the collisions (e.g., NACKs) on all Tx beams.

[0210] In addition and / or alternatively, some links can be defined from the Tx beams for transmission to the Rx beams for channel sensing for transmission, or vice versa. For example, each of Tx beams #1, #2, and #3 corresponds to Rx beam #0. In this case, the LBT parameters can be managed for each Rx beam. For example, counters and CWS can be managed for each node. Once the counter for a given Rx beam reaches zero, gNB 160 can be allowed to perform transmission using any one of the Tx beams linked to the given Rx beam, and a single CWS for the given Rx beam is maintained by referring to the collisions on all Tx beams linked to the given Rx beam. The COT can be graphed according to the Rx beam. Within the COT of a given Rx beam, gNB 160 can be allowed to perform transmission using any one of the Tx beams corresponding to the given Rx beam, subject to Cat-1 or Cat-2 LBT. Alternatively, the counters or CWS can be managed for the Rx beams, while other parameters can be managed for the nodes. For example, the counters are managed for each Rx beam, and once the counter reaches zero, gNB 160 can be allowed to perform transmission using any one of the Tx beams linked to the Rx beam. On the other hand, for the CWS adjustment for Rx beam #0, the collisions on all Tx beams (including Tx beams #1, #2, and #3 and any other beams of gNB 160) can be considered.

[0211] Cat-1 LBT is a channel access procedure without channel sensing. Cat-2 LBT is a channel access procedure with single channel sensing. Cat-2 LBT can also be referred to as type 2 channel access procedure. According to the channel sensing slot length, Cat-2 LBT can be further divided into two types. The first is Cat-2 LBT with a 25 μs channel sensing slot, and the other is Cat-2 LBT with a 16 μs channel sensing slot. Cat-1 LBT and Cat-2 LBT can be allowed only inside the COT. If the gap length starting from the timing of channel idle is equal to 16 μs, Cat-2 LBT with a 16 μs channel sensing slot can be allowed. If the gap length starting from the timing of channel idle is equal to or longer than 25 μs, Cat-2 LBT with a 25 μs channel sensing slot can be allowed. Cat-3 LBT is a channel access procedure with random backoff with a fixed CW size. Cat-4 LBT is a channel access procedure with random backoff with an adaptive CW size. Cat-4 LBT can also be referred to as type 1 channel access procedure.

[0212] The Tx beam may correspond to some physical channels or physical signals. For example, each Tx beam may correspond to a corresponding quasi - co - location (QCL) assumption source. The QCL assumption source may include SS / PBCH, CSI - RS, PT - RS, NR - U discovery signals / channels that may include SS / PBCH, etc. Therefore, it should be noted that the above "Tx beam" can be interpreted as the corresponding physical channel or physical signal. Alternatively and / or in addition, the Tx beam may correspond to a certain transmission antenna configuration, such as the weight vector for a transmission antenna array. In this case, the above "Tx beam" can be interpreted as the corresponding antenna configuration. Similarly, the Rx beam may correspond to a certain receiving antenna configuration, such as the weight vector for a receiving antenna array. In this case, the above "Rx beam" can be interpreted as the corresponding antenna configuration.

[0213] If the beamforming gain for channel sensing is different from the beamforming gain for the corresponding transmission, it may be necessary to adjust the threshold of channel sensing. For example, the antenna gain ratio between the Rx antenna configuration and the Tx antenna configuration in a given direction (e.g., the direction to the target UE, the center direction of the main lobe of the Tx beam, the peak direction of the main lobe of the Tx beam) can be used for threshold adjustment. More specifically, if the antenna gain in the center direction of Tx beam #1 is 20 dBi, and the antenna gain in the same direction of Rx beam #0 (which is linked to Tx beam #1) is 2 dBi, then compared with the non - directional transmission case, the threshold of channel sensing using Rx beam #0 can be reduced by 18 dBi.

[0214] Figure 25An example of LBT for transmission using directional beams is shown. gNB 160 is capable of transmitting using multiple narrow Tx beams (e.g., Tx beam #1, #2, and #3), and receiving using multiple narrow Rx beams (e.g., Rx beam #1, #2, and #3). Immediately before transmitting a signal using any Tx beam, gNB 160 may have to perform LBT. Some links (e.g., 1-to-1 mapping) from the Tx beam used for transmission to the Rx beam used for channel sensing for transmission may be defined, or vice versa. For example, Tx beam #1, #2, and #3 respectively correspond to Rx beam #1, #2, and #3. Immediately before transmitting using a given Tx beam, LBT may have to be performed using the Rx beam linked to the given Tx beam. In other words, once gNB 160 obtains a channel by using LBT with a given Rx beam, gNB 160 may be allowed to perform transmission using the Tx beam linked to the given Rx beam. LBT parameters can be managed for each Tx beam. The COT can be graphed according to the Tx beam. Within the COT of a given Tx beam, gNB 160 may be allowed to use the given Tx beam to perform transmission subject to Cat-1 or Cat-2 LBT. Additionally, some LBT parameters can be managed for each node. For example, a single counter can be generated and updated for each Tx beam, while the single CWS for each node can be adjusted by considering collisions on all Tx beams. The COT can be graphed according to the node. Within the COT, gNB 160 may be allowed to use any one of the Tx beams to perform transmission subject to Cat-1 or Cat-2 LBT.

[0215] Figure 26An example of sub-band configuration is shown. The NR band may include one or more NR carriers (also simply referred to as carriers). A carrier may include one or more BWPs. BWP#0 (also referred to as the initial BWP or initial DL BWP, which may be configured by the master information block (MIB), system information block type 1 (SIB1), or the equivalent of the PCell) may have a bandwidth of 20 MHz. Other BWPs may have a bandwidth that is a multiple of 20 MHz. Each sub-band may include a bandwidth of 20 MHz or a multiple of 20 MHz and is defined within the BWP. BWP#0 may consist of a single 20-MHz sub-band. Any other BWP may consist of one or more sub-bands. A sub-band may be the unit of frequency scheduling. A sub-band may also be referred to as a sub-channel, channel access bandwidth, etc. The higher-layer configuration regarding the BWP may include the configuration of sub-bands within the BWP. Alternatively, the sub-band may be configured by using the frequency-domain resource allocation in the CORESET configuration. A sub-band may be the upper limit of the resources that can be scheduled by a single DCI. In other words, the PDSCH / PUSCH resource allocation is defined within the sub-band, rather than across the sub-band boundary. A sub-band may be the unit of LBT. A sub-band may be the unit of CORESET configuration. The CORESET frequency resource allocation is defined within the sub-band, rather than across the sub-band boundary.

[0216] In addition and / or alternatively, the CORESET configuration may contain information for indicating the frequency repetition of the CORESET. For example, if the CORESET configuration contains an information element for frequency repetition, the frequency repetition of the CORESET may be considered enabled. If the CORESET configuration does not contain an information element for frequency repetition, the frequency repetition of the CORESET may be considered disabled. The information element for frequency repetition may include one or more of the following: 1) the frequency-domain repetition factor (i.e., the number of frequency-domain repetitions), 2) the frequency-domain interval between adjacent repetitions, etc. If UE 102 is configured to have enabled repetition, UE 102 may assume that the same set of PDCCHs is transmitted in those repeated CORESETs.

[0217] The PDCCH in the CORESET within a given sub-band may be able to schedule only the PDSCH within the same sub-band. For example, the DCI format for scheduling PDSCH / PUSCH in an NR-U cell may include a frequency-domain resource allocation field - [log2(N(N + 1) / 2)] bits, where N may be the size of the bandwidth of the sub-band in which the PDCCH carrying the DCI is detected if the DCI is detected in the UE-specific search space and the requirements for the total number of different DCI sizes are met. Otherwise (e.g., if the DCI is detected in the common search space), N may be the size of the bandwidth of the sub-band corresponding to the initial BWP (i.e., BWP#0). N may be represented by the RB number.

[0218] In a BWP, the gNB 160 may perform channel sensing in each sub-band and may transmit signals (PDCCH, PDSCH, etc.) in the sub-bands on which the gNB 160 successfully obtains channel access. The UE 102 may be able to monitor the PDCCH in multiple CORESETs corresponding to different sub-bands. The gNB 160 may manage the LBT parameters for each sub-band, alternatively for each BWP, or alternatively for each cell. In addition and / or alternatively, some of the LBT parameters may be managed for each sub-band, and other parameters may be managed in different ways (e.g., for each BWP or each cell).

[0219] In a BWP, the UE 102 may perform channel sensing in each sub-band and may transmit signals (PUCCH, PUSCH, etc.) in the sub-bands on which the UE 102 successfully obtains channel access. The gNB 160 may be able to monitor the signals in each sub-band. The UE 102 may manage the LBT parameters for each sub-band, alternatively for each BWP, or alternatively for each cell. In addition and / or alternatively, some of the LBT parameters may be managed for each sub-band, and other parameters may be managed in different ways (e.g., for each BWP or each cell).

[0220] In addition and / or alternatively, the PDCCH in each sub-band may be able to schedule the PDSCH in the entire bandwidth of the BWP. For example, the DCI format for scheduling the PDSCH / PUSCH in an NR-U cell may include a frequency domain resource allocation field - [log2(N(N + 1) / 2)] bits, where N may be the bandwidth size of the active BWP. In a BWP, assuming that the entire bandwidth of the BWP is available for PDSCH / PUSCH transmission, the gNB 160 may prepare the PDSCH / PUSCH. The gNB 160 may perform channel sensing in each sub-band and may transmit the prepared PDSCH only on the sub-bands where LBT is successful. On the sub-bands where LBT fails, the PDSCH resources (e.g., RE or RB) may have to be truncated (i.e., the PDSCH is not mapped to physical resources) so that PDSCH transmission does not occur in those sub-bands. Regarding the PDCCH for scheduling the PDSCH, multiple PDCCHs for scheduling the same PDSCH may be prepared. These PDCCHs may be assumed to be mapped in different sub-bands in the BWP. The PDCCH in the sub-band on which the gNB 160 successfully obtains channel access may be transmitted, while the PDCCH in the sub-band on which the gNB 160 does not successfully obtain channel access may not be transmitted.

[0221] In this case, if gNB 160 obtains channel access in more than one sub-band, UE 102 may detect more than one PDCCH scheduling the same PDSCH. Scheduling the same PDSCH may mean that the DCI in the PDCCH has the same value in each information field and CRC. Alternatively, this may mean that the DCI in the PDCCH indicates the same PDSCH parameter set, e.g., the allocated resources, counter DAI, PUCCH resources, etc. Yet alternatively, this may mean that those PDCCHs are repeated in a repeated CORESET (i.e., a CORESET with frequency-domain repetition). If UE 102 can detect more than one PDCCH scheduling the same PDSCH, the UE may have to discard all but one of these PDCCHs. In other words, only one PDCCH is considered valid, and all other detected PDCCHs are considered invalid. Alternatively, UE 102 may treat those multiple detected PDCCHs as a single detected PDCCH, and the repetition indication for the multiple detected PDCCHs may be applied only once.

[0222] The above principle can be applied to another type of DCI (e.g., DCI format 0_0, 0_1, 2_0, 2_1, 2_2, 2_3) instead of the DCI scheduling the PDSCH. For example, gNB 160 may transmit multiple PDCCHs with DCI format 2_2 in those multiple sub-bands in the BWP. If UE 102 detects multiple PDCCHs with DCI format 2_2 in those multiple sub-bands, the TPC command of only one PDCCH with DCI format 2_2 may be applied, and the TPC commands of other PDCCHs may not be applied.

[0223] The frequency-domain resource allocation field in the DCI in the PDCCH may indicate that the allocated resources (e.g., resource blocks) include resources on the sub-band to which gNB 160 did not actually map the PDSCH due to channel access failure. Without any additional information, UE 102 that detects the DCI may assume that the PDSCH is mapped to the resources in those sub-bands.

[0224] Alternatively, UE 102 may utilize some additional information such that UE 102 can assume that the PDSCH is not mapped to the resources in those sub-bands to perform PDSCH decoding. The additional information may be the result of PDCCH detection in the sub-band. In addition to and / or alternatively, the additional information may be the information provided by the CC-PDCCH or SFI PDCCH. In addition to and / or alternatively, the additional information may be the information provided by DCI format 2_1 (also referred to as the preemption indication).

[0225] Based on the result of PDCCH detection in a sub - band, UE 102 can assume that the PDSCH is not mapped to the resources in those sub - bands to perform PDSCH decoding. More specifically, for example, if UE 102 is configured with repetitions of a CORESET, UE 102 can assume that multiple PDCCHs scheduling a single PDSCH are transmitted in all repetitions of the CORESET. If UE 102 does not detect a PDCCH in a given sub - band, UE 102 can assume that the PDSCH resources scheduled in the sub - band are not available for PDSCH transmission, and the PDSCH is punctured (i.e., ready to be mapped but not actually mapped) on those PDSCH resources. On the other hand, if UE 102 detects a PDCCH in a given sub - band, UE 102 can assume that the scheduled PDSCH resources in the sub - band are available for PDSCH transmission.

[0226] Based on the information provided by the CC - PDCCH or SFI PDCCH, UE 102 can assume that the PDSCH is not mapped to the resources in those sub - bands to perform PDSCH decoding. For example, an SFI PDCCH indicating the slot format (e.g., a PDCCH with DCI format 2_0 or a PDCCH with a DCI format indicating the slot format) can be transmitted in each sub - band of a BWP. Referring to the sub - carrier spacing configuration μ ref Can be configured by a higher - layer parameter. Each SFI PDCCH can indicate the slot format and / or COT structure in the corresponding sub - band to which the SFI PDCCH is mapped.

[0227] Two transmission schemes for PUSCH are supported: codebook-based transmission and non-codebook-based transmission. For codebook-based transmission, the gNB 160 can provide a transmission precoding matrix indication to the UE in the DCI. The UE 102 can use this indication to select a PUSCH transmission precoder from the codebook. For non-codebook-based transmission, the UE 102 can determine its PUSCH precoder based on the broadband SRI field from the DCI. Closed-loop DMRS-based spatial multiplexing for PUSCH is supported. For a given UE102, up to 4-layer transmission is supported. The number of codewords can be one. When transform precoding is used, only single MIMO layer transmission is supported. Transmission durations from 1 to 14 symbols in a time slot are supported. Aggregation of multiple time slots with TB repetition is supported. Two types of frequency hopping are supported, namely, in-slot frequency hopping and, in the case of time slot aggregation, inter-slot frequency hopping. The PUSCH can be scheduled using DCI on the PDCCH, or a semi-static configured grant can be provided via RRC, where two types of operations are supported: the first PUSCH is triggered by DCI, and subsequent PUSCH transmissions follow the RRC configuration and are scheduled on the DCI, or the PUSCH is triggered by data buffering in the transmission buffer of the UE and the PUSCH transmission follows the RRC configuration. In the uplink, the gNB 160 can dynamically allocate resources to the UE 102 via the C-RNTI on the PDCCH. The UE 102 can always monitor the PDCCH to find possible grants for uplink transmission when downlink reception is enabled (activity controlled by DRX at configuration). When CA is configured, the same C-RNTI can be applied to all serving cells.

[0228] The UE may transmit the corresponding PUSCH indicated by the DCI when detecting a PDCCH with configured DCI format 0_0 or 0_1. When detecting DCI format 0_1 with the "UL-SCH indicator" set to "0" and a non-zero "CSI request", where for all CSI reports triggered by the "CSI request" in this DCI format 0_1, the associated "reportQuantity" in CSI-ReportConfig is set to "none", the UE may ignore all fields in this DCI except the "CSI request", and the UE may not transmit the corresponding PUSCH indicated by this DCI format 0_1. For any HARQ process ID in a given scheduled cell, it may not be desirable for the UE to transmit a PUSCH that has a time overlap with another PUSCH. For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to transmit the first PUSCH starting at symbol j by a PDCCH ending at symbol i, it may not be desirable for the UE to be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH ending later than symbol i. It may not be desirable for the UE to be scheduled to transmit another PUSCH during a given HARQ process by DCI format 0_0 or 0_1 scrambled by C-RNTI or MCS-C-RNTI until the expected transmission of the last PUSCH in this HARQ process ends.

[0229] UE 102 can determine the resource block allocation in the frequency domain using the resource allocation field in the detected PDCCH DCI, except for PUSCH transmissions scheduled by RAR UL grant, in which case the frequency domain resource allocation can be determined. Three types of uplink resource allocation schemes, type 0, type 1, and type 2, can be supported. Uplink resource allocation scheme type 0 for PUSCH can be supported only when transform precoding is disabled. For both cases when transform precoding is enabled or disabled, uplink resource allocation schemes type 1 and type 2 for PUSCH can be supported. Uplink resource allocation scheme 3 is supported only for PUSCH in NR-U cells. If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the frequency domain resource allocation field by setting the higher layer parameter resourceAllocation in pusch-Config to "dynamicSwitch", then UE 102 can use the uplink resource allocation type 0, type 1, or type 2 defined by this DCI field. Otherwise, UE 102 can use the uplink frequency resource allocation type defined by the higher layer parameter resourceAllocation. UE 102 can assume that when receiving the scheduling PDCCH with DCI format 0_0, then uplink resource allocation type 1 is used in non-NR-U cells. UE102 can assume that when receiving the scheduling PDCCH with DCI format 0_0, then uplink resource allocation type 2 is used in NR-U cells. If the bandwidth part indicator field is not configured in the scheduling DCI, then the RB indices for uplink type 0, type 1, and type 2 resource allocations can be determined within the active bandwidth part of the UE. If the bandwidth part indicator field is configured in the scheduling DCI, then the RB indices for uplink type 0, type 1, and type 2 resource allocations can be determined within the bandwidth part of the UE indicated by the bandwidth part indicator field value in the DCI. UE 102 can first determine the uplink bandwidth part when detecting the PDCCH intended for UE 102, and then determine the resource allocation within the bandwidth part. The RB numbering starts from the lowest RB in the determined uplink bandwidth part.

[0230] In the uplink resource allocation of type 0, the resource block allocation information can include a bitmap indicating the resource block groups (RBGs) allocated to the scheduled UE 102, where an RBG is a set of consecutive virtual resource blocks defined by the higher layer parameter rbg-Size configured in pusch-Config and the size of the bandwidth part.

[0231] The total number (N RBG ) of RBGs in the uplink bandwidth part i of size PRB can be given by, where the size PRB can be given by given by, where the size of the first RBG can be If then the size of the last RBG can be Otherwise it is P. The size of all other RBGs can be P.

[0232] The size of the bitmap can be N RBG bits, where each RBG has one bitmap bit such that each RBG is addressable. The RBGs can be indexed in increasing order of the frequency of the bandwidth part and starting from the lowest frequency. The order of the RBG bitmap can be such that RBGs 0 to RBG N RBG -1 are mapped from the MSB to the LSB of the bitmap. If the corresponding bit value in the bitmap is 1, the RBG can be allocated to UE 102, otherwise the RBG may not be allocated to UE 102. In frequency range 1, only "almost continuous allocation" can be allowed as the per-component-carrier discontinuous allocation for UL RB allocation for CP-OFDM. In frequency range 2, the per-component-carrier discontinuous allocation for UL RB allocation for CP-OFDM may not be supported.

[0233] In type 1 uplink resource allocation, the resource block allocation information can indicate to the scheduled UE 102 a non-interleaved set of contiguous virtual resource blocks within the active carrier bandwidth part of size PRB, except in the case of decoding DCI format 0_0 in any common search space, in which case the size of the initial bandwidth part can be used. The uplink type 1 resource allocation field can include a resource indication value (RIV) corresponding to the starting virtual resource block (RB 开始 ) and a length L RB for the contiguous allocated resource blocks. The resource indication value can be defined as follows: If then otherwise

[0234] L RB ≥ 1 and it is not possible to exceed When the DCI size of DCI format 0_0 in the USS is derived from an initial BWP of size but applied to another active BWP of size , the uplink type 1 resource block allocation field can include a resource indication value (RIV) corresponding to the starting resource block RB start = 0, K, 2·K,...-1)K and a length L RBS = K, 2·K,...K. The resource indication value can be defined as follows: If then otherwise L' RB = LRB / K , RB' 开始 = RB 开始 / K, and L' RB cannot exceed If then K is the maximum value in the set {1, 2, 4, 8} that satisfies , otherwise K = 1.

[0235] Uplink resource allocation type 2 can only be applied to NR-U cells. The uplink resource allocation of type 2 can be used to indicate one or more interleavings, where each interleaving includes a set of PRBs that locate discrete frequency positions with a common frequency spacing. There are several ways for the uplink resource allocation of type 2, such as the RIV-based scheme (hereinafter referred to as type 2-1) and the bitmap-based scheme (hereinafter referred to as type 2-2).

[0236] The resource allocation information for uplink resource allocation type 2-1 can indicate to the scheduled UE 102 a set of virtual resource blocks RB for interleaved allocation 开始 + l + i·N, where within the effective carrier bandwidth portion of the size of the PRB, for SCS = 15 kHz, and for SCS = 30 kHz, except for the case of decoding DCI format 0_0 in any common search space, in which case the size of the initial bandwidth portion and the value of the SCS of the initial bandwidth portion can be used. Alternatively, the resource allocation information for uplink resource allocation type 2-1 can indicate to the scheduled UE 102 a set of resource blocks (RB <? 开始 - RB 偏移 ) mod N + l + i - N, where within the active carrier bandwidth portion of the size of the PRB and within the active carrier bandwidth portion with RB 偏移 , for SCS = 15 kHz, N = 10, and for SCS = 30 kHz, N = 5; and except for the case of decoding DCI format 0_0 in any common search space, in which case the size of the initial bandwidth portion , the N value for the SCS of the initial bandwidth portion, and the value of RB 偏移 of the initial bandwidth portion can be used.

[0237] The uplink type 2 resource block allocation field in the scheduling grant can include a resource indication value (RIV). For 0 ≤ RIV < N(N + 1) / 2 and l = 0, 1,... L - 1, the resource indication value corresponds to the starting resource block (RB 开始) And a sum value L (L≥1). The resource indication value is defined as follows: If (L - 1) ≤ [N / 2], then RIV = N(L - 1) + RB 开始 ; otherwise RIV = N(N - L + 1) + (N - 1 - RB 开始 ). For RIV≥N(N + 1) / 2, the resource indication value corresponds to the starting resource block (RB 开始 ) and the set of values l defined according to the table, where each entry in the table specifies the corresponding association between the value of RIV - N(N + 1) / 2 and the combination of the starting resource block (RB 开始 ) and the set of l. In this case, the RIV value set to 0 may correspond to the PRB interleaving including the PRB with the lowest PRB index within the active UL BWP. When the DCI size of DCI format 0_0 in USS is derived from an initial BWP of size but applied to another active BWP of size , the uplink type 2 resource block allocation field may include a resource indication value (RIV). For 0≤RIV<N(N + 1) / 2, where the size of the initial bandwidth part is and the value of the initial bandwidth part is and l = 0,…,K - 1,K,…,2K - 1,…K(L' - 1),…,K·L' - 1, the resource indication value corresponds to the starting resource block (RB 开始 ) and the value L (L≥1), where RB' 开始 = RB 开始 / K and L' = L / K. The resource indication value is defined as follows: If (L - 1) ≤ [N / 2], then RIV = N(L - 1) + RB 开始 ; otherwise RIV = N(N - L' + 1) + (N - 1 - RB' 开始 ). L' may not exceed If then K is the maximum value in the set {1,2,4,8} that satisfies ; otherwise K = 1.

[0238] RB 偏移 can be given by a higher layer parameter (such as an RRC parameter) configurable according to the UL BWP. Alternatively, RB 偏移 can be given by the following equation , where is the common resource block, where the bandwidth part starts relative to the common resource block 0. For the subcarrier spacing configuration μ, the common resource blocks in the frequency domain are numbered starting from 0 upwards. The center of subcarrier 0 of the common resource block 0 for the subcarrier spacing configuration μ coincides with "point A". The relationship between the common resource block number in the frequency domain and the resource element (k,l) of the subcarrier spacing configuration μ is given by Given, where k is defined relative to point A such that k=0 corresponds to a subcarrier centered around point A.

[0239] The resource allocation information for uplink resource allocation type 2-1 may indicate to the scheduling UE 102 the resource block set (RB 开始 -RB 偏移 )mod N+1+iN bitmap, where the size within the active carrier bandwidth portion of the PRB and using RBs in the active carrier bandwidth portion 偏移 , for SCS=15kHz, N=10, and for SCS=30kHz, N =5; and Except when decoding DCI format 0_0 in any common search space, in which case the initial bandwidth part can be used The size of the SCS and the N value used for the initial bandwidth part and the RB of the initial bandwidth part 偏移 The resource block allocation information indicates a bitmap of allocation values l, where l = 0, 1, ... N-1. The order of resource block set to bitmap bit mapping is as follows: l = 0 to l = N-1 are mapped to the MSB to LSB of the bitmap respectively. If the corresponding bit value in the bitmap is 1, the resource block set is allocated to the UE, and no other resource block sets are allocated. Alternatively, in uplink resource allocation type 2-2, the resource block allocation information may include a bitmap indicating interleaved allocated resource block sets, each interleaved resource block group (IRBG) including (IRBG 开始 -RB 偏移 )mod N+i·N, where Within the active carrier bandwidth portion of the PRB and offset by RB in the active carrier bandwidth portion, for SCS = 15kHz, N = 10, and for SCS = 30 kHz, N = 5; and Except when decoding DCI format 0_0 in any common search space, in which case the initial bandwidth part can be used The size of the SCS for the initial bandwidth part and the RB for the initial bandwidth part 偏移 The bitmap can be N bits in size, with one bitmap bit for each IRBG, so that each IRBG can be identified by 开始 To address. The bitmap order makes IRBG 开始 =0 to IRBG 开始 =N-1 IRBGs are mapped from the MSB to the LSB of the bitmap. If the corresponding bit value in the bitmap is 1, the IRBG is allocated to the UE, otherwise the RBG is not allocated to the UE.

[0240] As an uplink type 2 resource block allocation scheme, the uplink type 2-1 resources can always be used to schedule all DCI formats for PUSCH. Alternatively, as an uplink type 2 resource block allocation scheme, the uplink type 2-2 resources can always be used to schedule all DCI formats for PUSCH. As another alternative, as an uplink type 2 resource block allocation scheme, the uplink type 2-1 resources can be used to schedule some of the DCI formats in the DCI formats for PUSCH, and the uplink type 2-2 resources can be used to schedule some other DCI formats in the DCI formats for PUSCH. As another alternative, as an uplink type 2 resource block allocation scheme, the uplink type 2-1 resources can be used for a UL BWP with a certain SCS (e.g., 15 kHz), and the uplink type 2-2 resources can be used for a UL BWP with another SCS (e.g., 30 kHz).

[0241] Even when the UE 102 is configured with a BWP wider than 20 MHz (e.g., 40 MHz, 60 MHz, 80 MHz, or 100 MHz), the gNB 160 can schedule the PUSCH mapped within a portion (e.g., 20 MHz) of the BWP. More specifically, even when the gNB 160 configures the UE 102 with a BWP including multiple subbands, the UE 102 can be scheduled with a PUSCH mapped within some but not all of the multiple subbands. Preferably, the PUSCH can be scheduled in the frequency domain of one or more consecutive subbands. The DCI format for scheduling the PUSCH can include a bit field (referred to as a subband allocation field) for indicating one or more subbands (subband set) allocated for PUSCH transmission (i.e., subband allocation). The subband allocation field can be included in all DCI formats for scheduling the PUSCH. Alternatively, the subband allocation field can be included in some of the DCI formats for scheduling the PUSCH, but not included in some other DCI formats for scheduling the PUSCH. For example, the subband allocation field can be included in DCI format 0_1, but not included in DCI format 0_0.

[0242] For at least NR-U cells operating in the 5 GHz spectrum, a 20 MHz UL BWP (e.g., up to 106 RBs for 15 kHz SCS and up to 51 RBs for 30 kHz SCS) may include one sub-band (e.g., sub-band #0), a 40 MHz UL BWP (e.g., up to 216 RBs for 15 kHz SCS and up to 106 RBs for 30 kHz SCS) may include two sub-bands (e.g., sub-band #0 and sub-band #1), a 60 MHz UL BWP (e.g., up to 162 RBs for 30 kHz SCS) may include two sub-bands (e.g., sub-band #0, sub-band #1, and sub-band #2), an 80 MHz UL BWP (e.g., up to 217 RBs for 30 kHz SCS) may include two sub-bands (e.g., sub-band #0, sub-band #1, sub-band #2, and sub-band #3), and a 100 MHz UL BWP (e.g., up to 273 RBs for 30 kHz SCS) may include two sub-bands (e.g., sub-band #0, sub-band #1, sub-band #2, sub-band #3, and sub-band #4). Each of the sub-bands may be a set of contiguous virtual resource blocks. The sub-bands may be indexed within the BWP in increasing order starting from the lowest frequency. There may be no gap between adjacent sub-bands. Alternatively, there may be a gap in the resource block units between adjacent sub-bands. The sub-band size S in the resource block units may depend on the SCS of the active UL BWP. For example, the sub-band size for SCS = 15 kHz may be equal to 108, and the sub-band size for SCS = 30 kHz may be equal to 53.

[0243] Alternatively, the sub - band size S in the resource block unit may depend on the SCS of the active UL BWP and the size of the active UL BWP. For example, for a 40 MHz UL BWP, the sub - band size for SCS = 15 kHz may be equal to 108, and for a 40 MHz UL BWP, the sub - band size for SCS = 30 kHz may be equal to 53. The sub - band sizes for the three sub - bands for SCS = 30 kHz and for a 60 MHz UL BWP may be 53, 55, and 53. The sub - band sizes for the four sub - bands for SCS = 30 kHz and for an 80 MHz UL BWP may be 53, 55, 55, and 53. The sub - band sizes for the five sub - bands for SCS = 30 kHz and for a 100 MHz UL BWP may be 54, 55, 55, 55, and 54. For another example, the sub - band sizes for the two sub - bands for SCS = 15 kHz and for a 40 MHz UL BWP may be equal to 110 and 106. The sub - band sizes for the two sub - bands for SCS = 30 kHz and for a 40 MHz UL BWP may be equal to 55 and 51. The sub - band sizes for the three sub - bands for SCS = 30 kHz and for a 60 MHz UL BWP may be 55, 55, and 51. The sub - band sizes for the four sub - bands for SCS = 30 kHz and for an 80 MHz UL BWP may be 55, 55, 55, and 51. The sub - band sizes for the five sub - bands for SCS = 30 kHz and for a 100 MHz UL BWP may be 55, 55, 55, 55, and 51. For another example, the sub - band sizes for the two sub - bands for SCS = 15 kHz and for a 40 MHz UL BWP may be equal to 106 and 110. The sub - band sizes for the two sub - bands for SCS = 30 kHz and for a 40 MHz UL BWP may be equal to 51 and 55. The sub - band sizes for the three sub - bands for SCS = 30 kHz and for a 60 MHz UL BWP may be 51, 55, and 55. The sub - band sizes for the four sub - bands for SCS = 30 kHz and for an 80 MHz UL BWP may be 51, 55, 55, and 55. The sub - band sizes for the five sub - bands for SCS = 30 kHz and for a 100 MHz UL BWP may be 51, 55, 55, 55, and 55. Note that the order of the above - mentioned sub - bands within the UL BWP may be in ascending order and in the frequency domain from the lowest frequency to the highest frequency within the UL BWP.

[0244] The DCI format for scheduling PUSCH on an NR-U cell may need to indicate several types of information, such as the type of channel access procedure (i.e., LBT category), the channel access priority level, the PUSCH start position, etc. For the type of channel access procedure, the gNB 160 may need to notify the UE 102 which channel access procedure type among Cat-1 LBT (also known as Type-0 UL channel access procedure or no channel sensing), Cat-2 LBT with a 16 ps duration (also known as Type-2 UL channel access procedure), Cat-2 LBT with a 25 ps duration, and Cat-4 LBT (also known as Type-1 UL channel access procedure) is used for transmitting the PUSCH scheduled by the DCI format. For the channel access priority level, the gNB 160 may need to notify the UE 102 which channel access priority level among categories 1, 2, 3, and 4 is used for Cat-4 LBT to transmit the PUSCH scheduled by the DCI format. For the PUSCH start position, the gNB 160 may need to notify the UE 102 the fractional-symbol-based start position of the PUSCH scheduled by the DCI format in order to create an appropriate gap length from the previous transmission. These parameters may affect each other.

[0245] Figure 27 A typical scenario for PUSCH transmission is shown. In this scenario, there is a period of time before scheduling the PUSCH transmission during which there is no uplink or downlink transmission. Through the DCI format for scheduling the PUSCH, the gNB 160 can notify the UE 102 that Cat-4 LBT is used for PUSCH transmission. The DCI format can also indicate the channel access priority level. The DCI format can further indicate, according to the time-domain resource allocation field in the DCI format, that the start position of the PUSCH is the initial boundary of the first symbol allocated to the PUSCH (i.e., x μs after the initial boundary of the first symbol where x = 0).

[0246] Figure 28 A typical scenario for PUSCH transmission is shown. In this scenario, there is a period of time before scheduling the PUSCH transmission during which there is no uplink or downlink transmission, but there may be a PRACH transmission of another UE whose time resources overlap with the relevant PUSCH transmission. Through the DCI format for scheduling the PUSCH, the gNB 160 can notify the UE 102 that Cat-4 LBT is used for PUSCH transmission. The DCI format can also indicate the channel access priority level. The DCI format can further indicate that the start position of the PUSCH is N TA_offset *T c after the initial boundary of the first symbol allocated to the PUSCH, such that the start position of the PUSCH is aligned with the start position of the possible PRACH transmission from another UE.

[0247] Downlink and uplink transmissions can be organized into T f =(Δf 最大 N f / 100)T c = frames of 10 ms duration, each including T sf =(Δf 最大 N f / l000)T c = ten subframes of 1 ms duration. The number of consecutive OFDM symbols in each subframe can be Each frame can be divided into two equal-sized half-frames of five subframes, each frame having a half-frame 0 including subframes 0 to 4 and a half-frame 1 including subframes 5 to 9. There can be a set of frames in the uplink on a carrier, and a set of frames in the downlink. The uplink frame number i for transmission from UE 102 can start T TA =(N TA +N TA,偏移 )T c before the start of the corresponding downlink frame at the UE. UE 102 can have the ability to follow the frame timing variations of the reference cell in the connected state. Uplink frame transmission may occur (in time) before the first detection path of the corresponding downlink frame received from the reference cell by (N TA+ N TA偏移 )×T c . If UE 102 is configured with a primary timing adjustment group (pTAG, also known as the TAG of the master cell group (MCG)) that includes the PCell, the UE can use the PCell as the reference cell for deriving the UE transmission timing for the cells in the pTAG. If the UE is configured with a primary-secondary TAG (psTAG, also known as the TAG of the secondary cell group (SCG)) that includes the PSCell, the UE can use the PSCell as the reference cell for deriving the UE transmission timing for the cells in the psTAG. The UE initial transmission timing accuracy, the maximum timing variation in an adjustment, the minimum adjustment rate, and the maximum adjustment rate are defined in the following requirements. The timing advance offset value N TA_offset of the serving cell can be provided to the UE through the n-TimingAdvanceOffset of the serving cell. If the n-TimingAdvanceOffset of the serving cell is not provided for the UE, the UE can determine the default value N TA_offset of the timing advance offset of the serving cell. For the FR1 FDD band in the case of no LTE-NR coexistence, the FR1 TDD band in the case of no LTE-NR coexistence, the FR1 FDD band in the case of LTE-NR coexistence, the FR1 TDD band in the case of LTE-NR coexistence or in the FR2 case, N TA_offsetThe default values can be 25600, 25600, 0, 39936, or 13792 respectively, with T c as the unit.

[0248] For the SCS of 2 μ ·15 kHz, the timing advance command of the TAG can be 16·64·T c / 2 μ times to indicate the change in the uplink timing relative to the current uplink timing of the TAG. For the start timing of the random access preamble, N TA can be assumed to be 0. In the case of a random access response, the timing advance command T A for the TAG can be indicated by the index value T A = 0, 1, 2,..., 3846 to indicate the N TA value, where the time alignment amount of the TAG with an SCS of 2 μ ·15 kHz is N TA = T A ·16·64 / 2 μ . N TA can be the SCS relative to the first uplink transmission from the UE after receiving the random access response. In other cases, the timing advance command T A for the TAG can indicate to adjust the current N TA value N TA to a new N A value N TA through the index value T TA_new = 0, 1, 2,..., 63, where for the SCS of 2 μ ·15 kHz, N TA-new = N TA_old +(T A -31)·16·64 / 2 μ ·T c = 1 / (Δf 最大 ·N f ), where Δf max = 480·10 3 Hz, and N f = 4096, that is, T c is 1 / (480*10 3 *4096). N TA is the timing adjustment value, and N TA_offset is the timing advance offset value.

[0249] Figure 29Illustrates a typical scenario for PUSCH transmission. In this scenario, there is another uplink transmission before scheduling the PUSCH transmission. Through the DCI format for scheduling the PUSCH, gNB 160 can notify UE 102 that Cat-2 LBT is used for PUSCH transmission. The DCI format may not have to indicate the channel access priority level because Cat-2 LBT does not require information on the channel access priority level. Alternatively, although the DCI format may not indicate the channel access priority level, UE 102 may not use the indicated channel access priority level. The DCI format can further indicate that the starting position of the PUSCH is 25 μs after the initial boundary of the first symbol allocated to the PUSCH, creating a 25-μs gap between the end of the previous uplink transmission and the start of the scheduled PUSCH.

[0250] Figure 30 Illustrates a typical scenario for PUSCH transmission. In this scenario, there is a downlink transmission before scheduling the PUSCH transmission. Through the DCI format for scheduling the PUSCH, gNB 160 can notify UE 102 that Cat-1 LBT is used for PUSCH transmission. The DCI format may not have to indicate the channel access priority level because Cat-1 LBT does not require information on the channel access priority level. Alternatively, although the DCI format may not indicate the channel access priority level, UE 102 may not use the indicated channel access priority level. The DCI format can further indicate that the starting position of the PUSCH is x μs after the initial boundary of the first symbol allocated to the PUSCH, where (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offset )*T c + 16 μs, ensuring that the interval between the end of the previous downlink transmission and the start of the scheduled PUSCH is less than 16 μs.

[0251] Figure 31Illustrates a typical scenario for PUSCH transmission. In this scenario, there is a downlink transmission before scheduling the PUSCH transmission. Through the DCI format that schedules the PUSCH, gNB 160 can notify UE 102 of Cat-2 LBT with a duration of 16 μs for PUSCH transmission. The DCI format may not have to indicate the channel access priority level because Cat-2 LBT does not require information on the channel access priority level. Alternatively, although the DCI format may not indicate the channel access priority level, UE 102 may not use the indicated channel access priority level. The DCI format can further indicate that the starting position of the PUSCH is after the initial boundary of the first symbol allocated to the PUSCH by (N TA +N TA_offset )*T c + 16 μs, such that a 16-μs gap is created between the end of the previous downlink transmission and the start of the scheduled PUSCH.

[0252] Figure 32 Illustrates a typical scenario for PUSCH transmission. In this scenario, there is a downlink transmission before scheduling the PUSCH transmission. Through the DCI format that schedules the PUSCH, gNB 160 can notify UE 102 of Cat-2 LBT with a duration of 25 μs for PUSCH transmission. The DCI format may not have to indicate the channel access priority level because Cat-2 LBT does not require information on the channel access priority level. Alternatively, although the DCI format may not indicate the channel access priority level, UE 102 may not use the indicated channel access priority level. The DCI format can further indicate that the starting position of the PUSCH is after the initial boundary of the first symbol allocated to the PUSCH by (N TA +N TA_offset )*T c + 25 μs, such that a 25-μs gap is created between the end of the previous downlink transmission and the start of the scheduled PUSCH.

[0253] Figure 33Illustrates a typical scenario for PUSCH transmission. In this scenario, there is a downlink transmission before scheduling the PUSCH transmission. Through the DCI format for scheduling the PUSCH, gNB 160 can notify UE 102 that Cat-2 LBT with a duration of 25 μs is used for PUSCH transmission. The DCI format may not have to indicate the channel access priority level because Cat-2 LBT does not require information on the channel access priority level. Alternatively, although the DCI format may not indicate the channel access priority level, UE 102 may not use the indicated channel access priority level. The DCI format can further indicate that the starting position of the PUSCH is the initial boundary of the first symbol allocated to the PUSCH. There may be a gap greater than 100 μs between the end of the previous downlink transmission and the start of scheduling the PUSCH.

[0254] There may be several options regarding the notification of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position.

[0255] The first option is that a single 4-bit information field in the DCI format indicates the combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position. UE 102 that detects the DCI format can use the field value to determine the values of these parameters based on the predefined association between the information field value and the combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position. Table 10 shows an example of the association between the information field value and the combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position.

[0256] [Table 10]

[0257]

[0258] Table 11 shows another example of the association between the information field value and the combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position.

[0259] [Table 11]

[0260]

[0261]

[0262] The associations shown in Table 10 and Table 11 can be characterized as follows. A single entry can correspond to Cat-1 LBT. For Cat-1 LBT, the duration and channel access priority level may not be specified. For Cat-1 LBT, a single PUSCH starting position is specified. Four entries (which are greater than one entry of Cat-1 LBT) can correspond to Cat-2 LBT. Among the four entries, a single entry can correspond to Cat-2 LBT with a duration of 16 μs, and three entries (which are greater than one of Cat-2 LBT with a duration of 16 μs and one of Cat-4 LBT) can correspond to Cat-2 LBT with a duration of 25 μs. For Cat-2 LBT, the channel access priority level may not be specified. For Cat-2 LBT with a duration of 16 μs, a single PUSCFH starting position is specified. For Cat-2 LBT with a duration of 25 μs, three different PUSCH starting positions are specified. Four or eight (i.e., multiples of four) entries can correspond to Cat-4 LBT. For Cat-4 LBT, the duration may not be specified. For Cat-4 LBT, a single PUSCH starting position (e.g., x = 0 μs) can be specified. Alternatively, two different PUSCH starting positions can be specified. For Cat-4 LBT and a given PUSCH starting position, four different channel access priority levels are specified.

[0263] The second option is that two information fields in the DCI format jointly indicate a combination of the channel access process type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position. The first 2-bit information field can indicate the channel access process type. The second 2-bit information field can indicate a combination of the duration and the PUSCH starting position or a combination of the channel access priority level and the PUSCH starting position, depending on the value of the first information field. Table 12 shows an example of the first 2-bit information. Tables 13 and 14 show examples of the second 2-bit information.

[0264] [Table 12]

[0265] Field Value Channel Access Procedure Type 0 Cat-1 LBT 1 Cat-2 LBT 2 Cat-4 LBT 3 Reservation

[0266] [Table 13]

[0267] Field Value Duration for Cat-2 LBT PUSCH Start Position x 0 16 μs <![CDATA[x = (N TA + N TA_offset ) * T c + 16 μs <!-- 42 -->]]> 1 25 μs X = 0 μs 2 25 μs X = 25 μs 3 25 μs <![CDATA[x = (N TA + N TA_offset ) * T c + 25 μs]]>

[0268] [Table 14]

[0269] Field Value Channel Access Priority Level p for Cat-4 LBT 0 Level 1 1 Level 2 2 Level 3 3 Level 4

[0270] Table 12, Table 13, and Table 14 can be characterized as follows. The value of the first 2-bit information field can indicate one of Cat-1 LBT, Cat-2 LBT, and Cat-4 LBT. If the value of the first 2-bit information field indicates Cat-1 LBT, the PUSCH start position is determined to be (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offset )*T c + 16 μs without referring to the second 2-bit information field. If the value of the first 2-bit information field indicates Cat-2 LBT, the value of the second 2-bit information field can be interpreted according to Table 13. Based on Table 13, the duration and the PUSCH start position can be determined. If the value of the first 2-bit information field indicates Cat-4 LBT, the PUSCH start position is determined to be x = 0 μs, and the value of the second 2-bit information field can be interpreted according to Table 14. In Table 14, each of the four entries can correspond to a respective channel priority level.

[0271] The third option is that two information fields in the DCI format jointly indicate a combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH start position. The first 2-bit information field can indicate a combination of the channel access procedure type and the duration for Cat-2 LBT. The second 2-bit information field can indicate the PUSCH start position or the channel access priority level, depending on the value of the first information field. Table 15 shows an example of the first 2-bit information. Tables 16 and 17 show examples of the second 2-bit information.

[0272] [Table 15]

[0273] Field Value Channel Access Procedure Type Duration for Cat-2 LBT 0 Cat-1 LBT - 1 Cat-2 LBT 16 μs 2 Cat-2 LBT 25 μs 3 Cat-4 LBT -

[0274] [Table 16]

[0275] Field Value PUSCH Start Position x 0 x = 0 μs 1 x = 25 μs 2 <![CDATA[x = (N TA + N TA_offset ) * T c + 25 μs]]> 3 Reservation

[0276] [Table 17]

[0277] Field Value Channel Access Priority Level p for Cat-4 LBT 0 Level 1 1 Level 2 2 Level 3 3 Level 4

[0278] Table 15, Table 16, and Table 17 can be characterized as follows. The value of the first 2-bit information field can indicate one of Cat-1 LBT, Cat-2 LBT with 16 μs, Cat-2 LBT with 25 μs, and Cat-4 LBT. If the value of the first 2-bit information field indicates Cat1 LBT, the PUSCH start position is determined to be (N TA +N TA_offset)*T c ≤x<(N TA +N TA_offset )*T c + 16 μs without referring to the second 2-bit information field. If the value of the first 2-bit information field indicates Cat-2 LBT with 16 μs, the PUSCH start position is determined as x = (N TA +N TA_offset )*T c + 16 μs without referring to the second 2-bit information field. If the value of the first 2-bit information field indicates Cat-2 LBT with 25 μs, the value of the second 2-bit information field can be interpreted according to Table 16. Based on Table 16, the PUSCH start position can be determined. If the value of the first 2-bit information field indicates Cat-4 LBT, the PUSCH start position is determined as x = 0 μs, and the value of the second 2-bit information field can be interpreted according to Table 17. In Table 17, each of the four entries can correspond to a respective channel priority level.

[0279] The fourth option is that the information field in the DCI format indicates one of the combinations of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH start position in the RRC configuration. More specifically, the gNB 160 can send the RRC parameters for configuring Y entries according to the combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH start position. The information field can include ceiling(log2(Y)) bits and can indicate one of the Y entries. The UE 102 that detects the DCI format can assume and / or use the combination of the channel access procedure type, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH start position corresponding to the entry indicated by the information field.

[0280] The fifth option is one of the RRC-selected combinations in the information field in the DCI format that indicates the type of channel access procedure, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position. More specifically, the possible combinations of the type of channel access procedure, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position can be predefined and indexed. For example, the combinations shown in Table 10 or Table 11 can be predefined and indexed as the corresponding indexes in the field value column. gNB 160 can send RRC parameters for configuring Y entries, each entry being set to the corresponding index in the indexes of the predefined combinations. The information field can include ceiling(log2(Y)) bits and can indicate one of the Y entries. The UE 102 that detects the DCI format can assume and / or use the combination of the type of channel access procedure, the duration for Cat-2 LBT, the channel access priority level for Cat-4 LBT, and the PUSCH starting position corresponding to the index associated with the entry indicated by the information field.

[0281] Different options can be applied to different DCI formats. For example, the fourth option or the fifth option can be applied to DCI format 0_1 whose size depends on the dedicated RRC configuration, while the first option (including the modified first option that uses a subset rather than the complete set of the combinations shown in Table 10 or Table 11), the second option, or the third option can be applied to the RAR UL grant and DCI format 0_0 whose size does not depend on the dedicated RRC configuration.

[0282] The predefined subsets of the combinations shown in Table 10 or Table 11 can be used by DCI format 0_0 and the RAR UL grant, while the complete set of the combinations shown in Table 10 or Table 11 can be used by DCI format 0_1. Different subsets can be applied to different RNTIs. For example, the first predefined subset of the combinations shown in Table 10 or Table 11 can be used by DCI format 0_0 with a CRC scrambled by the TC-RNTI, while the second predefined subset of the combinations shown in Table 10 or Table 11 (which can be different from the first predefined subset) can be used by DCI format 0_0 with a CRC scrambled by the C-RNTI. Different subsets can be applied to different types of search space sets. For example, the first predefined subset of the combinations shown in Table 10 or Table 11 can be used by DCI format 0_0 in the common search space set, while the second predefined subset of the combinations shown in Table 10 or Table 11 (which can be different from the first predefined subset) can be used by DCI format 0_0 in the UE-specific search space set.

[0283] Figure 34A method for a UE to communicate with a gNB is shown. The method may include monitoring a physical downlink control channel (PDCCH) with a downlink control (DCI) format (step 3401). The method may also include transmitting a physical uplink shared channel (PUSCH) subject to a channel access procedure (step 3402). The starting position of the PUSCH may be x microseconds after the initial boundary of the initial symbol allocated to the PUSCH. The DCI format may include a 4-bit information field. The 4-bit information may be characterized by at least one or more of the following values: The first value of the 4-bit information field indicates that the channel access procedure type is Category-1 Listen Before Talk (Cat-1 LBT), and (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offset )*T c +16; The second value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and x = (N TA +N TA_offset )*T c +16; The third value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; The fourth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 25; The fifth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = (N TA +N TA_offset )*T c +25; The sixth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0; The seventh value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; The eighth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; And the ninth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0. N TA may be a timing adjustment value. N TA_offset may be a timing advance offset value. T c may be 1 / (480*10 3*4096)

[0284] Figure 35 A method of a gNB for communicating with a UE is shown. The method may include transmitting a physical downlink control channel (PDCCH) with a downlink control (DCI) format (step 3501). The method may also include receiving a physical uplink shared channel (PUSCH) transmitted subject to a channel access procedure (step 3502). The starting position of the PUSCH may be x microseconds after the initial boundary of the initial symbol allocated to the PUSCH. The DCI format may include a 4-bit information field. The 4-bit information may be characterized by at least one or more of the following values: The first value of the 4-bit information field indicates that the channel access procedure type is Category-1 Listen-Before-Talk (Cat-1 LBT), and (N TA +N TA_offset )*T c ≤x<(N TA +N TA_offset )*T c +16; The second value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and x = (N TA +N TA_offset )*T c +16; The third value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; The fourth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 25; The fifth value of the 4-bit information field indicates that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = (N TA +N TA_offset )*T c +25; The sixth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0; The seventh value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; The eighth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; And the ninth value of the 4-bit information field indicates that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0. N TA may be a timing adjustment value. N TA_offsetIt can be a timing advance offset value. T c It can be 1 / (480*10 3 *4096).

[0285] The 4-bit information can be characterized by at least one or more of the following values: the tenth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority for Cat-4 LBT is level 1, and x = N TA _ offset *T c ; the eleventh value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = N TA_offset *T c ; the twelfth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = N TA_offset *T c ; and the thirteenth value of the 4-bit information field indicates that the channel access process type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = N TA_offset *T c .

[0286] It should be noted that the above variables used as the number of stripes or indices can be considered non-negative integers.

[0287] It should be noted that the decision on whether a given channel and / or data (including TB and CB) is successfully received can be made by referring to the cyclic redundancy check (CRC) bits attached to the given channel and / or data.

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

[0289] It should be noted that, basically, UE 102 and gNB 160 may have to assume the same procedures. For example, when UE 102 follows a given procedure (e.g., the above-mentioned procedure), gNB 160 may also have to assume that UE 102 follows that procedure. Additionally, gNB 160 may also have to execute the corresponding procedure. Similarly, when gNB 160 follows a given procedure, UE 102 may also have to assume that gNB 160 follows that procedure. Additionally, UE 102 may also have to execute the corresponding procedure. The physical signals and / or channels received by UE 102 may be transmitted by gNB 160. The physical signals and / or channels transmitted by UE 102 may be received by gNB 160. The high-layer signals and / or channels obtained by UE 102 (e.g., dedicated RRC configuration messages) may be sent by gNB 160. The high-layer signals and / or channels transmitted by UE 102 (e.g., dedicated RRC configuration messages, MAC CE messages) may be obtained by gNB 160.

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

[0291] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or a processor. As used herein, the term "computer-readable medium" may represent a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the required program code in the form of instructions or data structures and can be accessed by a computer or a processor. As used herein, disk and optical disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and optical disk, where disks typically reproduce data magnetically, while optical disks utilize lasers to reproduce data optically.

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

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

[0294] 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 may be made to the arrangements, operations, and details of the systems, methods, and apparatuses described herein.

[0295] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls a CPU or the like in a manner to implement the functions according to the system and method (a program for computer operation). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, this information is stored in various ROMs or HDDs and read by the CPU whenever needed for modification or writing. As a recording medium on which the program is stored, any 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 above system and method are implemented by running the loaded program, and furthermore, based on instructions from the program, the functions according to the system and method are implemented in combination with an operating system or other application programs.

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

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

Claims

1. A user equipment (UE) communicating with a base station, the UE comprising: a receiving circuit configured to monitor a physical downlink control channel (PDCCH) having a downlink control information (DCI) format; and a transmitting circuit configured to transmit a physical uplink shared channel (PUSCH) subject to a channel access procedure, wherein a starting position of an initial symbol for the PUSCH is adjusted by using a value x; wherein the DCI format includes an information field, the information field is characterized by a first value and one or more of at least a second value, a third value, a fourth value, a fifth value, a sixth value, a seventh value, an eighth value, and a ninth value, the first value of the information field indicating that the channel access procedure type of the channel access procedure is Category 1 listen-before-talk (Cat-1 LBT), and the value x is given by at least a timing advance (TA) value and 16, wherein the Cat-1 LBT is a type of channel access procedure without channel sensing; the second value of the information field indicating that the channel access procedure type is Cat-2 LBT, a duration for Cat-2 LBT is 16 microseconds, and the value x is given by at least the TA value and 16, wherein the Cat-2 LBT is a type of channel access procedure with channel sensing for a single time slot; the third value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; the fourth value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and the value x is given by at least 25 without the TA value; the fifth value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and the value x is given by at least the TA value and 25; the sixth value of the information field indicating that the channel access procedure type is Cat-4 LBT, a channel access priority level for Cat-4 LBT is level 1, and x = 0, wherein the Cat-4 LBT is a type of channel access procedure with random backoff having an adaptive contention window (CW) size; the seventh value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; the eighth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; and the ninth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0.

2. A base station communicating with a user equipment UE, the base station comprising: a transmission circuit configured to transmit a physical downlink control channel PDCCH having a downlink control information DCI format; and a receiving circuit configured to receive a physical uplink shared channel PUSCH transmitted subject to a channel access procedure, and a starting position of an initial symbol for the PUSCH is adjusted by using a value x; wherein the DCI format includes an information field, the information field is characterized by a first value and one or more of at least a second value, a third value, a fourth value, a fifth value, a sixth value, a seventh value, an eighth value, and a ninth value: the first value of the information field indicating that the channel access procedure type of the channel access procedure is Category 1 listen-before-talk Cat-1 LBT, and the value x is given by at least a timing advance TA value and 16, wherein the Cat-1 LBT is a type of channel access procedure without channel sensing; the second value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and the value x is given by at least the TA value and 16, wherein the Cat-2 LBT is a type of channel access procedure with channel sensing for a single time slot; the third value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; the fourth value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and the value x is given by at least 25 without the TA value; the fifth value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and the value x is given by at least the TA value and 25; the sixth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0, wherein Cat-4 LBT is a type of channel access procedure with random backoff having an adaptive contention window CW size; the seventh value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; the eighth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; and The ninth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0.

3. A method for a user equipment UE communicating with a base station, the method comprising: Monitoring a physical downlink control channel PDCCH having a downlink control information DCI format; and Transmitting a physical uplink shared channel PUSCH subject to a channel access procedure, the starting position of the initial symbol of the PUSCH being adjusted by using a value x; wherein the DCI format includes an information field, the information field being characterized by a first value and one or more of at least a second value, a third value, a fourth value, a fifth value, a sixth value, a seventh value, an eighth value, and a ninth value, the first value of the information field indicating that the channel access procedure type is Category 1 listen-before-talk Cat-1 LBT, and the value x is given by at least a timing advance TA value and 16, wherein the Cat-1 LBT is a type of channel access procedure without channel sensing; the second value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 16 microseconds, and the value x is given by at least the TA value and 16, wherein the Cat-2 LBT is a type of channel access procedure with channel sensing for a single time slot; the third value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and x = 0; the fourth value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and the value x is given by at least 25 without the TA value; the fifth value of the information field indicating that the channel access procedure type is Cat-2 LBT, the duration for Cat-2 LBT is 25 microseconds, and the value x is given by at least the TA value and 25; the sixth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 1, and x = 0, wherein Cat-4 LBT is a type of channel access procedure with random backoff having an adaptive contention window CW size; the seventh value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 2, and x = 0; the eighth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 3, and x = 0; and The ninth value of the information field indicating that the channel access procedure type is Cat-4 LBT, the channel access priority level for Cat-4 LBT is level 4, and x = 0.

Images