Communication device and base station involving uplink configuration

Abstract

A communication device, a base station, and methods for the communication device and the base station are provided. The communication apparatus includes a transceiver that receives a transmission configuration and a resource type configuration, the transmission configuration defining a first time resource for uplink transmission applicable to a semi-static configuration of an associated resource type, the resource type configuration defining a resource type of a second time resource; and circuitry to determine, based on the transmission configuration and the resource type configuration, whether to initiate execution or skip a semi-statically configured uplink transmission on the first time resource. If the first time resource overlaps the second time resource and if the uplink transmission is not suitable for the resource type of the second time resource, the circuitry determines to skip the uplink transmission, and the transceiver performs or skips the semi-statically configured uplink transmission in accordance with the determination.

Description

Technical Field

[0001] The present disclosure relates to signal transmission and reception in a communication system. In particular, the present disclosure relates to methods and apparatus for such transmission and reception. Background Art

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

[0003] For systems such as LTE, LTE-A and NR, further modifications and options may facilitate efficient operation of the communication system and specific equipment related to the system. Summary of the invention

[0004] One non-limiting and exemplary embodiment facilitates efficient interference reporting and interfering cell management.

[0005] In an embodiment, the technology disclosed herein is characterized by a communication device, which includes a transceiver and a circuit, the transceiver receiving a transmission configuration and a resource type configuration, the transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type, and the resource type configuration defining a resource type of a second time resource; the circuit determining whether to initiate execution or skip the semi-statically configured uplink transmission on 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 if 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 on the first time resource, and the transceiver executes or skips the semi-statically configured uplink transmission based on the determined result.

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

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

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

[0009] Figure 1 An exemplary architecture of a 3GPP NR system is shown;

[0010] Figure 2 is a schematic diagram showing the functional division between NG-RAN and 5GC,

[0011] Figure 3 is a sequence diagram of the RRC connection establishment / reconfiguration process,

[0012] Figure 4 is a schematic diagram showing usage scenarios of enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC),

[0013] Figure 5 is a block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario,

[0014] Fig. 6A and Figure 6B is a schematic diagram showing sub-band non-overlapping full-duplex from the perspective of the gNB and the perspective of the UE,

[0015] Figure 7 is a schematic diagram showing potential overlap of CG PUSCH with downlink transmissions in sub-band non-overlapping full-duplex operation,

[0016] Figure 8 is a block diagram showing a base station and a communication device,

[0017] Fig. 9 is a block diagram showing an uplink transmission determination circuit of the configuration,

[0018] Fig.10 is a flow chart showing the steps of a communication method for a communication device,

[0019] Fig.11 is a flow chart showing the steps of a communication method for a base station,

[0020] Fig.12 is a schematic diagram showing association between CG PUSCH configuration and symbol type,

[0021] Fig.13 is a flow chart showing the steps of a communication method for a communication device,

[0022] Fig.14 is a flow chart showing the steps of a communication method for a base station;

[0023] Fig.15 is a schematic diagram illustrating determination regarding CG PUSCH transmission based on reception of a dynamic slot format indicator. DETAILED DESCRIPTION

[0024] 5G NR system architecture and protocol stack

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

[0026] Apart from this, the overall system architecture assumes a NG-RAN (Next Generation Radio Access Network) comprising gNBs (gNodeBs), providing NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC, Radio Resource Control) protocol terminations to the UE. The gNBs are interconnected with each other by means of Xn interfaces. The gNB is also connected to the NGC (Next Generation Core) via a Next Generation (NG) interface, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) via a NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) via a NG-U interface. The NG-RAN architecture is Figure 1 (see, for example, 3GPP TS 38.300 v15.6.0, Section 4).

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

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

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

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

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

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

[0033] In NR, a resource block (RB) is defined as 12 consecutive subcarriers in the frequency domain. Resource blocks are numbered from zero upwards in the frequency domain as common resource blocks configured with subcarrier spacing. Physical resource blocks (PRBs) are defined within bandwidth parts (subsets of consecutive common resource blocks) and are numbered per bandwidth part. 5G NR functional division between NG-RAN and 5GC

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

[0035] In particular, gNB and ng-eNB host the following key functions:

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

[0037] -IP header compression, encryption and data integrity protection;

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

[0039] - Routing user plane data towards UPF;

[0040] - Routing control plane information towards the AMF;

[0041] -Connection establishment and release;

[0042] - Scheduling and transmission of paging messages;

[0043] - Scheduling and transmission of system broadcast information (derived from AMF or OAM);

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

[0045] - Transport level packet marking in uplink;

[0046] -Session management;

[0047] -Support network slicing;

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

[0049] -Support UE in RRC_INACTIVE state;

[0050] -NAS (Non-Access Stratum) message distribution function;

[0051] - Radio access network sharing;

[0052] -Dual connection;

[0053] - Tight interworking between NR and E-UTRA.

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

[0055] - Non-access stratum NAS signaling termination;

[0056] -NAS signaling security;

[0057] -Access layer AS security control;

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

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

[0060] -Registration area management;

[0061] -Support mobility within and between systems;

[0062] -Access authentication;

[0063] -Access authorization, including roaming permission checks;

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

[0065] -Support network slicing;

[0066] -Session management function SMF selection.

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

[0068] - Anchor point for intra / inter-RAT mobility (when applicable);

[0069] - External PDU session points interconnected with the data network;

[0070] -Packet routing and forwarding;

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

[0072] - Traffic usage report;

[0073] - Uplink classifier to support routing of traffic flows to the data network;

[0074] -Support branching points for multi-host PDU sessions;

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

[0076] - Uplink service verification (SDF to QoS flow mapping);

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

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

[0079] -Session management;

[0080] -UE IP address allocation and management;

[0081] -Selection and control of UP function;

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

[0083] -Policy implementation and QoS control part;

[0084] - Downlink data notification.

[0085] RRC connection establishment and reconfiguration process

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

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

[0088] Therefore, in the present disclosure, an entity (e.g., AMF, SMF, etc.) of a fifth generation core (5GC) is provided, which includes a control circuit and a transmitter, the control circuit establishes a next generation (NG) connection with a gNodeB, and the transmitter sends an initial context establishment message to the gNodeB via the NG connection, so as to cause a signaling radio bearer between the gNodeB and a user equipment (UE) to be established. Specifically, the gNodeB sends a radio resource control RRC signaling containing a resource allocation configuration information element to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.

[0089] IMT usage scenarios in 2020 and beyond

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

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

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

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

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

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

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

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

[0098] In slot-based scheduling or allocation, the slot corresponds to the timing granularity (TTI - Transmission Time Interval) used for scheduling allocations. Typically, the TTI determines the timing granularity used for scheduling allocations. One TTI is the time interval during which a given signal is mapped to the physical layer. For example, conventionally, the TTI length can vary from 14 symbols (slot-based scheduling) to 2 symbols (non-slot-based scheduling). Downlink (DL) and uplink (UL) transmissions are specified to be organized into frames (10ms duration) consisting of 10 subframes (1ms duration). In slot-based transmission, the subframes are further divided into slots, the number of which is defined by the parameter set / subcarrier spacing. The range of specified values ​​is between 10 slots per frame (1 slot per subframe) for a subcarrier spacing of 15kHz to 80 slots per frame (8 slots per subframe) for a subcarrier spacing of 120kHz. The number of OFDM symbols per slot is 14 for a normal cyclic prefix and 12 for an extended cyclic prefix (see Section 4.1 (General frame structure), Section 4.2 (Parameter sets), Section 4.3.1 (Frame and TTI subframes) and Section 4.3.2 (Slots) of 3GPP TS 38.211 V15.3.0, Physical Channels and Modulation, 2018-09). However, the allocation of time resources for transmission may also be non-slot based. In particular, a TTI in a non-slot based allocation may correspond to a mini-slot instead of a slot. That is, one or more mini-slots may be allocated to the transmission of requested data / control signaling. In a non-slot based allocation, the minimum length of a TTI may be, for example, 1 or 2 OFDM symbols.

[0099] QoS Control

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

[0101] For each UE, the 5GC establishes one or more PDU Sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU Session, and may subsequently configure (one or more) additional DRBs for (one or more) QoS flows of that PDU Session (depending on when the NG-RAN does so), e.g. as described above with reference to Figure 3 As shown in Figure 2. NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0102] Figure 5 The 5G NR non-roaming reference architecture is shown (see TS 23.501 v16.1.0, Section 4.23). Figure 4 The application function (AF) (e.g., an external application server hosting 5G services) described in the exemplary embodiment interacts with the 3GPP core network to provide services, such as to support the impact of applications on service routing, access network exposure functions (NEFs), or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function, PCF). Based on operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Operators do not allow application functions that directly access network functions to interact with related network functions using an external exposure framework via NEF.

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

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

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

[0106] In time division duplex (TDD) operation, time domain resources are divided between downlink and uplink. Allocating limited duration for uplink in TDD may result in reduced coverage, increased latency and reduced capacity. In view of this, full duplex such as sub-band non-overlapping full duplex (SFBD) is studied in NR (see 3GPP TSG RAN#94-e, RP-213591, "New SI: Study on the evolution of NR duplex operation").

[0107] How to enable SBFD within the TDD band is being studied. SBFD provides for the simultaneous presence of downlink and uplink within the TDD band, where subbands within the TDD band are used to divide or separate different transmission directions. For example, uplink and downlink transmissions are processed simultaneously by the base station. Examples of SBFD operation are shown in 6A from the perspective of (a) a base station (gNB) and in 6B from the perspective of (b) a user equipment (UE).

[0108] For illustrative purposes, an example is shown in FIG. 6 and in other figures of the present disclosure, where in the time domain, uplink and downlink resources are allocated at the slot level. However, the present disclosure is also applicable to scenarios where the granularity level in the time domain for allocating uplink and downlink (or flexible) resources is different from the slot level. For example, the symbols within a slot as uplink, downlink and flexible allocations can be provided by the slot format.

[0109] Configuration Grant (CG) PUSCH

[0110] Uplink transmissions on PUSCH may be scheduled via dynamic grants, e.g., using DCI (Downlink Control Information) or without dynamic grants. PUSCH without dynamic grants is called Configuration Grant (CG) PUSCH. CG PUSCH is semi-statically configured, e.g., by RRC, and includes the following types.

[0111] For Type 1CG PUSCH, all transmission parameters including time and frequency resource allocations are RRC configured for a given BWP. For example, the time resource allocation may include periodicity in terms of time slots and number of symbols within a time slot. For Type 2CG PUSCH, the transmission periodicity is provided by the RRC configuration, and DCI is used to activate and deactivate transmissions. Although the time and frequency resource allocations are dynamically indicated by the activating DCI, the same resource allocations will be used for all PUSCH instances with the configured periodicity, e.g. until Type 2CG PUSCH is deactivated or released by another DCI.

[0112] In both Type-1 and Type-2 CG PUSCH, the time-frequency resource allocation is of a semi-static nature, which is different from the dynamic nature of PUSCH scheduled by dynamic grants.

[0113] Time slot format

[0114] In NR operation including Release 15-17 (Rel-15 / 16 / 17), the gNB informs the UE of the transmission direction via the slot format. The slot format includes downlink (D, DL), uplink (U, UL), and flexible (F) symbols. The slot format indicating that each symbol in the slot is U, D, or F can be semi-statically configured by RRC signaling or dynamically configured by DCI. The semi-static configuration may include 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, which may be broadcast, for example, by SIB1 (System Information Block 1). In UE-specific signaling, the slot format may be indicated using the information element tdd-UL-DL-ConfigurationDedicated. Dynamic configuration of the slot format is provided in the DCI using a slot format indicator (SFI) (e.g., SlotFormatIndicator) sent by a field in DCI format 2_0. The SFI provides a pointer to a specific slot format combination generated according to the standardized slot format. In addition, the standardized slot format 255 is used to indicate that the uplink / downlink / flexible transmission mode is not determined by a dynamically indicated slot format combination. For example, if the SFI indicates the standardized slot format 255, the UE can determine the slot format of the slot based on tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0115] When configuring the timeslot format via NR Release 15-17 specifications, the following rules shall be observed:

[0116] • Semi-static cell-common D and U symbols cannot be changed by either UE-specific RRC or dynamic configuration (SFI in DCI format 2_0).

[0117] ● Only the semi-static cell common F symbol can be rewritten as D or U by UE-specific RRC.

[0118] ● If the semi-static cell-common F symbol is not rewritten to D or U by the UE-specific RRC, it remains semi-static F, which may be further indicated by the SFI in DCI format 2_0 as dynamic D, dynamic U or dynamic F.

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

[0120] For CG PUSCH resource allocation, the allocated time resources may overlap in time with UL resources in one instance, but may overlap in time with SBFD resources in another instance. Figure 7 In case that CG PUSCH allocation overlaps with SBFD slots or symbols, their resource allocation may degrade the performance of DL transmissions allocated to one of the subbands on the same symbol or slot, and for example when the frequency resources of CG PUSCH and DL transmissions overlap (see Figure 7 Time slots #3 and #4 in the example in have an interference effect.

[0121] In this disclosure, "SBFD symbols" refer to symbols with subbands that the gNB will potentially use for SBFD operation, and "normal UL symbols" or "UL symbols" are symbols used for UL in legacy NR (Rel-15 / 16 / 17) that do not contain subband splitting. Both SBFD and normal UL symbols are defined from the gNB perspective, while the UE may or may not be aware of the gNB's intended usage. Corresponding definitions also apply to SBFD and ("normal") UL timeslots, or more generally, to time resources.

[0122] In view of the above-mentioned interference and performance degradation issues, if the gNB operates SBFD symbols in a semi-static manner, in principle, the CG PUSCH can be configured in a way that the time resources (e.g., periodicity and symbol offset) are aligned with the time resources of either UL symbols or SBFD symbols. However, this alignment is an additional constraint on the CG PUSCH configuration, which needs to be handled by the gNB and increases the complexity of resource allocation. In addition, if the SBFD time pattern changes, reconfiguration of the CG PUSCH is required for the new alignment, which increases the signaling overhead.

[0123] In view of the above, the method disclosed in the present invention is to introduce an association between the CG PUSCH configuration and the applicable symbol type, so that if the CG PUSCH instance does not overlap or match the applicable symbol type, the UE will skip the CG PUSCH instance (no transmission). Different examples of "symbol type" will be provided for several embodiments.

[0124] like Figure 8 As shown, a communication device 860 including a transceiver 870 and a circuit 880 is provided.

[0125] The transceiver receives a transmission configuration that defines a first time resource allocated for a semi-statically configured uplink transmission. In the transmission configuration, the uplink transmission is configured to be applicable to an associated resource type. The transceiver 870 also receives a resource type configuration that defines a resource type for a second time resource.

[0126] Based on the received transmission configuration and resource type configuration, the circuit 880 determines whether to initiate or skip the semi-statically configured uplink transmission on the first time resource. In the determination, if the first time resource overlaps with the second time resource and if 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 on the first time resource.

[0127] According to the determination result, the transceiver 870 performs or skips the semi-statically configured uplink transmission on the first time resource according to the determination result.

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

[0129] The UE circuit 880 may include a configured uplink transmission determination circuit 885. Fig. 9As shown, the exemplary configured uplink transmission determination circuit 885 includes: a configuration evaluation circuit 986, which evaluates the received transmission and resource type configuration; and a transmission initiation or skipping decision circuit 987, which determines whether to control the UE transceiver 870 to initiate or skip the semi-statically configured uplink transmission based on the evaluation.

[0130] Further provide and also Figure 8 Shown in FIG. 8 is a base station 810 . The base station includes a transceiver 820 and a circuit 830 .

[0131] The transceiver 820 generates a transmission configuration defining a first time resource allocated for uplink transmissions applicable to a semi-static configuration of an associated resource type. The circuit 830 also generates a resource type configuration defining a resource type of a second time resource.

[0132] Based on the transmission configuration and the resource type configuration, circuit 830 determines whether to initiate or skip receiving a semi-statically configured uplink transmission on a first time resource, wherein if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined to skip receiving the semi-statically configured uplink transmission on the first time resource.

[0133] The transceiver 820 performs reception of uplink transmission of the semi-static configuration or skips reception of uplink transmission of the semi-static configuration according to the result of the determination.

[0134] Base station 810 may be a scheduling entity or a scheduling node, such as a gNB.

[0135] For example, the base station circuitry 830 includes an uplink transmission determination circuitry 835 that is configured.

[0136] To distinguish the circuits and transceivers of the communication equipment (UE) 860 and the base station 810, we will use the terms "UE circuits / transceivers and gNB circuits / transceivers", respectively.

[0137] like Figure 8 As shown, the base station 810 and the communication device 860 perform communication (transmission and reception) via a communication channel such as a wireless channel via the transceivers 820 and 870. For example, in the above-mentioned transmission and reception operations to be performed by the base station 810 and the communication device 870, the base station 810 transmits to the communication device 860 and receives from the communication device 860, and vice versa.

[0138] As described herein, the gNB and UE transceivers 820 and 870 perform transmission and reception of data such as the aforementioned configuration or uplink transmission or other data to be mentioned below. For example, the transceiver transmits or receives a signal carrying corresponding data. Circuits 830 and 880 control the corresponding transceiver 820 or 870 to perform corresponding transmission or reception of data.

[0139] like Fig.10 As shown, corresponding to the communication device is a communication method performed by the communication device 860, which includes method steps performed by a communication device such as a UE. In step S1010, the UE receives a transmission configuration, which is defined as 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, which defines a resource type of a second time resource. For example, the transmission and resource type configurations are received from a base station. Based on the transmission configuration and based on the resource type configuration, in step S1030, the UE makes a determination as to whether to initiate or skip an uplink transmission of a semi-static configuration on a first time resource. In the determination step S1030, if the first time resource overlaps with the second time resource and if the uplink transmission of the semi-static configuration is not applicable to the resource type of the second time resource, it is determined to skip the uplink transmission of the semi-static configuration on the first time resource. The UE performs (S1040-2) or skips (S1040-1) the uplink transmission of the semi-static configuration on the first time resource according to the result of the determination.

[0140] In addition, if Fig.11 As shown, a communication method is provided, which includes steps performed by a base station 810.

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

[0142] In step S1130, the base station generates a resource type configuration, which defines a resource type of the second time resource, and sends the resource type configuration in step S1140.

[0143] In addition, in the method, the base station performs step S1150: making a determination as to whether to initiate or skip receiving a semi-statically configured uplink transmission on a first time resource. In this step, if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined to skip receiving the semi-statically configured uplink transmission on the first time resource.

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

[0145] Note that the present disclosure is not limited to the Fig.10 and Fig.11 For example, in the method of the UE, the order of receiving the transmission configuration and the resource type configuration (steps S1010 and S1020) may be exchanged. Accordingly, in the method of the base station, steps S1130 and S1140 of generating and sending the resource type configuration may be performed before steps S1110 and S1120 of generating and sending the semi-static uplink transmission configuration.

[0146] As mentioned, the base station 810 and the communication device 860 communicate with each other via a communication channel. Accordingly, each transmission operation disclosed on one entity (communication device or base station) side means a corresponding reception operation on the other side. In addition, each operation detail described with respect to the device means a corresponding method step in the method corresponding to the device.

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

[0148] The transmission configuration is received via semi-static signaling (e.g., RRC signaling) and configures a semi-statically configured uplink transmission, such as a transmission that is not configured by a dynamic grant. The semi-statically configured uplink transmission may be, but is not limited to, the above-mentioned CG PUSCH, such as the above-mentioned type 1 and type 2 CG PUSCH. The semi-static configuration configures frequency resources and time resources for the semi-statically configured uplink transmission (for type 2 CG PUSCH, as described above, although the frequency resources are allocated by DCI, the same frequency resources will be used for all CG PUSCH instances until the CG PUSCH is deactivated by another DCI). Frequency resources may be placed within a frequency band (e.g., a bandwidth portion), or within a subband of a frequency band. Time resources may include slot periodicity, slot offset, and number of symbols. In the present disclosure, time resources configured or indicated by a semi-static transmission configuration are represented as one or more "first" time resources.

[0149] The resource type configuration may also include a configuration that is semi-statically (e.g., RRC) configured. However, the resource type configuration may also be dynamically configured via DCI. The resource type configuration configures a time pattern in which a resource type is indicated for each of a plurality of available time resources (such as time slots, symbols, etc.). Time resources are associated with corresponding resource types to divide the available resources into time resources that allow SBFD operation and time resources that allow uplink operation but may not allow SBFD operation.

[0150] In the present disclosure, time resources configured by a resource type configuration are denoted as "second" time resources. The resource type configuration can be configured independently of the semi-static uplink transmission configuration, for example, with a different periodicity. As another example, when configuring the resource type of the second time resource, the base station does not need to know or care which resources are allocated for the semi-statically configured uplink transmission. In addition, uplink transmissions such as CG PUSCH can be semi-statically configured without knowing or ignoring knowledge of the temporal pattern of the resource type or the resource type configuration. Therefore, the second time resources may include time resources that overlap with the first time resources allocated for semi-static uplink transmission, and they may include time resources that do not overlap with the first time resources.

[0151] However, it is also possible to generate a resource type configuration and determine the time pattern indicated therein based on the resource allocation in the semi-static transmission configuration, or to generate a transmission configuration based on the resource type configuration and the time pattern indicated therein.

[0152] As described, both the base station 810 and the communication device 860 make a determination as to whether the communication device 860 initiates or skips the semi-statically configured uplink transmission. If it is determined that the first time resource overlaps with the second time resource and if it is determined that the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined to skip the semi-statically configured uplink transmission.

[0153] If the first time resource overlaps with the second time resource and it is determined that the semi-statically configured time resource is applicable to the resource type of the second time resource, the circuit 880 determines to initiate the semi-statically configured uplink transmission on the first time resource, and the communication device 860 initiates the semi-statically configured uplink transmission. Here, "initiating" the transmission (and receiving at the base station side) may include further determinations or tests, such as checking whether there is a dynamic permission transmission allocated to the second time resource, such as a downlink transmission. Therefore, "performing a transmission of the semi-statically configured uplink resource according to the result of the determination" may include further conditions for performing the uplink transmission.

[0154] In the following, examples will be described of how to enable a UE to determine the resource type associated with an uplink transmission and whether a semi-statically configured transmission is applicable for a given resource type.

[0155] One possibility is that the UE is configured with a first transmission configuration and a second transmission configuration. In such a case, the UE transceiver 870 may receive a first transmission configuration defining a first time resource allocated for a first semi-statically configured uplink transmission applicable to a first resource type as an associated resource type, and 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 an associated resource type, wherein the first semi-statically configured uplink transmission is not applicable to the second resource type.

[0156] Similar to the uplink transmission of the first semi-static configuration allocated to the first time resource, circuits 880 and 830 determine whether to initiate or skip the uplink transmission of the second semi-static configuration on the third time resource, and the transceiver 870 performs or skips the transmission of the second semi-static configuration on the third time resource according to the determination result.

[0157] As described above, the first uplink transmission and the second uplink transmission may be semi-statically configured, wherein the first uplink transmission is applicable to the first resource type, the second uplink transmission is applicable to the second resource type, and the uplink transmission of the first semi-static configuration is not applicable to the second resource type. In this case, the uplink transmission of the second semi-static configuration may be applicable to or not applicable to the first resource type.

[0158] Note that the expressions "first" and "second" resource types are used interchangeably to refer to either one resource type that allows SBFD and another resource type that does not allow SBFD. Accordingly, the "first" resource type may refer to either a resource type that allows SBFD or a resource type that does not allow SBFD. Similarly, the expression "second resource type" may refer to both types and is used to describe a scenario in which the first resource type and the second resource type are to be distinguished.

[0159] The resource type to which the semi-statically configured uplink transmission is applicable may be one of (i) a resource type that allows sub-band duplexing (eg, SBFD) and (ii) a resource type that prohibits sub-band duplexing.

[0160] For example, the gNB circuit 830 determines that the UE 860 skips the semi-statically configured uplink transmission on the first time resource when allocating or reserving the first time resource for sub-band duplex operation. In this case, for example, the semi-statically configured uplink transmission can be configured to be applicable to the resource type that prohibits sub-band duplexing, but not applicable to the resource type that allows sub-band duplexing.

[0161] For example, the first resource type is a resource type that allows sub-band duplexing, and the second resource type is a resource type that prohibits sub-band duplexing. Alternatively, the first resource type may be a resource type that prohibits sub-band duplexing, and the second resource type may be a resource type that allows sub-band duplexing.

[0162] In order to enable the UE to determine whether the semi-statically configured uplink transmission is applicable to the resource type or to determine the corresponding resource type, applicability information may be signaled from the base station to the UE.

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

[0164] 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 more briefly, a "type indicator") for indicating the associated resource type. The resource type indicator may be a tag or label attached 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.

[0165] As an alternative to the resource type indicator in the uplink transmission configuration, the UE may know the applicable resource type for semi-statically configured uplink transmission based on the configuration type of the uplink configuration and specific rules specified in the standard. For example, the standard may specify that a certain type of uplink configuration is applicable to a certain resource type.

[0166] Full-duplex resources and uplink resources

[0167] In the following, reference will be made to Fig.12 An example is described in which a time pattern of resource types is configured in a semi-static uplink transmission configuration and a resource type indicator is provided. In this example, the applicable resource type for the time resource is a resource type in the following items: (i) full-duplex (e.g., SBFD) resources, and (ii) uplink resources that prohibit full-duplex (or "non-full-duplex uplink resources").

[0168] As shown, the time pattern of SBFD time resources is configured to the UE as an example of resource type configuration. This configuration can be done semi-statically via RRC or dynamically via DCI. The time pattern of the resource type configuration determines which time resources among multiple time resources (e.g., consecutive time slots or symbols within a time slot) are SBFD time resources. Although Fig.12 The time slots are shown as time resources, but the configuration of the time pattern can be done, for example, at the time slot level, the symbol level, a combination of both, or other time units such as mini-slots. Fig.12In the example, the time pattern configures time slots #1, #2, #3, and #4 as configured SBFD time resources. The other uplink resources outside this SBFD time pattern (time slots #2 and #5 in this example) are treated as "normal" uplink time resources that do not allow full duplex. Although the SBFD time resources contain subbands that can be used for different transmission directions (UL, DL), the gNB is not required to always operate in full duplex in the SBFD time resources. For example, the gNB can schedule UL transmissions on the UL subband and leave the DL subband unused in the SBFD time resources.

[0169] In the CG PUSCH configuration which is an example of a semi-statically configured transmission configuration, there is a type indicator (or tag or label) which indicates that the CG PUSCH is applicable to SBFD symbol / time resources ( Fig.12 ) or "normal" non-full-duplex symbol / time resources ( Fig.12 If the applicable symbol type or resource type is not indicated in the CG PUSCH configuration, the configuration can be applied to both types ( Fig.12 ).

[0170] One example is to include the following parameter as a type indicator in the CG PUSCH configuration:

[0171] Cg-PUSCH-resourceType ENUMERATED{SBFD,non-SBFD}

[0172] exist Fig.13Exemplary method steps for a UE method are shown in , wherein the resource type configuration includes a SBFD time pattern. In step S1310, the UE is configured with a time pattern of SBFD symbols as a resource type configuration. In step S1320, the UE is configured with a CG PUSCH configuration, which includes an indication of an applicable symbol type (e.g., an SBFD symbol). Step S1310 corresponds to step S1020 of receiving the resource type configuration, and step SS1320 corresponds to step S1010 of receiving the uplink transmission configuration, and their time order may be exchanged as described above. In step S1335 (as part of the determination from step S1030), the UE checks whether the CG PUSCH instance overlaps with a SBFD symbol (or multiple symbols). If not, the UE does not send a CG PUSCH at a time instance that overlaps with a SBFD symbol (step 1341). If so, the UE initiates performing an uplink transmission, which may include further testing, such as checking further rules to determine whether to send a CG PUSCH at the instance (step 1342). For example, if the UE has received another DCI to schedule DL reception at this symbol, the UE shall not send a CG PUSCH transmission.

[0173] exist Fig.14 The corresponding method steps of the gNB are shown in . In step S1410, the gNB indicates the time pattern of SBFD symbols to the UE in the resource type configuration. In step S1430, the gNB provides the UE with a CG PUSCH configuration as a semi-static transmission configuration, which CG PUSCH configuration includes an indication of the applicable symbol type (e.g., SBFD symbol). In step S1435, the gNB determines whether the CG PUSCH instance overlaps with the SBFD symbol. If not, the gNB does not expect to receive a CG PUSCH from the UE at this instance (step S1451). If yes, the gNB can prepare to receive a CG PUSCH transmission, where it can check further rules to determine whether a CG PUSCH is expected at this instance (step 1452). For example, if the gNB has already sent another DCI to schedule DL reception at this symbol, the gNB will not expect to receive a CG PUSCH from the UE.

[0174] Fig.13 and Fig.14 An example is shown where the applicable resource type for CG PUSCH transmission is SBFD (full duplex). Fig.13 and 14 The method steps shown in can also be performed for "uplink" (SBFD not allowed) as the applicable resource (e.g. symbol) type. In this case, Fig.13 Steps S1320 and S1335 and Fig.14 The "SBFD symbols" in steps S1420 and S1435 may be replaced by the "uplink symbols" in steps S1320 and S1335, respectively.

[0175] In the above example, the type indicator indicates whether the semi-statically configured transmission is (i) full-duplex or (ii) a time resource for an uplink in which full-duplex is disabled, and the resource type configuration includes a time mode for the full-duplex time resource. However, as will be further described in the following example, other information may be used to indicate the suitability of a time resource for a certain resource type for uplink transmission.

[0176] Conflict and non-conflict resources

[0177] Hereinafter, a method of the present disclosure will be described in which the UE is not required to know the explicit definition of "SBFD symbol" or "full-duplex time resource" and "uplink symbol". Instead, the UE is configured with a first semi-static time slot format and a second semi-static time slot format. For example, in an NR system, the second semi-static time slot format may be provided as an additional semi-static time slot (e.g., "Rel-18 time slot format") format to the "legacy" cell common time slot format used in Rel-15 / 16 / 17.

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

[0179] 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 (e.g., conflicting symbol directions between the first "legacy" semi-static slot format and the new Rel-18 semi-static slot format, such as D->U and D->F), and

[0180] ii) a non-conflicting resource type, wherein the first time slot format indicates the second time resource as a flexible resource, or wherein the corresponding indications of the second time resource in the first time slot format and the second time slot format are the same (e.g., the non-conflicting symbol directions between the first semi-static time slot format and the second semi-static time slot format mentioned above, such as U->U, F->U and F->F).

[0181] Therefore, the UE can receive a combination of two semi-static time slot formats as shown in Table 1 below.

[0182]

[0183]

[0184] Table 1

[0185] Similar to the above method with full-duplex and non-full-duplex uplink as symbol types, a type indicator (e.g., a label or tag) or a resource type indicator may be provided in a semi-static transmission (e.g., a CG PUSCH configuration) to indicate the applicable symbol type or resource type, such as whether the CG PUSCH or other semi-statically configured transmission is applicable to conflicting symbols or non-conflicting symbols. If no type indicator is provided in the transmission configuration, the UE (e.g., using UE circuit 880) may determine that the semi-statically configured uplink transmission is applicable to both (conflicting and non-conflicting) types.

[0186] As an alternative to a type indicator, 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, as an example of a "first" uplink transmission configuration type, in addition to any legacy (Rel-15 / 16 / 17) CG configuration types as examples of a "second" uplink transmission configuration type, a "Rel-18CG PUSCH configuration type" may be introduced. In the determination by the communication device and base station whether the resource type is applicable to the configured uplink transmission, the following rule may be applied: legacy configuration types apply to non-conflicting time resources (e.g., symbols), while Rel-18 transmission types apply to conflicting time resources. An explicit type indicator may be provided in the configuration, but need not be provided, as the UE may use other indications (e.g., the format of the configuration or configuration signaling) to determine the configuration type.

[0187] In the present method where the resource type is determined as conflicting or non-conflicting, the conflicting symbols with the conflicting direction configuration in the first and second slot configurations may correspond to SBFD operation symbols on the gNB side as a resource type that allows subband duplex operation. For example, the gNB may allocate conflicting symbols for full-duplex operation. However, the UE does not need to know whether SBFD is actually performed.

[0188] Semi-static and dynamic transport configuration

[0189] Hereinafter, a method will be described in which a configuration type (e.g., "Rel-18 CG PUSCH configuration type") is introduced as in the above-mentioned method of using conflicting and non-conflicting time resources. The applicable resource type is distinguished from the dynamic F symbol indicated by the DCI and the dynamic U symbol indicated by the DCI. For example, the DCI is a group common DCI such as DCI 2_0, or a dedicated DCI without actual PDSCH / PUSCH allocation.

[0190] In some embodiments, the resource type configuration includes a semi-statically configured time slot format, and in addition to the semi-statically configured time slot format in the transmission configuration, the UE (e.g., using a UE transceiver) also receives a dynamically configured time slot format. The dynamically configured time slot format can be sent by the base station in a DCI (e.g., DCI 2_0).

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

[0192] If the semi-statically configured time slot format indicates the second time resource as a flexible resource and the dynamically configured time 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.

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

[0194] In the above method, the type indicator in the semi-static transmission configuration is provided as the applicability information. In the present method, the dynamically configured time slot format is provided as a kind of applicability information, which indicates whether the semi-statically configured transmission is applicable to the resource type of the semi-statically configured time slot format.

[0195] For example, with an uplink transmission configuration having 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., DCI 2_0), and if the dynamic SFI indicates a dynamic slot format (having a value other than 255), then the Rel-18 CG PUSCH configuration applies only to the dynamically configured F symbols, such as Fig.15 The upper part of is shown for symbols in time slots #1, #2 and #3.

[0196] If the dynamic SFI indicates 255 (meaning to ignore the dynamic SFI) or the UE is otherwise configured (e.g., by semi-static configuration) not to monitor the dynamic SFI, then the (e.g., Rel-18 CG PUSCH) uplink transmission configuration applies to both semi-statically configured U symbols and semi-statically configured F symbols, as Fig.15 as shown in the lower part of .

[0197] For example, if both of the following conditions (the first condition and the case separated by at least an "or" of the second condition) apply, then the semi-statically configured uplink transmission is applicable to the second time resource: if the resource type configuration includes defining the resource type of the second time resource as a flexible semi-statically configured time slot format, and if the transceiver receives a configuration that ignores the configuration of the time slot format for dynamic indication of the second time resource (e.g., a value of 255 in the SFI) or a parameter indicating that the configuration of the time slot format for dynamic indication of the second time resource is not configured to the UE. In the latter case, an example of such an indication may be that an sfi-RNTI (Radio Network Temporary Identifier) ​​value is not provided to the communication device 860, or a control resource set for DCI format 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.

[0198] In the above description, "Rel-18 CG PUSCH configuration type" has been mentioned as an example of a first uplink transmission configuration type for a first uplink transmission configuration, and the first uplink transmission configuration may be configurable in addition to a second uplink transmission type for a second uplink transmission (e.g., "legacy" / Rel 15-17CG PUSCH configuration).

[0199] 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, the second semi-statically configured uplink transmission being applicable to a second resource type as an associated resource type. If the third time resource overlaps with the second time resource, the second semi-statically configured uplink transmission is applicable to the resource type of the second time resource, the semi-statically configured time slot format indicates the second time resource as a flexible resource, and the dynamically configured time slot format indicates the second time resource as an uplink resource.

[0200] For example, for the legacy CG PUSCH configuration, the following rules apply: The UE is allowed to send CGPUSCH on the following symbols:

[0201] On a semi-statically configured U symbol (as a "third" time resource), such as Fig.15 Time slot #5 shown in the upper part.

[0202] If the UE is not configured to monitor SFI, then on the semi-statically configured F symbol, such as Fig.15 as shown in the lower part of .

[0203] In addition, according to the rules, for semi-statically configured F symbols, if the UE is configured to monitor SFI, the following applies: (i) if the SFI indicates a value other than 255, the UE is allowed to send CG PUSCH on dynamic U symbols (such as Fig.15 (i) If the UE misses the SFI (e.g., reception of the SFI fails), the UE determines whether to send or not according to the parameter "enableconfiguredUL" provided by the RRC signaling. In more detail, if enableconfiguredUL is configured to be "enabled", the UE is allowed to send an uplink signal / channel (e.g., CG PUSCH) in a symbol set of a time slot when the UE does not detect DCI format 2_0 that provides a dynamic time slot format for the symbol set.

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

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

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

[0207] Zero and non-zero N TA Offset

[0208] According to the present method, the resource type applicable to the semi-statically configured uplink transmission is a resource type with a zero timing advance offset (eg, a resource type with a zero value N TA,offset symbol) and a resource type with a non-zero timing advance offset (e.g., with a non-zero value N TA,offset ) is one of the symbols.

[0209] For example, a symbol or symbols are configured with a zero value N TA,offset . Zero value N TA,offset This configuration can be done semi-statically (eg, via RRC) or dynamically (via DCI).

[0210] Timing Advance Offset N TA,offset Used to adjust the timing difference between uplink and downlink transmissions. An uplink transmission occurs before the corresponding downlink transmission is received (N TA +N TA,offset )×T c . N TA Used to ensure that uplink transmissions from the UE are synchronized when received by the gNB. N TA,offset Used to reserve the switching time from UL to DL. C is the basic time unit of NR (e.g. T C =1 / (480000×4096) seconds).

[0211] In a similar manner as described for the resource types above, a resource type indicator (e.g., a tag or label) may be provided in a semi-static transmission configuration (e.g., a CG PUSCH configuration) to indicate that the configured uplink transmission is for a tx with zero timing advance offset N. TA,offset The time resources (e.g., symbols) of TA,offset time resources (e.g., symbols).

[0212] In addition, with zero value N TA,offset The symbol may correspond to an SBFD operation symbol on the gNB side which is a symbol type allowing subband duplexing, and the UE does not need to know whether SBFD is actually performed on the corresponding symbol.

[0213] The present disclosure and various methods and embodiments described herein provide techniques by which uplink transmissions (e.g., CG PUSCH instances) with semi-static configurations thereof can be sent or dropped (e.g., skipped) in a controlled manner. In addition, such control of performing or skipping semi-statically configured transmissions is facilitated without imposing restrictions on the periodicity and SBFD time domain pattern for aligning the CG PUSCH on the gNB side. For example, by indicating the time resource type of a time resource as allowing subband duplexing, interference with CG type uplink transmissions can be prevented if the (semi-static) CG transmission configuration is not applicable to the resource type of the allowed uplink transmission.

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

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

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

[0217] In the present disclosure, a base station may be, for example, a transmit receive point (TRP), a cluster head, an access point, a remote radio head (RRH), an eNodeB (eNB), a gNodeB (gNB), a base station (BS), a base transceiver station (BTS), a base station unit, or a gateway. In addition, in sidelink communication, a terminal may be used instead of a base station. A base station may be a relay device that relays communication between a higher node and a terminal. A base station may also be a roadside unit.

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

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

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

[0221] The present disclosure may be applied to any one of a data channel and a control channel. The channels in the present disclosure may be replaced by data channels including PDSCH, PUSCH and PSSCH and / or control channels including PDCCH, PUCCH, PBCH, PSCCH and PSBCH.

[0222] In the present disclosure, a reference signal is a signal known to both a base station and a mobile station, and each reference signal may be referred to as a reference signal (RS) or sometimes referred to as a pilot signal. The reference signal may be any one of a DMRS, a channel state information reference signal (CSI-RS), a tracking reference signal (TRS), a phase tracking reference signal (PTRS), a cell-specific reference signal (CRS), and a sounding reference signal (SRS).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0236] In summary, according to a first aspect, a communication device is provided, comprising: a transceiver, which receives a transmission configuration and a resource type configuration, wherein the transmission configuration defines a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type, and the resource type configuration defines a resource type for a second time resource; and a circuit, which determines whether to initiate execution or skip the semi-statically configured uplink transmission on 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 if 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 on the first time resource, and the transceiver executes or skips the semi-statically configured uplink transmission on the first time resource based on the determined result.

[0237] According to a second aspect that can be provided in combination with the first aspect, the transceiver receives: a first transmission configuration, which defines a first time resource allocated for an uplink transmission of a first semi-static configuration applicable to a first resource type as the associated resource type; and a second transmission configuration, which defines a third time resource allocated for an uplink transmission of a second semi-static configuration applicable to a second resource type as the associated resource type, and wherein the uplink transmission of the first semi-static configuration is not applicable to the second resource type.

[0238] According to a third aspect which may be provided in combination with the first or second aspect, the transmission configuration comprises a resource type indicator indicating a type of an associated resource.

[0239] According to a fourth aspect that can be provided in combination with any one of the first to third aspects, the resource type applicable to the semi-statically configured uplink transmission is one of a resource type allowing sub-band duplexing and a resource type prohibiting sub-band duplexing.

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

[0241] According to a sixth aspect that can be provided in combination with any one of the first to third aspects, the resource type applicable to the semi-statically configured uplink transmission is one of a resource type with a zero timing advance offset and a resource type with a non-zero timing advance offset.

[0242] According to the seventh aspect that can be provided in combination with the first aspect, the resource type configuration includes a semi-statically configured time slot format; the transceiver receives a dynamically configured time slot format; each of the semi-statically configured time slot format and the dynamically configured time slot format indicates the resource type of the second time resource as uplink, downlink or flexible; and if the semi-statically configured time slot format indicates the second time resource as a flexible resource and the dynamically configured time 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.

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

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

[0245] According to the tenth aspect which can be provided in combination with the first aspect or the second aspect, the semi-statically configured uplink transmission is applicable to the second time resource in the following circumstances: if the resource type configuration includes defining the resource type of the second time resource as a flexible semi-statically configured time slot format; and if the transceiver receives a configuration that ignores a dynamic indication of the time slot format for the second time resource, or a parameter indicating that the configuration of the dynamic indication of the time slot format for the second time resource is not configured to the communication device.

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

[0247] According to the twelfth aspect which can be provided in combination with any one of the first to eleventh aspects, if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is applicable to the resource type of the second time resource, the circuit determines to initiate execution of the semi-statically configured uplink transmission on the first time resource.

[0248] According to the thirteenth aspect, there is provided a base station, comprising: a circuit that generates a transmission configuration and a resource type configuration, wherein the transmission configuration defines a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type, and the resource type configuration defines a resource type of a second time resource; and a transceiver that sends the transmission configuration and the resource type configuration. The circuit determines whether to initiate or skip receiving the semi-statically configured uplink transmission on the first time resource based on the transmission configuration and the resource type configuration; if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, it is determined to skip receiving the semi-statically configured uplink transmission on the first time resource; and the transceiver executes or skips receiving the semi-statically configured uplink transmission on the first time resource according to the determined result.

[0249] According to a fourteenth aspect which may be provided in combination with the thirteenth aspect, the circuit determines that when allocating the first time resource for sub-band duplex operation, the communication device is to skip the semi-statically configured uplink transmission on the first time resource.

[0250] According to the fifteenth aspect, a communication method is provided, comprising the following steps to be performed by a communication device: receiving a transmission configuration, the transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type; receiving a resource type configuration, the resource type configuration defining a resource type of a second time resource; based on the transmission configuration and the resource type configuration, determining whether to initiate execution or skip the semi-statically configured uplink transmission on the first time resource, wherein if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, determining to skip the semi-statically configured uplink transmission on the first time resource; and executing or skipping the semi-statically configured uplink transmission based on the determined result.

[0251] According to the sixteenth aspect, a communication method for a base station is provided, comprising the following steps to be performed by the base station: generating a transmission configuration, the transmission configuration defining a first time resource allocated for an uplink transmission for a semi-static configuration applicable to an associated resource type; sending the transmission configuration; generating a resource type configuration, the resource type configuration defining a resource type for a second time resource; sending the resource type configuration; based on the transmission configuration and the resource type configuration, determining whether to initiate or skip receiving an uplink transmission for the semi-static configuration on the first time resource, wherein if the first time resource overlaps with the second time resource and if the uplink transmission for the semi-static configuration is not applicable to the resource type of the second time resource, determining to skip receiving the uplink transmission for the semi-static configuration on the first time resource; sending the resource type configuration; and based on the determined result, executing or skipping receiving the uplink transmission for the semi-static configuration on the first time resource.

[0252] Also provided is an integrated circuit configured to control a communication device to execute the method according to the fifteenth aspect; and an integrated circuit for controlling a base station to execute the communication method according to the sixteenth aspect.

[0253] Furthermore, a non-transitory medium storing program instructions is provided, which, when executed on a processing circuit such as a general-purpose processor, causes the processing circuit to perform all the steps of the above method embodiments or aspects.

Claims

1. A communication device, comprising: a transceiver that receives a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type and a resource type configuration defining a resource type for a second time resource; as well as circuitry that determines whether to initiate or skip the semi-statically configured uplink transmission on 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 if 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 on the first time resource, and The transceiver performs or skips the semi-statically configured uplink transmission on the first time resource according to the determined result.

2. The communication device according to claim 1, wherein: The transceiver receives: a first transmission configuration defining a first time resource for an uplink transmission allocation applicable to a first semi-static configuration of a first resource type being the associated resource type, and 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, and wherein the first semi-statically configured uplink transmission is not applicable to the second resource type.

3. The communication device according to claim 1 or 2, wherein: The transmission configuration includes a resource type indicator indicating a type of associated resource.

4. The communication device according to any one of claims 1 to 3, wherein: The resource type applicable to the semi-statically configured uplink transmission is one of a resource type allowing sub-band duplexing and a resource type prohibiting sub-band duplexing.

5. The communication device according to any one of claims 1 to 3, wherein: The resource type configuration includes a first time slot format and a second time slot format, each of the first time slot format and the second time slot format specifies the second time resource as uplink, downlink or flexible, and the resource type applicable to the semi-statically configured uplink transmission is one of the following: i) a conflicting resource type, wherein the first time slot format indicates the second time resource as a downlink resource, and the second time slot format indicates the second time resource as an uplink resource or a flexible resource, and ii) a non-conflicting resource type, wherein the first time slot format indicates the second time resource as a flexible resource, or wherein the corresponding indications of the second time resource in the first time slot format and the second time slot format are the same.

6. The communication device according to any one of claims 1 to 3, wherein: The resource type applicable to the semi-statically configured uplink transmission is one of a resource type with a zero timing advance offset and a resource type with a non-zero timing advance offset.

7. The communication device according to claim 1, wherein: The resource type configuration includes a semi-statically configured time slot format, the transceiver receiving the dynamically configured time slot format, Each of the semi-statically configured time slot format and the dynamically configured time slot format indicates a resource type of the second time resource as uplink, downlink, or flexible, and If the semi-statically configured time slot format indicates the second time resource as a flexible resource and the dynamically configured time 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.

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

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

10. The communication device according to claim 1 or 2, wherein: In the following cases, the semi-statically configured uplink transmission is applicable to the second time resource: If the resource type configuration includes defining the resource type of the second time resource as a flexible semi-statically configured time slot format, and If the transceiver receives a configuration to ignore the dynamically indicated time slot format for the second time resource, or a parameter indicating that the configuration of the dynamically indicated time slot format for the second time resource is not configured to the communication device.

11. The method according to claim 1 or 2, wherein: The transceiver receives applicability information indicating whether the semi-statically configured uplink transmission is applicable to a resource type of the second time resource.

12. The communication device according to any one of claims 1 to 11, wherein: The semi-statically configured uplink transmission is an uplink transmission without a dynamic grant.

13. The communication device according to any one of claims 1 to 11, wherein: If the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is applicable to the resource type of the second time resource, the circuit determines to initiate performing the semi-statically configured uplink transmission on the first time resource.

14. A base station, comprising: circuitry that generates a transmission configuration defining a first time resource allocated for uplink transmissions applicable to a semi-static configuration of an associated resource type and a resource type configuration defining a resource type for a second time resource, and a transceiver that sends the transmission configuration and the resource type configuration, wherein the circuit determines whether to initiate or skip receiving the semi-statically configured uplink transmission on 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 if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, determining to skip receiving the semi-statically configured uplink transmission on the first time resource, and The transceiver performs or skips receiving the semi-statically configured uplink transmission on the first time resource according to the determined result.

15. The base station according to claim 14, wherein: The circuit determines that the communications device is to skip the semi-statically configured uplink transmission on the first time resource when the first time resource is allocated for sub-band duplex operation.

16. A communication method, comprising the following steps performed by a communication device: receiving a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type; receiving a resource type configuration, the resource type configuration defining a resource type of a second time resource; determining whether to initiate or skip the semi-statically configured uplink transmission on 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 if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, determining to skip the semi-statically configured uplink transmission on the first time resource; as well as According to the determined result, the semi-statically configured uplink transmission is performed or skipped.

17. A communication method, comprising the following steps to be performed by a base station: generating a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type; sending the transmission configuration; generating a resource type configuration, wherein the resource type configuration defines a resource type of a second time resource; Sending the resource type configuration; determining, based on the transmission configuration and the resource type configuration, whether to initiate or skip receiving the semi-statically configured uplink transmission on the first time resource; Wherein, if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, determining to skip receiving the semi-statically configured uplink transmission on the first time resource; sending the resource type configuration; and Receiving the semi-statically configured uplink transmission on the first time resource is performed or skipped according to the determined result.

18. An integrated circuit causing a communication device to perform the following steps: receiving a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type; receiving a resource type configuration, the resource type configuration defining a resource type of a second time resource; determining whether to initiate or skip the semi-statically configured uplink transmission on 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 if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, determining to skip the semi-statically configured uplink transmission on the first time resource; as well as According to the determined result, uplink transmission in the semi-static configuration is performed or skipped.

19. An integrated circuit causing a base station to perform the following steps: generating a transmission configuration defining a first time resource allocated for a semi-statically configured uplink transmission applicable to an associated resource type; sending the transmission configuration; generating a resource type configuration, wherein the resource type configuration defines a resource type of a second time resource; Sending the resource type configuration; determining, based on the transmission configuration and the resource type configuration, whether to initiate or skip receiving the semi-statically configured uplink transmission on the first time resource; Wherein, if the first time resource overlaps with the second time resource and if the semi-statically configured uplink transmission is not applicable to the resource type of the second time resource, determining to skip receiving the semi-statically configured uplink transmission on the first time resource; sending the resource type configuration; and Receiving the semi-statically configured uplink transmission on the first time resource is performed or skipped according to the determined result.

Images