COMMUNICATION DEVICE AND BASE STATION INVOLVED IN UPLINK SETTING - Patent application

Abstract

A communications device, a base station, and a method for the communications device and the base station are provided. The communications device includes a transceiver unit that receives a transmission configuration defining a first time resource for semi-statically configured uplink transmission applicable to an associated resource type and a resource type configuration defining a resource type of a second time resource, and a circuit that determines whether to start or skip the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration. The circuit determines to skip the uplink transmission when the first time resource overlaps with the second time resource and the uplink transmission is not applicable to the resource type of the second time resource, and the transceiver unit, in operation, performs or skips the semi-statically configured uplink transmission according to the result of the determination.

Description

[Technical Field]

[0001] 1.Technical Field FIELD OF THE DISCLOSURE The present disclosure relates to transmitting and receiving signals in a communication system. In particular, the present disclosure relates to methods and apparatus for such transmission and reception. [Background technology]

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

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

[0004] [Non-Patent Document 1] 3GPP TS 38.300 v15.6.0 [Non-patent document 2] 3GPP TS 38.211 [Non-patent document 3] ITU-R M.2083 [Non-patent document 4] TR 38.913 [Non-Patent Document 5] TS 23.501 [Non-patent document 6] 3GPP TSG RAN#94-e, RP-213591, “New SI: Study on evolution of NR duplex operation” Summary of the Invention [Problem to be solved by the invention]

[0005] One non-limiting exemplary embodiment facilitates efficient interference reporting and interfering cell management. [Means for solving the problem]

[0006] In one embodiment, the technique of the present disclosure features a communications device comprising: a transceiver unit that, in operation, receives a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmission applicable to an associated resource type; and a resource type configuration defining a resource type of a second time resource; and a circuit that determines whether to start or skip execution of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, wherein if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, the circuit determines to skip the semi-statically configured uplink transmission in the first time resource, and the transceiver unit executes or skips the semi-statically configured uplink transmission according to the result of the determination.

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

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

[0009] Exemplary embodiments will now be described in more detail with reference to the accompanying drawings. [Brief explanation of the drawings]

[0010] [Figure 1] 1 illustrates an example architecture of a 3GPP NR system; [Figure 2] Schematic diagram showing the functional division between NG-RAN and 5GC [Figure 3] Sequence diagram of RRC connection setup / reconfiguration procedure [Figure 4] Schematic diagram showing usage scenarios for high-speed, large-capacity (eMBB: enhanced Mobile Broadband), multiple simultaneous connections (mMTC: massive Machine Type Communications), and ultra-reliable and low latency (URLLC: Ultra Reliable and Low Latency Communications) [Figure 5] Block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario [Figure 6A] Schematic diagram showing non-overlapping full-duplex subbands from the gNB perspective [Figure 6B] Schematic diagram showing non-overlapping full duplex subbands from the user equipment (UE) perspective [Figure 7] Schematic diagram showing potential overlap of CG PUSCH and downlink transmission in non-overlapping full-duplex operation of subbands [Figure 8] Block diagram showing a base station and a communication device [Figure 9] Block diagram showing a configured uplink transmission decision circuit [Figure 10]1 is a flowchart illustrating steps of a communication method for a communication device; [Figure 11] 1 is a flowchart illustrating steps of a communication method for a base station. [Figure 12] CG PUSCH setting and symbol type correspondence diagram [Figure 13] 1 is a flowchart illustrating steps of a communication method for a communication device; [Figure 14] 1 is a flowchart illustrating steps of a communication method for a base station. [Figure 15] Schematic diagram illustrating decisions regarding CG PUSCH transmission in response to receiving a dynamic slot format indicator. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] In particular, the overall system architecture assumes an NG-RAN (Next Generation Radio Access Network) with gNBs, which terminate NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) protocols and control plane (RRC: Radio Resource Control) protocols. The gNBs are interconnected with each other via an Xn interface. The gNBs are also connected to an NGC (Next Generation Core) via a Next Generation (NG) interface, more specifically to an AMF (Access and Mobility Management Function) (e.g., a specific core entity that runs the AMF) via an NG-C interface, and to a UPF (User Plane Function) (e.g., a specific core entity that runs the UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 1 (see, for example, Section 4 of Non-Patent Document 1).

[0013] The user plane protocol stack in NR (see, for example, Section 4.4.1 of Non-Patent Document 1) includes a PDCP (Packet Data Convergence Protocol) sublayer, an RLC (Radio Link Control) sublayer, and a MAC (Medium Access Control) sublayer, which are terminated at the gNB on the network side. In addition, a new access stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced above PDCP (see, for example, Section 6.5 of Non-Patent Document 1). NR also defines a control plane protocol stack (see, for example, Section 4.4.2 of Non-Patent Document 1). An overview of Layer 2 functions is provided in Section 6 of Non-Patent Document 1. The functions of the PDCP, RLC, and MAC sublayers are respectively described in Sections 6.4, 6.3, and 6.2 of 3GPP TS 26.10. The functions of the RRC layer are described in Section 7 of 3GPP TS 26.10.

[0014] For example, the Medium-Access-Control (MAC) layer handles scheduling and scheduling-related functions, including multiplexing logical channels and handling various numerologies.

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

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

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

[0018] In the new wireless system 5G-NR, for each numerology and carrier, a resource grid of subcarriers and OFDM symbols is defined for both the uplink and the downlink. Each element within the resource grid is called a resource element and is identified based on the frequency index in the frequency domain and the symbol position in the time domain (see Version 15.6.0 of Non-Patent Document 2).

[0019] In NR, a resource block (RB) is defined as 12 consecutive subcarriers in the frequency domain. Resource blocks are numbered from zero in the frequency domain as common resource blocks for subcarrier spacing settings. A physical resource block (PRB) is defined within a bandwidth part (a subset of consecutive common resource blocks) and is numbered for each bandwidth part.

[0020] <Split of 5G NR Functions between NG-RAN and 5GC> Figure 2 shows the split of functions between NG-RAN and 5GC. The logical nodes of NG-RAN are gNB or ng-eNB (next generation eNB). The logical nodes of 5GC are AMF, UPF, and SMF.

[0021] In particular, gNB and ng-eNB handle the following main functions. - Functions of radio resource management such as radio bearer control, radio admission control, connection mobility control, and dynamic resource allocation (scheduling) to the UE in both the uplink and downlink directions - IP header compression, encryption, and integrity protection of data - Selection of AMF at UE attachment when the routing to AMF cannot be determined from the information provided by the UE - Routing of user plane data to UPF - Routing control plane information to AMF - Establishing and releasing connections - Scheduling and sending paging messages - System broadcast information (sent from AMF or OAM) (scheduling and transmission) - Configuring measurements and measurement reporting for mobility and scheduling - Transport-level packet marking in the uplink - Session Management - Network slicing support - QoS flow management and mapping to data radio bearers - Support for UEs in RRC_INACTIVE state - Non-access stratum (NAS) message delivery function - Wireless Access Network Sharing - Dual Connectivity - Tight interworking between NR and E-UTRA

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

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

[0024] Finally, the Session Management Function (SMF) handles the following major functions: - Session Management - UE IP address allocation and management - UP function selection and control - Configuration of traffic steering in the user plane function (UPF) for routing traffic to the correct destination - Policy enforcement and QoS control part - Downlink data notification

[0025] <Procedures for establishment and reconfiguration of RRC connection> Figure 3 shows the interaction among the UE, gNB, and AMF (5GC entity) in the NAS part when the UE transitions from RRC_IDLE to RRC_CONNECTED (see Non-Patent Document 1).

[0026] RRC is the upper layer signaling (protocol) used for the configuration of the UE and gNB. In particular, in this transition, the AMF creates UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB by means of an INITIAL CONTEXT SETUP REQUEST (Initial Context Setup Request). Next, the gNB activates the AS security with the UE, which is executed by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. After that, the gNB executes reconfiguration to establish signaling radio bearer 2 (SRB2) and data radio bearer (DRB: Data Radio Bearer), which is by the gNB sending an RRCReconfiguration message to the UE and the gNB receiving RRCReconfigurationComplete from the UE in response. In the case of a signaling-only connection, SRB2 and DRB are not established, so these steps related to RRCReconfiguration are skipped. Finally, the gNB notifies the AMF by means of an INITIAL CONTEXT SETUP RESPONSE (Initial Context Setup Response) that the establishment procedure has completed.

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

[0028] <IMT usage scenarios after 2020> Figure 4 shows some use cases for 5G NR. The 3GPP NR (3rd Generation Partnership Project New Radio) is considering three use cases envisioned for IMT-2020 to support a wide variety of services and applications. Phase 1 specifications for enhanced mobile broadband (eMBB) have been finalized. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to further extending eMBB support. Figure 4 shows some examples of IMT usage scenarios envisioned for 2020 and beyond (see, for example, Figure 2 in Non-Patent Document 3).

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

[0030] From a physical layer perspective, there are several possible ways to improve reliability. The current scope for improving reliability includes defining a separate CQI table for URLLC, a more compact Downlink Control Information (DCI) format, PDCCH repetition, etc. However, as NR becomes more stable and more developed (a key requirement for NR URLLC), the scope for achieving ultra-high reliability may expand. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

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

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

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

[0034] For NR URLLC, further use cases with more stringent requirements have been identified, e.g., in factory automation, the transport industry, and power supply. These more stringent requirements include higher reliability (up to 10 times faster) depending on the use case. -6 level), higher availability, packet size up to 256 bytes, time synchronization on the order of a few microseconds (values range from 1 to a few microseconds depending on the frequency range), and short latency on the order of 0.5 to 1 ms (target latency for the user plane in particular is 0.5 ms).

[0035] Furthermore, for NR URLLC, several technology enhancements are possible from the perspective of the physical layer. In particular, enhancements related to the PDCCH (Physical Downlink Control Channel) include compact DCI, PDCCH repetition, and increased PDCCH monitoring. Also, enhancements related to the UCI (Uplink Control Information) include HARQ (Hybrid Automatic Repeat Request) enhancements and CSI feedback enhancements. Also, PUSCH enhancements related to minislot-level hopping and retransmission / repetition are recognized. The term "minislot" refers to a transmission time interval (TTI) that contains fewer symbols than a slot (e.g., a slot contains 14 symbols).

[0036] In slot-based scheduling or allocation, a slot corresponds to the granularity of timing for scheduling allocation (corresponding to the Transmission Time Interval (TTI)). Generally, the TTI determines the granularity of the timing of scheduling allocation. One TTI is the time interval during which a given signal is mapped to the physical layer. For example, conventionally, the length of the TTI can vary from 14 symbols (slot-based scheduling) to 2 symbols (non-slot-based scheduling). Downlink (DL) and uplink (UL) transmissions are defined to be organized into a frame (10 ms in duration) composed of 10 subframes (each 1 ms in duration). In slot-based transmission, a subframe is further divided into slots, and the number of slots is defined by the numerology / subcarrier spacing. The defined values range from 10 slots per frame (1 slot per subframe) when the subcarrier spacing is 15 kHz to 80 slots per frame (8 slots per subframe) when the subcarrier spacing is 120 kHz. The number of OFDM symbols per slot is 14 with a normal cyclic prefix and 12 with an extended cyclic prefix (see Sections 4.1 ("General Frame Structure"), 4.2 ("Numerology"), 4.3.1 ("Frames and Subframes"), and 4.3.2 ("Slots") of V15.3.0 "Physical Channels and Modulation" in September 2018 of Non-Patent Document 2). However, the allocation of time resources for transmission can also be non-slot-based. In particular, the TTI in non-slot-based allocation may correspond to a mini-slot rather than a slot. That is, one or more mini-slots may be allocated for the required transmission of data / control signaling. In non-slot-based allocation, the minimum length of the TTI may be, for example, one or two OFDM symbols.

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

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

[0039] Figure 5 shows the 5G NR non-roaming reference architecture (see Section 4.23 of Non-Patent Document 5). Application Functions (AFs) (e.g., external application servers handling 5G services as exemplified in Figure 4) interact with the 3GPP Core Network to provide services. For example, they support application influence on traffic routing, access Network Exposure Functions (NEFs), or interact with a policy framework (see Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on the operator's deployment, application functions (AFs) deemed trusted by the operator can be allowed to directly interact with the relevant Network Functions. Application Functions (AFs) not permitted by the operator to directly access network functions interact with the relevant Network Functions using an external exposure framework via the NEF.

[0040] Figure 5 shows further functional units of the 5G architecture: Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN) (e.g., operator services, internet access, or third-party services). All or part of the core network functions and application services may be located and run in a cloud computing environment.

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

[0042] <Full duplex with non-overlapping subbands> In time division duplex (TDD) operation, time domain resources are divided between the downlink and uplink. The limited time allocation for the uplink in TDD can result in reduced coverage, increased delay, and reduced capacity. For this reason, full duplex, such as subband-non-overlapping full duplex (SBFD), is being considered for NR (see Non-Patent Document 6).

[0043] Methods for enabling SBFD within the TDD band are being explored. SBFD provides for the simultaneous presence of downlink and uplink within the TDD band by dividing or separating different transmission directions using sub-bands within the TDD band. For example, uplink and downlink transmissions are processed simultaneously by the base station. An example of SBFD operation is shown in Figure 6A (a) from the perspective of the base station (gNB) and in Figure 6B (b) from the perspective of the user equipment (UE).

[0044] For illustrative purposes, Figure 6 and further figures of this disclosure illustrate an example in which resource allocation for uplink and downlink is performed at the slot level in the time domain. However, this disclosure is also applicable to scenarios in which the time domain granularity level for allocating uplink and downlink (or flexible) resources is different from the slot level. For example, a slot format may provide for allocation of symbols within a slot as uplink, downlink, or flexible.

[0045] <Configured Grant (CG: Configured Grant) PUSCH> Uplink transmissions on PUSCH can be scheduled by dynamic grant (e.g., using Downlink Control Information (DCI)) or without dynamic grant. A PUSCH without dynamic grant is called a Configured Grant (CG) PUSCH. A CG PUSCH is semi-statically configured, for example by RRC, and includes the following types:

[0046] For a Type-1 CG PUSCH, all transmission parameters, including time and frequency resource allocation, are configured by the RRC for a given BWP. For example, the time resource allocation may include the slot and the period of the symbol number within the slot. For a Type-2 CG PUSCH, the transmission period is provided by the RRC configuration, and a DCI is used to enable and disable the transmission. Although the time and frequency resource allocation is dynamically signaled by the enable DCI, the same resource allocation may be used for all PUSCH instances of the configured period, for example, until the Type-2 CG PUSCH is disabled or released by another DCI.

[0047] In both Type 1 and Type 2 CG PUSCH, the time-frequency resource allocation has a quasi-static nature in contrast to the dynamic nature of PUSCH scheduled by dynamic grant.

[0048] <Slot format> In NR operation, including Releases 15-17 (Rel-15 / 16 / 17), a gNB informs a UE of its transmission direction via a slot format. Slot formats include downlink (D, DL), uplink (U, UL), and flexible (F) symbols. The slot format, which indicates each symbol in the slot as U, D, or F, can be configured semi-statically by RRC signaling or dynamically by DCI. Semi-static configuration may involve cell-level common signaling or UE-specific RRC signaling. The slot format in cell-level common signaling is provided by the information element tdd-UL-DL-ConfigurationCommon and may be broadcast, for example, by SIB1 (System Information Block 1). In UE-specific signaling, the slot format may be signaled using the information element tdd-UL-DL-ConfigurationDedicated. Dynamic configuration of slot formats is provided within the DCI using a slot format indicator (SFI), such as the SlotFormatIndicator field transmitted in DCI format 2_0. The SFI provides a pointer to a specific slot format combination derived from a standardized slot format. Furthermore, standardized slot format 255 is used to signal that the uplink / downlink / flexible transmission pattern is not determined by the dynamically signaled slot format combination. For example, if the SFI indicates standardized slot format 255, the UE may determine the slot format of the slot based on tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0049] When configuring slot formats according to the NR Release 15-17 specifications, the following rules should be observed:

[0050] ● The semi-static cell-wide D and U symbols cannot be changed by UE-specific RRC or dynamic configuration (SFI in DCI format 2_0).

[0051] ● Only semi-static cell-wide F symbols can be overwritten to D or U by UE-specific RRC.

[0052] ● If a semi-static cell-common F symbol is not overwritten to D or U by the UE-dedicated RRC, it remains a semi-static F and can be further signaled as dynamic D, dynamic U or dynamic F by the SFI in DCI format 2_0.

[0053] When a gNB operates in SBFD operation, the available UL frequency resources and interference situation differ between UL symbols or UL slots (e.g., "normal" UL symbols or UL slots, which are uplink resources across the entire band) and SBFD symbols or SBFD slots (subbands within a frequency band are used to separate DL and UL transmission directions).

[0054] For CG PUSCH resource allocation, the allocated time resources may overlap in time with UL resources in some instances and with SBFD resources in other instances. These two cases are illustrated in Figure 7. If a CG PUSCH allocation overlaps with an SBFD slot or SBFD symbol (e.g., if the frequency resources of the CG PUSCH and DL transmissions overlap (see slots #3 and #4 in the example of Figure 7)), that resource allocation may degrade the performance of and have an interference impact on DL transmissions assigned to one of the subbands of the same symbol or slot.

[0055] In this disclosure, "SBFD symbol" refers to a symbol having subbands that a gNB may use for SBFD operations, and "normal UL symbol" or "UL symbol" refers to a symbol used for UL in conventional NR (Rel-15 / 16 / 17) that does not involve subband splitting. SBFD and normal UL symbols are defined from the perspective of the gNB, but the UE may or may not be aware of the gNB's intended usage. Corresponding definitions also apply to SBFD and ("normal") UL slots, or more generally, time resources.

[0056] Considering the above-mentioned interference and performance degradation issues, if a gNB manipulates SBFD symbols quasi-statically, it is possible in principle to configure the CG PUSCH in a way that aligns the time resources (e.g., periodicity and symbol offset) with either the UL symbols or the SBFD symbols. However, such alignment is an additional constraint on the CG PUSCH configuration that the gNB needs to pay attention to, increasing the complexity of resource allocation. Furthermore, if the SBFD time pattern changes, the CG PUSCH needs to be reconfigured for the new alignment, which increases signaling overhead.

[0057] In light of the above, the approach of the present disclosure is to introduce an association between a CG PUSCH configuration and an applicable symbol type, so that the UE skips (does not transmit) a CG PUSCH instance if the CG PUSCH instance does not overlap or match the applicable symbol type. For some embodiments, different examples of "symbol type" are provided.

[0058] As shown in FIG. 8, a communication device 860 is provided that includes a transceiver 870 and circuitry 880 .

[0059] The transceiver 870 receives a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission, where the uplink transmission is configured to be applicable to an associated resource type. The transceiver 870 further receives a resource type configuration defining a resource type of a second time resource.

[0060] In operation, the circuit 880 determines whether to start or skip a semi-statically configured uplink transmission in a first time resource based on the received transmission configuration and resource type configuration, and determines to skip the semi-statically configured uplink transmission in the first time resource if the first time resource overlaps with a second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource.

[0061] According to the result of the determination, in operation, the transceiver unit 870 performs or skips the semi-statically configured uplink transmission in the first time resource according to the result of the determination.

[0062] For example, the communication device 860 may be a communication apparatus, such as a user equipment (UE), a user device, or a terminal / apparatus.

[0063] The circuitry 880 of the UE may include a configured uplink transmission decision circuit 885. As shown in FIG. 9 , the configured uplink transmission decision circuit 885 illustratively includes a configuration evaluation circuit 986 that evaluates the received transmission configuration and resource type configuration during operation, and a transmission start or skip decision circuit 987 that determines, according to the evaluation, whether to control the transceiver unit 870 to start or skip execution of the semi-statically configured uplink transmission.

[0064] Further provided is a base station 810, also shown in Figure 8. The base station includes a transceiver 820 and a circuit 830.

[0065] In operation, the transceiver 820 generates a transmission configuration defining a first time resource allocated for uplink transmission that is applicable to an associated resource type, and the circuit 830 further generates a resource type configuration defining a resource type of a second time resource.

[0066] In operation, based on the transmission configuration and the resource type configuration, the circuit 830 determines whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource, and determines that if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, reception of the semi-statically configured uplink transmission in the first time resource is skipped. In operation, the transceiver unit 820 performs or skips reception of the semi-statically configured uplink transmission according to the result of the determination.

[0067] The base station 810 may be a scheduling entity or scheduling node such as a gNB.

[0068] For example, the base station circuitry 830 includes a configured uplink transmission decision circuitry 835 .

[0069] To distinguish between the circuits and transceivers of the communication device (UE) 860 and the base station 810, the terms "UE circuitry / transceiver and gNB circuitry / transceiver, respectively" are used.

[0070] 8, the base station 810 and the communication device 860 communicate (transmit and receive) over a communication channel, such as a wireless channel, via transceivers 820 and 870. For example, in the transceiver operations performed by the base station 810 and the communication device 860 described above, the base station 810 transmits to and receives from the communication device 860, and vice versa.

[0071] As described herein, the transceivers 820 and 870 of the gNB and UE transmit and receive data, such as the configuration and uplink transmissions described above, or other data as described below. For example, the transceivers transmit and receive signals carrying the respective data. Circuits 830 and 880 control the respective transceivers 820 or 870 to perform the corresponding transmission or reception of data.

[0072] As shown in FIG. 10 , the corresponding communication method is a communication method performed by a communication device 860 including method steps performed by the communication device, such as a UE. In step S1010, the UE receives a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type. In step S1020, the UE receives a resource type configuration defining a resource type of a second time resource. For example, the transmission configuration and the resource type configuration are received from a base station. Based on the transmission configuration and the resource type configuration, in step S1030, the UE determines whether to start or skip the execution of the semi-statically configured uplink transmission in the first time resource. In the determination step S1030, if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined that the semi-statically configured uplink transmission in the first time resource is to be skipped. The UE performs (S1040-2) or skips (S1040-1) the semi-statically configured uplink transmission in the first time resource according to the result of the determination.

[0073] Further, as shown in FIG. 11, a communication method is provided that includes steps performed by a base station 810.

[0074] In step S1110, the base station generates a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmission applicable to the associated resource type, and transmits the transmission configuration in step S1120.

[0075] In step S1130, the base station generates a resource type configuration that defines a resource type of the second time resource, and transmits the resource type configuration in step S1140.

[0076] Further, in this method, the base station determines whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource in step S1150, where if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it determines that reception of the semi-statically configured uplink transmission in the first time resource is skipped.

[0077] The method for the base station further includes step S1160-2 of performing or skipping step S1160-1 receiving the semi-statically configured uplink transmission according to a result of the determination.

[0078] It should be noted that the present disclosure is not limited to the order of the method steps described above or the order shown in Figures 10 and 11. For example, in the UE method, the order of receiving the transmission configuration and resource type configuration, steps S1010 and S1020, may be swapped. Accordingly, in the base station method, steps S1130 and S1140 of generating and transmitting the resource type configuration may be performed before steps S1110 and S1120 of generating and transmitting the quasi-static uplink transmission configuration.

[0079] As described above, the base station 810 and the communication device 860 communicate with each other via a communication channel. Therefore, each transmission operation disclosed on the side of one entity (communication device or base station) implies a corresponding reception operation on the other side. Furthermore, details of each operation described with respect to the device imply a corresponding method step in a method corresponding to the device.

[0080] As described above, the transmission configuration and resource type configuration are received by the communications device 860 from the base station 810 .

[0081] The transmission configuration is received via semi-static signaling, such as RRC signaling, and configures a semi-statically configured uplink transmission (e.g., a transmission not configured by a dynamic grant). The semi-statically configured uplink transmission is the above-mentioned CG PUSCH, such as, but not limited to, the above-mentioned Type 1 and Type 2 CG PUSCH. The semi-static configuration configures frequency and time resources for the semi-statically configured uplink transmission (for Type 2 CG PUSCH, as described above, frequency resources are assigned by DCI, but the same frequency resources are used for all CG PUSCH instances until the CG PUSCH is disabled by another DCI). The frequency resources may be located within, for example, a bandwidth portion or a subband of a band. The time resources may include a slot period, a slot offset, and a symbol number. In this disclosure, a time resource configured or signaled by the semi-static transmission configuration is referred to as a “first” time resource or a first time resource.

[0082] The resource type configuration may include semi-statically configured (e.g., by RRC). However, the resource type configuration can also be dynamically configured via DCI. The resource type configuration configures the time pattern in which resource types are signaled for each of the available time resources (e.g., slots, symbols). A time resource is associated with each resource type and divides the available resources into time resources that allow SBFD operation and time resources that allow uplink operation but do not allow SBFD operation.

[0083] In this disclosure, the time resources configured by the resource type configuration are referred to as "second" time resources. The resource type configuration may be configured independently of the semi-static uplink transmission configuration, e.g., have a different periodicity. As another example, when configuring the resource type of the second time resource, the base station need not be aware of or care about the resources allocated for the semi-statically configured uplink transmission. Furthermore, it is possible to semi-statically configure uplink transmissions such as CG PUSCH without knowledge of or ignoring the time pattern of the resource types or the resource type configuration. Thus, the second time resources may include time resources that overlap with the first time resources allocated for the semi-static uplink transmission and may include time resources that do not overlap with the first time resources.

[0084] Nevertheless, a resource type configuration may be generated and the time pattern indicated therein may be determined based on the allocation of resources in the semi-static transmission configuration, or the transmission configuration may be generated based on the resource type configuration and the time pattern indicated in the resource type configuration.

[0085] As described above, the base station 810 and the communication device 860 determine whether the communication device 860 should start performing or skip the semi-statically configured uplink transmission. If it is determined that the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined that the semi-statically configured uplink transmission is to be skipped.

[0086] If it is determined that the first time resource overlaps with the second time resource and the semi-statically configured time resource is applicable to the resource type of the second time resource, the circuit 880 determines to start performing the semi-statically configured uplink transmission in the first time resource, and the communications device 860 starts performing the semi-statically configured uplink transmission. Here, the "start" of the transmission (reception at the base station side) may further include further determinations or tests, such as checking whether there is a dynamically allowed transmission (e.g., downlink transmission) assigned to the second time resource. Thus, "performing the transmission of the semi-statically configured uplink resource according to the result of the determination" may include further conditions subject to which the performance of the uplink transmission is subject.

[0087] The following describes an example of how a UE can determine the resource type associated with an uplink transmission and whether semi-statically configured transmissions are applicable to a given resource type.

[0088] One possibility is when a UE is configured with a first transmission configuration and a second transmission configuration. In such a case, the transceiver 870 may receive a first transmission configuration that defines as an associated resource type a first time resource allocated for a first semi-statically configured uplink transmission that is applicable to a first resource type, and a second transmission configuration that defines as an associated resource type a third time resource allocated for a second semi-statically configured uplink transmission that is applicable to a second resource type, where the first semi-statically configured uplink transmission is not applicable to the second resource type.

[0089] Similar to the first quasi-statically configured uplink transmission assigned to the first time resource, the circuits 880 and 830 determine whether to start or skip the execution of the second quasi-statically configured uplink transmission in the third time resource, and the transceiver unit 870 executes or skips the second quasi-statically configured transmission in the third time resource according to the result of the determination.

[0090] As described above, the first uplink transmission and the second uplink transmission may be semi-statically configured, where the first uplink transmission is applicable to a first resource type, the second uplink transmission is applicable to a second resource type, and the first semi-statically configured uplink transmission is not applicable to the second resource type. In this case, the second semi-statically configured uplink transmission may or may not be applicable to the first resource type.

[0091] Note that the terms "first" and "second" resource type are used interchangeably to refer to either a resource type that allows SBFD or another resource type that does not allow SBFD. Thus, a "first" resource type may refer to a resource type that allows SBFD or a resource type that does not allow SBFD. Similarly, the term "second resource type" may refer to either type and is used to describe scenarios that distinguish between a first resource type and a second resource type.

[0092] The resource types applicable to semi-statically configured uplink transmissions may be either (i) resource types that allow sub-band duplexing (e.g., SBFD) or (ii) resource types that prohibit sub-band duplexing.

[0093] For example, during operation, the gNB circuitry 830 determines that the UE 860 is to skip semi-statically configured uplink transmissions in the first time resource when allocating or reserving the first time resource for subband duplex operation, e.g., the semi-statically configured uplink transmissions are configured to be applicable to resource types that prohibit subband duplexing but not to resource types that allow subband duplexing.

[0094] For example, the first resource type may be a resource type that allows subband duplexing and the second resource type may be a resource type that prohibits subband duplexing, or the first resource type may be a resource type that prohibits subband duplexing and the second resource type may be a resource type that allows subband duplexing.

[0095] Applicability information may be signaled from the base station to the UE to enable the UE to determine whether a semi-statically configured uplink transmission is applicable to a resource type or to enable the UE to determine the corresponding resource type.

[0096] The transceiver 870 may receive applicability information indicating whether the semi-statically configured uplink transmission is applicable to a resource type of the second time resource.

[0097] One possibility is to provide the applicability information in the form of a resource type indicator. For example, the transmission configuration may include a resource type indicator (or, simply, a "type indicator") that indicates the associated resource type. The resource type indicator may be a label or tag that is added to or included in the semi-statically configured uplink configuration. The resource type indicator may indicate a first resource type or a second resource type.

[0098] Instead of a resource type indicator in the uplink transmission configuration, the UE may know the resource types applicable to the semi-statically configured uplink transmission from the configuration type of the uplink configuration and specific rules specified in the standard, for example, the standard may specify that a specific type of uplink configuration is applicable to a specific resource type.

[0099] <Full-duplex resources and uplink resources> An example will now be described with reference to Figure 12, in which a time pattern of resource types is configured and a resource type indicator is provided in the quasi-static uplink transmission configuration. In this example, the applicable resource types of the time resources are either (i) full-duplex (e.g., SBFD) resources and (ii) uplink resources that prohibit full-duplex (or "non-full-duplex uplink resources").

[0100] As shown, as an example of resource type configuration, a time pattern of SBFD time resources is configured in the UE. This configuration can be performed semi-statically via RRC or dynamically via DCI. The time pattern of the resource type configuration determines which time resources (e.g., consecutive slots or symbols within a slot) are SBFD time resources. Although slots are shown as time resources in FIG. 12, the time pattern configuration can be performed at other time units, such as the slot level, symbol level, a combination of both, or minislots. For example, in FIG. 12, the time pattern configures slots #1, #2, #3, and #4 as SBFD time resources. Other uplink resources outside this SBFD time pattern (slots #2 and #5 in this example) are considered "normal" uplink time resources that do not allow full duplex. Although SBFD time resources include subbands available for different transmission directions (UL, DL), it is not necessary for the gNB to always operate in full duplex mode on SBFD time resources. For example, a gNB may schedule UL transmissions in UL subbands and leave DL subbands unused in SBFD time resources.

[0101] In the CG PUSCH configuration, as an example of a quasi-statically configured transmission configuration, there is a type indicator (or label or tag) that indicates whether this CG PUSCH is applicable to SBFD symbol / time resources (top of Figure 12) or "normal" non-full duplex symbol / time resources (center of Figure 12). If no applicable symbol type or resource type is indicated in the CG PUSCH configuration, the configuration may apply to both types (bottom of Figure 12).

[0102] As an example, the following parameters may be included in the CG PUSCH configuration as type indicators: Cg-PUSCH-resourceType ENUMERATED {SBFD, non-SBFD}

[0103] Exemplary method steps of a UE method in which the resource type configuration includes an SBFD time pattern are shown in FIG. 13. In step S1310, the UE is configured with a time pattern of SBFD symbols as the resource type configuration. In step S1320, the UE is configured with a CG PUSCH configuration that includes an indication of applicable symbol types (e.g., SBFD symbols). Step S1310 corresponds to step S1020 of receiving the resource type configuration, and step S1320 corresponds to step S1010 of receiving the uplink transmission configuration. As noted above, these time orders may be reversed. In step S1335 (as part of the determination from step S1030), the UE checks whether a CG PUSCH instance overlaps with an SBFD symbol (or multiple SBFD symbols). If "No," the UE does not transmit a CG PUSCH at the time instance that overlaps with an SBFD symbol (step S1341). If yes, the UE may begin uplink transmission, which may include further tests, such as checking further rules to determine whether to transmit a CG PUSCH at that instance (step 1342). For example, if the UE has received another DCI for scheduling DL reception at the symbol, the UE will not transmit a CG PUSCH.

[0104] The corresponding method steps of the gNB are shown in FIG. 14. In step S1410, the gNB notifies the UE of the time pattern of the SBFD symbols in the resource type configuration. In step S1430, the gNB provides the UE with a CG PUSCH configuration including an indication of the applicable symbol type (e.g., SBFD symbol) as a semi-static transmission configuration. In step S1435, the gNB determines whether the CG PUSCH instance overlaps with the SBFD symbol. If no, the gNB does not expect to receive a CG PUSCH from the UE in that instance (step S1451). If yes, the gNB may prepare to receive a CG PUSCH transmission. In doing so, it may check further rules to determine whether to expect a CG PUSCH in that instance (step 1452). For example, if the gNB transmits another DCI for scheduling DL reception in the symbol, the gNB does not expect to receive a CG PUSCH from the UE.

[0105] 13 and 14 show an example in which the resource type applicable to CG PUSCH transmission is SBFD (full duplex). However, the method steps shown in Figures 13 and 14 can also be performed for "uplink" (which does not allow SBFD) as the applicable resource (e.g., symbol) type. In this case, "SBFD symbols" in steps S1320 and S1335 of Figure 13 and steps S1420 and S1435 of Figure 14 can be replaced with "uplink symbols" in steps S1320 and S1335, respectively.

[0106] In the above example, the type indicator indicates whether the semi-statically configured transmission is (i) full duplex or (ii) uplink prohibiting full duplex time resources, and the resource type configuration includes the time pattern of the full duplex time resources. However, as further explained in the following example, other information can be used to indicate the applicability of time resources to a particular resource type for uplink transmission.

[0107] <Conflicting and non-conflicting resources> The following describes an approach of the present disclosure in which the UE does not need to know the explicit definitions of "SBFD symbol" or "full-duplex time resource" and "uplink symbol." Instead, the UE is configured with first and second semi-static slot formats. For example, in an NR system, the second semi-static slot format may be provided as an additional semi-static slot format (e.g., "Rel-18 slot format") to the "legacy" cell-common slot format used in Rel-15 / 16 / 17.

[0108] In some embodiments of the present disclosure, the resource type configuration includes a first slot format and a second slot format, each of which designates the second time resource (or multiple resources, such as symbols in a slot) as an uplink resource, a downlink resource, or a flexible resource (U, D, or F). The resource type to which the semi-statically configured uplink transmission in the first time resource is applicable is one of the following:

[0109] i) conflicting resource types (e.g., conflicting symbol directions (e.g., D→U and D→F) between the first "legacy" quasi-static and the new Rel-18 quasi-static slot formats), where the first slot format indicates the second time resource as a downlink resource and the second slot format indicates the second time resource as an uplink resource or a flexible resource; and ii) A non-colliding resource type (e.g., non-colliding symbol directions (e.g., U→U, F→U, and F→F) between the above-mentioned first and second quasi-static slot formats) in which the first slot format indicates the second time resource as a flexible resource or the respective notifications of the second time resource in the first slot format and the second slot format are the same.

[0110] Therefore, the UE may receive a combination of the two semi-static slot formats shown in Table 1 below. [Table 1]

[0111] Similar to the full-duplex and non-full-duplex uplink symbol type approach described above, a type indicator (e.g., label or tag) or resource type indicator may be provided in the semi-static transmission (e.g., CG PUSCH configuration) to signal the applicable symbol type or resource type (e.g., whether the CG PUSCH or other semi-statically configured transmission is applicable to collisional or non-colliding symbols). If no type indicator is provided in the transmission configuration, the UE (e.g., using the UE circuitry 880) may determine that the semi-statically configured uplink transmission is applicable to both types (colliding and non-colliding).

[0112] Instead of or in addition to a type indicator, a first transmission configuration having a first configuration type and a second transmission configuration having a second configuration type may be configurable. For example, a "Rel-18 CG PUSCH configuration type" may be introduced as an example of a "first" uplink transmission configuration type, in addition to any legacy (Rel-15 / 16 / 17) CG configuration type as an example of a "second" uplink transmission configuration type. In determining whether a resource type is applicable to a configured uplink transmission by a communication device and a base station, the rule that "legacy configuration types are applicable to non-conflicting time resources (e.g., symbols) while Rel-18 transmission types are applicable to conflicting time resources" may apply. An explicit type indicator may or may not be provided in the configuration because the UE may use other indications (e.g., configuration format or configuration signaling) to determine the configuration type.

[0113] In this approach, where resource types are determined to be conflicting or non-conflicting, conflicting symbols with conflicting direction settings in the first and second slot configurations may correspond to SBFD operation symbols on the gNB side as resource types that allow subband duplex operation. For example, the gNB may assign the conflicting symbols to full-duplex operation. However, the UE does not need to know whether SBFD is actually being performed.

[0114] <Semi-static and dynamic sending settings> In the following, similar to the approaches using conflicting and non-conflicting time resources described above, an approach is described in which a configuration type (e.g., "Rel-18 CG PUSCH configuration type") is introduced. Applicable resource types are distinguished between dynamic F symbols signaled by DCI and dynamic U symbols signaled by DCI. For example, the DCI can be a group-common DCI such as DCI2_0, or a dedicated DCI without actual PDSCH / PUSCH allocation.

[0115] In some embodiments, the resource type configuration includes a semi-statically configured slot format, and the UE receives (e.g., using the UE transceiver) the dynamically configured slot format in addition to the semi-statically configured slot format in the transmission configuration. The dynamically configured slot format may be transmitted by the base station in a DCI (e.g., DCI2_0).

[0116] Each of the semi-statically configured slot format and the dynamically configured slot format indicates a resource type of the second time resource as uplink, downlink, or flexible.

[0117] The semi-statically configured uplink transmission is not applicable to the resource type of the second time resource if the semi-statically configured slot format indicates the second time resource as a flexible resource and the dynamically configured slot format indicates the second time resource as an uplink or downlink resource.

[0118] A semi-statically configured uplink transmission is applicable to a resource type of a second time resource if both the semi-statically configured slot format and the dynamically configured slot format indicate the second time resource as a flexible resource.

[0119] In the above approach, a type indicator in the semi-static transmission configuration is provided as applicability information. In this approach, a dynamically configured slot format is provided as a type of applicability information indicating whether a semi-statically configured transmission is applicable to the resource type of the semi-statically configured slot format.

[0120] For example, in an uplink transmission configuration with a configuration type such as Rel-18 described above, the following rule may apply: "If the UE receives a dynamic slot format indicator (SFI) via DCI (e.g., DCI2_0), and the dynamic SFI indicates a dynamic slot format (having a value other than 255), then the Rel-18 CG PUSCH configuration is only applicable to the dynamically configured F symbols." This is shown at the top of Figure 15 for the symbols of slots #1, #2, and #3.

[0121] If the dynamic SFI signals 255 (meaning ignore the dynamic SFI) or the UE is otherwise configured not to monitor the dynamic SFI (e.g., via semi-static configuration), the uplink transmission configuration (e.g., for Rel-18 CG PUSCH) applies to both the semi-statically configured U symbol and the semi-statically configured F symbol. This is shown at the bottom of Figure 15.

[0122] For example, the semi-statically configured uplink transmission is applied to the second time resource if both of the following conditions apply (the first condition and at least one of the cases separated by "or" in the second condition): the resource type configuration includes a semi-statically configured slot format that defines the resource type of the second time resource as flexible, or the transceiver receives a configuration in operation to ignore the dynamically signaled slot format for the second time resource (e.g., an SFI value of 255), or the UE is not configured with a parameter indicating the configuration of the dynamically signaled slot format for the second time resource. In the latter case, examples of such signaling could be that a value of sfi-Radio Network Temporary Identifier (RNTI) is not provided to the communication device 860, or a control resource set for DCI type 2_0 is not provided to the UE, or an RRC IE SlotFormatIndicator is not provided to the UE and the UE is configured not to monitor the dynamic SFI.

[0123] In the above description, a "Rel-18 CG PUSCH configuration type" is mentioned as an example of a first uplink transmission configuration type for a first uplink transmission configuration, which can be configured in addition to a second uplink transmission type (e.g., a "legacy" / Rel 15-17 CG PUSCH configuration) for a second uplink transmission.

[0124] For example, a first transmission configuration (of a first configuration type) defines a first time resource allocated for a first semi-statically configured uplink transmission, and a second transmission configuration (of a second configuration type) defines a third time resource allocated for a second semi-statically configured uplink transmission that is applicable to the second resource type as the associated resource type. The second semi-statically configured uplink transmission applies to the resource type of the second time resource if the third time resource overlaps with the second time resource, the semi-statically configured slot format indicates the second time resource as a flexible resource, and the dynamically configured slot format indicates the second time resource as an uplink resource.

[0125] For example, in the case of legacy CG PUSCH configuration, "UE In the U symbol quasi-statically configured as the "third" time resource, as shown in slot #5 at the top of Figure 15, or ● As shown in the bottom of Figure 15, if the UE is not configured to monitor the SFI, then in the quasi-statically configured F symbol: The rule that "CG PUSCH is permitted to be transmitted" applies.

[0126] Furthermore, according to the above rules, for a semi-statically configured F symbol, if the UE is configured to monitor the SFI, (i) if the SFI indicates a value other than 255, the UE is permitted to transmit a CG PUSCH in a dynamic U symbol (as shown in the symbol of slot #4 at the top of FIG. 15), but the transmission in the dynamic F symbol is canceled / skipped; (ii) if the SFI indicates 255, the UE behaves as if it is not configured to monitor the SFI; and (iii) if the UE fails to receive the SFI (e.g., if it fails to receive the SFI), the UE determines whether to transmit or not depending on the parameter enableconfiguredUL provided by RRC signaling. More specifically, if enableconfiguredUL is set as "enabled," the UE is permitted to transmit an uplink signal / channel (e.g., a CG PUSCH) within a set of symbols of a slot when the UE does not detect DCI format 2_0, which provides a dynamic slot format for the set of symbols.

[0127] As mentioned above, the semi-statically configured slot format may be the "Rel-18 CG configuration type" described above, and the dynamically configured slot format may be received in the DCI as described above.

[0128] Furthermore, if another quasi-static transmission configuration (e.g., Legacy / Rel 15 / 16 / 17) type is available, the above transmission configuration may be an example of the "first" transmission configuration, and the legacy configuration may be an example of the second uplink transmission configuration, or vice versa.

[0129] In this approach, the dynamic F symbol corresponds to an SBFD operation symbol on the gNB side and therefore may correspond to a resource type that allows subband duplexing, but the UE does not need to know whether SBFD is actually being performed on that symbol.

[0130] <N for zero and non-zero TAOffset> According to this approach, the resource types to which semi-statically configured uplink transmissions are applicable are resource types with zero timing advance offset (e.g., N TA,offset symbols with a value of zero) and resource types with non-zero timing advance offsets (e.g., N TA,offset (symbols with non-zero values).

[0131] For example, N symbols or multiple symbols with a value of zero TA,offset If this value is zero, N TA,offset The configuration of can be done semi-statically (e.g., via RRC) or dynamically (via DCI).

[0132] Timing Advance Offset N TA,offset is used to adjust for the timing difference between uplink and downlink transmissions. An uplink transmission must be received (N TA +N TA,offset )×T c It is carried out in N TA is used to ensure that uplink transmissions from the UE are synchronized when received by the gNB. TA,offset is used to reserve the switchover time from UL to DL. C is the basic time unit of NR (e.g., T C =1 / (480000×4096) seconds).

[0133] Configured uplink transmission timing advance offset N of zero TA,offset time resources (e.g., symbols) with TA,offset A resource type indicator (e.g., a label or tag) may be provided in the quasi-static transmission configuration (e.g., CG PUSCH configuration) to indicate whether a given value is applicable to a time resource (e.g., a symbol), similar to the resource types described above.

[0134] Furthermore, N TA,offsetA symbol with a value of zero may correspond to an SBFD operation symbol on the gNB side as a symbol type that allows subband duplexing, but the UE does not need to know whether SBFD is actually being performed in each symbol.

[0135] The present disclosure and various approaches and embodiments described herein provide techniques for transmitting or dropping (e.g., skipping) semi-statically configured uplink transmissions (e.g., CG PUSCH instances) in a controlled manner. Furthermore, this control facilitates performing or skipping semi-statically configured transmissions without imposing constraints on the periodicity of CG PUSCH and SBFD time-domain patterns at the gNB side. For example, by indicating the time resource type of a time resource as allowing subband duplexing, uplink transmissions of interfering CG types can be prevented if the (semi-static) CG transmission configuration is inapplicable to the resource type allowing the uplink transmission.

[0136] It should be noted that CG PUSCH is mentioned as an example in the present disclosure and description of its approach. The described techniques are applicable to other (semi-statically) configured transmissions of UL signals and channels, such as Sounding Reference Signal (SRS), PUSCH repetition, or PUCCH repetition.

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

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

[0139] In the present disclosure, a base station may be, for example, a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a base unit, or a gateway. In addition, a terminal may be used instead of a base station in sidelink communication. The base station may be a repeater that relays communication between an upper node and a terminal. The base station may be a roadside unit.

[0140] The present disclosure may be applied to any of the uplink, downlink, and sidelink.

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

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

[0143] The present disclosure may be applied to both data channels and control channels.

[0144] For example, the channels of the present disclosure may be replaced with data channels PDSCH, PUSCH, and PSSCH, and control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

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

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

[0147] The present disclosure may be applied to both licensed and unlicensed bands.

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

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

[0150] An antenna port refers to a logical antenna (antenna group) formed from one or more physical antennas. That is, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna composed of multiple antennas. For example, the number of physical antennas that configure an antenna port is not defined. Instead, an antenna port is defined as the smallest unit that a terminal is permitted to transmit a reference signal. An antenna port can also be defined as the smallest unit that is multiplied by the weighting of a precoding vector.

[0151] The present disclosure can be implemented by software, hardware, or software cooperating with hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI (Large Scale Integration), which is an integrated circuit (IC), and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be formed as an individual chip, or a single chip may be formed to include some or all of the functional blocks. The LSI may include a data input / output unit coupled to it. Depending on the level of integration, the LSI may also be referred to as an IC (Integrated Circuit), system LSI, super LSI, or ultra LSI. However, the technology for implementing an integrated circuit is not limited to LSI, and may be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays), which can be programmed after LSI fabrication, and reconfigurable processors, which can reconfigure the connections and settings of circuit cells arranged within LSIs, may also be used. The present disclosure can be implemented using digital or analog processing. If, as a result of advances in semiconductor technology or other derivative technologies, LSI is replaced by future integrated circuit technologies, these future integrated circuit technologies can be used to integrate functional blocks. Biotechnology can also be applied.

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

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

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

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

[0156] Communication may include, for example, exchanging data through cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

[0157] A communications apparatus may include devices such as controllers and sensors connected to a communications device that perform the communications functions described in this disclosure, such as a controller or sensor that generates control or data signals used by the communications device to perform the communications functions of the communications apparatus.

[0158] Communications equipment may also include infrastructure facilities such as base stations, access points, and other equipment, devices, and systems that communicate with or control equipment such as the above non-limiting examples.

[0159] In summary, according to a first aspect, there is provided a communications device comprising: a transceiver unit that, in operation, receives a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmission applicable to an associated resource type; and a resource type configuration defining a resource type of a second time resource; and circuitry that, in operation, determines whether to start or skip performance of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, wherein the circuit determines to skip the semi-statically configured uplink transmission in the first time resource if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource; and the transceiver unit, in operation, performs or skips the semi-statically configured uplink transmission in the first time resource according to a result of the determination.

[0160] According to a second aspect that may be provided in combination with the first aspect, the transceiver unit, in operation, receives a first transmission configuration that defines as the associated resource type a first time resource allocated for a first quasi-statically configured uplink transmission that is applicable to a first resource type, and a second transmission configuration that defines as the associated resource type a third time resource allocated for a second quasi-statically configured uplink transmission that is applicable to a second resource type, wherein the first quasi-statically configured uplink transmission is not applicable to the second resource type.

[0161] According to a third aspect that may be provided in combination with the first or second aspect, the transmission configuration includes a resource type indicator that indicates the associated resource type.

[0162] According to a fourth aspect which may be provided in combination with any of the first to third aspects, the resource type to which the quasi-statically configured uplink transmission is applicable is either a resource type which allows subband duplexing or a resource type which prohibits subband duplexing.

[0163] According to a fifth aspect which may be provided in combination with any of the first to third aspects, the resource type configuration includes a first slot format and a second slot format, each of the first slot format and the second slot format specifying the second time resource as an uplink, a downlink, or a flexible resource, and a resource type to which the quasi-statically configured uplink transmission is applicable is one of i) a conflicting resource type, in which the first slot format indicates the second time resource as a downlink resource and the second slot format indicates the second time resource as an uplink resource or a flexible resource, and ii) a non-conflicting resource type, in which the first slot format indicates the second time resource as a flexible resource or the respective indications of the second time resource in the first slot format and the second slot format are the same.

[0164] According to a sixth aspect which may be provided in combination with any of the first to third aspects, the resource type to which the quasi-statically configured uplink transmission is applicable is either a resource type with a timing advance offset of zero or a resource type with a timing advance offset of non-zero.

[0165] According to a seventh aspect that may be provided in combination with the first aspect, the resource type configuration includes a semi-statically configured slot format, and the transceiver unit receives, during operation, a dynamically configured slot format, and each of the semi-statically configured slot format and the dynamically configured slot format indicates a resource type of the second time resource as uplink, downlink, or flexible, and if the semi-statically configured slot format indicates the second time resource as a flexible resource and the dynamically configured slot format indicates the second time resource as an uplink or downlink resource, the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource.

[0166] According to an eighth aspect which may be provided in combination with the seventh aspect, if both the semi-statically configured slot format and the dynamically configured slot format indicate the second time resource as a flexible resource, the semi-statically configured uplink transmission is applicable to a resource type of the second time resource.

[0167] According to a ninth aspect which may be provided in combination with the seventh or eighth aspect, if a first transmission configuration defines a first time resource allocated for a first semi-statically configured uplink transmission, and a second transmission configuration defines a third time resource allocated for a second semi-statically configured uplink transmission applicable to a second resource type as the associated resource type, the third time resource overlaps with the second time resource, the semi-statically configured slot format indicates the second time resource as a flexible resource, and the dynamically configured slot format indicates the second time resource as an uplink resource, then the second semi-statically configured uplink transmission is applicable to a resource type of the second time resource.

[0168] According to a tenth aspect which may be provided in combination with the first or second aspect, the semi-statically configured uplink transmission is applicable to the second time resource if the resource type configuration includes a semi-statically configured slot format which defines a resource type of the second time resource as flexible, and if the transceiver unit, in operation, receives a configuration which ignores the dynamically notified slot format for the second time resource, or if a parameter indicating the configuration of the dynamically notified slot format for the second time resource is not configured in the UE.

[0169] According to an eleventh aspect which may be provided in combination with the first or second aspect, the transceiver unit receives, during operation, applicability information indicating whether the quasi-statically configured uplink transmission is applicable to a resource type of the second time resource.

[0170] According to a twelfth aspect which may be provided in combination with any of the first to eleventh aspects, when the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is applicable to a resource type of the second time resource, the circuit determines to start execution of the semi-statically configured uplink transmission in the first time resource.

[0171] According to a thirteenth aspect, there is provided a base station comprising: a circuit for generating, in operation, a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmission applicable to an associated resource type, and a resource type configuration defining a resource type of a second time resource; and a transceiver unit for transmitting, in operation, the transmission configuration and the resource type configuration, wherein the circuit determines, in operation based on the transmission configuration and the resource type configuration, whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource; and, if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it determines that reception of the semi-statically configured uplink transmission in the first time resource is to be skipped; and, in operation, the transceiver unit performs or skips reception of the semi-statically configured uplink transmission in the first time resource according to a result of the determination.

[0172] According to a fourteenth aspect that may be provided in combination with the thirteenth aspect, the circuit, when operating, determines that when the first time resource is allocated for subband duplex operation, the communication device skips the quasi-statically configured uplink transmission in the first time resource.

[0173] According to a fifteenth aspect, there is provided a communication method, comprising: receiving a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmission applicable to an associated resource type performed by a communication device; receiving a resource type configuration defining a resource type of a second time resource; determining whether to start or skip performance of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, wherein if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined that the semi-statically configured uplink transmission is to be skipped in the first time resource; and performing or skipping the semi-statically configured uplink transmission according to a result of the determination.

[0174] According to a sixteenth aspect, there is provided a communication method for a base station, comprising: generating a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmission applicable to an associated resource type; transmitting the transmission configuration; generating a resource type configuration defining a resource type of a second time resource; transmitting the resource type configuration; determining, based on the transmission configuration and the resource type configuration, whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource, wherein if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined that reception of the semi-statically configured uplink transmission in the first time resource is to be skipped; transmitting the resource type configuration; and performing or skipping reception of the semi-statically configured uplink transmission in the first time resource according to a result of the determination.

[0175] Further provided is an integrated circuit configured to control a communications device to perform a method according to the fifteenth aspect, and an integrated circuit for controlling a base station to perform a communications method according to the sixteenth aspect.

[0176] Additionally, a non-transitory medium is provided that stores program instructions that, when executed on a processing circuit such as a general processor, cause the execution of all the steps of the above method embodiments or aspects.

Claims

1. a transceiver unit configured to receive, in operation, a transmission configuration defining a first time resource allocated for uplink transmissions, the transmission configuration being applicable to an associated resource type, and a resource type configuration defining a resource type of the second time resource; and a circuit configured to, during operation, determine whether to start or skip execution of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration; the circuit determines to skip the semi-statically configured uplink transmission in the first time resource when the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource; and wherein the transceiver unit, during operation, performs or skips the semi-statically configured uplink transmission in the first time resource according to a result of the determination. Communication devices.

2. The transceiver unit, when operating, a first transmission configuration that defines the first time resources allocated for a first semi-statically configured uplink transmission applicable to a first resource type as the associated resource type; a second transmission configuration defining a third time resource allocated for a second semi-statically configured uplink transmission applicable to a second resource type as the associated resource type; the first semi-statically configured uplink transmission is not applicable to the second resource type; The communication device of claim 1 .

3. the transmission configuration includes a resource type indicator indicating the associated resource type; The communication device of claim 1 .

4. The resource type to which the semi-statically configured uplink transmission is applicable is either a resource type that allows subband duplexing or a resource type that prohibits subband duplexing. The communication device of claim 1 .

5. The resource type configuration includes a first slot format and a second slot format, each of the first slot format and the second slot format specifying the second time resource as uplink, downlink, or flexible, and the resource type to which the semi-statically configured uplink transmission is applicable is: i) conflicting resource types, where the first slot format indicates the second time resource as a downlink resource and the second slot format indicates the second time resource as an uplink resource or a flexible resource; and ii) a non-conflicting resource type, in which the first slot format indicates the second time resource as a flexible resource or the respective indications of the second time resource in the first slot format and the second slot format are the same; The communication device of claim 1 .

6. the resource type to which the semi-statically configured uplink transmission is applicable is either a resource type having a timing advance offset of zero or a resource type having a timing advance offset of non-zero; The communication device of claim 1 .

7. The resource type configuration includes a semi-statically configured slot format; The transceiver receives a dynamically configured slot format during operation; Each of the semi-statically configured slot format and the dynamically configured slot format indicates a resource type of the second time resource as uplink, downlink, or flexible; If the semi-statically configured slot format indicates the second time resource as a flexible resource and the dynamically configured slot format indicates the second time resource as an uplink or downlink resource, the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource. The communication device of claim 1 .

8. If both the semi-statically configured slot format and the dynamically configured slot format indicate the second time resource as a flexible resource, the semi-statically configured uplink transmission is applicable to a resource type of the second time resource. The communication device of claim 7.

9. a first transmission configuration defining the first time resources allocated for a first semi-statically configured uplink transmission; a second transmission configuration defining a third time resource allocated for a second semi-statically configured uplink transmission applicable to a second resource type as the associated resource type; If the third time resource overlaps with a second time resource, the semi-statically configured slot format indicates the second time resource as a flexible resource, and the dynamically configured slot format indicates the second time resource as an uplink resource, the second semi-statically configured uplink transmission is applicable to a resource type of the second time resource. The communication device of claim 7.

10. The semi-statically configured uplink transmission is applicable to the second time resource if: the resource type configuration includes a semi-statically configured slot format that defines a resource type of the second time resource as flexible; and the transceiver unit receives, during operation, a configuration to ignore the dynamically notified slot format for the second time resource, or a parameter indicating a configuration of the dynamically notified slot format for the second time resource is not configured in the communication device. A communication device according to claim 1 or 2.

11. and wherein the transceiver unit, upon operation, receives applicability information indicating whether the semi-statically configured uplink transmission is applicable to a resource type of the second time resource. The communication device of claim 1 .

12. The semi-statically configured uplink transmission is an uplink transmission without a dynamic grant. The communication device of claim 1 .

13. When the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is applicable to a resource type of the second time resource, the circuit determines to start performing the semi-statically configured uplink transmission in the first time resource. The communication device of claim 1 .

14. a circuit for generating, during operation, a transmission configuration defining a first time resource allocated for uplink transmissions, the first time resource being semi-statically configured and applicable to an associated resource type; and a resource type configuration defining a resource type of the second time resource. a transceiver that, when operational, transmits the transmission configuration and the resource type configuration; In operation, the circuit determines whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration; determining that reception of the semi-statically configured uplink transmission in the first time resource is skipped when the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource; and wherein the transceiver unit, during operation, performs or skips reception of the semi-statically configured uplink transmission in the first time resource according to a result of the determination. Base station.

15. The circuitry, in operation, determines that if the first time resource is allocated for subband duplex operation, the communications device skips the semi-statically configured uplink transmission in the first time resource. The base station of claim 14.

16. Executed by a communication device receiving a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmissions applicable to an associated resource type; receiving a resource type configuration defining a resource type of a second time resource; determining whether to start or skip execution of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, determining, if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource, that the semi-statically configured uplink transmission is determined to be skipped in the first time resource; performing or skipping the semi-statically configured uplink transmission according to a result of the determination. Communication method.

17. Executed by the base station generating a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmissions applicable to the associated resource type; transmitting the transmission setting; generating a resource type configuration defining a resource type of the second time resource; sending the resource type configuration; determining whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, determining, if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource, that reception of the semi-statically configured uplink transmission in the first time resource is determined to be skipped; performing or skipping reception of the semi-statically configured uplink transmission in the first time resource according to a result of the determination; Communication method.

18. When in operation, receiving a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmissions applicable to an associated resource type; receiving a resource type configuration defining a resource type of a second time resource; determining whether to start or skip execution of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, determining, if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource, that the semi-statically configured uplink transmission is determined to be skipped in the first time resource; performing or skipping the semi-statically configured uplink transmission according to a result of the determination; An integrated circuit that causes a communication device to perform the above.

19. When in operation, generating a transmission configuration defining a first time resource allocated for semi-statically configured uplink transmissions applicable to the associated resource type; transmitting the transmission setting; generating a resource type configuration defining a resource type of the second time resource; sending the resource type configuration; determining whether to start or skip reception of the semi-statically configured uplink transmission in the first time resource based on the transmission configuration and the resource type configuration, determining, if the first time resource overlaps with the second time resource and the semi-statically configured uplink transmission is not applicable to a resource type of the second time resource, that reception of the semi-statically configured uplink transmission in the first time resource is determined to be skipped; sending the resource type configuration; performing or skipping reception of the semi-statically configured uplink transmission in the first time resource according to a result of the determination; An integrated circuit that enables a base station to perform the above.

Images