Coordination for cross-link interference processing.

Abstract

The present disclosure provides a communications apparatus and a communications method for cooperation for crosslink interference processing, wherein the communications apparatus is a base station including: a circuit configured, in operation, to generate a signal including information of a plurality of sets of slot formats for one or more serving cells, wherein each set of slot formats of the plurality of sets corresponds to a plurality of frequency segments of each serving cell of the one or more serving cells; and a transmitter, in operation, to transmit the signal to one or more second base stations.

Description

[Technical Field]

[0001] The following disclosure relates to a communication device and a communication method for cooperation with other communication devices, and more particularly to cooperation between gNBs (base stations) for handling crosslink interference (CLI). [Background technology]

[0002] A Release 18 Study Item (SI) entitled "Study on evolution of near-radio (NR) duplex operation" has been approved in RAN#94-e [RP-213591]. One of the main topics is to explore how to enable subband non-overlapping full duplex (SBFD) within legacy time division duplex (TDD) bands. This allows downlink (DL) and uplink (UL) to coexist within legacy TDD bands, where subbands are used to separate the transmission directions.

[0003] However, when SBFD is used, different TDD DL / UL patterns used between neighboring gNBs (e.g., UL transmission in one gNB and DL reception in another neighboring gNB) may interfere with each other and cause crosslink interference (CLI). This inter-gNB CLI is an important issue that needs to be addressed, but there is no concrete solution yet on how to achieve inter-gNB coordination for handling inter-gNB CLI in SBFD operation.

[0004] Therefore, there is a need for a communication apparatus and method for inter-gNB coordination for CLI processing that solves the above problems. Furthermore, other desirable features and characteristics will become apparent from the following detailed description and the appended claims, taken in conjunction with the accompanying drawings and the background art of this disclosure. Summary of the Invention

[0005] The non-limiting and exemplary embodiments contribute to providing a communication device and a communication method for inter-gNB coordination for inter-gNB CLI processing.

[0006] In a first aspect, the present disclosure provides a first base station, the first base station comprising: circuitry configured, upon operation, to generate a signal including information of a plurality of sets of slot formats for one or more serving cells, each set of slot formats corresponding to a plurality of frequency segments of each serving cell of the one or more serving cells; and a transmitter, upon operation, to transmit the signal to one or more second base stations.

[0007] In a second aspect, the present disclosure provides a second base station, the second base station comprising: a receiver configured, in operation, to receive a signal from a first base station, the signal including information of a plurality of sets of slot formats, each set of slot formats corresponding to a plurality of frequency segments of each serving cell of one or more serving cells; and a circuit configured, in operation, to perform a scheduling procedure based on the information.

[0008] In a third aspect, the present disclosure provides a third base station, the third base station being associated with a first serving cell and one or more second serving cells, the third base station comprising: a circuit configured, in operation, to generate a signal including information of a set of slot formats for the first serving cell, the set of slot formats corresponding to a plurality of frequency segments of the first serving cell; and a transmitter, in operation, to transmit the signal to the one or more second serving cells.

[0009] In a fourth aspect, the present disclosure provides a communication method, the communication method including: generating a signal including information of a plurality of sets of slot formats for one or more serving cells, each set of slot formats of the plurality of sets of slot formats corresponding to one of a plurality of frequency bands of each serving cell of the one or more serving cells; and transmitting the signal to one or more second base stations.

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

[0011] In the accompanying drawings, where like reference characters refer to the same or functionally similar elements throughout the separate views, the drawings, together with the following detailed description, which are incorporated into and form a part of this specification, illustrate various embodiments and serve to explain various principles and advantages according to the present embodiments. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram of an example architecture of a 3GPP Next Generation Radio Access Network (NG-RAN) to which example embodiments of the present disclosure may be applied; [Figure 2] FIG. 1 is a schematic diagram illustrating the division of functions between NG-RAN and 5GC to which exemplary embodiments of the present disclosure may be applied. [Figure 3] FIG. 1 is a sequence diagram of a Radio Resource Control (RRC) connection setup / reconfiguration procedure to which an exemplary embodiment of the present disclosure can be applied. [Figure 4]1 is a schematic diagram illustrating usage scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC), to which exemplary embodiments of the present disclosure may be applied. [Figure 5] Block diagram illustrating an exemplary 5G system architecture for vehicle-to-everything (V2X) communications in a non-roaming scenario [Figure 6] Diagram showing the configuration update procedure between two gNBs [Figure 7] Schematic diagram showing the overall architecture of NG-RAN and 5GC, where the gNB is shown in a split gNB scenario, including a gNB central unit (gNB-CU) and multiple gNB distributed units (gNB-DUs). [Figure 8] A diagram showing the configuration update procedure between the gNB distributed unit (gNB-DU) and the gNB central unit (gNB-CU) in a split gNB scenario. [Figure 9] Two block diagrams showing legacy (Release 15 / 16 / 17) Time Division Duplex (TDD) and Release 18 Sub-Band Non-Overlapping Full Duplex (SBFD), respectively. [Figure 10] Diagram showing an example of gNB cooperation with conventional cross-link interference (CLI) [Figure 11A] Diagram showing the legacy TDD format used in inter-gNB cooperation for inter-gNB CLI processing in Release 16 [Figure 11B] FIG. 1 illustrates an example TDD format used in inter-gNB cooperation according to various embodiments of the present disclosure for inter-gNB CLI processing. [Figure 12] 1 is a schematic example of a communication device according to various embodiments; [Figure 13] 1 is a flowchart illustrating a communication method implemented by a first communication device according to various embodiments of the present disclosure. [Figure 14A] FIG. 1 is a block diagram illustrating an example TDD band with fully overlapping / shared subband allocation in inter-gNB cooperation for inter-gNB CLI processing according to a first embodiment of the present disclosure. [Figure 14B] FIG. 10 is a block diagram illustrating an example TDD band with partially overlapping / shared subband allocation for inter-gNB cooperation for inter-gNB CLI processing according to a second embodiment of the present disclosure. [Figure 15] 1 is a flowchart illustrating a first exemplary inter-gNB coordination process for gNB CLI processing according to a first embodiment of the present disclosure. [Figure 16] 1 is a flowchart illustrating a second exemplary inter-gNB coordination process for gNB CLI processing according to a first embodiment of the present disclosure. [Figure 17] 10 is a flowchart illustrating a third exemplary inter-gNB coordination process for gNB CLI processing according to the first embodiment of the present disclosure. [Figure 18] FIG. 1 is a block diagram illustrating an example TDD band with a new quasi-static slot format for inter-gNB cooperation for gNB CLU processing, according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] Those skilled in the art will appreciate that the elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures, block diagrams, or flowcharts may be exaggerated relative to other elements to allow an accurate understanding of the embodiments.

[0014] Some embodiments of the present disclosure will now be described, by way of example only, with reference to the drawings in which like reference numbers and letters indicate similar or equivalent elements.

[0015] 3GPP continues to work on the next release of fifth-generation cellular technology (simply referred to as 5G), which includes the development of New Radio Access Technology (NR), which will operate in frequencies up to 100 GHz. The first version of the 5G standard was completed in late 2017, allowing for the prototyping and commercial deployment of smartphones compliant with the 5G NR standard to proceed.

[0016] The second version of the 5G standard was finalized in June 2020, further expanding 5G's reach to new services, spectrum, and deployments such as unlicensed spectrum (NR-U), non-public networks (NPN), time-sensitive networking (TSN), and cellular V2X.

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

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

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

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

[0021] SL supports direct UE-to-UE communication using SL resource allocation modes, physical layer signals / channels, and physical layer procedures. Two New Radio (NR) SL resource allocation modes are supported: (a) Mode 1, in which NR SL resource allocation is provided by the network, and (b) Mode 2, in which the UE determines the NR SL transmission resources in a resource pool. Two SL resource allocation modes are applicable to LTE V2X: (a) Mode 3, in which LTE SL resource allocation is scheduled by the eNB primarily for the transmission of periodically occurring messages, and (b) Mode 4, in which the UE autonomously determines the LTE SL transmission resources in a resource pool.

[0022] The PSCCH indicates the resources and other transmission parameters used by the UE for the PSSCH. PSCCH transmission is associated with a Demodulation Reference Signal (DM-RS). The PSSCH transmits transport blocks (TBs) of the data itself and control information such as for HARQ procedures and channel state information (CSI) feedback triggers. At least six Orthogonal Frequency Division Multiplexing (OFDM) symbols within a slot are used for PSSCH transmission. The PSSCH transmission is associated with the DM-RS and may also be associated with a Phase-Tracking Reference Signal (PT-RS).

[0023] The PSFCH carries HARQ feedback over the SL from the UE that is the intended recipient of the PSSCH transmission to the UE that performed the transmission. The PSFCH sequence is transmitted in one PRB that is repeated across two OFDM symbols near the end of the SL resource of the slot.

[0024] The SL synchronization signal consists of the SL Primary Synchronization Signal (S-PSS) and the SL Secondary Synchronization Signal (S-SSS), which occupy 2 symbols and 127 subcarriers, respectively. The Physical Sidelink Broadcast Channel (PSBCH) occupies 9 symbols and 5 symbols in the normal and extended cyclic prefix cases, respectively, and contains the associated demodulation reference signal (DM-RS).

[0025] Regarding the physical layer procedure for HARQ feedback in the sidelink, SL HARQ feedback uses the PSFCH and can be performed in one of two options: In one option, which can be set to unicast and groupcast, the PSFCH transmits either an ACK or a NACK using resources dedicated to a single UE transmitting the PSFCH; in the other option, which can be set to groupcast, the PSFCH transmits a NACK on resources that can be shared by multiple UEs transmitting the PSFCH, or no PSFCH signal is transmitted.

[0026] In SL resource allocation mode 1, a UE that receives a PSFCH can report SL HARQ feedback to the gNB via a PUCCH or PUSCH.

[0027] Regarding physical layer procedures for power control in the sidelink, in the case of in-coverage operation, the power spectral density of SL transmissions may be adjusted based on the path loss from the gNB, while in the case of unicast, the power spectral density of some SL transmissions may be adjusted based on the path loss between two communicating UEs.

[0028] Regarding the physical layer procedure for CSI reporting, in the unicast case, the channel state information reference signal (CSI-RS) is supported for CSI measurement and CSI reporting in the sidelink. The CSI report is carried in the SL MAC CE.

[0029] For sidelink measurements, the following UE measurements are supported: PSBCH Reference Signal Received Power (PSBCH RSRP); PSSCH Reference Signal Received Power (PSSCH-RSRP); PSCCH Reference Signal Received Power (PSCCH-RSRP); Sidelink Received Signal Strength Indicator (SL RSSI); Sidelink Channel Occupancy Ratio (SL CR); Sidelink Channel Busy Ratio (SL CBR)

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

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

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

[0033] 2 shows a functional division between NG-RAN and 5GC to which exemplary embodiments of the present disclosure can be applied. The logical node of NG-RAN is gNB or ng-eNB. The 5GC has logical nodes AMF, UPF, and SMF.

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

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

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

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

[0038] Figure 3 shows some of the interactions between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see TS 38.300 v16.3.0). The transition steps are as follows: 1. The UE requests to set up a new connection from the RRC_IDLE state. 2 / 2a. The gNB completes the RRC setup procedure. Note: Scenarios in which the gNB rejects a request are described below. 3. The first NAS message from the UE, piggybacked in RRCSetupComplete, is sent to the AMF. 4 / 4a / 5 / 5a. Additional NAS messages may be exchanged between the UE and the AMF. See TS 23.502. 6. The AMF prepares and sends UE context data (including PDU session context, security keys, UE radio capabilities, and UE security capabilities, etc.) to the gNB. 7 / 7a. The gNB activates AS security with the UE. 8 / 8a. The gNB performs reconfiguration to set up SRB2 and DRB. 9. The gNB notifies the AMF that the setup procedure is complete.

[0039] RRC is a higher layer signaling protocol used to configure the UE and the gNB. Specifically, in this transition, the AMF creates UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sends it to the gNB via an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE by sending a SecurityModeCommand message to the UE, and the UE responds with a SecurityModeComplete message. The gNB then performs reconfiguration to establish signaling radio bearer 2 (SRB2) and data radio bearers (DRBs) by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete message from the UE in response. For signaling-only connections, the RRCReconfiguration step is omitted because SRB2 and DRBs are not set up. Finally, the gNB notifies the AMF that the establishment procedure is complete via an INITIAL CONTEXT SETUP RESPONSE.

[0040] Figure 4 shows some use cases for 5G NR. The Third Generation Partnership Project on Radio (3GPP NR) considers three use cases envisioned for IMT-2020 to support a wide variety of services and applications. Phase 1 specifications for enhanced mobile broadband (eMBB) have been finalized. Current and upcoming work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to further extending eMBB support. Figure 4 shows some example IMT usage scenarios envisioned for 2020 and beyond (see, for example, Figure 2 in ITU-R M.2083).

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

[0042] From a physical layer perspective, there are several ways to improve reliability. Current scope for reliability improvement includes defining a separate CQI table for URLLC, a more compact DCI format, repeated PDCCH transmission, etc. However, as NR becomes more stable and developed (a key requirement for NR URLLC), the scope for achieving ultra-high reliability may increase. Specific use cases for NR URLLC in Rel. 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

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

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

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

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

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

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

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

[0050] Figure 5 shows the 5G NR non-roaming reference architecture (see Section 4.2.1.1 of TS 23.287 v16.4.0). An Application Function (AF) (e.g., an external application server hosting 5G services, as illustrated in Figure 4) interacts with the 3GPP core network to support service provision, e.g., application influence on traffic routing, access to the Network Exposure Function (NEF), or interaction with a policy framework (see Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on the operator's deployment, Application Functions (AFs) deemed trusted by the operator can be allowed to interact directly with the relevant Network Functions. Application Functions (AFs) not permitted by the operator to directly access Network Functions interact with the relevant Network Functions using an external exposure framework via the NEF.

[0051] Figure 5 further illustrates additional functional units of the 5G architecture for V2X communication, namely, Unified Data Management (UDM), Policy Control Function (PCF), Network Exposure Function (NEF), Application Function (AF), Unified Data Repository (UDR), Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF) in 5G, as well as the V2X Application Server (V2AS) and Data Network (DN; e.g., operator-provided services, internet access, or third-party services). All or part of the core network functions and application services may be located and executed in a cloud computing environment.

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

[0053] Figure 6 illustrates a configuration update procedure between two Next Generation Radio Access Network (NG-RAN) nodes 602, 604. The configuration update procedure is for updating the configuration messages required for two NG-RAN nodes to interoperate correctly over the Xn-C interface. NG-RAN Logical Node 1 (also referred to as gNB or ng-eNB) first initiates the configuration update procedure by sending an NG-RAN Configuration Update message to its peer NG-RAN Node 2. NG-RAN Node 2 returns a gNB-DU Configuration Update Response message to acknowledge that it has successfully updated its configuration data. If NG-RAN Node 2 is unable to accept the update, it shall respond with an NG-RAN Node Configuration Update Failure message and an appropriate cause value.

[0054] FIG. 7 shows a schematic diagram 700 illustrating the overall architecture of NG-RAN and 5GC, in which a gNB is shown in a split gNB scenario, including a gNB central unit (gNB-CU) and multiple gNB distributed units (gNB-DUs). NG-RAN 700 comprises a set of gNBs (e.g., gNBs 702, 704) connected to a 5GC 706 via an NG interface. The set of gNBs 702, 704 are interconnected via an Xn interface. A gNB (e.g., gNB 704) may consist of a gNB-CU 708 and one or more gNB-DUs 710, 712. The gNB-CU 708 and gNB-DUs 710, 712 are connected via an F1 interface. One gNB-DU 710, 712 is connected to only one gNB-CU 708. NG, Xn, and F1 are logical interfaces.

[0055] Figure 8 shows a diagram 800 illustrating the configuration update procedure between a gNB distributed unit (DU) 802 and a gNB central unit (CU) 804. The gNB-DU 802 first initiates the configuration update procedure by sending a gNB-DU Configuration Update message to the gNB-CU containing the appropriate set of updated configuration data to be used for operation. The gNB-CU 804 returns a gNB-DU Configuration Update Response message to acknowledge successful update of the configuration data. The updated configuration data is stored in both nodes 802, 804 and used as long as there is an active Transport Network Layer (TNL) association or until a subsequent update is performed. If the gNB-CU 804 cannot accept the update, it shall instead respond with a gNB-DU Configuration Update Failed (not shown) message and an appropriate cause value.

[0056] As mentioned above, a new Release 18 study item entitled "Study on the Evolution of NR Duplex Operation" has been approved in RAN#94-e [RP-213591], and one of the main topics is to consider how to achieve sub-band non-overlapping full duplex (SBFD) within legacy TDD bands. On the gNB side, (quasi-) full duplexing is performed, and on the UE side, half duplexing can be used.

[0057] FIG. 9 shows an example legacy TDD slot format 902 according to Release 15 / 16 / 17 and an example SBFD or cross-division duplex (XDD) slot format 904 for inter-gNB cooperation. In this example, the legacy TDD band and SBFD / XDD are changed from an initial TDD band of four slots (four different time resource allocations) with slot format “DFFU” upon L1 signaling. Here, slot formats “D,” “U,” and “F” correspond to downlink, uplink, and quasi-static flexible (uplink and / or downlink) communications, respectively. Upon receiving L1 signaling, the second and third slot formats of the legacy TDD band are changed from “F” to “D” and “U,” respectively. In SBFD / XDD, the first three slots of the TDD band (slots n, n+1, and n+2) are divided into three different subbands (three different frequency resource allocations), each with a different slot format upon L1 signaling. In this way, DL and UL can coexist within the legacy TDD band. For example, the first slot formats in the first subband, the second subband, and the third subband are "D," "U," and "D," respectively. The subbands are then used to divide the transmission directions for, for example, three different UEs. For an undivided slot, e.g., slot n+3, a slot format spanning the frequency domain is transmitted in the uplink transmission direction. Here, for example, the slot format "DDUU" in the first subband #1 is transmitted to UE #1, the slot format "UUUU" in the second subband #2 is transmitted to UE #2, and the slot format "DUUU" in the third subband #3 is transmitted to UE #3. This behavior motivates providing more UL time duration to expand UL coverage, reduce latency, and improve UL capacity.

[0058] In TDD, when neighboring cells / gNBs use different TDD DL / UL patterns (slot formats), UL transmissions at one cell / gNB may interfere with DL reception at another cell / gNB, a phenomenon known as cross-link interference (CLI). R1-2204432 acknowledges that the UL performance of small cells with dynamic TDD DL / UL patterns (or dynamic slot formats) is significantly affected by strong gNB-gNB CLI from macro cells with TDD configurations that have a high DL presence. In other words, the affected gNB is significantly affected by the strongest CLI aggressor cell (e.g., the nearest macro gNB). Similar results are observed even when SBFD operation is performed, making inter-gNB CLI a significant issue that must be addressed. Therefore, RP-213591 addresses inter-gNB and inter-UE CLI handling as one of its main topics and identifies solutions to address them.

[0059] In RAN#1109e, several candidate schemes for inter-gNB CLI handling in SBFD operation are proposed for further consideration as follows, where coordinated scheduling schemes are the main focus, and inter-gNB CLI may be adjacent channel CLI, co-channel CLI, or both, depending on the deployment scenario.

[0060] As agreed in RAN1#109e, for consideration of potential extensions to dynamic / flexible TDD and / or SBFD, the following will be considered as potential extensions to gNB to gNB CLI processing, and further prioritization / narrowing of candidate schemes for consideration may occur at future meetings: - gNB to gNB CLI measurement and reporting - Cooperative Scheduling - Expansion of spatial domain - Advanced receiver - UE and gNB transmit and receive timing - Power control based solutions - Potential expansion of Rel-16 RIM - Sensing-based mechanisms - Note: It is necessary to identify whether a particular scheme requires OTA or backhaul information exchange. - Note: Any other inter-gNB CLI handling schemes are not excluded. - Note: For potential extensions to dynamic / flexible TDD and / or SBFD, we will leverage the results of the discussions in Rel-15 and Rel-16, and avoid repeating the same discussions. - NOTE: Potential extensions specific to SBFD are discussed in 9.3.2.

[0061] For inter-gNB CLI handling in TDD, inter-gNB coordination in Release 16 (e.g., TS38.423 v16.10.0) supports exchanging the intended TDD DL-UL configuration via the Xn / F1 interface in a semi-static manner (i.e., semi-static slot format and cell-specific slot format configuration exchanged between gNBs via the higher layer parameter IntendedTDD-DL-ULConfiguration-NR, see Figure 11A). For inter-gNB CLI handling, gNBs need to take this information exchange into account when scheduling their own.

[0062] Although inter-gNB CLI processing in TDD has been discussed, how to achieve inter-gNB coordination for inter-gNB CLI processing in SBFD operation has not been specified. Figure 10 is a schematic diagram showing conventional Release 16 inter-gNB coordination in TDD operation. If a UE with SBFD capability attempts to use Release 16 inter-gNB coordination, the performance of CLI processing may be undesirable because Release 16 inter-gNB coordination only supports exchanging semi-static and cell-specific TDD UL-DL configurations, but does not support exchanging dynamic slot formats or subband-based configurations between gNBs. Therefore, it does not work well in SBFD operation.

[0063] On the other hand, SBFD operation may support slot formats dynamically indicated by a Slot Format Indicator (SFI) in Downlink Control Information (DCI) format 2_0 (e.g., slot formats #46-55 defined in Section 11.1.1 of TS38.213) or new slot formats. The frequency domain resource allocation (i.e., subband allocation) of DL-UL slots / symbols in SBFD operation may differ from the frequency domain resource allocation for TDD operation shown in Figure 10, resulting in different total amounts of CLI measured by neighboring gNBs. Therefore, neighboring gNBs do not have sufficient information to adjust their scheduling for inter-gNB CLI processing.

[0064] In the coordination between gNBs for CLI processing according to the present disclosure, multiple slot formats per cell are exchanged between gNBs, and each of the multiple slot formats is associated with a subband within the cell. The subband includes a frequency domain resource allocation (e.g., resource blocks (RBs) / physical RBs (PRBs)), into which the band of the cell is divided. The subbands do not overlap with each other and are used to divide the transmission direction.

[0065] Figure 11A shows the legacy TDD format 1102 used in Rel-16 inter-gNB cooperation for inter-gNB CLI processing. In Rel-16 inter-gNB cooperation, only cell-specific format slots per cell for legacy TDD bands are exchanged semi-statically between gNBs over the Xn / F1 interface by the current upper layer parameter IntendedTDD-DL-ULConfiguration-NR.

[0066] 11B shows an example TDD format 1104 used in inter-gNB cooperation according to various embodiments of the present disclosure for inter-gNB CLI processing. In inter-gNB cooperation according to the present disclosure, multiple slot formats (e.g., UE-specific slot formats) per cell per gNB based on a set of subbands (e.g., subband #1, subband #2, ..., subband #j) in a serving cell (or legacy TDD band) can be exchanged semi-statically between gNBs via the Xn / F1 interface. This may be exchanged by the current upper layer parameter IntendedTDD-DL-ULConfiguration-NR or by a new upper layer parameter to support inter-gNB CLI processing in SBFD operation.

[0067] Table 1 shows exemplary slot format indication information, i.e., multiple slot formats per cell per gNB (e.g., gNB1, gNB2, gNB3, or gNBs with index numbers 1, 2, and 3), exchanged between gNBs for inter-gNB coordination for inter-gNB CLI processing, according to various embodiments of the present disclosure. In this example, it is assumed that a gNB serves one cell, and SFI i,j indicates the slot format for gNB index i and subband index j. For example, in Table 1, the first column indicates gNB index i=1,...,3, the second column indicates multiple slot formats for subband indexes 1 to j, and SFI i,j gNB i This is the slot format used for subband #j of the . [Table 1]

[0068] When a gNB serves multiple cells, the slot format for each cell of the gNB is as shown in Table 2. i,j,kwhere i denotes the gNB index, j denotes the cell index, and k denotes the subband index. [Table 2]

[0069] Optionally, the validity period of multiple slot formats for each gNB (e.g., gNB1, gNB2, gNB3), in terms of milliseconds (ms) or number of slots, is also exchanged, and the validity period can be defined by a higher layer parameter, such as the higher layer parameter NRDL-ULTransmissionPeriodicity in the specification.

[0070] According to the present disclosure, after multiple slot formats per cell are exchanged between gNBs, extended DCI format 2_0 1114, which is extended from legacy DCI format 2_0 1112, is used to support the function of indicating multiple slot formats per cell (SFI) for each gNB. Extended DCI format 2_0 includes all or part of the SFIs for different rows and columns (frequency and time resource allocations), and such DCI can be used by a gNB (in this case, gNB_i). The TDD band 1104 may also be divided into a corresponding number of subbands in different time domains. In this example, the TDD band is divided into three subbands corresponding to three gNB indices (row numbers), and the subbands are used to divide the transmission directions for, for example, gNB1, gNB2, and gNB3, respectively. Instead of extending DCI format 2_0, other DCI formats may be extended to indicate multiple slot formats. For example, a DCI format may be dedicated to a UE.

[0071] FIG. 12 is a schematic diagram illustrating an example configuration of a communications device 1200 for inter-gNB coordination for inter-gNB CLI processing in accordance with various embodiments of the present disclosure. The communications device 1200 may be implemented as a base station configured for transmitting and receiving signals in accordance with the present disclosure. As shown in FIG. 12 , the communications device 1200 may include a circuit 1214, at least one radio transmitter 1202, at least one radio receiver 1204, and at least one antenna 1212 (for simplicity, only one antenna is depicted in FIG. 12 for illustrative purposes). The circuit 1214 may include at least one controller 1206, which is used for software- and hardware-assisted execution of tasks designed to be performed by the at least one controller 1206, including control of communications with one or more other communications devices in a multiple-input and multiple-output (MIMO) wireless network. The circuit 1214 may further include at least one transmit signal generator 1208 and at least one receive signal processor 1210. The at least one controller 1206 may control the at least one transmit signal generator 1208 to generate downlink or sidelink signals to be transmitted by the at least one wireless transmitter 1202, and may control the at least one receive signal processor 1210 to process uplink, downlink, or sidelink signals received by the at least one wireless receiver 1204 from one or more other communication devices. The at least one transmit signal generator 1208 and the at least one receive signal processor 1210 may be standalone modules of the communication device 1200 that communicate with the at least one controller 1206 for the above-mentioned functions, as shown in FIG. 12 . Alternatively, the at least one transmit signal generator 1208 and the at least one receive signal processor 1210 may be included in the at least one controller 1206. It will be apparent to those skilled in the art that the arrangement of these functional modules is adjustable and may be changed according to actual needs and / or requirements. Data processing, virtual memory, and other related control devices may be provided on an appropriate circuit board and / or within a chipset.In various embodiments, in operation, at least one wireless transmitter 1202 , at least one wireless receiver 1104 , and at least one antenna 1212 may be controlled by at least one controller 1206 .

[0072] In operation, communications apparatus 1200 provides functionality necessary for inter-gNB coordination for inter-gNB CLI processing. For example, communications apparatus 1200 is a first base station, and circuit 1214 (or at least one transmit signal generator 1208 of circuit 1214) is configured to generate a signal including information on multiple sets of slot formats for one or more serving cells, each set of slot formats corresponding to multiple frequency segments of each serving cell of the one or more serving cells, and at least one radio transmitter 1202 may transmit the signal to one or more other communications devices.

[0073] In one embodiment, the multiple frequency segments of each serving cell of the one or more serving cells are formed by dividing a frequency band of each serving cell of the one or more serving cells.

[0074] In one embodiment, the circuit 1214 (or at least one transmit signal generator 1208 of the circuit 1214) may be configured to generate a signal in response to expiration of the validity period.

[0075] In another embodiment, the at least one radio transmitter 1202 may transmit second information to at least one of the plurality of user equipments based on the information of the plurality of sets of slot formats using one or a combination of higher layer parameters or downlink control information.

[0076] In yet another embodiment, the at least one radio receiver 1204 may be configured to receive a request from one of the one or more second base stations, and the circuit 1214 (or the at least one transmit signal generator 1208 of the circuit 1214) may be configured to generate, in response to receiving the request, multiple new sets of slot formats corresponding to multiple frequency segments for the one or more serving cells, and generate a signal including information of the multiple new sets of slot formats.

[0077] In one embodiment, the circuit 1214 (or at least one transmit signal generator 1208 of the circuit 1214) may be configured to generate a second signal including information of a plurality of updated frequency segments, each set of slot formats of the plurality of sets corresponding to a plurality of updated frequency segments for each serving cell of the one or more serving cells.

[0078] For example, communications device 1200 may be a second base station, and at least one radio receiver 1204 may receive, from the other communications device, a signal including information on multiple sets of slot formats for one or more serving cells, each set of slot formats corresponding to multiple frequency segments of each serving cell of the one or more serving cells, each serving cell of the one or more serving cells being associated with the other communications device. Circuit 1214 (or at least one controller 1206 of circuit 1214) may be configured to perform a scheduling procedure based on the information.

[0079] According to an alternative embodiment of the present disclosure, communications apparatus 1200, in operation, provides functionality necessary for inter-gNB coordination for inter-gNB CLI processing. For example, communications apparatus 1200 is a third base station, and a first serving cell and a second serving cell are associated with the third base station. Circuit 1214 (or at least one transmit signal generator 1208 of circuit 1214) may be configured to generate a signal including information of multiple sets of slot formats of the first serving cell, the sets of slot formats corresponding to multiple frequency segments of the first serving cell, and at least one radio transmitter 1202 may transmit the signal to the second serving cell.

[0080] 13 shows a flowchart 1300 illustrating a communication method for inter-gNB cooperation for inter-gNB processing in accordance with various embodiments of the present disclosure. In step 1302, a step of generating a signal including information on multiple sets of slot formats for one or more serving cells is performed, where each set of slot formats in the multiple sets of slot formats corresponds to multiple frequency segments of each serving cell of the one or more serving cells. In step 1304, a step of transmitting the signal to one or more second base stations is performed.

[0081] In the following paragraphs, a first embodiment of the present disclosure is described with respect to exchanging slot format indicator information with substantially overlapping / shared subband allocation for inter-gNB cooperation.

[0082] 14A shows a block diagram 1400 illustrating an example TDD band with fully overlapped / shared subband allocation for inter-gNB cooperation for inter-gNB CLI processing according to the first embodiment of the present disclosure. In the frequency domain, subbands (e.g., subbands #1 to #7) are defined for all cells of a group of neighboring gNBs (e.g., gNB #1 and gNB #2) and are fully shared (overlapping). There may be multiple sets of subbands for multiple gNB groups, and SFI information for those subbands does not need to be exchanged. However, in the time domain, multiple slot formats (SFI information) per cell are exchanged between gNBs based on the subband. Each of the multiple slot formats corresponds to a respective subband.

[0083] In one embodiment, the slot formats of a cell may be updated based on a validity period. In other words, the slot format is valid for a validity period, and when the validity period expires, a new slot format is generated to replace the slot format in the subband. The slot formats of each subband of a cell may also be updated at different periods / timings based on their respective validity periods. In another embodiment, SFI information is exchanged upon receiving a request from a corresponding gNB.

[0084] Each of the multiple slot formats indicates how each symbol within a single slot is used. In particular, it defines which symbols are used for the uplink, which symbols are used for the downlink, and which symbols are used as flexible symbols within a particular slot. If the flexible symbols are quasi-static symbols, they can be further configured as downlink or uplink symbols by using dedicated RRC configuration or dynamic indication in the serving cell. In other cases, the flexible symbols can be used as guard periods for beam switching or uplink-downlink switching when the UE operates in half-duplex splitting operation. Furthermore, different slot format types may be available, providing high flexibility in gNB scheduling, especially in TDD or SBFD operation. For example, there may be a slot format type used for downlink-heavy transmissions with uplink symbols, another slot format type used for uplink-heavy transmissions with downlink control symbols, and another slot format type used for downlink-heavy transmissions without uplink symbols. Thus, by applying slot formats or sequentially combining different slot formats in the time domain, the gNB can configure various different types of scheduling.

[0085] In response to reception of the SFI information by the corresponding gNB, multiple slot formats can be signaled in the cell of the corresponding gNB to the UE, or to one or more of the multiple UEs associated with the corresponding gNB, using either or both of the following two options: (1) a dedicated Radio Resource Control (RRC) configuration, where the multiple slot formats are semi-statically configured in the UE using new dedicated RRC parameters, and (2) an indication in the DCI, where the multiple slot formats are indicated to the UE by extending the SFI indication with multiple SFI fields of DCI format 2_0, where the position bits of each of the multiple slot formats for each subband are configurable or a bitmap.

[0086] For example, referring to FIG. 14B, in Option 2, assuming that a gNB serves one cell, SFI i,j gNB i The slot format used for subband #j of DCI format 2_0 is the slot format used for subband #j of DCI format 2_0. Multiple slot formats are dynamically indicated using multiple SFI fields in DCI format 2_0. It is also possible to indicate dynamic slot formats #46-55 defined in Section 11.1.1 of TS38.213, but this may not be possible using the current Rel. 16 inter-gNB coordination.

[0087] Note that a gNB may be a gNB as defined in TS 38.300 in a non-split gNB scenario, or a gNB distributed unit (gNB-DU) as defined in TS 38.401 in a split gNB scenario. A gNB may also serve one or more cells. In a non-split gNB scenario, information exchange can be performed between gNBs based on the Xn interface, i.e., under the responsibility of the gNB. In a split gNB scenario, information exchange can be performed between gNB-DUs via the gNB central unit (gNB-CU) based on the F1 interface, i.e., under the responsibility of the gNB-DU. For example, in a non-split gNB scenario (e.g., from gNB#1 to gNB#2), a gNB exchanges multiple slot format sets for its cell with neighboring gNBs via Xn. In a split gNB scenario, a gNB-DU exchanges a set of its cell's multiple slot formats with a gNB-CU node via the F1 interface, and then with a neighboring gNB-DU, or with a gNB via the F1 and Xn interfaces, e.g., from gNB-DU#1 to gNB-DU#2 via gNB-CU via the F1 interface, or from gNB-DU#1 to gNB via gNB-CU via the F1 and Xn interfaces. Also, according to the current specification, in TDD operation, the same slot format indicated by the SFI is commonly applied to all RB sets of a group of UEs in the serving cell, whereas in SBFD operation, multiple slot formats SFI may be applied to different subbands (each of which contains multiple RBs). The bit width of the multiple SFI field may be provided by higher layer parameters and may be determined as log_2(subband size). Alternatively, the size of the multiple SFI field may be defined based on the number of gNBs and subbands in the group.

[0088] FIG. 15 shows a flowchart 1500 illustrating a first exemplary inter-gNB coordination process (Option 1) for gNB CLI processing according to the first embodiment of the present disclosure. In step 1502, the network configures multiple slot formats (multiple slot formats per cell per gNB) for a group of gNBs operating in SBFD based on the subband for inter-gNB CLI processing. Each of the multiple slot formats per cell per gNB is unique for each subband. In step 1504, each gNB in ​​the group of gNBs monitors inter-gNB CLI measurements. In step 1506, each gNB determines whether the inter-gNB CLI is greater than or equal to an inter-gNB CLI threshold level (Threshold #1). If the inter-gNB CLI is greater than or equal to Threshold #1, step 1512 is executed, in which the gNB requests updating of SFI information to include new candidates for the multiple slot formats. If determined to be less than Threshold #1, the gNB signals the multiple slot formats to the UE or one or more UEs among the multiple UEs associated with the gNB. Steps 1508 and 1510 show signaling in Option 1. In Option 1, each gNB semi-statically configures multiple slot formats for its UE in the serving cell using dedicated RRC parameters. In step 1508, each gNB configures multiple SFI fields for each of the cells used to indicate the multiple slot formats to its UE in the serving cell using the new dedicated RRC parameters. In step 1510, the UE receives the RRC parameters and obtains the multiple slot formats.

[0089] FIG. 16 shows a flowchart 1600 illustrating a second exemplary inter-gNB coordination process (Option 2) for gNB CLI processing according to the first embodiment of the present disclosure. In step 1602, the network configures multiple slot formats (multiple slot formats per cell per gNB) for a group of gNBs operating in SBFD based on subbands for inter-gNB CLI processing. Each of the multiple slot formats per cell per gNB is unique for each subband. In step 1604, each gNB in ​​the group of gNBs monitors inter-gNB CLI measurements. In step 1606, each gNB determines whether the inter-gNB CLI is greater than or equal to an inter-gNB CLI threshold level (Threshold #1). If the inter-gNB CLI is greater than or equal to Threshold #1, step 1612 is performed, in which the gNB requests updating of SFI information to include new candidates for multiple slot formats. If determined to be less than Threshold #1, the gNB signals the multiple slot formats to the UE or one or more UEs among multiple UEs associated with the gNB. Steps 1608 and 1610 show signaling in option 2. In step 1608, each gNB configures multiple SFI fields in DCI format 2_0 for each cell used to indicate multiple slot formats to its UE in the serving cell. i,j The position bits of may be configurable or a bitmap. In step 1610, the UE monitors DCI format 2_0 and acquires multiple slot formats.

[0090] FIG. 17 shows a flowchart 1700 illustrating a third exemplary inter-gNB coordination process (Option 2) for gNB CLI processing according to the first embodiment of the present disclosure. In this example, inter-UE CLI measurement is considered. In particular, in step 1702, the network configures multiple slot formats (multiple slot formats per cell per gNB) for a group of gNBs operating in SBFD based on subbands for inter-gNB CLI processing. Each of the multiple slot formats per cell per gNB is unique for each subband. In step 1704, each gNB in ​​the group of gNBs monitors inter-gNB CLI measurements and receives reports from the UE. In step 1706, each gNB determines whether the inter-gNB CLI is greater than or equal to an inter-gNB CLI threshold level (Threshold #1) and whether the inter-UE CLI is greater than or equal to an inter-UE CLI threshold level (Threshold #2). If the inter-gNB CLI is greater than or equal to threshold #1 and the inter-UE CLI is greater than or equal to threshold #2, step 1712 is executed, in which the gNB requests updating of SFI information to include new candidates for multiple slot formats. If it determines that the inter-gNB CLI is lower than threshold #1 and the inter-UE CLI is lower than threshold #2, the gNB signals the multiple slot formats to the UE, or to one or more UEs among the multiple UEs associated with the gNB. In step 1708, each gNB configures multiple SFI fields of DCI format 2_0 for each cell used to indicate multiple slot formats to its UE in the serving cell (option 2). The slot format SFI for each subband i,j The position bits of may be configurable or a bitmap. In step 1710, the UE monitors DCI format 2_0 and obtains multiple slot formats.

[0091] In the following paragraphs, a second embodiment of the present disclosure is described with respect to exchanging slot format indicator information with partially overlapping / shared subband allocation for inter-gNB cooperation.

[0092] 14B shows a block diagram 1420 illustrating an example TDD band with partially overlapping / shared subband allocation for inter-gNB cooperation for inter-gNB CLI processing in accordance with a second embodiment of the present disclosure. In the frequency domain, subbands (e.g., subbands #1-7) are defined with partially overlapping subbands (e.g., subband #4) shared among cells in a group of gNBs, while there are non-overlapping subbands among cells in a group of gNBs (e.g., subbands #1-3 assigned to gNB #1 and subbands #5-7 assigned to gNB #2).

[0093] In one embodiment, as shown in FIG. 14B, a partially overlapping subband (e.g., subband #4) is defined as "SBFD disabled," and the remaining non-overlapping subbands (e.g., subbands #1-3 and #5-7) are defined as "SBFD enabled." In an alternative embodiment, a partially overlapping subband (e.g., subband #4) is defined as "SBFD enabled," and the remaining non-overlapping subbands (e.g., subbands #1-3 and #5-7) are defined as "SBFD disabled." In another embodiment, the combination of all subbands in a group is defined as "SBFD enabled." Essentially, multiple slot formats in subbands defined as "SBFD enabled" are exchanged. Limiting the amount of SFI information exchange to only those that are SBFD enabled reduces the number of subbands used in SBFD operation and the signaling and CLI required between gNBs.

[0094] In the time domain, multiple slot formats (SFI information) per cell are exchanged between gNBs based on the "SBFD enabled" sub-bands. The remaining operations are similar to those shown in the first embodiment based on multiple slot formats in the "SBFD enabled" sub-bands.

[0095] For example, in one embodiment, only the slot formats for each of the cell's "SBFD enabled" subbands may be updated based on their respective validity periods. Alternatively, only the slot formats for each of the cell's "SBFD disabled" subbands may be updated based on their respective validity periods. Thus, the slot formats for each of the cell's subbands may also be updated at different periods / timings based on their respective validity periods. In another embodiment, SFI information is exchanged upon receiving a request from a corresponding gNB.

[0096] Also, once the corresponding gNB receives the SFI information, multiple slot formats can be signaled in the cell of the corresponding gNB to the UE or to one or more UEs among multiple UEs associated with the corresponding gNB using either one of the following two options or a combination of both: (1) a dedicated Radio Resource Control (RRC) configuration, where the multiple slot formats are semi-statically configured in the UE using new dedicated RRC parameters, and (2) an indication in the DCI, where the multiple slot formats are indicated to the UE by extending the SFI indication with multiple SFI fields in DCI format 2_0, where the position bits of the multiple slot formats for each subband can be configurable or a bitmap.

[0097] It should be noted that the number of slot formats with fully overlapping subband allocations in the first embodiment may be different from the number of slot formats with partially overlapping subband allocations in the second embodiment depending on the set of "SBFD enabled" subbands.

[0098] In one example of various embodiments of the present disclosure, in the time domain, the same slot format per cell used for all subbands (or all subbands that are "SBFD enabled") is exchanged between groups of gNBs. [Table 3]

[0099] In other examples of various embodiments of the present disclosure, instead of using defined subbands in the frequency domain, subbands can be configured / updated (e.g., different bandwidths and / or numbers of subbands) and exchanged. In the time domain, similar content as already described in the first or second embodiment can be used. The information exchange includes SFI information along with the subbands of each cell. Advantageously, this allows for more flexibility in RRC configuration for SBFD operation. Optionally, in each cell in a group, the configured subbands in the frequency domain can be dynamically activated or deactivated in the time domain (i.e., with respect to frequency resources). [Table 4]

[0100] According to yet another example of various embodiments of the present disclosure, in the time domain, multiple per-cell slot formats can be a new per-cell semi-static (SBFD) slot format exchangeable between gNBs. Such a new per-cell semi-static (SBFD) slot format can be configured by using a new RRC parameter (e.g., intendedXDD-UL-DL-Configuration-r18) in the current IntendedTDD-DL-ULConfiguration-NR in addition to the legacy semi-static (TDD) slot format. A different direction other than the direction configured by the legacy (TDD) semi-static slot format is indicated for a slot / symbol using the new RRC parameter, such as tdd-UL-DL-ConfigurationXDD-r18.

[0101] In this new semi-static (SBFD) slot format, it is possible to overwrite the legacy semi-static "D" and / or "U" symbols / slots in addition to the F symbols / slots. Each gNB in ​​the group schedules its UEs using the corresponding overwritten slot format. The overwriting rules are shown in Table 5. [Table 5]

[0102] As shown in Table 5, the legacy quasi-static slot format "DDDUFFF" can be overwritten to "DUFUFUF", and the second and third slot formats "D" and "D" are overwritten to "U" and "F", respectively, in addition to the overwrite rules for the fifth and sixth slot formats "F" to be overwritten from "F" to "D" and "U" per Release 15 / 16 / 17. These overwrite rules differ from the overwrite rules in Release 15 / 16 / 17, where only slot format "F" can be overwritten.

[0103] Optionally, SBFD symbol / slot available and SBFD symbol / slot unavailable can be introduced as defined in the second embodiment. In such a case, the available SBFD symbols / slots (which may be legacy quasi-static D and / or U symbols / slots) are symbols / slots that are allowed to be overwritten other than the legacy quasi-static F symbols / slots.

[0104] In Rel. 15 / 16 / 17, the overwriting rules for configuring the slot format are as follows: (i) The semi-static D and U symbols cannot be overwritten by either UE-dedicated RRC or dynamic configuration (using DCI format 2_0). (ii) Only the semi-static F symbol can be overwritten to D or U by UE-dedicated RRC or DCI format 2_0. (iii) If the semi-static F symbol is not overwritten to D or U by UE-dedicated RRC or DCI format 2_0, the UE follows the scheduling DCI (e.g., DCI format 0_0 / 0_1 / 0_2 / 1_0 / 1_1 / 1_2) to determine whether to transmit or receive.

[0105] 18 is a block diagram illustrating an example TDD band with a new quasi-static slot format for gNB cooperation for inter-gNB CLU processing, according to one embodiment of the present disclosure. The slot format "DDDU" of the legacy TDD band 1800 is overwritten in the new quasi-static SBFD 1820 by replacing the IntendedTDD-DL-ULConfiguration-NR with "DUUU" for subband #1, "UUUU" for subband #2, and "DDUU" for subband #3.

[0106] According to various embodiments of the present disclosure, the information exchange may further include one or more of the following:

[0107] Physical gNB Identity (ID) Sounding Reference Signal (SRS) settings Beam coordination (beam index pairing between gNBs) Inter-gNB CLI and / or inter-UE CLI measurements (e.g., Sounding Reference Signal-Reference Signal Received Power (SRS-RSRP) and CLI Received Signal Strength Indicator (CLI-RSSI)) Subband index

[0108] SRS-RSRP indicates the linear average of the power contribution of the SRS measured over the configured resource elements within the measurement frequency bandwidth considered in the time resource at the configured measurement occasion, while CLI-RSSI indicates the linear average of the total received power observed only in a specific OFDM symbol of the measurement time resource within the measurement band over the resource elements configured for measurement by the UE.

[0109] According to various embodiments of the present disclosure, the information exchange may also be performed via a radio-based or backhaul-based framework. Although the embodiments are described with respect to a group of neighboring gNBs, it will be understood that the embodiments are applicable to all gNBs in the network.

[0110] Although not specified, it is understood by those skilled in the art that such inter-gNB coordination for gNB CLI processing is applicable to intra-gNB coordination for cell CLI processing, assuming that one gNB serves multiple cells.

[0111] As mentioned above, a table of multiple slot formats for a group of neighboring gNBs can be configured by IntendedXDD-UL-DL-Configuration-r18 of IntendedTDD-DL-ULConfiguration-NR, where gNB_i is the index of a gNB in ​​the group GroupOfgNB, slotConfiguration-List_XDD includes dynamic slot format candidates for XDD operation (e.g., slot formats #46 to #55 in TS38.213), and SFI_ij indicates multiple dynamic slot formats for three predetermined subbands, where the subband index of gNB_i is 1 to 3. Examples of slot formats for IntendedTDD-DL-ULConfiguration-NR, IntendedXDD-UL-DL-Configuration-r18, and SlotConfiguration_XDD are shown below. [Table 6]

[0112] In one alternative embodiment, for CLI processing between gNBs in SBFD operation, information exchange between gNBs is dynamic and frequently updated. The information exchange includes at least a set of subbands and corresponding slot formats. In a radio-based framework, a gNB transmits information exchange in DCI to other gNBs over the air interface. On the other hand, in a backhaul-based framework, a gNB transmits information with a transmission period in the IntendedTDD-DL-ULConfiguration-NR IE to other gNBs over a wired backhaul network on a slot-by-slot basis. However, since this may result in a large amount of information exchange, it is more preferable to apply it to intra-gNB coordination for inter-cell CLI processing in a centralized RAN where a gNB serves multiple cells, or in sector operation, etc.

[0113] In the above embodiments, "exchange between gNBs" can be replaced with "transmit to another gNB" or "send to another gNB." Also, "exchange between gNBs" can be replaced with "transmit to user equipment (UE)" or "send to UE."

[0114] According to the present disclosure, various examples are described below.

[0115] 1. A circuit configured, in operation, to generate a signal including information of a plurality of sets of slot formats for one or more serving cells, each set of slot formats corresponding to a plurality of frequency segments of each serving cell of the one or more serving cells; a transmitter that, in operation, transmits signals to one or more second base stations; a first base station comprising:

[0116] 2. The first base station of Example 1, wherein the plurality of frequency segments of each serving cell of the one or more serving cells are formed by dividing a frequency band of each serving cell of the one or more serving cells.

[0117] 3. The first base station of example 1 or 2, wherein each slot format of each set of slot formats corresponds to one of a plurality of frequency segments of each serving cell of the one or more serving cells.

[0118] 4. The first base station of any one of examples 1 to 3, wherein the frequency segments do not overlap with one another.

[0119] 5. The first base station of any one of Examples 1 to 4, wherein each slot format of each set of slot formats indicates a set of transmission directions in a particular slot, and each of the sets of transmission directions is an uplink direction, a downlink direction, or both.

[0120] 6. The first base station of any one of Examples 1 to 5, wherein the circuitry is configured to generate a signal in response to expiration of the validity period.

[0121] 7. The first base station of any one of Examples 1 to 5, wherein the effective period of one set of slot formats among the plurality of sets of slot formats is different from the effective period of another set of slot formats among the plurality of sets of slot formats.

[0122] 8. The first base station of any one of Examples 1 to 4, wherein the signal includes information about the validity period of each set of slot formats of the plurality of sets of slot formats, and the circuitry is configured to generate a new set of slot formats to replace each set of slot formats of the plurality of sets of slot formats upon expiration of the validity period.

[0123] 9. The first base station of Example 8, wherein each slot format of each set of slot formats indicates a set of transmission directions in a particular slot, the transmission directions being an uplink direction, a downlink direction, or both, and the new set of slot formats replaces only one or more transmission directions of the set of transmission directions in the particular slot.

[0124] 10. The first base station of any one of Examples 1 to 9, wherein the transmitter further transmits, to at least one of the plurality of user equipments, second information based on the information of the plurality of sets of slot formats using one or a combination of higher layer parameters or downlink control information.

[0125] 11. The first base station of any one of Examples 1 to 10, further comprising a receiver that, during operation, receives a request from one of the one or more second base stations, wherein the circuitry is configured to, in response to receiving the request, generate a plurality of new sets of slot formats corresponding to a plurality of frequency segments for the one or more serving cells, and generate a signal including information of the plurality of new sets of slot formats.

[0126] 12. The first base station of any one of Examples 1 to 11, wherein the multiple sets of slot formats include a first set of slot formats and a second set of slot formats, the one or more serving cells include one or more first serving cells associated with the first base station and one or more second serving cells associated with one of the one or more second base stations, the first set of slot formats corresponds to one or more first frequency segments of the one or more first serving cells among the multiple frequency segments, and the second set of slot formats corresponds to one or more second frequency segments of the one or more second serving cells among the multiple frequency segments, and at least one of the one or more first frequency segments does not overlap with the one or more second frequency segments and / or at least one of the one or more second frequency segments does not overlap with the one or more first frequency segments.

[0127] 13. The first base station of Example 12, wherein the information on the multiple sets of slot formats includes information on a set of first slot formats and a set of second slot formats that correspond only to one or more second frequency segments that do not overlap with one or more first frequency segments, and one or more first frequency segments that do not overlap with one or more second frequency segments.

[0128] 14. The first base station of Example 12, wherein the information on the multiple sets of slot formats includes information on a set of first slot formats and a set of second slot formats that correspond only to one or more first frequency segments that overlap with one or more second frequency segments.

[0129] 15. The first base station of Example 12, wherein the information on the multiple sets of slot formats includes information on a set of first slot formats and a set of second slot formats corresponding to at least one of (i) one or more first frequency segments that do not overlap with one or more second frequency segments and one or more second frequency segments that do not overlap with one or more first frequency segments, and (ii) one or more first frequency segments that do not overlap with one or more second frequency segments.

[0130] 16. The first base station of any one of Examples 1 to 15, wherein each slot format set of the multiple sets of slot formats corresponding to the multiple frequency segments of each of the one or more serving cells includes a single slot format.

[0131] 17. The first base station of any one of Examples 1 to 16, wherein the circuitry is further configured to generate a second signal including information of a plurality of updated frequency segments, each set of slot formats of the plurality of sets of slot formats corresponding to a plurality of updated frequency segments of each serving cell of the one or more serving cells.

[0132] 18. The first base station of any one of examples 1 to 17, wherein the transmitter is configured to transmit signals to one or more second base stations via radio resource control signaling.

[0133] 19. The first base station of any one of Examples 1 to 17, wherein the transmitter is configured to transmit signals in the downlink control information to one or more second base stations at regular intervals each time through radio resource control signaling via a wireless or wired network.

[0134] 20. The first base station of any one of Examples 1 to 19, wherein the signal includes third information, the third information including at least one of a physical cell identity, an index of a plurality of frequency segments, a sounding reference signal configuration, beam coordination information, a beam index, and a crosslink interference measurement in each serving cell of one or more serving cells.

[0135] 21. A second base station, comprising: a receiver that, during operation, receives from a first base station a signal including information of a plurality of sets of slot formats for one or more serving cells, each set of slot formats of the plurality of sets of slot formats corresponding to a plurality of frequency segments of each serving cell of the one or more serving cells; and a receiver that is associated with the first base station. and a circuit configured, in operation, to perform a scheduling procedure based on the information.

[0136] 22. A third base station to which a first serving cell and one or more second serving cells are associated, a circuit configured, in operation, to generate a signal including information of a set of slot formats for a first serving cell, the set of slot formats corresponding to a plurality of frequency segments of the first serving cell; a transmitter that, in operation, transmits signals to one or more second serving cells; a third base station comprising:

[0137] 23. A step of generating a signal including information of a plurality of sets of slot formats for one or more serving cells, each set of slot formats corresponding to a plurality of frequency segments of each serving cell of the one or more serving cells; transmitting a signal to one or more second base stations; A communication method, including:

[0138] In the following paragraphs, certain exemplary embodiments are described with reference to terminology related to 5G core networks and the present disclosure relating to a communications apparatus and method for allocating one or more additional operating windows between two semi-statically configured SL DRX periods for receiving or transmitting SL signals.

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

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

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

[0142] (Uplink / Downlink / Sidelink) The present disclosure may be applied to any of the uplink, downlink, and sidelink.

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

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

[0145] (Data channel / Control channel) The present disclosure may be applied to both data channels and control channels. For example, the channels of the present disclosure may be replaced with data channels such as PDSCH, PUSCH, and PSSCH, and control channels such as PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

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

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

[0148] (frequency band) The present disclosure may be applied to both licensed and unlicensed bands.

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

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

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

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

[0153] The present disclosure may be implemented by any type of apparatus, device, or system having communication capabilities (collectively referred to as communication apparatus).

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

[0155] Non-limiting examples of such communications devices include telephones (e.g., mobile phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still cameras / video cameras), digital players (digital audio players / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote healthcare / medicine prescription) devices, and vehicles (e.g., cars, airplanes, ships) that provide communications capabilities, in various combinations.

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

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

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

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

[0160] Those skilled in the art will appreciate that numerous variations and / or modifications may be made to the present disclosure as set forth in the specific embodiments without departing from the spirit or scope of the disclosure as broadly described, and the present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims

1. A circuit configured to generate a signal during operation that includes a subband index for subband non-overlapping full duplex (SBFD) and slot format information for the subbands for one or more serving cells, During operation, the system includes a transmitting unit that transmits the aforementioned signal to one or more second base stations, The first base station is equipped with the following.

2. The signal further includes another slot format information for one or more serving cells, and another subband index relating to subband non-overlapping full duplex (SBFD). The first base station according to claim 1.

3. The aforementioned subband index and the aforementioned other subband index overlap with each other. The first base station according to claim 2.

4. The aforementioned slot format information is included in IntendedTDD-DL-ULConfiguration-NR IE, The first base station according to claim 1.

5. In addition to the flexible symbols configured by the aforementioned slot format information, downlink symbols are overwritten by SBFD symbols. The first base station according to claim 1.

6. The signal includes an ID relating to the first base station, The first base station according to claim 1.

7. The aforementioned slot format information expires after the validity period. The first base station according to claim 1.

8. A communication method performed by a first base station, A step of generating a signal that includes subband indices for subband non-overlapping full duplex (SBFD) and slot format information for subbands for one or more serving cells, The steps include transmitting the aforementioned signal to one or more second base stations, A communication method that includes this.

9. The signal further includes another slot format information for one or more serving cells, and another subband index relating to subband non-overlapping full duplex (SBFD). The communication method according to claim 8.

10. The aforementioned subband index and the aforementioned other subband index overlap with each other. The communication method according to claim 9.

11. The aforementioned slot format information is included in IntendedTDD-DL-ULConfiguration-NR IE, The communication method according to claim 8.

12. In addition to the flexible symbols configured by the aforementioned slot format information, downlink symbols are overwritten by SBFD symbols. The communication method according to claim 8.

13. The signal includes an ID relating to the first base station, The communication method according to claim 8.

14. The aforementioned slot format information expires after the validity period. The communication method according to claim 8.

15. An integrated circuit to be implemented in the first base station, During operation, a generation circuit controls the generation of a signal that includes a subband index for subband non-overlapping full duplex (SBFD) and slot format information for the subbands for one or more serving cells, A transmission circuit that controls the transmission of the aforementioned signal to one or more second base stations during operation, An integrated circuit equipped with the following features.

Images