User equipment and base station involving time division communication

Abstract

The present disclosure relates to a user equipment, UE, including the following. The receiver receives a plurality of time division configurations. The circuitry determines a communication direction for each of the plurality of time intervals based on a first set of one or more of the previously received plurality of time division configurations. A receiver receives information about a full duplex resource. A receiver receives a DCI message including a configuration switching indication indicating one of a plurality of previously received time division configurations to be used. The circuitry determines a communication direction for each of the one or more full duplex time intervals of the full duplex resource and correspondingly for a complete full duplex frequency region of the full duplex resource based on a second set of one or more of the previously received plurality of time division configurations. The second set of time division configurations includes at least the indicated time division configurations.

Description

Technical Field

[0001] The present disclosure is directed to methods, apparatus, and articles of manufacture in a communication system, such as a 3GPP communication system. Background Art

[0002] Currently, the 3rd Generation Partnership Project (3GPP) is working on the technical specifications of a new radio access technology - 5G NR (New Radio), which is also referred to as fifth generation (5G) or NR and is used interchangeably in this article.

[0003] One goal is to provide a single technical framework (see, e.g., Section 6 of 3GPP TR 38.913 (e.g., Release 16.0.0 or Release 17.0.0)) that addresses all use cases, requirements, and deployment scenarios, including at least enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). For example, eMBB deployment scenarios may include indoor hotspots, dense urban, rural, urban macro, and high-speed; URLLC deployment scenarios may include industrial control systems, mobile healthcare (remote monitoring, diagnosis, and treatment), real-time control of vehicles, wide-area monitoring and control systems for smart grids; mMTC deployment scenarios may include scenarios with a large number of devices with non-time-critical data transmissions, such as smart wearables and sensor networks. Services eMBB and URLLC are similar in that they both require very wide bandwidth, while they are different in that URLLC services may preferably require ultra-low latency.

[0004] A second objective is to achieve forward compatibility, which facilitates completely new system designs and / or the introduction of novel features. Summary of the invention

[0005] One non-limiting and exemplary embodiment facilitates providing a process for a UE to perform an improved time division communication process.

[0006] In an embodiment, the technology disclosed herein is characterized in that a user equipment (UE) includes the following. A receiver of the UE receives multiple time division configurations. The circuit of the UE determines the communication direction for each time interval in a plurality of time intervals based on a first set of one or more time division configurations in the plurality of time division configurations previously received. The receiver receives information about full-duplex resources. The receiver receives a downlink control information DCI message including a configuration switching indication. The configuration switching indication indicates one time division configuration to be used in the plurality of time division configurations previously received. The circuit determines the communication direction for each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and accordingly for a complete full-duplex frequency region of the full-duplex resource based on a second set of one or more time division configurations in the plurality of time division configurations previously received. The second set of time division configurations includes at least the indicated time division configuration.

[0007] It should be noted that the general or specific embodiments may be implemented as a system, method, integrated circuit, computer program, storage medium or any selective combination thereof. For example, an integrated circuit may control the processing of a UE or a base station.

[0008] Additional benefits and advantages of the disclosed embodiments and different implementations will be apparent from the description and drawings. Benefits and / or advantages can be obtained individually from the various embodiments and features of the description and drawings, and these embodiments and features do not need to be provided in full in order to obtain one or more such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Hereinafter, exemplary embodiments are described in more detail with reference to the accompanying drawings.

[0010] Figure 1 An exemplary architecture of a 3GPP NR system to which the improved procedures of the present disclosure may be applied is shown;

[0011] Figure 2 is a schematic diagram showing the functional division between NG-Radio Access Network (NG-RAN) and 5G Core Network (5GC), to which the improved process of the present disclosure can be applied,

[0012] Figure 3 is a sequence diagram of a radio resource control (RRC) connection establishment / reconfiguration procedure to which the improved procedure of the present disclosure may be applied,

[0013] Figure 4 is a schematic diagram showing usage scenarios of eMBB, mMTC and URLLC to which the improved process of the present disclosure can be applied,

[0014] Figure 5 is a block diagram illustrating an exemplary 3GPP NR system architecture for non-roaming scenarios,

[0015] Figure 6 The relationship between bandwidth parts, control resource sets (CORESET), search spaces, search space sets and PDCCH candidates is shown.

[0016] Figure 7 An exemplary time domain structure in a communication system such as 5G NR is shown, including radio frames, subframes, time slots, and OFDM symbols with different subcarrier spacings,

[0017] Figure 8 and Fig. 9 shows an exemplary configuration of the format of time slots and symbols and an exemplary communication direction therein,

[0018] Fig.10 The result of combining the cell common TDD configuration and the UE dedicated TDD configuration is shown.

[0019] Fig.11 The results of combining cell-common TDD configuration and DCI-based TDD configuration are shown.

[0020] Fig.12 shows half-duplex operation of the UE and sub-band full-duplex operation at the gNB,

[0021] Fig.13 shows variable and fixed frequency resources in different time periods of sub-band full-duplex resources,

[0022] Fig.14 shows the problematic collision of uplink and downlink resources of two different UEs in the same sub-band full-duplex resource,

[0023] Fig.15 shows an exemplary and simplified structure of a UE and a gNB,

[0024] Fig.16 shows the structure of a UE according to an exemplary embodiment of an improved time division communication process,

[0025] Fig.17 A flow chart showing UE behavior according to an exemplary embodiment of an improved time division communication process,

[0026] Fig.18 shows the structure of a base station according to an exemplary embodiment of an improved time division communication process,

[0027] Fig.19 A flow chart showing base station behavior according to an exemplary embodiment of an improved time division communication process,

[0028] Fig. 20is a signaling diagram illustrating exemplary exchanges between a UE and a gNB for an exemplary implementation of an improved time division communication procedure,

[0029] Fig.21 shows the TDD communication directions obtained inside and outside the SBFD resources when the exemplary implementation of the improved time division communication process is applied to the first scenario,

[0030] Fig. 22 shows the TDD communication directions obtained inside and outside the SBFD resources when the exemplary implementation of the improved time division communication process is applied to the second scenario,

[0031] Fig.23 shows the TDD communication directions obtained inside and outside the SBFD resources when the exemplary embodiment of the improved time division communication process is applied to a variation of the second scenario,

[0032] Fig.24 shows the TDD communication directions obtained inside and outside the SBFD resource when the exemplary implementation of the improved time division communication process is applied to the third scenario,

[0033] Fig.25 shows the TDD communication directions obtained inside and outside the SBFD resources when the exemplary embodiment of the improved time division communication process is applied to a variation of the third scenario,

[0034] Fig.26 shows the TDD communication directions obtained inside and outside the SBFD resource when the exemplary embodiment of the improved time division communication process is applied to the first scenario, and

[0035] Fig. 27 The resulting TDD communication directions inside and outside the SBFD resources when the exemplary embodiment of the improved time division communication process is applied to the first scenario are shown. DETAILED DESCRIPTION

[0036] 5G NR system architecture and protocol stack

[0037] 3GPP has been working on the next version of the fifth generation of cellular technology, or 5G for short, including the development of new radio access technologies operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, which allowed the continuation of 5G NR standard-compliant trials and commercial deployment of smartphones.

[0038] The overall system architecture assumes, among other things, a NG-RAN (Next Generation Radio Access Network) comprising gNBs, providing NG Radio Access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminations to the UE. The gNBs are interconnected to each other via Xn interfaces. The gNBs are also connected to the 5GC via Next Generation (NG) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that implements the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity that implements the UPF) via the NG-U interface. The NG-RAN architecture is Figure 1 (see, for example, 3GPP TS 38.300 (eg, v17.1.0), Section 4).

[0039] The user plane protocol stack for NR (see e.g. 3GPP TS 38.300, Section 4.4.1) consists of the PDCP (Packet Data Convergence Protocol, see Section 6.4 of 3GPP TS 38.300), RLC (Radio Link Control, see Section 6.3 of TS 38.300) and MAC (Medium Access Control, see Section 6.2 of TS 38.300) sublayers, which terminate in the gNB on the network side. In addition, a new access stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced on top of PDCP (see e.g. subclause 6.5 of TS 38.300). A control plane protocol stack is also defined for NR (see e.g. TS 38.300, Section 4.4.2). An overview of the Layer 2 functionality is given in subclause 6 of TS 38.300. The functionality of the RRC layer is listed in subclause 7 of TS 38.300.

[0040] For example, the medium access control layer handles logical channel multiplexing as well as scheduling and scheduling-related functions, including handling different parameter sets.

[0041] The physical layer (PHY) is responsible for, for example, coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. It also handles the 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 the transmission of a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, the physical channels are PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) for uplink and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel) and PBCH (Physical Broadcast Channel) for downlink.

[0042] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type communications (mMTC), which have different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and user-experienced data rates that are approximately three times higher than those provided by IMT-Advanced. On the other hand, in the case of URLLC, there are requirements for ultra-low latency (0.5 ms for both UL and DL for user plane latency) and high reliability (1-10 ms within 1ms). -5 Finally, mMTC may preferably require high connection density (1,000,000 devices / km2 in urban environments), large coverage in harsh environments, and extremely long-life batteries (15 years) for low-cost devices.

[0043] Therefore, an OFDM parameter set (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is suitable for one use case may not be well suited for another use case. For example, low-latency services may preferably require shorter symbol duration (and therefore larger subcarrier spacing) and / or fewer symbols per scheduling interval (a.k.a. TTI) compared to mMTC services. Furthermore, deployment scenarios with large channel delay spread may preferably require longer CP duration than scenarios with short delay spread. The subcarrier spacing should be optimized accordingly to retain similar CP overhead. NR can support more than one value of subcarrier spacing. Accordingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, ... are currently being considered. Symbol duration T u and subcarrier spacing Δf by the formula Δf=1 / T u In a similar manner as in the LTE system, the term "resource element" may be used to denote a minimum resource unit consisting of one subcarrier of the length of one OFDM / SC-FDMA symbol.

[0044] In the new radio system 5G-NR, for each parameter set and carrier, a resource grid of subcarriers and OFDM symbols is defined for uplink and downlink, respectively. Each element in the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 (e.g., v17.2.0), e.g., Section 4). For example, downlink and uplink transmissions are organized into frames with a duration of 10 ms, each frame consisting of ten subframes with a duration of 1 ms respectively. In a 5g NR implementation, the number of consecutive OFDM symbols per subframe depends on the subcarrier spacing configuration. For example, for a 15-kHz subcarrier spacing, a subframe has 14 OFDM symbols (similar to an LTE-compliant implementation, assuming a normal cyclic prefix). On the other hand, for a 30-kHz subcarrier spacing, a subframe has two slots, each slot including 14 OFDM symbols.

[0045] 5G NR functional division between NG-RAN and 5GC

[0046] Figure 2 The functional division between NG-RAN and 5GC is shown. The NG-RAN logical node is gNB or ng-eNB. 5GC has logical nodes AMF, UPF and SMF.

[0047] Specifically, gNB and ng-eNB host the following main functions:

[0048] — Functions for radio resource management, such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in both uplink and downlink (scheduling);

[0049] —IP header compression, encryption and data integrity protection;

[0050] - when the route to the AMF cannot be determined from the information provided by the UE, the AMF is selected at UE attach;

[0051] - routing user plane data towards UPF;

[0052] - routing control plane information towards the AMF;

[0053] —Connection establishment and release;

[0054] - Scheduling and transmission of paging messages;

[0055] — Scheduling and transmission of system broadcast information (originating from AMF or OAM);

[0056] - Measurements and measurement reporting configuration for mobility and scheduling;

[0057] - Transmission level packet marking in uplink;

[0058] —Session management;

[0059] —Support network slicing;

[0060] - QoS flow management and mapping to data radio bearers;

[0061] — Support for UEs in RRC_INACTIVE state;

[0062] —NAS message distribution function;

[0063] — Radio access network sharing;

[0064] — dual connectivity;

[0065] —Tight interworking between NR and E-UTRA.

[0066] The Access and Mobility Management Function (AMF) hosts the following key functions:

[0067] - Non-access stratum NAS signalling termination;

[0068] —NAS signaling security;

[0069] —Access layer AS security control;

[0070] - Core Network CN inter-node signalling for mobility between 3GPP access networks;

[0071] - Idle mode UE reachability (including control and execution of paging retransmissions);

[0072] —Registration area management;

[0073] - Support intra-system and inter-system mobility;

[0074] —Access authentication;

[0075] —Access authorization, including roaming rights checks;

[0076] - Mobility management control (subscription and policy);

[0077] —Support network slicing;

[0078] —Session Management Function SMF selection.

[0079] Additionally, the User Plane Function (UPF) hosts the following key functions:

[0080] - anchor point for intra / inter-RAT mobility (when applicable);

[0081] — External PDU session point interconnected with the data network;

[0082] —Packet routing and forwarding;

[0083] - Packet inspection and user plane part of policy rule enforcement;

[0084] - Traffic usage reports;

[0085] - an uplink classifier to support routing of traffic flows to the data network;

[0086] - Support branching points for multi-homed PDU sessions;

[0087] - QoS processing in the user plane, such as packet filtering, gating, UL / DL rate enforcement;

[0088] - Uplink traffic verification (SDF to QoS flow mapping);

[0089] - Downlink packet buffering and downlink data notification triggering.

[0090] Finally, the session management function SMF hosts the following main functions:

[0091] —Session management;

[0092] - UE IP address allocation and management;

[0093] —Selection and control of UP function;

[0094] - configure traffic steering at the user plane function UPF to route the traffic to the appropriate destination;

[0095] - Policy implementation and QoS control part;

[0096] —Downlink data notification.

[0097] RRC connection establishment and reconfiguration process

[0098] Figure 3 Some interactions between the UE, gNB and AMF (5GC entity) are shown in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED for the NAS part (see 3GPP TS 38.300).

[0099] RRC is a higher layer signaling (protocol) used for UE and gNB configuration. Specifically, the transition may involve the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities and UE security capabilities, etc.) and sending it to the gNB along with the Initial Context Setup Request. The gNB then activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE and by the UE responding to the gNB with a SecurityModeComplete message. Thereafter, the gNB performs reconfiguration to establish a signaling radio bearer 2 SRB2 and a data radio bearer DRB by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete from the UE by the gNB in ​​response. For a signaling-only connection, the steps related to RRCReconfiguration are skipped since SRB2 and DRB are not established. Finally, the gNB notifies the AMF of the completion of the establishment procedure with an Initial Context Setup Response.

[0100] Therefore, in the present disclosure, an entity of 5GC (e.g., AMF, SMF, etc.) is provided, which includes a circuit for establishing a next generation (NG) connection with a gNodeB; and a transmitter, which sends an initial context establishment message to the gNodeB via the NG connection to cause a signaling radio bearer establishment between the gNodeB and the user equipment (UE). Specifically, the gNodeB sends RRC signaling containing 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.

[0101] IMT use cases in 2020 and beyond

[0102] Figure 4 Some use cases for 5G NR are shown. In the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases that have been envisioned for IMT-2020 to support a wide variety of services and applications are being considered. The specification of Phase 1 for enhanced mobile broadband (eMBB) has been finalized. In addition to further extending eMBB support, current and future work will also involve standardization of ultra-reliable and low-latency communications (URLLC) and massive machine-type communications. Figure 4 Some examples of envisaged usage scenarios for IMT for 2020 and beyond are shown (see e.g. ITU-R M.20183 Figure 2 ).

[0103] URLLC use cases have stringent requirements on capabilities such as throughput, latency, and availability, and have been envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, remote medical surgery, distribution automation in smart grids, transportation safety, etc. Ultra-reliability for URLLC will be supported by identifying technologies that meet the requirements set by 3GPP TR 38.913. For NR URLLC in Release 15, the key requirements include a target user plane latency of 0.5 ms for UL (uplink) and a target user plane latency of 0.5 ms for DL ​​(downlink). The general URLLC requirement for one transmission of a packet is a BLER (block error rate) of 1E-5 for a packet size of 32 bytes, with a user plane latency of 1 ms.

[0104] From a physical layer perspective, reliability can be improved in a number of possible ways. The current scope for improving reliability involves defining a separate CQI table for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR becomes more stable and developed (a key requirement for NR URLLC), the scope for achieving ultra-reliability may widen. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0105] In addition, the technical enhancements targeted by NR URLLC are aimed at latency improvement and reliability improvement. Technical enhancements for latency improvement include configurable parameter sets, non-slot-based scheduling with flexible mapping, unlicensed (configured licensed) uplink, slot-level repetition for data channels, and downlink preemption. Preemption means stopping the transmission for which resources have been allocated, and the allocated resources are used for another transmission that has been requested later but has lower latency / higher priority requirements. Therefore, the already permitted transmission is preempted by the later transmission. Preemption can be applied independently of a specific service type. For example, a transmission for service type A (URLLC) can be used to preempt transmissions for service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0106] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices that typically send relatively small amounts of non-delay sensitive data. The devices are required to be low cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is a possible solution to save power from the UE's perspective and achieve long battery life.

[0107] As mentioned above, the range of reliability in NR is expected to widen. A key requirement for all cases, especially required for URLLC and mMTC, is high reliability or ultra-reliability. Several mechanisms can be considered to improve reliability from a radio perspective and a network perspective. In general, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity with respect to frequency, time and / or spatial domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0108] For NR URLLC, further use cases with more stringent requirements have been identified, such as factory automation, transportation industry and power distribution. The more stringent requirements are higher reliability (up to 10 6 level), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of a few μs (where the value can be one or a few μs, depending on the frequency range), and short latencies of around 0.5 to 1 ms, specifically a target user plane latency of 0.5 ms, depending on the use case.

[0109] In addition, for NR URLLC, several technical enhancements from a physical layer perspective have been identified. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. In addition, PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements have been identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes a smaller number of symbols than a slot (a slot including fourteen symbols).

[0110] QoS Control

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

[0112] 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) together with the PDU Session, and may subsequently configure one or more additional DRBs for one or more QoS Flows of that PDU Session (when to do so is up to the NG-RAN), e.g. as described above with reference to Figure 3 As shown. NG-RAN maps packets belonging to different PDU sessions to different DRBs. The NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while the AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0113] Figure 5 The 5G NR non-roaming reference architecture is shown (see, e.g., 3GPP TS 23.501, e.g., v16.9.0, section 4.2.3, see also v17.5.0). Figure 4 The application function (AF) (e.g., an external application server hosting 5G services) described in the exemplary embodiment interacts with the 3GPP core network to provide services, such as to support the application's influence on traffic routing, access the network exposure function (NEF), or interact with the policy framework (see Policy Control Function, PCF) for policy control (e.g., QoS control). Based on the operator deployment, the application function that is considered to be trusted by the operator may be allowed to interact directly with the relevant network function. The operator does not allow the application function that directly accesses the network function to interact with the relevant network function using the external exposure framework via the NEF.

[0114] Figure 5 Other functional units of the 5G architecture are shown, namely the network slice selection function (NSSF), the network repository function (NRF), the unified data management (UDM), the authentication server function (AUSF), the access and mobility management function (AMF), the session management function (SMF) and the data network (DN), such as operator services, Internet access or third-party services. All or part of the core network functions and application services can be deployed and run on a cloud computing environment.

[0115] Therefore, in the present disclosure, an application server (e.g., AF of 5G architecture) is provided, which includes a transmitter and a circuit, which sends a request including QoS requirements of at least one of URLLC, eMBB and mMTC services to at least one of the functions of 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements, and the circuit uses the established PDU session to perform the service.

[0116] Bandwidth Part - BWP

[0117] NR systems will support a maximum channel bandwidth much wider than the 20MHz bandwidth of LTE (e.g., 100MHz). Wideband communications are also supported in LTE via carrier aggregation (CA) of up to 20MHz component carriers. By defining a wider channel bandwidth in NR, frequency resources can be dynamically allocated via scheduling, which can be more efficient and flexible than LTE's carrier aggregation operation whose activation / deactivation is based on MAC control elements. Having a single wideband carrier also has advantages in terms of low control overhead because it only requires a single control signaling (carrier aggregation requires separate control signaling for each aggregated carrier).

[0118] In addition, similar to LTE, NR can also support aggregation of multiple carriers via carrier aggregation or dual connectivity.

[0119] Since UEs do not always require high data rates, using wide bandwidths may result in higher idle power consumption from the perspective of RF and baseband signal processing. In this regard, the newly developed concept of bandwidth portions for NR provides a way to operate UEs with a bandwidth smaller than the configured channel bandwidth in order to provide an energy-efficient solution despite supporting wideband operation. Any low-end terminal that cannot access the entire bandwidth of NR can benefit from this.

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

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

[0122] Although a UE may be configured with more than one BWP (e.g., up to 4 BWPs per serving cell, as currently defined for NR), a UE has only one active DL BWP at a time.

[0123] More information on BWP operation can be found in section 5.15 of 3GPP TS 38.321 (e.g. v17.1.0).

[0124] Switching between configured BWPs can be achieved in different ways. The operation of bandwidth parts in uplink and downlink is defined, for example, in 5G NR compatible implementations in 3GPP 38.321, e.g., v17.1.0, section 5.15. The BWP can be switched, for example, by downlink control information (DCI) (e.g., using bandwidth part indicators in DCI format 0_1 ​​(UL grant) and DCI format 1_1 (DL scheduling)), using BWP-inactivity timers, using RRC signaling, and by the MAC entity itself when initiating a random access procedure. For the 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 the secondary cell (SCell), the initial BWP is always explicitly configured, and the default BWP can also be configured. When a default BWP is configured for a serving cell, the expiration of the inactivity timer associated with the cell switches the active BWP to the default BWP.

[0125] Some DCI formats do not contain a BWP ID (such as formats 0_0 and 1_0), while in other DCI formats, the number of bits of the BWP ID is RRC configurable and can be 0, 1, 2 bits (such as for formats 0_1, 0_2, 1_1, and 1_2).

[0126] Figure 6 A scenario is shown in which three different BWPs are configured, namely BWP1 with a frequency bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP2 with a width of 10 MHz and a subcarrier spacing of 15 kHz, and BWP3 with a width of 20 MHz and a subcarrier spacing of 60 kHz.

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

[0128] According to an exemplary 5G NR compatible implementation in accordance with 3GPP 38.331 (e.g., v17.1.0), different RRCReconfiguration information elements may be used.

[0129] Control Information-Search Space Set

[0130] PDCCH monitoring is done by the UE in order 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).

[0131] The control information in the downlink (which may be referred to as e.g. downlink control information DCI) has essentially the same purpose in 5G NR as DCI in LTE, namely 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 5G NR compatible implementation, a number of different DCI formats have been defined (see TS 38.212, e.g. v17.2.0 Section 7.3.1). The following table gives an overview.

[0132]

[0133] According to an exemplary embodiment of TS 38.212, DCI format 2_0 is used to notify a slot format, a COT duration, an available RB set, and a search space set group switching.

[0134] The following information is sent via DCI format 2_0 with CRC scrambled by SFI-RNTI:

[0135] - If the higher layer parameter slotFormatCombToAddModList is configured,

[0136] - slot format indicator 1, slot format indicator 2, ..., slot format indicator N,

[0137] - If the higher layer parameter availableRB-SetsToAddModList is configured,

[0138] - Available RB set indicator 1, Available RB set indicator 2, ..., Available RB set indicator N1,

[0139] - If the higher layer parameter co-DurationsPerCellToAddModList is configured

[0140] - COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator N2.

[0141] - If the higher layer parameter switchTriggerToAddModList is configured

[0142] -Search space set group switching flag 1, search space set group switching flag 2, ..., search space set group switching flag M.

[0143] According to clause 11.1.1 of TS 38.213, the size of DCI format 2_0 may be configured by higher layers up to 128 bits.

[0144] In 5G NR, the PDCCH is sent in a region of radio resources called a Control Resource Set (CORESET). In LTE, the concept of a CORESET does not exist explicitly. Instead, the PDCCH in LTE uses the full carrier bandwidth (four for the narrowest case) in the first 1-3 OFDM symbols. In contrast, a CORESET in 5G NR can occur anywhere within a timeslot and anywhere in the frequency range of the carrier, except for CORESETs that the UE is not expected to process outside of its active bandwidth part (BWP).

[0145] Therefore, the UE performs a monitoring operation of the PDCCH, for example, as defined in Sections 10 and 11 of 3GPP TS 38.213 (e.g., Version 17.2.0). As exemplarily defined therein, the UE monitors a set of PDCCH candidates, which is defined according to a PDCCH search space set. The search space set may be a common search space set (CSS set) or a UE-specific search space set (USS set).

[0146] The search space sets are monitored in one or more CORESETs on the active DL BWP on each activated serving cell configured with PDCCH monitoring using the corresponding search space sets, where monitoring implies decoding each PDCCH candidate according to the monitored DCI format.

[0147] Conceptually, Figure 6 An exemplary illustration of the relationship between the bandwidth part, CORESET, search space, search space set and PDCCH candidates that the UE can monitor is provided. Figure 6 Obviously, one CORESET is shown per BWP, but more than one is possible. Each CORESET can then have several search spaces for one or more PDCCH candidates of a specific aggregation level (such as AL 2, 4 or 8), which can then be grouped into search space sets, such as a common SS set and a UE-specific SS set.

[0148] Time Domain Structure in 5G NR

[0149] In the time domain, transmissions in 5G NR are organized into frames of length 10ms, each of which is divided into 10 equally sized subframes of length 1ms. A subframe is in turn divided into one or more slots, each consisting of 14 OFDM symbols. The duration of a slot in milliseconds depends on the parameter set. For example, for a 15kHz subcarrier spacing, the NR slot thus has the same structure as an LTE subframe with a normal cyclic prefix. The subframes in 5G NR serve as a time reference independent of the parameter set, which is useful, especially in cases where multiple parameter sets are mixed on the same carrier, while the slot is a typical dynamically scheduled unit. This frame structure, on which 3GPP 5G NR communications are based, is described in [3GPP 5G NR Regulations]. Figure 7 Further exemplary details of the frame structure may be obtained from 3GPP TS 38.211 v 17.2.0 Section 4.3 "Frame structure" (further including Section 4.3.2 "Time slots").

[0150] Time Domain Duplex and Timeslot Format

[0151] The two key duplex schemes used in mobile communications are frequency division duplex (FDD) and time division duplex (TDD). Traffic patterns are changing and very specific to particular use cases, including not only downlink-heavy applications such as streaming, but also uplink-heavy applications such as cloud storage and personal broadcasting. To increase flexibility as well as make spectrum usage more efficient, time division duplex (TDD) is useful. TDD uses the same frequency for each direction, but separates the communications by using different time periods, for example, a frame that includes different time periods and time slots for uplink or downlink communications.

[0152] In order to make the most efficient use of the spectrum and avoid interference, all TDDs operating in the same frequency range and in the same area must be synchronized. This includes that base stations need to transmit in the same time period, and all devices should only transmit in dedicated time periods. To this end, terminals can be configured with specific transmission directions for time periods.

[0153] In LTE TDD, if a subframe (equivalent to a slot in NR) is configured for DL ​​or UL, all symbols within the subframe should be used as DL or UL. But in 5G NR, each symbol within a slot can be configured differently, for example, as downlink (hereinafter referred to as DL or D) or uplink (hereinafter referred to as UL or U). There are also flexible symbols (hereinafter referred to as F), which can be used as DL or UL, depending on further UE operation.

[0154] Each UE can then be configured by its base station with respect to the transmission direction of the time slots and symbols within each time slot. For example, the UE follows the UL or DL ​​scheduling DCI (e.g., DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2) to decide whether to transmit or receive in such flexible symbols.

[0155] Conceptually, the base station and UE therefore have a common understanding of the direction of transmission over time slots and symbols for TDD operation.

[0156] Figure 8 An exemplary format of slots and symbols is shown. As is apparent from this example, slots 0-6 are downlink slots, where all symbols are configured for the downlink direction. Slot 7 is a hybrid flexible / downlink slot, where the first 4 symbols are exemplarily assumed to be symbols for the downlink direction, where the remaining symbols in the slot have a flexible direction (i.e., can ultimately be used for either downlink or uplink). Slots 8-14 are flexible slots, where all symbols have a flexible direction. Slot 15 is a hybrid flexible / uplink slot, where the last 7 symbols are exemplarily assumed to be symbols for the uplink direction. Finally, slots 16-19 are uplink slots, where all symbols are configured for the uplink direction.

[0157] In the following, a more specific exemplary embodiment of TDD according to 5G NR will be explained. 5G NR currently uses a specific mechanism for defining the transmission direction of time slots and symbols and other specific mechanisms for signaling the defined transmission direction of time slots and symbols to the UE. Based on this information, the UE can then apply rules on how to determine the actual transmission direction of a time slot or symbol.

[0158] In this exemplary 5G-NR implementation, three different TDD configuration mechanisms are supported:

[0159] 1) Semi-static TDD configuration on a cell-common basis via SIB or RRC

[0160] 2) Semi-static TDD configuration on a UE-specific basis via RRC

[0161] 3) Dynamic TDD configuration of UE or UE group through dynamic (e.g. DCI) scheduling

[0162] 1) Semi-static cell public TDD configuration

[0163] Higher layer signaling, such as system information block SIB1 (eg, ServingCellConfigCommon SIB information element (IE)) or RRC message (eg, including ServingCellConfigCommon IE), may be used to provide an information element, called TDD-UL-DL-ConfigCommon, including information about the TDD configuration to the UE.

[0164] The information element TDD-UL-DL-ConfigCommon as currently defined in TS 38.331 v17.1.0 is presented below.

[0165] –TDD-UL-DL-ConfigCommon

[0166] IE TDD-UL-DL-ConfigCommon determines the cell-specific uplink / downlink TDD configuration.

[0167] TDD-UL-DL-ConfigCommon information element

[0168] --ASN1START

[0169] -- TAG-TDD-UL-DL-CONFIGCOMMON-START

[0170] TDD-UL-DL-ConfigCommon ::= SEQUENCE {

[0171] referenceSubcarrierSpacing SubcarrierSpacing,

[0172] pattern1 TDD-UL-DL-Pattern,

[0173] pattern2 TDD-UL-DL-Pattern OPTIONAL, -- Need R ...

[0175] }

[0176] TDD-UL-DL-Pattern ::= SEQUENCE {

[0177] dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1,ms1p25, ms2, ms2p5, ms5, ms10},

[0178] nrofDownlinkSlots INTEGER (0..maxNrofSlots),

[0179] nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1),

[0180] nrofUplinkSlots INTEGER (0..maxNrofSlots),

[0181] nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1),

[0182] ..., [[

[0184] dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL -Need R ]]

[0186] }

[0187] -- TAG-TDD-UL-DL-CONFIGCOMMON-STOP

[0188] --ASN1STOP

[0189]

[0190] As is apparent from the above example cell-specific TDD configuration, the parameter dl-UL-TransmissionPeriodicity defines the slot configuration period in milliseconds to which the TDD configuration applies. Within the slot configuration period, slots and symbols are defined as UL, DL or flexible for a period of time based on a combination of parameters nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots and nrofUplinkSymbols.

[0191] Therefore, two different modes (Mode 1 and Mode 2) can be defined, with Mode 1 being mandatory and Mode 2 being optional. The two modes may contain the same parameters, which are usually different values. If two modes are configured in TDD-UL-DL-ConfigCommon, the UE sets the slot format of each time slot on the first set of time slots as indicated in Mode 1, and sets the slot format of each time slot on the second set of time slots as indicated in Mode 2.

[0192] Fig. 9 An example of such a semi-static cell-specific configuration is shown in Fig. 9 Obviously, assuming a total of 20 slots in the time slot configuration cycle, for example, based on the formula S = P * 2 μ , resulting from a dl-UL transmission period of 2.5 ms and μ = 3. The parameter nrofDownlinkSlots is set to 7, causing the first 7 slots of the slot configuration period to be downlink slots, each comprising only downlink symbols. The parameter nrofDownlinkSymbols is set to 4, causing the first slot after the last full DL slot (here slot 7) to start with 4 DL symbols. The remaining symbols of slot 7 are not defined as D and are therefore considered to be flexible F.

[0193] The parameter nrofUplinkSlots is set to 4, causing the last 4 slots of the slot configuration period to be uplink slots, each comprising only uplink symbols. The parameter nrofUplinkSymbols is set to 7, causing the slot immediately before the first full UL slot (here slot 15) to end with 7 UL symbols. The remaining symbols of slot 15 are not defined as UL and are therefore considered to be flexible F.

[0194] Furthermore, the remaining slots of the slot configuration period are flexible slots and therefore include flexible symbols.

[0195] 2) Semi-static UE-specific TDD configuration

[0196] In addition, the use of the above cell-common TDD configuration, IE TDD-UL-DL-ConfigDedicated allows the network to further configure the flexible time slots defined by the cell-common TDD configuration (see the above IE TDD-UL-DL-ConfigCommon), for example, to adjust it to the traffic requirements of the UE. The IE TDD-UL-DL-ConfigDedicated can be sent from the base station to the UE, for example, using an RRC message, for example, as part of the IE ServingCellConfig (and then used to configure the serving cell for the UE).

[0197] The information element TDD-UL-DL-ConfigDedicated as currently defined in TS 38.331 v17.1.0 is presented below.

[0198] –TDD-UL-DL-ConfigDedicated

[0199] IE TDD-UL-DL-ConfigDedicated determines the UE-specific uplink / downlink TDD configuration.

[0200] TDD-UL-DL-ConfigDedicated information element

[0201] --ASN1START

[0202] -- TAG-TDD-UL-DL-CONFIGDEDICATED-START

[0203] TDD-UL-DL-ConfigDedicated ::= SEQUENCE {

[0204] slotSpecificConfigurationsToAddModList SEQUENCE (SIZE(1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig OPTIONAL, -- Need N

[0205] slotSpecificConfigurationsToReleaseList SEQUENCE (SIZE(1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N ...

[0207] }

[0208] TDD-UL-DL-ConfigDedicated-IAB-MT-r16::= SEQUENCE {

[0209] slotSpecificConfigurationsToAddModList-IAB-MT-r16 SEQUENCE (SIZE(1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig-IAB-MT-r16 OPTIONAL, -- Need N

[0210] slotSpecificConfigurationsToReleaseList-IAB-MT-r16 SEQUENCE (SIZE(1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N ...

[0212] }

[0213] TDD-UL-DL-SlotConfig ::= SEQUENCE {

[0214] slotIndex TDD-UL-DL-SlotIndex,

[0215] symbols CHOICE {

[0216] allDownlink NULL,

[0217] allUplink NULL,

[0218] explicit SEQUENCE {

[0219] nrofDownlinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S

[0220] nrofUplinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S

[0221] }

[0222] }

[0223] }

[0224] TDD-UL-DL-SlotConfig-IAB-MT-r16::= SEQUENCE {

[0225] slotIndex-r16 TDD-UL-DL-SlotIndex,

[0226] symbols-IAB-MT-r16 CHOICE {

[0227] allDownlink-r16 NULL,

[0228] allUplink-r16 NULL,

[0229] explicit-r16 SEQUENCE {

[0230] nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, --Need S

[0231] nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL -- NeedS

[0232] },

[0233] explicit-IAB-MT-r16 SEQUENCE {

[0234] nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, --Need S

[0235] nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL -- NeedS

[0236] }

[0237] }

[0238] }

[0239] TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1)

[0240] -- TAG-TDD-UL-DL-CONFIGDEDICATED-STOP

[0241] -- ASN1STOP

[0242]

[0243]

[0244]

[0245]

[0246] As is apparent from the above example cell-specific TDD configuration, a set of slot configurations may be defined, where each slot in the set of configurations is assigned an index (slotIndex) within the slot configuration period (as defined by the above cell-common TDD configuration). The configuration of such a slot may then be all DL ("allDownlink"), or all UL ("allUplink"), or mixed ("explicit"). If the configuration is all DL or all UL, all OFDM symbols within the indexed slot are DL or UL. If the configuration is explicit, there are additional parameters to indicate the number of initial downlink symbols in the indexed slot ("nrofDownlinkSymbols") and to indicate the number of last uplink symbols in the indexed slot ("norofUplinkSymbols"). The remaining symbols in the slot (i.e., not defined as uplink or downlink) are considered flexible.

[0247] IE tdd-UL-DL-ConfigDedicated is optional, and if the network does not configure this IE, the UE uses only the tdd-UL-DL-ConfigCommon IE to derive the time slot TDD configuration. When the IE tdd-UL-DL-ConfigDedicated is provided, the configuration in the tdd-UL-DLConfigDedicated IE can only cover the flexible time slots and symbols as defined by tdd-UL-DL-ConfigCommon. In other words, the UE-specific TDD configuration cannot change the direction of the time slots / symbols that have been allocated for the downlink or uplink defined by the tdd-UL-DL-ConfigCommon IE.

[0248] Fig.10 It is shown how the UE-specific TDD configuration can be used to further define the cell-common TDD configuration. Fig.10 Assumptions Fig. 9 The same cell-common TDD configuration of (see above description) and further assume an exemplary UE-specific configuration of flexible symbols and time slots with respect to the cell-common TDD configuration. Fig.10In this example, the UE-specific TDD configuration defines slots 7 and 8 of the slot configuration period as all downlink (e.g., using slotIndex and allDownlink), and slot 15 as all uplink (e.g., using slotIndex and allUplink). In addition, slots 9 and 14 are explicitly configured with a specific sequence (not shown) of downlink, uplink symbols in sequence (e.g., using slotIndex, explicit, and nrofDownlinkSymbols and nrofUplinkSymbols). The remaining symbols in slots 9 and 14 are flexible symbols, and the remaining slots 10, 11, and 12 remain flexible slots (including flexible symbols).

[0249] 3) Dynamic TDD configuration

[0250] By using downlink control information messages, in particular downlink control information messages of DCI format 2_0, a further and fast mechanism is supported by which the network can configure the flexible time slots defined by the cell-common TDD configuration (see IE TDD-UL-DL-ConfigCommon above), e.g. to adapt them to the traffic requirements of the UE.

[0251] Using DCI format 2_0, very dynamic TDD configurations can be implemented in a short time. 5G NR provides multiple slot formats, each of which defines the transmission direction of symbols within a single slot.

[0252] In this example 5G NR compliant implementation, the gNB uses the Slot Format Indicator (SFI) to inform the UE of the slot format to be used (see also TS 38.213 v17.2.0 section 11.1.1).

[0253] DCI format 2_0 may carry slot format indicator 1, slot format indicator 2, ... slot format indicator N (see TS 38.212, Section 7.3.1.3.1). For example, the slot format indicator includes an index value associated with one of a plurality of slot formats, e.g. in the form of a table, such as the following excerpt from Table 11.1.1-1 "Slot format for normal cyclic prefix" of TS 38.213.

[0254] Table 11.1.1-1: Slot format for normal cyclic prefix

[0255] The SFI Index field value of DCI format 2_0 indicates to the UE the slot format of each of a plurality of slots (e.g., each DL BWP or each UL BWP) starting from the slot in which the UE detects DCI format 2_0. The number of slots is equal to or greater than the PDCCH monitoring period of DCI format 2_0. As a result, in those slots where the TDD configuration defined by the SFI of DCI 2_0 is applicable, the UE follows the TDD configuration as defined by the SFI and the above table.

[0256] There may be up to N SFIs, where each SFI is provided to facilitate configuring a different SFI to a different UE (or UE group). The UE is then additionally provided with a position within the DCI ("positionInDCI") to be directed to one SFI. In this sense, DCI format 2_0 is a group common DCI.

[0257] Fig.11 It is shown how the dynamic TDD configuration of DCI 2_0 can be used to further define the cell-common TDD configuration. Fig.11 Assumptions Fig. 9 The same cell-common TDD configuration of (see above) and further exemplarily assume that the base station sends DCI 2_0 in slot 8, which is a flexible slot of the cell-common TDD configuration. It is further exemplarily assumed that the DCI 2_0 TDD configuration definition is valid for 5 slots, i.e. up to and including slot 12. The result is that the TDD configuration of the SFI overwrites the flexible definition originally defined by the cell-common TDD configuration in slots 8 to 12; Fig.11 In , this is shown by denoting the time slot as "SFI".

[0258] Even though not shown, it should be noted that as another option, the dynamic TDD configuration based on DCI 2_0 can also be used by the base station to further define a combined TDD configuration resulting from the cell-common and UE-specific TDD configurations (see Fig.10 of the display).

[0259] Sub-band non-overlapping full-duplex

[0260] Allocating limited duration for uplink in TDD results in reduced coverage, increased latency and reduced capacity. As a possible enhancement to this limitation of legacy TDD operation, 3GPP has initiated a study project "Study onevolution of NR duplex operation" to investigate the feasibility of allowing simultaneous downlink and uplink, also known as full duplex, or more specifically, sub-band non-overlapping full duplex (SFBD) at the gNB side within the legacy TDD band. Providing full-duplex operation within the TDD band can achieve more UL duration to enhance UL coverage, can reduce latency and can allow for increased UL capacity. If possible, there should be no or minimal impact on legacy UEs that will not support SBFD.

[0261] 3GPP may take a phased approach in Release 18, requiring only the gNB side to operate in full-duplex, while UEs can still operate in half-duplex. The gNB uses resources in the same frequency band for both transmission and reception. However, at a given time, each UE is only transmitting or receiving in the resources of the frequency band. SBFD operation is Fig.12 As shown in the example, full duplex on the gNB side and half duplex on the UE side are assumed. However, it is also possible that (one or more) UEs operate in full duplex to implement SBFD. Correspondingly, in time periods 2 and 3 (e.g., OFDM symbols 2 and 3, or time slots 2 and 3), UE1 and UE2 have different TDD directions, respectively. The solution for the improved TDD communication process further presented below is applicable to UEs supporting half duplex operation as well as UEs supporting full duplex operation.

[0262] SBFD should facilitate more flexible TDD directions (UL and DL) in certain time / frequency resources (e.g., subbands in the frequency domain and time periods in the time domain (such as one or more symbols, one or more time slots)). As another option, the frequency band used for SBFD operation can remain the same over the time period (or a portion thereof) or can change. In other words, SBFD can operate based on the same or different frequency resources across different SBFD time periods (e.g., SBFD symbols). Fig.13 Variable (left side) and identical frequency resources (right side) in different SBFD time periods (eg, SBFD symbols) are shown.

[0263] For example, subbands are used to allow flexible and possibly different communication directions (UL / DL) for several UEs. As an example, with SBFD, non-overlapping downlink subbands coexist during uplink timeslots, and uplink subbands coexist during corresponding downlink timeslots. This reduces TDD buffering delays caused by each exclusive TDD transmission opportunity.

[0264] From the UE's perspective, the communication direction in the subband may be different from the traditional communication direction (e.g., defined by one or more of the public or dedicated TDD configuration and SFI, see above). How to define the TDD direction in the SBFD resource is still under discussion. However, it may conflict with the traditional TDD direction.

[0265] Conceptually, the SFBD mode is different from the FDD mode in that the frequency separation between the UL band and the DL band is significantly smaller or narrower than that of the FDD mode. Optionally, the SFBD mode can operate on a single unpaired spectrum band, while the FDD mode operates on a paired spectrum including a UL spectrum band and a DL spectrum band.

[0266] For sub-band non-overlapping full-duplex (SFBD) operation at the gNB, the gNB may have to configure different transmission directions to different UEs on the same one or more symbols or time slots. As mentioned above, the current 3GPP specifications (e.g., Release 15 / 16 / 17) can implement such different configurations through UE-specific RRC TDD configuration or TDD configuration based on DCI 2_0.

[0267] SBFD operation is still under development in 3GPP. So far, only a few aspects of SBFD have been agreed upon.

[0268] An open question concerns whether (and if so how) the UE should be informed about the time and / or frequency location of the frequency (sub)bands used for SBFD operation. 3GPP discussed the following alternatives:

[0269] —SBFD Operation Alternative 1:

[0270] ◦ The time and frequency locations of the subbands used for SBFD operation are unknown to the UE.

[0271] ◦UE behavior follows the existing specification without introducing new UE behavior for SBFD operation on the gNB side.

[0272] —SBFD Operation Alternative 2:

[0273] ◦ The time and frequency locations of the subbands used for SBFD operation are unknown to the UE.

[0274] ◦ The UE behavior for non-SBFD-aware UEs follows the existing specifications.

[0275] ◦ From RAN1 perspective, new UE behaviors can be introduced for SBFD-aware UEs.

[0276] —SBFD Operation Alternative 3:

[0277] ◦ Only the temporal location of the subbands for SBFD operation is known to SBFD-aware UEs.

[0278] ◦ The UE behavior for non-SBFD-aware UEs follows the existing specifications.

[0279] ◦ From RAN1 perspective, new UE behaviors may be introduced for SBFD-aware UEs based on the temporal location of the subbands used for SBFD operation.

[0280] —SBFD Operation Alternative 4:

[0281] ◦ Both the time and frequency locations of the subbands for SBFD operation are known to SBFD-aware UEs.

[0282] ◦ The UE behavior for non-SBFD-aware UEs follows the existing specifications.

[0283] ◦ From RAN1 perspective, new UE behaviors can be introduced for SBFD-aware UEs based on the time and frequency location of the sub-bands used for SBFD operation.

[0284] The solution for the improved TDD communication process presented further below is mainly applicable to alternative 4 (and will therefore be described mainly on that basis for illustrative reasons only), since the improved UE knows both the time and frequency positions of the subbands used for SBFD operation. However, the solution for the improved TDD communication process presented further below can also be applied to alternative 3, according to which the UE only knows the time positions of the subbands used for SBFD operation.

[0285] If the location (frequency and / or time) of the subbands for SBFD operation is to be provided to the UE, semi-static (eg, SIB or RRC based) or dynamic configuration (eg, DCI based) is possible.

[0286] If the UE is aware of the SBFD resources, it may be beneficial for UE-to-UE co-channel CLI (cross-link-interference) measurement reports, which can be specific for SBFD, for example including one or more of the following:

[0287] - Measurement resource / report configuration

[0288] - Measurement / reporting details (including UE processing delays)

[0289] - Exchange of relevant information (between gNBs) (if necessary)

[0290] —Use of measurements at the gNB.

[0291] Furthermore, if the UE is aware of the SBFD resources, then for the UE configured with UL subbands in SBFD symbols, at least the following options are possible:

[0292] Option 1: SBFD-aware UE does not expect to be scheduled with UL transmission outside the UL subband or DL ​​reception inside the UL subband in SBFD symbols

[0293] Option 2: SBFD-aware UE does not expect to be scheduled with UL transmission outside the UL subband in SBFD symbols, and may be scheduled with DL reception inside the UL subband

[0294] - Option 3: SBFD-aware UE does not expect to be scheduled with DL reception inside the UL subband in SBFD symbols, and may be scheduled with UL transmission outside the UL subband

[0295] Option 4: SBFD-aware UEs can be scheduled with UL transmission outside the UL subband or DL ​​reception inside the UL subband in SBFD symbols

[0296] For example, for options 2 and 4, a UE can be scheduled with either UL or DL ​​in the SBFD UL subband, thereby supporting more flexible scheduling. On the other hand, options 1 and 3 allow scheduling in one direction.

[0297] Further Improvements

[0298] In the above, enhancements to full-duplex operation of TDD have been discussed, in particular the SBFD operation to be introduced in 3GPP Release 18. SBFD operation is still under development in 3GPP, and only a few aspects of SBFD have been agreed upon so far.

[0299] Therefore, the inventors have recognized the need to define SBFD operations in more detail.

[0300] In addition, since the TDD direction in SBFD (followed by new SBFD-capable UEs of Release 18) can be different from the legacy TDD direction (followed by legacy UEs of Release 15 / 16 / 17), the coexistence between Release 18 UEs using SBFD and legacy UEs following legacy TDD rules is an important issue that needs to be addressed.

[0301] Legacy UEs may receive many different communications, such as one or more of SSB (Synchronization Signal Block), SIBx (System Information Block), CSI-RS (Channel State Information Reference Signal), SPS PDSCH (Semi-Persistent Scheduling PDSCH), and DL paging. Legacy UEs may send many different communications, such as one or more of SRS (Sounding Reference Signal), PRACH (Physical Random Access Channel), MsgA (of random access procedure), CSI report and scheduling request on PUCCH, PUSCH transmission based on configured grant in UL.

[0302] Some or all of these downlink and uplink signals are semi-statically configured (e.g., via SIB and / or RRC) and cannot be dynamically adapted by the scheduling device (gNB) in a short period of time. Therefore, it is difficult for the gNB to coordinate all UL / DL communications from various UEs to avoid conflicts.

[0303] Specifically, cross-link interference (CLI), direct or in-band transmissions may occur and affect the semi-static UL / DL transmissions of legacy UEs (see, e.g., the signals above). This may occur, for example, in the following situations:

[0304] ◦SBFD is configured in some OFDM symbols / PRBs in Release 18, and

[0305] ◦ The actual scheduled TDD direction in the SBFD resources used by Release-18 UEs overrides the TDD direction defined by the legacy rules used by legacy UEs.

[0306] like Fig.14 As shown in , if Release-18 UE 2 is configured with SBFD resources and is instructed to transmit in SBD resources used as UL resources, DL transmission of legacy UE 1 may be affected due to CSI caused by direct resource overlap or by in-band transmission.

[0307] Despite Fig.14 In the exemplary scenario of , the two colliding resources directly overlap, but there are also problems where CLI is caused by resources that do not overlap but are close to each other in time and frequency (also assuming for example that two UEs are closely located in a cell).

[0308] It can also be exemplarily assumed that UE1's DL transmissions are dynamically scheduled (e.g., by DL DCI) or semi-persistently scheduled (SPS configuration). In the case of dynamically scheduled DL transmissions for UE1, the gNB can try to avoid such overlap of resources by adapting the scheduled DL resources or even canceling the DL grant. However, in the case of SPS, such fast adaptation of SPS DL transmissions is not possible, making the collision problem more severe.

[0309] Therefore, the inventors have identified the possibility of providing an improved TDD communication procedure allowing to avoid one or more of the above mentioned disadvantages.The present invention relates to different solutions and variants for such an improved TDD communication mobility procedure.

[0310] For example, the TDD configuration followed by the UE and gNB can be reconfigured in a flexible and fast manner, especially in the context of SBFD operation.

[0311] Example

[0312] In the following, UE, base station and corresponding processes that meet these requirements will be described for the new radio access technology envisioned for 5G mobile communication systems, but it can also be used in previous LTE-based mobile communication systems or future (e.g., 6G) mobile communication systems. Different implementations and variations will also be explained. The following disclosure is facilitated by the discussions and findings as described above and may, for example, be based at least on a portion thereof.

[0313] In general, it should be noted that many assumptions have been and are being made herein in order to be able to explain the basic principles of the present disclosure in a clear, concise and understandable manner. However, these assumptions are only to be understood as examples made herein for illustrative purposes, which are not necessarily necessary for the present invention, and therefore should not limit the scope of the present disclosure. The skilled person will know that the principles disclosed below and the principles set forth in the claims can be applied to different scenarios and in ways not explicitly described herein.

[0314] In addition, some of the terms for processes, entities, layers, etc. used below are closely related to the terms used in LTE / LTE-A systems or the current 3GPP 5G standardization, even though the specific terms used in the context of new radio access technologies for the next communication system have not yet been fully decided or may eventually change. Therefore, the terms may be changed in the future without affecting the functionality of the corresponding features and solutions. Therefore, those skilled in the art know that the solution and its scope of protection should not be limited to the specific terms used exemplarily herein due to the lack of updated or finally agreed terms, but should be understood more broadly in terms of the functions and concepts that form the basis of the solution explained in the present disclosure.

[0315] For example, a mobile station or mobile node or user terminal or user equipment (UE) is a physical entity (physical node) within a communication network. A node may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a set of predetermined functions to other functional entities of the same or another node or network. A node may have one or more interfaces that attach the node to a communication facility or medium through which the node can communicate. Similarly, a network entity may have a logical interface that attaches the functional entity to a communication facility or medium through which the network entity can communicate with other functional entities or communication nodes.

[0316] The term "base station" or "radio base station" here refers to a physical entity within a communication network. Like a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a set of predetermined functions to other functional entities of the same or another node or network. The physical entity performs some control tasks regarding the communication device, including one or more of scheduling and configuration. Note that the base station functionality and the communication device functionality can also be integrated within a single device. For example, a mobile terminal can also implement the functionality of a base station for other terminals. The term used in LTE is eNB (or eNodeB), while the currently used term for 5G NR is gNB. In addition, the base station can also be a gNB in ​​a non-terrestrial network (NTN) NR system.

[0317] The communication between a UE and a base station is generally standardized and may be defined by different layers such as PHY, MAC, RRC, etc. (see background discussion above).

[0318] For each of one or more time intervals of the time division configuration, the expression "time division configuration" here can be understood as the configuration of the communication direction in the time division-based communication scheme. The "communication direction" can be configured as one of the uplink direction, the downlink direction, or the flexible direction through the time division configuration.

[0319] The flexible direction may then in turn be either the uplink direction or the downlink direction. In an example embodiment, the "time division configuration" may be a "cell common" configuration or a "UE specific" configuration, such as the cell common TDD configuration and the UE dedicated TDD configuration defined by 5G, respectively (see above). Optionally, the UE specific time division configuration may be, for example, a "DCI based" configuration dedicated to a UE or a group of UEs, such as the time division configuration provided by DCI format 2_0 defined by 5G (see above). In this context, "cell common" may, for example, be understood to mean that the time domain configuration is common in the cell of the gNB, for example, common to all UEs located in the cell. In this context, "UE specific" may, for example, be understood to mean that the time domain configuration is specific to one UE or one group of UEs (which may also be referred to as "dedicated" to one UE). In this context, "DCI based" may, for example, be understood to mean that the time domain configuration is provided to the UE based on a DCI message, for example, quite dynamic in time when compared to typical communication mechanisms (such as RRC or SIB) for "cell common" time division configuration.

[0320] The expression "full-duplex resources" herein may be understood as resources (e.g., time-frequency resources) on which a gNB serving several UEs may operate in full-duplex, transmitting and receiving signals simultaneously via the same frequency. An example implementation is the sub-band non-overlapping full-duplex (SFBD) operation discussed and introduced in 5G (see above). "Full-duplex resources" may be understood as spanning one or more time periods, such as one or more symbols, or time slots, or subframes, or frames. Furthermore, "full-duplex resources" may be understood as spanning one or more frequency regions, such as one or more sub-bands, frequency bands, bandwidth portions, or any other suitable frequency units. For example, "full-duplex resources" may span less than the entire frequency range in which the UE operates, or may span the entire frequency range in which the UE operates.

[0321] The expression "for replacing" should be understood in the context of indicating which time division configurations are to be used. An alternative wording may indicate switching from a previously used time division configuration to another indicated time division configuration. Another alternative wording may be indicated as flipping from a previously used time division configuration to another indicated time division configuration. Another alternative wording may be stopping using a previously used time division configuration and starting using another indicated time division configuration.

[0322] Fig.15 A general, simplified and exemplary block diagram of a user equipment (also referred to as a communication device) and a scheduling device (here exemplarily assumed to be located in a base station, such as an LTE eNB (alternatively referred to as ng-eNB) or a gNB in ​​5G NR) is shown. The UE and the eNB / gNB communicate with each other via a (wireless) physical channel using transceivers, respectively.

[0323] The communication device may include a transceiver and a processing circuit. The transceiver may include and / or be used as a receiver and a transmitter. The processing circuit may be one or more hardware, such as one or more processors or any LSI. There is an input / output point (or node) between the transceiver and the processing circuit, through which the processing circuit can control the transceiver, that is, control the receiver and / or transmitter and exchange receive / transmit data. The transceiver as a transmitter and receiver may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit may implement control tasks, such as controlling the transceiver to send user data and control data provided by the processing circuit and / or receiving user data and control data further processed by the processing circuit. The processing circuit may also be responsible for performing other processing, such as determining, deciding, calculating, measuring, etc. The transmitter may be responsible for performing the processing of transmission and other processing related thereto. The receiver may be responsible for performing the receiving processing and other processing related thereto, such as monitoring the channel.

[0324] Different solutions for the improved time division communication process are described below. In the connection, an improved UE, an improved base station and an improved integrated circuit are presented, which participate in the improved time division communication process separately or together. Corresponding methods for UE behavior and base station behavior are also provided. The integrated circuit can correspond to the UE and the base station and their behaviors respectively.

[0325] The present solution for an improved time division communication procedure may be based on some or a combination of the different mechanisms described above in the context of an exemplary 3GPP 5G-NR implementation, including, for example, the use of signaling mechanisms (e.g., information elements in particular for common, UE-specific and dynamic signaling) or the use of defined rules for determining a specific transmission direction of a time slot or symbol based on received configuration information.

[0326] Fig.16 A simplified and exemplary UE structure according to an exemplary embodiment of an improved time division communication process solution is shown, which can be based on a combination of Fig.15 The general UE structure explained is implemented. Fig.16 The various structural elements of the UE shown in may be interconnected with each other, for example using corresponding input / output nodes (not shown), for example, to exchange control and user data and other signals. Although not shown for illustration purposes, the UE may include further structural elements.

[0327] As from Fig.16 Obviously, the UE may include a time division configuration receiver, a communication direction determination circuit, a full-duplex resource information receiver and a configuration switching indication receiver.

[0328] In this example, the receiver of the UE can therefore exemplarily at least partially perform one or more of receiving multiple time division configurations, receiving information about full-duplex resources, receiving a downlink control information message including a configuration switching indication, etc.

[0329] In the present example, as will become apparent from the following disclosure, the processing circuitry of the UE may thus exemplarily at least partially perform one or more of determining a communication direction based on different sets of one or more time division configurations, etc.

[0330] In the present example, as will become apparent from the following disclosure, the transmitter of the UE may thus exemplarily at least partially perform communications with the base station.

[0331] An exemplary process as will be disclosed in further detail below is implemented by a UE including the following. A receiver of the UE receives a plurality of time division configurations. A circuit of the UE determines a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations in a plurality of time division configurations previously received. The receiver receives information about a full-duplex resource. The receiver receives a downlink control information DCI message including a configuration switching indication. The configuration switching indication indicates a time division configuration to be used in a plurality of time division configurations previously received. The circuit determines a communication direction for each of one or more full-duplex time intervals of the full-duplex resource and, accordingly, for a complete full-duplex frequency region of the full-duplex resource based on a second set of one or more time division configurations in a plurality of time division configurations previously received. The second set of time division configurations includes at least the indicated time division configuration.

[0332] According to an optional and exemplary embodiment of the above-mentioned UE, the indicated time division configuration will be used instead of the previously used time division configuration in the first set of time division configurations, and the second set of time division configurations includes at least the indicated time division configuration but not the previously used time division configuration in the first set of time division configurations.

[0333] The corresponding exemplary method comprises the following steps performed by the UE:

[0334] Receive multiple time-division configurations,

[0335] determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of time division configurations previously received,

[0336] Receive information about full-duplex resources,

[0337] receiving a downlink control information (DCI) message including a configuration switch indication, wherein the configuration switch indication indicates a time division configuration to be used among the plurality of previously received time division configurations, and

[0338] For each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, the communication direction is determined based on a second set of one or more time division configurations of the previously received multiple time division configurations, wherein the second set of time division configurations includes at least the indicated time division configuration.

[0339] exist Fig.17 A corresponding sequence diagram of exemplary UE behaviors according to the above-mentioned UE and UE method is shown in FIG.

[0340] Thus, the improved TDD communication process described above achieves the purpose and overcomes some of the above disadvantages. For example, the improved TDD communication process facilitates easy and flexible and dynamic configuration of the communication direction of full-duplex resources (e.g., the SBFD resources mentioned above). The gNB can therefore control the communication direction of the full-duplex resources separately from the non-full-duplex resources. This facilitates changing the communication direction in order to avoid conflicts within the SBFD resources, as described above in conjunction with Fig.14 The above mechanism of the improved TDD communication procedure can be used to control different UEs supporting the mechanism.

[0341] Therefore, by dynamically controlling the TDD communication direction followed by the new version UE within the SBFD resources, it is facilitated to avoid or reduce intra-cell interference between the legacy UE and the new version UE supporting the improved TDD communication process. According to one option, the TDD communication direction within the SBFD resources can be changed from U to D, or from D to U, as needed, to be consistent with the conflicting legacy UE.

[0342] In addition, the improved TDD communication process is also beneficial to avoid or reduce inter-cell interference. Specifically, the gNB can control the TDD communication direction of the new version of the UE within the SBFD resource to align with the TDD communication direction used in the neighboring cell.

[0343] Some exemplary embodiments of the improved TDD communication process also relate to an improved base station. Accordingly, the improved TDD communication process also provides an improved base station participating therein, as will be explained below.

[0344] Fig.18 A simplified and exemplary base station structure according to an exemplary embodiment of an improved TDD communication process is shown, which can be based on a combination of Fig.15 The general base station structure explained above is implemented. Fig.18The various structural elements of the base station shown in the figure may be interconnected with each other, for example using corresponding input / output nodes (not shown), for example, to exchange control and user data and other signals. Although not shown for illustration purposes, the base station may include further structural elements.

[0345] As is apparent therefrom, the base station includes a time division configuration transmitter, a time division configuration determination circuit, a communication direction determination circuit, a full-duplex resource information transmitter, and a configuration switching indication transmitter.

[0346] In the present example, as will become apparent from the following disclosure, the receiver of the base station may thus exemplarily at least partially perform receiving communications from the UE, etc.

[0347] In the present example, as will become apparent from the disclosure below, the processing circuitry of the base station can therefore exemplarily at least partially perform one or more of determining a communication direction based on different sets of one or more time division configurations, determining a time division configuration for full-duplex resources, and the like.

[0348] In the present example, as will become apparent from the disclosure below, the base station's transmitter can therefore exemplarily at least partially perform one or more of sending multiple time division configurations, sending information about full-duplex resources, sending a downlink control information message including a configuration switching indication, and the like.

[0349] An exemplary process as will be disclosed in further detail below is implemented by a base station including the following. A transmitter of the base station sends a plurality of time division configurations. A circuit of the base station determines a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations in a plurality of time division configurations previously sent. The transmitter sends information about a full-duplex resource. The circuit determines a time division configuration to be used for the full-duplex resource in a plurality of time division configurations previously sent. The transmitter sends a downlink control information DCI message including a configuration switching indication, wherein the configuration switching indication indicates a determined time division configuration. The circuit determines a communication direction for each of one or more full-duplex time intervals of the full-duplex resource and correspondingly for a complete full-duplex frequency region of the full-duplex resource based on a second set of one or more time division configurations in a plurality of time division configurations previously sent. The second set of time division configurations includes at least the indicated time division configuration.

[0350] The corresponding method comprises the following steps performed by the base station:

[0351] Send multiple time-division configurations,

[0352] determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of the plurality of previously transmitted time division configurations,

[0353] Send information about full-duplex resources,

[0354] determining a time division configuration to be used for the full-duplex resource from among the plurality of time division configurations previously sent,

[0355] Sending a downlink control information DCI message including a configuration switching indication, wherein the configuration switching indication indicates a determined time division configuration;

[0356] For each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, the communication direction is determined based on a second set of one or more time division configurations in a plurality of time division configurations previously sent, wherein the second set of time division configurations includes at least the indicated time division configuration.

[0357] exist Fig.19 A corresponding sequence diagram of an exemplary base station behavior according to the above base station and corresponding method is shown in . The sequence diagram shows an exemplary and simplified implementation of the above base station method.

[0358] Fig. 20 is a signaling diagram of an exemplary and simplified implementation of the modified TDD communication procedure, showing the message exchange between different participating entities (here UE and gNB) and the steps performed at these entities.

[0359] The UE behavior and gNB behavior follow the above UE and base station and corresponding methods.

[0360] Fig. 20 Additionally shown is the communication between the UE and the gNB resulting from the determined communication direction. It is apparent that the UE and the gNB perform corresponding operations to allow synchronized communication based on the same understanding of the communication direction given by the configured TDD configuration. The improved TDD communication process facilitates communication within full-duplex resources that may be different compared to non-full-duplex resources by providing different TDD configurations for determining the communication direction of the full-duplex resources. A configuration switch indication may be sent from the gNB to the UE to indicate a different TDD configuration. To illustrate the difference, Fig. 20 The resulting communications are shown to be based on a first set of TDD configurations before and / or outside of the SBFD resources, while the resulting communications inside the SBFD resources are based on a second set of TDD configurations (which may be different than the first set).

[0361] The improved TDD communication process explained above may be applied to different exemplary scenarios, as will be explained in detail below.

[0362] According to the first scenario, the UE is configured with a cell-common TDD configuration and a UE-specific TDD configuration. The first set of the above-mentioned TDD configurations may include one or both of the cell-common time division configuration and the UE-specific time division configuration. Accordingly, the configuration switching indication of the DCI message indicates one of the cell-common time division configuration and the UE-specific time division configuration, which is then included in the second set of the above-mentioned TDD configurations. As a result, the (one or more) TDD communication directions inside the SBFD resource follow the indicated TDD configuration and may therefore be different from the (one or more) TDD communication directions outside the SBFD resource.

[0363] In one example of this first scenario, the UE is configured with both a cell-common TDD configuration and a UE-specific TDD configuration, and thus operates primarily according to a combination of both the cell-common TDD configuration and the UE-specific TDD configuration, e.g., as explained in detail above (see e.g. Fig.10 ). In this example, the first set of TDD configurations indicated above may include a cell-common TDD configuration and a UE-specific TDD configuration. In addition, for TDD communication operations of SBFD resources, the configuration switching indication of the DCI message may indicate a cell-common TDD configuration, so that the second set of TDD configurations indicated above includes only the indicated cell-common TDD configuration. As a result, the (one or more) TDD communication directions within the SBFD resources only follow the indicated cell-common TDD configuration, for example, ignoring the UE-specific TDD configuration.

[0364] Fig.21 An exemplary implementation of this example of the first scenario is shown in Fig.21 In FIG. 1 , a first scenario is shown from the perspective of one UE communicating with a gNB. The UE supports the SBFD mechanism and is therefore aware of the SBFD resources. An exemplary cell-common TDD configuration is shown in the top row, an exemplary UE-specific TDD configuration is shown in the middle row, and the resulting combined TDD configuration is shown in the bottom row, as will be explained in more detail below.

[0365] In this exemplary embodiment, it is assumed that the parameters introduced for the exemplary 5G compatible embodiment of the TDD configuration discussed above (see e.g. Fig. 9 , Fig.10 and Fig.11) to define the TDD configuration, and therefore uses RRC parameters such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, NrofUplinkSlots, allDownlink, allUplink. The communication directions (D, F, U) of the cell-common TDD configuration and UE-specific TDD configuration shown should be considered purely exemplary and illustrative and may be different from the communication directions shown.

[0366] Furthermore, the bottom row is divided into two sub-rows, where the bottom sub-row represents the SBFD sub-band (as an example of a full-duplex frequency region), where the upper sub-row represents the remaining frequency region to be operated by the UE. In the time domain, the SBFD resources are exemplarily assumed to span time slots 8-12.

[0367] In this exemplary embodiment, it is further assumed that the gNB sends a DCI with a configuration switching indication in time before the SBFD resources (here in time slot 7), indicating the cell-common TDD configuration.

[0368] As is apparent from the bottom row, the TDD communication direction inside the SBFD resources follows the indicated cell-common TDD configuration and is therefore partially different from the TDD communication direction outside the SBFD resources. Specifically, in the non-SBFD frequency region in time slots 8 to 12, the UE determines the communication direction based on a combination of the cell-common TDD configuration and the UE-specific TDD configuration. In this regard, the exemplary scenario assumes that the communication directions D and U of the cell-common TDD configuration cannot be overwritten by the UE-specific TDD configuration; only the flexible direction of the cell-common TDD configuration can be redefined by the UE-specific TDD configuration.

[0369] Therefore, the resulting TDD communication directions in the non-SBFD frequency region in time slots 8 to 12 are D, D, D / U, U and U, respectively.

[0370] On the other hand, in the SBFD frequency region in time slots 8 to 12, the UE determines the communication direction based only on the indicated cell-common TDD configuration, resulting in communication directions D, D, D / F, F, F (basically corresponding to the cell-common TDD configuration).

[0371] Comparing the TDD communication directions during the SBFD time intervals of the SBFD sub-band and the remaining frequency region, it is apparent that for time slots 10, 11 and 12, the respective communication directions are different.

[0372] Assumptions Fig.21 A collision between the UE and another UE (not shown) occurs in time slots 10, 11, and 12. Fig.21The UE communicates mainly in the uplink in time slots 10-12, while the other UE may communicate in the downlink. By changing the communication direction inside the SBFD resource in those time slots 10, 11 and 12, direct conflicts in the communication directions between different UEs can be avoided. According to the second scenario, the UE is configured with multiple different cell-common TDD configurations. The first set of the above-mentioned TDD configurations may include one of the multiple cell-common time division configurations. Accordingly, the configuration switching indication of the DCI message may indicate a cell-common time division configuration that is different from the cell-common time division configuration already used in the multiple cell-common time division configurations, and then the cell-common time division configuration corresponds to the second set of TDD configurations represented above. As a result, the (one or more) TDD communication directions inside the SBFD resource follow the indicated cell-common TDD configuration, and can therefore be different from the (one or more) TDD communication directions outside the SBFD resource that follow the original cell-common TDD configuration.

[0373] Fig. 22 An exemplary implementation of the second scenario is shown in FIG. Fig.21 Similar assumptions are made for the first scenario. In addition, the UE is configured with two cell-common TDD configurations #1 and #2, which define different TDD communication directions in some time slots (specifically in time slots 2-15). It is assumed that the UE mainly operates according to only one cell-common TDD configuration (here, cell-common TDD configuration #1), for example, as explained in detail above (see, for example, Fig. 9 ). Again, the gNB promptly sends the DCI and configuration switch indication, indicating cell-common TDD configuration #2 in this example.

[0374] As from Fig. 22 As apparent from the bottom row, the TDD communication direction inside the SBFD resources follows the indicated cell-common TDD configuration #2 and is therefore partially different from the TDD communication direction outside the SBFD resources following the cell-common TDD configuration #1.

[0375] In detail, the resulting TDD communication directions in the non-SBFD frequency area in time slots 8 to 12 are D, D, D, D / F, and F, corresponding to cell-common TDD configuration #1. On the other hand, in the SBFD frequency area in time slots 8 to 12, the UE determines the communication direction based on the indicated cell-common TDD configuration #2, resulting in communication directions U, U, U, U, and U.

[0376] Comparing the TDD communication directions during the SBFD time intervals of the SBFD sub-band and the remaining frequency region, it is obvious that the TDD communication directions in all time slots 8 to 12 are different, including even opposite directions (D to U) in time slots 8, 9, and 10, and also partially opposite directions in time slot 11.

[0377] If in any of these time slots 8-12 it may occur Fig. 22 If a UE has a potential conflict with another UE (not shown), such conflict can be avoided by changing the communication direction of the SBFD resources.

[0378] In addition, gNBs can be allowed to reuse the scheduling of Release 18 UEs that support cross-division-duplex (XDD) in the frequency domain (e.g., different frequency sub-bands), allowing for less impact on legacy UEs. Cell-common configuration can be more efficient.

[0379] According to a variation of the second scenario, the UE is not only configured with two different cell-common TDD configurations, but also with a UE-specific TDD configuration. Therefore, the UE-specific TDD configuration is also considered for determining the TDD communication direction (see, for example Fig.10 ). Accordingly, the first set of TDD configurations indicated above to be used outside the SBFD resources also includes the UE-specific TDD configuration in addition to one of the cell-common TDD configurations, and the second set of TDD configurations indicated above of the TDD configurations to be used inside the SBFD resources also includes the UE-specific TDD configuration in addition to another of the cell-common TDD configurations. Therefore, the two sets are based on the same UE-specific TDD configuration, but differ from each other in the cell-common TDD configuration used.

[0380] Fig.23 An exemplary implementation of this variant of the second scenario is shown in Fig. 22 The same cell common TDD configuration #1 and #2. In addition, Fig.23 An exemplary UE-specific TDD is shown in FIG, which may exemplarily include many uplink time slots. In this example illustration, it is assumed that the SBFD resources span time slots 4 to 11. In detail, the resulting TDD communication directions in the non-SBFD frequency region in time slots 4 to 11 are the result of the combination of the cell-common TDD configuration #1 and the UE-specific TDD configuration: D, D, D, D, D, D, D, D, D / U. On the other hand, in the SBFD frequency region in time slots 4 to 11, the TDD communication directions are the result of the combination of the cell-common TDD configuration #2 and the UE-specific TDD configuration: F, D, D / F, U, U, U, U, U, U.

[0381] Comparing the TDD communication directions during the SBFD time intervals for the SBFD subband and the remaining frequency region, it is apparent that the TDD communication directions substantially change, including even opposite directions (D to U). This facilitates reconfiguration of the TDD communication directions within the SBFD resources according to the new improved TDD communication process.

[0382] According to the third scenario, the UE is configured with multiple different UE-specific TDD configurations. First, it is exemplarily assumed that the UE is not configured with a cell-common TDD configuration. However, a variation of the third scenario to be described later assumes that in addition to multiple different UE-specific TDD configurations, the UE is additionally configured with a cell-common TDD configuration.

[0383] The first set of TDD configurations indicated above may include one of a plurality of UE-specific TDD configurations. Accordingly, the configuration switching indication of the DCI message may indicate another UE-specific time division configuration different from one of the plurality of UE-specific time division configurations that is already in use, and then the other UE-specific time division configuration corresponds to the second set of TDD configurations indicated above. As a result, the (one or more) TDD communication directions inside the SBFD resource follow the indicated UE-specific TDD configuration, and therefore may be different from the (one or more) TDD communication directions outside the SBFD resource that follow the original UE-specific TDD configuration.

[0384] Fig.24 An exemplary implementation of the second scenario is shown in FIG. Fig.21 and Fig. 22 The first scenario and the second scenario are similar. In addition, the UE is configured with two UE-specific TDD configurations #1 and #2, which define different TDD communication directions in some time slots (specifically in time slots 2-15). For the convenience of explanation and illustration, the communication directions defined by the two UE-specific TDD configurations are the same as those defined by Fig. 22 In the second scenario, the communication directions defined by the common TDD configuration of the two cells are the same.

[0385] It is exemplarily assumed that the UE mainly operates according to only one UE-specific TDD configuration #1. Again, the gNB sends DCI and configuration switching indication in a timely manner, indicating UE-specific TDD configuration #2 in this example.

[0386] exist Fig.24In the exemplary scenario of , it is exemplarily assumed that the SBFD resources span time slots 8 to 12. In detail, the TDD communication directions obtained in the non-SBFD frequency area in time slots 8 to 12 are D, D, D, D / F, and F, corresponding to UE-specific TDD configuration #1. On the other hand, in the SBFD frequency area in time slots 8 to 12, the UE determines the communication direction based on the indicated UE-specific TDD configuration #2, resulting in communication directions U, U, U, U, and U.

[0387] Comparing the TDD communication directions during the SBFD time intervals of the SBFD sub-band and the remaining frequency region, it is obvious that the TDD communication directions in all time slots 8 to 12 are different, including even opposite directions (D to U) in time slots 8, 9, and 10, and also partially opposite directions in time slot 11.

[0388] if Fig.24 A potential collision of the UE with another UE (not shown) may occur in any of these time slots 8-12, and such collision may be avoided by changing the communication direction of the SBFD resources.

[0389] As also mentioned above in connection with the second scenario, the improved TDD communication process may also be beneficial in connection with UE scheduling of Release 18 UEs supporting XDD.

[0390] According to a variation of the third scenario, the UE is not only configured with two different UE-specific TDD configurations, but also configured with a cell-common TDD configuration. Therefore, the cell-common TDD configuration is also considered for the determination of the TDD communication direction (see, for example Fig.10 ). Accordingly, in addition to the cell-common TDD configuration, the first set of TDD configurations to be used outside the SBFD resources includes one of the multiple UE-specific TDD configurations, and in addition to the cell-common TDD configuration, the second set of TDD configurations to be used inside the SBFD resources includes another of the multiple UE-specific TDD configurations. Therefore, the two sets are based on the same cell-common TDD configuration, but differ from each other in the UE-specific TDD configuration used.

[0391] Fig.25 An exemplary implementation of this variation of the third scenario is shown in FIG. Fig.25 An exemplary cell-common TDD configuration with indicated communication directions is shown. In addition, Fig.25Two different UE-specific TDD configurations #1 and #2 are shown. The two UE-specific TDD configurations differ from each other in that one includes a number of downlink time slots (see #1) and the other includes a number of uplink time slots (see #2), which introduces flexibility on how to switch the communication direction inside the SBFD resources.

[0392] Again, the gNB sends the DCI and configuration switch indication in a timely manner, indicating UE-specific TDD configuration #2 in this example.

[0393] As Fig.25 As a result of this scenario, the TDD communication direction outside the SBFD resource follows the combination of the cell-common TDD configuration and the UE-specific TDD configuration #1. On the other hand, inside the SBFD resource, the determination of the communication direction follows the indicated UE-specific TDD configuration #2 combined with the cell-common TDD configuration. Since different UE-specific TDD configurations are used, the (one or more) TDD communication directions outside the SBFD resource can be different from the TDD communication directions inside the SBFD resource.

[0394] In detail, the TDD communication directions obtained in the non-SBFD frequency area in time slots 8 to 12 are all D, following D-weight UE-specific TDD configuration #1. On the other hand, in the SBFD frequency area in time slots 8 to 12, the UE determines the communication directions D / F, U, U, U, U, respectively.

[0395] Comparing the TDD communication directions during the SBFD time intervals of the SBFD sub-band and the remaining frequency region, it is apparent that the TDD communication directions are different for all time slots 8 to 12, including even opposite directions (D vs. U) in time slots 9 to 12.

[0396] if Fig.25 A potential collision of the UE with another UE (not shown) may occur in any of these time slots 9-12, and such collision can be avoided by changing the communication direction of the SBFD resources.

[0397] The above three different exemplary scenarios differ with respect to TDD configuration, and the TDD communication direction is determined based on the TDD configuration.

[0398] In the above embodiments and variations of the improved TDD communication procedure, it is assumed that the configuration switching indication is sent from the gNB to the UE in a DCI message. However, it is not necessary to use a DCI message to convey the configuration switching indication.

[0399] Furthermore, the following variations, which may be combined with other embodiments and variations of the improved TDD communication procedure, respectively, provide details on how DCI messages and configuration switching indications may be implemented.

[0400] According to an exemplary embodiment, the DCI message may be DCI format 2_0, which is already known from the above-mentioned current 5G compatible process. As is apparent from the current definition of DCI format 2_0, the DCI includes slot format indicators 1 to N, each of which points to a table of the technical standard, associating different slot format indicator values ​​with different slot formats (which communication direction D, U, F) to be used in the slot. In the current technical standard of 5G, this table can be found in Table 11.1.1-1 of TS 38.213 (see also the above table in the section on "3) dynamic TDD configuration"). However, the SFI (in particular its number of bits) allows indicating more values ​​than the values ​​required to select the slot format for the slot. One or more of these alternate values ​​of the SFI can therefore be used to indicate the intended TDD configuration. DCI format 2_0, in particular the SFI, can therefore be reused as a configuration switching indicator to indicate the TDD configuration for the SBFD resource.

[0401] Alternatively, while reusing the DCI format 2_0, a separate field for configuring a switching indication may also be included (instead of the SFI as assumed above).

[0402] Still alternatively, a new DCI message may be created to carry the configuration switching indication.

[0403] In the above alternatives, the configuration switching indication may be of different numbers of bits, so as to be able to clearly indicate and distinguish different TDD configurations that the UE may be configured with. In some cases, one bit may be sufficient for the configuration switching indication.

[0404] In any of the above embodiments, the DCI message and the configuration switch indication allow the gNB to provide appropriate indication to the UE as to which TDD configuration should be used to determine the communication direction of the SBFD resources.

[0405] In the above-described embodiment of the improved time division communication procedure, it is described that the UE obtains information about SBFD resources, for example from a gNB serving the UE. A further embodiment of the improved time division communication procedure (which can be combined with any other described embodiment) provides further details on how the SBFD resource notification mechanism can be implemented.

[0406] According to an exemplary embodiment, the information about the full duplex (SFBD) resource may include information about one or more of the following:

[0407] ◦ One or more full-duplex time periods for full-duplex resources, and

[0408] ◦ One or more full-duplex frequency regions for full-duplex resources.

[0409] The improved TDD communication process is therefore applicable to situations in which the UE is informed of the SBFD time period (e.g., time slot) but not the SBFD frequency region (e.g., subband), in which the UE is informed of the SBFD frequency region but not the SBFD time period, and in which the UE is informed of both the SBFD time period and the SBFD frequency region.

[0410] Several communication mechanisms can be used to provide the SBFD resource information from the gNB to the UE. According to one option, system information broadcast can be used, according to which the necessary information is included in one system information block. Considering that the SBFD resource information is cell-common, system information broadcast allows to easily and efficiently reach the UE in the cell of the gNB.

[0411] According to another option, a message of the RRC protocol can be used, according to which the necessary information is included in the RRC message and sent separately to UEs requiring SBFD resource information, such as UEs supporting the improved TDD communication procedure.

[0412] In the above explained embodiments of the improved time division communication process, it is described how the UE can switch between different time division configurations for TDD communication based on the received configuration switching indication. In addition, further embodiments of the improved time division communication process (which can be combined with any other described embodiments) relate to subsequent processing at the UE and the gNB after the switch, for example, how long the TDD communication in the SBFD resources follows the indicated time division configuration and how the TDD communication can be switched to another time division configuration such as the original time division configuration.

[0413] According to the first embodiment, the determination of the communication direction of the full-duplex resources based on the configuration switch indication is carried out until otherwise indicated; therefore, it is not necessarily limited in time, but still remains under the direct control of the gNB. As presented above, the configuration switch indication is sent by the gNB to indicate the specific TDD configuration to be used to determine the communication direction within the SBFD resources. If needed, this same mechanism can be reused to change the communication direction within the SBFD resources again.

[0414] In more detail, the TDD communication direction in the SBFD resources is determined based on the previous configuration switch indication (in particular the TDD configuration indicated therein) until a new configuration switch indication is received and followed. At a certain moment, the gNB may decide that the TDD communication direction in the SBFD resources should be changed for the UE, for example because there is no longer a conflict with another UE or because the characteristics of the conflict have changed. The gNB therefore determines again the appropriate TDD configuration for being indicated, sets the configuration switch indication according to the determined TDD configuration, and sends the configuration switch indication together with the DCI to the UE. Therefore, the UE receives this further DCI with the further configuration switch indication from the gNB. Then, according to any of the explained improved TDD communication procedures, the UE determines the communication direction in the SBFD resources based on at least the TDD configuration indicated by the new DCI and the new configuration switch indication. Accordingly, a third set of TDD configurations may be defined, based on which the communication direction of the subsequent SBFD resources is determined. The third set of TDD configurations includes at least the TDD configuration indicated by the new configuration switch indication.

[0415] Will combine Fig.26 An example of the first embodiment is explained. Fig.26 In, combine as above Fig.21 The scenario shown and discussed applies the first embodiment. Accordingly, the UE is configured with a cell-common TDD configuration and a UE-specific TDD configuration. Fig.26 Exemplarily, two separate SBFD resources separated in the time domain are assumed, where the first SBFD resource #1 spans time slots 7 to 11, and the second SBFD resource #2 spans time slots 13 to 17. In addition, Fig.26 Two separate DCI messages are shown, each including a configuration switching indication. The two configuration switching indications indicate different TDD configurations to be followed within the SBFD resource. In this exemplary scenario, the first DCI #1 indicates a cell-common TDD configuration, so that the TDD communication direction for SBFD resource #1 is determined based on the indicated cell-common TDD configuration. Accordingly, the TDD communication directions obtained in time slots 7 to 11 are D, D, D, D / F and F, corresponding to the corresponding TDD communication directions defined by the cell-common TDD configuration. On the other hand, the TDD communication direction outside the SBFD resource #1 is determined based on a combination of cell-common and UE-specific TDD configurations, for example, in the non-SBFD frequency region of time slots 7 to 11, directions D, D, D, D / U and U are generated.

[0416] Then, the second DCI #2 indicates the UE-specific TDD configuration, so that the TDD communication direction of SBFD resource #2 is determined based on the indicated UE-specific TDD configuration and the cell-common TDD configuration. As a result, the TDD communication directions inside the SBFD resource and outside the SBFD resource are the same, for example, in time slots 13 to 17, they are all U.

[0417] Thus, as already explained above, the repeated transmission of the DCI allows to repeatedly change the determination of how the TDD communication direction inside the SBFD resources should be performed.

[0418] According to another embodiment, determining the communication direction of the full-duplex resource based on the configuration switching indication is completed within a limited time depending on the effective time period. These embodiments of the improved TDD communication process are based on a previously configured or fixed effective time period associated with the configuration switching indication, and are different from the previous embodiments, so additional DCI and configuration switching indication are not necessarily required to change the TDD communication direction determination in the SBFD resource. Therefore, compared with the previous first embodiment, these embodiments can save overhead on the PDCCH.

[0419] Conceptually, these further embodiments involve completing the determination of the TDD communication direction within the SBFD resources based on the received configuration switch indication (particularly the TDD configuration indicated therewith) until the corresponding validity period expires.

[0420] When the valid period expires, the TDD configuration previously indicated by the configuration switching indication for the SBFD resource is automatically switched to another TDD configuration (which can be represented as a fallback TDD configuration). As a result, after the valid period expires, the UE determines the communication direction in the SBFD resource based on at least the other fallback TDD configuration to which it is switched. Correspondingly, a third set of TDD configurations can be defined, based on which, after the valid period expires, the communication direction of the subsequent SBFD resource is then determined. The third set of TDD configurations includes at least another fallback TDD configuration.

[0421] The fallback TDD configuration may be one of multiple TDD configurations that the UE is configured with, such as a previous TDD configuration before the DCI-based handover (denoted as, for example, the initial TDD configuration) or such as a TDD configuration different from the initial TDD configuration (eg, the default TDD configuration).

[0422] There are several possibilities on how to implement the validity period (e.g., when the validity period should start). In one example, in general, the validity period may start at a time related to the reception time of the DCI message with the configuration switching indication. In addition, the start of the validity period may be fixed in advance, or may be configurable, for example, by the gNB.

[0423] One option is that the valid time period starts at the start of the time slot in which the configuration switch indication is received or the start of the directly subsequent time slot. However, these are only two of many different options.

[0424] Other example options may use one of the following as the start of the validity period:

[0425] - the Nth time slot / symbol from the time when the configuration switch indication is received,

[0426] —The Nth slot / symbol after the HARQ-ACK feedback transmission, which refers to the acknowledgement of the DCI and is sent to the base station to confirm to the gNB that the DCI is correctly decoded.

[0427] —N can be 0, 1, 2, ..., which can be fixed or configured.

[0428] A further improvement of the TDD communication process involves the use of an effective period and the introduction of a reset of the effective period when the UE is scheduled for transmission or reception in full-duplex resources. As a result, the effective period is restarted and thus automatically extended without the need to send another DCI again. This allows for overhead savings.

[0429] Furthermore, there are several possibilities as to how the length of the validity period may be defined. According to one option, the validity period may have a length based on a fixed value specified, for example, by the firmware (operating system) of the UE. For example, the validity period is set by a technical standard, and the definition of the technical standard is then encoded into the firmware, based on which the UE operates.

[0430] According to yet another option, the validity period may adopt a cell-common value that applies to all UEs in the cell. The cell-common value may be defined by the gNB and then sent to the UE, for example, based on system information broadcast (e.g., in a system information block) or using one or more suitable RRC messages.

[0431] According to yet another option, the validity period may take a UE-specific value that is configured and applied by the specific UE for which it is intended. Thus, the UE-specific value may be defined by the gNB and then sent to the UE, for example, in a suitable RRC message or downlink control information DCI message.

[0432] According to another embodiment, the UE may support two or more of the above options on how to define the validity period. In that case, as an example, a cell-common value of the validity period may be broadcast in the cell for all UEs to receive. Then, a UE-specific value may be sent to the UE, overwriting the cell-common value obtained by broadcasting.

[0433] In some of the above options, the validity period value is defined by the gNB. The validity period may be specified, for example, in number of slots, symbols or frames, or a combination of the above.

[0434] Will combine Fig. 27 An example of these further embodiments is explained. Fig. 27 In, combine as above Fig.21 These embodiments are applied to the scenarios shown and discussed above. Accordingly, the UE is configured with a cell-common TDD configuration and a UE-specific TDD configuration. Fig.26 In the same way described, Fig. 27 Exemplarily, two separate SBFD resources separated in the time domain are assumed. Fig.26 Using another DCI as done in Fig. 27 The implementation depends on the validity period associated with the DCI carrying the configuration switching indication. It is exemplarily assumed that the validity period in this example starts with the reception of the DCI and has a length of 6 time slots.

[0435] Correspondingly, assuming that DCI #1 is received in time slot 6, the valid time period expires in time slot 12, just before the start of the second SBFD resource #2. When the valid time period expires, the determination of the TDD communication direction for the SBFD resource falls back to the UE-specific TDD configuration used before the switch triggered by DCI #1. Therefore, the TDD communication direction of SBFD resource #2 is determined based on the fallen back UE-specific TDD configuration and the cell-common TDD configuration. As a result, the TDD communication direction inside and outside SBFD resource #2 is the same, here, for example, in time slots 13 to 17, all are U.

[0436] As already explained above, the use of the validity period thus allows implementing differently determined time limits for TDD communication directions within the SBFD resources triggered by the DCI in a simple manner and without additional transmission overhead.

[0437] In the above, an embodiment of an improved TDD communication process has been described, which utilizes an effective time period to control the time for determining the TDD communication direction of the SBFD resource based on the TDD configuration indicated by the DCI. According to a variation that can be combined with the described embodiment of the improved TDD communication process, the effective time period can be implemented as a timer operated at the UE and the base station. The timer will be configured with an expiration value corresponding to the length of the effective time period (e.g., defined as discussed above). According to any of the options discussed above, the timer starts at a certain time, such as starting at the beginning of the time slot directly after the time slot in which the DCI with the configuration switching indication is received. The timer can stop when it expires. In another variation, when the UE is scheduled for transmission or reception in a full-duplex resource, the timer (also generally discussed above) can be reset.

[0438] The improved TDD communication process has been described above as determining the TDD communication direction inside and outside the SBFD resource based on one or more different TDD configurations. The determination of the TDD communication direction follows the determination rule of how to combine one or more TDD configurations to derive the final TDD communication direction within the corresponding time period. How to determine the TDD communication direction may depend on which TDD configurations exist or are configured to the UE. For example, if there is only a cell-common TDD configuration, but there is no UE-specific TDD configuration, the determination rule involves determining the TDD communication direction based only on the cell-common TDD configuration. On the other hand, if there is a cell-common TDD configuration and a UE-specific TDD configuration, the determination rule involves determining the TDD communication direction based on both the cell-common TDD configuration and the UE-specific TDD configuration (for example, wherein the UE-specific TDD configuration can cover the flexible communication direction defined by the cell-common TDD configuration). Therefore, which determination rule should be followed to determine the TDD communication direction depends on one of the multiple TDD configurations configured by the UE, where the decisive TDD configuration is exemplarily represented, if it exists, it is the UE-specific TDD configuration, or if there is no UE-specific TDD configuration, it is the cell-common TDD configuration.

[0439] With reference to different sets of TDD configurations to be used inside and outside the SBFD resource, the deterministic TDD configurations of the first and second sets of TDD configurations can be different or the same. Fig.21 The solution discussed, the deterministic TDD configuration is different inside and outside the SBFD resource, for example, changing from a cell-common TDD configuration to a UE-specific TDD configuration and vice versa. Fig. 22 In the solution discussed, the deterministic TDD configuration is also changed, that is, from one cell common TDD configuration to another cell common TDD configuration. Fig.23The discussed solution, the deterministic TDD configuration remains the same, ie, the UE-specific TDD configuration, regardless of changes in the cell-common TDD configuration.

[0440] According to another improved TDD communication process, instead of the indication of the TDD configuration, the above DCI includes a suitable indication to indicate the determination rule followed by the UE inside the SBFD resource, which may be a determination rule different from the determination rule followed by the UE outside the SBFD resource. Therefore, this improved TDD configuration process changes in the indication carried by the DCI. Other aspects of the improved TDD communication process with configuration switching indication described above can also be applied in the same way to the improved TDD communication process with determination rule indication, for example, as combined with Figure 21-Figure 25 One or more of the different scenarios discussed, and how one or more of the DCI and indications may be implemented, and how one or more of the time spans during which the DCI indications are applied may be controlled (see e.g. Fig.26 and 27 ),etc.

[0441] In the described variations and embodiments of the TDD communication process, it is assumed that the UE is configured with multiple TDD configurations. This can be implemented, for example, by providing the UE with a cell-common TDD configuration using system information broadcasting and providing the UE with a UE-specific TDD configuration using RRC signaling or DCI signaling.

[0442] In addition, the cell-common TDD configuration may be, for example, the same as the traditional cell-common TDD configuration discussed above in conjunction with the 5G IE tdd-UL-DL-ConfigurationCommon. Additionally or alternatively, the cell-common TDD configuration may be a new configuration to be used in particular in the context of these improved TDD communication procedures. For example, a new RRC information element tdd-UL-DL-ConfigurationCommon-rel18 may be defined, for example, following the structure of the corresponding traditional RRC IE tdd-UL-DL-ConfigurationCommon.

[0443] In addition, the UE-specific TDD configuration may be, for example, the same as the conventional UE-specific TDD configuration discussed above in conjunction with the 5G IE tdd-UL-DL-ConfigurationDedicated. Additionally or alternatively, the UE-specific TDD configuration may be a new configuration specifically for use in the context of these improved TDD communication procedures. For example, a new RRC information element tdd-UL-DL-ConfigurationDedicated-rel18 may be defined, for example, following the structure of the corresponding conventional RRC IE tdd-UL-DL-ConfigurationDedicated.

[0444] As a result, zero or one or more than one of the TDD configurations for the improved TDD communication procedure may be defined based on the new RRC information element.

[0445] The use of new RRC information elements in the context of these improved TDD communication procedures may facilitate increased configuration flexibility, as the gNB is allowed to separately define TDD configurations for those UEs that support the improved TDD communication procedures, while non-supporting UEs may follow other (legacy) TDD configurations defined by the legacy RRC information elements.

[0446] As an example, in combination with Fig.21 In the described solution, the two TDD configurations can reuse the conventional information elements, or use new information elements instead. Fig. 22 In the solution described, one or both of the two cell common TDD configurations can be defined by a new information element. Fig.24 In the described solution, one or both of the two UE-specific TDD configurations may be defined by a new information element.

[0447] As explained above for the improved TDD communication process, the determination of the TDD communication direction inside the SBFD resource can be controlled to be different or the same as outside the SBFD resource. In other words, according to the DCI and / or valid time period mechanism described above, the separate TDD configuration operation for the SBFD resource is disabled or enabled. For example, a DCI with a configuration switching indication enables different SBFD resource-specific operations (following the indicated TDD configuration). Accordingly, the expiration of the valid time period for the subsequent DCI or the initial DCI can disable different SBFD resource-specific operations, so that the determination of the TDD communication direction inside and outside the SBFD resource is the same again.

[0448] Other aspects

[0449] According to a first aspect, a user equipment is provided, comprising the following contents. A receiver of the UE receives a plurality of time division configurations. A circuit of the UE determines a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations in a plurality of time division configurations previously received. The receiver receives information about a full-duplex resource. The receiver receives a downlink control information DCI message including a configuration switching indication. The configuration switching indication indicates a time division configuration to be used in a plurality of time division configurations previously received. The circuit determines a communication direction for each of a plurality of full-duplex time intervals in one or more full-duplex time intervals of the full-duplex resource and correspondingly for a complete full-duplex frequency region of the full-duplex resource based on a second set of one or more time division configurations in a plurality of time division configurations previously received. The second set of time division configurations includes at least the indicated time division configuration.

[0450] According to a second aspect provided in addition to the first aspect, the indicated time division configuration is used to replace a previously used time division configuration in the first set of time division configurations. The second set of time division configurations comprises at least the indicated time division configuration without the previously used time division configuration of the first set of time division configurations.

[0451] According to a third aspect provided in addition to the first or second aspect, the plurality of time division configurations include:

[0452] ◦Cell common time division configuration, and

[0453] ◦UE-specific time division configuration,

[0454] The first set of time division configurations includes one of a cell-common time division configuration and a UE-specific time division configuration. The configuration switching indication of the received DCI message indicates one of the cell-common time division configuration and the UE-specific time division configuration.

[0455] In an optional embodiment, the circuit determines the communication direction of the full-duplex resource based on the indicated cell-common time division configuration or UE-specific time division configuration.

[0456] According to a fourth aspect provided in addition to one of the first to third aspects, the plurality of time division configurations include:

[0457] ◦Multiple cells share common time division configuration.

[0458] The first set of time division configurations includes a first cell-common time division configuration among a plurality of cell-common time division configurations. The configuration switching indication of the received DCI message indicates a second cell-common time division configuration among the plurality of cell-common time division configurations that is different from the first cell-common time division configuration.

[0459] In an optional embodiment, the circuit determines the communication direction of the full-duplex resource based on a second set including the indicated second cell common time division configuration.

[0460] According to a fifth aspect provided in addition to the fourth aspect, the plurality of time division configurations further comprises a UE-specific time division configuration. The first set of time division configurations comprises the UE-specific time division configuration, and the second set comprises the UE-specific time division indication.

[0461] According to a sixth aspect provided in addition to one of the first to fifth aspects, the plurality of time division configurations include:

[0462] ◦Multiple UE-specific time division configurations.

[0463] The first set of time division configurations includes a first UE-specific time division configuration among the multiple UE-specific time division configurations. The configuration switching indication of the received DCI message indicates a second UE-specific time division configuration among the multiple UE-specific time division configurations that is different from the first UE-specific time division configuration.

[0464] In an optional embodiment, the circuit determines the communication direction of the full-duplex resource based on a second set including the indicated second UE-specific time division configuration.

[0465] According to a seventh aspect provided in addition to the sixth aspect, the plurality of time division configurations further comprises a cell-common time division configuration. The first set of time division configurations comprises the cell-common time division configuration, and the second set comprises the cell-common time division indication.

[0466] According to an eighth aspect provided in addition to one of the first to seventh aspects, the DCI message has format 2_0, and a configuration switching indication of the DCI message is included in a field for carrying a time slot format indicator, the time slot format indicator indicating one of a plurality of time slot formats. The value of the configuration switching indication is such that it indicates one of a plurality of time division configurations rather than a time slot format.

[0467] According to a ninth aspect provided in addition to any one of the first to eighth aspects, the determination of the communication direction of the full-duplex resource is performed by the UE based on a configuration switching indication received in a DCI message until:

[0468] o A further DCI message is received, the further DCI message comprising a further configuration switch indication indicating one of the plurality of time division configurations previously received.

[0469] The circuit determines a communication direction for each of the one or more full-duplex time intervals of the full-duplex resource and, accordingly, for the complete full-duplex frequency region of the full-duplex resource based on a third set of one or more time division configurations of the plurality of time division configurations previously received, the third set of time division configurations comprising at least the time division configuration indicated by the further configuration switch indication.

[0470] According to the tenth aspect provided in addition to one of the first to ninth aspects, the determination of the communication direction of the full-duplex resource is performed by the UE based on the configuration switching indication received in the DCI message until:

[0471] o The validity period associated with the configuration switch indication received in the DCI message expires.

[0472] In an optional embodiment, when the validity period associated with the configuration switching indication expires, the circuit determines the communication direction for each of the one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency region of the full-duplex resource based on a third set of one or more time division configurations in the plurality of time division configurations previously received. The third set of time division configurations includes at least a fallback time division configuration instead of the time division configuration indicated by the configuration switching indication.

[0473] In an optional embodiment, the fallback time division configuration is one of a plurality of time division configurations. Further optionally, the fallback time division configuration is the same as or different from a previously used time division configuration in the first set of time division configurations.

[0474] In yet another alternative embodiment, the circuit determines that the valid time period starts at a time associated with a received DCI message including the configuration switch indication, such as at a time slot in which the DCI message is received.

[0475] According to an eleventh aspect provided in addition to the tenth aspect, the circuit determines the valid time period based on one or more of the following:

[0476] a fixed value specified by the UE's firmware,

[0477] a cell common value, which is optionally configured to the UE based on a radio resource control RRC message or based on a system information block SIB message, and

[0478] A UE specific value, which is optionally configured to the UE based on a downlink control information message.

[0479] In an optional implementation, the valid time period starts again when the UE is scheduled for uplink transmission or downlink reception in full-duplex resources.

[0480] According to a twelfth aspect provided in addition to the tenth or eleventh aspect, the circuit operates a timer for a valid time period. The timer is configured with an expiration value corresponding to the valid time period. The timer starts at a time associated with a received DCI message including a configuration switching indication, for example, at a time slot when the DCI message is received.

[0481] In an optional implementation, the timer is reset when the UE is scheduled for uplink transmission or downlink reception in full-duplex resources.

[0482] According to the thirteenth aspect provided in addition to one of the first to twelfth aspects, the determination of the communication direction by the circuit follows a determination rule of how to combine one or more time division configurations in each set of time division configurations. The determination rule to be followed is specified by the decisive time division configuration in the time division configuration of each set. The decisive time division configurations of the first set and the second set are the same or different.

[0483] In an optional embodiment, if the UE-specific time division configuration is in each set of time division configurations to be used by the circuit for determining the communication direction, the deterministic time division configuration is the UE-specific time division configuration. The determination rule associated with the UE-specific time division configuration enables the UE-specific time division configuration to configure a communication direction different from the communication direction configured by the cell-common time division configuration for one or more time intervals in the time interval of the cell-common time division configuration.

[0484] In an alternative embodiment, if there is no UE-specific time division configuration in the respective set of time division configurations to be used by the circuit to determine the communication direction, the decisive time division configuration is the cell-common time division configuration. The determination rule associated with the cell-common time division configuration is based only on the cell-common time division configuration.

[0485] According to a fourteenth aspect provided in addition to one of the first to thirteenth aspects, the information about the full-duplex resource includes information about one or more of the following:

[0486] ◦ one or more full-duplex time periods of the full-duplex resource, and

[0487] ◦ One or more full-duplex frequency regions of the full-duplex resource.

[0488] In an optional embodiment, the information about the full-duplex resources is received in one or more of a system information broadcast and a message of a radio resource control RRC protocol.

[0489] According to the fifteenth aspect provided in addition to one of the first to fourteenth aspects, the time division configuration configures the communication direction as one of an uplink direction or a downlink direction or a flexible direction for each of one or more time intervals of the time division configuration.

[0490] According to a sixteenth aspect provided in addition to one of the first to fifteenth aspects, the receiver and the transmitter perform communication based on the determined communication direction, optionally wherein the communication is performed with a base station serving the UE.

[0491] According to a seventeenth aspect, a method is provided, comprising the following steps performed by a user equipment UE:

[0492] Receive multiple time-division configurations,

[0493] determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of time division configurations previously received,

[0494] Receive information about full-duplex resources,

[0495] receiving a downlink control information (DCI) message including a configuration switch indication, wherein the configuration switch indication indicates a time division configuration to be used among the plurality of previously received time division configurations, and

[0496] For each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, the communication direction is determined based on a second set of one or more time division configurations of the previously received multiple time division configurations, wherein the second set of time division configurations includes at least the indicated time division configuration.

[0497] According to the eighteenth aspect, a base station is provided, comprising the following contents. A transmitter of the base station sends multiple time division configurations. A circuit of the base station determines a communication direction for each time interval in multiple time intervals based on a first set of one or more time division configurations in the multiple time division configurations previously sent. The transmitter sends information about full-duplex resources. The circuit determines a time division configuration to be used for full-duplex resources in the multiple time division configurations previously sent. The transmitter sends a downlink control information DCI message including a configuration switching indication, wherein the configuration switching indication indicates a determined time division configuration. The circuit determines a communication direction for each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and correspondingly for a complete full-duplex frequency region of the full-duplex resource based on a second set of one or more time division configurations in the multiple time division configurations previously sent. The second set of time division configurations includes at least the indicated time division configuration.

[0498] According to a nineteenth aspect, there is provided a method, comprising the following steps performed by a base station:

[0499] Send multiple time-division configurations,

[0500] determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of the plurality of previously transmitted time division configurations,

[0501] Send information about full-duplex resources,

[0502] determining a time division configuration to be used for the full-duplex resource among the plurality of time division configurations previously sent,

[0503] Sending a downlink control information DCI message including a configuration switching indication, wherein the configuration switching indication indicates a determined time division configuration;

[0504] Based on a second set of one or more time division configurations among the multiple time division configurations previously sent, a communication direction is determined for each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

[0505] According to a twentieth aspect, there is provided an integrated circuit controlling a process of a user equipment (UE), the process comprising the following steps performed by the UE:

[0506] Receive multiple time-division configurations,

[0507] determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of time division configurations previously received,

[0508] Receive information about full-duplex resources,

[0509] receiving a downlink control information (DCI) message including a configuration switch indication, wherein the configuration switch indication indicates a time division configuration to be used among the plurality of previously received time division configurations, and

[0510] Based on a second set of one or more time division configurations among the multiple time division configurations previously received, a communication direction is determined for each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

[0511] According to aspect 21, there is provided an integrated circuit controlling a process of a base station, the process comprising the following steps performed by the base station:

[0512] Send multiple time-division configurations,

[0513] determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of the plurality of previously transmitted time division configurations,

[0514] Send information about full-duplex resources,

[0515] determining a time division configuration to be used for the full-duplex resource among the plurality of time division configurations previously sent,

[0516] Sending a downlink control information DCI message including a configuration switching indication, wherein the configuration switching indication indicates a determined time division configuration;

[0517] Based on a second set of one or more time division configurations among the multiple time division configurations previously sent, a communication direction is determined for each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

[0518] Further variations, including hardware and software implementations of the present disclosure

[0519] The present disclosure can be implemented by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each of the above embodiments can be partially or entirely implemented by an LSI such as an integrated circuit, and each process described in each embodiment can be partially or entirely controlled by the same LSI or a combination of LSIs. The LSI can be formed as a chip alone, or a chip can be formed to include a part or all of the functional blocks. The LSI may include data inputs and outputs coupled thereto. According to the difference in integration, the LSI here may be referred to as an IC (integrated circuit), a system LSI, a super LSI, or a super LSI. However, the technology for implementing an integrated circuit is not limited to LSI, and can be implemented by using a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after LSI manufacturing or a reconfigurable processor that can reconfigure the connection and setting of the circuit unit arranged inside the LSI can be used. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI as a result of the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology can be used to integrate functional blocks. Biotechnology can also be applied.

[0520] The present disclosure may be implemented by any kind of device, apparatus, or system having a communication function, which is referred to as a communication device.

[0521] The communication device may include a transceiver and a processing / control circuit. The transceiver may include and / or function as a receiver and a transmitter. As a transmitter and a receiver, the transceiver may include an RF (radio frequency) module and one or more antennas, and the RF module may include an amplifier, an RF modulator / demodulator, etc.

[0522] Some non-limiting examples of such communication devices include phones (e.g., cellular (cell) phones, smart phones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telemedicine / telemedicine (remote health and medicine) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0523] Communication devices are not limited to portable or movable, and may also include any kind of device, equipment, or system that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in a network of the Internet of Things (IoT).

[0524] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

[0525] The communication device may include a device such as a controller or a sensor that is coupled to a communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or a sensor that generates a control signal or a data signal that is used by the communication device that performs the communication functions of the communication device.

[0526] Communications devices may also include infrastructure facilities such as base stations, access points, and any other device, equipment, or system that communicates with or controls devices such as those in the above non-limiting examples.

[0527] (Control signal)

[0528] In the present disclosure, a downlink control signal (information) related to the present disclosure may be a signal (information) transmitted through a PDCCH of a physical layer, or may be a signal (information) transmitted through a MAC control element (CE) or RRC of a higher layer. The downlink control signal may be a predefined signal (information).

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

[0530] (Base Station)

[0531] 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 station unit, or a gateway. In addition, in sidelink communication, a terminal may be used instead of a base station. A base station may be a relay device that relays communication between a higher node and a terminal. A base station may also be a roadside unit.

[0532] (Uplink / Downlink / Sidelink)

[0533] The present disclosure may be applied to any one of an uplink, a downlink, and a sidelink.

[0534] The present disclosure can be applied to, for example, uplink channels (such as PUSCH, PUCCH and PRACH), downlink channels (such as PDSCH, PDCCH and PBCH), and sidelink channels (such as physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH) and physical sidelink broadcast channel (PSBCH)).

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

[0536] (Data channel / Control channel)

[0537] The present disclosure may be applied to any one of a data channel and a control channel. 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.

[0538] (Reference signal)

[0539] In the present 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 sometimes referred to as a pilot signal. The reference signal may be any one 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).

[0540] (Time interval)

[0541] In the present disclosure, the time resource unit is not limited to one or a combination of a time slot and a symbol, and may be a time resource unit such as a frame, a superframe, a subframe, a time slot, a time slot subslot, a mini-slot, or a time resource unit such as a symbol, an orthogonal frequency division multiplexing (OFDM) symbol, a single carrier-frequency division multiplexing access (SC-FDMA) symbol, or other time resource units. The number of symbols included in a time slot is not limited to any number of symbols exemplified in the above (s) embodiment, and may be other numbers of symbols.

[0542] (Frequency band)

[0543] The present disclosure may be applied to any of the licensed and unlicensed frequency bands.

[0544] (communication)

[0545] The present disclosure can be applied to any one of the communication between a base station and a terminal (Uu-link communication), the communication between terminals and terminals (Sidelink communication), and the vehicle-to-everything (V2X) communication. The channels in the present disclosure can be replaced by PSCCH, PSSCH, physical sidelink feedback channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0546] In addition, the present disclosure can also be applied to any network in a terrestrial network or a network other than a terrestrial network using a satellite or a high altitude pseudo satellite (HAPS) (NTN: Non-Terrestrial Network). In addition, the present disclosure can be applied to a network with a large cell size and a terrestrial network with a large delay compared to a symbol length or a time slot length, such as an ultra-wideband transmission network.

[0547] (Antenna port)

[0548] An antenna port refers to a logical antenna (antenna group) formed by one or more physical antennas. That is, an antenna port does not necessarily refer to one physical antenna, but sometimes refers to an array antenna formed by multiple antennas, etc. For example, it is not defined how many physical antennas form an antenna port, but the antenna port is defined as the minimum unit through which the terminal is allowed to send a reference signal. The antenna port can also be defined as the minimum unit for multiplication of precoding vector weights.

[0549] In addition, various embodiments can also be implemented by software modules executed by a processor or directly executed in hardware. Combinations of software modules and hardware implementations are also possible. Software modules can be stored on any kind of computer-readable storage medium, such as RAM, EPROM, EEPROM, flash memory, registers, hard disk, CD-ROM, DVD, etc. It should also be noted that the various features of different embodiments can be the subject of another embodiment alone or in any combination.

[0550] Those skilled in the art will appreciate that many changes and / or modifications may be made to the present disclosure as shown in the specific embodiments. Therefore, the present embodiments are to be considered in all aspects as illustrative and not restrictive.

Claims

1. A user equipment UE, comprising: a receiver that receives a plurality of time division configurations, circuitry that determines a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of time division configurations previously received, The receiver receives information about full-duplex resources, The receiver receives a downlink control information (DCI) message including a configuration switch indication, wherein the configuration switch indication indicates a time division configuration to be used among the plurality of previously received time division configurations, and The circuit determines the communication direction for each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource based on a second set of one or more time division configurations of the multiple time division configurations previously received, wherein the second set of time division configurations includes at least the indicated time division configuration.

2. The UE according to claim 1, wherein: The indicated time division configuration is to be used instead of a previously used time division configuration in the first set of time division configurations, and wherein the second set of time division configurations comprises at least the indicated time division configuration without the previously used time division configuration in the first set of time division configurations.

3. The UE according to claim 1 or 2, wherein: The multiple time division configurations include: ◦Cell common time division configuration, and ◦UE-specific time division configuration, The first set of time division configurations includes one of the cell-common time division configuration and the UE-specific time division configuration, wherein the configuration switching indication of the received DCI message indicates one of the cell-common time division configuration and the UE-specific time division configuration, Optionally, the circuit determines the communication direction of the full-duplex resource based on the indicated cell-common time division configuration or UE-specific time division configuration.

4. The UE according to any one of claims 1 to 3, wherein: The multiple time division configurations include: ◦Multiple cells share time division configuration, and The first set of time division configurations includes the first cell-common time division configuration among the plurality of cell-common time division configurations, The configuration switching indication of the received DCI message indicates a second cell common time division configuration different from the first cell common time division configuration among the multiple cell common time division configurations, Optionally, the communication direction of the full-duplex resource determined by the circuit is based on the second set including the indicated second cell-common time division configuration.

5. The UE according to claim 4, wherein: The multiple time division configurations also include a UE-specific time division configuration, and wherein the first set of time division configurations includes the UE-specific time division configuration, and the second set includes the UE-specific time division indication.

6. The UE according to any one of claims 1 to 5, wherein: The multiple time division configurations include: ◦ Multiple UE-specific time division configurations, and The first set of time division configurations includes a first UE-specific time division configuration among the multiple UE-specific time division configurations, The configuration switching indication of the received DCI message indicates a second UE-specific time division configuration different from the first UE-specific time division configuration among the multiple UE-specific time division configurations, Optionally, the communication direction of the full-duplex resources determined by the circuit is based on the second set including the indicated second UE-specific time division configuration.

7. The UE according to claim 6, wherein: The multiple time division configurations also include a cell-common time division configuration, and wherein the first set of time division configurations includes the cell-common time division configuration, and the second set includes the cell-common time division indication.

8. The UE according to any one of claims 1 to 7, wherein: The DCI message has format 2_0, and the configuration switching indication of the DCI message is included in a field for carrying a time slot format indicator, wherein the time slot format indicator indicates one time slot format among multiple time slot formats, wherein the value of the configuration switching indication is such that it indicates one time division configuration among the multiple time division configurations rather than a time slot format.

9. The UE according to any one of claims 1 to 8, wherein: The UE determines the communication direction of the full-duplex resource based on the configuration switching indication received in the DCI message until: o receiving a further DCI message, the further DCI message comprising a further configuration switch indication indicating one of the plurality of time division configurations previously received, The circuit determines the communication direction for each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource based on a third set of one or more time division configurations of the multiple time division configurations previously received, wherein the third set of time division configurations includes at least the time division configuration indicated by the additional configuration switching indication.

10. The UE according to one of claims 1 to 9, wherein: The UE determines the communication direction of the full-duplex resource based on the configuration switching indication received in the DCI message until: ◦ the validity period associated with the configuration switch indication received in the DCI message expires, Optionally, when the valid time period associated with the configuration switching indication expires, the circuit determines the communication direction for each full-duplex time interval of the one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource based on a third set of one or more time division configurations in the plurality of time division configurations previously received, wherein the third set of time division configurations includes at least a fallback time division configuration without the time division configuration indicated by the configuration switching indication, Optionally, wherein the fallback time division configuration is one of the multiple time division configurations, optionally, wherein the fallback time division configuration is the same as or different from a previously used time division configuration in the first set of time division configurations, Optionally, the circuit determines that the valid time period starts at a time related to a received DCI message including the configuration switch indication, such as starting at a time slot when the DCI message is received.

11. The UE according to claim 10, wherein: The circuit determines the validity period based on one or more of the following: ◦ a fixed value specified by the UE's firmware, ◦ a cell-common value, which is optionally configured to the UE based on a Radio Resource Control (RRC) message or based on a System Information Block (SIB) message, and ◦ A UE specific value, optionally configured to the UE based on a downlink control information message, Optionally, when the UE is scheduled for uplink transmission or downlink reception in full-duplex resources, the valid time period starts again.

12. The UE of claim 10 or 11, wherein the circuit operates a timer for the validity period, wherein the timer is configured with an expiration value corresponding to the validity period, and wherein the timer starts at a time associated with a received DCI message, the DCI message including the configuration switch indication, such as starting at a time slot at which the DCI message is received, Optionally, wherein The timer is reset when the UE is scheduled for uplink transmission or downlink reception in full-duplex resources.

13. The UE according to any one of claims 1 to 12, wherein: the determination of the communication direction by the circuit follows a determination rule of how to combine the one or more time division configurations in respective sets of time division configurations, wherein the determination rule to be followed is specified by a deterministic time division configuration in the time division configurations of the respective sets, and wherein the deterministic time division configurations of the first set and the second set are the same or different, Optionally, if the UE-specific time division configuration is in each set of time division configurations to be used by the circuit to determine the communication direction, the deterministic time division configuration is the UE-specific time division configuration, wherein the determination rule associated with the UE-specific time division configuration causes the UE-specific time division configuration to configure a communication direction different from the communication direction configured by the cell-common time division configuration for one or more time intervals of the time interval of the cell-common time division configuration, Optionally, if there is no UE-specific time division configuration in each set of time division configurations to be used by the circuit to determine the communication direction, the decisive time division configuration is a cell-common time division configuration, wherein the determination rule associated with the cell-common time division configuration is based only on the cell-common time division configuration.

14. The UE according to any one of claims 1 to 13, wherein: The information about the full-duplex resource includes information about one or more of the following: ◦ one or more full-duplex time periods of the full-duplex resource, and ◦ one or more full-duplex frequency regions of the full-duplex resource, Optionally, the information about the full-duplex resource is received in one or more of a system information broadcast and a message of a radio resource control (RRC) protocol.

15. The UE according to any one of claims 1 to 14, wherein: The time division configuration configures the communication direction as one of an uplink direction or a downlink direction or a flexible direction for each of the one or more time intervals of the time division configuration.

16. The UE according to any one of claims 1 to 15, wherein: The receiver and transmitter perform communication based on the determined communication direction, optionally wherein the communication is performed with a base station serving the UE.

17. A method performed by a user equipment UE comprising the following steps: Receive multiple time-division configurations, determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of time division configurations previously received, Receive information about full-duplex resources, receiving a downlink control information DCI message including a configuration switching indication, wherein: The configuration switching indication indicates a time division configuration to be used among the plurality of time division configurations previously received, and Based on a second set of one or more time division configurations among the multiple time division configurations previously received, a communication direction is determined for each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

18. A base station, comprising: A transmitter that transmits multiple time-division configurations, circuitry that determines a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of previously transmitted time division configurations, The transmitter sends information about full-duplex resources, The circuit determines a time division configuration of the plurality of previously transmitted time division configurations to be used for the full-duplex resource, The transmitter sends a downlink control information DCI message including a configuration switching indication, wherein the configuration switching indication indicates a determined time division configuration, and The circuit determines the communication direction for each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource based on a second set of one or more time division configurations of the multiple time division configurations previously sent, wherein the second set of time division configurations includes at least the indicated time division configuration.

19. A method comprising the following steps performed by a base station: Send multiple time-division configurations, determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of previously transmitted time division configurations, Send information about full-duplex resources, determining a time division configuration to be used for the full-duplex resource among the plurality of time division configurations previously sent, Sending a downlink control information DCI message including a configuration switching indication, wherein: The configuration switching indication indicates a determined time-division configuration; Based on a second set of one or more time division configurations among the multiple time division configurations previously sent, a communication direction is determined for each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

20. An integrated circuit controlling a process of a user equipment UE, the process comprising the following steps performed by the UE: Receive multiple time-division configurations, determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of time division configurations previously received, Receive information about full-duplex resources, receiving a downlink control information DCI message including a configuration switching indication, wherein: The configuration switching indication indicates a time division configuration to be used among the plurality of time division configurations previously received, and Based on a second set of one or more time division configurations among the multiple time division configurations previously received, a communication direction is determined for each full-duplex time interval of one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

21. An integrated circuit controlling a process of a base station, the process comprising the following steps performed by the base station: Send multiple time-division configurations, determining a communication direction for each of a plurality of time intervals based on a first set of one or more time division configurations of a plurality of previously transmitted time division configurations, Send information about full-duplex resources, determining a time division configuration to be used for the full-duplex resource among the plurality of time division configurations previously sent, Sending a downlink control information DCI message including a configuration switching indication, wherein: The configuration switching indication indicates a determined time-division configuration; Based on a second set of one or more time division configurations among the multiple time division configurations previously sent, a communication direction is determined for each full-duplex time interval in one or more full-duplex time intervals of the full-duplex resource and correspondingly for the complete full-duplex frequency area of ​​the full-duplex resource, wherein the second set of time division configurations includes at least the indicated time division configuration.

Images