User equipment, scheduling node, method for user equipment, and method for scheduling node - Patents.com

Abstract

The circuitry obtains from the first signaling a first notification indicating a first slot format for the frequency band and from the second signaling a second notification indicating a second slot format for the frequency band, the second slot format specifying a different transmission direction than the first slot format for time intervals of the plurality of time intervals in which the first slot format specifies the transmission direction to be a downlink direction and / or specifying a different transmission direction than the first slot format for time intervals of the plurality of time intervals in which the first slot format specifies the transmission direction to be an uplink direction.

Description

[Background technology]

[0001] 1.Technical Field This disclosure relates to the transmission and reception of signals in communication systems, such as 3GPP® communication systems. In particular, this disclosure relates to methods and apparatus for such transmission and reception.

[0002] 2. Description of Related Technology The 3rd Generation Partnership Project (3GPP) is working on technical specifications for next-generation cellular technology (also known as fifth generation (5G)), including New Radio (NR) access technology (RAT), operating in the frequency range up to 100 GHz. NR is the successor to technologies represented by Long Term Evolution (LTE) and LTE Advanced (LTE-A).

[0003] In systems such as LTE and NR, further improvements and options may facilitate efficient operation of the communication system and certain devices associated with the communication system. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 [Non-patent document 2] 3GPP TS 38.211 [Non-patent document 3] ITU-R M.2083 [Non-patent document 4] TS 23.501 v16.1.0 [Non-patent document 5] 3GPP TS 38.321 [Non-patent document 6] 3GPP TS 38.331 [Non-Patent Document 7] TS 38.212 [Non-patent document 8] 3GPP TS 38.213 Summary of the Invention [Problem to be solved by the invention]

[0005] One non-limiting exemplary embodiment facilitates improving the efficiency and / or flexibility of current communication systems. In particular, it may enable flexible slot configuration / format configuration for individual UEs or specific groups of UEs, and may enable subband non-overlapping full duplex (SBFD) within conventional / legacy (e.g., Rel-15 / 16 / 17 NR) time division duplex (TDD) bands. In particular, techniques are disclosed that may enable SBFD operation in Rel-18 and beyond while minimizing impact on legacy NR deployments. [Means for solving the problem]

[0006] In one embodiment, the disclosed technology features an apparatus (e.g., a communications device, particularly user equipment (UE)). The apparatus includes a transceiver and a circuit. The transceiver, in operation, receives first signaling and second signaling, where the first signaling is cell-common signaling. The circuit, in operation, obtains, from the first signaling, a first notification indicating a first slot format for a frequency band, and obtains, from the second signaling, a second notification indicating a second slot format for the frequency band. The first slot format specifies, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. The second slot format specifies, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. Furthermore, the second slot format (i) specifies a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as a downlink direction, and / or (ii) specifies a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction.

[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 selective combination thereof.

[0008] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, but not all of them necessarily need to be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0009] The following exemplary embodiments are described in more detail with reference to the accompanying drawings. [Figure 1] FIG. 1 illustrates an example architecture of a 3GPP NR system. [Figure 2] Schematic diagram showing functional separation between NG-RAN and 5GC [Figure 3] Sequence diagram of RRC connection setup / reconfiguration procedure [Figure 4] Schematic showing enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC) usage scenarios [Figure 5] Block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario [Figure 6] A diagram showing the relationship between bandwidth portions, control resource sets (CORESETS), search spaces, search space sets, and PDCCH candidates. [Figure 7] A diagram showing an example of the time domain structure of a communication system such as 5G NR, including radio frames, subframes, slots, and OFDM symbols at various subcarrier spacings. [Figure 8] 1 illustrates the use of dedicated legacy signaling to configure flexible slots of a first (legacy cell common) slot format as downlink for some UEs (UE1 and UE3) and as uplink for other UEs (UE2). [Figure 9] A block diagram illustrating a communication system including user equipment and a base station, and the structure of the user equipment and the base station. [Figure 10] Block diagram showing the functional configuration of a processing circuit on the user device side [Figure 11] Block diagram showing the functional configuration of the processing circuit on the base station side [Figure 12] A flowchart illustrating exemplary steps performed by a user equipment and exemplary steps performed by a base station. [Figure 13] 1 is a flowchart illustrating exemplary steps performed by a user equipment to determine a transmission direction in a time interval in which a second, non-legacy slot format indicates a different transmission direction relative to a non-flexible time interval of a first, legacy slot format. [Figure 14] 14 is a flowchart illustrating exemplary steps different from those of FIG. 13 performed by a user equipment to determine a transmission direction in a time interval in which a second, non-legacy slot format indicates a different transmission direction relative to a non-flexible time interval of a first, legacy slot format. [Figure 15] 1 is a flowchart illustrating exemplary steps performed by a base station to perform SBFD on downlink symbols of a first legacy slot format. [Figure 16] 1 illustrates the use of second cell-common signaling to obtain a "D→U" configuration in the n+1 to n+3 slots of a second non-legacy slot format "DUUUU" for a first legacy cell-common slot format "DDDDU"; [Figure 17] 1 illustrates the use of second cell-common signaling for a first legacy cell-common slot format "DDDDU" to obtain a "D→F" configuration in slots n+1 to n+3 of a second non-legacy slot format "DFFFU"; [Figure 18] 10 illustrates the use of two second dedicated signalings to obtain two second non-legacy slot formats: a second slot format "DUUUU" having a "D→U" setting in the n+1st to n+3rd slots relative to the first legacy cell common slot format "DDDDU"; and a second slot format "DDFFU" having a "D→F" setting in the n+2nd and n+3rd slots relative to the first slot format. [Figure 19]1 illustrates the use of second cell-common signaling to obtain a "D→U" configuration in the n+1th slot, a "D→U" configuration in the n+2th slot, and a "U→D" configuration in the n+3th slot in a second non-legacy slot format "DUUDU" for a first legacy cell-common slot format "DDDUU"; [Figure 20] 1 illustrates the use of second cell-common signaling to obtain a "D→U" configuration in the n+1th slot, a "D→U" configuration in the n+2th slot, and a "U→F" configuration in the n+3th slot in a second non-legacy slot format "DUUFU" for a first legacy cell-common slot format "DDDUU"; [Figure 21] 10 is a diagram illustrating the use of two second dedicated signalings to obtain two second non-legacy slot formats: a second slot format "DUUDU" having a "D→U" setting in the n+1th slot, a "D→U" setting in the n+2nd slot, and a "U→D" setting in the n+3rd slot for a first legacy cell common slot format "DDDUU"; and a second slot format "DFFFU" having a "D→F" setting in the n+1st to n+3rd slots for the first slot format. DETAILED DESCRIPTION OF THE INVENTION

[0010] <5G NR system architecture and protocol stack> 3GPP continues to work on the next release of fifth-generation cellular technology (also known as simply "5G"), which includes the development of New Radio Access Technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed in late 2017, allowing for the prototyping and commercial deployment of 5G NR-compliant smartphones.

[0011] In particular, the system architecture as a whole assumes an NG-RAN (Next Generation - Radio Access Network) comprising gNBs. The gNBs provide UE-side termination of NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity that performs AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity that performs UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 1 (see, for example, Non-Patent Document 1, Version 15.6.0, Section 4).

[0012] The NR user plane protocol stack (see, for example, Section 4.4.1 of Non-Patent Document 1) includes a Packet Data Convergence Protocol (PDCP) sublayer (see, for example, Section 6.4 of Non-Patent Document 1), a Radio Link Control (RLC) sublayer (see, for example, Section 6.3 of Non-Patent Document 1), and a Medium Access Control (MAC) sublayer (see, for example, Section 6.2 of Non-Patent Document 1), which are terminated on the network side at the gNB. A new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has also been introduced on top of PDCP (see, for example, Section 6.5 of Non-Patent Document 1). A control plane protocol stack has also been defined for NR (see, for example, Section 4.4.2 of Non-Patent Document 1). An overview of Layer 2 functions is described in Section 6 of Non-Patent Document 1. The functions of the PDCP, RLC, and MAC sublayers are listed in Sections 6.4, 6.3, and 6.2 of Non-Patent Document 1, respectively. The functions of the RRC layer are listed in section 7 of Non-Patent Document 1.

[0013] For example, the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various numerologies.

[0014] For example, the physical layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. The physical layer also handles mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) as uplink physical channels, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) as downlink physical channels.

[0015] NR use cases / deployment scenarios may 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 rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates approximately three times higher than those offered by IMT-Advanced. Meanwhile, URLLC imposes stricter requirements for ultra-low latency (0.5 ms user-plane latency for both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC may require preferably high connection density (1,000,000 devices / km2 in urban environments), wide coverage in adverse environments, and extremely long battery life (15 years) for low-cost devices.

[0016] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also called TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with small delay spreads. Subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR may support two or more subcarrier spacing values. Therefore, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently considered. Symbol length T u and the subcarrier spacing Δf is given by the formula Δf=1 / T u Similar to LTE systems, the term "resource element" can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0017] In the new radio system 5G-NR, a resource grid of subcarriers and OFDM symbols is defined for each numerology and each carrier in the uplink and downlink, respectively. Each element of 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 Non-Patent Document 2, Version 15.6.0 or, for example, Version 16.2.0, Section 4). For example, downlink and uplink transmissions are configured as frames with a time length of 10 ms. Each frame consists of 10 subframes, each with a time length of 1 ms. In a 5G NR implementation, the number of consecutive OFDM symbols per subframe depends on the subcarrier spacing setting. For example, with a subcarrier spacing of 15 kHz, a subframe has 14 OFDM symbols (similar to an LTE-compliant implementation, assuming a normal cyclic prefix). On the other hand, with a subcarrier spacing of 30 kHz, a subframe has two slots, each with 14 OFDM symbols.

[0018] NR supports several different types of subcarrier spacing, labeled by the parameter μ, compared to LTE numerology (subcarrier spacing and symbol length). (LTE only allows 15 kHz subcarrier spacing, which corresponds to μ=0 in NR.) The types of NR numerology are summarized in NR 2015, ed. 15.7.0.

[0019] <Functional separation between NG-RAN and 5GC in 5G NR> Figure 2 shows the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0020] In particular, the gNB and ng-eNB host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, encryption, and integrity protection of data; - AMF selection at UE attach time if routing to the AMF cannot be determined from information provided by the UE; - Routing of user plane data towards UPF; - Routing of control plane information towards AMF; - Connection setup and release; - scheduling and sending of paging messages; - Scheduling and transmission of system broadcast information (originating from AMF or Operation, Admission, and Maintenance (OAM) functions); - Setting up measurements and reporting of measurements 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; - Non-Access Stratum (NAS) message delivery functions; - Sharing of radio access networks; - Dual connectivity; - Close cooperation between NR and E-UTRA.

[0021] The Access and Mobility Management Function (AMF) hosts the following main functions: - Terminating Non-Access Stratum (NAS) signaling; - NAS signaling security; - Access Stratum (AS) security controls; - 3GPP Core Network (CN) inter-node signaling for mobility between access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Managing the registration area; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization, including checking roaming privileges; - Mobility management control (subscription and policy); - Network slicing support; - Selection of Session Management Function (SMF).

[0022] Additionally, the User Plane Function (UPF) hosts the following main functions: - Anchor points for intra-RAT / inter-RAT mobility (if applicable); - External PDU (Protocol Data Unit) session points for interconnection with data networks; - Packet routing and forwarding; - Packet inspection and policy rule enforcement for the user plane; - Traffic usage reporting; - uplink classifier that supports routing of traffic flows to the data network; - Branching Point for supporting multi-homed PDU sessions; - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement); - Verification of uplink traffic (mapping to the QoS flow of the SDF); - Downlink packet buffering and triggering function for downlink data notification.

[0023] Finally, the Session Management Function (SMF) hosts the following main functions: - Session management; - Allocation and management of IP addresses for the UE; - Selection and control of the UPF; - Traffic steering setting function in the User Plane Function (UPF) for routing traffic to the appropriate destination; - Policy enforcement and QoS in the control part; - Notification of downlink data.

[0024] <Procedures for RRC connection setup and reconfiguration> Figure 3 shows some of the interactions between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see Non-Patent Document 1, version 15.6.0).

[0025] RRC is a higher layer signaling protocol used to configure the UE and the gNB. In particular, with this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sends it to the gNB with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB reconfigures the UE to set up a Signaling Radio Bearer 2 (SRB2) and a Data Radio Bearer (DRB). For signaling-only connections, the RRCReconfiguration steps are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0026] Therefore, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: control circuitry that, in operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, in operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.

[0027] <IMT usage scenarios from 2020 onwards> Figure 4 illustrates some use cases for 5G NR. The 3rd Generation Partnership Project New Radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 4 illustrates some examples of expected usage scenarios for IMT beyond 2020 (see, for example, Figure 2 in Non-Patent Document 3).

[0028] URLLC use cases have stringent performance requirements such as throughput, latency, and availability, and are envisioned as one of the enablers of future applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, automated power transmission and distribution in smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by [Non-Patent Document 3]. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms on the uplink (UL) and 0.5 ms on the downlink (DL). A typical URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.

[0029] From a physical layer perspective, reliability can be improved in many possible ways. Current reliability improvement room includes defining a separate CQI table for URLLC, a more compact DCI format, repeated transmission of PDCCH, etc. However, this room can be expanded to achieve ultra-high reliability as NR (with respect to the key requirements of NR URLLC) becomes more stable and developed. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0030] Additionally, technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repeated transmission in the data channel, and preemption in the downlink. Preemption means that a transmission with already allocated resources is stopped and the allocated resources are used for another transmission with a later requested lower latency / higher priority. Thus, a previously allowed transmission is preempted by a later transmission. Preemption is applicable 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 for reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0031] The use case for massive machine-type communication (mMTC) is characterized by a very large number of connected devices that typically transmit relatively small amounts of data that are not sensitive to latency. These devices are required to be low cost and have very long battery life. From an NR perspective, using very narrow bandwidth portions is one solution that saves power and allows for long battery life for the UE.

[0032] As mentioned above, the scope of reliability improvement in NR is expected to become broader. One of the key requirements for all cases, especially for URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can improve reliability from a radio perspective and a network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, data channel / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.

[0033] Further use cases with more stringent requirements are envisioned for NR URLLC, such as factory automation, transportation, and power distribution. The stringent requirements include high reliability (10 -6 reliability up to a certain level), high availability, packet sizes up to 256 bytes, time synchronization up to a few microseconds (depending on the use case, the value can be 1 microsecond or a few microseconds depending on the frequency range and low latency in the 0.5ms-1ms range (especially for targeted user plane latency of 0.5ms).

[0034] Furthermore, for NR URLLC, several technical extensions are possible from the perspective of the physical layer. These technical extensions include the extension of the Physical Downlink Control Channel (PDCCH) related to compact DCI, the repeated transmission of PDCCH, and the increased monitoring of PDCCH. Also, the extension of UCI (Uplink Control Information) is related to the extension of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Additionally, there may be extensions of PUSCH related to hopping at the mini-slot level, and extensions of retransmission / repeated transmission. The term "mini-slot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0035] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (GBR (Granteed Bit Rate) QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) that is carried in an encapsulation header via the NG-U interface.

[0036] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for each PDU session, e.g., as shown above with reference to Figure 3. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and the 5GC associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and the NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0037] Figure 5 shows the non-roaming reference architecture for 5G NR (see Section 4.23 of Non-Patent Document 4). An Application Function (AF) (e.g., an external application server hosting 5G services as illustrated in Figure 4) interacts with the 3GPP core network to provide services, for example, to support application influence on traffic routing, access to a Network Exposure Function (NEF), or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on the operator's deployment, Application Functions that are considered trusted by the operator can interact directly with the relevant Network Functions. Application Functions that are not permitted by the operator to directly access Network Functions interact with the relevant Network Functions using an external exposure framework via the NEF.

[0038] Figure 5 further illustrates further functional units of the 5G architecture, namely, 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-provided services, Internet access, or third-party services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.

[0039] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) including: a transmitter configured, in operation, to transmit a request including QoS requirements for at least one of a URLLC service, an eMBB service, and an mMTC service to at least one of 5GC functions (e.g., an NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit configured, in operation, to perform a service using the established PDU session.

[0040] <Control signal> In the present disclosure, the downlink control signal (information) related to the present disclosure may be a signal (information) transmitted via a PDCCH of a physical layer, or may be a signal (information) transmitted via a MAC Control Element (CE) of a higher layer or RRC. The downlink control signal may be a predefined signal (information).

[0041] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted via a PUCCH of a physical layer, or may be a signal (information) transmitted via a MAC CE of a higher layer or RRC. The uplink control signal may also be a predefined signal (information). The uplink control signal may be uplink control information (UCI), first-stage sidelink control information (SCI), or second-stage sidelink control information.

[0042] <Uplink / Downlink / Sidelink> The present disclosure may be applied to any of the uplink, downlink, and sidelink.

[0043] For example, the present disclosure may be applied to the uplink PUSCH, PUCCH, and PRACH, the downlink PDSCH, PDCCH, and PBCH, and the sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).

[0044] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel, respectively. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel, respectively. The PBCH and PSBCH are examples of a broadcast channel, and the PRACH is an example of a random access channel.

[0045] <Data channel / control channel> The present disclosure may be applied to both data channels and control channels. The channels in the present disclosure may be replaced with data channels including PDSCH, PUSCH, and PSSCH, and / or control channels including PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0046] <Reference signal> In this disclosure, a reference signal is a signal known to both a base station and a mobile station, and each reference signal may be referred to as a reference signal (RS) or a pilot signal. A reference signal may be any of a DMRS, a Channel State Information - Reference Signal (CSI-RS), a Tracking Reference Signal (TRS), a Phase Tracking Reference Signal (PTRS), a Cell-specific Reference Signal (CRS), and a Sounding Reference Signal (SRS).

[0047] <time interval> In the present disclosure, the time resource unit is not limited to one or a combination of a slot and a symbol, and may be a time resource unit such as a frame, a superframe, a subframe, a slot, a subslot of a time slot, a minislot, or a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing Access (SC-FDMA) symbol, or other time resource unit. The number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be other numbers of symbols.

[0048] <Frequency band> The present disclosure may be applied to both licensed and unlicensed bands.

[0049] <Communication> The present disclosure may be applied to communication between a base station and a terminal (Uu link communication), communication between terminals (sidelink communication), and V2X (Vehicle to Everything) communication. The channels in the present disclosure may be rephrased as PSCCH, PSSCH, physical sidelink feedback channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0050] The present disclosure can be applied to both terrestrial networks and non-terrestrial networks (NTNs) using satellites or high altitude pseudo satellites (HAPSs). The present disclosure can also be applied to networks with large cell sizes and terrestrial networks with large delays compared to the symbol length or slot length, such as ultra-wideband transmission networks.

[0051] <Antenna port> An antenna port refers to a logical antenna (antenna group) formed from one or more physical antennas. That is, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas constituting an antenna port is not defined. Instead, an antenna port is defined as the smallest unit through which a terminal is permitted to transmit a reference signal. An antenna port can also be defined as the smallest unit for multiplication of precoding vector weights.

[0052] <Downlink control channel monitoring, PDCCH, DCI> Many of the functions performed by a UE include monitoring a downlink control channel (e.g., PDCCH, see 3GPP TS 26.110, version 15.6.0, section 5.2.3) to receive, for example, specific control information or data intended for the UE.

[0053] Below is a non-exhaustive list of such features: - Paging message monitoring function, - System information acquisition function, - signaling supervision operation in discontinuous reception (DRX) functionality; - inactivity monitoring behavior in the discontinuous reception (DRX) function; - receiving a random access response in a random access function; - Packet Data Convergence Protocol (PDCP) layer reordering function As described above, the PDCCH is monitored by the UE to identify and receive information intended for the UE, such as control information and user traffic (e.g., DCI on the PDCCH, user data on the PDSCH indicated by the PDCCH).

[0054] These DCI formats represent the predetermined formats that the respective information is formed and transmitted in. In particular, DCI formats 0_1 and 1_1 are used for scheduling the PUSCH and PDSCH in one cell, respectively.

[0055] The PDCCH monitoring in each of these functions serves a specific purpose and is therefore initiated for that purpose. PDCCH monitoring is typically controlled at least based on a timer operated by the UE. The timer has the purpose of controlling PDCCH monitoring, for example, to limit the maximum length of time that the UE monitors the PDCCH. For example, the UE does not need to monitor the PDCCH indefinitely and can stop monitoring after a certain time to conserve power.

[0056] As mentioned above, one of the purposes of the DCI in the PDCCH is to dynamically schedule resources in the downlink, uplink, or sidelink. In particular, several formats of the DCI are provided to convey notification of resources allocated to a data channel for a particular user (resource allocation, RA). The resource allocation may include specifying resources in the frequency domain and / or the time domain.

[0057] <Physical resource block> The term "physical resource block" (PRB) typically refers to the smallest allocable resource unit available for transmission of (user) data. In LTE and NR, a PRB has a predetermined number of consecutive subcarriers in the frequency domain (e.g., 12) and a predetermined number of symbols in the time domain (e.g., 14 OFDM symbols in LTE).

[0058] <BWP:bandwidth part> The NR system supports much wider channel bandwidths (e.g., hundreds of MHz) than the 20 MHz of LTE. LTE also supports wideband communications through carrier aggregation (CA) of component carriers up to 20 MHz. By defining wider channel bandwidths in NR, frequency resources can be dynamically allocated through scheduling, which can be more efficient and flexible than the carrier aggregation operation of LTE, where activation / deactivation is based on MAC control elements. Having a single wideband carrier also has the advantage of reducing control overhead by requiring only a single control signaling (carrier aggregation requires separate control signaling for each aggregated carrier).

[0059] Furthermore, similar to LTE, NR may also support aggregation of multiple carriers via carrier aggregation or dual connectivity.

[0060] Because UEs do not always require high data rates, the use of a wide bandwidth can result in higher idle power consumption, both in terms of RF and baseband signal processing. In this regard, the newly developed concept of bandwidth portions for NR provides a means for UEs to operate at bandwidths smaller than the configured channel bandwidth, providing an energy-efficient solution while supporting wideband operation. This benefits low-end terminals that cannot access the entire bandwidth for NR.

[0061] A bandwidth part (BWP) is a subset of the total cell bandwidth of a cell (e.g., the location and number of contiguous physical resource blocks (PRBs)). Bandwidth parts may be defined separately for the uplink and downlink. Furthermore, each bandwidth part may be associated with a specific OFDM numerology (e.g., subcarrier spacing and cyclic prefix). For example, bandwidth adaptation is achieved by configuring a BWP in a UE and informing the UE which of the configured BWPs is the currently active BWP.

[0062] Illustratively, in 5G NR, a specific BWP is configured only for a UE in the RRC_Connected state. For example, other than an initial BWP (e.g., one for UL and one for DL), a BWP exists only for a UE in the connected state. To support initial data exchange between the UE and the network, for example, during the process of moving the UE from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state, an initial DL BWP and an initial UL BWP are configured in the minimum system information.

[0063] A UE may have more than one BWP defined (e.g., up to four BWPs per serving cell as currently defined for NR), but the UE has only one active DL BWP at a time.

[0064] For details of BWP operation, see section 5.15 of Non-Patent Document 5.

[0065] Switching between configured BWPs can be achieved in various ways. The operation of bandwidth portions in the uplink and downlink is defined in 3GPP TS 36.11b, version 16.8.0, section 5.15 for a 5G NR-compliant implementation. The BWP can be switched, for example, by downlink control information (DCI) (e.g., using the bandwidth portion indicators in DCI format 0_1 (UL grant) and DCI format 1_1 (DL schedule)), by using the BWP inactivity timer, by using RRC signaling, or by the MAC entity itself at the start of the random access procedure. For a primary cell (PCell), the initial BWP is the BWP used for initial access, and the default BWP is the initial BWP unless another initial BWP is explicitly configured. For a secondary cell (SCell), the initial BWP is always explicitly configured, and a default BWP can also be configured. When a default BWP is configured for a serving cell, the active BWP switches to the default BWP when the inactivity timer associated with that cell expires.

[0066] Some DCI formats (such as formats 0_0 and 1_0) do not include a BWP ID, while other DCI formats (such as formats 0_1, 0_2, 1_1, and 1_2) allow the number of bits for the BWP ID to be configurable by RRC, which may be 0, 1, or 2 bits.

[0067] FIG. 6 shows a scenario in which three different BWPs are set: BWP1, which has a frequency bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP2, which has a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP3, which has a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz.

[0068] The different BWPs can be configured, for example, using appropriate information elements of the RRC protocol. A carrier bandwidth portion is a contiguous set of physical resource blocks selected from a contiguous subset of common resource blocks of a given numerology (u) on a given carrier.

[0069] According to an exemplary 5G NR compatible implementation in accordance with 3GPP TS 36.11, e.g., version 16.8.0, different RRCReconfiguration information elements can be used.

[0070] <Control information: Search space set> PDCCH monitoring is performed by the UE to identify and receive information intended for the UE, such as control information and user traffic (eg, DCI on the PDCCH and user data on the PDSCH indicated by the PDCCH).

[0071] Control information in the downlink (which can be referred to as, for example, Downlink Control Information (DCI)) has essentially the same purpose in 5G NR as DCI in LTE, i.e., it is a special set of control information for scheduling, for example, a downlink data channel (e.g., PDSCH) or an uplink data channel (e.g., PUSCH). In an exemplary implementation according to 5G NR, there are several different DCI formats already defined (see 3GPP TS 26.10, 17.1.0, section 7.3.1). An overview is provided in the following table: [Table 1]

[0072] In 5G NR, the PDCCH is transmitted in a radio resource region called the control resource set (CORESET). In LTE, the concept of a CORESET does not explicitly exist. Instead, the PDCCH in LTE uses the entire carrier bandwidth in the first one to three OFDM symbols (four in the narrowest case). In contrast, the CORESET in NR can occur anywhere within a slot and anywhere within the frequency range of the carrier, except that the UE is not supposed to process the CORESET outside the active bandwidth portion (BWP).

[0073] Therefore, the UE performs PDCCH monitoring operations as specified in 3GPP TS 23.110, e.g., version 17.1.0, clauses 10 and 11. In the exemplary specification, the UE monitors a set of PDCCH candidates defined as a PDCCH search space set. The search space set can be a common search space (CSS) or a UE-specific search space (USS).

[0074] As exemplarily defined in Section 10.1 of Non-Patent Document 8, the UE: - the Type0-PDCCH CSS set by MIB pdcch-ConfigSIB1 or PDCCH-ConfigCommon searchSpaceSIB1 or PDCCH-ConfigCommon searchSpaceZero for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG; - Type0A-PDCCH CSS set by searchSpaceOtherSystemlnformation in PDCCH-ConfigCommon for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG - Type1-PDCCH CSS set by ra-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell - Type2-PDCCH CSS set by the pagingSearchSpace of PDCCH-ConfigCommon for DCI formats with CRC scrambled by P-RNTI on the primary cell of the MCG - Type3-PDCCH CSS set by SearchSpace in PDCCH-Config with searchSpaceType=common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, or CI-RNTI and, for the primary cell only, by C-RNTI, MCS-C-RNTI, CS-RNTI, or PS-RNTI. - a USS set configured by the SearchSpace of the PDCCH-Config with searchSpaceType=ue-Specific for a DCI format with a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL semi-persistent scheduling V-RNTI The PDCCH candidate is monitored in one or more of the sets of CSSs and USSs, such as:

[0075] Each activated serving cell configured for PDCCH monitoring with the corresponding search space set monitors one or more CORESETs in the active DL BWP, where monitoring implies decoding each PDCCH candidate according to the monitored DCI format.

[0076] Conceptually, Figure 6 shows an exemplary relationship between bandwidth portions, CORESETs, search spaces, search space sets, and PDCCH candidates that a UE can monitor. As is apparent from Figure 6, one CORESET is shown per BWP, but there can be more than one. Each CORESET can have several search spaces for one or more PDCCH candidates at a particular aggregation level (e.g., AL2, 4, or 8). These search spaces can be grouped into search space sets, such as shared SS sets and UE-specific SS sets.

[0077] <Time domain in 5G NR> In the time domain, 5G NR transmissions are organized into frames of 10 ms length, each divided into ten equally sized subframes of 1 ms length. Subframes are divided into one or more slots of 14 OFDM symbols each. The time length of a slot, in milliseconds, depends on the numerology. Thus, for example, with a subcarrier spacing of 15 kHz, an NR slot has the same structure as an LTE subframe with a regular cyclic prefix. A subframe in 5G NR serves as a numerology-independent time reference, which is particularly useful when multiple numerologies are mixed on the same carrier, while a slot is a typical dynamic scheduling unit. This frame structure, on which 3GPP 5G NR communications are based, is exemplarily shown in Figure 7.

[0078] <Rel-15 / 16 / 17 NRにおけるスロットフォーマット> In Rel-15 / 16 / 17 NR, the gNB informs the UE of the transmission direction via the slot format (transmission directions are uplink (U), downlink (D), and flexible (F)). The slot format may be semi-statically configured by RRC or dynamically configured by DCI. For semi-static configuration, cell-level common signaling (tdd-UL-DL-ConfigurationCommon) or dedicated RRC signaling (tdd-UL-DL-ConfigurationDedicated) can be used. To dynamically configure the slot format, a slot format indicator (SFI) is sent to the UE (SlotFormatIndicator via DCI format 2_0).

[0079] According to the Rel-15 / 16 / 17 specifications, when configuring the slot format, the semi-static cell-common D and U symbols cannot be changed by UE-dedicated RRC or dynamic configuration (DCI2_0). Therefore, conflicting configurations between the cell-common slot configuration and dedicated RRC or specific UE dynamic configuration are currently not allowed (i.e., for each time interval and UE, the transmission direction must follow or be "allowed" to the cell-common slot configuration). In other words, only the semi-static cell-common F symbol can be overwritten to D or U by UE-dedicated RRC or DCI2_0. If the semi-static cell-common F symbol is not changed to a D or U symbol (either by UE-dedicated RRC or DCI2_0), the UE follows the scheduling DCI (DCI formats 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2) to determine whether to transmit or receive.

[0080] <Further improvements> 3GPP is constantly exploring further possibilities to extend coverage (UL and / or DL), improve resource utilization efficiency, reduce latency, etc. For example, Rel. 18 concerns "studying the evolution of NR duplex operation" (with minimal or no impact on legacy UEs, if possible).

[0081] The slot format configuration for Rel-15 / 16 / 17 NR has been briefly described above. The inventors have conducted various studies to solve the above-mentioned problems. For example, in conventional time division duplex (TDD) operation, the limited time length allocated for the uplink in TDD can result in reduced coverage, increased latency, and reduced capacity. Providing full-duplex operation within the TDD band can enable a longer UL time length to expand UL coverage, reduce latency, and increase UL capacity. This is one of the main topics of the "Study on the Evolution of Duplex Operation in NR."

[0082] However, for subband non-overlapping full-duplex (SBFD) operation at a gNB, the gNB may need to be able to configure different transmission directions for different UEs in the same symbol / slot. In the Rel-15 / 16 / 17 specifications, this can only be achieved through UE-specific RRC slot format configuration or DCI2_0. An example using UE-specific RRC is shown in Figure 8. More specifically, the first row in Figure 8 shows a semi-static configuration example configured by the base station via cell-level common signaling (tdd-UL-DL-ConfigurationCommon). The semi-static configuration is "DDDFU" for five slots (e.g., each symbol in the D slot is a D symbol, and similarly for the U and F slots). However, as shown in Figure 8, the existing signaling scheme (UE-specific RRC slot format configuration or DCI2_0 (not shown in Figure 8)) can only override the semi-static flexible symbol / slot. For example, in the example of Figure 8, the scheduling device can override only the flexible fourth slot (i.e., further configure the slot as a U slot or a D slot for individual UEs). This is shown in the second row of Figure 8, where three dedicated RRC signalings (tdd-UL-DL-ConfigurationDedicated) are used to indicate to three UEs that the F slot is a D slot or a U slot, respectively. More specifically, it indicates to UE1 and UE3 that the F slot is a D slot (to UE1 and UE3), and it indicates to UE2 that the F slot is a U slot (to UE2).

[0083] This may mean that SBFD is only allowed for F slots / symbols, and SBFD means full-duplex operation on the gNB side and half-duplex operation on the UE side. In other words, when performing full-duplex operation, the gNB simultaneously transmits and receives using the same frequency band resources. However, at a given time, each UE is either only transmitting or only receiving on the frequency band resources. In other words, in Figure 8, SBFD is only performed in the fourth slot, where UE2 is configured with a transmission direction (i.e., U) that is different from the transmission direction (D) configured for the other two UEs.

[0084] In particular, the term "SBFD" therefore refers to the simultaneous existence of downlink (DL) and uplink (UL) in a communication system within a frequency band or frequency sub-band (conventional / legacy time division duplex (TDD) band) in which the same cell-common slot format is used (each frequency band or some frequency bands may use / have different cell-common slot formats). When performing SBFD, the sub-band used is used to separate the transmission directions. In other words, when performing SBFD in a frequency (sub)band, different transmission directions exist in the frequency (sub)band at the same time. It should be noted that, at least from the base station's perspective, a TDD band used for SBFD may no longer operate in TDD mode.

[0085] Performing SBFD based on a quasi-static F symbol may limit base station flexibility, especially since the F symbol is not widely used in current 5G NR deployments. For example, in Japan's 5G deployments, the TDD pattern (per slot) of "DDDSUUDDDDD" is used, where S is a special slot containing the D, F, and U symbols, and the F symbol is only used in the gap for switching between D and U.

[0086] Although the above problems are caused by subband non-overlapping full-duplex operation, similar problems exist in subband overlapping full-duplex operation. In other words, it does not matter how frequency resources are allocated for full-duplex operation. As long as the base station operates in full-duplex and the UE operates in half-duplex, the following problems and corresponding solutions are applicable.

[0087] <Embodiment> The inventors have identified the possibility of providing an improved procedure that allows one or more of the above-mentioned disadvantages to be avoided. The present invention relates to different solutions and variants for such an improved procedure.

[0088] Accordingly, the present disclosure provides techniques for improving the efficiency and / or flexibility of resource usage in current communication systems.

[0089] In particular, the slot configuration / format for individual UEs or specific groups of UEs may be flexibly configured, enabling SBFD within conventional / legacy (e.g., Rel-15 / 16 / 17 NR) TDD bands. In particular, techniques are disclosed that enable supporting SBFD operation in Rel-18 and beyond while minimizing the impact on legacy NR deployments.

[0090] The present disclosure provides, inter alia, a scheduling device, a corresponding method for the scheduling device, a user equipment, a corresponding method for the user equipment, a communication system including the scheduling device and the user equipment, and an integrated circuit that, in operation, controls processes for the scheduling device / user equipment to perform the respective methods.

[0091] <Technical terms> The following describes UEs, base stations, and procedures for new radio access technologies envisioned in 5G mobile communication systems (although these may also be used in LTE mobile communication systems). Various implementations and variations are also described. The following disclosure is facilitated by, and may be based, for example, at least in part on, the above discussion and findings.

[0092] Generally, it should be noted that many assumptions have been made herein so as to explain the principles underlying the present disclosure in a clear and understandable manner. However, it should be understood that these assumptions are merely examples made herein for illustrative purposes, are not necessarily essential to the invention, and do not limit the scope of the present disclosure. Those skilled in the art will understand that the principles described in the following disclosure and claims can be applied to different scenarios and in ways not explicitly described herein.

[0093] Furthermore, although specific terminology used in the context of new radio access technologies for upcoming communication systems has not yet been fully determined or may ultimately change, some of the terms used below, such as procedures, entities, and layers, are closely related to those used in LTE / LTE-A systems or in the current 3GPP 5G standardization. Therefore, the terminology may change in the future without affecting the functionality of the embodiments. Therefore, those skilled in the art will recognize that the embodiments and their scope of protection are not limited to the specific terminology illustratively used herein due to the absence of newer or ultimately agreed-upon terminology, but should be understood more broadly in terms of the functions and concepts underlying the functions and principles of the present disclosure.

[0094] <terminal> A terminal, user terminal, user device, mobile station, or mobile node is referred to as user equipment (UE) in LTE and NR. User equipment may be a mobile device or communication device, such as a wireless telephone, smartphone, tablet computer, or universal serial bus (USB) stick with user equipment functionality. However, the term mobile device is not limited thereto; in general, a relay may also have such mobile device functionality or function as a relay. For example, a terminal is a physical entity (physical node) in a communication network. Furthermore, a communication device may be any machine-type communication device, such as an IoT device. A node may have several functional entities. A functional entity refers to a software or hardware module that realizes and / or provides a predetermined set of functions to the same node or other nodes or other functional entities of the network. A node may have one or more interfaces that attach the node to a communication facility or medium over which the node can communicate. Similarly, a network entity may have logical interfaces that attach the functional entity to a communication facility or medium over which the functional entity may communicate with other functional entities or corresponding nodes.

[0095] <Base station> In the present disclosure, a base station may be, for example, a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a base unit, or a gateway. Also, in sidelink communication, a terminal may be used instead of a base station. The base station may be a relay device that relays communication between an upper node and a terminal. The base station may be a roadside unit. The base station may be, for example, a scheduling node or a network node that forms part of a network for providing services to terminals. In particular, the base station may provide wireless access to terminals. Communication between a communication device (e.g., a UE or a terminal) and a scheduling device (e.g., a base station) is generally standardized and may be defined by various layers, such as PHY, MAC, RRC, etc. (see also the above description). In LTE and NR, the air interface protocol stack includes a physical layer, a medium access layer (MAC), and upper layers. The control plane is provided with a higher layer protocol, the Radio Resource Control Protocol. Through RRC, base stations can control the configuration of terminals, and terminals can communicate with base stations to perform control tasks such as establishing and modifying connections and bearers, measurements, and other functions. The term used in LTE is eNB (or eNodeB), while the term currently used in 5G NR is gNB. The term base station or radio base station here refers to a physical entity in a communication network. Similar to a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that realizes and / or provides a predetermined set of functions to other functional entities of the same or other nodes or networks. The physical entity performs several control tasks for communication devices, including one or more of scheduling and configuration.It should be noted that base station functionality and communication device functionality may also be integrated within a single device. For example, a mobile terminal may also implement the functionality of a base station for other terminals. The term used in LTE is eNB (or eNodeB), and the term currently used in 5G NR is gNB. In particular, a base station may be a gNB in a Non-Terrestrial Network (NTN) NR system.

[0096] As described above, the present disclosure provides a scheduling device (e.g., a base station) and a communication device (e.g., a scheduled device or user equipment). The present disclosure further provides a system including the scheduled device and the scheduling device, as well as corresponding methods and programs. An example of such a communication system is shown in FIG. 9. The communication system 900 may be a wireless communication system (particularly, an NR communication system) compliant with 5G technical specifications. However, the present disclosure is not limited to a 3GPP NR terrestrial network (TN) and may also be applied to an NTN or other wireless or cellular network.

[0097] FIG. 9 shows a general simplified exemplary block diagram of a communication device 910 (herein illustratively assumed to be a UE) and a scheduling device 960 (herein illustratively assumed to be located in a base station, e.g., an LTE eNB (also referred to as an ng-eNB) or a 5G NR gNB). However, typically, the scheduling device may be a terminal in the case of a sidelink connection between two terminals. Furthermore, particularly with regard to URLLC, eMBB, and mMTC use cases, the communication device 910 may be a sensor device, a wearable device, or a connected vehicle or a controller of an automated machine in an industrial factory. Furthermore, the communication device 910 may be capable of functioning as a relay between a base station and other communication devices (e.g., the present disclosure is not limited to a communication “terminal” or a user “terminal”).

[0098] 9, a communication device 910 and a scheduling device 960 (eNB / gNB) can communicate with each other over a (wireless) physical channel 950 using respective transceivers 920 (UE side) and 970 (base station side). The scheduling device 960 and the communication device 910 together form a communication system 900. The communication system 900 may further include other entities than those shown in FIG.

[0099] As shown in FIG. 9 (left side), the communication device comprises a transceiver and circuitry (or processing circuitry), and the scheduling device comprises a transceiver and (processing) circuitry.

[0100] A transceiver unit may include or function as a receiver and / or a transmitter. In other words, in this disclosure, the term "transceiver unit" is used for hardware and software components that enable a communication device or a base station to transmit and / or receive wireless signals, respectively, over a wireless channel. Thus, a transceiver unit corresponds to a receiver unit, a transmitter unit, or a combination of a receiver and a transmitter unit. Typically, it is assumed that base stations and communication devices can both transmit and receive wireless signals. However, for some applications, particularly eMBB, mMTC, and URLLC (smart home, smart city, industrial automation, etc.), it is possible that a device, such as a sensor, only receives signals. Furthermore, the term "circuit" includes a processing circuit formed by one or more processors or processing units, etc.

[0101] The transmitter may be responsible for performing the process of transmission and other processes related thereto, and the receiver may be responsible for performing the process of reception and other processes related thereto, such as monitoring the channel.

[0102] The circuit or processing circuit may be one or more hardware components, such as one or more processors or any LSI. Between the transceiver and the processing circuit, there is an input / output point (or node), and the processing circuit, in operation, controls the transceiver, i.e., controls the receiver and / or transmitter, and exchanges receive / transmit data. The transceiver may include a radio frequency (RF) front end, including one or more antennas, amplifiers, RF modulators / demodulators, etc., as the transmitter and receiver. The processing circuit may control the transceiver to perform control tasks, such as transmitting user data and control data provided by the processing circuit and / or receiving user data and control data that are further processed by the processing circuit. The processing circuit may also be responsible for performing other processes, such as judging, determining, calculating, measuring, etc.

[0103] According to an exemplary embodiment, there is provided a communication device 910 as illustrated in Figure 9 (left side). The communication device 910 comprises a transceiver 920 and a circuit 930.

[0104] In operation, the transceiver 920 receives “first signaling” and “second signaling,” which will be described further below. The transceiver may also transmit and receive other data and / or other control signals. The transceiver may transmit / receive according to a slot format (particularly, a second slot format). The (processing) circuit 930, in operation, (i) obtains from the first signaling a first indication indicating a “first slot format” of the frequency band, and (ii) obtains from the second signaling a second indication indicating a “second slot format” of the frequency band. The first and second slot formats will be described in more detail below. For example, the UE may obtain the first and second slot formats by analyzing the first and second signaling and / or extracting the first and second indications and / or the first and second slot formats from the first and second signaling, respectively.

[0105] It should be noted that the circuitry 930 may implement more functionality than obtaining the first and second notifications described above, such as controlling the transceiver 920 to receive control signaling (particularly the first and second signaling), receive data, and / or transmit data, and this control of the transceiver may be performed according to the first and / or second slot formats.

[0106] Thus, the circuitry 930 may be considered to include, for example, a resource handling circuit 935 configured to obtain the first and second notifications, which may be provided by hardware adaptation and / or software.

[0107] 10 illustrates an example functional structure of the resource handling circuit 935. In particular, the resource handling circuit 935 may include a slot format acquisition circuit 1010 that acquires the first and second notifications, and a transmission direction determination circuit 1020 that determines the transmission direction of the time interval according to the first and / or second slot format.

[0108] It should be noted that the resource handling circuit 935 may implement more functions. For example, the resource handling circuit 935 may determine resources for transmitting and receiving data based on a received scheduling grant (e.g., DCI / PDCCH), and the data transmission and reception may be performed according to the determined transmission direction. This functionality may be provided by a grant handling circuit 1030, which is illustratively assumed to be part of the resource handling circuit 935.

[0109] Corresponding to the above-mentioned communication device, a communication method executed by the communication device is provided. As shown in FIG. 12, the method includes a step S1225 of receiving first signaling, a step S1235 of obtaining a first notification indicating a first slot format for a frequency band from the first signaling, a step S1265 of receiving second signaling, and a step S1275 of obtaining a second notification indicating a second slot format for the frequency band from the second signaling. The obtaining steps S1235 and S1275 may be performed by analysis / extraction as described above. Note that the order of the steps may be different from that shown in FIG. 12. For example, the second signaling may be received before the notification of the first slot format is obtained. In particular, the first and second signaling may be received together, for example, as part of the same transmission.

[0110] As further shown in FIG. 12, the UE may transmit (S1285) and / or receive (S1285) data or control signals according to the first and / or second slot formats. In particular, the UE may interpret a scheduling grant allocating resources to the UE according to the transmission direction determined by the transmission direction determination circuit 1020. Thus, step S1285 may include determining the transmission direction of the assigned resources according to the first and / or second slot formats, particularly according to the transmission direction determined for the time interval and frequency band in which the assigned resources are located. More specifically, resources allocated in a time interval and frequency band whose transmission direction is determined to be UL may be interpreted as UL resources without further explicit notification from the base station (similarly, resources in a DL time interval may be interpreted as resources intended for reception by the UE without further explicit notification). Thus, the UE may assume that only DL or UL grants are present for the DL interval or UL interval, respectively, and plan its operation (e.g., buffering, sleep operation, etc.) accordingly. If the granted resources are in time intervals and frequency bands determined to be directionally flexible, the UE may expect further indication in the scheduling grant whether the allocated resources are for transmission or reception by the UE.

[0111] 9 (right side), according to another exemplary embodiment, a scheduling device 960 is provided. The scheduling device 960 includes a transceiver 970 and a circuit 980. In operation, the circuit 980 (i) determines a first slot format for the frequency band, (ii) generates first signaling including a first notification indicating the first slot format, (iii) determines a second slot format for the frequency band, and (iv) generates second signaling indicating the second slot format. Furthermore, in operation, the transceiver 970 transmits the first signaling and the second signaling.

[0112] The circuitry 980 may implement more functions than the determining and generating described above, for example, further controlling the transceiver 970 to transmit the first and second signaling, or controlling the transceiver to receive or transmit data. Thus, the circuitry 980 may be considered to include, for example, a scheduling circuit 985 configured to perform the determining and generating described above. This configuration may be provided by hardware adaptation and / or software.

[0113] 11 shows an example functional structure of the scheduling circuit 985. In particular, the scheduling circuit 985 may include a slot format determination circuit 1110 that determines first and second slot formats and a signaling generation circuit 1120 that generates first and second signaling. It should be noted that the scheduling circuit 985 may also implement more functions. For example, the scheduling circuit 985 may allocate resources to UEs and generate respective scheduling grants (e.g., pDCCH / DCI) according to the first and second slot formats corresponding to time intervals and the corresponding transmission directions. This functionality may be provided by a resource allocation circuit 1130 that is illustratively assumed to be part of the scheduling circuit 985.

[0114] Corresponding to the above-mentioned scheduling device, a communication method performed by the scheduling device is provided. As shown in Fig. 12, the method includes a step S1200 of determining a first slot format for a frequency band, a step S1210 of generating first signaling including a first notification indicating the first slot format, a step S1220 of transmitting the first signaling, a step S1240 of determining a second slot format for the frequency band, a step S1250 of generating second signaling indicating the second slot format, and a step S1260 of transmitting the second signaling.

[0115] As further shown in FIG. 12, the scheduling device may receive (S1280) and / or transmit (S1280) further transmissions (transmissions other than the transmission of the first and second signaling) according to the first and second slot formats and the transmission direction indicated to the UE by the slot formats. Step S1280 may include or be the step of allocating resources for transmission and reception to the UE according to the slot format and transmission direction in response to the generated corresponding scheduling grant and transmitting the grant to the UE. Step S1280 generally takes into account traffic conditions and quality requirements of services used by one or more UEs and may be performed jointly with scheduling of resources for other transmissions and receptions of other UEs. As already described for the UE above, the order of steps may be different from the order shown in FIG. 12. This also applies to the scheduling device. For example, after the second slot format is determined (S1240) and the second signaling is generated (S1250), the first signaling may be transmitted (S1220). For example, the first slot format and the second slot format may be determined together (e.g., in one step / jointly), the first and second slot formats may be generated together, and / or the first and second slot formats may be transmitted together, e.g., as part of the same transmission.

[0116] In particular, in this regard, it should be noted that since the present disclosure relates to resource usage and scheduling, both entities, i.e., a scheduled device (typically a communication device / transceiver device) and a scheduling device (typically a network node), are involved. Therefore, in the following description, unless explicitly stated or indicated by context, details and embodiments may apply to (and be implemented by) each of a communication device, a scheduling device (or scheduling node), and a corresponding method. In particular, the scheduling device may be configured to generate and transmit control signals, as described below, and the communication device / UE may be configured to receive such signaling and obtain notifications therefrom. In particular, any of the steps / operations described below may be performed or controlled by circuit 930 (UE side) and / or circuit 980 (base station side). Furthermore, any receiving and transmitting steps may be performed by (e.g., controlled by) the transceiver unit 920 (UE side) and / or the transceiver unit 970 (base station side) (e.g., controlled by the respective circuits).

[0117] Regarding the determination of slot formats and transmission directions by the UE and the scheduling device, it should be noted that since the UE and the scheduling device form a communication system, in general, for a particular resource granted to the UE, both devices should obtain the same transmission direction. In other words, both devices should know the same slot formats and transmission directions. However, the UE's slot format determination may differ in some respects from the scheduling device's slot format determination.

[0118] The scheduling device determination is a step in which the slot format and transmission direction are set / defined, and the UE typically only infers the slot format and transmission direction determined by the scheduling device (from corresponding signaling or notification in the signaling). In particular, the scheduling device may take into account additional parameters such as available resources, quality of service, requests from the UE (including requests from other UEs), received channel state information, traffic load, and the battery status of the UE. For example, the scheduling device may optimize all of these additional parameters and attempt to find the most suitable slot format and transmission direction based on all of them. Some of these parameters may be known to the UE or indicated by transmissions by the UE to the scheduling device, while others of these parameters (especially those related to other UEs) may not be known to the UE.

[0119] Therefore, in general, the scheduling device determines the slot format and transmission direction in its determination (e.g., steps 1200 and 1240, up to a flexible time interval that may be determined later), while the UE usually only determines / guesses the slot format and transmission direction set by the base station (for this UE). The UE's determination is based on the first and second signaling. Since the UE's determination should yield the same result as the scheduling device's (for this UE) determination, the method according to the present disclosure is generally applied to the UE and base station sides (network node, scheduling device).

[0120] Furthermore, the use of the transmission direction may concern the base station in different ways. That is, the base station may need to generate further control signaling / grant to enable the UE to determine the intended / correct transmission direction based on further control signaling in addition to the first and second signaling. Therefore, the generated first and second signaling should enable the UE to determine the transmission direction in the case of the UL and DL directions, and further notification should be sent to the UE regarding the allocated resources in the flexible time interval. Therefore, as described above, there may be a step (on the base station side) of allocating UL or DL resources to the UE depending on the transmission direction. More specifically, when allocating UL resources, resources of the time interval in which the transmission direction for this UE is uplink or flexible are selected, and when allocating DL resources to the UE, resources of the time interval in which the transmission direction for this UE is downlink or flexible are selected. The base station may then generate corresponding grants / signaling indicating the allocated resources to the UE. The UE may then receive the grants / signaling and determine the allocated resources according to the slot format. That is, the UE may determine whether the allocated resource is a UL resource or a DL resource according to the transmission direction in time / frequency of the allocated resource (or may expect further notification in the case of flexible direction).

[0121] In the above description, the first signaling and the second signaling are used to indicate the first slot format and the second slot format, respectively. The first and second slot formats do not necessarily mean that they should be transmitted by the base station (and received by the UE) in a specific order. For example, both the first and second slot formats may be transmitted by the base station (and received by the UE) simultaneously within the same SIB. In this case, the first signaling and the second signaling may be understood as two different parameters within the same SIB (the same RRC signaling).

[0122] <Slot format> In general, the slot formats (particularly the slot formats referred to herein as the “first slot format” and the “second slot format”) define, for each of a plurality of time intervals, whether the transmission direction in the time interval is flexible, the uplink direction, or the downlink direction. This description is explained in more detail below. In general, the second slot format and particularly the second signaling may not (explicitly) define the transmission direction for each time interval in which the first slot format defines the transmission direction, but may (explicitly) define the transmission direction only for a subset of the time intervals in which the first slot format defines the transmission direction. The transmission direction in time intervals in which the second slot format and / or the second signaling do not explicitly define the transmission direction may correspond to (e.g., be the same as) the transmission direction defined by the first slot format in that time interval. In other words, the second signaling may define the transmission direction only in time intervals in which the transmission directions of the second slot format and the first slot format differ from each other. Examples of such second signaling are presented in two syntax examples in the "Second Signaling - Cell Common Signaling" section below, where "slotIndex" is used to identify in which slot the second slot format has a different transmission direction.

[0123] <Slot format - frequency band> A slot format is typically for (or applied to) one or more frequency bands, and other slot formats may be applied to other frequency bands. In other words, the transmission directions of two frequency bands to which different slot formats are applied at the same time may be different from each other. The frequency bands may be indicated in the first and second signaling or may be implicitly known to the UE. For example, the frequencies to which the first and second signaling are applied may be the frequency bands in which the first and second signaling are received.

[0124] Here, the terms "first slot format" and "second slot format" refer to the same frequency band. For example, the frequency band in which the first and second slot formats define the transmission direction may be a (traditional) TDD band and / or a bandwidth portion (BWP). In general, the frequency band may be a specific frequency range or a range of frequency ranges. This range may be signaled to the UE (e.g., quasi-statically), predefined, or pre-configured (e.g., defined in a standard). The UE and the base station may use frequency bands other than the frequency bands to which the first and second slot formats apply. For ease of understanding, such other frequency bands may not always be explicitly mentioned (e.g., the transmission direction indicated by a slot format for a time interval may be stated to be a specific direction without explicitly stating that the transmission direction in the other frequency bands may be different from the transmission direction indicated by the first and second slot formats in the frequency bands to which the first and second slot formats apply).

[0125] <Slot format - time interval> As mentioned above, the slot format defines a corresponding transmission direction for each of a plurality of time intervals (transmission directions corresponding to the time intervals). These time intervals may generally be non-overlapping and contiguous, i.e., there may be no time gap between two consecutive / adjacent time intervals. In particular, the plurality of time intervals may be divisions of a period of the plurality of time intervals. Thus, the time intervals may be non-overlapping and cover the period (and thus the period itself is a time interval).

[0126] Because the time intervals are typically symbols, such time intervals are also referred to herein as flexible (F) symbols, uplink (U) symbols, or (D) downlink symbols, respectively. For example, a slot format may include downlink (D), uplink (U), and flexible (F) symbols and specify which symbols are D symbols, which symbols are U symbols, and which symbols are F symbols. In the figures, the time intervals are shown to be slots, which can, and often will, mean that each symbol in such an F / U / D slot is of the same F / U / D type.

[0127] However, the present disclosure is not limited to the specific time intervals used by the slot format. In particular, the time intervals may be symbols, frames, subframes, slots, etc., or any number of symbols, frames, subframes, slots, etc. Furthermore, in general, the time intervals may be of the same length (time length) or of different lengths (again, this may be the length of a slot / symbol / frame / subframe, etc.). The time intervals and (or any characteristics of the time intervals, such as their length and location) may be predetermined and / or the time intervals may be the basic time unit of the resource grid employed by the UE or an integer multiple of the basic time unit of the employed resource grid. Alternatively, signaling (e.g., "first signaling," "second signaling," and / or different control signaling (e.g., other DCI or RRC messages)) may include notification of the time intervals, and in particular the length of the time intervals.

[0128] The first time interval (or the first time interval in the case of multiple time intervals ordered in time) may start at the beginning of a (reference) time, such as a reference frame, subframe, slot, or symbol. This reference time may be provided by system broadcast and may be the slot / frame / symbol at which signaling indicating the slot format is received. Alternatively, the pattern may start at the beginning of the frame, subframe, slot, or symbol plus a predetermined time offset. Typically, the value of such an offset is predetermined, signaled to the UE by the scheduling device, or configured by other means.

[0129] <Slot format - repeating pattern> In general, the slot format may indicate a sequence of direction indications (here, F is considered to be one of the possible directions). The first indicated direction is considered to be the indicated transmission direction for the first time interval (first time interval when ordered in time), the second indicated direction is considered to be the transmission direction for the second time interval, and so on. However, in general, the association of indicated transmission directions may be different as long as the UE and the base station use the same convention.

[0130] In particular, the slot format may be a pattern of transmission direction notification (possibly including flexibility of the indicated transmission direction). Such a pattern may start at the beginning of the first time interval and repeat after the end of the last time interval (the last if the time intervals are ordered in time). In other words, the multiple time intervals may correspond to divisions of the (repeating) period of each slot format (e.g., the first and / or second slot format) into time intervals. In this manner, the period covered by the time intervals may be the (repeating) period of the pattern. In this regard, it should be noted that, in general, the first and second slot formats may have the same or different repeating periods. In this case, the multiple time intervals are (i) sub-intervals of the repeating period of the first slot format, (ii) sub-intervals of the repeating period of the second slot format, and / or, for example, (iii) sub-intervals of the common repeating period of the first slot format and the second slot format (e.g., if the first slot format has a repeating period of 5 slots and the second slot format has a repeating period of 10 slots, the common repeating period is 10 slots, 20 slots, etc.).

[0131] In general, the (repeating) period of a slot format refers to the length of time following which the pattern of transmission directions defined by the slot format is repeated. More specifically, after the last time interval (of multiple time intervals), there may be a time interval having the same length and transmission direction as the first time interval beginning with the end of the last time interval, followed by a time interval having the same length and transmission direction as the first time interval and any subsequent time intervals. For example, if the pattern of Figure 8 (DDDFU) has a repeating period of 5 slots, then slots 6 through 20 would be DDDFUDDDFUDDDFU.

[0132] <Slot format - transmission direction> Generally, from the perspective of a UE operating in half-duplex mode in a frequency band whose slot format indicates the transmission direction, in each time interval, all resources of the frequency band are indicated as having the same transmission direction (UL / DL) or as all having flexible transmission directions. In the latter case, the UE may expect further signaling specifying the transmission direction. This can be done by further specifying the slot format semi-statically via dedicated RRC, dynamically via DCI, or explicitly in a grant (e.g., scheduling DCI) that allocates resources for a specific transmission. Note that the above applies to resources assigned to this UE. Other UEs may not operate in half-duplex mode in the frequency band, may use different slot formats, and / or may have different transmission directions associated with specific resources. If these resources are assigned to other UEs, the other UEs may have transmission directions associated with these resources when using these resources.

[0133] In particular, if the transmission direction for a particular time interval is indicated as being downlink, the UE may only expect to receive transmissions (especially transmissions from the base station for which it received the slot format). In particular, each resource grant for a time interval is / is expected to be a DL grant. Thus, the UE may only expect to receive DL grants in such time intervals and interpret the grants accordingly. In particular, the base station may not need to indicate whether the resources it has granted / allocated to the UE in a time interval are DL or UL resources. Thus, the UE may assume that only DL grants are present in that interval and plan its behavior (e.g., buffering, sleep behavior, etc.) accordingly. Accordingly, the base station may allocate only resources for DL transmissions to the UE in a particular time interval.

[0134] If the transmission direction for a particular time interval is indicated as uplink, the UE may only expect to transmit (especially to the base station from which it received the slot format). In particular, each resource grant for a time interval is / is expected to be an UL grant. Therefore, the UE may only expect to receive UL grants in such time intervals and interpret the grants accordingly. In particular, the base station may not need to indicate whether the resources it has granted / allocated to the UE in a time interval are DL or UL resources. Therefore, the UE may assume that it only has an UL grant for that interval and plan its behavior (e.g., buffering, sleep behavior, etc.) accordingly. Accordingly, the base station may only allocate resources for UL transmissions to the UE in a particular time interval.

[0135] If the transmission direction for a particular time interval is indicated as flexible, the resources allocated in this time interval may be UL or DL resources and are indicated by further specification of the slot format or, for example, directly by the grant allocating resources in such time interval.

[0136] <First signaling and first slot format> In general, the first signaling may be cell-common signaling indicating the first slot format (or including a notification indicating the first slot format). In other words, the first slot format is a cell-common slot format. For example, the first slot format may be a slot format made known to all / each UE in a cell and / or all / each UE served by a base station, for example, by a broadcast (e.g., SIB1). For example, the first slot format may be a legacy format (e.g., first signaling that all legacy UEs are expected to follow or use in Rel-15 / 16 / 17, and / or the first signaling is signaling recognized by legacy UEs (the second signaling may not be recognized by legacy UEs, as further described below).

[0137] However, it should be noted that the cell-common first signaling may be transmitted to different UEs in different ways (e.g., dedicated group RRC for different UE groups) and at different times and may not be broadcast. In other words, the base station may generate the first signaling as cell-common signaling, meaning that the carried control information / signaling (i.e., the first slot format) is common / applies to all UEs in the cell. In other words, cell-common signaling does not necessarily mean that the transmission of this particular first signaling is broadcast and / or received by each UE in the cell (some UEs may receive the cell-common signaling in different transmissions).

[0138] <Second signaling> Generally, the signaling indicating the second slot format to the UE is referred to as second signaling. Thus, generally, the second signaling may indicate whether the transmission direction is (i) flexible, (ii) uplink direction, or (iii) downlink direction for each of a plurality of time intervals, or for a subset of a plurality of time intervals.

[0139] In general, the second signaling may be cell-common signaling or dedicated signaling. In this regard, it should be noted that these possibilities are not mutually exclusive. That is, both cell-common and dedicated second signaling may be supported (simultaneously by the same UE or base station). In other words, certain second signaling may be cell-common or dedicated, but generally, some second signaling may be cell-common and some other second signaling may be dedicated. Thus, UEs and base stations may generally be configured to support cell-common and / or dedicated second signaling (e.g., receive such signaling and derive the second slot format therefrom).

[0140] Therefore, the base station may determine, based on current conditions (e.g., traffic load, UE QOS requirements, SR), whether the second slot format should be used (i) by each (non-legacy) UE, (ii) by only some UEs (e.g., a group), or (iii) by only one specific UE. In this regard, options (ii) and (iii) may include determining which UEs will use the second slot format. Generally, these determinations may be made in conjunction with determining the second slot format. The base station may generate and transmit corresponding second signaling or corresponding second signaling to associated UEs.

[0141] Dedicated second signaling allows the base station to configure an individual slot format for each UE, which may increase the flexibility of the base station and improve the efficiency of resource usage in the communication system. Cell-common second signaling reduces signaling overhead and may be more suitable when served UEs have similar requirements, e.g., regarding the current ratio of UL to DL traffic.

[0142] In general, the present disclosure is not limited to any particular type of second signaling, details and examples of which are further described below.

[0143] <Second signaling - cell-wide signaling> As mentioned above, the second signaling can be cell-common signaling. In particular, the new / second slot format can be semi-static and / or configured in a cell-common manner. For example, a new parameter, denoted herein as "tdd-UL-DL-ConfigurationCommon-r18," can be used. In general, the new parameter tdd-UL-DL-ConfigurationCommon-r18 can reuse the same structure as the existing "tdd-UL-DL-ConfigurationCommon" or can use a new structure.

[0144] Although this is cell-wide signaling, since it is a newly introduced parameter, it will be invisible to legacy UEs (e.g., Rel-15 / 16 / 17 UEs). This means that the slot configuration of legacy UEs will not be affected by this new cell-wide parameter. Therefore, for Rel-18 and later UEs, the UE capability to accept this new parameter can be introduced as an option. Rel-18 and later UEs that have this capability can use this new parameter (and the slot format indicated via this parameter), while non-capable Rel-18 and later UEs can ignore such parameters.

[0145] For example, as a first example, the following syntax may be used: [Table 2]

[0146] In this example, "slotIndex" is used to identify a slot within the slot configuration period given in the legacy tdd-UL-DL-ConfigurationCommon. This period may be the repetition period of the pattern of the second slot format. Note that the first and second slot formats may generally have the same repetition period. In this case, the period of the second slot format may not need to be indicated to the UE (e.g., if the UE is aware of this, e.g., if it is predefined or preconfigured).

[0147] Furthermore, "symbols" is used to set the direction of the symbols in this slot (the slot identified by "slotIndex"). In particular, (i) the value "allDownlink" indicates that all symbols in this slot are used for the downlink, (ii) the value "allUplink" indicates that all symbols in this slot are used for the uplink, (iii) the value "allFlexible" indicates that all symbols in this slot are flexible, and (iv) the value "explicit" explicitly indicates how many symbols are allocated to the downlink and uplink at the beginning and end of this slot, respectively.

[0148] In other words, the second signaling may indicate a sequence of slot indexes (or time interval indexes) and a sequence of slot configurations. Elements of these two sequences may be associated with each other in a one-to-one correspondence. In particular, a slot index may be followed by an associated slot configuration. The transmission directions of slots not included in the indicated sequence of slot indexes may be the respective transmission directions indicated by the first slot format for these slots. In other words, the sequence of slot indexes indicates slots for which the transmission direction of the second slot format differs (at least for some symbols) from the transmission direction of the first slot format.

[0149] Furthermore, the slot configuration for a slot may be indicated by (i) indicating that all symbols in the associated slot are UL symbols, (ii) indicating that all symbols in the associated slot are DL symbols, (iii) indicating that all symbols in the associated slot are flexible symbols, (iv) or by explicitly indicating the number of UL symbols and the number of DL symbols. In (iv), DL symbols may be assumed at the beginning of the slot, UL symbols at the end, and the remaining symbols may be assumed to be intermediate flexible symbols. For example, if a slot has a total of X symbols, the number of DL symbols is m, and the number of UL symbols is n, the first m symbols may be DL symbols, followed by Xmn flexible symbols, and n UL symbols at the end of the slot. However, the present disclosure is not limited in this respect. For example, whether the first symbol is a UL symbol or a DL symbol may depend on the transmission direction in the slot preceding the currently considered slot, to which the explicit configuration applies.

[0150] As a second example, the following syntax may be used: [Table 3]

[0151] As in the above example, slotIndex is used to identify a slot within a given slot configuration period in the legacy tdd-UL-DL-ConfigurationCommon. Furthermore, the position of the UL symbol of the slot is indicated by a bitmap. In other words, this example differs from the above examples in the notification of slot configuration. In particular, as in the above example, by using a bitmap, the position of the uplink symbol is not limited to the end of the slot, as in the first example. Furthermore, the transmission direction in a slot that is not part of the indicated sequence of slot indexes may be the respective transmission direction indicated by the first slot format. Furthermore, the transmission direction of a symbol indicated as the uplink direction may be the respective transmission direction indicated by the first slot format. For such symbols, the first slot format may indicate that the transmission direction is typically the DL direction or flexible.

[0152] <Second signaling - dedicated RRC> As mentioned above, the second signaling may be dedicated signaling, e.g., dedicated Radio Resource Control (RRC) signaling. In particular, the new second slot format may be semi-static and / or configured in a UE-specific manner. For example, existing parameters (legacy configurations) such as the existing Rel-15 / 16 / 17 NR parameter "tdd-UL-DL-ConfigurationDedicated" may be reused. Alternatively or additionally, a new parameter, denoted herein as "tdd-UL-DL-ConfigurationDedicated-r18," may be introduced. Providing dedicated second signaling may provide flexibility for the gNB in selecting which UEs to configure, as well as the flexibility to configure different non-legacy UEs with different slot formats than other non-legacy UEs.

[0153] The new parameter "tdd-UL-DL-ConfigurationDedicated-r18" can reuse the same structure as the existing tdd-UL-DL-ConfigurationDedicated, or can adopt a new structure. If a new structure is used (i.e., a structure different from the structure used for the first signaling, e.g., as in Rel-15 / 16 / 17 NR), the new parameter may include one or more of the following elements: - U time intervals within a slot period (e.g., which symbols and / or slots) (especially if the second slot format has a "D→U" setting with respect to the first slot format) - F time intervals within a slot period (e.g., which symbols and / or slots) (especially if the second slot format has a "D→F" setting and / or a "U→F" setting with respect to the first slot format), and / or - D time intervals within a slot period (e.g., which symbols and / or slots) (especially if the second slot format has a "U→D" setting and / or a "U→F" setting relative to the first slot format).

[0154] The "certain period" may be, for example, the recurrence period of the second slot format. In other words, the positions of each "D→U," "D→F," "U→D," and "U→F" time interval may be indicated. The transmission direction of these time intervals (whose positions are included / indicated by the second signaling) may be indicated, in particular, when (i) both "D→U" and "D→F" are permitted and / or (ii) both "U→D" and "U→F" are permitted. That is, for each of these time intervals that are D time intervals in the first slot format, it may be indicated whether they are U time intervals or F time intervals in the second slot format, and for each of these time intervals that are U time intervals in the first slot format, it may be indicated whether they are D time intervals or F time intervals in the second slot format.

[0155] <Second Signaling - Dynamic DCI> It should also be noted that the present disclosure is not limited to a semi-static second slot format as in the above two examples of cell-wide and RRC-specific signaling. For example, instead of configuring a semi-static symbol / slot with a transmission direction different from the transmission direction indicated by the first slot format for that symbol / slot as described in the above two examples, a special DCI (e.g., a new DCI) may be used to dynamically schedule a transmission with a different transmission direction. For example, in a semi-static DL symbol, such a DCI may schedule an UL transmission to a UE.

[0156] <Second slot format> In general, the second slot format (i) defines a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format defines the transmission direction to be an uplink direction, and / or (ii) defines a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format defines the transmission direction to be a downlink direction. In other words, the second format changes the transmission direction for time intervals that are not flexible time intervals of the first slot format.

[0157] For example, a Rel-18 (and later) UE may be configured with a new semi-static slot format in which a different direction is indicated for a slot or symbol than that configured by the legacy cell-common semi-static slot format (i.e., tdd-UL-DL-ConfigurationCommon). Thus, in general, the second slot format may be semi-static according to this disclosure, although as noted above, this disclosure is not limited in this respect.

[0158] In general, a (non-legacy) UE may be configured to determine that the transmission direction indicated by the second slot format applies (ignoring the transmission direction indicated by the first slot format) in each time interval (a subset of time intervals in which the transmission direction is (explicitly) specified by the second slot format). The base station may be configured to schedule only the transmission direction according to the transmission direction indicated to the UE by the second slot format. For example, in each time interval in which (i) the first slot format specifies that the transmission direction is the downlink direction and (ii) the second slot format specifies that the transmission direction is the uplink direction, the transmission direction may be the uplink direction (particularly, the UE may determine that the transmission direction is the uplink direction). Note that if both slot formats indicate the uplink direction, the UE may determine that the transmission direction is the uplink direction. The above condition (i) is included primarily to emphasize that the two slot formats indicate opposite directions for a particular time interval.

[0159] This is shown in FIG. 13, where the UE receives a legacy cell common slot configuration (corresponding to a first slot format) in step S1320, and then receives another slot format (corresponding to a second slot format) through a new cell common parameter or dedicated RRC configuration that configures all or some of the symbols / slots (corresponding to time intervals) configured by the legacy cell common configuration in step S1340. The UE may then determine (S1360) whether the second slot format indicates a different transmission direction from the first slot format in any time interval in which the first slot format indicates the uplink direction or the downlink direction (i.e., whether the second slot format indicates a different transmission direction from the first slot format in a time interval in which the first slot does not indicate that the transmission direction is flexible). Note that step S1360 may be omitted in the example of FIG. 13. The UE then determines in step S1380 that the second slot format is to be applied. More specifically, in each time interval, the UE may determine that the transmission direction in that time interval is the transmission direction indicated by the second slot format.

[0160] However, the present disclosure is not limited in this regard. For example, as shown in FIG. 14, a (non-legacy) UE may generally be configured to determine, in each time interval, whether the second slot format indicates a different transmission direction than the first slot format in any time interval in which the first slot format indicates an uplink (U) or downlink (D) direction. In other words, the UE may determine whether there are time intervals in which the first slot format does not indicate that the transmission direction is flexible (i.e., indicates U or D) and the second slot format indicates either U or D. In particular, the UE may determine time intervals in which the transmission direction indicated by the first slot format is not flexible and the second slot format indicates a different transmission direction. This step S1460 and receiving steps S1420 and S1440 may be identical to steps S1360, S1320, and S1340 already described with respect to FIG. 13.

[0161] The UE may determine that the transmission direction in the time intervals determined in step S1460 is undetermined by the slot format and reuse legacy rules for handling quasi-static F symbols. For example, in each of multiple time intervals in which a first slot format specifies that the transmission direction is the downlink direction and a second slot format specifies that the transmission direction is the uplink direction, the transmission direction may be flexible. In other words, the UE may determine (S1480) that the transmission direction in the time intervals determined in step S1460 is flexible, or at least can be considered flexible. Therefore, the gNB may configure the UE to either receive or transmit (not simultaneously) in these symbols / slots, or may indicate the transmission direction in a grant allocating resources for transmission.

[0162] Providing the second slot format can enhance UL coverage, which can be an issue in legacy (Rel-15 / 16 / 17) NR configurations. For example, the total number (or, e.g., total number, amount, or count) of time intervals in which the second slot format specifies the transmission direction as the uplink direction may be greater than the total number (or, e.g., total number, amount, or count) of time intervals in which the first slot format specifies the transmission direction as the uplink direction. Here, the two total numbers of the first and second slot formats are total numbers for the same time length (e.g., the total number in a common repeating period of the two slot formats). In other words, the number of UL slots / symbols in the new semi-static slot format can be greater than the number of UL slots / symbols in the conventional slot format, thereby improving UL coverage. Alternatively, or in addition, the sum of the total number of flexible time intervals of the second slot format and the total number of UL time intervals of the second slot format may be greater than the sum of the total number of flexible time intervals of the first slot format and the total number of UL time intervals of the first slot format.

[0163] Furthermore, provision of the second slot format can avoid configuration changes of the slot format in legacy deployments. It can also enable SBFD operation, for example, by using different transmission directions between legacy UEs and Rel-18 and later UEs, as described with reference to the gNB flowchart shown in Figure 15. In the example of Figure 15, the gNB transmits a legacy cell common slot configuration (configuration corresponding to the first signaling indicating the first slot format) at S1520.

[0164] Next, the gNB performs S1540 to determine or decide in which symbol to operate SBFD. In other words, the base station has determined a time interval suitable for transmitting (simultaneously) to some UEs and receiving from other UEs. For example, the gNB may determine that for a legacy D symbol, the first UE (UE1) performs reception and the second UE (UE2) performs transmission. In other words, the gNB determines that the time interval corresponding to the above D symbol is used for SBFD, and the transmission direction in the above time interval is DL for the first UE and UL for the second UE. In step S1560, the gNB thus transmits to UE2 a dedicated slot setting (corresponding to the second signaling) for setting U for the above legacy D symbol (that is, s becomes a D→U symbol from the perspective of UE2). In other words, the gNB transmits to UE2 a second signaling including a notification indicating a second slot format indicating that the transmission direction in the time interval corresponding to the above legacy D symbol is the UL direction. In step S1580, the gNB starts / executes DL transmission to UE1 and UL reception from UE2 in the above symbol (for example, simultaneously).

[0165] <Permission for D→U setting> Generally, the second slot format may define that the transmission direction is the uplink direction in a time interval (for example, one or more / at least one / some time intervals) in which the first slot format defines that the transmission direction is the downlink direction.

[0166] Note that currently, for the sake of convenience of explanation, this situation is denoted as "D→U". Furthermore, generally, when the first slot format indicates X (X is U / D / F) and the second slot format indicates Y (Y is U / D / F and is usually different from X), it is denoted as "X→Y". It should be noted that this is not intended to indicate that the first slot format is changed (especially changed for legacy UEs) or that the second signaling indicates a difference regarding the first slot format.

[0167] For example, "D" in tdd-UL-DL-ConfigurationCommon (corresponding to the first signaling) may be configured as "U" by the second slot format. The UE may perform UL transmission in the "D→U" time interval (i.e., the UE follows the "new" configuration "U" and ignores the legacy configuration "D" indicated by the first slot format), and the gNB may not configure DL reception in these symbols / slots, as described with reference to FIG. 13. Alternatively, the gNB may configure the UE so that the UE and the base station receive or transmit (but not simultaneously) for these symbols / slots, following the approach described with reference to FIG. 14.

[0168] An example of "D→U" is shown in Fig. 16. The first and second slot formats are assumed to be indicated by two parameters, tdd-UL-DL-ConfigurationCommon (specified in Rel-15 / 16 / 17 NR for example) and tdd-UL-DL-ConfigurationCommon-r18, respectively, as explained in one of the above examples. Both parameters are assumed to be notified by the SIB, and an exemplary slot format with a 5-slot period is set. In other words, both slot formats have a repeating period of 5 slots. Rel-15 / 16 / 17 UEs recognize tdd-UL-DL-ConfigurationCommon (only) and obtain the slot format as "DDDDU". UEs after Rel-18 can recognize both parameters and obtain a different slot format "DUUUU" from tdd-UL-DL-ConfigurationCommon-r18. As a result, the SBFD operation in the gNB becomes possible by simultaneously performing DL transmission and UL reception in the "D→U" symbols (i.e., the symbols included in slots n+1, n+2, and n+3). More specifically, at the time of these "D→U" symbols, legacy UEs can receive transmissions from the base station, and non-legacy UEs can transmit data to the base station.

[0169] The second slot format of the "D→U" setting enables the SBFD operation in the base station using the time interval indicating that the first slot format such as the legacy (Rel-15 / 16 / 17 NR) D symbol / slot has a downlink transmission direction.

[0170] <Permission for D→F setting> Generally, the second slot format may define that the transmission direction is flexible in the time interval (e.g., one or more time intervals / at least one time interval / some time intervals) that defines that the first slot format has a downlink transmission direction.

[0171] For example, in tdd-UL-DL-ConfigurationCommon (corresponding to the first signaling), "D" can be set as "F" by the second slot format. The UE may assume that the transmission direction for such a time interval is undetermined by the slot format. Therefore, the gNB can set either reception or transmission (but not both simultaneously) for the UE in these "D→F" symbols / slots.

[0172] This example is shown in FIG. 17. FIG. 17 is the same as the "D→U" case in FIG. 16, and the only difference is that DFFFU is set by tdd-UL-DL-ConfigurationCommon-r18 (i.e., the second slot format). This enables the SBFD operation in the gNB by simultaneously transmitting (DL) and receiving (UL) via the "D→U" symbols and "D→F" symbols. <D→UおよびD→F設定の複合ケース>

[0173]

[0174] <Compound case of D→U and D→F settings> Generally, the second slot format may define that (i) for some (e.g., one or more) time intervals where the first slot format defines the transmission direction as the downlink direction, the transmission direction is the uplink direction, and (ii) for some other (e.g., one or more) time intervals where the first slot format defines the transmission direction as the downlink direction, the transmission direction is flexible. Note that the "some time intervals" in (ii) are different time intervals from those in (i).

[0175] The UE's determination of whether the second slot format indicates flexible transmission direction may be based on whether the UE is configured to monitor a DCI format (e.g., group-common and / or dynamic control signaling, DCI format 2_0) in which dynamic configuration of flexible time intervals is transmitted by the base station. More specifically, such dynamic configuration may signal the UE the dynamic configuration of flexible time intervals of the first and / or second slot formats. In particular, the dynamic configuration may specify whether the transmission direction in the flexible time intervals (i.e., the time intervals in which the slot format indicates flexible transmission) is the downlink direction or the uplink direction. It should also be noted that such dynamic configuration may be transmitted in the form of a notification (also referred to herein as a dynamic slot format indicator (SFI)) included in the aforementioned DCI for receiving the dynamic configuration of flexible time intervals. For example, the slot format indicator may include an index value (e.g., in the form of a table) associated with the slot format.

[0176] In particular, the UE may (i) determine that the second signaling cannot specify that the transmission direction is flexible for any time interval for which the first slot format specifies that the transmission direction is downlink if the UE is not configured to receive a dynamic setting of flexible time intervals (e.g., SFI) (e.g., via DCI format 2_0), and (ii) determine that the second signaling can specify that the transmission direction is flexible for any time interval for which the first slot format specifies that the transmission direction is downlink if the UE is configured to receive SFI.

[0177] In other words, if the UE is not configured (e.g., not configured by the base station) to receive an SFI indicating whether the flexible transmission direction is DL or UL, the second slot format does not indicate a flexible transmission direction, thereby reducing overhead in situations where such a dynamic slot format indicator is not configured for the UE if flexible time intervals are not specifically required for the UE.

[0178] Examples of when a UE is not configured to monitor dynamic SFI include when an sfi-RNTI (Radio Network Temporary Identifier) value is not provided to the UE, when a control resource set for DCI format 2_0 is not provided to the UE, or when, for example, an RRC IE SlotFormatIndicator is not provided to the UE.

[0179] For example, for a UE that is not configured to monitor DCI2_0, the "D" in tdd-UL-DL-ConfigurationCommon can be configured as "U" or "D" (but not "F") according to the second slot format. On the other hand, for a UE that is configured to monitor DCI2_0, the "D" in tdd-UL-DL-ConfigurationCommon can be configured as "F" according to the second slot format. For example, the SFI in DCI2_0 can be used to indicate the dynamic transmission direction of the flexible time intervals of the first and second slot formats.

[0180] An example of this is shown in FIG. 18. The Rel-15 / 16 / 17 UEs recognize the tdd-UL-DL-ConfigurationCommon transmitted by the base station in SIB1 and obtain the first slot format as "DDDDU" as shown in the first row of FIG. 18. As shown in the second row, for one UE after Rel-18, it does not monitor DCI2_0, and the second slot format "DUUUU" is set by the dedicated RRC tdd-UL-DL-ConfigurationDedicated. Other UEs after Rel-18 that monitor DCI2_0 (the third row in FIG. 18) are set to the second slot format "DDFFU" by the dedicated RRC tdd-UL-DL-ConfigurationDedicated. Thus, the SBFD operation in the gNB is possible by transmitting DL via the "D→F" or "D→U" symbol / slot and receiving UL simultaneously.

[0181] The second slot format with the "D→U" and / or "D→F" setting can thus enable the SBFD operation at the base station by using a time interval such as the legacy (Rel-15 / 16 / 17 NR) D symbol / slot where the first slot format indicates that the transmission direction is the downlink direction.

[0182] <Permit U→D setting> Generally, the second slot format may define that the transmission direction is the downlink direction in a time interval (e.g., one or more time intervals / at least one time interval / some time intervals) where the first slot format defines that the transmission direction is the uplink direction. For example, "U" in tdd-UL-DL-ConfigurationCommon (corresponding to the first signaling) can be set as "D" by the second slot format.

[0183] The UE may assume DL transmission in the "U→D" time interval (i.e., the UE may follow the new configuration "D" and ignore the legacy configuration "U" indicated by the first slot format), and the gNB may not configure UL reception in these symbols / slots as described with reference to Figure 13. Specifically, the transmission direction may be the downlink direction in each time interval where the first slot format specifies that the transmission direction is the uplink direction and the second slot format specifies that the transmission direction is the downlink direction.

[0184] Alternatively, the gNB may configure the UE so that the UE and the base station receive or transmit (but not simultaneously) these symbols / slots according to the approach described with reference to Figure 14. Specifically, the transmission direction may be flexible in each of a plurality of time intervals in which the first slot format specifies the transmission direction as the uplink direction and the second slot format specifies the transmission direction as the downlink direction.

[0185] The example of FIG. 19 shows a combination of the above "D→U" setting (i.e., the (n + 1)-th slot and the (n + 2)-th slot) and the current "U→D" setting (the (n + 3)-th slot). As shown in FIGS. 16 and 17, both parameters of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationCommon-r18 are notified by the SIB and set the first slot format having a period of 5 slots. Rel-15 / 16 / 17 UEs recognize only tdd-UL-DL-ConfigurationCommon (corresponding to the first signaling) and obtain the slot format DDDUU as shown in the first row of FIG. 19. UEs after Rel-18 recognize both parameters and may obtain a different slot format such as DUUDU from tdd-UL-DL-ConfigurationCommon-r18, for example. Thereby, the SBFD operation in the gNB becomes possible by simultaneously performing DL transmission and UL reception via the "D→U" and "U→D" symbols / slots. In particular, the second slot format of the "U→D" setting enables the SBFD operation in a base station using a time interval (such as one or more time intervals / at least one time interval / some time intervals) in which the first slot format indicates that the transmission direction is the uplink direction, such as a legacy (Rel-15 / 16 / 17 NR) D symbol / slot.

[0186] <Permission for U→F setting> Generally, the second slot format may define that the transmission direction is flexible in a time interval (e.g., one or more time intervals / at least one time interval / some time intervals) that defines that the transmission direction of the first slot format is the uplink direction.

[0187] For example, in tdd-UL-DL-ConfigurationCommon (corresponding to the first signaling), "U" can be set as "F" by the second slot format. The UE may assume that the transmission direction for such a time interval is undetermined by the slot format. Therefore, the gNB can set either reception or transmission (but not both simultaneously) for the UE in these "U→F" symbols / slots.

[0188] This example is shown in FIG. 20. It is similar to the "U→D" case in FIG. 19, but the only difference is that DUUFU is set by tdd-UL-DL-ConfigurationCommon-r18 (i.e., the second slot format). This enables the SBFD operation in the gNB by simultaneously transmitting (DL) and receiving (UL) via the "D→U" symbols and "U→F" symbols.

[0189] More specifically, at the time of the "D→U" symbols and "U→F" symbols (i.e., the time of the symbols in the second slot, the (n + 2)-th slot, or the (n + 3)-th slot), the legacy UE may transmit to the base station, and the non-legacy UE may receive data from the base station. In particular, the second slot format with the "U→F" setting can enable the SBFD operation in the base station by using the time intervals indicated by the first slot format such as legacy (Rel-15 / 16 / 17 NR) D symbols / slots where the transmission direction is the uplink direction.

[0190] <Composite Case of U→D and U→F Settings> In general, the second slot format may (i) specify that the transmission direction is the downlink direction for some (e.g., one or more) time intervals for which the first slot format specifies that the transmission direction is the uplink direction, and (ii) specify that the transmission direction is flexible for some (e.g., one or more) other time intervals for which the first slot format specifies that the transmission direction is the uplink direction, where the "some time intervals" in (ii) are different from the "some time intervals" in (i).

[0191] Similar to the case of the D-→U and D-→F combinations, the UE's determination of whether the second slot format indicates flexible transmission direction may be based on whether the UE is configured to monitor a DCI format (e.g., group-common and / or dynamic control signaling (e.g., DCI format 2_0)). Dynamic configuration of the flexible time intervals is transmitted by the base station (e.g., in the form of a dynamic slot format indicator (SFI) as already described for the case of the D-→U and D-→F configuration combinations). Details regarding dynamic configuration and SFI have already been described in the description of the case of the D-→U and D-→F configuration combinations and will not be repeated here.

[0192] In general, the UE may determine that (i) if the UE (i.e., the UE itself) is not configured to receive dynamic configuration (e.g., SFI) of flexible time intervals (e.g., via DCI format 2_0), the second signaling cannot specify that the transmission direction is flexible for any time interval for which the first slot format specifies that the transmission direction is an uplink direction, and (ii) if the UE is configured to receive SFI, the second signaling can specify that the transmission direction is flexible for any time interval for which the first slot format specifies that the transmission direction is an uplink direction.

[0193] In other words, if the UE is not configured (e.g., not configured by the base station) to receive an SFI indicating whether the flexible transmission direction is DL or UL, the second slot format does not indicate a flexible transmission direction, thereby reducing overhead in situations where such a dynamic slot format indicator is not configured for the UE if flexible time intervals are not specifically required for the UE.

[0194] Examples of when a UE is not configured to monitor dynamic SFI include when an sfi-RNTI (Radio Network Temporary Identifier) value is not provided to the UE, when a control resource set for DCI format 2_0 is not provided to the UE, or when, for example, an RRC IE SlotFormatIndicator is not provided to the UE.

[0195] For example, a UE that is not configured to monitor DCI2_0 can configure a "U" in tdd-UL-DL-ConfigurationCommon as "D" or "U" (but not "F") according to the second slot format. On the other hand, a UE that is configured to monitor DCI2_0 can configure a "U" in tdd-UL-DL-ConfigurationCommon as "F" according to the second slot format. As mentioned above, for example, the SFI in DCI2_0 can be used to indicate the dynamic transmission direction of the flexible time intervals of the first and second slot formats.

[0196] An example of this is shown in Figure 21. A Rel-15 / 16 / 17 UE recognizes the tdd-UL-DL-ConfigurationCommon sent in the SIB by the base station and obtains the first slot format as DDDUU, as shown in the first row of Figure 21. As shown in the second row, one Rel-18 or later UE does not monitor DCI2_0 and is configured with the second slot format "DUUDU" by the dedicated RRC tdd-UL-DL-ConfigurationDedicated. Also, a Rel-18 or later UE that monitors DCI2_0 (third row of Figure 21) has the second slot format configured as "DFFFU" by the dedicated RRC tdd-UL-DL-ConfigurationDedicated. Therefore, SBFD operation in a gNB is possible by simultaneously transmitting (DL) and receiving (UL) in "D→F" (n+1st and n+2nd slots), "D→U" (n+1st and n+2nd slots), "U→D" (n+3rd slot), and / or "U→F" symbols / slots (n+3rd slot).

[0197] The second slot format having a "U→D" and / or "U→F" configuration may therefore enable SBFD operation at the base station using time intervals where the first slot format indicates the transmission direction is the uplink direction, such as legacy (Rel-15 / 16 / 17NR) U symbols / slots.

[0198] The above-mentioned slot configurations "D→U", "D→F", "U→D", and "U→F" can be combined. In other words, the second slot format may have a "D→U" slot, a "D→F" slot, a "U→D" slot, and / or a "U→F" slot relative to the first slot format (e.g., a cell-common legacy slot format).

[0199] Hardware and Software Implementations of the Disclosure The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block described in the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit. Each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data inputs and outputs. Depending on the level of integration, the LSI may be referred to as an IC, system LSI, super LSI, or ultra LSI. The integration method is not limited to LSIs; it may also be realized by dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays), which can be programmed after LSI fabrication, or reconfigurable processors, which allow the connections and settings of circuit cells within the LSI to be reconfigured, may also be used. The present disclosure may be realized as digital or analog processing. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology is also a possibility.

[0200] The present disclosure may be implemented in any type of apparatus, device, or system having a communication function (collectively referred to as a communication apparatus).

[0201] A communications device may include a transceiver (transmitter / receiver unit) and processing / control circuitry. The transceiver unit may include a receiver unit and a transmitter unit, or both. The transceiver unit (transmitter unit, receiver unit) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like.

[0202] Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0203] Communications equipment is not limited to portable or mobile equipment, but also includes non-portable or fixed equipment, devices, and systems of any kind, such as smart home devices (appliances, lighting equipment, smart meters or metering devices, control panels, etc.), vending machines, and any other "things" that may exist on an Internet of Things (IoT) network.

[0204] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

[0205] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0206] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0207] Furthermore, various embodiments may also be implemented by software modules. These software modules are executed by a processor or directly in hardware. A combination of software modules and hardware implementation is also possible. The software modules may be stored on any type of computer-readable storage medium. In particular, according to another implementation, a non-transitory computer-readable storage medium is provided. The storage medium stores a program that, when executed by one or more processors, causes the one or more processors to perform the steps of a method according to the present disclosure.

[0208] By way of non-limiting example, such computer-readable storage media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is referred to as a computer-readable medium, as appropriate. For example, if instructions are transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but instead cover non-transitory tangible storage media. As used herein, a disc includes a compact disc (CD), a laser disc, an optical disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, where a "disk" typically reproduces data magnetically, while a "disc" reproduces data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0209] Furthermore, it should be noted that individual features of different embodiments may be the subject of other embodiments, individually or in any combination. Those skilled in the art will appreciate that the present disclosure, as set forth in the specific embodiments, may be subject to various changes and / or modifications without departing from the concept or scope of the invention as broadly described. The embodiments described herein are therefore to be considered in all respects as illustrative and not restrictive.

[0210] Further Aspects According to a first aspect, a communications device is provided. The communications device includes a transceiver unit and circuitry. The transceiver unit, in operation, receives first signaling and second signaling, the first signaling being cell-common signaling. The circuitry, in operation, obtains from the first signaling a first notification indicating a first slot format for a frequency band and obtains from the second signaling a second notification indicating a second slot format for the frequency band. The first slot format specifies, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction, and the second slot format specifies, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether the transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. In particular, the second slot format (i) specifies a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as a downlink direction, and / or (ii) specifies a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction.

[0211] According to a second aspect provided in addition to the first aspect, the second slot format specifies that the transmission direction is an uplink direction for time intervals among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction.

[0212] According to a third aspect provided in addition to the second aspect, in operation, the circuit determines that the transmission direction is an uplink direction in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is a downlink direction and (ii) the second slot format specifies that the transmission direction is an uplink direction.

[0213] According to a fourth aspect provided in addition to the second aspect, in operation, the circuit determines that the transmission direction is flexible in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is a downlink direction and (ii) the second slot format specifies that the transmission direction is an uplink direction.

[0214] According to a fifth aspect provided in addition to any one of the first to fourth aspects, the total number of time intervals in which the first slot format specifies that the transmission direction is an uplink direction is greater than the total number of time intervals in which the second slot format specifies that the transmission direction is an uplink direction.

[0215] According to a sixth aspect provided in addition to any one of the first to fifth aspects, the second slot format specifies that the transmission direction is flexible for a time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction.

[0216] According to a seventh aspect, which is provided in addition to any one of the first to sixth aspects, the circuit, when operating, (i) determines that, when the communication device is not configured to monitor downlink control information (DCI) to receive dynamic setting of flexible time intervals, the second signaling cannot specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction, and (ii) when the communication device is configured to monitor the DCI to receive dynamic setting of flexible time intervals, the second signaling can specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction.

[0217] According to an eighth aspect provided in addition to the seventh aspect, (i) the second slot format specifies that the transmission direction is a downlink direction for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction, and / or (ii) the second slot format specifies that the transmission direction is flexible for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction.

[0218] According to a ninth aspect provided in addition to the eighth aspect, in operation, the circuit determines that the transmission direction is a downlink direction in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is an uplink direction and (ii) the second slot format specifies that the transmission direction is a downlink direction.

[0219] According to a tenth aspect provided in addition to the eighth aspect, in operation, the circuit determines that the transmission direction is flexible in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is an uplink direction and (ii) the second slot format specifies that the transmission direction is a downlink direction.

[0220] According to an eleventh aspect, which is provided in addition to any one of the first to tenth aspects, the circuit, when operating, (i) determines that, when the communication device is not configured to monitor downlink control information (DCI) to receive dynamic setting of flexible time intervals, the second signaling cannot specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies the transmission direction to be an uplink direction, and (ii) when the communication device is configured to monitor the DCI to receive dynamic setting of flexible time intervals, the second signaling can specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies the transmission direction to be an uplink direction.

[0221] According to a twelfth aspect, which is provided in addition to any one of the first to eleventh aspects, the second signaling is cell common signaling or dedicated signaling, and the cell common signaling or the dedicated signaling indicates, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether the transmission direction is flexible, an uplink direction, or a downlink direction, and the plurality of time intervals correspond to divided sections obtained by dividing a period of the second slot format into time intervals, and the period is a time length after which a pattern of transmission directions defined by the second slot format is repeated.

[0222] According to a thirteenth aspect, there is provided a method for a communications device, the method including: (i) receiving first signaling, the first signaling being cell common signaling; (ii) obtaining from the first signaling a first indication indicating a first slot format for a frequency band, the first slot format specifying, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; (iii) receiving second signaling; and (iv) obtaining from the second signaling a second indication indicating a second slot format for the frequency band, the second slot format specifying, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. In particular, the second slot format (i) specifies a different transmission direction from the first slot format for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as a downlink direction, and / or (ii) specifies a different transmission direction from the first slot format for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as an uplink direction.

[0223] According to a fourteenth aspect, there is provided a scheduling device comprising: a circuit and a transceiver unit. In operation, the circuit (i) determines, for each of a plurality of time intervals, a first slot format for a frequency band that specifies whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; (ii) generates first signaling, the first signaling being cell-common signaling, including a first notification indicating the first slot format; (iii) determines a second slot format for the frequency band; and (iv) generates second signaling indicating the second slot format. In operation, the transceiver unit transmits the first signaling and the second signaling, the second slot format specifying, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. In particular, the second slot format (i) specifies a different transmission direction from the first slot format for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as a downlink direction, and / or (ii) specifies a different transmission direction from the first slot format for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as an uplink direction.

[0224] According to a 15th aspect, which is provided in addition to the 14th aspect, the second slot format specifies that the transmission direction is an uplink direction for time intervals among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction.

[0225] According to a 16th aspect provided in addition to the 15th aspect, the transmission direction is an uplink direction in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is a downlink direction and (ii) the second slot format specifies that the transmission direction is an uplink direction.

[0226] According to a 17th aspect provided in addition to the 15th aspect, the transmission direction is flexible in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is a downlink direction and (ii) the second slot format specifies that the transmission direction is an uplink direction.

[0227] According to an 18th aspect, which is provided in addition to any one of the 14th to 17th aspects, the total number of time intervals in which the second slot format specifies that the transmission direction is an uplink direction is greater than the total number of time intervals in which the first slot format specifies that the transmission direction is an uplink direction.

[0228] According to a 19th aspect, which is provided in addition to any one of the 14th to 18th aspects, the second slot format specifies that the transmission direction is flexible for time intervals among the plurality of time intervals in which the first slot format specifies that the transmission direction is a downlink direction.

[0229] According to a twentieth aspect, which is provided in addition to any one of the fourteenth to eighteenth aspects, (i) if the communication device to which the second signaling is transmitted is not configured to monitor dedicated downlink control information (DCI) for receiving dynamic setting of flexible time intervals of a second slot format, the second signaling cannot specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction, and (ii) if the communication device is configured to monitor dedicated DCI for receiving dynamic setting of flexible time intervals, the second signaling can specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction.

[0230] According to a 21st aspect, provided in addition to the 20th aspect, (i) the second slot format specifies that the transmission direction is a downlink direction for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction, and / or (ii) the second slot format specifies that the transmission direction is flexible for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction.

[0231] According to a 22nd aspect provided in addition to the 21st aspect, the transmission direction is a downlink direction in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is an uplink direction, and (ii) the second slot format specifies that the transmission direction is a downlink direction.

[0232] According to a 23rd aspect provided in addition to the 21st aspect, the transmission direction is flexible in each time interval among the plurality of time intervals in which (i) the first slot format specifies that the transmission direction is an uplink direction, and (ii) the second slot format specifies that the transmission direction is a downlink direction.

[0233] According to a 24th aspect, which is provided in addition to any one of the 14th to 23rd aspects, (i) if the communication device to which the second signaling is transmitted is not configured to monitor dedicated downlink control information (DCI) for receiving dynamic setting of flexible time intervals of a second slot format, the second signaling cannot specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is an uplink direction, and (ii) if the communication device is configured to monitor the dedicated DCI for receiving dynamic setting of the flexible time intervals, the second signaling can specify that the transmission direction is flexible for any time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is an uplink direction.

[0234] According to a 25th aspect, which is provided in addition to any one of the 14th to 24th aspects, the second signaling is cell common signaling or dedicated signaling, and the cell common signaling or the dedicated signaling indicates, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether the transmission direction is flexible, an uplink direction, or a downlink direction, and the plurality of time intervals correspond to divided sections obtained by dividing a period of the second slot format into time intervals, and the period is a time length after which a pattern of transmission directions defined by the second slot format is repeated.

[0235] According to a 26th aspect, there is provided a method for a scheduling device, the method including: (i) determining, for each of a plurality of time intervals, a first slot format for a frequency band that specifies whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction, (ii) generating first signaling, the first signaling being cell-common signaling, the first signaling including a first notification indicating the first slot format, (iii) transmitting the first signaling, (iv) determining a second slot format for the frequency band, (v) generating second signaling indicating the second slot format, and (vi) transmitting the second signaling, wherein the second slot format specifies, for each of the plurality of time intervals, or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. In particular, the second slot format (i) specifies a different transmission direction from the first slot format for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as a downlink direction, and / or (ii) specifies a different transmission direction from the first slot format for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as an uplink direction.

[0236] According to a twenty-seventh aspect, there is provided an integrated circuit which, in operation, controls processing of a communications device including the steps of the method of the thirteenth aspect.

[0237] According to a twenty-eighth aspect, there is provided an integrated circuit that, in operation, controls processing of a scheduling device including steps of the method of the twenty-sixth aspect.

[0238] In summary, the present disclosure relates to a communication device, a scheduling device, and respective methods for the communication device and the scheduling device. For example, the communication device is a user equipment (UE) including a circuit and a transceiver. The transceiver may be configured to receive first signaling and second signaling, where the first signaling is cell-common signaling. The circuit may be configured to obtain, from the first signaling, a first notification indicating a first slot format for a frequency band and to obtain, from the second signaling, a second notification indicating a second slot format for the frequency band. The first slot format specifies, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. The second slot format specifies, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction. Furthermore, the second slot format (i) specifies a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as a downlink direction, and / or (ii) specifies a different transmission direction than the first slot format for time intervals among the plurality of time intervals for which the first slot format specifies the transmission direction as an uplink direction.

Claims

1. a transceiver unit that, in operation, receives first signaling and second signaling, the first signaling being cell-common signaling; When in operation, obtaining a first indication from the first signaling, the first indication indicating a first slot format for a frequency band; obtaining from the second signaling a second indication indicating a second slot format for the frequency band; a circuit; the first slot format defines, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; the second slot format defines, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; The second slot format comprises: - defining a transmission direction different from the first slot format for a time interval in which the first slot format defines the transmission direction as a downlink direction among the plurality of time intervals; and / or specifying a transmission direction different from the first slot format for a time interval in which the first slot format specifies that the transmission direction is an uplink direction among the plurality of time intervals; Communication devices.

2. the second slot format specifies that the transmission direction is an uplink direction for a time interval among the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction; The communication device of claim 1 .

3. In operation, the circuitry detects: the first slot format defines the transmission direction as a downlink direction; the second slot format defines the transmission direction as an uplink direction; determining, in each time interval, that the transmission direction is an uplink direction; The communication device of claim 2 .

4. In operation, the circuitry detects: the first slot format defines the transmission direction as a downlink direction; the second slot format defines the transmission direction as an uplink direction; determining, at each time interval, that the transmission direction is flexible; The communication device of claim 2 .

5. a total number of time intervals in which the first slot format specifies that the transmission direction is an uplink direction is greater than a total number of time intervals in which the second slot format specifies that the transmission direction is an uplink direction; The communication device of claim 1 .

6. the second slot format specifies that the transmission direction is flexible for a time interval among the plurality of time intervals in which the first slot format specifies that the transmission direction is a downlink direction. The communication device of claim 1 .

7. The circuit, in operation, if the communications device is not configured to monitor Downlink Control Information (DCI) for receiving dynamic configuration of flexible time intervals, determining that the second signaling cannot specify that the transmission direction is flexible for any time interval of the plurality of time intervals for which the first slot format specifies the transmission direction to be a downlink direction; if the communications device is configured to monitor the DCI to receive dynamic configuration of the flexible time intervals, determining that the second signaling may specify that the transmission direction is flexible for time intervals of the plurality of time intervals for which the first slot format specifies that the transmission direction is a downlink direction; The communication device of claim 1 .

8. The second slot format specifies that the transmission direction is a downlink direction for a time interval among the plurality of time intervals in which the first slot format specifies the transmission direction as an uplink direction, and / or the second slot format specifies that the transmission direction is flexible for a time interval in which the first slot format specifies the transmission direction as an uplink direction among the plurality of time intervals. The communication device of claim 1 .

9. In operation, the circuitry detects: - the first slot format specifies that the transmission direction is an uplink direction; and the second slot format defines the transmission direction as a downlink direction; determining, at each time interval, that the transmission direction is a downlink direction; 9. The communication device of claim 8.

10. In operation, the circuitry detects: - the first slot format specifies that the transmission direction is an uplink direction; and the second slot format defines the transmission direction as a downlink direction; determining, at each time interval, that the transmission direction is flexible; 9. The communication device of claim 8.

11. The circuit, in operation, if the communications device is not configured to monitor downlink control information (DCI) for receiving dynamic configuration of flexible time intervals, determining that the second signaling cannot specify that the transmission direction is flexible for any time interval of the plurality of time intervals for which the first slot format specifies that the transmission direction is an uplink direction; if the communications device is configured to monitor the DCI to receive dynamic configuration of the flexible time intervals, determining that the second signaling may specify that the transmission direction is flexible for time intervals of the plurality of time intervals for which the first slot format specifies that the transmission direction is an uplink direction; The communication device of claim 1 .

12. the second signaling is cell-common signaling or dedicated signaling; the cell-common signaling or the dedicated signaling indicates, for each of the plurality of time intervals or a subset of the plurality of time intervals, whether the transmission direction is flexible, an uplink direction, or a downlink direction; the plurality of time intervals correspond to divided sections obtained by dividing a period of the second slot format into time intervals; the period is a time length following which a transmission direction pattern defined by the second slot format is repeated; The communication device of claim 1 .

13. receiving first signaling, the first signaling being cell common signaling; obtaining, from the first signaling, a first indication indicating a first slot format for a frequency band, the first slot format specifying, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; receiving second signaling; obtaining a second indication from the second signaling, the second indication indicating a second slot format for the frequency band; the second slot format defines, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; The second slot format comprises: - defining a transmission direction different from the first slot format for a time interval in which the first slot format defines the transmission direction as an uplink direction among the plurality of time intervals; and / or specifying a transmission direction different from the first slot format for a time interval in which the first slot format specifies that the transmission direction is a downlink direction among the plurality of time intervals; A method for a communication device.

14. When in operation, determining, for each of a plurality of time intervals, a first slot format for the frequency band that defines whether a transmission direction in said time interval is flexible, an uplink direction, or a downlink direction; generating first signaling, the first signaling being cell-common signaling, the first signaling including a first indication indicating the first slot format; determining a second slot format for said frequency band; generating second signaling indicating said second slot format; The circuit and a transceiver unit that, in operation, transmits the first signaling and the second signaling; the second slot format defines, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; The second slot format comprises: - defining a transmission direction different from the first slot format for a time interval in which the first slot format defines the transmission direction as an uplink direction among the plurality of time intervals; and / or specifying a transmission direction different from the first slot format for a time interval in which the first slot format specifies that the transmission direction is a downlink direction among the plurality of time intervals; Scheduling device.

15. determining, for each of a plurality of time intervals, a first slot format for the frequency band that defines whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; generating first signaling, the first signaling being cell common signaling, the first signaling including a first notification indicating the first slot format; transmitting the first signaling; determining a second slot format for the frequency band; generating second signaling indicating the second slot format; transmitting the second signaling; the second slot format defines, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; The second slot format comprises: - defining a transmission direction different from the first slot format for a time interval in which the first slot format defines the transmission direction as an uplink direction among the plurality of time intervals; and / or specifying a transmission direction different from the first slot format for a time interval in which the first slot format specifies that the transmission direction is a downlink direction among the plurality of time intervals; A method for a scheduling device.

16. 1. An integrated circuit that, in operation, controls the processing of a communications device, said processing comprising: receiving first signaling, the first signaling being cell common signaling; obtaining, from the first signaling, a first indication indicating a first slot format for a frequency band, the first slot format specifying, for each of a plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; receiving second signaling; obtaining a second indication from the second signaling, the second indication indicating a second slot format for the frequency band; the second slot format defines, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; The second slot format comprises: - defining a transmission direction different from the first slot format for a time interval in which the first slot format defines the transmission direction as an uplink direction among the plurality of time intervals; and / or specifying a transmission direction different from the first slot format for a time interval in which the first slot format specifies that the transmission direction is a downlink direction among the plurality of time intervals; Integrated circuit.

17. An integrated circuit that, in operation, controls the processing of a scheduling device, said processing comprising: determining, for each of a plurality of time intervals, a first slot format for the frequency band that defines whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; generating first signaling, the first signaling being cell common signaling, the first signaling including a first notification indicating the first slot format; transmitting the first signaling; determining a second slot format for the frequency band; generating second signaling indicating the second slot format; transmitting the second signaling; the second slot format defines, for each of the plurality of time intervals or for a subset of the plurality of time intervals, whether a transmission direction in the time interval is flexible, an uplink direction, or a downlink direction; The second slot format comprises: - defining a transmission direction different from the first slot format for a time interval in which the first slot format defines the transmission direction as an uplink direction among the plurality of time intervals; and / or specifying a transmission direction different from the first slot format for a time interval in which the first slot format specifies that the transmission direction is a downlink direction among the plurality of time intervals; Integrated circuit.

Images