User equipment and base station performing transmission and reception operations

Abstract

To provide user equipment (UE) and a base station (BS) involved in an improved physical random access channel (PRACH) transmission.SOLUTION: A method includes: configuring, by UE, based on a received unlicensed channel access configuration, symbols of an occupancy time of respective unlicensed channel for uplink communication; receiving indication information on a timing of channel resources which are to be used for a PRACH transmission; determining whether or not the indicated timing of channel resources is included within the symbols configured for uplink communication; in a case of a positive determination, performing a clear channel assessment (CCA) for a gap duration before the start of the indicated timing of channel resources which are to be used for the PRACH transmission; and if successful, transmitting a random access preamble within the symbols configured for uplink communication at the indicated timing of channel resources which are to be used for the PRACH transmission.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] The present disclosure is directed to methods, apparatus, and articles in communication systems, such as 3GPP communication systems. [Background technology]

[0002] Currently, the 3rd Generation Partnership Project (3GPP) is working on technical specifications for the next generation of cellular technology, also known as the fifth generation (5G).

[0003] One objective is to provide a single technical framework that addresses all usage scenarios, requirements, and deployment scenarios (see, for example, TR 38.913 version 15.0.0, Clause 6), including at least enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communication (mMTC). For example, deployment scenarios for eMBB may include indoor hotspots, dense urban, suburban, urban, and high-speed. Deployment scenarios for URLLC may include industrial control systems, mobile health management (remote monitoring, remote diagnosis, and remote treatment), real-time control of vehicles, and wide-area monitoring and control systems for smart grids. Deployment scenarios for mMTC may include scenarios using a large number of devices with low latency sensitive data transmission, such as smart wearables and sensor networks. eMBB and URLLC services are similar in that both require extremely high bandwidth, but differ in that URLLC services preferably require extremely low latency.

[0004] The second objective is to achieve forward compatibility: backward compatibility to Long Term Evolution (LTE, LTE-A) cellular systems is not required, which will facilitate the design of entirely new systems and / or the introduction of new features. Summary of the Invention

[0005] One non-limiting exemplary embodiment of the present invention facilitates providing an improved procedure for performing PRACH transmissions over an unlicensed channel (i.e., performing PRACH transmissions during an occupancy time of the unlicensed channel).

[0006] In one embodiment, the techniques disclosed herein provide a user equipment (UE) including a processor, a receiver, and a transmitter. The processor, in operation, configures at least one symbol of an occupancy time of each unlicensed channel for uplink communication based on a received unlicensed channel access configuration. The receiver, in operation, receives an indication of a timing of a channel resource used for a physical random access channel (PRACH) transmission. The processor, in operation, determines whether the indicated timing of the channel resource used for the PRACH transmission is included within at least one symbol configured for uplink communication. If the determination is positive, the processor, in operation, performs a clear channel assessment (CCA) for a gap period before the start of the indicated timing of the channel resource used for the PRACH transmission. If the CCA is positive, the transmitter, in operation, performs a PRACH transmission by transmitting a random access (RA) preamble at the indicated timing of the channel resource used for the PRACH transmission within at least one symbol configured for uplink communication.

[0007] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any combination thereof.

[0008] Further benefits and advantages of the disclosed embodiments and various implementations will become apparent from the specification and drawings. These benefits and / or advantages may be obtained individually by the various embodiments and features of the specification and drawings, although it is not necessary for all of these features to be present in order to obtain one or more of such benefits and / or advantages.

[0009] In the following, exemplary embodiments are explained in more detail with reference to the accompanying drawings. [Brief description of the drawings]

[0010] [Figure 1] 1 illustrates an example architecture of a 3GPP 5G system including a 5G Core network (5GC) and a Next Generation Radio Access Network (NG-RAN). [Diagram 2] An exemplary decentralized deployment scenario is depicted in which a 5G system including gNBs is co-located with an LTE system including eNBs. [Diagram 3] 1 illustrates a schematic diagram of the functional division between the functions provided by the Next Generation Radio Access Network (NG-RAN) and the 5G Core Network (5GC). [Figure 4] This shows the Radio Resource Control (RRC) connection establishment / re-establishment procedure in a 3GPP 5G system as a sequence diagram. [Diagram 5] Enhanced Mobile Broadband (eMBB), Massive Machine Type Communications (mMTC), and Ultra-Reliable Low Latency Communications (URLLC) usage scenarios are outlined. [Figure 6]1 illustrates an exemplary block diagram of 3GPP's 5G service based architecture (SBA) for a non-roaming scenario. [Figure 7] An exemplary configuration for PRACH (i.e., for parameter prach-ConfigurationIndex=22 and parameter msg1-FDM=2) is shown. [Figure 8] An exemplary frame structure of a gNB channel occupancy time (COT) is depicted, including a single switching point from DL to UL and with a switching gap. [Figure 9] 1 shows an exemplary simplified structure of a UE and a gNB. [Figure 10] 10A-10C show exemplary simplified structures of a gNB and a UE, respectively, according to a typical scenario of improved PRACH transmission operation. [Figure 11] 10A-10C show exemplary simplified structures of a gNB and a UE, respectively, according to a typical scenario of improved PRACH transmission operation. [Figure 12] Each illustrates a flow chart of UE and gNB operation according to a typical scenario of improved PRACH transmission operation. [Figure 13] Each illustrates a flow chart of UE and gNB operation according to a typical scenario of improved PRACH transmission operation. [Figure 14] 1 illustrates a flow diagram of a UE operation according to a first exemplary implementation of an improved PRACH transmission operation. [Figure 15] 13 illustrates an exemplary channel resource configuration for an occupancy time when a UE performs an improved PRACH transmission operation according to a first exemplary implementation. [Figure 16] 13 illustrates another exemplary channel resource configuration of the occupancy time when the UE performs an improved PRACH transmission operation according to a first exemplary implementation. [Figure 17]13 shows a flow diagram of a UE operation according to a second exemplary implementation of an improved PRACH transmission operation. [Figure 18] 13 illustrates an exemplary channel resource configuration for an occupancy time when a UE performs an improved PRACH transmission operation according to a second exemplary implementation. [Figure 19] 13 illustrates another exemplary channel resource configuration of occupancy time when the UE performs an improved PRACH transmission operation according to a second exemplary implementation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] [5G NR system architecture and protocol stack] The 3rd Generation Partnership Project (3GPP) is working on the next release of the fifth generation of cellular technology (known simply as 5G), which includes the development of a new radio access technology (NR) that will operate in frequencies up to 100 GHz. The first version of the 5G standard will be completed at the end of 2017, which will allow smartphones compliant with the 5G NR standard to proceed to testing and commercial deployment.

[0012] In particular, the overall system architecture envisages an NG-RAN (Next Generation - Radio Access Network) with gNBs terminating the NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols towards the UEs.

[0013] The gNBs are interconnected with each other by the Xn interface, and further connected to the Next Generation Core (NG) by the Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF) (i.e. a specific core entity running the AMF) by the NG-C interface, and to the User Plane Function (UPF) (i.e. a specific core entity running the UPF) by the NG-U interface.

[0014] Figure 1 shows the architecture of NG-RAN (see, for example, 3GPP TS 38.300 v15.6.0, clause 4).

[0015] Various different deployment scenarios can be supported (see, for example, 3GPP TR 38.801 v14.0.0), which presents, for example, a decentralized deployment scenario (see, for example, section 5.2 of 3GPP TR 38.801 v14.0.0, the centralized one being described in section 5.4), in which base stations supporting 5G NR can be deployed.

[0016] Figure 2 illustrates an exemplary decentralized deployment scenario (see e.g. Figure 5.2.-1 of 3GPP TR 38.801 v14.0.0), further illustrating an LTE eNB and a user equipment (UE), which is connected to both a gNB and an LTE eNB. The new eNB for NR 5G can be exemplarily referred to as a gNB. The eLTE eNB is an evolution of the eNB and supports connectivity to EPC (Evolved Packet Core) and NGC (Next Generation Core).

[0017] The user plane protocol stack in NR (see, for example, Section 4.4.1 of 3GPP TS 38.300 v15.6.0) includes the PDCP (Packet Data Convergence Protocol, see Section 6.4 of 3GPP TS 38.300 v15.6.0) sublayer, the RLC (Radio Link Control, see Section 6.3 of 3GPP TS 38.300 v15.6.0) sublayer, and the MAC (Medium Access Control, see Section 6.2 of 3GPP TS 38.300 v15.6.0) sublayer, which are terminated in the gNB on the network side. In addition to this, a new sublayer of the Access Stratum (AS) (SDAP: Service Data Adaptation Protocol) is introduced on top of PDCP (see eg section 6.5 of 3GPP TS 38.300 v15.6.0).

[0018] NR also defines a control plane protocol stack (see, for example, 3GPP TS 38.300 v15.6.0, clause 4.4.2). An overview of Layer 2 functionality is given in 3GPP TS 38.300 v15.6.0, clause 6. The functionality of the PDCP sublayer, RLC sublayer, and MAC sublayer are given in 3GPP TS 38.300 v15.6.0, clauses 6.4, 6.3, and 6.2, respectively. The functionality of the RRC layer is given in 3GPP TS 38.300 v15.6.0, clause 7.

[0019] The Medium Access Control layer (MAC) handles, for example, the multiplexing of logical channels, as well as scheduling and scheduling-related functions (including handling of various numerologies).

[0020] The physical layer (PHY) is responsible for, for example, coding, PHY HARQ processing, modulation, multi-antenna processing, mapping of signals to the appropriate physical time-frequency resources. Additionally, the physical layer (PHY) handles the mapping of transport channels to physical channels. The physical layer (PHY) provides services to the MAC layer in the form of transport channels.

[0021] A physical channel corresponding to a set of time-frequency resources is used for the transmission of the transport channels. Each transport channel is mapped to a corresponding physical channel. One physical channel is the Physical Random Access Channel (PRACH) used for random access.

[0022] NR use cases / deployment scenarios include enhanced Mobile Broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications (mMTC), which have diverse requirements in terms of data rates, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps downlink and 10 Gbps uplink) and user-perceived data rates that are on the order of three times higher than those offered by IMT-Advanced. In contrast, URLLC has more stringent requirements, including extremely low latency (user plane latency of 0.5 ms for uplink and downlink, respectively) and high reliability (1-10 Mbps within 1 ms). -5 ) is imposed. In addition, mMTC requires high connection density (1 km 2 1,000,000 devices per second), wide coverage in harsh environments, and extremely long battery life (15 years) to lower device costs may be desirable.

[0023] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is suitable for one use case may not work well for another use case.

[0024] For example, low latency services may preferably require a shorter symbol duration (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also referred to as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer cyclic prefix (CP) duration than scenarios with small delay spreads. To maintain a similar cyclic prefix (CP) overhead, the subcarrier spacing should be optimized depending on the delay spread. In NR, more than one value of subcarrier spacing may be supported. Thus, currently, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, ... are considered. Symbol duration T u and the subcarrier spacing Δf is expressed by the formula Δf=1 / T u As in LTE systems, the term "resource element" can be used to denote the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0025] In the new radio system 5G NR, for each numerology and carrier, a resource grid of subcarriers and OFDM symbols is defined in the uplink and downlink, respectively. Each element in the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0026] [Splitting 5G NR functions between NG-RAN and 5GC] Figure 3 shows the division of functions between NG-RAN and 5GC. The logical nodes of NG-RAN are gNB or ng-eNB. The logical nodes of 5GC are AMF, UPF, and SMF.

[0027] The gNB and ng-eNB handle among other things the following key functions: - Radio Resource Management functions, such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic resource allocation (scheduling) to UEs in both uplink and downlink directions - IP header compression, encryption, and data integrity protection - Selection of AMF at UE attach time when routing to AMF cannot be determined from information provided by the UE - Routing user plane data to the UPF - Routing control plane information to AMF - Establishing and releasing connections - Scheduling and sending paging messages - Scheduling and transmission of system broadcast information (sent from AMF or OAM) - Configuring measurements and measurement reporting for mobility and scheduling - Transport-level packet marking in the uplink - Session Management - Network slicing support - QoS flow management and mapping to data radio bearers - Support for UEs in RRC_INACTIVE state - NAS message delivery function - Wireless Access Network Sharing - Dual Connectivity - Tight interworking between NR and E-UTRA

[0028] The Access and Mobility Management Function (AMF) handles the following main functions: - Termination of Non-Access Stratum (NAS) signalling - NAS signaling security - Access Stratum (AS) security control - Core Network (CN) inter-node signaling for mobility between 3GPP access networks - Idle mode UE reachability (including control and execution of paging retransmissions) - Registration Area Management - Support for intra-system and inter-system mobility - Access Authentication - Access authentication, including roaming rights checks - Mobility management controls (subscriptions and policies) - Network slicing support - Selection of Session Management Function (SMF)

[0029] In addition, the User Plane Function (UPF) handles the following main functions: - Anchor points for intra-RAT / inter-RAT mobility (when applicable) - External PDU session points for interconnection with data networks - Packet routing and forwarding - User plane part of packet inspection and policy rule enforcement - Traffic usage reports - An uplink classifier to support routing of traffic flows to the data network. - Branching points to support multi-homed PDU sessions - User plane QoS processing (e.g. packet filtering, gating, UL / DL rate enforcement) - Validation of uplink traffic (mapping of SDF to QoS flows) - Downlink packet buffering and downlink data notification triggering

[0030] Finally, the Session Management Function (SMF) handles the following major functions: - Session Management - UE IP address allocation and management - UP function selection and control - Configuring traffic steering in the User Plane Function (UPF) to route traffic to the correct destination - Policy enforcement and QoS control parts - Downlink data notification

[0031] [RRC connection establishment and reconfiguration procedures] Figure 4 shows the interactions between the UE, gNB and AMF (5GC entities) in the NAS part when the UE transitions from RRC_IDLE to RRC_CONNECTED (see 3GPP TS 38.300 v15.6.0).

[0032] RRC is a higher layer signaling (protocol) used for UE and gNB configuration. In particular, in this transition, the AMF prepares UE context data (including e.g. PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB via an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE, which is done by the gNB sending a SecurityModeCommand message to the UE and the UE responding with a SecurityModeComplete message to the gNB.

[0033] The gNB then performs a reconfiguration to establish a signaling radio bearer 2 (SRB2) and a data radio bearer (DRB) by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete from the UE in response. In the case of a signaling-only connection, these steps related to RRCReconfiguration are skipped since SRB2 and DRB are not established. Finally, the gNB informs the AMF that the establishment procedure is complete by an INITIAL CONTEXT SETUP RESPONSE.

[0034] Thus, in the present disclosure, a fifth generation core (5GC) entity (e.g., AMF, SMF, etc.) is provided, which includes a control circuit that, in operation, establishes a next generation (NG) connection with a gNodeB such that a signaling radio bearer is established between the gNodeB and a user equipment (UE), and a transmitter that, in operation, transmits an initial context setup message to the gNodeB via the NG connection. In particular, the gNodeB transmits radio resource control (RRC) signaling including a resource allocation configuration information element to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0035] [Usage scenarios for IMT-2020 and beyond] Figure 5 shows some of the use cases for 5G NR. Three use cases are considered for 3GPP New Radio (3GPP NR) that support the various services and applications envisaged by early IMT-2020. Phase 1 specifications for enhanced mobile broadband (eMBB) have been finalized. Current and future work includes standardization of Ultra-Reliable and Low-Latency Communications (URLLC) and Large-Scale Machine-Type Communications beyond 2020, in addition to further extending support for eMBB.

[0036] URLLC use cases have stringent requirements regarding capabilities such as throughput, latency and availability and are envisioned as one of the enablers of future vertical applications such as wireless control of industrial manufacturing and production processes, remote medical surgery, power distribution automation in smart grids, transportation safety, etc. URLLC's ultra-high reliability is supported by identifying technologies to meet the requirements set by TR 38.913 version 15.0.0.

[0037] The above mentioned stringent requirements are, depending on the use case, higher reliability (up to 10-6 level), higher availability, packet size up to 256 bytes, time synchronization on the order of a few μs (values ​​range from 1 to a few μs depending on the frequency range), and low latency on the order of 0.5-1 ms (specifically the target latency for the user plane is 0.5 ms). A typical URLLC requirement for a single transmission of a packet is a BLER (block error rate) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.

[0038] Furthermore, for NR URLLC, several technology enhancements are recognized from the RAN1 perspective. In particular, PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. Furthermore, UCI (Uplink Control Information) enhancements related to HARQ (Hybrid Automatic Repeat Request) enhancements and CSI feedback enhancements. Also, PUSCH enhancements related to minislot level hopping and retransmission / repetition are recognized. The term "minislot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot containing 14 symbols).

[0039] However, as NR becomes more stable and development progresses (a key requirement for NR URLLC), the scope for achieving ultra-reliability may increase. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0040] Furthermore, technology enhancements targeted by NR URLLC target latency improvement and reliability improvement. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition of data channel, and preemption for downlink. Preemption means that a transmission for which resources are already allocated is aborted and the already allocated resources are used for another transmission with smaller latency / higher priority requirement requested later. Thus, an already granted transmission is preempted by a later transmission. Preemption applies regardless of the specific service type. For example, a transmission of service type A (URLLC) can be preempted by a transmission of service type B (eMBB, etc.). Technology enhancements related to reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0041] The mMTC (Massive Machine Type Communication) use case is characterized by a very large number of connected devices transmitting relatively small amounts of data that are generally not sensitive to latency. The devices need to be low cost and have extremely long battery life. From an NR perspective, utilizing very narrow bandwidth portions is one possible solution to achieve power saving from the UE perspective to enable long battery life.

[0042] As mentioned above, it is expected that the scope of reliability in NR will expand. One key requirement for all cases, especially for URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can be considered to improve reliability from a radio perspective and from a network perspective. In general, there are several key areas that can help improve reliability. These areas include compact control channel information, data channel / control channel repetition, diversity related to frequency domain, time domain, and / or spatial domain. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0043] [QoS Control] The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows that require guaranteed flow bitrates (GBR QoS flows) and QoS flows that do not require guaranteed flow bitrates (non-GBR QoS flows). At the NAS level, QoS flows are therefore the finest granularity of QoS differentiation in a PDU session. Within a PDU session, QoS flows are identified by a QoS Flow Identifier (QFI) that is conveyed in the encapsulation header over the NG-U interface.

[0044] The 5GC establishes one or more PDU sessions for each UE. The NG-RAN establishes at least one Data Radio Bearer (DRB) for each UE together with the PDU session, and may then configure additional DRBs for the QoS flows of that PDU session (NG-RAN decides when to do so), e.g. as described above with reference to Figure 4. The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, and AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0045] Figure 6 shows the 5G NR non-roaming reference architecture (see TS 23.501 v16.1.0, section 4.23). Application Functions (AFs) (e.g., external application servers handling 5G services exemplarily described in Figure 5) interact with the 3GPP core network to provide services, e.g., to support application influence on traffic routing, to access Network Exposure Functions (NEFs), or to interact with a policy framework (see Policy Control Function PCF) for policy control (e.g., QoS control). Based on the operator's deployment, application functions (AFs) that are considered trusted by the operator can be allowed to interact directly with the relevant network functions (Network Functions). Application Functions (AFs) that are not allowed by the operator to directly access network functions interact with the relevant network functions using an external exposure framework via the NEF.

[0046] Furthermore, the functional units of the 5G architecture are shown as Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN) (e.g. operator services, Internet access, or third-party services).

[0047] [Random Access Procedure] In 5G NR, random access channel transmissions are devised to allow a UE to make an initial access to a cell of the NG-RAN system. Such random access transmissions are performed in a defined sequence, i.e. according to a random access procedure. The random access channel procedure is standardized (see e.g. 3GPP TS38.321 v.15.6.0, section 5.1), and the following description only gives a rough overview of the individual aspects.

[0048] Once the UE has found a cell, it can access it. This can be done using a random access procedure. This procedure consists of four "steps". In the first step, the UE transmits a random access (RA) preamble (preamble for short) to the gNB on the Physical Random Access Channel (PRACH) (message 1 of the RA procedure). If the gNB detects the RA preamble, in the second step it transmits a Random Access Response (RAR) message (message 2 of the RA procedure) on the PDSCH (Physical Downlink Shared Channel). Before the RAR message, control information with the (random access) RA-RNTI that schedules the RAR message is transmitted on the PDCCH.

[0049] The RAR message conveys the detected RA preamble, a time alignment command (TA command) to synchronize subsequent uplink transmissions, an initial uplink resource allocation (UL grant) for the first scheduled transmission, and the allocation of a Temporary Cell Radio Network Temporary Identifier (T-CRNTI) that the gNB uses to address the UE until the RACH procedure is finished, since at this point the gNB does not know the "true" identity of the UE.

[0050] The third and fourth steps (messages 3 / 4 of the RA procedure) are provided with the aim of resolving potential collisions. Such collisions occur when two UEs transmit the same RA preamble on the same PRACH resource (e.g., collide). In this case, the gNB either fails to receive the RA preamble due to interference between the two transmissions, or receives only one RA preamble successfully. In the latter case, however, the gNB cannot distinguish between the two UEs. The gNB therefore responds with one RAR message containing one UL grant, which is received by both UEs.

[0051] The UE monitors the PDCCH in a given time window (e.g., referred to as the RAR time window) configured by the gNB to receive the RAR message. The UE uses the indicated UL grant to perform the first scheduled uplink transmission (message 3 of the RA procedure) on the assigned radio resources. This scheduled uplink transmission carries the actual RRC message, e.g., an RRC connection request or an RRC resume request.

[0052] In response, the gNB transmits a second actual RRC message (message 4 of the RA procedure) over the PDSCH, which transitions the UE to an RRC connected state if the RA procedure is successful. Prior to this scheduled downlink transmission, control information is transmitted on the PDCCH, including a DL assignment for scheduling the respective RRC message. This RRC message can be an RRC Setup message or an RRC Resume message.

[0053] Returning to the collision case, two UEs receiving one RAR message will transmit message 3 of the RA procedure using one UL grant from the RAR message. Naturally, this transmission will fail, since the two UEs are operating using the same T-CRNTI from the RAR message. Depending on the level of interference between the two uplink transmissions, either none of the two transmissions will be successfully received by the gNB, or at most only one transmission will be received by the gNB. In this case, conventional known mechanisms such as the timer validity mechanism (see 3GPP TS38.331 v.15.6.0, section 7.1) allow for collision detection and corresponding resolution.

[0054] [Physical Random Access Channel] The physical random access channel is designated based on time-frequency resources, i.e. resources intended to carry the RA preamble (message 1 of the RA procedure). Such resources are also called PRACH occasions. This emphasizes that the PRACH resources are simply opportunities for the transmission of the RA preamble. However, only a small part of the resources is actually used for the transmission of the RA preamble.

[0055] In 5G NR, the random access preamble is specified as follows: the random access preamble may only be transmitted in the time resources given by the higher layer parameter prach-ConfigurationIndex according to Table 6.3.3.2-2 to Table 6.3.3.2-4, and depends on FR1 or FR2 (see e.g. 3GPP TS 38.211 v15.6.0, section 6.3.3.2) and the spectrum type, which corresponds to either paired or unpaired spectrum (see e.g. TS 38.104).

[0056] The random access preamble can only be transmitted on the frequency resource given by the higher layer parameter msg1-FrequencyStart.RA ∈{0,1,...,M-1}, where M is equal to the higher layer parameter msg1-FDM, are numbered in ascending order from the lowest frequency in the initial uplink bandwidth portion at first access. Otherwise, n RA are numbered in ascending order starting from the lowest frequency in the active uplink bandwidth portion.

[0057] The slot numbering in the table assumes the following subcarrier spacing: - 15kHz for FR1 - 60kHz for FR2 Paired or unpaired spectrum, L max For handover to a target cell using TS 38.213-111111.11.4 using TS 38.213-111111.11, the UE shall determine whether the absolute value of the time difference between radio frame i in the current cell and radio frame i in the target cell is greater than or equal to 153600T. s It can be assumed that the

[0058] If the source cell is a paired or unpaired spectrum and the target cell is an unpaired spectrum, max For inter-frequency handover using 1 = 8, the UE determines whether the absolute value of the time difference between radio frame i in the current cell and radio frame i in the target cell is 76800T s It can be assumed that the

[0059] For simplicity, the following example table reproduces only a portion of Table 6.3.3.2-2 of 3GPP TS 38.211 v15.6.0 cited above, i.e., the table only shows the random access configurations for indexes 0-27 and 255.

[0060] [Table 1]

[0061] FIG. 7 shows an exemplary configuration of the PRACH, i.e., the configuration with the parameter prach-ConfigurationIndex=22 and the parameter msg1-FDM=2. In particular, index=22 specifies that the PRACH occasions are located in subframes #1, #4, and #7. Also, in this configuration, separate PRACH slots are defined in subframes #1, #4, and #7, respectively. Furthermore, in this example, two PRACH frequency resources n RA We assume that ∈{0,1,...,M-1}, i.e., M=2.

[0062] [Access to unlicensed spectrum] Considering the objective of meeting the ever-increasing demand for wireless broadband, the "Study on NR-based Access to Unlicensed Spectrum" was conducted (see, for example, 3GPP TS38.889 v16.0.0). In this study, various regulatory requirements for unlicensed operation below 7 GHz bands (e.g., 5 GHz and 6 GHz bands) are detailed and various deployment scenarios are considered. Furthermore, design objectives, capabilities and solutions are discussed and performance evaluations are performed.

[0063] The study identified five possible deployment scenarios (see, for example, section 6 of 3GPP TS38.889 v16.0.0): Scenario A is the case of carrier aggregation between licensed band NR (PCell) and NR-U (SCell), where the NR-U SCell can have both DL and UL or is DL only; Scenario B is dual connectivity between licensed band LTE (PCell) and NR-U (PSCell); Scenario C is a single NR-U; Scenario D is an NR cell with unlicensed band DL and licensed band UL; Scenario E is dual connectivity between licensed band NR (PCell) and NR-U (PSCell).

[0064] Furthermore, depending on the region and band, regulatory requirements must be taken into account. Such requirements include Dynamic Frequency Selection (DFS), Transmit Power Control (TPC), Listen Before Talk (LBT) and Discontinuous Transmission with limited maximum transmission duration (also known as Channel Occupancy Time COT). All these requirements, covering different regions and the 5 GHz band, must be addressed at the system design level, calling for the creation of a single global solution framework for NR-based access to unlicensed spectrum.

[0065] [Listen-Before-Talk (LBT) in Unlicensed Spectrum] The Listen Before Talk (LBT) procedure is defined as a mechanism for a device to perform a Clear Channel Assessment (CCA) check before using a channel. According to one exemplary implementation, CCA utilizes at least energy detection to determine whether another signal is present on an unlicensed channel in order to determine whether the unlicensed channel is occupied or free. For example, European and Japanese regulations mandate the use of LBT in unlicensed bands. Beyond the regulatory requirements, carrier detection with LBT is one way to fairly share unlicensed spectrum and is therefore considered a key feature for the fair and friendly operation of unlicensed spectrum within the framework of a single global solution.

[0066] In unlicensed spectrum, channel availability cannot always be guaranteed. In addition to this, certain regions, such as Europe and Japan, prohibit continuous transmission and impose restrictions on the maximum duration of a transmission burst in unlicensed spectrum (maximum channel occupancy time). Discontinuous transmission, which limits the maximum transmission duration, is therefore a feature for 5G NR.

[0067] According to this European regulation on LBT, a device must monitor the channel for a certain minimum time during CCA (e.g. 20 μs for Europe, see ETSI 301 893 section 4.8.3). If the detected energy level exceeds the set CCA threshold (e.g. -73 dBm / MHz for Europe, see ETSI 301 893 section 4.8.3), the channel is considered occupied, and conversely, if the detected power level is lower than the set CCA threshold, the channel is considered free. If a channel is determined to be occupied, the device does not transmit on that channel for the next fixed frame period. If the channel is classified as free, the device is allowed to transmit immediately. The maximum transmission period is limited in order to promote fair resource sharing with other devices operating in the same band.

[0068] Clear channel assessment (CCA) can be performed repeatedly, optionally with backoff periods in between.

[0069] Furthermore, the total time that a device performs transmission on a given carrier without re-evaluating the availability of that carrier (i.e. LBT / CCA) is defined as the channel occupation time (see, e.g., section 4.8.3.1 of ETSI 301 893). The channel occupation time may range from 1 ms to 10 ms, and the maximum channel occupation time may be, e.g., 4 ms as currently defined in Europe.

[0070] In addition, there is also a minimum idle time during which the UE is not allowed to transmit after transmitting on an unlicensed cell, which is at least 5% of the channel occupancy time. The UE may perform a new CCA shortly before the end of the idle period, and so on. Furthermore, after receiving a signal by another entity, CCA may not be required for a certain period of time (e.g., within 16 μs) as part of the shared channel occupancy time (COT). For example, DL to UL and UL to DL switches within the shared gNB COT do not require LBT.

[0071] To comply with this European regulation on LBT, 3GPP considered classifying NR-based access to unlicensed spectrum into four different categories (see section 8.2 of 3GPP TS38.889 v16.0.0):

[0072] Category 1: Transmit immediately after a short switching gap. This is used for transmitters to transmit immediately after a switching gap inside the COT. The switching gap from receive to transmit is to accommodate the turnaround time of the transmitter and receiver and is less than or equal to 16 μs.

[0073] Category 2: LBT with no random backoff. The amount of time the channel is detected as idle before the transmitting entity transmits is deterministic.

[0074] Category 3: LBT with random backoff using a fixed-size contention window. The LBT procedure has as one of its steps the following procedure: The transmitting entity generates a random number N within the contention window. The size of the contention window is specified by the minimum and maximum values ​​of N. The size of the contention window is fixed. The random number N is used in the LBT procedure to determine the length of time the channel is detected as idle before the transmitting entity transmits on the channel.

[0075] Category 4: LBT with random backoff using a variable-sized contention window. The LBT procedure has as one of its steps the following procedure: The transmitting entity generates a random number N within the contention window. The size of the contention window is specified by the minimum and maximum values ​​of N. The transmitting entity may vary the size of the contention window when generating the random number N. The random number N is used in the LBT procedure to determine the amount of time the channel is detected as idle before the transmitting entity transmits on the channel.

[0076] Different categories of channel access schemes may be used for different transmissions within the COT and for different channels / signals transmitted.

[0077] [Framework of unlicensed spectrum] Additionally, the study describes a technically advantageous specification "solution" for a frame structure for operation in unlicensed spectrum (see, e.g., 3GPP TS38.889 v16.0.0, section 7.2.1.1). In particular, it is recognized that it would be advantageous to support a frame structure with single or multiple switching points from DL to UL and from UL to DL within a shared gNB Channel Occupancy Time (COT). Additionally, Listen Before Talk (LBT) requirements for supporting single or multiple switching points are recognized (see, e.g., 3GPP TS38.889 v16.0.0, section 7.2.1.3.1).

[0078] For NR-U DL operation, being able to operate all DL signals / channels using the same numerology of carriers and at least in-band CA in the serving cell in the unlicensed band has been confirmed to have at least the following advantages: low implementation complexity (at least for standalone operation) (e.g. one FFT, no switching gaps), low impact on specifications, no gaps required for frequency measurements with a serving cell in the unlicensed band.

[0079] For NR-U UL operation, being able to operate all UL signals / channels (except PRACH) using the same numerology of carriers and at least in-band CA in the serving cell in the unlicensed band has been confirmed to have at least the following advantages: low implementation complexity (e.g. one FFT, no switching gaps), low impact on specifications, common interlace structure, no gaps required for SRS transmission with a serving cell in the unlicensed band.

[0080] For an unlicensed PCell, the UE assumes one SSB numerology per band.

[0081] It has been recognized that it is advantageous for the NR-U design that the gNB does not need to change the predefined TBS for PDSCH transmission depending on the results of the LBT, at least when the PDSCH is transmitted at the beginning of the gNB's COT.

[0082] For at least the first PDSCH or PDSCHs transmitted in a DL transmission burst, the following options are recognized as possible candidates for PDSCH transmission in a partial slot: These options are not mutually exclusive:

[0083] - Option 1: Release 15 NR-like PDSCH - Option 2: PDSCH punctured according to the result of LBT - Option 3: PDSCH mapping type B with duration other than 2 / 4 / 7 symbols - Option 4: PDSCH across slot boundaries

[0084] In addition to the functionality provided by DCI format 2_0 in NR Release 15, it has been identified as advantageous to indicate the COT structure in the time domain.

[0085] It has been found to be advantageous for the NR-U design that the UE does not need to change the TBSs allowed for PUSCH transmission depending on the results of the LBT.

[0086] The following options are recognized as possible candidates for at least the first PUSCH or PUSCHs transmitted in an UL transmission burst: These options are not mutually exclusive:

[0087] - Option 1: PUSCH as in Release 15 NR - Option 2: For a PUSCH scheduled by one UL grant (i.e. not a configured grant), multiple start positions in one or more slots are allowed, and one of these multiple PUSCH start positions may be determined depending on the result of the LBT. Please note that in the above options, the end position of the PUSCH is fixed as indicated by the UL grant.

[0088] Figure 8 shows an example frame structure for a shared gNB Channel Occupancy Time (COT), which includes one switching point from DL to UL with a switching gap (e.g., 16 μs) to accommodate the gNB transceiver turnaround time to switch from transmit to receive.

[0089] Recognizing that according to 3GPP different LBT categories can be used for different transmissions and different channels / signals within the COT, this example assumes a situation where the UE's PRACH transmission is assigned LBT category 4.

[0090] However, the long gap period defined by LBT Category 4 may overlap with gNB downlink transmissions resulting in unsuccessful CCA, which may result in the UE being unable to utilize the indicated PRACH occasion.

[0091] [Common scenarios] In view of the above, the authors of this disclosure have recognized the need for flexible support of downlink / uplink switching points within the channel occupation time (COT) of a gNB. Such flexible support will play an important role in the widespread acceptance of channel access schemes in unlicensed spectrum. At the same time, the authors of this disclosure have recognized that the implementation of Listen Before Talk (LBT) does not provide sufficient consideration to ensure regulatory compliance while enabling flexible support of downlink / uplink switching points within the channel occupation time (COT) of a gNB.

[0092] For uplink transmissions, especially non-scheduled PRACH transmissions, special care must be taken when introducing transmission gaps within the gNB's COT to facilitate UE uplink transmissions.

[0093] A UE must successfully complete a Clear Channel Assessment (CCA) as part of its Listen Before Talk (LBT) operation before it can perform an uplink transmission. This may seem contradictory given that this CCA is performed during the gNB's COT, i.e., during the time when the gNB occupies the channel. However, such a contradiction satisfies regulatory requirements and is easily resolved. The gNB needs to adapt its uplink scheduling to accommodate such transmission gaps within its COT and facilitate successful completion of the UE's LBT operation.

[0094] This adaptation of the uplink scheduling by the gNB is simple and straightforward for scheduled uplink transmissions, but not for non-scheduled uplink transmissions: the gNB cannot know in advance for a particular PRACH resource whether a non-scheduled PRACH transmission will be received in this resource or not, and therefore the gNB cannot know whether it needs to adapt its uplink scheduling (as a whole) to accommodate such a transmission gap in the COT (thus facilitating successful completion of the UE's LBT operation).

[0095] For these reasons, the authors of the present disclosure propose to introduce a mechanism to provide all involved UEs with an indication of the timing of the channel resources used for the Physical Random Access Channel (PRACH) transmissions. It will be readily appreciated that such an indication of timing can take various forms and may be provided separately or in combination with other functionally related information.

[0096] In any case, the gNB uses this timing indication information to inform all UEs to adapt their uplink scheduling to accommodate the transmission gaps in their COT before the channel resources used for the PRACH transmission, so that the gNB can ensure that the UEs successfully complete the LBT operation before actually performing the PRACH transmission on the channel resources used.

[0097] It will be appreciated by those skilled in the art from the following description that the proposed timing indication is not intended to and cannot replace any configuration of channel resources for the PRACH, but rather has been found to be advantageous in complementing such configuration with regard to the details of the channel access scheme for unlicensed spectrum.

[0098] 9 illustrates an exemplary communication system including a user equipment (UE) 910 and a base station (BS) 960 in a wireless communication network. Such a communication system may be a 3GPP system, such as NR and / or LTE and / or UMTS. For example, as illustrated in the figure, the base station (BS) may be a gNB (gNodeB, e.g., NR gNB) or an eNB (eNodeB, e.g., LTE gNB). However, the present disclosure is not limited to these 3GPP systems or any other system.

[0099] Although the embodiments and example implementations are described using some terminology of a 3GPP system, the present disclosure is also applicable to any other communication system, in particular any cellular, wireless, and / or mobile system.

[0100] It should be noted that many assumptions have been made to allow the principles underlying the present disclosure to be explained in a clear and understandable manner. However, it should be understood that these assumptions are merely examples for the purpose of explanation and do not limit the scope of the present disclosure. Those skilled in the art will recognize that the principles of the following disclosure and those described in the claims can be applied in various scenarios and in ways not explicitly described herein.

[0101] A mobile terminal is referred to as a user equipment (UE) in LTE and NR. A user equipment can be a mobile device such as a mobile phone, a smartphone, a tablet computer, or a USB (Universal Serial Bus) stick having the functionality of a user equipment. However, the term mobile device is not limited thereto, and in general, a repeater can have the functionality of such a mobile device, and a mobile device can function as a repeater.

[0102] A base station (BS) forms at least part of a system of interconnected units (e.g. a (central) baseband unit and various radio frequency units) and interfaces with the various antenna panels and radio heads in the network to serve the terminals. In other words, the base station provides wireless access to the terminals.

[0103] Referring again to the figure, the user equipment 910 includes a processing circuit (or processor) 930 and a transmitter / receiver (or transceiver) 920, which are shown as separate building blocks in the figure. Similarly, the base station 960 includes a processing circuit (or processor) 980 and a transmitter / receiver (or transceiver) 970, which are shown as separate building blocks in the figure. The transmitter / receiver 920 of the user equipment 910 is communicatively coupled to the transmitter / receiver 970 of the base station 960 via a wireless link 950.

[0104] 10 and 11 depict example implementations of the building blocks of a user equipment 910 and a base station 960 according to a typical scenario.

[0105] The user equipment 910 of this exemplary implementation includes an uplink (UL) symbol setting processing circuit 930-a, a physical random access channel (PRACH) channel resource timing indication information receiver 920-a, a PRACH channel resource decision processing circuit 930-b, a clear channel assessment (CCA) performing processing circuit 930-c, and a PRACH transmission transmitter 920-b. Similarly, the base station 960 of the exemplary implementation includes a UL symbol setting processing circuit 980-a, a PRACH channel resource timing indication information transmitter 970-a, a PRACH channel resource decision processing circuit 980-b, a transmission gap identification processing circuit 980-c, and a PRACH transmission receiver 970-b.

[0106] The present disclosure is described under the assumption that the user equipment 910 performs a PRACH transmission, which may be part of a random access procedure, such as the contention-based random access (RA) procedure described above, or may be part of a non-contention-based random access procedure, or may be part of some other form of random access procedure, and in any case, the present disclosure is not intended to be limited to any such random access procedure.

[0107] In any case, it should be understood that the present disclosure also covers the situation where the user equipment 910 performs the PRACH transmission without the intention or need to perform further steps of the random access procedure other than the PRACH transmission. In other words, the user equipment 910 may perform the PRACH transmission as part of a one-shot signaling mechanism for the purpose of conveying predefined information to the base station 960, for example through the transmission of a predefined RA preamble.

[0108] Furthermore, the present disclosure is described for the use case where the user equipment 910 performs PRACH transmission in an unlicensed spectrum. Instead of considering the use case where the RACH transmission is performed in a licensed spectrum, the user equipment 910 must deal with the uncertainty that the indicated channel resource (more precisely, the timing indication information of the channel resource) may not be used for the PRACH transmission. In this case, the PRACH transmission must be aborted.

[0109] In other words, unlicensed spectrum operation adds uncertainty to the PRACH transmission, and the user equipment 910 must verify (positively determine) that the timing indication information of the channel resources used (in general) for PRACH transmission can actually be used for PRACH transmission at the (specific) occupancy time of the unlicensed spectrum.

[0110] For ease of explanation, unlicensed spectrum operations are illustrated below as transmissions performed by the user equipment 910 through channel resources of an unlicensed channel. In this regard, such unlicensed channel refers to channel resources in the unlicensed spectrum used for uplink communications, in particular PRACH transmissions performed by the user equipment 910.

[0111] Of course, unlicensed spectrum operation (or uplink communication over unlicensed channels) complies with the regulatory requirements mentioned above. This includes compliance with Listen Before Talk (LBT), which involves a Clear Channel Assessment (CCA) required of the user equipment 910 prior to the actual uplink communication. Only when the CCA is positive can the user equipment 910 perform uplink communication.

[0112] FIG. 12 illustrates a sequence diagram of a user equipment (UE) performing a PRACH transmission according to a typical scenario, i.e., since the PRACH transmission of the user equipment 910 is performed over an unlicensed channel, it must check for a transmission gap for the corresponding gap period before the PRACH transmission is actually performed.

[0113] The user equipment 910 (specifically, the processing circuit 930 of FIG. 9) configures at least one symbol of the occupancy time of the unlicensed channel for uplink communication (see, for example, step 01 of FIG. 12). This operation of configuring at least one symbol for the uplink configuration is based on the received unlicensed channel access configuration. This configuration operation can be performed, for example, by the uplink symbol configuration processing circuit 930-a shown in FIG. 11.

[0114] An unlicensed channel access configuration is related to a (particular) unlicensed channel. In other words, the unlicensed channel access configuration allows the user equipment 910 to configure the access of the respective unlicensed channel (in this case at least one symbol for uplink configuration). The at least one symbol is a channel resource of the unlicensed channel.

[0115] This disclosure is described with a focus on time resources rather than frequency resources. This generalization is introduced merely for the sake of brevity. Deployment scenarios are also covered in which uplink communication is performed over channel resources specified by both time and frequency resources, such as a resource element consisting of one subcarrier for the length of one symbol (i.e., an OFDM / SC-FDMA symbol). Such a resource element is also a channel resource of an unlicensed channel.

[0116] In one example implementation, the user equipment 910 receives the configuration on which the configuration operation is based via the receiver 920 of Figure 9. In another example implementation, the user equipment 910 receives the configuration from a memory that temporarily or permanently stores the configuration for the processing circuitry 930 to perform the configuration operation.

[0117] In the context of this disclosure, the received unlicensed channel access configuration may support various implementations.

[0118] In one exemplary implementation, the configuration is used only to configure at least one symbol for uplink communication. In another exemplary implementation, the configuration is not only used to configure at least one symbol for uplink communication. Rather, at least one (some) other (different) symbol for downlink communication can be configured based on the same configuration.

[0119] In a further example implementation, the configuration includes information designating each symbol as an uplink symbol, a downlink symbol, or a flexible symbol. In yet another example implementation, the configuration specifies a switching time instance for switching between downlink and uplink communications or between uplink and downlink communications. The user equipment 910 may also configure at least one symbol for uplink communications based on such switching time instance.

[0120] In another example implementation, the configuration specifies uplink and / or downlink communications at a coarser granularity, such as at the slot or subframe level, rather than at the symbol level, where again the user equipment 910 can configure all symbols of the respective slot or subframe, as well as at least one symbol for uplink communications.

[0121] In a further exemplary implementation, this setting relates (only) to at least one individual slot of the occupancy time of the unlicensed channel, and thus the setting operation of each symbol of (this) at least one individual slot is based on this setting.

[0122] In particular, when the configuration relates to multiple individual slots of the occupied time of the unlicensed channel, this allows to configure one of the multiple individual slots to be composed entirely (or only) of symbols designated as uplink symbols or to be composed entirely (or only) of symbols designated as downlink symbols, in other words an overlap is formed.

[0123] For the purposes of explanation, if we assume that a slot consists only of designated uplink symbols, then the corresponding configuration cannot be signaled during this slot since there are no downlink symbols. Therefore, if the configuration is signaled separately for each individual slot, separate signaling is not possible for individual slots consisting only of designated uplink symbols. In order to avoid such a situation, a configuration can relate to multiple (overlapping) slots of occupied time.

[0124] In yet another exemplary implementation, the setting is related to the entire occupied time of the unlicensed channel, and thus the setting operation of all symbols in the entire occupied time is based on this setting.

[0125] In a further example implementation, the configuration relates to at least one slot (or subframe or radio frame), regardless of whether the at least one individual slot is included (contained) in the occupied time. In this regard, the user equipment 910 first determines the occupied time, and then configures only the symbols of each at least one individual slot (or subframe or radio frame) based on the configuration included in the determined occupied time.

[0126] In another example implementation, this configuration is received by the user equipment 910 in the form of semi-static signaling. Considering the signaling overhead inherent in semi-static signaling, semi-static signaling facilitates the configuration of symbols for the occupied time (total) (i.e., starting from a time instance and spanning the period during which the unlicensed channel is occupied).

[0127] Such semi-static signaling may rely on an RRC signaling mechanism, preferably including at least one Broadcast System Information (SI) Block or SI message (e.g. SIB1) or a dedicated RRC message, which includes information elements carrying respective configuration and / or indication information.

[0128] Furthermore, semi-static signaling facilitates configuration of at least one slot (or subframe or radio frame), regardless of whether at least one individual slot is included in the occupied time. If the configuration itself is not related to the occupied time, this configuration is conveyed to specify the occupied time (total) (i.e. starting from the time instance and spanning the period during which the unlicensed channel is occupied).

[0129] In a further example implementation, this configuration is received by the user equipment 910 in the form of dynamic signaling. Given the inherent low latency of dynamic signaling, the same form of dynamic signaling facilitates the configuration of symbols for a portion of the occupied time of the unlicensed channel (e.g., individual slots, or subframes or radio frames). Thus, the user equipment 910 receives multiple configurations over the duration of the occupied time.

[0130] Such dynamic signaling may rely on Medium Access Control (MAC) signaling, preferably including at least one MAC Control Element (MAC CE) conveying the respective configuration, or on Physical (PHY) signaling, preferably including at least one Downlink Control Information (DCI) (e.g. DCI format 2-0) conveying the respective configuration.

[0131] Of course, the above example implementations do not describe mutually exclusive alternatives, but can be combined to form a single functioning implementation. For example, such a combination can include both semi-static and dynamic signaling, with the dynamic signaling taking precedence over settings from the semi-static signaling (when present) at the user equipment 910.

[0132] The user equipment 910 (specifically the receiver 920 of FIG. 9) then receives an indication of the timing of the channel resources used for the Physical Random Access Channel (PRACH) transmission (see, for example, step S02 of FIG. 12). This receiving operation can be performed, for example, by the PRACH channel resource timing indication receiver 920-a shown in FIG. 11.

[0133] In the assumed deployment scenario, there are several different physical uplink channels different from the PRACH (such as PUSCH, PUCCH, ...). The unlicensed channel access configuration allows the user equipment 910 to configure at least one symbol of the uplink resource independently of the physical uplink channel to be used.

[0134] For this reason, the user equipment 910 further receives timing indication information of the channel resources used for the PRACH transmission. In other words, the received timing indication information indicates the timing (e.g., start time and / or duration, etc.) of the channel resources used by the user equipment 910 for the PRACH transmission.

[0135] At this time, the received timing indication information of the channel resource for PRACH transmission does not take into account whether the unlicensed channel is actually occupied or not, in other words, the timing indication information does not reflect whether the unlicensed channel access configuration enables the configuration of at least one symbol for uplink communication at the indicated timing of the channel resource for PRACH transmission or not.

[0136] Therefore, the user equipment 910 (specifically the processing circuitry 920 of FIG. 9) determines whether the indicated timing of the channel resource used for the PRACH transmission is included within at least one symbol configured for uplink communication (see, for example, step S03 of FIG. 12). In other words, the user equipment 910 determines whether the indicated timing of the channel resource for the PRACH transmission falls within at least one symbol configured for uplink communication. This determination operation can be performed, for example, by the PRACH channel resource determination processing circuitry 930-b shown in FIG. 11.

[0137] For purposes of example, it is assumed that an indicated timing of channel resources for PRACH transmission is received by the user equipment 910. However, as mentioned above, the indicated timing does not take into account the occupied time itself (e.g., its start time or duration), nor does it take into account compatibility with (re)configuration of the occupied time, which may result from reuse of individual symbols or slots or subframes of the occupied time, e.g., to match a reduced demand for uplink communications over unlicensed channels. As such, the user equipment 910 must constantly determine whether the indicated timing of channel resources for PRACH transmission is compatible with (re)configuration of the occupied time.

[0138] For example, a decrease in the demand for uplink communication may prompt a (re)configuration of the occupancy time such that there are more symbols for downlink communication than for uplink communication, in which case the decision operation ensures that the user equipment 910 still uses only the indicated timing of the channel resources for PRACH transmission that fits the fewer symbols for uplink communication configured based on the (re)configured occupancy time.

[0139] The separation of the above mentioned information has been found to be advantageous in that it separates each function according to its purpose, i.e. unlicensed channel access configuration for specifying (at a high level) the access to the unlicensed channel during the occupancy time, and timing indication information for specifying (at a low level) the timing of the channel resources for the PRACH transmission. Only if both individual pieces of information are present, is a PRACH transmission over the unlicensed channel facilitated.

[0140] In the context of the present disclosure, the received timing indication information of the PRACH channel resource may support various implementations.

[0141] In one exemplary implementation, the received timing indication information specifies the timing of the channel resources in the form of a start time and / or duration of the channel resources used for the PRACH transmission. In other words, the timing indication information explicitly indicates the timing of the PRACH channel resources. From such timing indication information, the user equipment 910 can infer the indicated timing of the channel resources for the PRACH transmission.

[0142] According to this example implementation, for example, the received timing indication information may indicate that the PRACH channel resource has a starting timing of symbol #0 and / or has a duration of 14 symbols. Such timing indication information thus indicates that (all) symbols #0 to #13 of a respective slot are channel resources (e.g., PRACH slots) used for PRACH transmission. From such timing indication information, the user equipment 910 may infer the indicated timing of the channel resources for PRACH transmission.

[0143] In another example implementation, the received timing indication information indicates an index into a pre-configured table (such as Table 1 above, or any of Tables 6.3.3.2-2 to 6.3.3.2-4 of 3GPP TS 38.211 v15.6.0). Again, the timing indication information explicitly indicates the timing of the PRACH channel resources. From such timing indication information, the user equipment 910 can infer the indicated timing of the channel resources for PRACH transmission by referring to the corresponding pre-configured table.

[0144] According to this exemplary implementation, for example, the received timing indication information may indicate index 22 of pre-configured Table 1, from which the user equipment 910 may infer that (all) symbols #0 to #14 of respective slots (in this case slots #1, #4, #7) are channel resources (e.g., PRACH slots) to be used for PRACH transmission.

[0145] In a further example implementation, the received timing indication information may indicate activation / disabling information of previously transmitted (pre-configured) indices of a pre-configured table (such as Table 1 above, or any of Tables 6.3.3.2-2 to 6.3.3.2-4 of 3GPP TS 38.211 v15.6.0). This timing indication information implicitly indicates the timing of the PRACH channel resources. Again, from such timing indication information, the user equipment 910 may infer the indicated timing of the enabled / disabled channel resources for PRACH transmission by referring to the previously transmitted corresponding indices of the pre-configured table.

[0146] According to this exemplary implementation, for example, the received timing indication information may indicate activation information for previously transmitted (pre-configured) index 22 of pre-configured Table 1, from which the user equipment 910 may infer that (all) symbols #0 to #13 of respective slots (in this case slots #1, #4, #7) are enabled channel resources (e.g., enabled PRACH slots) to be used for PRACH transmission.

[0147] In another example implementation, this timing indication information is received by the user equipment 910 in the form of semi-static signaling. Considering the signaling overhead inherent in semi-static signaling, the semi-static signaling facilitates indicating the timing of the PRACH channel resources for the entire occupied time (i.e., starting from the time instance and spanning the period during which the unlicensed channel is occupied).

[0148] Such semi-static signaling may rely on an RRC signaling mechanism, preferably including at least one Broadcast System Information (SI) Block or SI message (e.g. SIB1) or a dedicated RRC message, containing information elements carrying respective configuration and / or indication information.

[0149] In semi-static signaling, it is easy for the timing indication of the PRACH channel resource to cover at least one slot (or subframe or radio frame), regardless of whether at least one individual slot is included in the occupied time. If the timing indication of the PRACH resource is not related to the occupied time itself, this timing indication is conveyed to specify the occupied time (total), i.e. starting from the time instance and spanning the period during which the unlicensed channel is occupied.

[0150] In a further example implementation, the indication of the timing of the PRACH channel resource is received by the user equipment 910 in the form of dynamic signaling. Given the inherent low latency of dynamic signaling, dynamic signaling facilitates indicating the timing of the PRACH channel resource for only a portion of the occupancy time of the unlicensed channel (e.g., individual slots, or subframes or radio frames). Thus, the user equipment 910 receives multiple timing indications over the duration of the occupancy time.

[0151] Such dynamic signaling may rely on Medium Access Control (MAC) signaling, which preferably includes at least one MAC Control Element (MAC CE) carrying the respective timing indication information, and Physical (PHY) signaling, which preferably includes at least one Downlink Control Information (DCI) (e.g. DCI format 2-0) carrying the respective timing indication information.

[0152] In yet another example implementation, there is a fixed correspondence between the type of signaling used when receiving the timing indication information and when the user equipment 910 utilizes the received timing indication information to infer the respective channel resources used for PRACH transmission. In other words, the type of signaling specifies when the timing indication information should be used.

[0153] Consider the case where the timing indication information is received in the form of semi-static signaling and the user equipment 910 infers the indicated timing from the semi-static signaling. In this case, the user equipment 910 associates (based on a fixed correspondence) the indicated timing with the pre-configured (total) occupation time of the unlicensed channel. In other words, the indicated timing of the channel resource is pre-configured with respect to the occupation time of the unlicensed channel.

[0154] Consider the case where timing indication information is received in the form of dynamic signaling from which the user equipment 910 infers the indicated timing, in which case the user equipment 910 associates (based on a fixed correspondence) at least some previously configured channel resources with the enabled / disabled channel resources relative to when the signaling is received.

[0155] According to this example implementation, for example, the dynamic signaling may indicate the timing in the form of activation information, which is interpreted as being directed to the previously transmitted (pre-configured) index 22 of the pre-configured Table 1, from which the user equipment 910 may infer that (all) symbols #0 to #14 of the respective slot are the enabled channel resources (e.g. enabled PRACH slots) to be used for PRACH transmission.

[0156] In this exemplary implementation, assuming further that the dynamic signaling is received in a particular slot (e.g., slot #0) of the occupancy time of the unlicensed channel, the user equipment 910 associates (based on a fixed correspondence) the channel resource previously set through the transmitted index 22 with the channel resource to be enabled, and the channel resource to be enabled is the next slot #1 relative to when the signaling was received (e.g., slot #0).

[0157] Thus, the activation / deactivation information may only relate to previously configured channel resources that are within a specified time interval (e.g., 2 slots, 3 slots, ..., 2 subframes, 3 subframes, ..., 2 radio frames, 3 radio frames, ...) relative to when the signaling is received. In other words, the activation / deactivation information is due to the use of dynamic signaling that is associated with the time interval to which this information applies.

[0158] Consider again the case where the timing indication information is received in the form of dynamic signaling and the user equipment 910 infers the indicated timing from this dynamic signaling, where in an alternative scenario the indicated timing of the channel resources covers a portion of the occupancy time of the unlicensed channel relative to when the signaling is received.

[0159] In this case, the activation / deactivation information may only relate to previously configured channel resources that are within a specified time interval (e.g., 2 slots, 3 slots, ..., 2 subframes, 3 subframes, ..., 2 radio frames, 3 radio frames, ...) relative to when the signaling is received. In other words, the activation / deactivation information is due to the use of dynamic signaling that is associated with the time interval to which this information applies.

[0160] Although not the focus of this disclosure, according to further example implementations, it is understood that an indication of the timing of the PRACH channel resources can be combined with an indication of the frequency content of the PRACH resources, this combined information being received by the user equipment 910 in a single receiving operation.

[0161] For example, the frequency indication may indicate activation / deactivation information for a previously transmitted parameter (such as the parameter msg1-FDM described above). In this regard, the activation / deactivation information may be used to indicate the PRACH frequency resource n RA ∈{0,1,...,M-1} can be enabled / disabled individually or all together.

[0162] Again, it should be understood that the above example implementations do not describe mutually exclusive alternatives, but can be combined to form a single functioning implementation, such as for example, including both semi-static and dynamic signaling, with the dynamic signaling taking precedence over timing indication information from the semi-static signaling (when present) at the user equipment 910.

[0163] The user equipment 910 then proceeds to the next operation if the determination is positive (case "Y") (see, for example, step S04 of FIG. 12), whereas if the determination is not positive, i.e., negative (case "N"), it determines that the timing indication information of the channel resource used for PRACH transmission is invalid (see, for example, step S05 of FIG. 12).

[0164] Again, the received timing indication of the channel resources for the PRACH transmission does not take into account whether the unlicensed channel is actually occupied or not, and therefore the timing indication may be invalid in the decision operation and therefore unusable.

[0165] Furthermore, if the determination is positive (case "Y"), the user equipment 910 (specifically its processing circuitry 920) performs a clear channel determination (CCA) (see, for example, step S06 in FIG. 12). The clear channel determination is performed for a gap period before the start of the indicated timing of the channel resource used for PRACH transmission. This CCA operation can be performed, for example, by the CCA execution processing circuitry 930-c in FIG. 11.

[0166] In the context of this disclosure, the CCA operation may support various implementations for obtaining the gap period.

[0167] This CCA operation serves to evaluate whether the channel is free before actually performing the PRACH transmission. As mentioned above, CCA is governed by the listen-before-talk requirement mandated by the regulatory requirements for operating over unlicensed channels. CCA ensures that the user equipment 910 does not use the unlicensed channel in the situation where another equipment performs a transmission operation after some time.

[0168] In one example implementation, the user equipment 910 (specifically its receiver 920) receives an indication of a gap period for which to perform clear channel assessment (CCA), which is received before the user equipment 910 intends to perform a PRACH transmission, so that the user equipment 910 can perform CCA before the start of the indicated timing of the channel resource used for the PRACH transmission.

[0169] In another example implementation, the user equipment 910 does not receive an indication of the gap period. Instead, the user equipment 910 (specifically, its processing circuitry) generates a random number N. The user equipment 910 then performs CCA for gap periods whose lengths vary based on the random number N.

[0170] In a further example implementation, assume that multiple gap periods are specified by standardization (e.g., 16 μs and 25 μs, etc.) When the user equipment 910 receives an indication of the gap period, it receives an indication of which of the multiple gap periods to use.

[0171] For example, the received gap period indication information may distinguish between a first case (user equipment 910 recognizes that a gap period of 16 μs is used for CCA purposes) and a second case (user equipment 910 recognizes that a gap period of 25 μs is used for CCA purposes).

[0172] The gap period of 16 μs corresponds to the value specified by regulatory requirements. In the following description, the gap period of 16 μs specified by regulatory requirements is assumed.

[0173] If a subcarrier spacing of 15 kHz is assumed, the symbol duration is 66 μs. In this case, a gap period of 16 μs corresponds to approximately 24% of the 66 μs symbol duration. If a subcarrier spacing of 60 kHz is then assumed, the symbol duration is 16.5 μs. In this case, a gap period of 16 μs corresponds to 97% of the 16.5 μs symbol duration. As the transmission band becomes more frequent, it is expected that the subcarrier spacing used for transmission operation will be further increased (e.g., values ​​of 120 kHz and above). In such cases, the symbol duration will be further shortened, and therefore the 16 μs gap period may contain more than one symbol.

[0174] In yet another example implementation, the user equipment 910 receives an indication of a gap period in the form of one of a number of listen-before-talk (LBT) categories, and if the one LBT category is used only in one gap period, the user equipment 910 infers from the one LBT category which gap period to use in the CCA operation.

[0175] For example, for LBT category 1, the gap duration is less than 16 μs. In such a case, the user equipment 910 immediately performs a PRACH transmission without performing CCA. The gap duration is short enough that no devices other than the indicated device can use the channel. Therefore, no collisions are expected. The user equipment 910 also operates as specified for LBT category 1 above.

[0176] In a further example implementation, the user equipment 910 receives an indication of one of the gap periods in combination with an indication of one of the LBT categories, and recognizes a gap period to use in a CCA operation from the indication of one of the gap periods.

[0177] For example, for LBT Category 2, the gap period is either 16 μs or 25 μs. Because the 16 μs gap period is used in either CCA operation according to LBT Category 1 or CCA operation according to LBT Category 2, signaling the gap period (only) is insufficient for the user equipment 910 to know whether it should operate as specified for LBT Category 1 or LBT Category 2.

[0178] For this reason, the combination of the gap duration indication information and the LBT category indication information is advantageous since it not only indicates the gap duration to be used for CCA operation before the start of the indicated timing of the channel resources used for PRACH transmission, but also specifies the behavior of the user equipment 910.

[0179] In another example implementation, the user equipment 910 receives gap period indication information that instructs the user equipment 910 that it should not perform PRACH transmission, and thus the user equipment 910 stops PRACH transmission at the indicated timing of the channel resource used for the PRACH transmission.

[0180] The above exemplary implementation form can be summarized as Table 2 below, according to which the user equipment 910 receives one of the following indication information of the gap period:

[0181] [Table 2]

[0182] The user equipment 910 then proceeds to the next operation (e.g., see step S07 of FIG. 12) if the CCA is positive (case "Y"), whereas if the CCA is not positive, i.e., negative (case "N"), the user equipment 910 aborts the PRACH transmission at the indicated timing of the channel resource used for the PRACH transmission.

[0183] Furthermore, if the CCA operation is positive (case “Y”), the user equipment 910 (specifically its transmitter 920) performs a PRACH transmission over the channel resources by transmitting a random access (RA) preamble within at least one symbol configured for uplink communication. The transmission operation is performed, for example, by a PRACH transmission transmitter 930-b.

[0184] The above description has been made from the perspective of the user equipment 910. However, this should not be understood as limiting the present disclosure. The base station 960 equally performs the general scenarios disclosed herein.

[0185] Again, this disclosure is described under the assumption that base station 960 receives a PRACH transmission, which may be part of a random access procedure, such as the contention-based random access (RA) procedure described above, or may be part of a non-contention-based random access procedure, or may be part of yet another form of random access procedure, and in any case, this disclosure should not be understood as being limited to any such random access procedure.

[0186] In any case, it should be understood that the present disclosure also covers the situation where the base station 960 receives the PRACH transmission without intending or needing to perform further steps other than receiving the PRACH transmission of the random access procedure. In other words, the base station 960 may receive the PRACH transmission as part of a one-shot signaling mechanism for the purpose of conveying predefined information from the user equipment 910, for example through the transmission of a predefined RA preamble.

[0187] FIG. 13 illustrates a sequence diagram of a base station (BS) receiving a PRACH transmission according to a typical scenario, i.e., the base station 960's receiving operation of the PRACH transmission is performed over an unlicensed channel, and therefore the BS must check the transmission gap for the corresponding gap period before the PRACH transmission is actually performed.

[0188] The base station 960 (specifically, its processing circuitry 970) configures at least one symbol of the occupancy time of each unlicensed channel for uplink communication (see, for example, step 01 in FIG. 13). The at least one symbol is configured based on the unlicensed channel access configuration. This configuration operation is performed, for example, by the UL symbol configuration processing circuitry 980-a in FIG. 10.

[0189] The base station 960 (specifically its transmitter 970) then transmits an indication of the timing of the channel resources used for the Physical Random Access Channel (PRACH) transmission (see, for example, step S02 of FIG. 13). This transmission operation is performed, for example, by a PRACH channel resource timing indication transmitter 970-a.

[0190] The base station 960 (specifically its processor 980) then determines whether the indicated timing of the channel resource used for PRACH transmission is included within at least one symbol configured for uplink communication (see, for example, step S03 of FIG. 13). This determination operation is performed, for example, by the PRACH channel resource determination processing circuit 980-b.

[0191] If the determination is negative (see case "N" in step S04 of FIG. 13), the base station 960 determines that the indicated timing of the channel resources used for the PRACH transmission is invalid (see, for example, step S05 of FIG. 13).

[0192] If the determination is positive (see, for example, case "Y" in step S04 of FIG. 13), the base station 960 (specifically its processing circuitry 980) identifies whether a transmission gap is set with a gap period before the start of the indicated timing of the channel resource used for the PRACH transmission (see, for example, step S06 of FIG. 13). This identification operation is performed, for example, by a transmission gap identification processing circuitry 980-c.

[0193] If the identification is negative (see, for example, case "N" in step S07 of FIG. 13), the base station 960 stops receiving the PRACH transmission at the indicated timing of the channel resource used for the PRACH transmission.

[0194] If the identification of a transmission gap is positive (see, for example, case "Y" in step S07 of FIG. 13), the base station 960 (specifically its receiver 970) receives a PRACH transmission in the form of a random access (RA) preamble transmitted within at least one symbol configured for uplink communication at the indicated timing of the channel resource used for the PRACH transmission. This receiving operation is performed, for example, by the PRACH transmitter receiver 970-b.

[0195] [First exemplary implementation] In a first exemplary implementation, the operation of the user equipment 910 according to a general scenario is described in more detail. In particular, this first exemplary implementation focuses on a scenario in which the user equipment 910 performs PRACH transmission over an unlicensed channel that is configured according to channel occupation time (COT) structure information (or parameters) provided via physical downlink control channel signaling.

[0196] Figure 14 shows a flow chart according to a first exemplary implementation. In this flow chart, a 5G NR deployment scenario is assumed and corresponding terminology is used. For example, not only a physical random access channel (PRACH) in the uplink but also a physical downlink control channel (PDCCH) in the downlink is mentioned. In this respect, the user equipment 910 not only performs the transmission of the uplink, i.e., the PRACH, but also performs the reception of the PDCCH in the downlink.

[0197] To this end, the user equipment 910 receives a PDCCH configuration (see, for example, step S01 of FIG. 14), which configures the user equipment 910 to be able to receive control information over a physical downlink control channel. With the PDCCH configuration, the user equipment 910 is configured to receive downlink control information (DCI) over the PDCCH.

[0198] Two different starting points must be distinguished. According to a first starting point, the user equipment 910 is in an "RRC connected" state. In this "RRC connected" state, the user equipment 910 is configured to receive dedicated control messages defined by the RRC (Radio Resource Control) protocol. In this case, the user equipment 910 receives the PDCCH configuration via a dedicated RRC control message.

[0199] This PDCCH configuration (received via a dedicated RRC control message) complements various cell-specific configurations provided via SystemInformationBlockType1 (SIB1 for short). SIB1 is broadcast to all user equipments 910 served by the cell. In other words, for all supplementary configurations not specified in the PDCCH configuration, the user equipments 910 follow SIB1.

[0200] According to the second starting point, the user equipment 910 is in an "RRC idle" state or an "RRC inactive" state. In either state, the user equipment 910 is not configured to receive dedicated control messages defined by the RRC protocol. However, the user equipment 910 is configured to receive cell-specific configuration provided via SystemInformationBlockType1 (SIB1 for short). At this point, the user equipment 910 receives the PDCCH configuration via the broadcasted SIB1.

[0201] Furthermore, the user equipment 910 receives via the same SIB1 (or via a supplementary SIB1) a parameter "prach-ConfigurationIndex" (see e.g. step S02 of Fig. 14) which specifies time-domain related aspects of the Physical Random Access Channel (PRACH) transmission, such as the slot number(s) of the radio frame carrying the PRACH transmission, the duration of the PRACH transmission in number of symbols, the start symbol of the PRACH transmission, the sequence used as RA preamble, etc. In this respect, the parameter "prach-ConfigurationIndex" indicates the timing (e.g. duration) of the channel resources used for the PRACH transmission.

[0202] In a first exemplary implementation, the user equipment (UE) 910 utilizes all aspects related to the time domain specified by the parameter "prach-ConfigurationIndex" except for the starting symbol of the PRACH transmission. In other words, the user equipment 910 expects to be provided with a dynamic indication of the starting symbol used for the PRACH transmission. The user equipment 910 expects to receive this dynamic indication during the occupancy time of the unlicensed channel. Using such a separate (dynamic) indication of the starting symbol allows further flexibility, i.e. the dynamic signaling can indicate a different starting symbol if needed, even at the last moment.

[0203] For the purposes of example, assuming that the signaled parameter "prach-ConfigurationIndex" contains the value 22, the user equipment 910 infers from pre-configured Table 1 (described above) that the channel resources used for PRACH transmission are slots #1, #4, and #7. In particular, all these channel resources have a duration of 14 symbols. However, as described above, this timing indication of the channel resources for PRACH transmission does not take into account whether the unlicensed channel is actually occupied.

[0204] In this respect, the user equipment 910 further receives an unlicensed channel access configuration (see, for example, step S03 of FIG. 14). In this first exemplary implementation, the unlicensed channel access configuration is signaled in the form of channel occupation time structure information (hereinafter "COT structure information"). The user equipment 910 configures at least one symbol of the occupation time of each unlicensed channel for uplink communication based on the received "COT structure information".

[0205] In other words, the "COT structure information" structures the channel occupation time, i.e., the time when the unlicensed channel is occupied for 5G NR operation. For example, if the unlicensed channel is shared between 5G NR and WiFi operation, the occupation time of the unlicensed channel refers exclusively to the time when the channel is occupied for 5G NR operation, i.e., the time when the user equipment 910 can reasonably expect to receive downlink communications and be scheduled for uplink communications.

[0206] However, such exclusive 5G NR operation does not mean that the user equipment 910 must not perform PRACH transmissions outside the channel occupancy time (COT). Conversely, the user equipment 910 may be prompted to perform PRACH transmissions outside the COT in some circumstances (e.g., see the description of FIG. 19). These PRACHs differ only in that interference with WiFi operation is not excluded outside the COT.

[0207] More specifically, the user equipment 910 receives the "COT structure information" via a physical downlink control channel (PDCCH), preferably within a respective field of a downlink control information (DCI) format. The "COT structure information" may be transmitted, for example, via DCI format 2-0 in the PDCCH. More specifically, the user equipment 910 monitors and decodes the PDCCH according to the PDCCH configuration in order to receive the "COT structure information".

[0208] The received “COT structure information” enables the user equipment 910 to configure at least one symbol of the occupancy time of each unlicensed channel for uplink communication.

[0209] In other words, the "COT structure information" conveys information about how individual symbols of the channel occupancy time (COT) are structured, i.e., when switching points between downlink and uplink (or vice versa) occur. More specifically, the "COT structure information" designates symbols of multiple slots of the occupancy time as either uplink symbols, downlink symbols, or flexible symbols, and the receiver receives multiple, partially overlapping "COT structure information" in operation.

[0210] Table 3 below shows a specific example of the "COT structure information", that is, the "COT structure information" specifies the "COT structure" for each symbol of a fixed duration of one slot individually. However, this Table 3 does not provide a list of all COT structures and should not be understood as a limitation of the present disclosure.

[0211] [Table 3]

[0212] In this Table 3, the "COT Structure Information" specifies an uplink symbol ("U" in Table 3), a downlink symbol ("D" in Table 3), or a flexible symbol ("F" in Table 3) for a fixed duration of one slot (corresponding to a sequence of 14 symbols).

[0213] Table 4 below shows another specific example of the "COT structure information", i.e., the "COT structure information" specifies the "COT structure" for each symbol of variable duration of one or two slots individually. However, this Table 4 does not provide a list of all COT structures and should not be understood as a limitation of the present disclosure.

[0214] [Table 4]

[0215] In this Table 4, the "COT Structure Information" specifies an uplink symbol (abbreviated as "U" in the table), a downlink symbol (abbreviated as "D" in the table), or a flexible symbol (abbreviated as "F" in the table) for a variable duration of one slot (corresponding to a sequence of 14 symbols) or two slots (corresponding to a sequence of 28 symbols).

[0216] In case the "COT structure information" specifies the "COT structure" of two (consecutive) slots, a signaling overlap occurs when two separately received "COT structure information" specify the "COT structure" of one and the same slot. This overlap facilitates the creation of some redundancy and also facilitates the improvement of the flexibility of the "COT structure", i.e. the COT structure including slots consisting of only uplink symbols.

[0217] We will explain in more detail how the flexibility of the "COT structure" is improved. Assuming the case where the "COT structure" is specified most flexibly and includes slots consisting (completely) of uplink symbols only, for such a "COT structure" the "COT structure information" needs to be signaled in the form of a combined signaling of the "COT structure" of at least two or more slots.

[0218] Now, for the purpose of example, assume that the "COT structure information" specifies the "COT structure" of a slot (e.g., slot #K) that contains only uplink symbols. In this case, this "COT structure information" cannot be received in the same slot (slot #K) because this slot is specified by the "COT structure" to have only uplink signals. In other words, for this "COT structure" that specifies a slot that has only uplink signals, the respective "COT structure information" needs to be signaled in another slot, i.e., the previous slot (e.g., slot #K-1).

[0219] Further assume in this example that this "COT structure information" was signaled in a previous slot (e.g. slot #K-1) and specifies for the next slot (slot #K) a "COT structure" that contains only uplink symbols. Again, no further "COT structure information" can be signaled in the next slot (slot #K) because this slot (slot #K) is specified to have a "COT structure" that contains only uplink symbols.

[0220] For this reason, when the "COT structure" is defined most flexibly and includes slots consisting (completely) of uplink symbols only, it is necessary to signal the respective "COT structure information" in the form of a combined signaling of the "COT structure" of at least two or more slots.

[0221] The creation of a degree of redundancy will now be explained in more detail. Consider the case where there is "COT structure information" that combines the signaling of multiple "COT structures" for at least two or more (consecutive) slots. In this case, signaling of corresponding "COT structure information" in each of the two or more slots is not prevented or prohibited as long as such signaling is permitted by the specified "COT structure". Rather, some degree of redundancy is created by signaling corresponding "COT structure information" in each of the two or more slots.

[0222] Now, for the purpose of example, assume that in one slot (say slot #K), we signal the "COT Structure Information" according to Table 4. This "COT Structure Information" has a value of 7. According to Table 4, the value of 7 specifies a "COT Structure" of two slots, i.e., a "COT Structure" of "DDDDDDDDDDDDDD DDDDDDDDDDDDFU".

[0223] In this example, in the next (consecutive) slot (e.g. slot #K+1), further "COT Structure Information" according to Table 4 is not prevented or prohibited from being signaled. In this case, this "COT Structure Information" has the value 1. According to Table 4, the value 1 specifies the "COT Structure" of one slot, i.e. the "COT Structure" of "DDDDDDDDDDDDFU".

[0224] In other words, the same "COT Structure" of "DDDDDDDDDDDDFU" is signaled in the (second) slot of "COT Structure Information" with value 7 as in the (first) slot of "COT Structure Information" with value 1. For this reason, by signaling corresponding "COT Structure Information" in each of two or more slots in this way, a degree of redundancy is created.

[0225] After receiving the parameter "prach-ConfigurationIndex" serving as an indication of the duration of the channel resources used for the Physical Random Access Channel (PRACH) transmission and further receiving "COT structure information" serving as the configuration of at least one symbol of the occupancy time of the respective unlicensed channel for uplink communication, the user equipment 910 proceeds to the next operation.

[0226] Specifically, the user equipment 910 determines whether the indicated duration of the channel resources used for the PRACH transmission is contained within (or falls within) at least one symbol configured for uplink communication (see, e.g., step S04 of FIG. 14). To further illustrate this determination operation, reference is made to the example shown in FIG.

[0227] FIG. 15 illustrates an exemplary operation of a user equipment 910 according to a first exemplary implementation form, i.e., the user equipment 910 performs PRACH transmission over an unlicensed channel that is configured according to “COT structure information” provided via PDCCH signaling.

[0228] As depicted in this figure, the user equipment 910 receives in slot #3 a PDCCH conveying "COT structure information" (with value 7) according to Table 4 above. The value 7 specifies the "COT structure" of consecutive slots #3 and #4, i.e., a "COT structure" of "DDDDDDDDDDDDDD UUUUUUUUUUUUUU." In this regard, slot #4 has a "COT structure" that includes only uplink symbols.

[0229] At the same time, the received parameter "prach-ConfigurationIndex" with the value 22 according to Table 1 indicates to the user equipment that the duration of the PRACH channel resource is 14 symbols. Note that the user equipment ignores the starting symbol indicated via the parameter "prach-ConfigurationIndex".

[0230] The user equipment 910 then determines whether the duration of the indicated 14 symbols used as channel resources for the PRACH transmission fits into the uplink symbols set based on the "COT structure information". In other words, the user equipment 910 determines whether the "COT structure" has a large enough number of consecutive uplink symbols to include the duration in symbols of the PRACH channel resource.

[0231] Since slot #4 has a “COT structure” that includes 14 uplink symbols, the user equipment 910 determines that the indicated duration of the PRACH channel resource for slot #4 (also 14 symbols) can be contained (fitted) within the symbols designated as uplink symbols by the “COT structure”.

[0232] For this reason, in the depicted example, the user equipment 910 positively determines slot #4 as resembling the channel resources of the unlicensed channel used for PRACH transmission.

[0233] This positive determination causes the user equipment 910 to proceed to identify an LBT category that specifies the behavior when accessing an unlicensed channel (see, for example, step S05 of FIG. 14). In this example, the user equipment 910 receives an indication of one of the gap periods in combination with an indication of the LBT categories that are used together from the multiple LBT categories.

[0234] Such indications can be sent in the same PDCCH as the "COT structure information" or in separate PDCCHs. If the same PDCCH is used, it is also possible for the gNB to use different CRC scrambling RNTIs (Radio Network Temporary Identifiers) to distinguish between these purposes. If the same RNTI is used to scramble a PDCCH, a UE receiving that PDCCH can decode both indications. On the other hand, if different RNTIs are used, a UE that only needs one indication can ignore decoding the second indication.

[0235] The user equipment 910 may receive this indication on a PDCCH in slot #3, which is the same as the PDCCH in slot #3 in which the "COT structure information" is conveyed as described in relation to Figure 15. Alternatively, the user equipment 910 may receive this PDCCH in the previous slot.

[0236] Now, for purposes of example, assume that the user equipment 910 receives an indication with a value of 2 that should be interpreted according to Table 2 above. In this case, the user equipment 910 knows that it must use a gap period of 25 μs when performing CCA and that it must operate according to LBT category 2. In this example, the user equipment 910 knows that it finds (e.g., receives) a valid LBT category (see, e.g., step S06 of FIG. 14) and proceeds to determine whether a PRACH is required (case "Y").

[0237] Now, for the purpose of another example, assume that the user equipment 910 receives an indication of value 4 to be interpreted according to Table 2 above. In this case, the user equipment 910 cannot determine a valid LBT category (case "N" in step S06 of FIG. 14). The user equipment 910 infers that the timing of the positively determined PRACH channel resource is invalid (see, for example, step S07 of FIG. 14). No PRACH transmission is performed at this invalid timing.

[0238] Returning to the case where the user equipment finds a valid LBT category, the user equipment 910 checks whether a PRACH transmission needs to be performed (see, e.g., step S08 of FIG. 14). If a PRACH transmission does not need to be performed (case "N"), the user equipment 910 knows not to take further action (see, e.g., step S09 of FIG. 14).

[0239] If PRACH transmission needs to be performed (case "Y"), the user equipment 910 performs a clear channel determination (CCA) (see, for example, step S10 of FIG. 14). The clear channel determination (CCA) is performed for the indicated gap period 25 μs before the start of the timing of the channel resource used for PRACH transmission. In other words, the user equipment 910 performs the CCA before the start of slot #4.

[0240] Referring again to the exemplary operation of the user equipment 910 shown in FIG. 15, the user equipment 910 actually performs CCA before the start of slot #4, i.e., before the start of the timing indicated as a channel resource for PRACH by the “prach-ConfigurationIndex” having a value of 22 and positively determined to include uplink symbols as specified by the “COT Structure”.

[0241] Further, if the CCA operation is positive (successful), the user equipment 910 performs a PRACH transmission over the channel resources by transmitting a random access (RA) preamble in at least one symbol (i.e., slot #4) configured for uplink communication (e.g., see step S10 of FIG. 14).

[0242] FIG. 16 illustrates another exemplary operation of a user equipment 910 according to a first exemplary implementation form, i.e., the user equipment 910 performs PRACH transmission over an unlicensed channel that is configured according to “COT structure information” provided via PDCCH signaling.

[0243] This figure differs from the previously described example in that the received parameter "prach-ConfigurationIndex" indicates the duration of the PRACH as 6 symbols instead of 14 symbols as in FIG.

[0244] In this case, the user equipment infers the starting symbol of the PRACH according to two pieces of information obtained: the first piece of information is the "COT structure" indicating the 14 UL symbols of slot #4, and the second piece of information is the duration of the PRACH. Starting from the first indicated UL symbol, the user equipment attempts to include a PRACH until the remaining UL symbols cannot contain one PRACH. As a result, the 14 UL symbols of the indicated slot #4 contain two PRACH time instances, starting with symbol #0 and symbol #6, respectively.

[0245] However, the scheduling node can further control the use of the indicated UL symbols by manipulating the gap for CCA before each PRACH time instance. For example, if the gNB does not intend to receive PRACH in the first PRACH time instance (from symbol #0 to symbol #5), the scheduling node can indicate no gap for CCA for the first PRACH time instance (e.g., value 4 in Table 2). Upon receiving such information, the user equipment knows that the first PRACH time instance is invalid and refrains from transmitting PRACH. The scheduling node can use the first six UL symbols to schedule other UL transmissions, such as PUCCH or PUSCH, without worrying about collisions caused by the PRACH transmitted by the (non-scheduled) UE. In contrast, if the scheduling node expects to receive PRACH in the second PRACH time instance (from symbol #6 to symbol #11 in slot #4), the scheduling node indicates a valid CCA period (e.g., 25 μs) to the user equipment. In this case, the user equipment performs CCA before the start of symbol #6 of slot #4.

[0246] Because the second CCA operation is positive (or successful), the user equipment 910 performs a PRACH transmission over these channel resources by transmitting a random access (RA) preamble in at least one symbol configured for uplink communication (i.e., symbols #6 to #12 of slot #4).

[0247] [Second exemplary implementation] In a second exemplary implementation, the operation of the user equipment 910 according to a general scenario is described in more detail. In particular, this second exemplary implementation focuses on determining whether the exact timing of the previously configured (pre-configured) channel resources for the PRACH (e.g., PRACH occasion) fits the dynamically signaled unlicensed channel access configuration.

[0248] Figure 17 shows a flow chart according to a second exemplary implementation. In this flow chart, a 5G NR deployment scenario is assumed and corresponding terminology is used. For example, not only a Physical Random Access Channel (PRACH) in the uplink but also a Physical Downlink Control Channel (PDCCH) in the downlink is mentioned. In this respect, the user equipment 910 not only performs uplink, i.e. PRACH transmission, but also performs downlink PDCCH reception.

[0249] To this end, the user equipment 910 receives a PDCCH configuration (see, for example, step S01 of FIG. 17), which configures the user equipment 910 to be able to receive control information over a physical downlink control channel. With the PDCCH configuration, the user equipment 910 is configured to receive downlink control information (DCI) over the PDCCH.

[0250] Two different starting points must be distinguished. According to a first starting point, the user equipment 910 is in an "RRC connected" state. In this "RRC connected" state, the user equipment 910 is configured to receive dedicated control messages defined by the RRC (Radio Resource Control) protocol. In this case, the user equipment 910 receives the PDCCH configuration via a dedicated RRC control message.

[0251] This PDCCH configuration (received via a dedicated RRC control message) complements various cell-specific configurations provided via SystemInformationBlockType1 (SIB1 for short). SIB1 is broadcast to all user equipments 910 served by the cell. In other words, for all supplementary configurations not specified in the PDCCH configuration, the user equipments 910 follow SIB1.

[0252] According to the second starting point, the user equipment 910 is in an "RRC idle" state or an "RRC inactive" state. In either state, the user equipment 910 is not configured to receive dedicated control messages defined by the RRC protocol. However, the user equipment 910 is configured to receive cell-specific configuration provided via SystemInformationBlockType1 (SIB1 for short). At this point, the user equipment 910 receives the PDCCH configuration via the broadcasted SIB1.

[0253] Furthermore, the user equipment 910 receives via the same SIB1 (or via a supplementary SIB1) a parameter "prach-ConfigurationIndex" (see, for example, step S02 in FIG. 17). This parameter serves as a timing indication indicating the exact timing (e.g. start time and duration) of the channel resources used for the Physical Random Access Channel (PRACH) transmission. In other words, the timing indication allows the user equipment 910 to infer when, i.e. at what time, the channel resources used for the PRACH transmission are provided.

[0254] This parameter specifies time domain related aspects of the Physical Random Access Channel (PRACH) transmission, such as the slot number(s) of the radio frame carrying the PRACH transmission, the duration of the PRACH transmission in number of symbols, the starting symbol of the PRACH transmission, the sequence used as RA preamble, etc. In this respect, the parameter "prach-ConfigurationIndex" indicates the timing (e.g. start time and duration) of the channel resources used for the PRACH transmission.

[0255] Unlike the first exemplary implementation, this second exemplary implementation is based on the understanding that the parameter "prach-ConfigurationIndex" specifies the exact timing of the channel resources that can be used for the PRACH transmissions thereafter. If this timing of the channel resources is determined to match the dynamically indicated "COT structure", the user equipment 910 does not deviate from such timing of the channel resources pre-configured via RRC.

[0256] For the purposes of example, assuming that the signaled parameter "prach-ConfigurationIndex" has the value 22, the user equipment 910 infers from pre-configured Table 1 (described above) that the channel resources used for PRACH transmission are symbols #0 to #13 in slots #1, #4 and #7. However, as described above, this timing indication of the channel resources for PRACH transmission does not take into account whether the unlicensed channel is actually occupied.

[0257] In this respect, the user equipment 910 further receives an unlicensed channel access configuration (see, for example, step S03 of FIG. 17). In this second exemplary implementation, the unlicensed channel access configuration is also signaled in the form of channel occupation time structure information (hereinafter "COT structure information"). The user equipment 910 configures at least one symbol of the occupation time of each unlicensed channel for uplink communication based on the received "COT structure information".

[0258] In other words, the "COT structure information" structures the channel occupation time, i.e., the time when the unlicensed channel is occupied for 5G NR operation. For example, if the unlicensed channel is shared between 5G NR and WiFi operation, the occupation time of the unlicensed channel refers exclusively to the time when the channel is occupied for 5G NR operation, i.e., the time when the user equipment 910 can reasonably expect to receive downlink communications and be scheduled for uplink communications.

[0259] However, such exclusive 5G NR operation does not mean that the user equipment 910 must not perform PRACH transmissions outside the channel occupancy time (COT). Conversely, the user equipment 910 may be prompted to perform PRACH transmissions outside the COT in some circumstances (e.g., see the description of FIG. 19). These PRACHs differ only in that interference with WiFi operation is not excluded outside the COT.

[0260] In particular, if no "COT structure information" is received (see, e.g., step S04 in FIG. 17), the user equipment 910 infers that the status of the configured PRACH channel resource is unknown (see, e.g., step S05 in FIG. 17). In other words, the user equipment 910 understands that the unlicensed channel is shared between 5G NR and WiFi operation at the timing of the configured PRACH channel resource.

[0261] In this respect, the user equipment 910 assumes operation according to LBT category 4 in the PRACH transmission (see, for example, step S06 in FIG. 17). In other words, the user equipment 910 generates a random number N and performs CCA for a gap period that varies based on the random number N. If the CCA is positive, the user equipment 910 performs the PRACH transmission over these channel resources by transmitting a random access (RA) preamble at the PRACH time instance (start time and duration) configured by "prach-ConfigurationIndex". If the CCA is unsuccessful, the PRACH transmission is aborted.

[0262] 19 illustrates an exemplary operation of a user equipment 910 according to a second exemplary implementation. In this case, the user equipment 910 performs PRACH transmission outside the channel occupation time (COT) using LBT category 4 behavior. Because the timing of the configured PRACH channel resource in slot #1 is outside the COT, the user equipment 910 does not receive "COT structure information" for this slot. In other words, the user equipment 910 performs PRACH transmission after successful CCA for a variable gap duration based on a random value.

[0263] More specifically, the user equipment 910 receives the "COT structure information" via a physical downlink control channel (PDCCH), preferably within a respective field of a downlink control information (DCI) format. The "COT structure information" may be transmitted, for example, via DCI format 2-0 in the PDCCH. More specifically, the user equipment 910 monitors and decodes the PDCCH according to the PDCCH configuration in order to receive the "COT structure information".

[0264] The received “COT structure information” enables the user equipment 910 to configure at least one symbol of the occupancy time of each unlicensed channel for uplink communication.

[0265] However, unlike the first exemplary implementation, in this second exemplary implementation, the “COT structure information” corresponds to instruction information for enabling / disabling previously configured (pre-configured) channel resources (e.g., PRACH occasions) for PRACH (and therefore whether / not PRACH transmission can be performed at those timings).

[0266] In other words, the "COT structure information" conveys information on how individual symbols of the channel occupancy time (COT) are structured, i.e., when switching points between downlink and uplink (or vice versa) occur. More specifically, the "COT structure information" designates symbols of multiple slots of the occupancy time as either uplink symbols, downlink symbols, or flexible symbols, and the receiver receives multiple, partially overlapping "COT structure information" in operation.

[0267] For specific examples of "COT structure information", please refer to Tables 3 and 4 and the respective descriptions above.

[0268] Upon receiving the parameter “prach-ConfigurationIndex” serving as an indication of the exact timing (e.g. start time and duration) of the channel resources to be used for the Physical Random Access Channel (PRACH) transmission, and further receiving the “COT structure information” serving as a setting of at least one symbol of the occupancy time of the respective unlicensed channel for uplink communication, the user equipment 910 proceeds to the next operation.

[0269] Specifically, the user equipment 910 determines whether the indicated precise timing (e.g., start time and duration) of the channel resources used for the PRACH transmission is contained (or fits) within at least one symbol configured for uplink communication (see, e.g., step S07 of FIG. 17). To further explain this determining operation, reference is made below to the example shown in FIG. 18.

[0270] FIG. 18 illustrates an exemplary operation of a user equipment 910 according to a second exemplary implementation, i.e., the user equipment 910 performs PRACH transmission over an unlicensed channel that is configured according to “COT structure information” provided via PDCCH signaling.

[0271] As depicted in this figure, the user equipment 910 receives in slot #3 a PDCCH conveying "COT structure information" (having value 9) according to Table 4 above. The value 9 specifies the "COT structure" of consecutive slots #3 and #4, i.e., a "COT structure" of "DDDDDDDDDDDDDD DFUUUUUUUUUUUU." In this regard, slot #4 has a "COT structure" that includes only 12 uplink symbols, symbol numbers #2 to #13.

[0272] At the same time, the received parameter “prach-ConfigurationIndex” having the value 22 according to Table 1 indicates to the user equipment that the start time of the PRACH channel resource is symbol number #0 and the duration of the PRACH channel resource is 14 symbols from symbol number #0 to #13.

[0273] Here, the user equipment 910 determines whether the indicated (exact) timing of the PRACH channel resource is included within the uplink symbol that is set based on the "COT structure information". In other words, the user equipment 910 determines whether the "COT structure" has an uplink symbol at the exact timing of the PRACH channel resource with respect to start time and duration.

[0274] Since slot #4 has a "COT structure" with only 12 uplink symbols and does not contain an uplink symbol at the start time (symbol number #0 or #1) as required by the received parameter "prach-ConfigurationIndex", the user equipment 910 determines that this PRACH channel resource cannot be used (see e.g. step 07, case "N" in FIG. 17). In other words, the (correct) timing of the channel resource used for PRACH transmission cannot be validated.

[0275] At this point, the user equipment 910 infers that PRACH channel resources are not allowed for the symbol configuration of two consecutive slots #3 and #4 based on the “COT structure information” value of 9 (see, for example, step S08 of FIG. 17).

[0276] The situation is different in slot #7. In slot #7, the parameter "prach-ConfigurationIndex" specifies a total of 14 uplink symbols at symbol numbers #0 to #13, and the "COT structure" results in a configuration of 14 uplink symbols at the same symbol numbers #0 to #13. The user equipment 910 therefore determines that this PRACH channel resource can be used (see, for example, step S07 of FIG. 17, case "Y"). In other words, the (precise) timing of the channel resources used for PRACH transmission is enabled.

[0277] This positive determination causes the user equipment 910 to proceed to identify an LBT category that specifies the behavior when accessing an unlicensed channel (see, for example, step S09 of FIG. 17). In this example, the user equipment 910 receives an indication of one of the gap periods in combination with an indication of the LBT categories that are used together from the multiple LBT categories.

[0278] Such indications can be sent in the same PDCCH as the "COT structure information" or in separate PDCCHs. If the same PDCCH is used, it is also possible for the gNB to use different CRC scrambling RNTIs (Radio Network Temporary Identifiers) to distinguish between these purposes. If the same RNTI is used to scramble a PDCCH, a UE receiving that PDCCH can decode both indications. On the other hand, if different RNTIs are used, a UE that only needs one indication can ignore decoding the second indication.

[0279] In this example, the user equipment 910 may receive this indication on a PDCCH in slot #6, which is the same as the PDCCH in slot #6 in which the "COT structure information" is conveyed as described in relation to Figure 18. Alternatively, the user equipment 910 may receive this PDCCH in a previous slot.

[0280] Now, for purposes of example, assume that the user equipment 910 receives an indication with a value of 2 that should be interpreted according to Table 2 above. In this case, the user equipment 910 knows that it must use a gap period of 25 μs when performing CCA and that it must operate according to LBT category 2. In this example, the user equipment 910 knows that it finds (e.g., receives) a valid LBT category (see, e.g., step S11 of FIG. 17) and proceeds to determine whether a PRACH is required (case "Y").

[0281] Now, for the purpose of another example, assume that the user equipment 910 does not receive the indication of the gap period (case "N"). In this case, the user equipment 910 does not know how to perform CCA before accessing the unlicensed channel. For this reason, the user equipment 910 infers that the PRACH transmission is not allowed over the uplink symbol configured in response to the provided "COT structure information" (see, for example, step S10 of FIG. 17).

[0282] Returning to the case where the user equipment finds a valid LBT category, the user equipment 910 checks whether a PRACH transmission needs to be performed (see, e.g., step S11 of FIG. 17). If a PRACH transmission does not need to be performed (case "N"), the user equipment 910 knows not to take further action (see, e.g., step S12 of FIG. 17).

[0283] If PRACH transmission needs to be performed (case "Y"), the user equipment 910 performs a clear channel determination (CCA) (see, for example, step S13 in FIG. 17). The clear channel determination (CCA) is performed for the indicated gap period 25 μs before the start of the timing of the channel resource used for PRACH transmission. In other words, the user equipment 910 performs CCA before the start of slot #7.

[0284] Referring again to the exemplary operation of the user equipment 910 shown in Figure 18, the user equipment 910 actually performs CCA before the start of slot #7, i.e., before the start of the timing that is indicated as a channel resource for PRACH by the "prach-ConfigurationIndex" having a value of 22 and that is positively determined to include uplink symbols specified by the "COT Structure". Note that the gNB must form a gap, for example by not transmitting a signal in part of the last symbol of the previous slot (slot #6), to facilitate CCA. Further, if the CCA operation is positive (successful), the user equipment 910 performs a PRACH transmission over the channel resources by transmitting a random access (RA) preamble within at least one symbol (i.e., slot #7) configured for uplink communication (e.g., see step S13 of FIG. 17).

[0285] [Further Aspects] According to a first aspect, a user equipment (UE) is provided, comprising a processor, a receiver, and a transmitter. The processor, in operation, configures at least one symbol of an occupancy time of each unlicensed channel for uplink communication based on a received unlicensed channel access configuration. The receiver, in operation, receives an indication of a timing of a channel resource used for a physical random access channel (PRACH) transmission. The processor, in operation, determines whether the indicated timing of the channel resource used for the PRACH transmission is included within at least one symbol configured for uplink communication. If the determination is positive, the processor, in operation, performs a clear channel assessment (CCA) for a gap period before a start of the indicated timing of the channel resource used for the PRACH transmission. If the CCA is positive, the transmitter, in operation, performs a PRACH transmission by transmitting a random access (RA) preamble at the indicated timing of the channel resource used for the PRACH transmission within at least one symbol configured for uplink communication.

[0286] According to a second aspect provided in addition to the first aspect, the receiver, in operation, further receives an indication of a gap period for which clear channel assessment (CCA) is performed before performing a PRACH transmission.

[0287] According to a third aspect provided in addition to the first aspect, if the receiver does not receive indication information of a gap period during operation, the processor generates a random number N during operation and performs CCA for a gap period that varies based on the random number N.

[0288] According to a fourth aspect provided in addition to the first or second aspect, the indication information for the gap period is one of: indication information for one gap period among a plurality of gap periods; indication information for one listen-before-talk (LBT) category used in combination with one gap period among a plurality of LBT categories; and indication information for one gap period among a plurality of gap periods in combination with indication information for one LBT category used together among a plurality of LBT categories.

[0289] According to a fifth aspect provided in addition to the fourth aspect, the gap period is one of 16 μs and 25 μs, and the LBT category is one of LBT category 1, LBT category 2, LBT category 3, and LBT category 4.

[0290] According to a sixth aspect provided in addition to the first or second aspect, the indication of the gap period is an indication that a PRACH transmission is not performed.

[0291] According to a seventh aspect, which is provided in addition to the first to sixth aspects, the receiver, in operation, further receives unlicensed channel access configuration in the form of one of semi-static signaling that sets an occupancy time starting from a time instance and spanning a period during which the unlicensed channel is occupied, and dynamic signaling that sets at least a portion of the occupancy time relative to when the signaling is received.

[0292] According to an eighth aspect, which is provided in addition to the first to seventh aspects, a processor, in operation, infers an indicated timing of the channel resources from one of: semi-static signaling indicating timing in the form of start times and / or durations of the channel resources; dynamic signaling indicating timing in the form of enablement / disablement information for at least some previously configured channel resources; dynamic signaling indicating timing in the form of start times and / or durations of at least some of the channel resources.

[0293] According to a ninth aspect provided in addition to the eighth aspect, if the processor infers the indicated timing from semi-static signaling, the indicated timing of the channel resource is pre-configured for an occupancy time of the unlicensed channel.

[0294] According to a tenth aspect provided in addition to the eighth aspect, when the processor infers the indicated timing from dynamic signaling, at least some previously configured channel resources that are enabled / disabled are based on the time when the signaling is received.

[0295] According to an eleventh aspect provided in addition to the eighth aspect, when the processor infers the indicated timing from the dynamic signaling, the indicated timing of the channel resource covers a portion of the occupancy time of the unlicensed channel relative to when the signaling is received.

[0296] According to a twelfth aspect, provided in addition to the seventh to eleventh aspects, the semi-static signaling is Radio Resource Control (RRC) signaling, preferably including at least one broadcast system information (SI) block or message or a dedicated RRC message having information elements carrying respective configuration and / or instruction information.

[0297] According to a thirteenth aspect, provided in addition to the seventh to eleventh aspects, the dynamic signaling is one of Medium Access Control (MAC) signaling, preferably including at least one MAC Control Element (MAC CE) carrying respective configuration and / or indication information, and Physical (PHY) signaling, preferably including at least one Downlink Control Information (DCI) carrying respective configuration and / or indication information.

[0298] According to a fourteenth aspect provided in addition to the first to thirteenth aspects, in operation, the transmitter does not perform a PRACH transmission over the channel resources if the CCA is negative.

[0299] According to a fifteenth aspect, provided in addition to the first to fourteenth aspects, the receiver, in operation, receives indication information of the timing of channel resources used for PRACH transmission in the form of channel occupation time (COT) structure information, and / or the COT structure information designates symbols of at least one slot of the occupied time as one of an uplink symbol, a downlink symbol, or a flexible symbol that is configured by the processor for uplink or downlink communication, respectively, and / or the COT structure information designates symbols of multiple slots of the occupied time as one of an uplink symbol, a downlink symbol, or a flexible symbol, respectively, the receiver, in operation, receives multiple overlapping COT structure information for the occupied time of the unlicensed channel for uplink communication.

[0300] According to a sixteenth aspect, there is provided a method comprising the following steps executed by a user equipment (UE): configuring at least one symbol of an occupancy time of each unlicensed channel for uplink communication based on a received unlicensed channel access configuration; receiving an indication of a timing of a channel resource used for a Physical Random Access Channel (PRACH) transmission; determining whether the indicated timing of the channel resource used for the PRACH transmission is included within at least one symbol configured for uplink communication; if the determination is positive, performing a clear channel assessment (CCA) for a gap period before a start of the indicated timing of the channel resource used for the PRACH transmission; and if the CCA is positive, performing a PRACH transmission by transmitting a random access (RA) preamble at the indicated timing of the channel resource used for the PRACH transmission within the at least one symbol configured for uplink communication.

[0301] According to a seventeenth aspect, a base station (BS) is provided, comprising a processor, a transmitter, and a receiver. The processor, in operation, configures at least one symbol of an occupancy time of each unlicensed channel for uplink communication based on an unlicensed channel access configuration. The transmitter, in operation, transmits an indication of a timing of a channel resource used for a physical random access channel (PRACH) transmission. The processor, in operation, determines whether the indicated timing of the channel resource used for the PRACH transmission is included within at least one symbol configured for uplink communication. If the determination is positive, the processor, in operation, identifies whether a transmission gap is configured having a gap period before a start of the indicated timing of the channel resource used for the PRACH transmission. If the identification of the transmission gap is positive, the receiver, in operation, receives a PRACH transmission in the form of a random access (RA) preamble transmitted within at least one symbol configured for uplink communication at the indicated timing of the channel resource used for the PRACH transmission.

[0302] According to an 18th aspect, there is provided a method comprising the following steps executed by a base station (BS): configuring at least one symbol of an occupancy time of an unlicensed channel for uplink communication based on an unlicensed channel access configuration; transmitting an indication of a timing of a channel resource used for a Physical Random Access Channel (PRACH) transmission; determining whether the indicated timing of the channel resource used for the PRACH transmission is included within at least one symbol configured for uplink communication; if the determination is positive, identifying whether a transmission gap is configured having a gap period before a start of the indicated timing of the channel resource used for the PRACH transmission; and if the identification of the transmission gap is positive, receiving a PRACH transmission in the form of a Random Access (RA) preamble transmitted within the at least one symbol configured for uplink communication at the indicated timing of the channel resource used for the PRACH transmission.

[0303] [Hardware and Software Implementation of the Disclosure] The present disclosure can be implemented by software, hardware, or software working in cooperation with hardware. Each functional block used in the description of each embodiment above can be implemented in part or in whole by an LSI such as an integrated circuit, and each process described in each embodiment can be controlled in part or in whole by the same LSI or a combination of LSIs.

[0304] The LSI may be formed as an individual chip, or may be formed as a single chip to include some or all of the functional blocks. The LSI may include a data input / output unit coupled thereto.

[0305] Depending on the degree of integration, LSI is called IC (integrated circuit), system LSI, super LSI, or ultra LSI. However, the technology to implement an integrated circuit is not limited to LSI, and it can be implemented by using a dedicated circuit, a general-purpose processor, or a dedicated processor. Furthermore, it is also possible to use FPGA (field programmable gate array), which can be programmed after the LSI is manufactured, and a reconfigurable processor, which can reconfigure the connections and settings of the circuit cells arranged inside the LSI.

[0306] The present disclosure can be implemented as digital processing or analog processing. As a result of the progress of semiconductor technology or another derivative technology, if a future integrated circuit technology replaces LSI, the future integrated circuit technology can be used to integrate the functional blocks. Biotechnology can also be applied.

[0307] The present disclosure may be implemented by any kind of apparatus, device or system having a communication capability (referred to as a communication apparatus).

[0308] Some non-limiting examples of such communications devices include phones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, e-book readers, telehealth / telemedicine equipment, vehicles providing communications capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0309] Communications devices are not limited to portable or portable, but can also include any type of equipment, device, or system that is non-portable or stationary, such as smart home devices (e.g., appliances, lights, smart meters, control panels), vending machines, and any other "things" in the Internet of Things (IoT) network.

[0310] Communication can include, for example, exchanging data through cellular systems, wireless LAN systems, satellite systems, etc., as well as various combinations thereof.

[0311] A communications device may include devices such as a controller or a sensor coupled to a communications device to perform the communications functions described in this disclosure. For example, a communications device may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications device.

[0312] The communications apparatus may further include infrastructure facilities, such as base stations, access points, and any other apparatus, devices, or systems that communicate with or control apparatuses such as the apparatuses in the non-limiting examples above.

[0313] Furthermore, the various embodiments may be implemented by means of software modules, which are executed by a processor or directly in hardware. Also a combination of software modules and hardware implementation is possible. The software modules can be stored on any kind of computer-readable storage medium, for example RAM, EPROM, EEPROM, flash memory, registers, hard disks, CD-ROM, DVD, etc. It should be noted further that individual features of the different embodiments may be the subject of another embodiment, individually or in any combination.

[0314] It will be apparent to those skilled in the art that various changes and / or modifications may be made to the present disclosure as set forth in the specific embodiments, and the present embodiments are therefore to be considered in all respects as illustrative and not restrictive.

Claims

1. A communication device, comprising: a processor configured, during operation, to set an occupancy time of a channel resource in an unlicensed spectrum, the processor configured to perform a clear channel assessment (CCA) for a gap period before the start of the channel resource used for uplink transmission; a transceiver for performing the uplink transmission within the occupied time if the CCA is positive, in operation; Equipped with When a procedure in the form of semi-static signaling is set, the communication device determines a setting related to the occupancy time by the semi-static signaling. Communications equipment.

2. The transceiver, in operation, receives an indication of timing of channel resources used for a physical random access channel (PRACH) transmission; The communications device of claim 1 , wherein the processor, in operation, determines whether the timing of channel resources used for the PRACH transmission is included in time resources configured for uplink transmission.

3. The communications device of claim 1 , wherein the CCA being positive indicates that channel resources prior to the uplink transmission are idle.

4. The communication device of claim 1 , wherein the settings related to the occupancy time include a time instance at which the occupancy time begins and a duration for which the occupancy time is occupied.

5. The communication device of claim 1, wherein when the transceiver does not receive information indicating the gap period during operation, the processor generates a random number N during operation and performs the CCA for the gap period that changes based on the random number N.

6. 2. The communication device of claim 1, wherein the transceiver, in operation, receives the indication information of the gap period in a combination of one gap period of a plurality of gap periods and one listen-before-talk (LBT) category of a plurality of LBT categories.

7. 7. The communication device of claim 6, wherein the gap period is one of 16 μs and 25 μs, and the LBT category is one of LBT category 1, LBT category 2, LBT category 3, and LBT category 4.

8. The communication device according to claim 1 , wherein, when a procedure in the form of dynamic signaling is set, the communication device determines another setting related to the occupancy time by the dynamic signaling.

9. The communications device of claim 8 , wherein at least a portion of the occupancy time relative to when the other configuration is received is indicated by the dynamic signaling.

10. The semi-static signaling is Radio Resource Control (RRC) signaling including at least one broadcast system information (SI) block or message or a dedicated RRC message having information elements carrying respective configuration or instruction information. or The dynamic signaling comprises: - Medium Access Control (MAC) signalling including at least one MAC Control Element (MAC CE) carrying said respective configuration and / or indication information; and - Physical (PHY) signaling including at least one Downlink Control Information (DCI) conveying said respective configuration and / or indication information; The communication device according to claim 8 , wherein the communication device is one of:

11. The communications device of claim 1 , wherein the transceiver, in operation, does not perform the uplink transmission over channel resources used for the uplink transmission if the CCA is negative.

12. if the gap duration is less than 16 μs, the communication device performs the uplink transmission immediately without performing the CCA; The communication device of claim 1 , wherein the communication device performs the CCA if the gap period is equal to or greater than 16 μs.

13. When the gap period is outside the occupancy time, performing the CCA using LBT Category 4; The communication device of claim 1 , wherein when the gap period is inside the occupancy time, the CCA is performed using LBT category 1 or LBT category 12.

14. 1. A method comprising the steps of: setting an occupation time of a channel resource in an unlicensed spectrum; performing a clear channel assessment (CCA) for a gap period before the start of a channel resource used for uplink transmission; performing the uplink transmission within the occupied time if the CCA is positive; Including, when a procedure in the form of semi-static signaling is configured, a configuration related to said occupancy time is determined by said semi-static signaling; method.

15. A base station (BS), a processor configured, during operation, to configure an occupancy time of a channel resource in an unlicensed spectrum; The processor identifies whether a transmission gap is configured having a gap duration before a start of a channel resource used for uplink transmission; a transceiver for receiving the uplink transmission within the occupied time if the identification of the transmission gap is positive, in operation; Equipped with when a procedure in the form of semi-static signaling is configured, a configuration related to said occupancy time is determined by said semi-static signaling; Base station (BS).

16. A method comprising the steps of: setting an occupation time of a channel resource in an unlicensed spectrum; identifying whether a transmission gap is configured, the gap duration being before a start of a channel resource used for uplink transmission; if the identification of the transmission gap is positive, receiving the uplink transmission within the occupied time; Including, when a procedure in the form of semi-static signaling is configured, a configuration related to said occupancy time is determined by said semi-static signaling; method.

17. An integrated circuit for controlling processing of a communication device, comprising: The process comprises: setting an occupation time of a channel resource in an unlicensed spectrum; performing a clear channel assessment (CCA) for a gap period before the start of a channel resource used for uplink transmission; performing the uplink transmission within the occupied time if the CCA is positive; Including, when a procedure in the form of semi-static signaling is configured, a configuration related to said occupancy time is determined by said semi-static signaling; Integrated circuits.

18. An integrated circuit for controlling processing of a base station, The process comprises: setting an occupation time of a channel resource in an unlicensed spectrum; identifying whether a transmission gap is configured, the gap duration being before a start of a channel resource used for uplink transmission; if the identification of the transmission gap is positive, receiving the uplink transmission within the occupied time; Including, when a procedure in the form of semi-static signaling is configured, a configuration related to said occupancy time is determined by said semi-static signaling; Integrated circuits.

Images