Coordination of cross-link interference handling

Abstract

The present disclosure provides a communication device and a communication method for coordination of cross-link interference handling, the communication device being a base station, comprising: circuitry configured to generate a signal comprising information of a plurality of slot format sets of one or more serving cells, each time slot format set in the plurality of time slot format sets corresponds to a plurality of frequency segments of each serving cell in the one or more serving cells; and a transmitter that transmits 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 coordinating with another communication device, and more particularly, to inter-gNB (base station) coordination of cross-link interference (CLI) processing. Background Art

[0002] A new Release 18 Study Item (SI) titled “study on evolution of near-radio (NR) duplex operation” was approved at the RAN#94-e [RP-213591] meeting. One of the main topics is to study how to enable sub-band non-overlapping full-duplex (SBFD) within the traditional time division duplex (TDD) band, as this will allow the coexistence of downlink (DL) and uplink (UL) within the traditional TDD, where sub-bands are used to separate the transmission directions.

[0003] However, when SBFD is deployed, 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, potentially causing cross-link interference (CLI). This inter-gNB CLI becomes a critical issue that needs to be handled, and currently there is no solution that specifies how to achieve inter-gNB coordination of inter-gNB CLI handling in SBFD operation.

[0004] Therefore, a communication device and a communication method for inter-gNB coordination for CLI processing are needed to solve the above problems. In addition, other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims in conjunction with the accompanying drawings and the background technology of the present disclosure. Summary of the invention

[0005] Non-limiting and exemplary embodiments help provide a communication device and a communication method for inter-gNB (base station) coordination for inter-gNB CLI processing.

[0006] In a first aspect, the present disclosure provides a first base station, comprising: a circuit configured to generate a signal, the signal comprising information of multiple time slot format sets of one or more service cells, wherein each of the multiple time slot format sets corresponds to multiple frequency segments of each of the one or more service cells; and a transmitter, sending the signal to one or more second base stations.

[0007] In a second aspect, the present disclosure provides a second base station, comprising: a receiver, receiving a signal from a first base station, the signal comprising information of a plurality of time slot format sets, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of one or more service cells, wherein each of the one or more service cells is attached to the first base station; and a circuit, configured to perform a scheduling process based on the information.

[0008] In a third aspect, the present disclosure provides a third base station, wherein a first service cell and one or more second service cells are attached to the third base station, comprising: a circuit configured to generate a signal comprising information of a time slot format set of the first service cell, wherein the time slot format set corresponds to multiple frequency segments of the first service cell; and a transmitter to send the signal to one or more second service cells.

[0009] In a fourth aspect, the present disclosure provides a communication method, comprising: generating a signal comprising information of multiple time slot format sets for one or more service cells, wherein each of the multiple time slot format sets corresponds to one of multiple frequency bands of each of the one or more service cells; and sending the signal to one or more second base stations.

[0010] Additional benefits and advantages of the disclosed embodiments will be apparent from the present specification and drawings. These benefits and / or advantages can be obtained individually through the features of the various embodiments and the specification and drawings, and do not need to be provided in full to obtain one or more of these benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings are used to illustrate various embodiments and to explain various principles and advantages according to the current embodiments, wherein like reference numerals represent the same or functionally similar elements in various views, and together with the following detailed description, the accompanying drawings constitute a part of the specification.

[0012] Figure 1 An exemplary 3GPP Next Generation Radio Access Network (NG-RAN) architecture is shown, to which exemplary embodiments of the present disclosure may be applied.

[0013] Figure 2 A schematic diagram illustrating a functional split between NG-RAN and 5GC to which exemplary embodiments of the present disclosure may be applied is described.

[0014] Figure 3 A sequence diagram for a radio resource control (RRC) connection establishment / reconfiguration procedure to which exemplary embodiments of the present disclosure may be applied is described.

[0015] Figure 4 Schematic diagrams showing usage scenarios of enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC) to which exemplary embodiments of the present disclosure may be applied are described.

[0016] Figure 5 A block diagram illustrating an exemplary 5G system architecture for vehicle-to-everything (V2X) communications in a non-roaming scenario is shown.

[0017] Figure 6 A diagram illustrating the configuration update procedure between two gNBs is shown.

[0018] Figure 7 A schematic diagram illustrating the overall architecture of NG-RAN and 5GC is shown, wherein a gNB is shown in a split gNB scenario, which includes a gNB centralized unit (gNB-CU) and multiple gNB distributed units (gNB-DUs).

[0019] Figure 8 A diagram illustrating the configuration update procedure between the gNB distributed unit (gNB-DU) and the gNB centralized unit (gNB-CU) in a split gNB scenario is shown.

[0020] Fig. 9 Two block diagrams showing legacy (System Release 15 / 16 / 17) Time Division Duplex (TDD) and System Release 18 Sub-Band Non-Overlapping Full Duplex (SBFD), respectively, are described.

[0021] Fig.10 An example of legacy inter-gNB coordination with cross-link interference (CLI) is described.

[0022] Fig.11A The legacy TDD format used in inter-gNB coordination for inter-gNB CLI processing in System Release 16 is shown.

[0023] Fig. 11B An exemplary TDD format used in inter-gNB coordination for inter-gNB CLI processing according to various embodiments of the present disclosure is shown.

[0024] Fig.12 An example of a schematic diagram of a communication device according to various embodiments is shown.

[0025] Fig.13 A flow chart illustrating a communication method implemented by a first communication device according to various embodiments of the present disclosure is shown.

[0026] Fig.14AA block diagram illustrating an exemplary TDD frequency band for fully overlapping / shared subband allocation for inter-gNB coordination for inter-gNB CLI processing according to the first embodiment of the present disclosure is shown.

[0027] Fig. 14B A block diagram illustrating an exemplary TDD band with partially overlapping / shared subband allocation for inter-gNB coordination for inter-gNB CLI processing according to the second embodiment of the present disclosure is shown.

[0028] Fig.15 A flowchart illustrating a first exemplary inter-gNB coordination process for inter-gNB CLI processing according to the first embodiment of the present disclosure is shown.

[0029] Fig.16 A flowchart illustrating a second exemplary inter-gNB coordination process for inter-gNB CLI processing according to the first embodiment of the present disclosure is shown.

[0030] Fig.17 A flowchart illustrating a third exemplary inter-gNB coordination process for inter-gNB CLI processing according to the first embodiment of the present disclosure is shown.

[0031] Fig.18 A block diagram illustrating an exemplary TDD band with a new semi-static slot format for inter-gNB coordination for handling CLU between gNBs according to an embodiment of the present disclosure is shown.

[0032] Those skilled in the art will appreciate that the elements in the figures are shown for simplicity and clarity and are not necessarily drawn to scale. For example, the size of some elements in the diagrams, block diagrams or flow charts may be exaggerated relative to other elements to help accurately understand the present embodiment. DETAILED DESCRIPTION

[0033] Certain embodiments of the present disclosure will be described, by way of example only, with reference to the accompanying drawings, in which like reference numerals and characters represent like elements or equivalents.

[0034] 3GPP has been working on the development of the next system version, the fifth generation of cellular technology, referred to as 5G, including the development of new radio access technology (NR) operating in the frequency range up to 100GHz. The first document version of the 5G standard was completed at the end of 2017, which enabled trials and commercial deployment of smartphones compliant with the 5G NR standard.

[0035] The second document version of the 5G standard was completed in June 2020, which further expanded the coverage of 5G to new services, spectrum and deployment methods, such as unlicensed spectrum (NR-U), non-public network (NPN), time-sensitive network (TSN) and cellular V2X.

[0036] In addition, the overall system architecture adopts NG-RAN (Next Generation Radio Access Network), which includes gNB, providing user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for NG wireless access for UE. gNBs are interconnected through the Xn interface. The gNB is also connected to the NGC (Next Generation Core) through the Next Generation (NG) interface, more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) through the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) through the NG-U interface. The NG-RAN architecture is Figure 1 As shown (see, for example, 3GPP TS 38.300 v16.3.0).

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

[0038] For example, the medium access control layer handles the multiplexing of logical channels, as well as scheduling and scheduling-related functions, including the handling of different numerologies.

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

[0040] SL supports UE-to-UE direct 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, where the network provides allocation of NR SL resources; and (b) Mode 2, where the UE determines the NR SL transmission resources in (multiple) resource pools. Two SL resource allocation modes are applicable to LTE V2X: (a) Mode 3, where the eNB schedules LTE SL resources, mainly for the transmission of periodically occurring messages; and (b) Mode 4, where the UE autonomously determines the LTE SL transmission resources in the resource pool.

[0041] The PSCCH indicates the resources and other transmission parameters used by the UE for the PSSCH. The PSCCH transmission is associated with a demodulation reference signal (DM-RS). The PSSCH sends the transport block (TB) of the data itself, as well as control information for the HARQ process and channel state information (CSI) feedback triggers, etc. Within a time slot, at least 6 orthogonal frequency division multiplexing (OFDM) symbols are used for PSSCH transmission. The PSSCH transmission is associated with a DM-RS and can be associated with a phase tracking reference signal (PT-RS).

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

[0043] The SL synchronization signal consists of the SL primary synchronization signal (S-PSS) and the SL secondary synchronization signal (S-SSS), each of which occupies 2 symbols and 127 subcarriers. The physical sidelink broadcast channel (PSBCH) occupies 9 and 5 symbols in the normal and extended cyclic prefix cases, respectively, including the associated demodulation reference signal (DM-RS).

[0044] Regarding the physical layer process of HARQ feedback for the sidelink, SL HARQ feedback uses PSFCH and can operate in one of two options. In one option that can be configured for unicast and multicast, PSFCH uses resources allocated specifically for a single PSFCH transmitting UE to send ACK or NACK. In another option that can be configured for multicast, PSFCH sends NACK on resources that can be shared by multiple PSFCH transmitting UEs, or does not send PSFCH signals.

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

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

[0047] Regarding the physical layer procedures for CSI reporting, for unicast, the Channel State Information Reference Signal (CSI-RS) is supported for CSI measurement and reporting in the sidelink. The CSI report is carried in the SL MAC CE.

[0048] For measurements on the sidelink, the following UE measurement quantities are supported:

[0049] PSBCH reference signal received power (PSBCH RSRP);

[0050] PSSCH reference signal received power (PSSCH-RSRP);

[0051] PSCCH reference signal received power (PSCCH-RSRP);

[0052] Sidelink received signal strength indicator (SL RSSI);

[0053] Side link channel occupancy rate (SL CR);

[0054] Side Link Channel Busy Rate (SL CBR).

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

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

[0057] In the new wireless system 5G-NR, for each parameter set and carrier, a resource grid consisting of subcarriers and OFDM symbols is defined for uplink and downlink respectively. Each element in the resource grid is called a resource element and is identified according to the frequency index in the frequency domain and the symbol position in the time domain (see 3GPP TS 38.211v16.3.0).

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

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

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

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

[0062] - Selection of the AMF at UE attach when the route to the AMF cannot be determined from the information provided by the UE;

[0063] - Routing user plane data towards UPF(s);

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

[0065] -Connection establishment and release;

[0066] - Scheduling and transmission of paging messages;

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

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

[0069] -Transport level packet marking in uplink;

[0070] -Session management;

[0071] -Support network slicing;

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

[0073] -Support UE in RRC_INACTIVE state;

[0074] -Distribution function for NAS messages;

[0075] - Radio access network sharing;

[0076] - Dual connectivity;

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

[0078] The access and mobility management function (AMF) is responsible for the following main functions:

[0079] - Non-Access Stratum (NAS) signaling terminal;

[0080] -NAS signaling security;

[0081] -Access layer (AS) security control;

[0082] - Core Network (CN) inter-node signaling for mobility between 3GPP access networks; - Idle mode UE reachability (including control and execution of paging retransmissions);

[0083] -Registration area management;

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

[0085] -Access authentication;

[0086] -Access rights control, including checking roaming rights;

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

[0088] -Support network slicing;

[0089] -Session Management Function (SMF) selection.

[0090] In addition, the User Plane Function (UPF) is responsible for the following main functions:

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

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

[0093] -Packet routing and forwarding;

[0094] -Packet inspection and user plane part enforced by policy rules;

[0095] - Traffic usage report;

[0096] - Uplink classifier that supports routing traffic flows to data networks;

[0097] -Support branch points for multi-homed PDU sessions;

[0098] -QoS processing for user plane, e.g. packet filtering, gating, UL / DL rate enforcement;

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

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

[0101] Finally, the Session Management Function (SMF) is responsible for the following main functions:

[0102] -Session management;

[0103] -UE IP address allocation and management;

[0104] -Selection and control of UP function;

[0105] -Configure traffic steering at the User Plane Function (UPF) to route traffic to the correct destination;

[0106] -Policy implementation and QoS control part;

[0107] - Downlink data notification.

[0108] Figure 3 Some interactions between the UE, gNB and AMF (5GC entity) are shown in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED (see TS 38.300 V16.3.0). The transition steps are as follows:

[0109] 1.UE requests to establish a new connection from RRC_IDLE.

[0110] 2 / 2a.gNB completes the RRC establishment process.

[0111] NOTE: The following describes the scenario where the gNB rejects the request.

[0112] 3. The first NAS message from the UE (which is carried in RRCSetupComplete) is sent to the AMF.

[0113] 4 / 4a / 5 / 5a. Additional NAS messages may be exchanged between the UE and the AMF, see TS23.502.

[0114] 6. The AMF prepares the UE context data (including PDU session context, security keys, UE radio capabilities and UE security capabilities, etc.) and transmits it to the gNB.

[0115] 7 / 7a.gNB and UE activate AS security.

[0116] 8 / 8a.gNB performs reconfiguration to establish SRB2 and DRB.

[0117] 9. The gNB notifies the AMF that the establishment process is completed.

[0118] RRC is a high-level signaling (protocol) used for UE and gNB configuration. Specifically, the transition involves the AMF preparing the UE's context data (e.g., PDU session context, security keys, UE radio capabilities, and UE security capabilities, etc.) and transmitting it to the gNB through an INITIALCONTEXT SETUP REQUEST. The gNB then activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE and by the UE responding to the gNB with a SecurityModeComplete message. Thereafter, the gNB performs reconfiguration by sending an RRCReconfiguration message to the UE to establish a signaling radio bearer 2 (SRB2) and (multiple) data radio bearers (DRBs), and, in response, receiving an RRCReconfigurationComplete from the UE by the gNB. For a signaling-only connection, the steps related to RRCReconfiguration are skipped since SRB2 and DRBs are not established. Finally, the gNB notifies the AMF that the configuration process is completed through the INITIAL CONTEXTSETUP RESPONSE message.

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

[0120] URLLC use cases have stringent requirements on 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, telemedicine surgery, distribution automation in smart grids, transportation safety, etc. Ultra-reliability of URLLC is supported by identifying technologies that meet the requirements set through TR38.913. For NR URLLC in system release 15, the key requirements include a target user plane latency of 0.5ms for UL (uplink) and a target user plane latency of 0.5ms for DL ​​(downlink). For a 32-byte packet size with a user plane latency of 1ms, the general URLLC requirement for one packet transmission is a BLER (block error rate) of 1E-5.

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

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

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

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

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

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

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

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

[0129] Figure 5 The 5G NR non-roaming reference architecture is shown (see, e.g., 3GPP TS 23.501 v16.7.0 or v17.1.1 Section 4.2.3). Application Function (AF) (e.g., in Figure 4 The external application server that hosts 5G services (described exemplarily in the 3GPP Core Network) interacts with the 3GPP core network to provide services, such as to support the application's influence on traffic routing, access to the network exposure function (NEF), or interacting with the policy framework (e.g., QoS control) for policy control (see Policy Control Function (PCF)). Based on the operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that are not allowed by the operator to directly access network functions interact with related network functions using the external exposure framework via NEF.

[0130] Figure 5 Additional functional units in the 5G architecture for V2X communication are shown, 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 5GC, as well as V2X application server (V2AS) and data network (DN) (e.g., operator service, Internet access or third-party service). All or part of the core network functions and application services can be deployed and run in a cloud computing environment.

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

[0132] Figure 6A diagram illustrating a configuration update procedure between two Next Generation Radio Access Network (NG-RAN) nodes 602 and 604 is shown. The configuration update procedure is used to update configuration messages required for two NG-RAN nodes to properly interoperate over the Xn-C interface. The NG-RAN logical node 1 (also known as gNB or ng-eNB) first initiates the configuration update procedure by transmitting a NG-RAN Configuration Update message to the peer NG-RAN node 2. The NG-RAN node 2 responds with a gNB-DU Configuration Update Confirm message to confirm that it has successfully updated the configuration data. If the NG-RAN node 2 is unable to accept the update, it shall respond with a NG-RAN NODE CONFIGURATION UPDATE FAILURE message along with an appropriate cause value.

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

[0134] Figure 8 A diagram 800 illustrating a configuration update procedure between a gNB distributed unit (DU) 802 and a gNB centralized unit (CU) 804 is shown. The gNB-DU 802 first initiates the configuration update procedure by transmitting a gNB-DU Configuration Update message to the gNB-CU, which includes the appropriate updated configuration data set that it has just put into operational use. The gNB-CU 804 responds with a gNB-DU Configuration Update Confirm message to confirm that it has successfully updated the configuration data. The updated configuration data shall be stored in both nodes 802 and 804 and used while there is an operational transport network layer (TNL) association, or until any further updates are performed. If the gNB-CU 804 is unable to accept the update, it shall respond with a gNB-DU Configuration Update Failure (not shown) message with an appropriate cause value.

[0135] As mentioned earlier, a new system release 18 study item was approved at the RAN#94-e [RP-213591] meeting, named "study on evolution of NR duplex operation", and one of the main topics is to study how to enable sub-band non-overlapping full-duplex (SBFD) within the traditional time division duplex (TDD) band. For the gNB side, (quasi) full-duplex is done, while for the UE side, half-duplex can be used.

[0136] Fig. 9 An exemplary legacy TDD slot format 902 and an exemplary SBFD or cross-division duplex (XDD) slot format 904 for inter-gNB coordination according to system release 15 / 16 / 17 are described. In this example, the legacy TDD band and SBFD / XDD are changed from an initial TDD band with four slots (four different time resource allocations) of slot format "DFFU" according to L1 signaling, where slot formats "D", "U" and "F" correspond to downlink communication, uplink communication and semi-static flexible (uplink and / or downlink) communication, respectively. After receiving L1 signaling, the second and third slot formats of the legacy TDD band are changed from "F" to "D" and "U", respectively. For SBFD / XDD, the first three slot formats (slots n, n+1 and n+2) of the TDD band are separated into three different sub-bands (three different frequency resource allocations), each with its own slot format according to L1 signaling. In this way, it allows the traditional TDD bands DL and UL to exist simultaneously, for example, the first time slot formats in the first, second and third subbands are "D", "U" and "D", respectively. These subbands are then used to separate transmission directions, for example, to three different UEs. For non-separated time slots, for example, time slot n+3, time slot formats across the frequency domain will be sent to the uplink transmission direction. Here, for example, the "DDUU" time slot format in the first subband #1 is transmitted to UE#1, the "UUUU" time slot format in the second subband #2 is transmitted to UE#2, and the "DUUU" time slot format in the third subband #3 is transmitted to UE#3. Through this operation, it is intended to provide more UL time duration to enhance UL coverage, reduce latency and increase UL capacity.

[0137] In TDD, when different TDD DL / UL patterns (time slot formats) are used between neighboring cells / gNBs, UL transmission in one cell / gNB may interfere with DL reception in another cell / gNB, which is called Cross Link Interference (CLI). According to RP-2204432, it is observed that the UL performance of small cells with dynamic TDD DL / UL patterns (or dynamic time slot formats) is significantly affected by strong gNB-gNB CLI from macro cells in DL heavy TDD configuration. In other words, the victim gNB is significantly affected by the strongest CLI aggressor cell (e.g., the nearest macro gNB). When SBFD operation is deployed, the same observation still occurs, and inter-gNB CLI becomes a critical issue to be handled. Therefore, this issue is listed as one of the main topics in RP-213591 to study inter-gNB and inter-UE CLI handling and determine solutions to manage these interferences.

[0138] In RAN#1109e, some candidate schemes are proposed for inter-gNB CLI handling in SBFD operation for further study in the following text, where the coordinated scheduling scheme is the main focus and the inter-gNB CLI can be either adjacent channel CLI, co-channel CLI, or both, depending on the deployment scenario.

[0139] According to the RAN#1109e agreement, for potential enhancement studies of dynamic / flexible TDD and / or SBFD, the following are considered as candidates for potential enhancement methods for inter-gNB CLI processing, and the candidate solutions can be further prioritized or narrowed in future meetings:

[0140] -gNB to gNB CLI measurement and reporting

[0141] - Coordination and scheduling

[0142] - Spatial domain enhancement

[0143] -Advanced Receiver

[0144] - UE and gNB transmission and reception timing

[0145] -Power control based solution

[0146] - Potential enhancements to Rel-16 RIM

[0147] -Sensor-based mechanism

[0148] - Note: It should be determined whether the specific solution requires OTA or backhaul information exchange

[0149] - Note: Any other scheme(s) for inter-gNB CLI processing are not excluded

[0150] - Note: For potential enhancements of dynamic / flexible TDD and / or SBFD, leveraging the results of Rel-15 and Rel-16 discussions while avoiding duplication of the same discussions

[0151] -Note: Potential enhancements to SBFD will be discussed in 9.3.2

[0152] For inter-gNB CLI handling in TDD, system Release 16 inter-gNB coordination (e.g., TS 38.423 v16.10.0) supports the exchange of the intended TDD DL-UL configuration in a semi-static manner over the Xn / Fl interface (i.e., the semi-static slot format and cell-specific slot format configuration exchanged between gNBs via the higher layer parameter IntendedTDD-DL-ULConfiguration-NR, see Fig.11A ). The (multiple) gNBs need to take this information exchange into account when performing their own scheduling for inter-gNB CLI processing.

[0153] Although inter-gNB CLI handling in TDD has been discussed, how to achieve inter-gNB coordination of inter-gNB CLI handling in SBFD operation has not been specified. Fig.10 A diagram is described showing conventional inter-gNB coordination over TDD operation of system Release 16. If a UE with SBFD capability attempts to use inter-gNB coordination of system Release 16, the performance of possible CLI processing may not be ideal because inter-gNB coordination of system Release 16 only supports exchange of semi-static and cell-specific TDD UL-DL configurations and does not support exchange of dynamic slot formats or subband-based configurations between gNBs, and thus inter-gNB coordination of system Release 16 does not work well in SBFD operation.

[0154] On the other hand, SBFD operation may support a slot format dynamically indicated by a slot format indicator (SFI) in downlink control information (DCI) format 2_0 (e.g., slot formats #46-55 defined in TS38.213 Section 11.1.1), or a new slot format. The frequency domain resource allocation (i.e., subband allocation) of a DL-UL slot / symbol in SBFD operation may be different from Fig.10 The frequency domain resource allocation (i.e., subband allocation) of DL-UL slots / symbols for TDD operation is shown, resulting in different total amounts of CLI measured by (multiple) neighboring gNBs. Therefore, neighboring gNBs cannot obtain enough information to adjust their scheduling for inter-gNB CLI processing.

[0155] For inter-gNB coordination of CLI processing according to the present disclosure, multi-slot formats per cell are exchanged between gNBs, each of which corresponds to each subband in the cell. A subband includes a frequency domain resource allocation (e.g., a resource block (RB) / physical resource block (PRB) into which the frequency band of the cell is divided). These subbands do not overlap with each other and are used to separate different transmission directions.

[0156] Fig.11A The legacy TDD format 1102 used in inter-gNB coordination of inter-gNB CLI processing in system release 16 is shown. In inter-gNB coordination in system release 16, only per-cell cell-specific format timeslots for the legacy TDD band are exchanged between gNBs in a semi-static manner through the Xn / Fl interface through the current higher layer parameter IntendedTDD-DL-ULConfiguration-NR.

[0157] Fig. 11B An exemplary TDD format 1104 used in inter-gNB coordination for inter-gNB CLI processing according to various embodiments of the present disclosure is shown. In the inter-gNB coordination of the present disclosure, a multi-slot format (e.g., a UE-specific slot format) per gNB per cell based on a subband set (e.g., subband #1, subband #2, ..., subband #j) within a serving cell (or a legacy TDD frequency band) may be exchanged between gNBs in a semi-static manner via an Xn / Fl interface. This may be exchanged via the current higher layer parameter IntendedTDD-DL-ULConfiguration-NR or a new higher layer parameter to support inter-gNB CLI processing in SBFD operation.

[0158] Table 1 shows example slot format indicator information (i.e., multi-slot format per cell per gNB (e.g., gNB1, gNB2, gNB3; or gNB subscripts 1, 2, 3)) exchanged between gNBs for inter-gNB CLI processing according to various embodiments of the present disclosure. In this example, assuming that the gNB serves one cell, SFI i,j Indicates the slot format of gNB index i and subband index j. For example, in Table 1, the first column shows the gNB index i=1,..,3, and the second column shows the multi-slot format of subband indexes from 1 to j, such that SFI i,j For gNB i The time slot format of subband #j.

[0159] [Table 1] Example of exchanging multi-slot formats per gNB per cell, where each gNB serves one cell.

[0160] <![CDATA[gNB index gNB i > <![CDATA[Multi-slot format SFI i,j > Validity period (optional) 1 <![CDATA[SFI 1,j ,…,SFI 1,j ]]> a(ms or time slot) 2 <![CDATA[SFI 2,j ,…,SFI 2,j ]]> b(ms or time slot) 3 <![CDATA[SFI 3,j ,…,SFI 3,j ]]> c (ms or time slot)

[0161] For the case where the gNB serves multiple cells, the slot format of each cell from the multiple cells of the gNB can be expressed as SFI i,j,k , where i represents the gNB index, j represents the cell index, and k represents the subband index, as shown in Table 2.

[0162] [Table 2] Example of switching multi-slot formats per gNB per cell, where each gNB serves multiple cells.

[0163]

[0164]

[0165] Optionally, the validity period of the multi-slot format expressed in milliseconds (ms) or number of slots for each gNB (e.g., gNB1, gNB2, gNB3) is also exchanged. In addition, the validity period can be defined by a higher layer parameter, such as the higher layer parameter NRDL-ULTransmissionPeriodicity in the specification.

[0166] According to the present disclosure, after exchanging the multi-slot format per cell between gNBs, an enhanced DCI format 2_0 1114 obtained by enhancing the legacy DCI format 2_0 1112 is used to support the function of indicating the multi-slot format (SFI) per cell for each gNB. The enhanced DCI format 2_0 includes all or part of the SFI of different rows and columns (frequency and time resource allocation), and such DCI can be used by the gNB (gNB_i in this example). It can divide the TDD band 1104 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 then these subbands are used to separate transmission directions, for example, to gNB1, gNB2, and gNB3 respectively. Note that in addition to enhancing DCI format 2_0, other DCI formats can also be enhanced to indicate a multi-slot format, for example, the DCI format is specifically configured for the UE.

[0167] Fig.12 A schematic diagram illustrating an example configuration of a communication apparatus 1200 for inter-gNB coordination of inter-gNB CLI processing according to various embodiments of the present disclosure is shown. According to the present disclosure, the communication apparatus 1200 may be implemented as a base station configured for signal transmission or reception. Fig.12 As shown, the communication device 1200 may include a circuit 1214, at least one wireless transmitter 1202, at least one wireless receiver 1204, and at least one antenna 1212 (for simplicity, for illustration purposes, Fig.12Only one antenna is described in the figure). The circuit 1214 may include at least one controller 1206 for software and hardware assistance in performing the tasks that the at least one controller 1206 is designed to perform, including controlling communications in a multiple-input multiple-output (MIMO) wireless network with one or more other communication devices. The circuit 1214 may also include at least one transmit signal generator 111208 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 a downlink signal or a sidelink signal to be transmitted by the at least one wireless transmitter 1202, and the at least one receive signal processor 1210 to process an uplink signal, a downlink signal, or a sidelink signal received from one or more other communication devices by the at least one wireless receiver 1204. As shown in FIG. Fig.12 As shown, at least one transmit signal generator 1208 and at least one receive signal processor 1210 can be independent modules of the communication device 1200, which communicate with at least one controller 1206 to implement the above functions. Alternatively, at least one transmit signal generator 1208 and at least one receive signal processor 1210 can be included in at least one controller 1206. For those skilled in the art, it can be understood that the layout of these functional modules is flexible and can be changed according to actual needs and / or requirements. Data processing, storage and other related control devices can be provided on appropriate circuit boards and / or chipsets. In various embodiments, at least one wireless transmitter 1202, at least one wireless receiver 1104 and at least one antenna 1212 can be controlled by at least one controller 1206.

[0168] The communication device 1200 provides functions required for inter-gNB coordination for inter-gNB CLI processing. For example, the communication device 1200 can be a first base station, and the circuit 1214 (or at least one transmit signal generator 1208 in the circuit 1214) can be configured to generate a signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells, and the at least one wireless transmitter 1202 can send the signal to one or more other communication devices.

[0169] In an embodiment, the plurality of frequency segments of each of the one or more serving cells are formulated by dividing a frequency band of each of the one or more serving cells.

[0170] 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 a validity period.

[0171] In another embodiment, the at least one wireless transmitter 1202 may also send second information to at least one of the plurality of user equipments based on information of the plurality of time slot format sets using one or a combination of higher layer parameters or downlink control information.

[0172] In another embodiment, at least one wireless receiver 1204 may receive a request from one of the one or more second base stations, and circuit 1214 (or at least one transmit signal generator 1208 of circuit 1214) may be configured to generate a plurality of new time slot format sets corresponding to a plurality of frequency segments of one or more service cells and a signal including information of the plurality of new time slot format sets in response to receiving the request.

[0173] In one embodiment, circuit 1214 (or at least one transmit signal generator 1208 of circuit 1214) may be configured to generate a second signal comprising information of a plurality of updated frequency segments, wherein each of a plurality of time slot format sets corresponds to a plurality of updated frequency segments of one or more service cells.

[0174] For example, the communication device 1200 may be a second base station, and the at least one wireless receiver 1204 may receive a signal from another communication device, the signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells, wherein each of the one or more serving cells is attached to the other communication device. The circuit 1214 (or at least one controller 1206 of the circuit 1214) may be configured to perform a scheduling process based on the information.

[0175] According to an alternative embodiment of the present disclosure, the communication device 1200 provides the functions required for inter-gNB coordination of inter-gNB CLI processing. For example, the communication device 1200 can be a third base station, wherein the first service cell and the second service cell are attached to the third base station, the circuit 1214 (or at least one transmission signal generator 1208 of the circuit 1214) can be configured to generate a signal, the signal including information of a plurality of time slot format sets for the first service cell, wherein the time slot format set corresponds to a plurality of frequency segments of the first service cell, and the at least one wireless transmitter 1202 can send the signal to the second service cell.

[0176] Fig.13A flow chart 1300 illustrating a communication method for inter-gNB coordination for inter-gNB processing according to various embodiments of the present disclosure is shown. In step 1302, a step of generating a signal is performed, the signal including information of a plurality of time slot format sets for one or more serving cells, wherein each time slot format set in the plurality of time slot format sets corresponds to a plurality of frequency segments of each serving cell in the one or more serving cells. In step 1304, a step of sending the signal to one or more second base stations is performed.

[0177] In the following paragraphs, a first embodiment of the present disclosure is explained with reference to the exchange of slot format indicator information with basic overlapping / shared subband allocation for inter-gNB coordination.

[0178] Fig.14A A block diagram 1400 of an exemplary TDD band showing fully overlapping / shared subband allocation for inter-gNB coordination for inter-gNB CLI processing according to the first embodiment of the present disclosure is shown. In the frequency domain, subbands (e.g., subbands #1-7) are defined and fully shared (overlapped) in all cells of a group of neighboring gNBs (e.g., gNB#1 and gNB#2). There can be multiple sets of subbands for multiple groups of gNBs, and SFI information does not have to be exchanged for these subbands; while in the time domain, multi-slot formats (SFI information) per cell are exchanged between gNBs based on subbands. Each slot format in the multi-slot format corresponds to each subband.

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

[0180] Each slot format in the multi-slot format indicates how each symbol within a single slot is used. In particular, it defines which symbols are used for uplink, which symbols are used for downlink, and which symbols are used as flexible symbols within a specific slot. In the case where the flexible symbols are semi-static symbols, they can also be configured as downlink or uplink symbols by using a dedicated RRC configuration or a dynamic indication in the serving cell. In another case, when the UE operates in half-duplex time-division slot operation, the flexible symbols can be used as a guard interval for beam switching or uplink-downlink switching, etc. In addition, there can be different types of slot formats, thereby providing a high degree of flexibility in gNB scheduling, especially for TDD operation or SBFD operation. For example, there can be a slot format type for downlink heavy load transmission with (multiple) uplink symbols; or another slot format type for uplink heavy load transmission with (multiple) downlink control symbols; or another downlink heavy load transmission slot format without (multiple) uplink symbols, etc. Therefore, by applying a slot format or combining different slot formats in sequence in the time domain, the gNB can configure various different types of scheduling.

[0181] Upon receiving the SFI information by the corresponding gNB, at the cell of the corresponding gNB, the multi-slot format may be signaled to the UE or one or more of the multiple UEs attached to the corresponding gNB by using one or a combination of the following two options: (1) dedicated radio resource control (RRC) configuration, where the multi-slot format is semi-statically configured to the UE by using new dedicated RRC parameters; and (2) indication in the DCI, where the multi-slot format is indicated to the UE by enhancing the SFI indication with multiple SFI fields in DCI format 2_0, and the position bit of each of the multi-slot formats for each subband may be configurable or a bitmap.

[0182] In option 2, for example, refer to Fig. 14B , assuming that the gNB serves one cell and SFI ij For gNB i The timeslot format of subband #j of the UEFI subband is indicated dynamically in DCI format 2_0 by using multiple SFI fields. Dynamic timeslot formats #46-55 defined in TS38.213 Section 11.1.1 may also be indicated, which may not be indicated by using the current system release 16 gNB coordination.

[0183] It should be noted that the gNB can be a gNB as defined in TS 38.300 in a non-separated gNB scenario or a gNB distributed unit (gNB-DU) as defined in TS38.401 in a separated gNB scenario, and the gNB can serve one or more cells. In the non-separated gNB scenario, information exchange can be performed between gNBs based on the Xn interface, i.e., the responsibility of the gNB, e.g. Figure X In the separated gNB scenario, information exchange can be performed between gNB-DUs via the gNB Centralized Unit (gNB-CU) based on the F1 interface, i.e., the responsibility of the gNB-DU, as shown in Figure X X#1 and XX#2. For example, in a non-separated gNB scenario, the gNB exchanges multiple slot format sets of its own cell to a neighboring gNB via Xn exchange, for example, gNB#1 to gNB#2. In a separated gNB scenario, the gNB-DU exchanges multiple slot format sets of its own cell to the gNB-CU node via the F1 interface, and then exchanges to the neighboring gNB-DU via the F1 interface, or exchanges to the gNB via the F1 and Xn interfaces, for example, gNB-DU#1 to gNB-CU and then to gNB-DU#2 via the F1 interface, or gNB-DU#1 to gNB-CU and then to gNB via the F1 and Xn interfaces. It should also be noted that according to the current specification, the same slot format indicated by the SFI is generally applied to all RB sets of a group of UEs in the serving cell in TDD operation, while the multi-slot format SFI can be applied to different subbands (each subband includes a certain number of RBs) in SBFD operation. The bit width of multiple SFI fields can be provided by high-level parameters and is determined as log_2(subband size). Alternatively, the sizes of multiple SFI fields can be defined based on the number of gNBs and subbands in the group.

[0184] Fig.15A flow chart 1500 is shown 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 multi-slot formats (multi-slot formats per gNB per cell) for inter-gNB CLI processing based on subband for a gNB group operating in SBFD. Each of the multi-slot formats per gNB per cell is specific to each subband. In step 1504, each gNB in ​​the gNB group monitors inter-gNB CLI measurements. In step 1506, it is determined by each gNB whether the inter-gNB CLI is equal to or greater than the inter-gNB CLI threshold level (threshold #1). If the inter-gNB CLI is equal to or greater than threshold #1, step 1512 is performed, in which the gNB requests an update of the SFI information to include a new candidate multi-slot format. If it is determined that the inter-gNB CLI is below threshold #1, the gNB signals the multi-slot format to the UE or one or more of the multiple UEs attached to the gNB. Steps 1508 and 1510 illustrate signaling under option 1. Under Option 1, each gNB semi-statically configures the multi-slot format to its own (multiple) UEs in the serving cell using dedicated RRC parameters. In step 1508, each gNB configures multiple SFI fields for each cell using new dedicated RRC parameters, and the multiple SFI fields are used to indicate the multi-slot format to its own (multiple) UEs in the serving cell. In step 1510, the UE receives the RRC parameters to obtain the multi-slot format.

[0185] Fig.16A flow chart 1600 illustrating a second exemplary inter-gNB coordination process (option 2) for gNB CLI processing according to the first embodiment of the present disclosure is shown. In step 1602, the network configures multiple multi-slot formats (multi-slot formats per gNB per cell) for inter-gNB CLI processing based on subband for a gNB group operating in SBFD. Each of the multi-slot formats per gNB per cell is specific to each subband. In step 1604, each gNB in ​​the gNB group monitors inter-gNB CLI measurements. In step 1606, it is determined by each gNB whether the inter-gNB CLI is equal to or greater than the inter-gNB CLI threshold level (threshold #1). If the inter-gNB CLI is equal to or greater than threshold #1, step 1612 is performed, in which the gNB requests an update of the SFI information to include a new candidate multi-slot format. If it is determined that the inter-gNB CLI is below threshold #1, the gNB signals the multi-slot format to the UE or one or more of the multiple UEs attached to the gNB. Steps 1608 and 1610 illustrate signaling under option 2. In step 1608, each gNB configures multiple SFI fields for each cell in DCI format 2_0, which are used to indicate the multi-slot format to its own (multiple) UEs in the serving cell. Slot format SFI for each subband i,j The position bit of may be configurable or a bitmap. In step 1610, the UE monitors DCI format 2_0 to obtain a multi-slot format.

[0186] Fig.17A flowchart 1700 is shown illustrating a third exemplary inter-gNB coordination process (option 2) of gNB CLI processing according to the first embodiment of the present disclosure. In this example, inter-UE CLI measurements are considered. Specifically, in step 1702, the network configures multiple multi-slot formats (multi-slot formats per gNB per cell) for inter-gNB CLI processing based on subband for a gNB group operating in SBFD. Each of the multi-slot formats per gNB per cell is specific to each subband. In step 1704, each gNB in ​​the gNB group monitors the inter-gNB CLI measurements and receives reports from (multiple) UEs. In step 1706, it is determined by each gNB whether the inter-gNB CLI is equal to or greater than the inter-gNB CLI threshold level (threshold #1) and whether the inter-UE CLI is equal to or greater than the inter-UE CLI threshold level (threshold #2). If the inter-gNB CLI is equal to or greater than threshold #1 and the inter-UE CLI is equal to or greater than threshold #2, step 1712 is performed, in which the gNB requests to update the SFI information to include a new candidate multi-slot format. If it is determined that the inter-gNB CLI is below threshold #1 and the inter-UE CLI is below threshold #2, the gNB signals the multi-slot format to the UE or one or more of the multiple UEs attached to the gNB. In step 1708, each gNB configures multiple SFI fields per cell in DCI format 2_0 (option 2), which are used to indicate the multi-slot format to its own (multiple) UEs in the serving cell. Slot format SFI for each subband i,j The position bit of may be configurable or a bitmap. In step 1710, the UE monitors DCI format 2_0 to obtain a multi-slot format.

[0187] In the following paragraphs, a second embodiment of the present disclosure is explained with reference to the exchange of slot format indicator information in partially overlapping / shared subband allocation for inter-gNB coordination.

[0188] Fig. 14B A block diagram 1420 illustrating an exemplary TDD frequency band for partially overlapping / shared subband allocations for inter-gNB coordination for inter-gNB CLI processing according to the second embodiment of the present disclosure is shown. In the frequency domain, subbands are defined with partially overlapping subbands (e.g., subband #4) shared between cells in a gNB group, while there are also non-overlapping subbands between cells in the gNB group (e.g., subbands #1-3 allocated to gNB #1; subbands #5-7 allocated to gNB #2).

[0189] In one embodiment, partially overlapping subbands (e.g., subband #4) are defined as “impossible SBFD usage”, while the remaining non-overlapping subbands (e.g., subbands #1-3 and #5-7) are defined as “possible SBFD usage”. Fig. 14BAs shown. In an alternative embodiment, partially overlapping subbands (e.g., subband #4) are defined as "possible SBFD usage", while the remaining non-overlapping subbands (e.g., subbands #1-3 and #5-7) are defined as "impossible SBFD usage". In yet another embodiment, the combination of all subbands in the group is defined as "possible SBFD usage". Essentially, multi-slot formats in subbands defined as "possible SBFD usage" are exchanged. This limits the number of SFI information exchanges to only those for possible SBFD usage, thereby reducing the number of subbands used in SBFD operation, the signaling required between gNBs, and reducing CLI.

[0190] In the time domain, the multi-slot format (SFI information) per cell is exchanged between gNBs based on the subband of "possible SBFD use". The remaining operations are similar to the operations based on the multi-slot format on the subband within "possible SBFD use" in the first embodiment.

[0191] For example, in one embodiment, the multi-slot format of each subband in the "possible SBFD usage" of the cell may be updated based on its validity period. Alternatively, the multi-slot format of each subband in the "impossible SBFD usage" of the cell may be updated based on its validity period. In this way, the multi-slot format of each subband of the cell may also be updated with different periods / timings based on their respective validity periods. In another embodiment, the SFI information is exchanged upon receiving a request from the corresponding gNB.

[0192] In addition, when the SFI information is received by the corresponding gNB, at the cell of the corresponding gNB, the multi-slot format can be signaled to the UE or one or more UEs of the multiple UEs attached to the corresponding gNB by using one of the following two options or a combination thereof: (1) a dedicated radio resource control (RRC) configuration, in which the multi-slot format is semi-statically configured to the UE by using new dedicated RRC parameters; and (2) an indication in the DCI, in which the multi-slot format is indicated to the UE by enhancing the SFI indication with multiple SFI fields in DCI format 2_0, and the position bit of each of the multi-slot formats of each subband can be configurable or a bit map.

[0193] It should be noted that the number of multi-slot formats with fully overlapping subband allocations in the first embodiment may be different from the number with partially overlapping subband allocations in the second embodiment, depending on the subband set in "Possible SBFD Use".

[0194] In one implementation of the various embodiments of the present disclosure, in the time domain, the same timeslot format per cell used for all subbands (or all subbands in "possible SBFD usage") is exchanged between gNB groups.

[0195] [Table 3] An example of exchanging multi-slot formats per cell per gNB (e.g., gNB1, gNB2, gNB3; or gNB subscripts 1, 2, 3) between gNBs for inter-gNB coordination of CLI processing according to an embodiment of the present disclosure, where the same slot format per cell is used on all subbands. SFI i represents the slot format of the i-th row (for gNB on all subbands in the legacy TDD band) i In other words, SFI i It is in gNB i The timeslot format used on all subbands #1-j of .

[0196] <![CDATA[gNB index gNB i > <![CDATA[Multi - slot format SFI i,j > Multi-slot 1 <![CDATA[SFI1=0]]> 5 2 <![CDATA[SFI2=0]]> 5 3 <![CDATA[SFI3=0]]> 5

[0197] In another implementation of the embodiments of the present disclosure, in the frequency domain, instead of using defined subbands, subbands can be configured / updated (e.g., with different bandwidths and / or numbers of subbands) and exchanged. In the time domain, the same content described in the first or second embodiment can be used. The information exchange includes SFI information and subbands for each cell. Advantageously, this provides more flexible RRC configurations for SBFD operations. Optionally, at each cell in the group, the subbands configured in the frequency domain can be dynamically activated or deactivated in the time domain (i.e., for frequency resources).

[0198] [Table 4] An example of inter-gNB coordination for inter-gNB CLI processing by exchanging a multi-slot format per cell per gNB (e.g., gNB1, gNB2, gNB3; or gNB subscripts 1, 2, 3) between gNBs, where subbands are configured, according to an embodiment of the present disclosure.

[0199]

[0200] According to another implementation of the embodiments of the present disclosure, in the time domain, the multi-slot format per cell may be a new semi-static (SBFD) slot format per cell, which may be exchanged between gNBs. In addition to the legacy semi-static (TDD) slot format, this new semi-static (SBFD) slot format per cell may also be configurable in the current IntendedTDD-DL-ULConfigurarion-NR by using a new RRC parameter (e.g., intendedXDD-UL-DL-Configuration-r18). By using a new RRC parameter (such as tdd-UL-DL-ConfigurationXDD-r18), a different direction is indicated for the slot / symbol than that configured by the legacy (TDD) semi-static slot format.

[0201] In addition to the F symbol / slot, this new semi-static (SBFD) slot format allows overwriting of the legacy semi-static "D" and / or "U" symbol / slot. Each gNB in ​​the group schedules its own UE using the corresponding overwritten slot format. The overwriting rules are shown in Table 5.

[0202] [Table 5] An example of overwriting rules for the new semi-static (SBFD) time slot format according to an embodiment of the present disclosure.

[0203] Traditional semi-static time slot format D D D U F F F New semi-static timeslot format D U F U D U F Proposed Overwrite Result D U F U D U F

[0204] As shown in Table 5, the conventional semi-static time slot format "DDDUFFF" can be overwritten as "DUFUFUF", where in addition to the overwriting rule of overwriting "F" as "D" and "U" in the fifth and sixth time slot formats "F" according to system version 15 / 16 / 17, the second time slot format "D" and the third time slot format "D" can be overwritten as "U" and "F", respectively. This overwriting rule is different from the overwriting in system version 15 / 16 / 17, in which only the time slot format "F" can be overwritten.

[0205] Optionally, possible SBFD symbol / time slot usage and impossible SBFD symbol / time slot usage defined in the second embodiment may be introduced. In this case, possible SBFD symbol / time slot (which may be a conventional semi-static D and / or U symbol / time slot) is a symbol / time slot that is allowed to be overwritten in addition to conventional semi-static F symbol / time slot.

[0206] It should be noted that in system version 15 / 16 / 17, when the time slot format is configured, the coverage rules are as follows: (i) semi-static D and U codewords cannot be overwritten by UE-specific RRC or dynamic configuration (using DCI format 2_0); (ii) only semi-static F codewords can be overwritten as D or U by UE-specific RRC or DCI format 2_0; (iii) if the semi-static F codeword is not overwritten as D or U codeword by UE-specific 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 decide whether to send or receive.

[0207] Fig.18A block diagram illustrating an exemplary TDD band for inter-gNB coordination with a new semi-static slot format for inter-gNB CLU processing according to an embodiment of the present disclosure is shown. By exchanging IntendedTDD-DL-ULConfiguration-NR, the slot format "DDDU" of the legacy TDD band 1800 is configured in the new semi-static SBFD 1820 and is overwritten as "DUUU" (for subband #1), as "UUUU" (for subband #2), and as "DDUU" (for subband #3).

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

[0209] Physical gNB identification (ID)

[0210] Sounding Reference Signal (SRS) configuration

[0211] Beam coordination (beam index pairs between gNBs)

[0212] 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))

[0213] Subband Index

[0214] SRS-RSRP refers to the linear average of the power contribution of the SRS to be measured on the configured resource elements within the measurement frequency bandwidth considered in the time resources in the configured measurement occasion; while CLI-RSSI refers to the linear average of the total received power observed only in specific OFDM symbols of (multiple) measurement time resources on the configured resource elements in the measurement bandwidth for measurement by the UE.

[0215] According to various embodiments of the present disclosure, information exchange may also be performed over a wireless or backhaul-based framework. Although the embodiments are described for a group of neighboring gNBs, it is understood that the embodiments may be applied to all gNBs in the network.

[0216] Although not described, the skilled person will understand that this inter-gNB coordination of gNBCLI processing is applicable to intra-gNB coordination of cell CLI processing, assuming that one gNB serves multiple cells.

[0217] As described above, the table of multi-slot formats for the group of neighboring gNBs can be configurable in IntendedTDD-DL-ULConfiguration-NR via IntendedXDD-UL-DL-Configuration-r18, where gNB_i is the index of the gNB in ​​the group GroupOnB, slotConfiguration-Lis_XDD includes candidate dynamic slot formats for XDD operation (e.g., slot formats #46-#55 in TS38.213), and SFI_ij indicates the multi-dynamic slot formats of the predefined 3 subbands (where the subband index is from 1 to 3) of gNB_i. The following is an example of the format of IntendedTDD-DL-ULConfiguration-NR, IntendedXDD-UL-DL-Configuration-r18, and SlotConfiguration_XDD:

[0218]

[0219] In an alternative embodiment, for inter-gNB CLI handling in SBFD operation, information exchange between gNBs is performed dynamically and updated frequently. The information exchange includes at least the subband set and the corresponding multi-slot format. For the wireless-based framework, the gNB transmits the information exchange in the DCI to another gNB over the air interface; while for the backhaul-based framework, the gNB transmits the information in the IntendedTDD-DL-ULConfiguration-NR IE with a transmission periodicity to another gNB on a per-slot basis through the wired backhaul network. However, since this may generate a large amount of information exchange and is more suitable for intra-gNB coordination for handling inter-cell CLI, where the gNB serves multiple cells in a centralized RAN or sector operation, etc.

[0220] For the above embodiments, "exchanged between gNBs" may be replaced with "sent to another gNB" or "transmitted to another gNB". In addition, "exchanged between gNBs" may be replaced with "sent to a user equipment (UE)" or "transmitted to a UE".

[0221] According to the present disclosure, various examples are described below:

[0222] 1. A first base station, comprising:

[0223] A circuit configured to generate a signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells; and

[0224] The transmitter sends the signal to one or more second base stations.

[0225] 2. The first base station according to Example 1, wherein the multiple frequency segments of each of the one or more service cells are formulated by dividing the frequency band of each of the one or more service cells.

[0226] 3. The first base station according to Example 1 or 2, wherein each time slot format in each time slot format set in multiple time slot format sets corresponds to one of multiple frequency segments of each service cell in one or more service cells.

[0227] 4. The first base station according to any one of Examples 1-3, wherein the multiple frequency segments do not overlap with each other.

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

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

[0230] 7. The first base station according to any one of Examples 1-5, wherein the validity period of one time slot format set among the multiple time slot format sets is different from the validity period of another time slot format set among the multiple time slot format sets.

[0231] 8. The first base station according to any one of Examples 1-4, wherein the signal includes information on a validity period of each time slot format set in a plurality of time slot format sets, and the circuit is configured to generate a new time slot format set in response to expiration of the validity period to replace each time slot format set in the plurality of time slot format sets.

[0232] 9. The first base station according to Example 8, wherein each time slot format in each time slot format set in multiple time slot format sets indicates a set of transmission directions in a specific time slot, which transmission direction is an uplink direction, a downlink direction, or both, and a new time slot format set only replaces one or more transmission directions in the set of transmission directions in the specific time slot.

[0233] 10. The first base station according to any one of Examples 1-9, wherein the transmitter also sends second information to at least one of a plurality of user devices using one or a combination of high-level parameters or downlink control information based on information of a plurality of time slot format sets.

[0234] 11. According to any one of Examples 1-10, the first base station also includes a receiver that receives a request from one of the one or more second base stations, and the circuit is also configured to generate a plurality of new time slot format sets corresponding to a plurality of frequency segments of one or more service cells and a signal including information of the plurality of new time slot format sets in response to receiving the request.

[0235] 12. The first base station according to any one of Examples 1-11, wherein the multiple time slot format sets include a first time slot format set and a second time slot format set, and the one or more service cells include one or more first service cells attached to the first base station, and one or more second service cells attached to a second base station among the one or more second base stations, wherein the first time slot format set corresponds to one or more first frequency segments among a plurality of frequency segments in the one or more first service cells, and the second time slot format set corresponds to one or more second frequency band segments among a plurality of frequency segments in the one or more second service cells, and wherein at least one of the one or more first frequency segments does not overlap with one or more second frequency segments, and / or at least one of the one or more second frequency segments does not overlap with one or more first frequency segments.

[0236] 13. The first base station according to Example 12, wherein the information of multiple time slot format sets includes information of a first time slot format set and a second time slot format set, and the first time slot format set and the second time slot format set respectively correspond only to 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.

[0237] 14. The first base station according to Example 12, wherein the information of multiple time slot format sets includes information of a first time slot format set and a second time slot format set, and the first time slot format set and the second time slot format set correspond only to one or more first frequency segments overlapping with one or more second frequency segments.

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

[0239] 16. The first base station according to any one of Examples 1-15, wherein each of a plurality of time slot format sets corresponding to a plurality of frequency segments of each service cell in one or more service cells includes a single time slot format.

[0240] 17. The first base station according to any one of Examples 1-16, wherein the circuit is also configured to generate a second signal, which includes information of multiple updated frequency segments, wherein each time slot format set in the multiple time slot format sets corresponds to multiple updated frequency segments of each service cell of one or more service cells.

[0241] 18. The first base station according to any one of Examples 1-17, wherein the transmitter is configured to send the signal to one or more second service cells via radio resource control signaling.

[0242] 19. The first base station according to any one of Examples 1-17, wherein the transmitter is configured to send the signal to one or more second service cells at each regular interval wirelessly in downlink control information or through radio resource control signaling on a wired network.

[0243] 20. The first base station according to any one of Examples 1-19, wherein the signal includes third information, and the third information includes at least one of the following: a physical cell identifier, an index of multiple frequency segments, a configuration of a sounding reference signal, beam coordination information, a beam index, and a cross-link interference measurement in each service cell in one or more service cells.

[0244] 21. A second base station, comprising:

[0245] a receiver, receiving a signal from a first base station, the signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells, wherein each of the one or more serving cells is affiliated with the first base station; and

[0246] The circuit is configured to perform a scheduling process based on the information.

[0247] 22. A third base station, wherein a first serving cell and one or more second serving cells are attached to the third base station, comprising:

[0248] A circuit configured to generate a signal, the signal including information of a time slot format set of a first serving cell, wherein the time slot format set corresponds to a plurality of frequency segments of the first serving cell; and

[0249] The transmitter sends the signal to one or more second serving cells.

[0250] 23. A communication method, comprising:

[0251] generating a signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells; and

[0252] The signal is transmitted to one or more second base stations.

[0253] In the following paragraphs, certain exemplary embodiments are explained with reference to terms related to a 5G core network and the present disclosure, which relate to a communication device and method for allocating one or more additional operation windows between two semi-statically configured SL DRX cycles to receive or transmit SL signals, namely:

[0254] Control Signal

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

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

[0257] Base Station

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

[0259] Uplink / Downlink / Sidelink

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

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

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

[0263] Data channel / control channel

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

[0265] Reference signal

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

[0267] Time interval

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

[0269] frequency band

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

[0271] communication

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

[0273] In addition, the present disclosure can be applied to any terrestrial network or other networks (NTN: non-terrestrial network) other than terrestrial networks using satellites or high altitude pseudo-satellites (HAPS). In addition, the present disclosure can also be applied to networks with larger cell sizes and terrestrial networks with larger delays compared to symbol lengths or time slot lengths, such as ultra-wideband transmission networks.

[0274] Antenna Port

[0275] An antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. That is, an antenna port does not necessarily refer to a physical antenna, and sometimes refers to an array antenna composed of multiple antennas, etc. For example, it is not defined how many physical antennas make up an antenna port, but rather, an antenna port is defined as the smallest unit through which a terminal is allowed to transmit a reference signal. An antenna port can also be defined as the smallest multiplication unit for precoding vector weighting.

[0276] The present disclosure can be implemented by software, hardware or software and hardware collaboration. Each functional block used in each of the above embodiments can be implemented in part or in whole by LSI such as integrated circuit, and each process described in each embodiment can be partially or completely controlled by the same LSI or a combination of LSI. LSI can be formed as a chip alone, or a chip can be formed to include some or all functional blocks. LSI can include data input and output coupled thereto. The LSI mentioned here can be called IC, system LSI, super LSI (super LSI) or very large LSI (ultraLSI) according to the different integration levels. However, the technology for implementing integrated circuits is not limited to LSI, and can also be implemented by using dedicated circuits, general-purpose processors or special-purpose processors. In addition, FPGA (field programmable gate array) that can be programmed after LSI manufacturing can also be used, or a reconfigurable processor can be used, wherein the connection and setting of LSI internal circuit units can be reconfigured. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI due to the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology can be used to integrate functional blocks. Biotechnology can also be applied.

[0277] The present disclosure may be implemented by any type of device, apparatus or system having a communication function, which are collectively referred to as communication devices.

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

[0279] Some non-limiting examples of communication devices include: phones (e.g., cellular (cell) phones, smartphones), tablet computers, personal computers (PCs) (e.g., laptop computers, desktop computers, netbook computers), cameras (e.g., digital cameras / camcorders), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, e-book readers, telehealth / telemedicine (e.g., telehealth and medical) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships), etc., as well as various combinations of the above.

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

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

[0282] The communication device may include devices such as controllers or sensors that are coupled to the communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or sensor that generates control signals or data signals that are used by the communication device that performs the communication functions of the communication device.

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

[0284] Those skilled in the art will appreciate that, without departing from the spirit or scope of the broad description of the present disclosure, many changes and / or modifications may be made to the present disclosure as shown in the specific embodiments. Therefore, the present embodiments should be considered in all aspects as illustrative and not restrictive.

Claims

1. A first base station, comprising: A circuit configured to generate a signal, the signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells; and A transmitter sends the signal to one or more second base stations.

2. The first base station according to claim 1, wherein: The multiple frequency segments of each of the one or more serving cells are formulated by dividing a frequency band of each of the one or more serving cells.

3. The first base station according to claim 1 or 2, wherein: Each time slot format in each of the plurality of time slot format sets corresponds to one of the plurality of frequency segments of the each of the one or more serving cells.

4. The first base station according to any one of claims 1 to 3, wherein: The multiple frequency segments do not overlap with each other.

5. The first base station according to any one of claims 1 to 4, wherein: Each time slot format in each of the plurality of time slot format sets indicates a set of transmission directions in a particular time slot, each transmission direction in the set of transmission directions being an uplink direction, a downlink direction, or both.

6. The first base station according to any one of claims 1 to 5, wherein: The validity period of one of the plurality of time slot format sets is different from the validity period of another of the plurality of time slot format sets.

7. The first base station according to any one of claims 1 to 4, wherein: The signal includes information of a validity period of each of the multiple time slot format sets, and the circuit is configured to generate a new time slot format set in response to expiration of the validity period to replace each of the multiple time slot format sets.

8. The first base station according to claim 7, wherein: Each time slot format in each of the multiple time slot format sets indicates a set of transmission directions in a specific time slot, wherein the transmission direction is an uplink direction, a downlink direction, or both, and the new time slot format set only replaces one or more transmission directions in the set of transmission directions in the specific time slot.

9. The first base station according to any one of claims 1 to 8, wherein: The transmitter also transmits second information to at least one of a plurality of user equipments using one or a combination of higher layer parameters or downlink control information based on the information of the plurality of time slot format sets.

10. The first base station according to any one of claims 1 to 10, wherein: The multiple time slot format sets include a first time slot format set and a second time slot format set, and the one or more service cells include one or more first service cells attached to the first base station, and one or more second service cells attached to a second base station among the one or more second base stations, wherein the first time slot format set corresponds to one or more first frequency segments among the multiple frequency segments of the one or more first service cells, and the second time slot format set corresponds to one or more second frequency segments among the multiple frequency segments of the one or more second service cells, and wherein 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.

11. The first base station according to any one of claims 1 to 10, wherein: The circuit is also configured to generate a second signal comprising information of a plurality of updated frequency segments, wherein each of the plurality of time slot format sets corresponds to the plurality of updated frequency segments of each of the one or more service cells.

12. The first base station according to any one of claims 1 to 11, wherein: The transmitter is configured to send the signal to the one or more second serving cells through radio resource control signaling.

13. The first base station according to any one of claims 1 to 12, wherein: The signal includes third information, and the third information includes at least one of the following: a physical cell identifier, an index of multiple frequency segments, a configuration of a sounding reference signal, beam coordination information, a beam index, and a cross-link interference measurement in each of the one or more service cells.

14. A third base station, wherein: The first serving cell and one or more second serving cells are attached to the third base station, including: A circuit configured to generate a signal, the signal comprising information of a time slot format set of the first serving cell, wherein the time slot format set corresponds to a plurality of frequency segments of the first serving cell; and A transmitter sends the signal to one or more second serving cells.

15. A communication method, comprising: generating a signal including information of a plurality of time slot format sets of one or more serving cells, wherein each of the plurality of time slot format sets corresponds to a plurality of frequency segments of each of the one or more serving cells; and The signal is transmitted to one or more second base stations.

Images