Method and Unit

Abstract

A distributed access network is disclosed in which information for configuring full duplex communication in terms of time division duplex is exchanged between nodes of the distributed access network.

Description

[Technical Field]

[0001] The present disclosure relates to communication systems. [Background technology]

[0002] The present disclosure relates particularly, but not exclusively, to wireless communication systems and devices that operate in accordance with 3rd Generation Partnership Project (3GPP®) standards or equivalents or derivatives thereof (including LTE-Advanced, Next Generation or 5G networks, future generations, and beyond). The present disclosure relates particularly, but not necessarily exclusively, to improved apparatus and methods that support full-duplex communication in Time Division Duplex (TDD) communication bands.

[0003] Previous evolutions of 3GPP standards were called the Long-Term Evolution (LTE) of the Evolved Packet Core (EPC) network and the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), commonly referred to as "4G." More recently, the terms "5G" and "new radio" (NR) have begun to be used to refer to evolving communications technologies expected to support a variety of applications and services. Various details of 5G networks are described, for example, in the "NGMN 5G White Paper" V1.0 by the Next Generation Mobile Networks (NGMN) Alliance, available at https: / / www.ngmn.org / 5g-white-paper.html. 3GPP intends to support 5G through the so-called 3GPP Next Generation (NextGen) Radio Access Network (RAN) and the 3GPP Next Generation Core Network.

[0004] Under 3GPP standards, a NodeB (or eNB in ​​LTE, gNB in ​​5G) is a Radio Access Network (RAN) node (or simply "access node," "access network node," "base station," or "RAN equipment") through which communication devices (user equipment or "UE") connect to the core network and communicate with other communication devices or remote servers. For simplicity, this application uses the terms access network node, RAN node, or base station to refer to any such access node.

[0005] For simplicity, this application uses the terms mobile device, user device, or UE to refer to any communication device that can connect to a core network via one or more base stations. Although this application may refer to mobile devices in the description, it will be understood that the described techniques can be implemented on any communication device (mobile and / or generally fixed) that can connect to a communication network to transmit / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0006] In current 5G architectures, the structure of a gNB can be split into two or more parts. In some RAN implementations, there are two parts: a Central Unit (CU) or gNB-CU, sometimes called a “control unit,” and a Distributed Unit (DU) or gNB-DU, connected by an F1 interface. This allows for the use of a “split” architecture. Typically, a “split” architecture is one in which “upper” CU layers (such as, but not limited to, the Packet Data Convergence Protocol (PDCP) layer and the Radio Resource Control (RRC) layer) and “lower” DU layers (such as, but not limited to, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical (PHY) layer) are separated between a particular CU and one or more DUs connected to and controlled by that CU via the F1 interface. Thus, for example, the higher layer CU functions of several gNBs may be implemented centrally (e.g., by a single processing unit or in a cloud-based or virtualized system) while the lower layer DU functions are kept local and separate in each gNB.

[0007] More recently proposed distributed RAN architectures have introduced the concept of a Radio Unit (RU), sometimes called a "remote unit," in addition to a CU and DU. In this architecture, the RU is responsible for processing the digital front end (DFE), digital beamforming functions, and lower-level functions typically related to the PHY layer, while the DU typically processes higher-level functions of the PHY, RLC, and MAC layers. The CU in this architecture remains responsible for controlling one or more DUs (each DU corresponding to a different gNB) and for processing higher-layer signaling (typically the RRC and PDCP layers).

[0008] The actual division of functionality between the CU and DU (and possibly RU, if applicable) in these distributed architectures is flexible, allowing functionality to be optimized for different use cases. In effect, the split architecture allows 5G networks to use different distributions of protocol stacks between the CU and DU (and possibly RU), depending on, for example, midhaul availability and network design.

[0009] The choice of how to divide the functions within the architecture depends, among other factors, on the wireless network deployment scenario, constraints, and corresponding desired use cases. Important considerations include the need to support a specific quality of service for each service and real-time / non-real-time application offered, support for specific user density and load requirements in a given geographic area, and available transport networks with different performance levels.

[0010] So-called "open" interfaces between various elements of the RAN have been promoted to move away from vendor-specific arrangements toward arrangements where hardware and software components from various vendors can interoperate and be mixed and matched. In previous generations, the RAN incorporated a controller responsible for orchestrating and managing the RAN. With the development of 4G, the overall network architecture became flatter, and it was expected that base stations would use a standardized base station-to-base station (X2) interface to communicate with each other and handle resource allocation to enable an optimal subscriber experience. However, although the X2 application protocol has been largely standardized, various RAN vendors still produce their own variations of the X2 interface, making it difficult for mobile network operators (MNOs) to use equipment from more than one RAN vendor in a given location. More recently, there has been a move back to the controller concept to decompose hardware and software into their component parts and develop open interfaces between them. This movement, known as "open RAN," is particularly relevant for 5G and future generations, but can also be applied to earlier generations of RAN development.

[0011] In light of the 5G need for low latency in many 5G scenarios, the implementation of 5G concepts such as Control and User Plane Separation (CUPS), functional RAN partitioning, and network slicing requires a combination of advanced RAN virtualization and software-defined networking (SDN). This has led to the concept of the RAN Intelligent Controller (RIC), which is being developed as part of the open RAN movement. RICs include non-real-time (non-RT) RICs (for tasks requiring latency greater than one second) and near-real-time (NRT) RICs (with latency less than one second).

[0012] The quasi-RT RIC is responsible for load balancing, radio resource management, and interference detection and mitigation, controlled per UE. To facilitate this, the quasi-RT RIC provides a cloud-based infrastructure for controlling a distributed collection of RAN nodes (eNBs, gNBs, CUs, and DUs) in a specific geographic area via an open "southbound" interface (E2) protocol. The quasi-RT RIC also provides open "northbound" interfaces (A1 and O1) for the service management and orchestration (SMO) framework for operators. The quasi-RT RIC hosts microservices-based applications called xApps that are executed by the quasi-RT RIC and can collect near-real-time information using the E2 interface (on a UE- or cell-based basis). These xApps cover functions such as mobility management, admission control, and interference management. The quasi-RT RIC also provides advanced control functions to enforce network policies toward radios via the E2 interface, increasing efficiency and providing improved radio resource management (RRM). These control functions utilize analytical and data-driven techniques, including advanced machine learning (ML) / artificial intelligence (AI) tools, to improve resource management capabilities. The quasi-RT RIC's control over E2 nodes (e.g., eNB, gNB, CU, DU, etc.) is driven through policies and data provided by the non-RT RIC over the A1 interface. The allocation of RRM functions between the quasi-RT RIC and E2 nodes is subject to the capabilities of the E2 nodes and controlled by the quasi-RT RIC. For example, the quasi-RT RIC can monitor, suspend / stop, override, or control nodes via policies enabled by the non-RT RIC.The near-RT RIC can be deployed in several ways, for example, as a virtual network function (VNF), a set of virtual machines (VMs), or a cloud native function (CNF).

[0013] The non-RT RIC forms part of the SMO framework and connects to the quasi-RT RIC for RAN management and optimization. Network management applications in the non-RT RIC receive and act on data from the DU and CU, provided in a standardized format over the A1 interface. Non-RT RIC functions include configuration management, device management, fault management, performance management, and lifecycle management of all network elements in the network. All new RUs are self-configured by the non-RT RIC, reducing the need for manual intervention. The insights provided by the non-RT RIC into network operation allow MNOs to better understand their networks and therefore better optimize them by applying desired service and policy parameters. The non-RT RIC supports intelligent RAN optimization by providing policy-based guidance, model management, and enrichment information to the quasi-RT RIC for efficient and effective RAN optimization. The non-RT RIC can use data analytics and machine learning (ML) / artificial intelligence (AI) training / inference to identify appropriate RAN optimization actions that can use SMO services.

[0014] Separating the functions on the southbound and northbound interfaces enables more efficient and cost-effective radio resource management for real-time and non-real-time functions as the RIC customizes network optimization for each network environment and use case.

[0015] Until now, communication systems have used two main duplexing schemes: frequency division duplex (FDD) and time division duplex (TDD). In FDD, the frequency domain resource is divided into downlink (DL) and uplink (UL), while in TDD, the time domain resource is divided into DL and UL.

[0016] The appropriate duplexing scheme to be used in a given scenario largely depends on the spectrum, with some overlap. When low-frequency bands are used for communication, paired spectrum UL and DL resource allocations are commonly used, thus FDD. In contrast, in high-frequency bands, the use of unpaired spectrum, and therefore TDD, is becoming increasingly prevalent. Thus, TDD is widely used in commercial NR deployments. Given that the carrier frequencies supported by 5G and future communication generations (6G and beyond) are significantly higher than those of previous communication generations, improved techniques for providing efficient use of unpaired spectrum are and will continue to be increasingly important.

[0017] However, the duration allocation for UL on TDD carriers is too limited, which may result in reduced coverage, increased delay, and reduced capacity.

[0018] Full duplex (FD) operation, which involves sharing resources in both the frequency and time domains between the UL and DL within the bandwidth of a conventional TDD carrier, is one way to achieve improvements over conventional TDD performance. Therefore, extensions are currently being developed to implement full duplex operation in gNBs within TDD carriers, and there are currently no limitations on the frequency range that can be used for such FD operation. For now, half-duplex operation within TDD carriers is still envisioned for UEs, but full-duplex UE operation remains an option for the future. However, using FD can cause serious interference issues at both the base station and the UE that can be difficult to address.

[0019] There are several possible FD implementations that can be implemented on a TDD carrier, for example, subband non-overlapping, subband overlapping, and full overlapping.

[0020] 1-4, in subband non-overlapping FD (SBFD), also known as cross division duplex (XDD), non-overlapping UL and DL sub-bands may be configured in a TDD carrier (as in the general case shown in FIG. 1). As shown in FIGS. 1-4, each sub-band comprises a respective relatively "narrow" frequency band having a bandwidth that occupies only a portion of the total bandwidth available in the current TDD carrier configured for communication in the associated cell. Thus, a base station can simultaneously transmit and receive (full duplex) in different respective non-overlapping sub-bands to and from different UEs.

[0021] Figure 2 shows a specific example in which only one dedicated DL subband and one dedicated UL subband are configured on a TDD carrier. Figure 3 shows an example in which full-duplex operation is active from the first slot to the fourth slot, with a UL subband in the center of the frequency band and two DL subbands on either side of the DL subband. In the fifth slot, the base station uses legacy TDD operation (i.e., the entire frequency band is used for UL only). Figure 4 shows an example in which full-duplex operation is active from the first slot to the fifth slot. In the first four slots, a UL subband is in the center of the frequency band and two DL subbands are on either side of the DL subband. The fifth slot has a complementary UL / DL configuration compared to the first four slots.

[0022] In subband overlapping FD, the UL and DL can be configured similarly to subband non-overlapping FD, but different subbands can overlap in frequency. [Prior art documents] [Patent documents]

[0023] [Patent Document 1] European Patent Application Publication No. 4199387 [Patent Document 2] European Patent Application Publication No. 3442157 [Patent Document 3] Chinese Patent Application Publication No. 109302708 [Non-patent literature]

[0024] [Non-Patent Document 1] "NGMN 5G White Paper" V1.0. Summary of the Invention [Problem to be solved by the invention]

[0025] In full overlap FD, the entire available bandwidth can be used for UL or DL ​​transmission.

[0026] One of the key advantages of SBFD is that it increases the number of consecutive UL opportunities, thereby increasing UL coverage because SBFD can easily utilize multi-slot UL repetition. Therefore, the current focus is on developing techniques to implement subband non-overlapping FD operation and potential related enhancements for dynamic or flexible TDD. However, it will be appreciated that other FD implementations remain options for the future, and that the enhancements envisioned for subband non-overlapping FD may have advantages in other FD schemes.

[0027] When implementing FD schemes, several considerations must be taken into account. A consideration particularly relevant to SBFD (and other FD schemes) is, for example, the need to avoid self-interference. More specifically, a particular concern for implementing SBFD within a base station / access network is self-interference from DL subbands to UL subbands (also known as inter-subband interference). Specifically, although DL and UL operate using different frequency resources, DL transmissions can interfere with UL reception due to transceiver elements (e.g., power amplifiers) having nonlinear channel responses. Furthermore, high DL transmit power (compared to low UL signal power) can saturate analog-to-digital conversion (ADC) units, which can significantly affect the resolution of the ADC for UL reception. This occurs primarily because the analog filtering operation performed prior to the ADC filters only out-of-band transmissions, and therefore the filtered output may contain both the UL-directed signal and the dominant DL transmit signal.

[0028] Several self-interference mitigation techniques can be applied, for example: · Self-interference cancellation mechanisms (which can be digital, analog, or a combination of both). · Spatial domain mechanisms (e.g., using beams with minimal radial overlap to reduce DL to UL self-interference). Power domain mitigation methods (e.g., DL power reduction and / or UL power improvement). Frequency domain separation (e.g., introducing / increasing a frequency gap (i.e., guard band) between DL and UL subbands). · A filtering mechanism (e.g., performing an analog filtering operation before the ADC to output only the UL subband components). ·· The degree of isolation that can be achieved depends on both the analog filtering characteristics and any guard bands between the UL and DL subbands, and therefore the frequency domain solution and the filtering solution are generally considered together. Antenna isolation (given that many 5G implementations use antenna panels with multiple antenna elements, using different antenna elements for DL ​​and UL can provide isolation).

[0029] Various aspects of SBFD, particularly self-interference mitigation techniques, affect various layers of the RAN architecture. Therefore, in the context of a distributed RAN with several different RAN entities (such as RUs, DUs, and CUs defined, e.g., by an O-RAN architecture), implementing SBFD can be complex. In particular, the way SBFD and any self-interference techniques are configured can affect the operation of the distributed entities. For example, a different set of antenna elements may be available for uplink (and / or downlink) communications during SBFD slots / symbols than for non-SBFD slots / symbols. This may affect how beamforming is performed in the RU and / or controlled by the DU / CU.

[0030] It can therefore be seen that there is a need for improved procedures and apparatus that adequately address the requirements of SBFD in the context of distributed RAN architectures. [Means for solving the problem]

[0031] The present disclosure aims to provide one or more devices and one or more associated methods that at least partially address the above-mentioned needs.

[0032] In one aspect, the present disclosure provides a method performed by a first unit of an access network, comprising transmitting, to a second unit of the access network, capability information indicative of a capability of the first unit, the capability information indicative of at least one of: an ability of the first unit to communicate with a user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or an ability of the first unit to separate downlink communication from uplink communication in at least one time resource configured for both downlink and uplink communication.

[0033] The capability information may include, for each of a plurality of different separation schemes, information indicating a corresponding separation capability. The capability information may include, for the plurality of different separation schemes, information indicating a combined separation capability. The capability information may include information identifying configurations of the different separation schemes used to determine the combined separation capability. The capability information may include, for each of a plurality of different configurations of the different separation schemes, information indicating the respective combined separation capabilities.

[0034] The different separation schemes may include at least one of a first separation scheme in which at least one guard band is used to separate downlink communications from uplink communications, a second separation scheme in which different beams are used to separate downlink communications from uplink communications, a third separation scheme in which different antenna configurations are used to separate downlink communications from uplink communications, and / or a fourth separation scheme in which at least one cancellation mechanism is used to separate downlink communications from uplink communications.

[0035] The method may further include receiving a request from the second unit, in response to which the capability information is provided.

[0036] In another aspect, the present disclosure provides a method, performed by a second unit of an access network, comprising receiving capability information from a first unit of the access network, the capability information indicating at least one of: an ability of the first unit to communicate with a user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or an ability of the first unit to separate downlink communication from uplink communication in at least one time resource configured for both downlink and uplink communication.

[0037] In one aspect, the present disclosure provides a method performed by a second unit of an access network, comprising transmitting configuration information for a communication scheme to a first unit of the access network, wherein at least one time resource of a plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication.

[0038] The configuration information may be for configuring the first unit to communicate with at least one user equipment (UE) using a plurality of time resources according to a communication scheme.

[0039] The configuration information may include, for each time resource of the plurality of time resources, information indicating whether the time resource is of a first type, a second type, or a third type.

[0040] The first unit may have an existing configuration for a plurality of time resources, with at least one time resource configured as a first type and at least one time resource configured as a second type, and the configuration information may include information indicating which of the plurality of time resources for the existing configuration should be modified from the first type or the second type to a third type.

[0041] The configuration information may include first information for configuring each resource of the plurality of time resources to be of a first type for uplink communication or a second type for downlink communication in a first frequency region, respectively, and second information for configuring each resource of the plurality of time resources to be of a first type for uplink communication or a second type for downlink communication in a second frequency region, respectively.

[0042] The method further includes transmitting to the first unit information indicating at least one time resource of the first type and / or at least one time resource of the second type to be dynamically modified to become a time resource of a third type, and / or further information indicating at least one time resource of the third type to be dynamically modified to become a time resource of the first type or a time resource of the second type.

[0043] The timing can be adjusted such that the transmission of the further information is received by the first unit a minimum time before the first unit receives control information related to data transmission for the at least one UE by the second unit, and the further information can be transmitted together with the control information related to data transmission for the at least one UE by the second unit.

[0044] The method may further include transmitting to the first unit a frequency domain indication of at least one of an uplink subband, a downlink subband, and / or a guard band. The method may further include transmitting to the first unit an indication of a filter to be applied to the time resources configured as a third type.

[0045] The configuration information may include at least one of information indicating a configuration of a communication scheme to implement in the first unit, information indicating a desired configuration for the communication scheme in the second unit, and / or information indicating a configuration of a communication scheme for a neighboring unit of the access network or another access network.

[0046] The configuration information may include information for configuring at least one time resource as a third type, including at least one of: an indication regarding frequency resources of at least one uplink subband; an indication regarding frequency resources of at least one downlink subband; an indication regarding frequency resources of at least one guard band; an indication regarding a time position of at least one uplink subband or downlink subband; and / or a time position of at least one time resource of the third type.

[0047] The configuration information may be transmitted on condition that the first unit supports reception of configuration information including information for configuring at least one time resource as a third type or supports operation according to a communication scheme in which at least one time resource is configured as a third type.

[0048] The configuration information may include information for configuring at least one time resource as a third type, provided that the first unit supports reception of configuration information including information for configuring at least one time resource as a third type or supports operation according to a communication scheme in which at least one time resource is configured as a third type.

[0049] The configuration information may be second configuration information, and transmitting the same may include transmitting the first configuration information for configuring at least one time resource as the first type and for configuring at least one time resource as the second type, without configuring the time resource as the third type.

[0050] The configuration information may include first configuration information for configuring at least one time resource as a first type and at least one time resource as a second type, and second configuration information for configuring at least one time resource configured as the first type or the second type by the first configuration information as a third type.

[0051] In another aspect, the present disclosure provides a method, performed by a first unit of an access network, comprising receiving, from a second unit of the access network, configuration information for a communication scheme, wherein at least one time resource of a plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication.

[0052] The configuration information may be for configuring the first unit to communicate with at least one user equipment (UE) using a plurality of time resources according to a communication scheme. The method may further include determining a filter to be applied between the uplink subband and the downlink subband based on the guard band configured by the second unit.

[0053] The configuration information may be second configuration information, and receiving the configuration information may include receiving the first configuration information to configure at least one time resource as a first type and to configure at least one time resource as a second type, without configuring the time resource as a third type.

[0054] The method further includes: ignoring the second configuration information and using the first configuration information if the first unit does not support receiving configuration information including information for configuring at least one time resource as a third type or does not support operation according to a communication method in which at least one time resource is configured as the third type; and using the second configuration information if the first unit supports receiving configuration information including information for configuring at least one time resource as a third type or supports operation according to a communication method in which at least one time resource is configured as the third type.

[0055] The configuration information may include first configuration information for configuring at least one time resource as a first type and at least one time resource as a second type, and second configuration information for configuring at least one time resource configured as the first type or the second type by the first configuration information as a third type.

[0056] The method may further include: ignoring the second configuration information and using the first configuration information if the first unit does not support receiving configuration information including information for configuring at least one time resource as a third type or does not support operation according to a communication method in which at least one time resource is configured as the third type; and using the first configuration information and the second configuration information if the first unit supports receiving configuration information including information for configuring at least one time resource as a third type or supports operation according to a communication method in which at least one time resource is configured as the third type.

[0057] The method may further include using a configuration of time resources based on whether the first configuration information and / or the second configuration is used, and sending an indication to the second unit to indicate that the configuration of time resources used in the first unit is a configuration that includes at least one time resource configured as a third type, or that the configuration of time resources used in the first unit is a configuration that does not include at least one time resource configured as the third type.

[0058] The method further includes providing to the second unit an indication of whether the first unit supports receiving configuration information including information for configuring at least one time resource as a third type or an indication of whether the first unit supports operation according to a communication scheme in which at least one time resource is configured as a third type.

[0059] The method may further include, in response to receiving the configuration information, sending an error message to the second unit if the first unit does not support receiving configuration information including information for configuring at least one time resource as a third type, or if the first unit does not support operation according to a communication method in which at least one time resource is configured as a third type.

[0060] In another aspect, the present disclosure provides a method, performed by a first unit of an access network, transmitting beam or antenna related information to a second unit of the access network, the information including: first information indicating at least one of at least one first beam configuration for at least one time resource configured for both downlink and uplink communications and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for the at least one time resource configured for both downlink and uplink communications and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and third information indicating a first set of at least one antenna component that may or may not be used for downlink communications in the at least one time resource configured for both downlink and uplink communications and a second set of at least one antenna component that may or may not be used for downlink communications in the at least one time resource configured for both downlink and uplink communications; and fourth information indicating at least one first configuration of antennas for uplink communications in the at least one time resource configured for both downlink and uplink communications and at least one second configuration of antennas for downlink communications in the at least one time resource configured for both downlink and uplink communications.

[0061] In another aspect, the present disclosure provides a method performed by a second unit of an access network, the method comprising receiving beam or antenna related information from a first unit of the access network, the first information indicating at least one of at least one first beam configuration for at least one time resource configured for both downlink and uplink communications and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for the at least one time resource configured for both downlink and uplink communications and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and receiving beam- or antenna-related information including at least one of: third information indicating a first set of at least one antenna component that may or may not be used for uplink communications in at least one time resource configured for both downlink and uplink communications; third information indicating a second set of at least one antenna component that may or may not be used for downlink communications in at least one time resource configured for both downlink and uplink communications; and fourth information indicating at least one first configuration of antennas for uplink communications in at least one time resource configured for both downlink and uplink communications and at least one second configuration of antennas for downlink communications in at least one time resource configured for both downlink and uplink communications.

[0062] The method may further include using the beam or antenna related information when identifying a beam to be used for at least one time resource configured for both downlink and uplink communications.

[0063] The method may further include using beam or antenna related information when identifying at least one weighting to be applied to beamforming for at least one time resource configured for both downlink and uplink communications.

[0064] In another aspect, the present disclosure provides a first unit for an access network, the first unit comprising: means for transmitting, to a second unit of the access network, capability information indicative of a capability of the first unit, the information indicative of at least one of: an ability of the first unit to communicate with a user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or an ability of the first unit to separate downlink communication from uplink communication in at least one time resource configured for both downlink and uplink communication.

[0065] In another aspect, the present disclosure provides a second unit for an access network, comprising: means for receiving capability information from a first unit of the access network, the capability information indicating at least one of: an ability of the first unit to communicate with a user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or an ability of the first unit to separate downlink communication from uplink communication in at least one time resource configured for both downlink and uplink communication.

[0066] In another aspect, the present disclosure provides a second unit for an access network, comprising: means for transmitting configuration information for a communication scheme to a first unit of the access network, wherein at least one time resource of the plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication.

[0067] In another aspect, the present disclosure provides a first unit for an access network, comprising: means for receiving configuration information for a communication scheme from a second unit of the access network, wherein at least one time resource of a plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication.

[0068] In another aspect, the present disclosure provides a first unit for an access network, comprising means for transmitting beam or antenna related information to a second unit of the access network, the first information indicating at least one of at least one first beam configuration for at least one time resource configured for both downlink and uplink communications and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for the at least one time resource configured for both downlink and uplink communications and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and and third information indicating a first set of at least one antenna component that may or may not be used for uplink communications in at least one time resource configured for both downlink and uplink communications and a second set of at least one antenna component that may or may not be used for downlink communications in at least one time resource configured for both downlink and uplink communications; and fourth information indicating at least one first configuration of antennas for uplink communications in at least one time resource configured for both downlink and uplink communications and at least one second configuration of antennas for downlink communications in at least one time resource configured for both downlink and uplink communications.

[0069] In another aspect, the present disclosure provides a second unit for an access network, comprising means for receiving beam or antenna related information from a first unit of the access network, the information indicating at least one of at least one first beam configuration for at least one time resource configured for both downlink and uplink communications and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for the at least one time resource configured for both downlink and uplink communications and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and and third information indicating a first set of at least one antenna component that may or may not be used for uplink communications in at least one time resource configured for both downlink and uplink communications and a second set of at least one antenna component that may or may not be used for downlink communications in at least one time resource configured for both downlink and uplink communications; and fourth information indicating at least one first configuration of antennas for uplink communications in at least one time resource configured for both downlink and uplink communications and at least one second configuration of antennas for downlink communications in at least one time resource configured for both downlink and uplink communications.

[0070] Although the communication system to which this application relates is described in terms of full-duplex enhancements at the base station side, half-duplex operation at the UE side, and no restrictions on frequency ranges, it will be appreciated that the described enhancements may also have advantages in other communication systems, for example communication systems in which the UE is capable of full-duplex operation and / or where there are restrictions on the frequency ranges that can be used.

[0071] Embodiments of the present disclosure will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief explanation of the drawings]

[0072] [Figure 1] FIG. 1 is a simplified time-frequency diagram illustrating a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 2] FIG. 2 is a simplified time-frequency diagram illustrating a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 3] FIG. 3 is a simplified time-frequency diagram illustrating a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 4] FIG. 4 is a simplified time-frequency diagram illustrating a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 5] FIG. 5 is a simplified block schematic diagram illustrating an open RAN (ORAN) network architecture that can be implemented for the RAN of the telecommunications system of FIG. [Figure 6] FIG. 6 is a simplified block schematic diagram illustrating an open RAN (ORAN) network architecture that can be implemented for the RAN of the telecommunications system of FIG. [Figure 7] FIG. 7 illustrates a typical frame structure that may be used in the telecommunications system of FIG. [Figure 8]FIG. 8 is a simplified sequence diagram illustrating various slot configuration procedures that may be employed in the telecommunications system of FIG. [Figure 9] FIG. 9 is a diagram showing an example of a slot configuration configured by the procedure of FIG. [Figure 10] FIG. 10 is a simplified time-frequency diagram displaying an exemplary embodiment of a full-duplex configuration that can be used in the telecommunications system of FIG. [Figure 11] FIG. 11 is a simplified time-frequency diagram displaying an exemplary embodiment of another full-duplex configuration that can be used in the telecommunications system of FIG. [Figure 12] FIG. 12 is a simplified time-frequency diagram displaying an exemplary embodiment of another full-duplex configuration that can be used in the telecommunications system of FIG. [Figure 13] FIG. 13 is a simplified diagram of an antenna panel configuration for full-duplex communication in the telecommunications system of FIG. [Figure 14] FIG. 14 is a simplified sequence diagram illustrating various procedures for exchanging slot configurations that may be employed in the telecommunications system of FIG. [Figure 15] FIG. 15 is a simplified sequence diagram illustrating a control plane and user plane message forwarding procedure for transmitting user plane data on the downlink that may be used in the telecommunications system of FIG. [Figure 16] FIG. 16 is a diagram illustrating an example message structure for control plane and / or user plane messages that may be used in the telecommunications system of FIG. [Figure 17] FIG. 17 is a simplified sequence diagram illustrating a procedure for configuring a TDD pattern at a radio / remote unit that can be used in the telecommunications system of FIG. [Figure 18] FIG. 18 is a diagram illustrating a simplified antenna panel configuration that can be used for beamforming in the telecommunications system of FIG. [Figure 19] FIG. 19 is a diagram illustrating a transceiver virtualization model of a radio / remote unit that can be used in the telecommunications system of FIG. [Figure 20] FIG. 20 is a diagram illustrating a transceiver virtualization model of another radio / remote unit that can be used in the telecommunications system of FIG. [Figure 21] FIG. 21 is a diagram illustrating beamforming implementations that may be supported by communication system 1. [Figure 22] FIG. 22 is a diagram illustrating another beamforming implementation that may be supported by the communication system 1. [Figure 23] FIG. 23 is a simplified diagram of an example of weight-based dynamic beamforming that can be applied to the communication system 1. [Figure 24] FIG. 24 is a simplified sequence diagram illustrating a procedure for indicating the capabilities of a wireless / remote unit to a distributed unit that can be used in the telecommunications system of FIG. [Figure 25] FIG. 25 is a simplified sequence diagram illustrating another procedure for indicating wireless / remote unit capabilities to a distributed unit that may be used in the telecommunications system of FIG. [Figure 26] FIG. 26 is a simplified sequence diagram illustrating another procedure for indicating wireless / remote unit capabilities to a distributed unit that may be used in the telecommunications system of FIG. [Figure 27] FIG. 27 is a simplified sequence diagram illustrating another procedure for indicating wireless / remote unit capabilities to a distributed unit that may be used in the telecommunications system of FIG. [Figure 28] FIG. 28 is a simplified sequence diagram illustrating some possible procedures for TDD information exchange between a distributed unit and a wireless / remote unit that can be used in the telecommunications system of FIG. [Figure 29]FIG. 29 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a distributed unit and a wireless / remote unit that can be used in the telecommunications system of FIG. [Figure 30] FIG. 30 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a distributed unit and a wireless / remote unit that can be used in the telecommunications system of FIG. [Figure 31] FIG. 31 is a simplified sequence diagram showing a procedure for TDD information exchange between a transmitting node (central unit / distributed unit) and a receiving node (central unit / distributed unit) that can be used in the telecommunications system of FIG. [Figure 32] FIG. 32 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a transmitting node (central unit / distributed unit) and a receiving node (central unit / distributed unit) that can be used in the telecommunications system of FIG. [Figure 33] FIG. 33 is a simplified sequence diagram showing a procedure for TDD information exchange between a transmitting node (central unit / distributed unit) and a central unit that can be used in the telecommunications system of FIG. [Figure 34] FIG. 34 is a simplified sequence diagram showing another procedure for TDD information exchange between a transmitting node (central unit / distributed unit) and a central unit that can be used in the telecommunications system of FIG. [Figure 35] FIG. 35 is a simplified sequence diagram showing another procedure for TDD information exchange between a transmitting node (central unit / distributed unit) and a central unit that can be used in the telecommunications system of FIG. [Figure 36] FIG. 36 is a simplified sequence diagram illustrating a procedure for TDD information exchange between a central unit and a distributed unit that can be used in the telecommunications system of FIG. [Figure 37]FIG. 37 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a central unit and a distributed unit that can be used in the telecommunications system of FIG. [Figure 38] FIG. 38 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a central unit and a distributed unit that can be used in the telecommunications system of FIG. [Figure 39] FIG. 39 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a central unit and a distributed unit that can be used in the telecommunications system of FIG. [Figure 40] FIG. 40 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a central unit and a distributed unit that can be used in the telecommunications system of FIG. [Figure 41] FIG. 41 is a simplified sequence diagram illustrating another procedure for TDD information exchange between a central unit and a distributed unit that can be used in the telecommunications system of FIG. [Figure 42] FIG. 42 is a simplified sequence diagram illustrating some possible procedures for supporting antenna-based isolation that can be used in the telecommunications system of FIG. [Figure 43] FIG. 43 is a simplified schematic block diagram showing the main components of user equipment for the telecommunications system illustrated in FIG. [Figure 44] FIG. 44 is a simplified schematic block diagram showing the main components of a radio / remote unit of a RAN for the telecommunications system shown in FIG. [Figure 45] FIG. 45 is a simplified schematic block diagram showing the main components of a distributed unit of a RAN for the telecommunications system shown in FIG. [Figure 46] FIG. 46 is a simplified schematic block diagram showing the main components of a central unit of a RAN for the telecommunications system shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0073] overview An exemplary telecommunications system will now be described in general terms, by way of example only, with reference to Figures 5 to 23.

[0074] FIG. 5 is a schematic diagram of a mobile ("cellular" or "wireless") communications system 1 to which embodiments of the present disclosure may be applied.

[0075] In communication system 1, user equipment (UEs) 3-1, 3-2, 3-3 (e.g., mobile phones and / or other mobile devices) can communicate with one another via a radio access network (RAN) 5 that operates according to one or more compatible radio access technologies (RATs). In the illustrated embodiment, RAN 5 comprises RAN equipment (or (R)AN nodes) forming distributed NR / 5G base stations or "gNBs" that operate one or more associated cells 9. Communications via RAN 5 are typically routed through a core network 7 (e.g., a 5G core network or an evolved packet core (EPC) network).

[0076] For illustrative purposes, three UEs 3 and one RAN 5 are shown in FIG. 5, however, those skilled in the art will appreciate that when the system is implemented it will typically include other RAN nodes and UEs.

[0077] Each RAN 5 controls one or more associated cells 9, either directly or indirectly via one or more other nodes (e.g., home base stations, repeaters, remote radio heads, distributed units, etc.). It will be appreciated that the RAN nodes may be configured to support both 4G and 5G, and / or any other 3GPP or non-3GPP communication protocols.

[0078] As can be seen in Figure 5, in this example, the illustrated RAN node comprises a distributed base station including multiple radio / remote units (RUs) 5a, distributed units (DUs) 5b, and a central unit (CU) 5c. Figure 6 is a simplified block diagram illustrating a possible open RAN (ORAN) network architecture for the RAN 5 of Figure 5, although it will be understood that the RAN is not limited to this architecture.

[0079] As can be seen in Figures 5 and 6, the CU 5c uses a separated control plane and user plane, itself divided between an ("open") control plane function (CU-CP / O-CU-CP) 5c-C and an ("open") user plane function (CU-UP / O-CU-UP) 5c-U, which communicate with the DU (or "O-DU") via an F1-C logical interface and an F1-U logical interface, respectively (together forming an F1 interface (or "reference point")), and with each other via an E1 logical interface.

[0080] The illustrated RAN nodes are controlled by a RAN intelligent controller (RIC) 13, which comprises a non-real time RIC (non-RT-RIC) 13-1 and a near-real time RIC (near-RT-RIC) 13-2, which communicate with each other via an A1 interface. The near-real time RIC 13-2 supports tasks requiring low latency (less than one second), while the non-real time RIC 13-1 supports tasks that can be performed with longer latency (greater than one second). The near-real time RIC 13-2 is responsible for load balancing, resource (resource block (RB)) management, and interference detection and mitigation, all controlled per UE. The non-real time RIC 13-1 forms part of the service management and orchestration (SMO) layer 30 and communicates with the near-real time RIC 13-2 via the A1 interface for management and optimization of the RAN 5. As can be seen in Figure 6, in terms of the ORAN architecture, a cloud computing platform 32, known as the Open Cloud or O-Cloud, is provided. The O-Cloud 32 comprises physical infrastructure nodes to host the O-RAN CUs 5c, DUs 5b and to meet the O-RAN requirements for supporting software and appropriate management and orchestration functions. An O-Cloud node typically includes, for example, several processors (central processing units, or "CPUs"), storage devices, network infrastructure cards (NICs), basic input / output systems (BIOS), baseband management controllers (BMCs), and accelerators that are required to offload computationally intensive functions (e.g., forward error correction, or FEC).

[0081] The physical layer functions are split between the DU 5b and the RU 5a, with the upper physical layer functions provided by the DU 5b and the lower physical layer functions provided by the RU 5a. To handle the interaction between the DU 5b and the RU 5a, an open fronthaul (FH) control, user and synchronization plane (CUS plane) interface and a management plane (M-plane) interface are provided.

[0082] As can be seen in Figure 6, DU5b can be responsible for functions such as scrambling, modulation, layer mapping, resource element (RE) mapping, in-phase / quadrature (IQ) compression, and precoding (which can be bypassed in bypass mode). RU5a can be responsible for functions such as I / Q decompression, precoding, digital beamforming, inverse fast Fourier transformation (IFFT), CP addition, digital-to-analog conversion, and / or analog beamforming. It can be seen that precoding can be performed in either DU5b or RU5a, and that there are other functions (e.g., optional, shown with dashed lines).

[0083] Above the physical layer, CU5c provides higher layer functions (e.g., but not limited to, the Packet Data Convergence Protocol (PDCP) layer and the Radio Resource Control (RRC) layer), and DU5b provides lower layer functions (e.g., but not limited to, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical (PHY) layer).

[0084] Although a distributed RAN node is shown and described, it will be appreciated that the RAN node may be provided in a non-distributed (or less distributed) form, for example as an integrated gNB or eNB (wherein at least some of the functionality of the RU 5a, DU 5b, and / or CU 5c are integrated into the same device).

[0085] As can be seen in Figure 5, UEs 3 and their serving RANs 5 are connected via a suitable air interface (e.g., the so-called "Uu" interface, etc.) Equipment of adjacent RANs 5 can be connected to each other via a suitable base station-to-base station interface (e.g., the so-called "X2" interface, "Xn" interface, etc.).

[0086] The core network 7 includes several logical nodes (or "functions") for supporting communications in the communication system 1. In this embodiment, the core network 7 comprises several control plane functions (CPFs) 10 and one or more user plane functions (UPFs) 11. The CPF 10 includes one or more Access and Mobility Management Functions (AMFs) 10-1, one or more Session Management Functions (SMFs), one or more unified data management (UDM) functions 10-3, and several other functions 10n (e.g., an Authentication Server Function (AUSF) that facilitates 5G security processes).

[0087] The communications system also includes an OAM system 14 that comprises one or more Operations, Administration and Maintenance (OAM) functions for provisioning and managing networks or elements within the wider communications system 1. The OAM 14 may be responsible for storing and analyzing several radio-related measurements and may perform several data analysis functions, including several RAN analyses.

[0088] The RAN 5 nodes are connected to core network nodes via appropriate interfaces (or "reference points"), such as the N2 reference point between the RAN 5 and the AMF 10-1 for communication of control signaling, and the N3 reference point between the RAN 5 and each UPF 11 for communication of user data. The UEs 3 are each connected to the AMFs 10-1 via a logical non-access stratum (NAS) connection over the N1 reference point (similar to the S1 reference point in LTE). It will be appreciated that N1 communications are generally routed transparently through the RAN nodes.

[0089] One or more UPFs 11 are connected to an external data network (eg an IP network such as the Internet) via reference point N6 for the communication of user data.

[0090] The AMF 10-1 performs mobility management related functions, maintains NAS signaling connections with each UE 3, and manages UE registration. The AMF 10-1 receives user information transmitted over the network and forwards the information to the SMF. The AMF 10-1 is also responsible for managing paging.

[0091] The SMF 10-2 provides session management functions (forming part of the MME functions in LTE) and also combines some control plane functions (provided by the Serving Gateway and Packet Data Network Gateway in LTE). The SMF 10-2 uses user information provided via the AMF 10-1 to determine which session manager is best assigned to the user. The SMF 10-2 can effectively be considered a gateway from the user plane to the network control plane. The SMF 10-2 also allocates IP addresses to each UE 3.

[0092] The UDM function 10-3 manages network user data in a single, centralized element. For example, the UDM 10-3 manages data for access permissions, user registration, and data network profiles, and provides subscriber data to the SMF. The UDM function 10-3 is typically provided as a cloud-native function and is typically paired with one or more user data repositories (UDRs), which store user data such as customer profile information, customer authentication information, and encryption keys for the information. Effectively, user information is stored in the UDR, and the UDM function 10-3 retrieves the data, sends it to other network functions, and manages it overall. The UDM 10-3 uses microservices for communication between the user plane and the control plane.

[0093] The RAN 5 of the communication system 1 is configured to operate at least one cell 9 on an associated TDD carrier operating in unpaired spectrum. It will be appreciated that the RAN 5 may also operate at least one cell 9 on an associated FDD carrier operating in paired spectrum.

[0094] The RAN 5 is also configured to transmit control information and user data via several downlink (DL) physical channels and to transmit several physical signals, and the UE 3 is configured to receive control information and user data via several DL physical channels and to transmit several physical signals, where the DL physical channels correspond to resource elements (REs) that carry information originated from higher layers and the DL physical signals correspond to REs that are used by the physical layer and do not carry information originated from higher layers.

[0095] The physical channels may include, for example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), and a physical downlink control channel (PDCCH). The PDSCH carries data that shares the capacity of the PDSCH on a time and frequency basis. The PDSCH can carry various data items, including, for example, user data, UE-specific higher layer control messages mapped down from higher channels, system information blocks (SIBs), and paging. The PDCCH carries downlink control information (DCI) to support several functions, including, for example, scheduling downlink transmissions on the PDSCH and also scheduling uplink data transmissions on the physical uplink shared channel (PUSCH). The PBCH provides a Master Information Block (MIB) to the UE 3. The PBCH also supports time and frequency synchronization in conjunction with the PDCCH, which aids in cell acquisition, selection, and reselection.

[0096] DL physical signals may include, for example, reference signals (RSs) and synchronization signals (SSs). Reference signals (sometimes known as pilot signals) are signals with predefined, special waveforms known to both the UE 3 and the RAN 5. Reference signals may include, for example, cell-specific reference signals, UE-specific reference signals (UE-RSs), downlink demodulation reference signals (DMRSs), and channel state information reference signals (CSI-RSs).

[0097] Similarly, the UE 3 is configured to transmit control information and user data via several uplink (UL) physical channels corresponding to REs carrying information originated from higher layers, and UL physical signals corresponding to REs used in the physical layer that do not carry information originated from higher layers. The base station 5 is configured to receive control information and user data via several UL physical channels corresponding to REs carrying information originated from higher layers, and UL physical signals corresponding to REs used in the physical layer that do not carry information originated from higher layers. The physical channels may include, for example, a PUSCH, a physical uplink control channel (PUCCH), and / or a physical random-access channel (PRACH). The UL physical signals may include, for example, demodulation reference signals (DMRS) for UL control / data signals and / or sounding reference signals (SRS) used for UL channel measurement.

[0098] Frame structure 7, which illustrates a typical frame structure that may be used in communication system 1, base stations 5 and UEs 3 of communication system 1 communicate with each other in the time domain using resources organized into frames of 10 ms length. Each frame comprises 10 equally sized subframes of 1 ms length. Each subframe is divided into one or more slots of 14 equal length Orthogonal Frequency-Division Multiplexing (OFDM) symbols.

[0099] As can be seen in FIG. 7, communication system 1 supports multiple different numerologies (subcarrier spacing (SCS), slot length, and therefore OFDM symbol length). Specifically, each numerology is identified by a parameter μ, where μ=0 represents 15 kHz (corresponding to LTE SCS). Currently, SCS for other values ​​of μ can actually be derived from μ=0 by scaling up by a power of two (i.e., SCS=15×2μkHz). The relationship between the parameter μ and SCS (Δf) is shown in Table 1. [Table 1]

[0100] Typical Slot Configuration Referring to Figures 8 and 9, the RAN 5 appropriately configures the use of slots within each cell 9 operating on a TDD carrier.

[0101] As can be seen in FIG. 8, which is a simplified sequence diagram illustrating various slot configuration procedures (S810, S814, S818) that can be applied in the communication system 1, the RAN 5 can employ several different procedures for configuring the slot usage in each cell 9 operating on a TDD carrier.

[0102] As seen in step S810, for example, the RAN 5 of the communication system 1 is configured to provide each cell 9 operating on a TDD carrier with a respective common (or "cell-specific") slot configuration. This common slot configuration can be provided to all UEs 3 in the cell using system information (as shown in S810a) (e.g., in a tdd-UL-DL-ConfigurationCommon information element (IE) in a system information block type 1 (SIB1)). This common slot configuration can also be provided to specific UEs 3 in the cell using dedicated (e.g., radio resource control (RRC)) signaling (e.g., in a tdd-UL-DL-ConfigurationCommon IE in an RRC message such as an RRC reconfiguration message) (as shown in S810b). Thus, upon receiving the common slot configuration, the UE 3 can set the common slot format configuration on a slot-by-slot basis across several slots (as seen in S812).

[0103] As can be seen in FIG. 9, which shows an example embodiment of a slot configuration configured according to the procedure of FIG. 8, slots can be configured as downlink-only slots, uplink-only slots, or as unassigned or "flexible" slots (which may be either downlink or uplink).

[0104] The common slot configuration is defined by several parameters provided by RAN5 as part of the common UL / DL slot configuration. These parameters include the slot configuration period (e.g., configured by the dl-UL-TransmissionPeriodicityIE), the number of slots having only downlink symbols (e.g., configured by the nrofDownlinkSlotsIE), the number of downlink symbols (e.g., configured by the nrofDownlinkSymbolsIE), the number of slots having only uplink symbols (e.g., configured by the nrofUplinkSlotsIE), and the number of uplink symbols (e.g., configured by the nrofUplinkSymbolsIE). As can be seen in Figure 9, these effectively form a repeating pattern of slot types (repeating with the slot configuration period), which in this example includes DL-only slots and symbols, followed by flexible slots and symbols, followed by UL-only slots and symbols. The repeating pattern starts with a DL group that includes a defined number of DL-only slots followed by a defined number of DL-only symbols in the next slot. The repeating pattern ends with a UL group containing a defined number of UL-only slots preceded by a defined number of UL-only symbols in the preceding slots. Flexible symbols and slots are symbols and slots between a DL group of DL-only slots and symbols and a UL group of UL-only slots and symbols.

[0105] As can be seen in step S814, the RAN 5 of the communication system 1 is also configured to provide, if necessary, a dedicated (or "UE-specific") slot configuration for a particular UE 3. This dedicated slot configuration can be provided to a particular UE 3 in a cell using dedicated (e.g., radio resource control (RRC)) signaling (e.g., in a tdd-UL-DL-ConfigurationDedicatedIE of an RRC message, such as an RRC reconfiguration message) (as shown in S815).

[0106] If a dedicated slot configuration is also provided to UE3 in addition to the common slot configuration, the dedicated slot configuration overrides only the symbols and slots configured as flexible symbols and slots, on a slot-by-slot basis, across the number of slots configured by the common slot configuration (as seen in the example of Figure 9).

[0107] If a dedicated configuration is provided, it includes one or more individual slot-specific configurations (e.g., using the slotSpecificConfigurationsToAddModListIE), each of which includes information identifying a particular slot within the slot configuration period defined by the common slot configuration (e.g., a slot index IE) and information defining the symbol structure (e.g., a symbols IE). The information defining the symbol structure provides the direction (downlink or uplink) of the symbols within the particular slot being configured. The information defining the symbol structure may, for example, indicate that all symbols in a particular slot are used for the downlink (e.g., by setting the symbolsIE to "allDownlink"), may indicate that all symbols in a particular slot are used for the uplink (e.g., by setting the symbolsIE to "allUplink"), or may explicitly indicate how many symbols are allocated to the downlink and uplink, respectively, at the beginning and end of a particular slot (e.g., the nrofDownlinkSymbolsIE may indicate the number of consecutive downlink symbols at the beginning of the slot identified by the slot index, and the nrofUplinkSymbolsIE may indicate the number of consecutive uplink symbols at the end of the slot identified by the slot index).

[0108] Thus, the UE 3 can set dedicated slot format configurations for each slot across several slots (as seen in S816).

[0109] Thus, UE 3 treats symbols in slots designated as downlink by the common slot configuration or by the dedicated slot configuration as available for reception. Similarly, UE 3 treats symbols in slots designated as uplink by the common slot configuration or by the dedicated slot configuration as available for transmission.

[0110] Even after the above-mentioned cell-specific and UE-specific slot configuration, there may still be some unassigned flexible slots / symbols remaining in the slot configuration. By utilizing Layer 1 signaling, the remaining flexible symbols (if any) can be dynamically reconfigured.

[0111] As seen in step S818, for example, the base station 5 of the communication system 1 is also configured to provide one or more dynamic slot configurations via a physical downlink control channel (PDCCH) to a group of one or more UEs 3. As shown in S819, downlink control information (DCI) using an appropriate DCI format (e.g., DCI format 2_0) can be used to provide one or more dynamic slot configurations to a specific group of one or more UEs 3 in the cell 9.

[0112] Indices of one or more slot format indicators (SFIs) are provided within the payload of the DCI for a group of one or more UEs 3. To address the DCI to one or more UEs 3 of the group and enable decoding, the cyclic redundancy check (CRC) bits of the DCI are scrambled with an associated radio network temporary identifier (RNTI), such as a slot format indicator RNTI (SFI-RNTI). One or more UEs in the group are assigned the same RNTI. Each UE 3 in the group is configured to extract its own SFI index based on the position of the SFI index in the DCI payload (this position can be configured, for example, by UE-specific RRC signaling). The RRC configuration may be by way of, for example, an RRC message carrying a PDCCH Serving Cell Configuration IE with a slot format indicator (SFI) IE that provides the SFI-RNTI for a particular serving cell (identified by a serving cell ID (e.g., by a servingCellId IE)), defines one or more slot format combinations (e.g., by a slotFormatCombinations IE), and specifies the starting position (bits) in the DCI of the SFI index applicable to the configured UE (e.g., by a positionInDCI IE).

[0113] Each SFI index provided by the DCI acts as a pointer to a slot format combination (each slot format corresponding to a respective combination of downlink symbols, uplink symbols, and / or flexible symbols) to define the slot format of each slot in several slots, starting from the slot where the UE detects the dynamic slot configuration DCI format.

[0114] Thus, for any slot that is indicated to UE3 as flexible by both the common slot configuration and the dedicated slot configuration, the DCI (as seen in the example of Figure 9) can be used to dynamically configure the downlink symbols, uplink symbols, and / or flexible symbols within that slot.

[0115] Therefore, the UE 3 can set a dynamic slot format configuration for each slot over several slots (as seen in S820).

[0116] Bandwidth Parts (BWPs) In communication system 1, the cell bandwidth can be divided into multiple bandwidth parts (BWPs), each of which starts at a corresponding common resource block (RB) and includes a set of contiguous RBs with a given numerology (sub-carrier spacing (SCS) and cyclic prefix (CP)) on a given carrier. Conventionally, it will be understood that the number of downlink symbols, uplink symbols, and flexible symbols in each slot of a (e.g., common or dedicated) slot configuration is common to each of the configured BWPs.

[0117] Thus, the UE 3 and the RAN 5 of the communication system 1 are configured to operate using BWPs. The RAN 5 can configure at least one downlink (DL) BWP (e.g., an initial DL BWP) for each serving cell of the UE 3. The RAN 5 can configure the UE 3 with up to (typically four) DL BWPs, with only a single DL BWP active at a given time. The UE 3 is not expected to receive PDSCH, PDCCH, or CSI-RS (except for radio resource management (RRM)) outside the active bandwidth portion. If the serving cell is configured with an uplink (UL), the RAN 5 can configure at least one UL BWP (e.g., an initial UL BWP). The RAN 5 can configure the UE 3 with up to (typically four) UL BWPs, with only one UL BWP active at a given time. The UE 3 does not transmit PUSCH or PUCCH outside the active bandwidth portion. In an active cell, the UE 3 does not transmit SRS outside the active bandwidth portion. It will be appreciated that the slot format identifier (e.g., the SFI index field value) of the dynamic slot configuration DCI format can indicate to the UE 3 the slot format of each slot within some slots of each DL BWP or each UL BWP.

[0118] A BWP identifier or index (BWP-ID) is used to refer to a BWP (independently in UL and DL), so that various radio resource control (RRC) configuration procedures can use the BWP-ID to associate them with a particular BWP.

[0119] In the case of paired spectrum (FDD), the DL BWP and UL BWP are configured separately, whereas in the case of unpaired spectrum (TDD), the DL BWP is effectively linked (paired) to the UL BWP, and the paired DL BWP and UL BWP share the same BWP-ID and center frequency (but possibly different bandwidths).

[0120] In particular, the base station 5 can configure the initial DL BWP (e.g., by the initialDownlinkBWP IE) via system information (e.g., system information block 1 (SIB1)) and / or via dedicated (e.g., RRC) signaling (e.g., RRC reconfiguration message, RRC resumption message, or RRC setup message). For example, common parameters for the initial DL BWP may be provided via system information, whereas UE-specific parameters may be provided via dedicated signaling (e.g., in a ServingCellConfig IE in an RRC message containing a dedicated UE-specific BWP configuration). The dedicated signaling may also include some cell-specific information that may be useful for specific scenarios (e.g., handover, etc.).

[0121] The RAN 5 can configure the initial UL BWP (e.g., by the initialUplinkBWP IE) via system information (e.g., system information block 1 (SIB1)) and / or via dedicated (e.g., RRC) signaling (e.g., RRC reconfiguration message, RRC resumption message, or RRC setup message). For example, one or more common parameters of the initial UL BWP may be provided via system information, whereas UE-specific parameters may be provided via dedicated signaling (e.g., in a ServingCellConfig IE in an RRC message containing a dedicated UE-specific BWP configuration). This provides configuration information for either a so-called special cell (SpCell), which is a primary cell (PCell) of a master cell group (MCG) or a secondary cell group (SCG), or a secondary cell (SCell).

[0122] The initial DL BWP and UL BWP are used at least for initial access before an RRC connection is established. The initial BWP has a BWP identifier (or "index") of 0 and is therefore known as BWP#0. Prior to receiving the system information defining the UE's initial DL BWP, each UE 3's DL BWP has a frequency range and numerology that corresponds to a control resource set (CORESET), e.g., CORESET#0, defined by a master information block (MIB) (or possibly dedicated RRC signaling). CORESET is used to carry downlink control information (DCI), which is transmitted over the PDCCH to schedule the system information blocks.

[0123] After receiving the system information (e.g., SIB1), the UE 3 configures the initial DL BWP and the initial UL BWP using the BWP configuration defined by the system information. The configured initial UL BWP is then used to initiate a random access procedure to set up an RRC connection. The RAN 5 configures the frequency domain location and bandwidth of the initial DL BWP in the system information so that the initial DL BWP includes the entire CORESET#0 in the frequency domain.

[0124] For each DL BWP in the set of DL BWPs for the primary cell (PCell), the UE 3 may be configured with a CORESET for a set of common search spaces (CSSs) of any type (sometimes called cell-specific search spaces (CSSs)) and a CORESET for a set of UE-specific search spaces (USSs). For each UL BWP in the set of UL BWPs for the PCell or PUCCH secondary cell, the UE 3 is configured with a resource set for PUCCH transmission.

[0125] The UE 3 is configured to switch its active BWP between its configured BWPs as needed. For example, switching in the UE 3 can be initiated by the reception of a scheduling DCI, by the expiration of an inactivity timer (e.g., BWPInactivityTimer), and / or by the initiation of a random access procedure.

[0126] Provides full-duplex communication The UE 3 and the RAN 5 of the communication system 1 are mutually configured to provide full duplex (FD) communication on a TDD carrier. Specifically, the UE 3 and the RAN 5 of the communication system 1 are configured to facilitate subband non-overlapping FD (SBFD) communication.

[0127] For example, as seen in FIG. 10, a simplified time-frequency diagram illustrating an exemplary embodiment of a full-duplex configuration that may be used in communication system 1, different UE-specific slot configurations allow a slot within a cell bandwidth to be effectively configured as an FD slot by configuring the slot as an uplink slot for one UE while the same slot is configured as a downlink slot for another UE (or vice versa). Thus, UL communication from one UE 3 in the cell bandwidth may occur in parallel with DL communication to another UE 3. While not specifically shown, it will be understood that parallel UL / DL communication may be configured at the symbol level as well as at the slot level.

[0128] It will be appreciated that the RAN 5 is configured to schedule frequency resources in any slot configured as an FD slot to ensure that frequency resources scheduled for UL communication by one UE 3 are part of a different sub-band than frequency resources scheduled for DL ​​communication to another UE 3. Thus, the RAN 5 is able to perform sub-band non-overlapping FD communication in this manner, while the UE 3 performs half-duplex communication.

[0129] Thus, the RAN 5 may configure one or more of the slots (and / or symbols) of a TDD carrier as FD slots (and / or symbols), or more specifically, as subband non-overlapping full duplex (SBFD) slots (and / or symbols) if SBFD is used for full-duplex operation. For convenience, from the RAN perspective, a slot / symbol that includes both an UL subband and a DL subband is generally referred to as an "SBFD" slot / symbol, or a slot / symbol with a configured UL subband / DL subband. Other slots / symbols that only include communication in a single transmit direction (UL or DL) are generally referred to as legacy (UL or DL) slots / symbols, or non-SBFD (UL or DL) slots / symbols.

[0130] It will be appreciated that from the UE's perspective, the SBFD slots or symbols may appear to be legacy UL, DL, or flexible symbols because the UE 3 is operating using half-duplex on a TDD carrier. However, the UE 3 may be informed of the FD / SBFD slots / symbols, either implicitly or explicitly, to enable the UE 3 to assist in interference avoidance / mitigation. For example, if the UE 3 can identify the FD / SBFD slots / symbols, the UE 3 can contribute to implementing appropriate frequency gaps between frequency resources used by that UE 3 (e.g., for UL or DL) and frequency resources used by another UE 3 (e.g., for UL or DL) and can avoid, reconfigure, and / or apply updated resources for a particular transmission / reception (e.g., for quasi-static transmissions such as SPS).

[0131] For example, the RAN 5 may explicitly indicate which slots / symbols are configured as FD / SBFD-type slots / symbols, e.g., dynamically using DCI with an appropriate DCI format and / or using a Medium Access Control (MAC) Control Element (CE). Alternatively or additionally, the RAN 5 may explicitly indicate which slots / symbols are configured as FD / SBFD-type slots / symbols via system information or dedicated (RRC) signaling (e.g., by frame structure signaling similar to that used for cell-specific and / or dedicated TDD UL / DL slot configuration). The UE 3 may implicitly determine whether a slot / symbol is configured as an FD / SBFD-type slot / symbol based on other information received from the network (RAN 5). For example, the UE may consider an SBFD slot to occur if the RAN 5 indicates that an UL transmission should occur during a DL-configured slot or that a DL transmission should occur during a UL-configured slot.

[0132] It will be appreciated that various variations exist for implementing SBFD, and that communication system 1 may be configured to provide support for any suitable SBFD scheme, including, for example, inter-BWP full duplex and / or intra-BWP full duplex.

[0133] For example, referring to Figure 11, which is a simplified time-frequency diagram illustrating an exemplary embodiment of an inter-BWP type of full-duplex configuration, inter-BWP full-duplex involves parallel UL and DL transmissions in different BWPs, where a particular slot in one BWP may be configured as an uplink slot while a corresponding slot (i.e., a slot with the same timing) in another BWP may be configured as a downlink slot (or vice versa). Thus, UL from one UE 3 in one BWP can occur in parallel with DL communication to another UE 3 in another BWP.

[0134] On the other hand, referring to FIG. 12, a simplified time-frequency diagram illustrating an exemplary embodiment of an intra-BWP type of full-duplex configuration, full-duplex within a BWP includes parallel UL and DL transmissions in the same BWP. In the embodiment shown in FIG. 12, UL subbands are effectively inserted into slots / symbols configured as (legacy) DL or flexible slots / symbols of the BWP. Specifically, each time resource of the BWP is configured as a DL, UL, or flexible slot / symbol (e.g., using TDD configuration techniques such as those described with reference to FIGS. 8 and 9). UL subbands (e.g., a set of contiguous UL frequency resources) are then configured within the BWP such that at least a subset of one or more of the DL or flexible slots / symbols effectively forms a slot / symbol consisting of the UL subband and one or two DL subbands. The configuration of one or more UL subbands can be achieved in any suitable manner, for example, by semi-static and / or dynamic configuration. Guard bands (frequency gaps) can be configured between the UL subband and each DL subband, during which no transmissions are performed, thereby helping to avoid interference. The RAN 5 can then schedule UL transmissions in the UL sub-band and DL transmissions in one or more DL sub-bands as needed.

[0135] While FIG. 12 shows UL subbands being inserted into downlink or flexible slots / symbols, it will be appreciated that a similar mechanism can be used to insert DL subbands into UL or flexible slots / symbols to achieve SBFD.

[0136] It will be appreciated that although UL (or DL) sub-bands may be configured within slots / symbols configured as DL (or UL) slots / symbols (e.g., by a TDD configuration), it would be particularly beneficial for the RAN to be able to dynamically schedule DL (or UL) transmissions within the configured UL (or DL) sub-bands (e.g., when no UL (or DL) transmission is needed) to improve radio resource utilization.

[0137] Separation of different antenna elements into UL and DL In the communication system 1, the RAN 5 is configured to transmit to a UE 3 in the downlink via a first set (or group) of antenna elements and receive from another UE 3 in the uplink via a second set (or group) of antenna elements that is spatially separated from the first set of antenna elements in the same one or more SBFD slots (or symbols). This spatial separation between the antenna elements used for the UL and DL can result in lower interference observed during UL reception at the RAN 5.

[0138] 13, which is a simplified diagram of an antenna panel configuration for full duplex communication in communication system 1, spatial separation can be achieved by using an antenna panel for DL ​​communication that is different from the antenna panel used for UL communication. In this embodiment, a radio frequency (RF) isolator is also provided to further reduce interference during UL reception in RAN 5.

[0139] During legacy TDD slots / symbols (e.g., dedicated UL-only slots / symbols or dedicated DL-only slots / symbols), both antenna elements of the first set and the second set of antenna elements can still be used for the same transmit direction (e.g., receive in UL / transmit in downlink).

[0140] As noted above, the RAN 5 (or another similar RAN 5 in the communication system 1) may have a single panel. In the case of a RAN 5 that communicates through a single antenna panel, the RAN 5 may be advantageously configured to separate the antenna elements within the panel. One such arrangement is shown in Figure 19, which is a simplified diagram of another antenna panel configuration for full-duplex communication in the communication system 1.

[0141] TDD configuration exchange (e.g., DU-CU / F1 interface) In the case of a RAN 5 including a DU 5b and a CU 5c, both the DU 5b and the CU 5c may exchange TDD slot configuration information (e.g., via the DU-CU / F1 interface) to ensure that both the DU 5b and the CU 5c are each aware of one or more associated TDD slot configurations applicable to / known by the other unit.

[0142] FIG. 14 is a simplified sequence diagram showing different procedures (S1410, S1420, S1430) for exchanging slot (TDD) configurations that can be employed in the communication system 1.

[0143] 14, in one step S1410, a given DU 5b can provide information to a CU 5c (e.g., as part of a "Desired TDD DL-UL Configuration" information element (IE)) indicating the DU's desired TDD (UL and / or DL) configuration. This information can comprise, for example, the cell's subcarrier spacing, cyclic prefix, and TDD DL-UL slot configuration that the receiving CU 5c should take into account for cross-link interference mitigation and / or dual connectivity (DC) power adjustment when operating its own cell.

[0144] Information identifying the desired TDD configuration may be provided, for example, as part of a procedure for DU5b and CU5c to exchange application-level data necessary for correct interoperation over the DU-CU ("F1") interface (and thus necessary to form a logical (e.g., "F1") connection between the CU5c control plane and DU5b). DU5b may provide information indicating the DU's desired TDD configuration to CU5c, for example, in a setup request message (e.g., F1 Setup Request) to initiate the procedure (seen in S1410a). Although not shown in FIG. 14, CU5c (control plane) may complete the procedure by returning an appropriate setup response (e.g., F1 Setup Response). This setup request may include information to inform CU5c (control plane) about the identity of the DU and the set of cells that DU5b supports. The setup response may include information to inform DU5b about which cells to activate in DU5b.

[0145] Alternatively or additionally, information identifying the desired TDD configuration may be provided by DU 5b to CU 5c as part of a procedure for updating application-level configuration data necessary for DU 5b and CU 5c to correctly interoperate over the F1 interface. DU 5b may, for example, provide information indicating the DU's desired TDD configuration to CU 5c in a configuration update message (e.g., a GNB-DU configuration update), as seen at S1410b. Although not shown in Figure 14, CU 5c may respond by returning an appropriate acknowledgement message (e.g., a GNB-DU configuration update confirm).

[0146] Thus, the receiving CU5c can use the received information to identify the desired TDD configuration for crosslink interference management and / or NR-DC power adjustment, as seen at S1412.

[0147] The receiving CU 5c may consider the received desired information identifying the desired TDD configuration to be valid until it receives an update of the information identifying the desired TDD configuration for one or more of the same cells.

[0148] 14, in another step S1420, a given CU 5c can provide information to a DU 5b (e.g., as part of a "Desired TDD DL-UL Configuration NR" information element) indicating one or more neighboring TDD configurations (e.g., one or more TDD configurations to be used by the neighboring DUs). This information can include, for example, the subcarrier spacing, cyclic prefix, and TDD DL-UL slot configuration of the cell that neighboring RAN nodes should take into account for cross-link interference mitigation and / or DC power adjustment when operating the cell.

[0149] Information identifying one or more neighboring TDD configurations can be provided by CU5c to DU5b, for example, as part of a procedure for updating application-level configuration data necessary for DU5b and CU5c to properly interoperate over the F1 interface. CU5c can provide information indicating one or more neighboring TDD configurations to DU5b in a configuration update message (e.g., a GNB-CU Configuration Update), as seen in S1420a, for example. Although not shown in FIG. 14, DU5b can respond by returning an appropriate acknowledgement message (e.g., a GNB-CU Configuration Update Confirm). For example, the information identifying one or more neighboring TDD configurations can be provided along with appropriate cell identities in a neighbor cell information list (e.g., one or more NR cell global identities (NRCGIs)).

[0150] Thus, the receiving DU5b may use the received information identifying one or more neighboring TDD configurations for crosslink interference management and / or NR-DC power adjustment, as seen in S1422.

[0151] As can be seen in FIG. 14, in another step S1430, a given CU 5c can provide information to a DU 5b indicating one or more TDD configurations to be used by the DU 5b.

[0152] Information indicating one or more TDD configurations to be used can be provided to DU 5b by CU 5c, for example, as part of a procedure for configuring the resource usage of DU 5b (e.g., as part of the "gNB-DU Cell NA Resource Configuration-TD" IE / "gNB-DU Cell Resource Configuration" IE). This information can include, for example, the subcarrier spacing and slot configuration used in the cell.

[0153] CU5c may provide information indicating one or more TDD configurations to be used by DU5b in a resource configuration message (e.g., a GNB-DU resource configuration), as seen in S1430a, for example. Although not shown in Figure 14, DU5b may respond by returning an appropriate acknowledgement message (e.g., a GNB-DU resource configuration acknowledgement). The information indicating one or more TDD configurations to be used by DU5b may be for, for example, a particular cell and / or integrated access and backhaul (IAB) node associated with DU5b.

[0154] The receiving DU5b can therefore use the received information to identify one or more TDD configurations to be used by the DU5b for the associated cell / IAB node, as seen at S1432.

[0155] 14 can be used alone in the communication system 1, but it will be understood that the communication system can be configured with all or a subset of the procedures. For example, the various procedures for exchanging slot (TDD) configurations (S1410, S1420, S1430) can be performed in the sequence shown. For example, the DU 5b can send TDD information indicating its desired TDD configuration to the CU 5c during setup, and the CU 5c can pass the given desired TDD configuration to other connected CUs 5c or DUs 5b (i.e., as a neighboring TDD configuration), and the CU 5c can indicate to the DU 5b to use a particular TDD configuration if it does not conflict with the TDD configuration of another DU.

[0156] The TDD configuration configured by CU 5c for DU 5b, the desired TDD configuration, and / or the TDD configuration of the neighboring DUs can include, for example, the subcarrier spacing, cyclic prefix, and TDD DL-UL slot configuration of the NR cell. The TDD DL-UL slot configuration can include DL / UL / flexible slot / symbol information for that cell.

[0157] Open Fronthaul (O-FH) Management (M) and Control / User / Synchronisation (CUS) planes (DU-RU interface)

[0158] The open FH M-plane is used for managing the (open)RU 5a, including exchanging capability information between the (open)RU 5a and the (open)DU 5b. For example, the capability information may indicate the capability of the (open)RU 5a to perform beamforming and / or antenna configuration for the capability information.

[0159] The open CUS plane is used for the transfer of user plane and control plane messages. In this embodiment, "user plane" messages refer to messages carrying IQ sample data for transfer between the (open) DU 5b and the (open) RU 5a. U-plane messages can include any radio transmission between the RAN 5 and the UE 3 (including both user data and control messages such as RRC, NAS, and PRACH messages). The RU 5a is generally unaware of the type of data transmitted by the DU 5b / received by the RU 5a. The RU 5a simply transparently performs packet transfer between the DU 5b and the UE 3. It will be understood that a single user plane message can include one or more transmissions for multiple UEs. Meanwhile, "control plane" messages in this embodiment specifically refer to messages for real-time control between the DU 5b and the RU 5a (and should not be confused with messages transmitted via the UE's control plane). Control plane messages typically carry scheduling information for one or more O-FH user plane messages. Specifically, a control plane message may include information indicating an association between a user plane message and a control plane message, including, for example, information identifying a symbol identifier, a slot identifier, a frame identifier, the beginning of a physical resource block (PRB), and / or the end of a PRB (and / or the number of consecutive PRBs / length within a PRB). A control plane message may also include information regarding one or more radio resource (time / frequency) assignments, antenna / beam assignments, cyclic prefix (CP) used / CP length, fast Fourier transform (FFT) size, filter identifier / index, etc.

[0160] The timing relationship between control plane messages and user plane messages is defined by the O-RAN specification, e.g., based on the time that a control plane message should be received by the RU 5a before the arrival of the associated user plane message and / or the processing time of the user plane message.

[0161] Figure 15 is a simplified sequence diagram illustrating the control plane and user plane message transfer procedures, for example for transmitting user plane data in the downlink, it will be appreciated that similar procedures apply for transmitting user plane data in the uplink.

[0162] 15, control plane messages for a given slot and one or more given symbols exchanged between the DU 5b and the RU 5a are followed, one at a time, by user plane data for that slot and one or more symbols. The user plane messages are transmitted by the DU 5b in the downlink (and by the RU 5a in the uplink) in the order of the symbols they carry IQ data. The control plane and downlink user plane messages are transmitted in advance by the DU 5b so that they arrive at the RU 5a within a sufficiently early time window to leave the RU 5a time to process them. 15 illustrates an example in which DU 5b transmits one or more downlink control plane messages describing symbols #M, M+1, ..., #N of a given slot S in a timing window defined by a maximum time (e.g., defined by a maximum timing parameter such as "T1a_max_cp_dl") and a minimum time (e.g., defined by a minimum timing parameter such as "T1a_min_cp_dl") before the start of downlink symbol #M (the earliest symbol described by the message). As shown in FIG. 15, the end of the reception time window of the downlink control plane messages describing symbols #M, M+1, ..., #N of slot S (here the earliest symbol described by each message) occurs at a period (e.g., defined by another timing parameter such as "Tcp_adv_dl") before the end of the reception time window of the downlink user plane message carrying the IQ data of symbol #M. The DU 5b transmits (and the RU 5a receives) downlink user plane messages in a specific transmission window (and a specific reception window).

[0163] Similarly, for user plane data in the uplink, DU 5b transmits UL control plane messages describing symbols #M, M+1, ..., N of slot S within a timing window defined by a maximum time (e.g., defined by a maximum timing parameter such as "T1a_max_cp_ul") and a minimum time (e.g., defined by a minimum timing parameter such as "T1a_min_cp_ul") before the start of uplink symbol #M (the earliest symbol described by the message). The end of the receive time window of the uplink control plane messages describing symbols #M, M+1, ..., N (the earliest symbol described by each message) occurs at an earlier period than the start of uplink symbol #M (e.g., defined by another timing parameter such as "T2a_min_cp_ul"). RU 5a transmits (and DU 5b receives) uplink user plane messages in a specific transmit window (and a specific receive window).

[0164] As can be seen in Figure 15, there is also a period between the time an RU receives a control plane message for a symbol and the time RU 5a needs to process the user plane data for that symbol. In particular, in the downlink, there is a period (e.g., defined by the parameter "Tcp_adv_dl") that provides RU 5a with a few microseconds (or the like) to, for example, update beamforming weights before processing the downlink data arriving from DU 5b. Similarly, in the uplink, there is a period (e.g., defined by the parameter "t2a_min_cp_ul") between RU 5a receiving the control plane message governing the processing of uplink data and the RU receiving the uplink signal at its antenna. These time intervals, combined with network delays and other processing latencies, result in the RAN 5 employing a closed hybrid automatic repeat request (HARQ) loop that enables feedback in air interface processing.

[0165] Control plane and user plane messages, in terms of the described O-RAN embodiment, are transported using the enhanced Common Public Radio Interface (eCPRI) message structure. eCPRI is a standard for transmitting radio signals between the CU / DU and the RU. The eCPRI standard is designed to enable the transmission of high-bandwidth, low-latency data streams over Ethernet-based networks.

[0166] O-RAN allows for several different transport headers within the Ethernet payload to further describe how application data should be processed in the control and user planes. In all cases, the transport headers are eight bytes long and provide basic data routing capabilities, including a description of the data flow type, send and receive port identifiers, the ability to support concatenation of multiple application messages within a single packet, and sequence numbering.

[0167] Referring to FIG. 16, which shows an exemplary message structure for control plane and / or user plane messages (e.g., O-FHCUS plane messages) in communication system 1, at 1610 there is seen a definition of an eCPRI transport header.

[0168] The eCPRI transport header seen in 1610 includes an eCPRI protocol version (ecpriVersion) parameter, an eCPRI reservation (ecpriReserved) parameter, an eCPRI concatenation indicator (ecpriConcatenation) parameter, an eCPRI message type (ecpriMessage) parameter, an eCPRI payload size (ecpriPayload) parameter, a real-time control data / IQ data transport message series (ecpriRtcid / ecpriPcid) parameter, and a message identifier (ecpriSeqid) parameter.

[0169] The eCPRI protocol version (ecpriVersion) parameter indicates the eCPRI protocol version. The eCPRI reserved (ecpriReserved) parameter is reserved for future eCPRI use. The eCPRI concatenation indicator (ecpriConcatenation) parameter indicates when eCPRI concatenation is being used (allowing multiple eCPRI messages within a single Ethernet payload). The eCPRI message type (ecpriMessage) parameter indicates the type of service conveyed by the message type. The eCPRI payload size (ecpriPayload) parameter indicates the size in bytes of the payload portion of the corresponding eCPRI message. The real-time control data / IQ data transfer message series (ecpriRtcid / ecpriPcid) parameter is an "extended" antenna carrier (eAxC) identifier (eAxCID) that identifies the specific data flow associated with each control plane (ecpriRtcid) or user plane (ecpriPcid) message; this effectively identifies the antenna carrier, component carrier, and multiple input multiple output (MIMO) stream. The message identifier (ecpriSeqid) parameter provides unique message identification and sequencing at two different levels: The first 8 bits of the ecpriSeqid parameter are the sequence ID and are used to identify the order of messages within the eAxC message stream.

[0170] TDD pattern configuration Referring to FIG. 17, which is a simplified sequence diagram illustrating a procedure for configuring a TDD pattern in a radio / remote unit in communication system 1, an (open) RU 5a can reveal its ability to support TDD pattern configuration by indicating support for the configurable-TDD-pattern-supported feature (S1710).

[0171] Thus, the (open) DU 5b can configure a TDD pattern configuration for the RU 5a (S1712). A single TDD pattern configuration can include a list of records (e.g., a corresponding record for each of several different channels / carriers). Each record can include, for example, details of the frame offset and signal "direction" to be applied when a particular frame offset occurs on the air interface. Supported directions include, for example, uplink and guard period (GP), i.e., neither uplink nor downlink. The RU 5a verifies that the TDD pattern configured as S714 is not violated by control plane and / or user plane messages.

[0172] Antenna panel configuration / beamforming Referring to FIG. 18 , which is a simplified diagram of an antenna panel configuration for an RU 5a of a RAN 5 in communication system 1, the RU 5a includes an antenna having multiple antenna panels 1810 (two in this example, although more antenna panels are possible). Each antenna panel 1810 includes at least one antenna array 1812, which may be a transceiver (TX) and / or receiver antenna array. Each antenna array includes a respective arrangement of multiple array elements 1814 (eight in this example, arranged in two rows of four, although any suitable number and arrangement is possible). Each array element 1814 includes a plurality of physical antenna elements 1816 (also referred to as “radiators”) arranged in cross-pole pairs of antenna elements in this example. In this example, each array element 1814 has eight physical antenna elements 1816 arranged in a single row of four cross-pole pairs, although it will be understood that an array element can have any suitable number of antenna elements, including a single cross-pole pair of antenna elements in any suitable arrangement. In the illustrated embodiment, each cross pole pair 1816 comprises a plus 45° antenna element and a minus 45° antenna element, although it will be appreciated that other arrangements are possible.

[0173] The configuration of a uniformly spaced antenna array in a two-dimensional plane can be represented by the model (M, N, P), where: M is the number of antenna elements with the same polarization in each column; N is the number of columns, P is the number of polarization dimensions.

[0174] Although RU 5a of RAN 5 is described as having multiple antenna panels, it will be understood that RU 5a could have a single panel, as at least some operators currently support a single antenna panel per RAN site. UE 3 could, of course, have an antenna with multiple antenna elements.

[0175] The use of antennas with multiple physical antenna elements allows the RAN 5 and UE 3 to transmit (and receive) using logical antenna ports that are mapped to one or more subsets of the physical antenna elements 1816. Thus, transmissions that share the same antenna port will experience the same propagation channel.

[0176] The use of logical antenna ports in the RU 5a or UE 3 enables multiple input multiple output (MIMO) communications, in which multiple data streams (called "transmission layers") can be transmitted (or received) in parallel using the same time and frequency resources, but via different logical antenna ports. Furthermore, the ability to map a given logical antenna port to a subset containing multiple physical antenna elements allows the RAN 5 (or UE 3) to beamform transmissions made via that logical antenna port (i.e., by applying appropriate amplitude and / or phase adjustments at each physical antenna element).

[0177] Thus, the distributed RAN 5 can beamform through the antenna panel 1810 of the RU 5a by controlling the amplitude and phase of each array element 1814 in the antenna array 1812. Generally, the amplitude and phase of the radiators 1816 in the array elements are not dynamically changed in real time. Each TX / RX antenna array 1812 can actually terminate one or more RU logical antenna ports (identified by RU_port_ID).

[0178] Each RU 5a has several transceiver units (TXRUs), each of which includes an FFT unit, and for beamforming purposes, frequency domain weighting (i.e., for phase and / or amplitude adaptation) can be applied within the TXRU before the FFT stage.

[0179] Each TXRU is mapped to an arranged group of antenna elements (e.g., a column for elevation beamforming) using an appropriate mapping function. There are several different possible TXRU architectures and corresponding TXRU virtualization weighting functions to implement various possible beamforming scenarios.

[0180] A TXRU model can be used to represent an array of TXRUs. Possible TXU models broadly correspond to, for example, antenna array model configurations (M, N, P), and (M TXRU , N, P), and M TXRU is the number of TXRUs per column per polarization dimension, e.g.,

number

number

[0181] The relationship between the signals at the TXRU and the signals at the antenna elements for various architectures / scenarios can be defined by corresponding TXRU virtualization models. Figures 19 and 20 each show, by way of example only, various corresponding TXRU virtualization models that can be used in communications system 1 to represent the connectivity between the TXRU and the antenna elements. Specifically, Figure 19 shows what is known as a subarray partition model, and Figure 20 shows what is known as a full connectivity model.

[0182] The following additional notation can be used in Figures 19 and 20: ·q is the transmitter signal vector at the M co-polarized antenna elements in the antenna element group (eg, a column). · w and W are the wideband TXRU virtualization weighting vector and matrix, respectively. x is M TXRU This is the TXRU signal vector at the TXRU.

[0183] The model in FIG. 19 can be a one-dimensional subarray partition model, defined as follows: ·q is given by the following equation:

number

number

[0184] The model in FIG. 19 can be a two-dimensional subarray partition model defined as follows: ·q is given by the following equation:

number

number

[0185] The model in FIG. 20 can be a one-dimensional fully connected model defined as follows: ·q is given by q=Wx. ·W is given by: · For m=1, ..., M and m'=1, ..., M TXRU :(m, m') element of W:

number

[0186] The model in FIG. 21 can be a two-dimensional fully connected model defined as follows: ·q is given by q=Wx. ·W is given by the following formula:

number

[0187] Different types of beamforming can be used in the communication system 1. For example, time-domain beamforming can be used, in which different beam weights are not applied to different frequency resources of the same symbol for an antenna array. Similarly, frequency-domain beamforming can be used, in which different beam weights are applied to different frequency resources for an antenna array. Such frequency-domain beamforming can be implemented by using different weights for different resource elements (Res) before the FFT processing stage. Furthermore, hybrid beamforming can be used, in which a combination of time-domain and frequency-domain beamforming is used.

[0188] Several different beamforming techniques supported by O-RAN can be used in the communication system 1.

[0189] Possible beamforming techniques include, for example, channel information-based beamforming, in which the DU 5b periodically provides channel information for each UE to the RU 5a. The DU 5b also provides scheduling information to the RU 5a, which the RU 5a uses to calculate appropriate beamforming weights. In this technique, there may not be a beam identifier (e.g., a beam ID value) associated with beamforming; instead, a UE identifier (e.g., a UE ID) is provided in association with each data section / segment to be transmitted.

[0190] Possible beamforming techniques may include, for example, beamforming with predefined beams (which may employ hybrid / frequency domain / time domain beamforming). In this embodiment, RU 5a is responsible for determining the characteristics of the beams and the number of beams. RU 5a provides DU 5b with a (limited) set of information about one or more beams, for example via M-plane signaling. The provided information may include, for example, information identifying a given beam, whether it is a coarse beam or a fine beam, and / or information about the relationship of neighboring beams (which may be associated with a beam identifier (beam ID value)). DU 5b can use the corresponding beam ID value.

[0191] For example, possible beamforming techniques may include attribute-based dynamic beamforming (e.g., based on beam attributes updated in real time). In this embodiment, only time-domain beamforming may be supported. RU 5a provides information to DU 5b about beam patterns (e.g., vertical and azimuth 3 dB beamwidth values) that may be generated by RU 5a, e.g., in association with beam IDs through the M-plane. DU 5b may then generate corresponding beam attributes, map one or more associated weights to the beam ID values, and provide this information to RU 5b.

[0192] Possible beamforming techniques may include, for example, weight-based dynamic beamforming (based on weights updated in real time). In this embodiment, beamforming may employ hybrid / frequency-domain / time-domain beamforming. RU 5a informs DU 5b of the number of vertical and / or horizontal antenna elements and antenna characteristics (per antenna array), e.g., via an M-plane. This typically also involves RU 5a indicating to DU 5b which digital weights should be applied to each antenna array / antenna array element. DU 5b may then generate beamforming weights, map one or more weights to beam ID values, and provide this information to RU 5a. In the case of hybrid beamforming, this may include generating weights for both frequency-domain and time-domain beamforming. Frequency-domain weights may be used for general beamforming or precoding.

[0193] Furthermore, in weight-based dynamic beamforming embodiments, different supported antenna array configurations can be advertised by the RU 5a to the DU 5b for different beamforming implementations.

[0194] Figures 21 and 22 each show, by way of example only, various respective beamforming implementations, one or both of which may be supported in communication system 1. Figure 23 shows a simplified diagram of one embodiment of weight-based dynamic beamforming.

[0195] In a first embodiment seen in Figure 21, RU 5a presents DU 5b with one antenna array containing two frequency-domain (digital) weighting elements. In this example, for each layer, DU 5b provides a beamforming weighting vector of the type: {wf1, wf2, wt1, wt2}. It will be appreciated that multiple layers can be supported by using different frequency-domain weightings, but any time-domain weightings are the same.

[0196] In a second embodiment seen in Figure 22, RU 5a presents two antenna arrays to DU 5b, each containing a single frequency-domain (digital) weighting element. In this example, DU 5b provides beamforming weighting vectors of the following types: For layer 1: {wf1,wt1} For layer 2: {wf2,wt2}

[0197] SBFD Considerations As will be explained in more detail later, the different communication entities of the RAN 5 of the communication system 1 are mutually configured to implement one or more procedures adapted to support a full duplex implementation in the context of TDD (with particular reference to SBFD).

[0198] Advantageously, for example to contribute to providing enhanced support for the duplexing and filtering requirements necessary for SBFD operation, this procedure may include one or more procedures by which the (open) RU5a may indicate whether it supports SBFD operation and / or one or more relevant parameters for indicating its ability to separate downlink communications from uplink communications.

[0199] Furthermore, as will be described in more detail below, this procedure may include one or more procedures by which the (open) DU 5b can provide the RU 5a with an extended TDD pattern configuration (e.g., as part of an extended TDD pattern configuration format) that includes one or more TDD extensions for providing information according to quasi-static SBFD and / or dynamic SBFD. This information may include, for example, information that enables the RU 5a to identify (explicitly or implicitly) the symbols / slots that are configured as (or are dynamically converted to / from) SBFD symbols / slots. The information may include, for example, information that enables the RU 5a to identify (explicitly or implicitly) any frequency regions that are configured as uplink subbands, downlink subbands, and / or guard bands. This information may include, for example, information that enables the RU 5a to identify (explicitly or implicitly) one or more filters to be applied between the uplink subbands and the downlink subbands. This represents a more efficient and flexible way of providing SBFD-related information to RU 5a than, for example, DU 5b providing RU 5a with a TDD pattern configuration that defines only downlink / uplink / and "guard period" (GP) symbols / slots, rather than providing this information in some other way.

[0200] As will be explained in more detail later, this procedure may include one or more procedures in which the (open) DU 5b (and / or (open) CU 5c) and the (another) (open) CU 5c may exchange extended TDD information including one or more TDD extensions for providing SBFD-related information (e.g., as part of an extended TDD configuration). The SBFD-related information may be exchanged, for example, as part of one or more procedures described with reference to Figure 14. Specifically, the SBFD-related information may be exchanged, for example, as part of one or more desired TDD configurations of the DU 5b provided by the DU 5b to the CU 5c, as part of one or more neighboring DU TDD configurations provided by the CU 5c to the DU 5b, and / or as part of one or more TDD configurations to be used in the DU configured by the CU for the DU.

[0201] The SBFD-related information may include one or more SBFD-related parameters that, for example, define frequency resources for one or more uplink (and / or downlink) subbands, define frequency resources for downlink (and / or uplink) subbands (e.g., to be used together with uplink (and / or downlink) subbands for SBFD communication in SBFD slots), define frequency resources for one or more guard bands (e.g., between a downlink (or uplink) subband and one or more uplink (or downlink) subbands), and / or define one or more time positions (slots / symbols) or time opportunities for SBFD slots / symbols for one or more respective uplink (and / or downlink) subbands used for SBFD. This represents a more efficient and flexible way of exchanging SBFD-related information than, for example, exchanging TDD information (between DU5b / CU5c and CU5c) that defines only downlink / uplink / flexible symbols / slots and providing SBFD-related information in some other manner.

[0202] As described in more detail below, this procedure may include one or more procedures for supporting antenna-based separation between the uplink and downlink for SBFD. In one such procedure, for example, the (open) RU5a may indicate various supported beam configurations for SBFD and non-SBFD (uplink-only / downlink-only) symbols / slots. In another such procedure, for example, the (open) RU5a may indicate various beamforming patterns that can be generated for SBFD and non-SBFD (uplink-only / downlink-only) symbols / slots. In another such procedure, for example, the (open) RU5a may indicate which sets of antenna panels, arrays, and / or elements are available (and / or unavailable) for use during SBFD operation for the uplink and / or downlink. In another such procedure, for example, the (open) RU5a may indicate a particular set of one or more antenna array configurations that can be used during SBFD operation for uplink and / or downlink communications. Such a procedure advantageously allows the impact on beamforming of differences in antenna element availability between SBFD and non-SBFD symbols / slots to be properly taken into account (e.g., when generating weights / weight vectors for beamforming).

[0203] RU's ability to support SBFD As mentioned above, to help provide enhanced support for the duplexing and filtering requirements necessary for SBFD operation, one or more procedures may be implemented in the communications system 1 by which an (open) RU 5a may indicate whether the RU 5a supports SBFD operation and / or one or more associated parameters to indicate the RU 5a's ability to separate downlink communications from uplink communications.

[0204] FIG. 24 is a simplified sequence diagram illustrating a possible procedure for indicating the capabilities of an RU 5a to a DU 5b that can be used in the communication system 1.

[0205] As can be seen in Figure 24, the RU 5a may indicate (at S2510) its capability to support SBFD operation. This may be signaled, for example, using M-plane signaling or possibly another suitable signaling mechanism. The DU 5b may then take this capability into account when determining (at S2412) the TDD and / or SBFD configuration to be used by the RU 5a, and configure the RU 5a accordingly (at S2414). This may be signaled, for example, using a control plane message, as part of CUS-plane signaling or possibly another suitable signaling mechanism.

[0206] FIG. 25 is a simplified sequence diagram illustrating another possible procedure for indicating the capabilities of an RU 5a to a DU 5b that can be used in the communication system 1.

[0207] As shown in Figure 25, the RU 5a may provide (at S2510) separation capability information indicating the RU 5a's ability to separate uplink communications from downlink communications (e.g., for purposes of mitigating interference during SBFD communications). The separation capability information may be transmitted, for example, using M-plane signaling or possibly another suitable signaling mechanism. In this embodiment, the provided separation capability information includes individual separation values ​​for each of a plurality of different separation schemes / types. The separation capability information may, for example, include one or more separation values ​​for each of any combination of the following separation schemes / types: Guardband Separation: One or more separation values ​​may be indicated for each of one or more guardband configurations / combinations supported by the RU 5a. Furthermore, each separation value may be provided in association with a value indicating the supported guardband configuration / combination. · Beam pair separation: One or more separation values ​​may be provided indicating the level of separation between different beam pairs supported by the RU 5a (e.g., in conjunction with information identifying the associated beam pair). Antenna array / panel isolation-based isolation: One or more isolations may be provided indicating a level of isolation for each of one or more different antenna configurations (e.g., associated with information indicating the associated antenna configuration). Supported Cancellation Mechanism-Based Isolation: One or more isolations may be provided indicating a level of isolation for each of one or more digital and / or analog cancellation mechanisms. In this example, an isolation value may be provided for each antenna element configuration and / or beam configuration (e.g., in conjunction with information indicating the associated antenna element configuration and / or beam configuration).

[0208] DU5b can then calculate (at S2512) the overall isolation capability of RU5a based on the individual isolation capabilities of different isolation schemes / types. This allows DU5b to identify how to schedule SBFD slots / symbols (e.g., whether better uplink power control is needed, what types of beams can be used simultaneously, etc.), and thus determine (at S2514) an appropriate configuration of SBFD to be used in RU5a that properly takes into account the overall isolation capability. DU5b can then configure RU5a for SBFD accordingly (at S2516). This configuration can be performed using control plane messages, for example, as part of CUS plane signaling, or possibly another appropriate signaling mechanism.

[0209] FIG. 26 is a simplified sequence diagram illustrating another possible procedure for indicating the capabilities of an RU 5a to a DU 5b that can be used in the communication system 1.

[0210] 26, in this example, RU 5a (rather than DU 5b) calculates (at S2610) the overall separation capacity of RU 5a based on the individual separation capacities of the different separation schemes / types. The overall separation capacity can be based on, for example, one or more separation values ​​for each of any combination of separation schemes / types described with reference to FIG. 25.

[0211] The RU 5a may then provide (at S2612) information indicating the overall isolation capability of the RU 5a for separating uplink communications from downlink communications (e.g., for purposes of mitigating interference during SBFD communications). It will be appreciated that the overall isolation value in this example may be for a particular configuration (e.g., a default), and that the RU 5a may also provide information indicating the detailed configuration (e.g., guard band size, selected antenna configuration, etc.) used to determine the overall isolation value, for example, as a particular configuration set.

[0212] DU5b can therefore identify how to schedule SBFD slots / symbols (e.g., whether better uplink power control is needed, what types of beams can be used simultaneously, etc.), and can therefore determine (at S2614) an appropriate configuration of SBFD to be used in RU5a that properly takes into account the overall isolation capabilities. DU5b can therefore configure RU5a for SBFD accordingly (at S2616). This configuration can be performed using control plane messages, for example, as part of CUS plane signaling, or possibly another appropriate signaling mechanism.

[0213] FIG. 27 is a simplified sequence diagram illustrating another possible procedure for indicating the capabilities of an RU 5a to a DU 5b that can be used in the communication system 1.

[0214] 27, in this embodiment, RU 5a calculates (at S2710) for each of a plurality of different possible sets of configuration information a corresponding overall isolation capacity of RU 5a. This may be based, for example, on the individual isolation capacities of the various isolation schemes / types when RU 5a is configured according to the corresponding configuration set. The overall isolation capacity for each case may be based, for example, on one or more isolation values ​​for each of any combination of isolation schemes / types described with reference to FIG. 25.

[0215] RU5a may then provide (at S2712) information indicating the overall isolation capability of each RU5a for each configuration set (e.g., for the purpose of mitigating interference during SBFD communications when that configuration set is being used).

[0216] DU5b can thus identify how to schedule SBFD slots / symbols (e.g., whether better uplink power control is needed, what types of beams can be used simultaneously, etc.), and can therefore determine (at S2714) an appropriate configuration for SBFD to be used in RU5a that appropriately takes into account the overall isolation capability of the corresponding configuration set. DU5b can therefore configure RU5a for SBFD accordingly (at S2716). This configuration can be performed using control plane messages, for example, as part of CUS plane signaling, or possibly another appropriate signaling mechanism.

[0217] It will be appreciated that in a variation of the procedures of Figures 25 to 27, DU5b can send a request to RU5a requesting an isolation value for a particular configuration (e.g., guard band size, beam pair, etc.). In this case, RU5a can calculate the expected isolation based on the requested configuration and indicate this value to DU5b. DU5b can thus identify how to schedule SBFD slots / symbols (e.g., whether better uplink power control is needed, what types of beams can be used simultaneously, etc.), and thus determine the appropriate configuration of SBFD to be used by RU5a for the particular configuration to which the request relates.

[0218] Although the procedures in Figures 25 through 27 are described separately, it will be understood that aspects of each procedure can be used in combination. For example, in a manner similar to the procedure described with reference to Figure 26 (or Figure 27), a combined "overall" isolation value can be provided for some isolation features (e.g., self-interference potential, antenna panel separation), and one or more separate "single" isolation values ​​can be provided for other isolation features (e.g., guard bands) (e.g., as described with reference to Figure 25).

[0219] TDD information exchange between DU and RU As described above, one or more procedures may be implemented in a communication system 1 in which a DU 5b may provide an extended TDD pattern configuration to an RU 5a that includes one or more TDD extensions (e.g., as part of an extended TDD pattern configuration format) for providing information according to quasi-static SBFD and / or dynamic SBFD.

[0220] FIG. 28 is a simplified sequence diagram showing some possible procedures for TDD information exchange between a DU 5a and an RU 5b that can be used in the communication system 1.

[0221] The procedures in Figure 28 represent various ways in which TDD information can be exchanged between the DU 5b and the RU 5a to (semi-statically) configure the SBFD symbols / slots for the RU 5a. It will be understood that one or more of these exemplary procedures can be implemented in a communication system (e.g., different procedures can be implemented for use in different situations).

[0222] As seen in FIG. 28, once DU5b determines (at S2810) the TDD configuration of RU5a, including SBFD symbols / slots, DU5b provides (e.g., as part of CUS plane signaling) the TDD information to configure RU5a for SBFD in those symbols or slots (as generally shown in S2812a, S2812b, and S2812c).

[0223] In one embodiment, the TDD configuration information effectively defines a new TDD configuration for RU5a, including symbols / slots that are explicitly marked (e.g., using one or more dedicated IEs) to be SBFD symbols / slots (as seen in S2812a).

[0224] In another embodiment, TDD configuration information is transmitted to RU 5a, which effectively modifies the existing TDD configuration of RU 5a by identifying existing (e.g., UL-only or DL-only) unidirectional symbols / slots that should be converted to full-duplex (SBFD) symbols / slots (as seen in S2812b). Thus, in effect, DU 5b provides an indication of which slots / symbols should "dominate" the existing TDD configuration and become SBFD symbols / slots. For example, DU 5b can indicate which symbols / slots of the existing TDD configuration should be converted to SBFD symbol / slot types.

[0225] In another embodiment (as in S2812c), TDD configuration information is transmitted to the RU 5a that configures a different respective TDD pattern for each of a number of different specific frequency domains / ranges for the RU 5a, thereby enabling some symbols / slots to be configured for uplink communications in one or more frequency domains and downlink communications in one or more other frequency domains, effectively enabling SBFD operation in those slots.

[0226] FIG. 29 is another simplified sequence diagram showing a possible procedure for TDD information exchange between a DU 5a and an RU 5b that can be used in the communication system 1.

[0227] The procedure in Figure 29 illustrates how TDD information can be exchanged between DU 5b and RU 5a to (dynamically) configure the SBFD symbols / slots for RU 5a.

[0228] 29, once the DU 5b determines (at S2910) the TDD configuration of the RU 5a, which includes SBFD symbols / slots, the DU 5b provides (at S2912) TDD information (e.g., as part of CUS plane signaling) for dynamically converting from one or more uplink-only and / or downlink-only symbols / slots to one or more SBFD symbols / slots, or vice versa. In the illustrated embodiment, information is provided to the RU 5a indicating that previously configured symbols / slots (e.g., of UL / DL / SBFD type) need to be dynamically updated (e.g., between UL-only / DL-only symbol / slot type and SBFD symbol / slot type).

[0229] It will be appreciated that in this embodiment, the timing of the transmission of the information indicating that previously configured symbols / slots need to be dynamically updated can be configured to specifically ensure that RU 5a receives a certain (minimum) margin time before receiving a control plane message carrying control information for the transmission of IQ data. Nevertheless, it will be appreciated that in a variation of this, the information indicating that previously configured symbols / slots need to be dynamically updated can be transmitted in the same control plane message (i.e., user plane message) that schedules the transmission of IQ data.

[0230] FIG. 30 is another simplified sequence diagram showing a possible procedure for TDD information exchange between a DU 5a and an RU 5b that can be used in the communication system 1.

[0231] 30, in this embodiment, the DU 5b determines (at S3010) the frequency domains / ranges of the uplink subbands, downlink subbands, and / or guard bands used to implement SBFD in the RU 5a, and then provides (at S3012) TDD information (e.g., as part of CUS plane signaling) including information for indicating to the RU 5a the frequency domains / ranges of the uplink subbands, downlink subbands, and / or guard bands used to implement SBFD.

[0232] It will be appreciated that in the example of Figure 30, RU5a may be configured to determine the filter to be applied between the uplink subband and the downlink subband (e.g., based on the guard band configured by DU5b). Nevertheless, it will also be appreciated that in this variant, DU5b may indicate to RU5a the filter to be applied between SBFD symbols / slots.

[0233] TDD information exchange between DU and CU As described above, one or more procedures may be implemented in a communication system 1 in which a DU5b (and / or CU5c) and a (different) CU5c may exchange extended TDD information, including one or more TDD extensions (e.g., as part of an extended TDD configuration), for providing SBFD-related information.

[0234] The SBFD-related information may be exchanged, for example, as part of one or more procedures described with reference to Figure 14. Specifically, the SBFD-related information may be exchanged, for example, as part of one or more desired TDD configurations of the DU 5b provided by the DU 5b to the CU 5c, as part of one or more neighboring DU TDD configurations provided by the CU 5c to the DU 5b, and / or as part of one or more TDD configurations to be used at the DU configured for the DU by the CU.

[0235] The SBFD-related information may include, for example, one or more SBFD-specific parameters. The SBFD-specific parameters may, for example, define frequency resources for one or more uplink (and / or downlink) subbands. For example, the SBFD-specific parameters may define frequency resources for downlink (and / or uplink) subbands (e.g., to be used together with uplink (and / or downlink) subbands for SBFD communication in SBFD slots). For example, the SBFD-specific parameters may define frequency resources of one or more guard bands (e.g., between a downlink (or uplink) subband and one or more uplink (or downlink) subbands). For example, the SBFD-specific parameters may define one or more time positions (slots / symbols) or time opportunities of SBFD slots / symbols of one or more respective uplink (and / or downlink) subbands used for SBFD.

[0236] Now, purely by way of example, we will describe in more detail some procedures in which a transmitting node (CU / DU) has an SBFD configuration to send to a receiving node (CU / DU) that may or may not support SBFD.

[0237] FIG. 31 is a simplified sequence diagram showing a possible procedure for TDD information exchange between a transmitting node (CU / DU) and a receiving node (CU / DU) that can be used in the communication system 1.

[0238] In the procedure of Figure 31, if a transmitting node (CU / DU) has an SBFD configuration to send to a receiving node (DU / CU) (at S3110), the transmitting node (CU / DU) determines (at S3112) whether the receiving node (DU / CU) supports "SBFD configuration reception." If the receiving node does not support "SBFD configuration reception" and TDD configuration information is sent to the receiving node (at S3114a), the SBFD configuration is not included in the TDD configuration information by the transmitting node (i.e., only legacy TDD configuration is included). If the receiving node supports "SBFD configuration reception" and TDD configuration information is sent to the receiving node (at S3114b), the SBFD configuration information is included in the TDD configuration information by the transmitting node.

[0239] FIG. 32 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a transmitting node (CU / DU) and a receiving node (CU / DU) that can be used in the communication system 1.

[0240] In the procedure of Figure 32, if a transmitting node (CU / DU) has an SBFD configuration to send to a receiving node (DU / CU) (at S3210), the transmitting node (CU / DU) determines (at S3212) whether the receiving node (DU / CU) supports "SBFD configuration reception." If the receiving node does not support "SBFD configuration reception" and TDD configuration information is sent to the receiving node (at S3214a), the SBFD parameters are removed from the TDD configuration (at S3213). Thus, only legacy TDD parameters are included in the TDD configuration information by the transmitting node (i.e., by removing the SBFD parameters, the legacy TDD configuration is sent). If the receiving node supports "SBFD configuration reception" and TDD configuration information is sent to the receiving node (at S3214b), the SBFD parameters are included in the TDD configuration information by the transmitting node.

[0241] It will be appreciated that in either of the procedures of Figures 31 and 32, if a receiving node (CU / DU) does not support "SBFD configuration reception" (e.g., because the receiving node is unable to decode the SBFD configuration), the receiving node may indicate this to the transmitting node by any suitable mechanism. For example, support (or lack of support) may be indicated implicitly or explicitly by the receiving unit to the transmitting unit, such as with an indication of supported versions / features / capabilities. Alternatively or additionally, lack of support may be indicated implicitly by providing an error response to a request carrying SBFD configuration information. The error response may include a Cause value indicating, for example, "unknown configuration" or "syntax error" referring to the SBFD parameters.

[0242] FIG. 33 is a simplified sequence diagram showing a possible procedure for TDD information exchange between a transmitting node (CU / DU) and a CU that can be used in the communication system 1.

[0243] In the procedure of Figure 33, if the transmitting node (CU / DU) has an SBFD configuration to send to CU5c-1 ​​(at S3310), the transmitting node (CU / DU) determines (at S3312) whether CU5c-1 ​​supports "SBFD operation." If the receiving node does not support "SBFD operation" and TDD configuration information is sent to the receiving node (at S3314a), the SBFD configuration is not included in the TDD configuration information by the transmitting node (i.e., only legacy TDD configuration is included). If the receiving node supports "SBFD operation" and TDD configuration information is sent to the receiving node (at S3314b), the SBFD configuration information is included in the TDD configuration information by the transmitting node.

[0244] It will be appreciated that, when supporting the procedure of Figure 33, a CU can indicate support (or non-support) of "SBFD operation" by any suitable mechanism. For example, support can be implicitly or explicitly indicated by the CU to the transmitting unit, such as by indicating supported versions / features / capabilities. Alternatively or additionally, non-support can be implicitly indicated by providing an error response to a request carrying SBFD configuration information. The error response can include, for example, a Cause value indicating "not supporting SBFD operation" or "one or more of the DUs do not support SBFD," pointing to SBFD parameters.

[0245] FIG. 34 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a transmitting node (CU / DU) and a CU that can be used in the communication system 1.

[0246] In the procedure of Figure 34, when a transmitting node (CU / DU) has an SBFD configuration to send to a CU5c-1 ​​(at S3410) and TDD configuration information is sent to a receiving node (at S3412), at least one additional legacy TDD configuration is included by the transmitting node along with the SBFD configuration. If the CU5c-1 ​​does not support "SBFD operation" at S3414, the CU simply ignores the SBFD configuration (at S3416a). Otherwise, if the CU5c-1 ​​supports "SBFD operation," the CU5c-1 ​​takes the SBFD configuration into account (at S3416b).

[0247] FIG. 35 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a transmitting node (CU / DU) and a CU that can be used in the communication system 1.

[0248] In the procedure of Figure 35, when a transmitting node (CU / DU) has an SBFD configuration to transmit to a CU5c-1 ​​(at S3510) and TDD configuration information is transmitted to the CU5c-1 ​​(at S3512), one or more SBFD-specific parameters (e.g., uplink (or downlink) subband time and frequency resources, downlink (or uplink) frequency resources, and / or guard band frequency resources) are provided by the transmitting node along with the legacy TDD configuration. If the CU5c-1 ​​does not support "SBFD operation" at S3514, the CU5c-1 ​​simply ignores the SBFD parameters (at S3516a). Otherwise, if the CU5c-1 ​​supports "SBFD operation," the CU takes the SBFD parameters into account (at S3516b).

[0249] 33 to 35, it will be understood that if one or more DUs 5b connected to the CU 5c-1 do not support SBFD, the CU 5c-1 may not support SBFD operation. Alternatively or additionally, if the CU 5c-1 does not intend to use SBFD operation, the CU 5c-1 may not accept the desired SBFD configuration from the connected DU 5b.

[0250] FIG. 36 is a simplified sequence diagram showing a possible procedure for TDD information exchange between a CU 5c and a DU 5b that can be used in the communication system 1.

[0251] In the procedure of Figure 36, when the CU5c has an SBFD configuration (for a neighboring DU) to send to the connected DU 5b (at S3610), the CU5c determines (at S3612) whether the connected DU 5b supports "SBFD operation". If the connected DU 5b does not support "SBFD operation" and the TDD configuration information is sent to the receiving node, the SBFD configuration of the neighboring DU is not included in the TDD configuration information by the CU5c (at S3614a) (i.e., only legacy TDD configuration is included). If the receiving node supports "SBFD operation" and the TDD configuration information is sent to the receiving node, the CU5c includes any SBFD configuration of the neighboring DU in the TDD configuration information (at S3614b).

[0252] FIG. 37 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a CU 5c and a DU 5b that can be used in the communication system 1.

[0253] In the procedure of FIG. 37, when the CU5c has an SBFD configuration (for a neighboring DU) to send to the connected DU 5b (at S3610), the CU5c determines (at S3712) whether the connected DU 5b supports "SBFD operation." If the connected DU 5b does not support "SBFD operation" and TDD configuration information is sent to the receiving node (at S3714a), any SBFD parameters of any neighboring SBFD configurations are removed from the TDD configuration (at S3713). Thus, only legacy TDD parameters are included in the TDD configuration information by the CU5c (i.e., one or more legacy TDD configurations for one or more neighboring DUs are sent by removing the SBFD parameters). If the receiving node supports "SBFD operation" and TDD configuration information is sent to the receiving node (at S3714b), any SBFD parameters of any neighboring SBFD configurations are included in the TDD configuration information by the CU5c.

[0254] FIG. 38 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a CU 5c and a DU 5b that can be used in the communication system 1.

[0255] In the procedure of Figure 38, when CU5c has SBFD configurations (for neighboring DUs) to send to connected DU5b (at S3810) and neighboring TDD configuration information is sent to the receiving node (at S3812), one or more SBFD-specific parameters for one or more neighboring DUs (e.g., uplink (or downlink) subband time and frequency resources, downlink (or uplink) frequency resources, and / or guard band frequency resources) are provided by CU5c along with the legacy TDD configuration. If DU5b does not support "SBFD operation" at S3814, DU5b simply ignores the SBFD parameters (at S3816a). Otherwise, if DU5b supports "SBFD operation", DU5b takes the SBFD parameters into account (at S3816b).

[0256] FIG. 39 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a CU 5c and a DU 5b that can be used in the communication system 1.

[0257] In the procedure of Figure 39, when a CU5c has an SBFD configuration to send to a DU5b to configure its DU5b (at S3910), the CU5c determines (at S3912) whether the DU5b supports "SBFD operation". If the DU5b does not support "SBFD operation" and TDD configuration information is sent to the DU5b (at S3914a), the SBFD configuration is not included in the TDD configuration information by the CU5c (i.e., only legacy TDD configuration is included). If the DU5b supports "SBFD operation" and TDD configuration information is sent to the receiving node (at S3914b), the CU5c includes the SBFD configuration information in the TDD configuration information.

[0258] FIG. 40 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a CU 5c and a DU 5b that can be used in the communication system 1.

[0259] In the procedure of Figure 40, when CU5c has an SBFD configuration to send to DU5b to configure its DU5b (at S4010), and TDD configuration information is sent to the receiving node (at S4012), at least one additional legacy TDD configuration is included along with the SBFD configuration by CU5c. If DU5b does not support "SBFD operation" at S4014, DU5b ignores the SBFD configuration and uses the legacy TDD configuration (at S4016a). Otherwise, if DU5b supports "SBFD operation," DU5b uses the SBFD configuration (at S4016b). DU5b indicates the legacy TDD / SBFD configuration applied by DU5 to CU5c at S4018.

[0260] FIG. 41 is a simplified sequence diagram showing another possible procedure for TDD information exchange between a CU 5c and a DU 5b that can be used in the communication system 1.

[0261] In the procedure of Figure 41, when CU5c has an SBFD configuration to send to DU5b to configure its DU5b (at S4110), and TDD configuration information is sent to the receiving node (at S4112), one or more SBFD-specific parameters (e.g., uplink (or downlink) subband time and frequency resources, downlink (or uplink) frequency resources, and / or guard band frequency resources) are provided by the transmitting node along with the legacy TDD configuration. If DU5b does not support "SBFD operation" at S4114, DU5b ignores the SBFD parameters and uses the legacy TDD configuration (at S4116a). Otherwise, if DU5b supports "SBFD operation," DU5b uses the SBFD configuration based on the SBFD parameters (at S4116b). DU5b indicates the legacy TDD / SBFD configuration applied by DU5 to CU5c at S4118.

[0262] It will be understood that if SBFD-specific extensions are not supported by DU5b in any of the procedures of Figures 36 to 41, DU5b may not support SBFD operations. Alternatively or additionally, if DU5b does not intend to use SBFD operations, DU5b may not affect the SBFD configuration.

[0263] It will also be appreciated that in support of any of the procedures of Figure 36, Figure 37, or Figure 39, DU5b can indicate its support (or lack of support) of "SBFD operation" by any suitable mechanism. For example, support can be implicitly or explicitly indicated by DU5b to the sending unit, such as by indicating supported versions / features / capabilities. Alternatively or additionally, lack of support can be implicitly indicated by providing an error response to a request carrying SBFD configuration information. The error response can include a Cause value indicating, for example, "not supporting SBFD operation."

[0264] Antenna base isolation As mentioned above, one or more procedures may be implemented in the communication system 1 to support antenna-based separation between the uplink and downlink for SBFD.

[0265] FIG. 42 is a simplified sequence diagram illustrating some possible procedures for supporting antenna-based separation between uplink and downlink that can be used in communication system 1.

[0266] The procedure shown in FIG. 42 includes a procedure for supporting different antenna configurations in terms of predefined beamforming (as seen in S4210).

[0267] As can be seen in Figure 42, in the predefined beamforming-based procedure S4210, the RU 5a provides (at S4210a) information indicating different supported beam configurations for SBFD and UL-only / DL-only symbols / slots (e.g., in relation to associated beam ID values). It will be understood that the indicated different supported beam configurations may specify multiple beam configurations for the SBFD symbol / slot (e.g., for different antenna configurations that can be used for the SBFD symbol / slot). The DU 5b can then use (at S4210b) the appropriate beam ID value depending on whether the particular symbol / slot is of SBFD type or DL-only / UL-only type.

[0268] The procedures shown in Figure 42 include procedures for supporting different antenna configurations in terms of attribute-based beamforming (as seen in S4212).

[0269] As can be seen in Figure 42, in the attribute-based beamforming-based procedure S4212, the RU 5a provides (at S4212a) information indicating different beamforming patterns that can be generated for SBFD symbols / slots (e.g., associated with an associated beam ID value) and for UL-only / DL-only symbols / slots. It will be appreciated that indicating different beamforming patterns can specify multiple beam patterns for SBFD that can be used for the SBFD symbols / slots (e.g., for different antenna configurations that can be used for the SBFD symbols / slots). The DU 5b can then use (at S4212b) the appropriate beam ID value depending on whether a particular symbol / slot is of SBFD type or DL-only / UL-only type.

[0270] The procedure shown in FIG. 42 includes procedures for supporting different antenna configurations in terms of weighting-based beamforming and / or channel information-based beamforming (as seen in S4214).

[0271] As can be seen in Figure 42, in the weighting-based beamforming and / or channel information-based beamforming-based procedure S4214, the RU 5a provides (at S4214a-1) information indicating (e.g., as part of the RU capability report) which antenna panels / antenna arrays / sets of antenna elements can be used (and / or cannot be used) for SBFD operation for the uplink and downlink. Alternatively or additionally, the RU 5a provides (at S4214a-2) information indicating (e.g., as part of the RU capability report) different sets of antenna array configurations for SBFD operation for the uplink and downlink. The DU 5b can then take the reported information into account and generate (at S4214b) an appropriate weighting vector depending on whether a particular symbol / slot is of SBFD type or DL-only / UL-only type.

[0272] User Equipment FIG. 43 is a schematic block diagram showing the main components of the UE 3 seen in FIG.

[0273] As shown, the UE 3 includes transceiver circuitry 4331 operable to transmit and receive signals to and from the RAN 5 via one or more antennas 4333. The UE 3 includes a controller 4337 that controls the operation of the UE 3. The controller 4337 is associated with memory 4339 and coupled to the transceiver circuitry 4331. Although not necessary for its operation, the UE 3 may, of course, include all the usual functionality associated with a conventional UE 3 (e.g., a user interface 4335, such as a touchscreen / keypad / microphone / speaker, for enabling direct user control and interaction), which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. Software may be pre-installed in the memory 4339 and / or may be downloaded, for example, via a telecommunications network or from a removable data storage device (RMD).

[0274] The controller 4337, in this example, is configured to control the overall operation of the UE 3 via program or software instructions stored in memory 4339. As shown, these software instructions include, among other things, an operating system 4341, a communications control module 4343, and a UE management module 4345.

[0275] The communications control module 4343 is operable to control communications between the UE 3 and its one or more serving RANs 5 (and other communications devices connected to the RAN 5, e.g., further UEs and / or core network nodes). The communications control module 4343 is configured to generally handle uplink communications sent by the UE towards the network, and to handle reception of downlink communications from the network.

[0276] The UE management module 4345 is responsible for managing the overall operation of the UE and the overall performance of tasks required for the UE. Such tasks include, among other things, generating and transmitting appropriate messages using appropriate signaling application protocols such as (but not limited to) RRC signaling, MAC signaling, and NAS signaling. For example, the UE management module 4345 is responsible for determining where to monitor downlink control information (e.g., the CSS / USS to monitor, the CORESET, and the location of associated PDCCH candidates), determining the resources to be used by the UE 3 for transmission / reception of UL / DL communications (including interleaved resources and resources subject to frequency hopping), managing frequency hopping at the UE side, determining how slots / symbols are configured (e.g., for UL, DL, or SBFD communications), determining which one or more bandwidth portions are configured for the UE 3, determining how uplink transmissions should be coded, and appropriately applying any SBFD-specific communication configurations.

[0277] RAN node (RU) FIG. 44 is a schematic block diagram illustrating the main components of an RU 5a of a RAN 5 of the communication system 1 shown in FIG. 5. As shown, the RU 5a includes a transceiver circuit 4451 for transmitting and receiving signals to and from a communication device (such as a UE 3) via one or more antennas 4453 (e.g., an antenna array / large-scale antenna), and transmits and receives signals to and from a DU 5b of the RAN 5 via a DU interface 4454 (e.g., including a DU-RU interface). The RU 5a includes a controller 4457 that controls the operation of the RU 5a. The controller 4457 is associated with a memory 4459. Software can be pre-installed in the memory 4459 and / or downloaded, for example, via the communication system 1 or from a removable data storage device (RMD). The controller 4457, in this example, is configured to control the overall operation of the RU 5a via program or software instructions stored in the memory 4459.

[0278] As shown, these software instructions include, among other things, an operating system 4461, a communications control module 4463, a DU-RU module 4465, and an RU management module 4472.

[0279] The communication control module 4463 is operable to control communications between the RU 5a and the UE 3 and between the RU 5a and the DU 5b. The communication control module 4463 is configured to generally control the reception of signals corresponding to uplink communications from the UE 3 at the physical layer level, and to handle the transmission of downlink communications to the UE 3 at the physical layer level.

[0280] The DU-RU module 4468 is responsible for the appropriate processing of signals transmitted to and received from the DU 5b via one or more DU interfaces 4454 (e.g., DU-RU).

[0281] The RU management module 4472 is responsible for managing the overall operation of the RU 5a and the overall performance of tasks required of the RU 5a, such as operations related to beamforming in the RU 5a and operations related to the configuration of the RU 5a in accordance with any TDD / SBFD-related configuration indicated by the DU 5b.

[0282] The RU management module 4472 is also responsible for, for example, any O-FHM plane capability information exchange with the DU 5b, as well as the transmission and reception of user plane and control plane messages via the O-FHCUS plane. The RU management module 4472 is also responsible for managing the generation and transmission of any signaling to the DU 5b to indicate its support for SBFD operation and / or its separation capability. The RU management module 4472 is also responsible for receiving and processing SBFD-related signaling from the DU 5b, such as any information indicating the configuration of the SBFD symbols / slots of the (open) RU 5a, any information indicating one or more symbols / slots to be changed from one or more SBFD symbols / slots to one or more UL / DL-only symbols / slots and from one or more UL / DL-only symbols / slots to one or more SBFD symbols / slots, and / or any information indicating UL subbands, DL subbands, and / or guard bands.

[0283] The RU management module 4472 also handles the transmission and reception of beamforming-related signaling to and from the DU 5b. The signaling transmitted to the DU 5b may include any signaling to indicate information related to beamforming, such as any information regarding beams that the RU 5a can use (e.g., coarse beam or fine beam, relationship between adjacent beams, beam patterns that can be generated by the RU 5a, etc.), any information indicating one or more configurations of the antenna arrays, such as the number of vertical and horizontal antenna elements and antenna characteristics of each antenna array (which may be different for SBFD operation compared to UL and / or DL ​​operation), and / or any information indicating which sets of antenna panels / array elements can / cannot be used for UL / DL SBFD operation. The signaling received from DU5b may include, for example, any beamforming-related channel information and / or scheduling information used to calculate beamforming weights, and / or any signaling from DU5b to indicate beamforming information, such as beamforming weights (e.g., for each layer), beamforming attributes, and / or associated beam identifiers.

[0284] RAN Node (DU) Figure 45 is a schematic block diagram illustrating the main components of a DU 5b of a RAN 5 for the communications system 1 seen in Figure 5. As shown, the DU 5b has transceiver circuitry 4551 for transmitting and receiving signals to and from communications devices (such as UE 3) via an RU 5a and associated DU-RU interface 4553, for transmitting and receiving signals to and from a CU 5c of a RAN node via a CU interface 4554 (e.g., comprising an F1 interface that may be divided into F1-U and F1-C interfaces for user plane and control plane signaling, respectively), and for transmitting and receiving signals to and from a RIC 13 (and in particular quasi-RT RIC 13-2) (e.g., including an E2 interface).

[0285] The DU 5b has a controller 4557 that controls the operation of the DU 5b. The controller 4557 is associated with a memory 4559. Software can be pre-installed in the memory 4559 and / or can be downloaded, for example, via the communication system 1 or from a removable data storage device (RMD). The controller 4557, in this embodiment, is configured to control the overall operation of the DU 5b by program instructions or software instructions stored in the memory 4559.

[0286] As shown, these software instructions include, among other things, an operating system 4561, a communications control module 4563, an F1 module 4565, an E2 module 4567, and a DU-RU module 4568. The communication control module 4563 is operable to control communications between the DU 5b and one or more RUs 5a (and thus between the DU 5b and the UE 3), between the DU 5b and the CU 5c, and between the DU 5b and the RIC 13 (and in particular the quasi-RT RIC 13-2). The communication control module 4563 is configured to generally control the reception of signals corresponding to uplink communications from the UE 3, and to handle the transmission of downlink communications destined for the UE 3.

[0287] The F1 module 4565 is responsible for appropriate processing of signals sent to and received from the CU5c via one or more (e.g., F1) CU interfaces 4554. These signals may be separated into user plane signals sent to and received from the CU-UP portion of the CU5c via the F1-U interface, and control plane signals sent to and received from the CU-CP portion of the CU5c via the F1-C interface.

[0288] The E2 module 4567 is responsible for the proper processing of signals sent to and received from the RIC 13 (and in particular the quasi-RT RIC 13-2) via one or more RIC interfaces 4552 (eg, E2).

[0289] The DU-RU module 4568 is responsible for appropriate processing of signals sent to and received from the RU 5a via one or more RU interfaces 4553 (e.g., DU-RU).

[0290] The DU management module 4572 is responsible for managing the overall operation of the DU 5b and the overall performance of the tasks required by the DU 5b, including, among other things, the interpretation of received MAC signaling and the generation of MAC signaling for transmission, and the generation and transmission of appropriate messages using the appropriate signaling application protocol depending on the functional division between the RU 5a, DU 5b, and CU 5c.

[0291] The DU management module 4572 is responsible for, for example, handling any O-FHM plane capability information exchange with the RU 5a, as well as the transmission and reception of user plane and control plane messages via the O-FHCUS plane. The DU management module 4572 is also responsible for managing the reception and processing of signaling to the RU 5a, for example, to indicate its support for SBFD operation and / or its separation capabilities. The DU management module 4572 is also responsible for generating and transmitting signaling related to SBFD to the RU 5a, such as information indicating the configuration of the SBFD symbols / slots of the (open) RU 5a, information indicating one or more symbols / slots that change between one or more SBFD symbols / slots and one or more UL / DL-only symbols / slots, and / or information indicating UL sub-bands, DL sub-bands, and / or guard bands.

[0292] The DU management module 4572 also processes the transmission and reception of beamforming-related signaling to and from the RU 5a. For example, the signaling received from the RU 5a may include any signaling to indicate beamforming-related information, such as any information regarding beams that the RU 5a can use (e.g., coarse beam or fine beam, relationships between adjacent beams, beam patterns that can be generated by the RU 5a, etc.), any information indicating one or more configurations of the antenna arrays, such as the number of vertical and horizontal antenna elements and antenna characteristics of each antenna array (which may be different for SBFD operation compared to UL and / or DL ​​operation), and / or any information indicating which sets of antenna panels / array elements can / cannot be used for UL / DL SBFD operation. The signaling transmitted to the RU 5a may include, for example, beamforming-related channel information and / or scheduling information used to calculate beamforming weights, and / or any signaling from the DU 5b to indicate beamforming information, such as beamforming weights, beamforming attributes, and / or associated beam identifiers (e.g., for each layer).

[0293] The DU management module 4572 also handles sending and receiving TDD configuration-related signaling to and from the CU 5c. This signaling may include, for example, any signaling for exchanging TDD information between the DU 5b and the CU 5c, including any information indicating any SBFD-specific configuration and / or any SBFD-specific parameters. This signaling may include, for example, any information indicating (explicitly or implicitly) support for (or non-support of) SBFD operation.

[0294] RAN node (CU) Figure 46 is a schematic block diagram illustrating the main components of a CU 5c of the RAN 5 for the communication system 1 shown in Figure 5. As shown, the CU 5c has transceiver circuitry 4651 for transmitting and receiving signals to and from the DU 5b via one or more DU interfaces 4654 (e.g., comprising an F1 interface that can be divided into F1-U and F1-C interfaces for user plane and control plane signaling, respectively), for transmitting and receiving signals to and from core network 7 functions via one or more core network interfaces 4655 (e.g., including N2 and N3 interfaces, etc.), and for transmitting and receiving signals to and from the RIC 13 (and, in particular, the quasi-RT RIC 13-2) via a RIC interface 4652 (e.g., including an E2 interface).

[0295] CU5c has a controller 4657 that controls the operation of CU5c. The controller 4657 is associated with a memory 4659. Software can be pre-installed in the memory 4659 and / or can be downloaded, for example, via the communication system 1 or from a removable data storage device (RMD). The controller 4657, in this embodiment, is configured to control the overall operation of CU5b by means of program or software instructions stored in the memory 4659.

[0296] As shown, these software instructions include, among others, an operating system 4661, a communications control module 4663, an F1 module 4665, an E1 module 4666, an E2 module 4667, an N2 module 4668, an N3 module 4669, a CU-UP management module 4671, and a CU-CP management module 4672.

[0297] The communications control module 4663 is operable to control communications between the CU5c and one or more DUs 5b (and thus between the CU5c and the UE3), between the CU5c and the core network 7, and between the CU5c and the RIC13 (and in particular the quasi-RT RIC13-2). The communications control module 4663 is configured to generally control the reception of signals corresponding to uplink communications from the UE3, and to handle the transmission of downlink communications destined for the UE3.

[0298] The F1 module 4665 is responsible for appropriate processing of signals transmitted to and received from the DU 5b via one or more DU (e.g., F1) interfaces 4654. These signals can be separated into user plane signals received at or transmitted by the CU-UP unit of the CU 5c via the F1-U interface, and control plane signals received at or transmitted by the CU-CP unit of the CU 5c via the F1-C interface.

[0299] The E1 module 4666 is responsible for the appropriate processing of signals transmitted between the CU-UP part of the CU5c and the CU-CP part of the CU5c via a corresponding internal CU interface (for example E1).

[0300] The E2 module 4667 is responsible for the proper processing of signals sent to and received from the RIC 13 (and in particular the quasi-RT RIC 13-2) via one or more RIC interfaces (eg, E2).

[0301] The N2 module 4668 is responsible for the appropriate processing of signals sent to and received from the AMF 10-1 via one or more corresponding core network interfaces 4655 (e.g., N2).

[0302] The N3 module 4669 is responsible for the appropriate processing of signals sent to and received from one or more core network user plane functions 11 via one or more corresponding core network interfaces 4655 (e.g. N3).

[0303] The CU-UP management module 4671 is responsible for managing the overall operation of the CU-UP part of the CU 5c and the overall performance of tasks required for the CU-UP.

[0304] The CU-CP management module 4672 is responsible for managing the overall operation of the CU-CP portion of the CU 5c and the overall performance of the tasks required for the CU-CP, including, among other things, the interpretation of received RRC signaling and the generation and transmission of appropriate messages using the appropriate signaling application protocol depending on the functional division between the RU 5a, DU 5b, and CU 5c, such as generating RRC signaling for transmission.

[0305] The CU-CP management module 4672 also handles the sending and receiving of signaling related to TDD configuration with the DU 5b. This signaling may include, for example, any signaling for exchanging TDD information between the DU 5b and the CU 5c, including any information indicating any SBFD-specific configuration and / or any SBFD-specific parameters. This signaling may include, for example, any information indicating (explicitly or implicitly) support (or non-support) of SBFD operation.

[0306] Modifications and Alternatives Detailed embodiments have been described above. As those skilled in the art will appreciate, several modifications and alternatives can be made to the above embodiments while still benefiting from the disclosure embodied therein.

[0307] For example, for clarity, a specific term for a cellular communication generation (e.g., 2G, 3G, 4G, 5G, 6G, etc.) may be used to refer to a particular communication entity, but it will be understood that the technical features described for a given entity are not limited to devices of that specific communication generation, and that the technical features may be implemented in any functionally equivalent communication entity regardless of the terminology used to refer to them.

[0308] In the above description, for ease of understanding, the UE and RAN nodes (which are DU, CU, and RU) have been described as having several separate functional components, or modules. While such modules may be provided in this manner in certain applications, for example where an existing system is modified to implement the present disclosure, in other applications, for example in systems designed from the beginning with the features of the present invention in mind, such modules may be incorporated into an overall operating system or code such that they may not be identifiable as separate entities.

[0309] In the above embodiments, several software modules have been described. As will be appreciated by those skilled in the art, the software modules may be provided in compiled or uncompiled form and may be provided to the RAN node (DU, CU, or RU) or UE as a signal, via a computer network, or on a recording medium. Furthermore, the functions performed by some or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred to facilitate the updating of the RAN or UE to update their functions.

[0310] Each controller may comprise any suitable form of processing circuitry, including (but not limited to) one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses, and / or address buses), direct memory access (DMA) facilities, hardware or software-implemented counters, pointers, and / or timers, etc. Various other modifications will be apparent to those skilled in the art and will not be described in further detail herein.

[0311] It should be noted that the present disclosure is not limited to dedicated communication devices, but can be applied to any device having communication capabilities as described in the following paragraphs.

[0312] The terms "user equipment" or "UE" (as this term is used in 3GPP), "mobile station," "mobile device," and "wireless device" are generally intended to be synonymous with each other and include standalone mobile stations such as terminals, cell phones, smartphones, tablets, cellular IoT devices, IoT devices, and machines. It will be understood that the terms "mobile station" and "mobile device" also encompass devices that remain stationary for extended periods of time.

[0313] For example, the UE may be an item of production or manufacturing equipment and / or an item of energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, nuclear generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or application systems thereof, tools, dies or molds, rolls, conveying equipment, elevators, material handling equipment, textile machinery, sewing machinery, printing and / or related machinery, paper converting machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, machinery and / or implements for the agricultural, forestry, and / or fisheries industries, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems for any of the foregoing equipment or machines, etc.).

[0314] For example, a UE may be an item of transportation equipment (e.g., rail cars, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, aircraft, rockets, satellites, drones, balloons, etc.).

[0315] For example, a UE may be an item of information and communication equipment (eg, information and communication equipment such as electronic computers and related equipment, communication and related equipment, electronic components, etc.).

[0316] For example, the UE may be a refrigerator, a refrigerator application product, an item of trade and / or service industry equipment, a vending machine, an automated service machine, an office machine or equipment, a home appliance or electronic device (e.g., household appliances such as audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electric fans or related equipment, vacuum cleaners, etc.).

[0317] For example, the UE may be an electrical application system or device (eg, an electrical application system or device such as an x-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, a power application device, etc.).

[0318] For example, the UE may be an electronic lamp, lighting fixture, measuring instrument, analyzer, tester, or surveying or detecting equipment (e.g., surveying or detecting equipment such as a smoke alarm, human alarm sensor, motion sensor, radio tag, etc.), a watch or clock, laboratory equipment, optical device, medical equipment and / or system, weapon, cutlery, hand tool, etc.

[0319] For example, the UE may be a wirelessly equipped personal digital assistant or related equipment (such as a wireless card or module designed to be attached to or inserted into another electronic device (e.g., a personal computer, an electrical measuring machine, etc.)).

[0320] The UE may be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below with respect to the "Internet of Things" (IoT).

[0321] Internet of Things devices (or "things") can be equipped with appropriate electronics, software, sensors, network connections, etc. that enable such devices to collect and exchange data with each other and with other communicating devices. IoT devices can include automated machines that follow software instructions stored in internal memory. IoT devices can operate without the need for human direction or interaction. IoT devices can also remain stationary and / or inactive for long periods of time. IoT devices can be implemented as part of (typically) stationary equipment. IoT devices can also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0322] It will be understood that IoT technologies may be implemented on any communication device capable of connecting to a communication network to send / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

[0323] It will be appreciated that IoT devices may also be referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices. It will be appreciated that a UE may support one or more IoT or MTC applications. Some examples of MTC applications are listed in the table below. This list is not exhaustive but is intended to illustrate some examples of machine-type communication applications. [Table 2]

[0324] The applications, services, and solutions may be Mobile Virtual Network Operator (MVNO) services, emergency wireless communication systems, Private Branch eXchange (PBX) systems, PHS / digital cordless telecommunications systems, Point of Sale (POS) systems, incoming advertising systems, Multimedia Broadcast and Multicast Service (MBMS), Vehicle to Everything (V2X) systems, train radio systems, location-related services, disaster / emergency wireless communication services, community services, video streaming services, femtocell application services, Voice over LTE (VoLTE) services, billing services, wireless on-demand services, roaming services, activity monitoring services, telecommunications carrier / communication NW selection services, function restriction services, Proof of Concept (PoC) services, personal information management services, ad hoc networks / delay tolerant networking (DTN) services, and the like.

[0325] Furthermore, the above-mentioned UE categories are merely examples of applications of the technical concepts and embodiments described herein, and it should be understood that these technical concepts and embodiments are not limited to the above-mentioned UEs and may be modified in various ways.

[0326] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0327] For example, all or part of the exemplary embodiments disclosed above can be described as follows, but are not limited to the following: (Appendix 1) 1. A method performed by a first unit of an access network, comprising: a capability of the first unit to communicate with user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or transmitting capability information of the first unit to a second unit of the access network indicating at least one of the first unit's capabilities to separate downlink communications from uplink communications in at least one time resource configured for both downlink and uplink communications; A method comprising: (Appendix 2) 2. The method of claim 1, wherein the capability information includes information indicating the corresponding separation capability for each of a plurality of different separation methods. (Appendix 3) 2. The method of claim 1, wherein the capability information includes information indicating a combined separation capability for a plurality of different separation methods. (Appendix 4) 4. The method of claim 3, wherein the capability information includes information identifying configurations of different separation schemes used to determine the combined separation capability. (Appendix 5) 5. The method of claim 3 or 4, wherein the capability information includes information indicating a corresponding combined separation capability for each of a plurality of different configurations of different separation schemes. (Appendix 6) 6. The method of any one of Supplementary Notes 2 to 5, wherein the different separation schemes include at least one of: a first separation scheme in which at least one guard band is used to separate downlink communications from uplink communications; a second separation scheme in which different beams are used to separate downlink communications from uplink communications; a third separation scheme in which different antenna configurations are used to separate downlink communications from uplink communications; or a fourth separation scheme in which at least one cancellation mechanism is used to separate downlink communications from uplink communications. (Appendix 7) 7. The method of any one of claims 1 to 6, further comprising receiving a request from a second unit, the capability information being provided in response to the request. (Appendix 8) A method performed by a second unit of an access network, comprising: a capability of the first unit to communicate with a user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or and an ability of the first unit to separate downlink communications from uplink communications in at least one time resource configured for both downlink and uplink communications. receiving capability information from a first unit of an access network, the capability information indicating at least one of: (Appendix 9) A method performed by a second unit of an access network, comprising: transmitting, to a first unit of the access network, configuration information for a communication scheme, wherein at least one time resource of the plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication; method. (Appendix 10) 10. The method of claim 9, wherein the configuration information is for configuring the first unit to communicate with at least one user equipment (UE) using multiple time resources according to a communication scheme. (Appendix 11) A method as described in Appendix 9 or 10, wherein the configuration information includes, for each time resource of the plurality of time resources, information indicating whether the time resource is of a first type, a second type, or a third type. (Appendix 12) 11. The method of claim 9 or 10, wherein the first unit has an existing configuration of a plurality of time resources, with at least one time resource configured as a first type and at least one time resource configured as a second type, and the configuration information includes information indicating which of the plurality of time resources of the existing configuration should be changed from the first type or the second type to a third type. (Appendix 13) This configuration information is first information for configuring each resource of the plurality of time resources to a first type for uplink communication or a second type for downlink communication in a first frequency region; and second information for configuring each resource of the plurality of time resources to a first type for uplink communication or a second type for downlink communication in a second frequency region, respectively; 11. The method of claim 9 or 10, comprising: (Appendix 14) In the first unit, at least one time resource of the first type and / or at least one time resource of the second type to be dynamically modified to become a time resource of a third type; and / or and information indicating at least one time resource of a third type that is to be dynamically modified to become a time resource of the first type or a time resource of the second type. 14. The method of any one of claims 9 to 13, further comprising transmitting: (Appendix 15) 15. The method of claim 14, wherein the transmission of the further information is timed to be received by the first unit a minimum time before the first unit receives control information related to transmission of data for at least one UE by the second unit. (Appendix 16) 15. The method of claim 14, wherein the further information is transmitted together with control information regarding data transmission for the at least one UE by the second unit. (Appendix 17) 17. The method of any one of claims 9 to 16, further comprising transmitting to the first unit a frequency domain indication of at least one of an uplink subband, a downlink subband, and / or a guard band. (Appendix 18) 17. The method of any one of claims 9 to 16, further comprising sending to the first unit an indication of a filter to be applied to the time resource configured as the third type. (Appendix 19) 10. The method of claim 9, wherein the configuration information includes at least one of information indicating a configuration of a communication method to implement in the first unit, information indicating a desired configuration for the communication method of the second unit, and / or information indicating a configuration for a communication method of an adjacent unit in the access network or another access network. (Appendix 20) 20. The method of claim 9 or 19, wherein the configuration information includes at least one of the following information: an indication on frequency resources of at least one uplink subband, an indication on frequency resources of at least one downlink subband, an indication on frequency resources of at least one guard band, an indication of a time position of at least one uplink subband or downlink subband, and / or a time position of at least one time resource of the third type, in order to configure at least one time resource as a third type. (Appendix 21) 21. The method of claim 9, 19 or 20, wherein the configuration information is transmitted on the condition that the first unit supports reception of configuration information including information for configuring at least one time resource as a third type, or on the condition that the first unit supports operation according to a communication scheme in which at least one time resource is configured as a third type. (Appendix 22) 21. The method of claim 9, 19 or 20, wherein the configuration information includes information for configuring at least one time resource as a third type, provided that the first unit supports reception of configuration information including information for configuring at least one time resource as a third type, or the first unit supports operation according to a communication scheme in which at least one time resource is configured as the third type. (Appendix 23) 10. The method of claim 9, wherein the configuration information is second configuration information, and wherein transmitting the configuration information includes transmitting first configuration information for configuring at least one time resource as a first type and for configuring at least one time resource as a second type without configuring any time resource as a third type. (Appendix 24) 10. The method of claim 9, wherein the configuration information includes first configuration information for configuring at least one time resource as a first type and at least one time resource as a second type, and second configuration information for configuring at least one time resource as a third type according to the first configuration information as the first type or the second type. (Appendix 25) 1. A method performed by a first unit of an access network, the method comprising receiving, from a second unit of the access network, configuration information for a communication scheme, wherein at least one time resource of a plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication. (Appendix 26) 26. The method of claim 25, wherein the configuration information is for configuring the first unit to communicate with at least one user equipment (UE) using multiple time resources according to a communication scheme. (Appendix 27) 27. The method of claim 25 or 26, further comprising determining a filter to be applied between the uplink subband and the downlink subband based on the guard band configured by the second unit. (Appendix 28) The configuration information is second configuration information, and receiving the configuration information includes receiving first configuration information for configuring at least one time resource as the first type and for configuring at least one time resource as the second type without configuring any time resource as the third type, and the method includes: If the first unit does not support receiving configuration information including information for configuring at least one time resource as a third type, or does not support operation according to a communication method in which at least one time resource is configured as a third type, ignore the second configuration information and use the first configuration information; and using the second configuration information if the first unit supports receiving configuration information including information for configuring at least one time resource as the third type or supports operation according to a communication method in which at least one time resource is configured as the third type. 26. The method of claim 25, further comprising: (Appendix 29) The configuration information includes first configuration information for configuring at least one time resource as a first type and at least one time resource as a second type, and second configuration information for configuring at least one time resource configured by the first configuration information as the first type or the second type as a third type, and the method includes: If the first unit does not support receiving configuration information including information for configuring at least one time resource as a third type, or does not support operation according to a communication method in which at least one time resource is configured as a third type, ignore the second configuration information and use the first configuration information; and If the first unit supports receiving configuration information including information for configuring at least one time resource as a third type, or supports operation according to a communication method in which at least one time resource is configured as a third type, using the first configuration information and the second configuration information. 26. The method of claim 25, further comprising: (Appendix 30) 30. The method of claim 28 or 29, further comprising using a configuration of time resources based on the first configuration information and / or whether the second configuration is used, and sending an indication to the second unit that the configuration of time resources used in the first unit is a configuration that includes at least one time resource configured as a third type, or that the configuration of time resources used in the first unit is a configuration that does not include at least one time resource configured as the third type. (Appendix 31) 31. The method of any one of claims 25 to 30, further comprising providing to the second unit an indication of whether the first unit supports reception of configuration information including information for configuring at least one time resource as a third type, or an indication of whether the first unit supports operation according to a communication scheme in which at least one time resource is configured as a third type. (Appendix 32) 31. The method of any one of claims 25 to 30, further comprising: sending an error message to the second unit in response to receiving the configuration information if the first unit does not support receiving configuration information including information for configuring at least one time resource as a third type, or if the first unit does not support operation according to a communication scheme in which at least one time resource is configured as a third type. (Appendix 33) 1. A method performed by a first unit of an access network, comprising: first information indicating at least one first beam configuration for at least one time resource configured for both downlink and uplink communications, and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for at least one time resource configured for both downlink and uplink communications, and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and / or third information indicating at least one first set of antenna components that may or may not be used for uplink communication in at least one time resource configured for both downlink and uplink communication, and at least one second set of antenna components that may or may not be used for downlink communication in at least one time resource configured for both downlink and uplink communication; fourth information indicating at least one first configuration for antennas for uplink communication in at least one time resource configured for both downlink and uplink communications, and at least one second configuration for antennas for downlink communication in at least one time resource configured for both downlink and uplink communications; transmitting beam or antenna related information, including at least one of: (Appendix 34) A method performed by a second unit of an access network, comprising: first information indicating at least one first beam configuration for at least one time resource configured for both downlink and uplink communications, and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for at least one time resource configured for both downlink and uplink communications, and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and / or third information indicating at least one first set of antenna components that may or may not be used for uplink communications in at least one time resource configured for both downlink and uplink communications, and at least one second set of antenna components that may or may not be used for downlink communications in at least one time resource configured for both downlink and uplink communications; fourth information indicating at least one first configuration for antennas for uplink communications in at least one time resource configured for both downlink and uplink communications, and at least one second configuration for antennas for downlink communications in at least one time resource configured for both downlink and uplink communications; receiving beam or antenna related information from a first unit of an access network, the beam or antenna related information including at least one of A method comprising: (Appendix 35) 35. The method of claim 34, further comprising using beam or antenna related information when identifying a beam to be used for at least one time resource configured for both downlink and uplink communications. (Appendix 36) 36. The method of claim 34 or 35, further comprising using beam- or antenna-related information when identifying at least one weighting to apply to beamforming for at least one time resource configured for both downlink and uplink communications. (Appendix 37) A first unit for an access network, the first unit comprising: a capability of the first unit to communicate with a user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or and an ability of the first unit to separate downlink communications from uplink communications in at least one time resource configured for both downlink and uplink communications. means for transmitting information indicating at least one of the following to a second unit of the access network: A unit comprising: (Appendix 38) a second unit for the access network, means for receiving capability information from the first unit of the access network, the capability information comprising: a capability of the first unit to communicate with user equipment (UE) using a communication scheme in which at least one time resource is configured for uplink communication, at least one time resource is configured for downlink communication, and at least one time resource is configured for both downlink and uplink communication; or and an ability of the first unit to separate downlink communications from uplink communications in at least one time resource configured for both downlink and uplink communications. a means for receiving capability information indicating at least one of A unit comprising: (Appendix 39) a second unit for an access network, means for transmitting, to a first unit of an access network, configuration information for a communication scheme, wherein at least one time resource of a plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication; A unit comprising: (Appendix 40) A first unit for an access network, comprising: means for receiving configuration information for the communication scheme from a second unit of the access network, the configuration information being such that at least one time resource of the plurality of time resources is configured as a first type for uplink communication, at least one time resource of the plurality of time resources is configured as a second type for downlink communication, and at least one time resource of the plurality of time resources is configured as a third type for both downlink and uplink communication; A first unit comprising: (Appendix 41) A first unit for an access network, comprising: means for transmitting beam or antenna related information to a second unit of the access network, the information comprising: first information indicating at least one first beam configuration for at least one time resource configured for both downlink and uplink communications, and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for at least one time resource configured for both downlink and uplink communications, and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and / or third information indicating at least one first set of antenna components that may or may not be used for uplink communication in at least one time resource configured for both downlink and uplink communication, and at least one second set of antenna components that may or may not be used for downlink communication in at least one time resource configured for both downlink and uplink communication; fourth information indicating at least one first configuration of antennas for uplink communications in at least one time resource configured for both downlink and uplink communications, and at least one second configuration of antennas for downlink communications in at least one time resource configured for both downlink and uplink communications; means for transmitting beam or antenna related information to a second unit of the access network, the means including at least one of A unit comprising: (Appendix 42) a second unit for an access network, means for receiving beam or antenna related information from a first unit of an access network, said information being first information indicating at least one first beam configuration for at least one time resource configured for both downlink and uplink communications, and at least one second beam configuration for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; second information indicating at least one first beam pattern for at least one time resource configured for both downlink and uplink communications, and at least one second beam pattern for at least one time resource configured exclusively for downlink communications or exclusively for uplink communications; and / or third information indicating at least one first set of antenna components configured for both downlink and uplink communications, which may or may not be used for uplink communications in at least one time resource, and at least one second set of antenna components configured for both downlink and uplink communications, which may or may not be used for downlink communications in at least one time resource. fourth information indicating at least one first configuration of antennas for uplink communication in at least one time resource configured for both downlink and uplink communications, and at least one second configuration of antennas for downlink communication in at least one time resource configured for both downlink and uplink communications; means for receiving beam or antenna related information from a first unit of an access network, the means including at least one of A unit comprising:

[0328] This application is based on and claims the benefit of priority from UK Patent Application No. 2304384.7, filed March 24, 2023, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0329] 1. Communication Systems 3. User Equipment 5. Radio Access Network 5a Radio / Remote Unit (RU) 5b Distributed Unit (DU) 7 Core Network 9 cells 10 Control Plane Functions 11 User Plane Functions 20 External Data Network 30 Service Management and Orchestration Framework 4331 Transceiver Circuit 4333 Antenna 4335 User Interface 4337 Controller 4339 memory 4341 Operating System 4343 Communication Control Module 4345 UE Management Module 4451 Transceiver Circuit 4453 Antenna 4454 DU interface 4457 Controller 4459 memory 4461 Operating Systems 4463 Communication Control Module 4468 DU-RU module 4472 RU Management Module 4551 Transceiver Circuit 4552 RIC interface 4553 RU interface 4554 CU interface 4557 Controller 4559 memory 4561 Operating Systems 4563 Communication Control Module 4565 F1 module 4567 E2 module 4568 DU-RU module 4572 DU Management Module 4651 Transceiver Circuit 4652 RIC interface 4654 DU interface 4655 CN interface 4657 Controller 4659 memory 4661 Operating Systems 4663 Communication Control Module 4665 F1 Module 4666 E1 Module 4667 E2 module 4668 N2 Module 4669 N3 Module 4671 CU-UP Management Module 4672 CU-CP Management Module

Claims

1. A method performed by a first unit of an access network, comprising: transmitting configuration information to a second unit of the access network indicating which time resources are configured for subband full duplex (SBFD); A method comprising:

2. the configuration information indicating which time resources are configured for uplink communications only or downlink communications only; The method of claim 1.

3. the configuration information indicating which time resources are to be modified to be configured for SBFD, for uplink communications only, or for downlink communications only; 3. The method according to claim 1 or 2.

4. The configuration information indicates a configuration of each time resource for each frequency domain.

4. The method according to any one of claims 1 to 3.

5. Each of the frequency regions is Uplink subbands, downlink subband, or Guard Band Indicate at least one of The method of claim 4.

6. a filter to be applied between the uplink subband and the downlink subband is determined by the second unit based on the guard band; The method of claim 5.

7. transmitting to the second unit a filter to be applied between the uplink subbands and the downlink subbands in the time resources configured for SBFD; The method of claim 5 further comprising:

8. the configuration information indicates which time resources are dynamically modified to be configured for SBFD, for uplink communications only, or for downlink communications only; the configuration information is received before receiving data transmitted using the time resource; or transmitted in a message for scheduling transmission of the data; 8. The method according to any one of claims 1 to 7.

9. The configuration information is The second unit is configured by the first unit; a configuration for the first unit, intended by the first unit, or Configuration for adjacent units of said access network or another access network Indicate at least one of the following:

9. The method according to any one of claims 1 to 8.

10. The configuration information is transmitted if the second unit supports an SBFD scheme.

10. The method according to any one of claims 1 to 9.

11. receiving information from the second unit indicating that the second unit does not support the SBFD scheme; The method of claim 1 , further comprising:

12. If the second unit does not support the SBFD method, the configuration information is ignored by the second unit.

12. The method according to any one of claims 1 to 11.

13. A method performed by a second unit of an access network, comprising: receiving configuration information from a first unit of the access network indicating which time resources are configured for subband full duplex (SBFD); A method comprising:

14. A method performed by a first unit of an access network, comprising: the capability of the first unit to communicate with user equipment (UE) using subband full duplex (SBFD) symbols; or the capability of the first unit to separate downlink communications from uplink communications in SBFD symbols in the frequency domain or spatial domain; transmitting capability information indicating at least one of the following to a second unit of the access network: A method comprising:

15. the capability information includes at least one parameter for a plurality of separation schemes for separating the downlink communication from the uplink communication in the SBFD symbol.

15. The method of claim 14.

16. the first set of at least one parameter is specific to one of the plurality of separation schemes; 16. The method of claim 15.

17. each of the at least one second set of the at least one parameter is common to the plurality of separation schemes; 17. The method of claim 15 or 16.

18. the capability information includes detailed configuration for determining a respective value of one of the at least one second set of the at least one parameter; 18. The method of claim 17.

19. receiving a request to transmit the at least one parameter using one detailed configuration; Further comprising: transmitting the capability information based on the detailed configuration; 20. The method of claim 18.

20. The at least one parameter is: at least one value, each indicating a respective supported guard band combination; at least one value, each indicating a respective supported beam pair; at least one value each indicating a respective supported antenna array and / or panel configuration, or At least one value each indicating each of the supported digital and / or analog cancellation mechanisms including at least one of 20. The method of any one of claims 14 to 19.

21. A method performed by a second unit of an access network, comprising: the capability of the first unit to communicate with user equipment (UE) using subband full duplex (SBFD) symbols; or the capability of the first unit to separate downlink communications from uplink communications in SBFD symbols in the frequency domain or spatial domain; receiving capability information from the first unit of the access network indicating at least one of A method comprising:

22. A method performed by a first unit of an access network, comprising: at least one first configuration for subband full duplex (SBFD) symbols; and at least one second configuration for uplink-only symbols or downlink-only symbols; transmitting beam or antenna related information to a second unit of said access network, A method comprising:

23. The at least one first configuration and the at least one second configuration are: Supported beam configurations, Supported beamforming patterns, or Supported antenna panels, antenna arrays, and / or sets of antenna elements each of which indicates at least one of 23. The method of claim 22.

24. A method performed by a second unit of an access network, comprising: at least one first configuration for subband full duplex (SBFD) symbols; and At least one second configuration for uplink-only symbols or downlink-only symbols. receiving beam or antenna related information from a first unit of the access network, A method comprising:

25. means for transmitting, to a first unit of an access network, configuration information indicating which time resources are configured for subband full duplex (SBFD) to a second unit of said access network; A unit comprising:

26. a second unit of the access network for receiving configuration information from the first unit of the access network indicating which time resources are configured for subband full duplex (SBFD); A unit comprising:

27. A first unit of an access network, comprising: the capability of the first unit to communicate with user equipment (UE) using subband full duplex (SBFD) symbols; or the capability of the first unit to separate downlink communications from uplink communications in SBFD symbols in the frequency domain or spatial domain; means for transmitting capability information indicating at least one of the following to a second unit of the access network: A unit comprising:

28. a second unit of the access network, the capability of the first unit to communicate with user equipment (UE) using subband full duplex (SBFD) symbols; or the capability of the first unit to separate downlink communications from uplink communications in SBFD symbols in the frequency domain or spatial domain; means for receiving capability information from the first unit of the access network, the capability information indicating at least one of A unit comprising:

29. A first unit of an access network, comprising: at least one first configuration for subband full duplex (SBFD) symbols; and At least one second configuration for uplink-only symbols or downlink-only symbols. means for transmitting beam or antenna related information to a second unit of said access network, A unit comprising:

30. a second unit of the access network, at least one first configuration for subband full duplex (SBFD) symbols; and At least one second configuration for uplink-only symbols or downlink-only symbols. means for receiving beam or antenna related information from a first unit of said access network, A unit comprising:

Images