Methods performed by mobile devices, methods performed by access network nodes, mobile devices, and access network nodes

Abstract

The present disclosure relates to a method performed by a user equipment (UE) (3), the method including: receiving, from an access network node, first information indicating at least one repeating pattern of time resources for uplink (UL) communications and time resources for downlink (DL) communications and at least one set of time resources for UL sub-bands; receiving control signals from the access network node; determining whether the at least one set of time resources for the UL sub-bands conflicts in the time domain with at least one time resource for control signals; and, based on the determination whether the set of at least one time resources for the UL sub-bands conflicts in the time domain with the at least one time resource for control signals, determining to the access network node whether to transmit a UL transmission on the UL sub-band using the at least one set of time resources for the UL sub-bands.

Description

Technical Field

[0001] The present disclosure relates to a method executed by a user equipment, a method executed by an access network node, a user equipment, and an access network node. The present disclosure is particularly relevant, although not exclusive, to wireless communication systems and their devices operating according to 3rd Generation Partnership Project (3GPP (registered trademark)) standards or equivalent or derivative standards thereof (including LTE Advanced, next generation or 5G networks, future generations, and so on). The present disclosure is particularly relevant, although not necessarily exclusive, to improved apparatuses and methods for supporting full duplex communication and uplink subbands in a time division duplex (TDD) communication band.

Background Art

[0002] Recent developments in 3GPP standards are referred to as Long-Term Evolution (LTE) of the Evolved Packet Core (EPC) network and the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), and are also generally referred to as "4G". Also, the terms "5G" and "new radio" (NR) refer to evolving communication technologies expected to support various applications and services. Various details of 5G networks are described in the "NGMN 5G White Paper" V1.0 by the Next Generation Mobile Network (NGMN) Alliance, which can be obtained, for example, from https: / / www.ngmn.org / / 5g-white-paper.html. 3GPP intends to support 5G with the so-called 3GPP Next Generation (NextGen) radio access network (RAN) and 3GPP NextGen core network.

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

[0004] In current 5G architectures, for example, a gNB structure can be split into two parts known as the Central Unit (CU) and the Distributed Unit (DU), connected by an F1 interface. This allows for the use of a “split” architecture, where typically the “upper” CU layer (e.g., not necessarily or not exclusively), PDCP, and typically the “lower” DU layer (e.g., not necessarily or not exclusively, RLC / MAC / PHY) are implemented separately. Thus, for example, in each gNB, some of the upper-layer CU functions of the gNB may be centrally implemented (e.g., by a single processing unit, or in a cloud-based or virtualized system), while the lower-layer DU functions are held locally.

[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. While this application may refer to mobile devices in the description, it will be understood that the technology described can be implemented in any communication device (mobile and / or generally stationary) that can connect to a communication network to transmit / receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

[0006] Until now, communication systems have used two core duplexing methods: frequency division duplex (FDD) and time division duplex (TDD). In FDD, frequency domain resources are divided into downlink (DL) and uplink (UL), while in TDD, time domain resources are divided into DL and UL. The appropriate duplexing scheme to be used in a given scenario is largely spectrum-dependent, although there is some overlap. When low-frequency bands are used for communication, paired spectrum UL and DL resource allocation are commonly used, and therefore FDD is used. In contrast, in high-frequency bands, the use of unpaired spectrum, i.e., TDD, is becoming increasingly prevalent. Thus, TDD is widely used in commercial NR deployments. Given the significantly higher carrier frequencies supported by 5G, and by future communication generations (6G and beyond), compared to previous generations, improved technologies to provide efficient use of unpaired spectrum are, and will continue to be, increasingly important.

[0007] However, because there are limitations on the duration allocation for UL in TDD carriers, this can result in reduced coverage, increased latency, and reduced capacity.

[0008] Full duplex (FD) operation, which involves sharing both frequency-domain and time-domain resources between the UL and DL within the bandwidth of a conventional TDD carrier, represents one possible way to achieve performance improvements over conventional TDD. Therefore, extensions for implementing full-duplex operation in gNBs within a TDD carrier are currently under development, and there are currently no limitations on the possible frequency range used for such FD operation. For now, half-duplex operation within a TDD carrier is still assumed for UEs, while full-duplex UE operation remains a future option. However, the use of FD can introduce serious interference problems that are difficult to address at both base stations and UEs.

[0009] For example, there are several possible FD implementations that can be implemented on a TDD carrier, including subband non-overlap, subband overlap, and full overlap.

[0010] Referring to Figures 1 to 4, in subband non-overlapping FD ("SBFD," also called cross-division duplex (XDD)), (as seen in the typical case shown in Figure 1) ) Non-overlapping UL and DL subbands can be configured within a TDD carrier. As seen in Figures 1 to 4, each subband contains its respective relatively "narrow" frequency band, having a bandwidth that extends only a portion of the total available bandwidth within the current TDD carrier configured for communication in the associated cell. Thus, a base station can perform simultaneous (full-duplex) transmission and reception to different UEs in different non-overlapping subbands.

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

[0012] In subband overlap FD, UL and DL can be configured similarly to subband non-overlapping FD, but different subbands can overlap in frequency.

[0013] In fully duplicated FD, the entire available bandwidth may be used for UL or DL ​​transmission.

[0014] One of the key advantages of SBFD is increased UL coverage because SBFD facilitates the use of multi-slot UL iterations due to the increased number of consecutive UL opportunities. Therefore, current focus is on developing techniques to implement subband non-overlapping FD operation and potential related extensions for dynamic or flexible TDD. However, other FD implementations remain future options, and it will be understood that extensions envisioned for subband non-overlapping FD may also benefit other FD schemes.

[0015] When implementing such a full-duplex scheme, several considerations must be taken into account. Among the considerations particularly relevant to SBFD (and other full-duplex schemes) is the need to avoid, or at least minimize, any impact on the operation of existing ("legacy") UEs designed / implemented prior to the implementation of any such duplex scheme. Furthermore, the impact of full-duplex on other procedures such as search space configuration, resource allocation for DL ​​and UL channels, as well as UL / DL transmission and configuration procedures (e.g., multi-slot transmission), retuning, and reception of synchronization signal block (SSB) and reference signals must be considered. [Prior art documents] [Non-patent literature]

[0016] [Non-Patent Document 1] "NGMN 5G White Paper" V1.0 [Overview of the Initiative] [Problems that the invention aims to solve]

[0017] This disclosure aims to provide apparatus and methods that address, at least partially, the above-mentioned needs and / or problems. [Means for solving the problem]

[0018] In a first aspect, the Disclosure provides a method performed by user equipment (UE), the method comprising: receiving first information from an access network node indicating at least one repeating pattern of time resources for uplink (UL) communications and time resources for downlink (DL) communications, and at least one set of time resources for a UL subband; receiving a control signal from the access network node; determining whether at least one set of time resources for a UL subband conflicts in the time domain with at least one set of time resources for a control signal; and, based on the determination of whether at least one set of time resources for a UL subband conflicts in the time domain with at least one set of time resources for a control signal, determining whether to send a UL transmission on the UL subband using at least one set of time resources for a UL subband to the access network node.

[0019] The method may include deciding to discard a UL transmission or a UL grant for a UL transmission if at least one set of time resources for a UL subband conflicts in the time domain with at least one time resource for a control signal.

[0020] The method may include deciding not to monitor at least one control resource set (CORESET) or downlink control information (DCI) if at least one set of time resources for the UL subband conflicts in the time domain with at least one time resource for control signals.

[0021] The method may include determining to perform UL transmission in a UL subband without using at least a portion of at least one set of time resources for the UL subband that conflicts with at least one time resource for a control signal in the time domain, when at least one set of time resources for the UL subband has a portion that conflicts with at least one time resource for a control signal in the time domain and another portion that does not conflict with at least one time resource for a control signal in the time domain, and using another portion of at least one set of time resources for the UL subband that does not conflict with at least one time resource for a control signal in the time domain.

[0022] The method may include determining to perform UL transmission in a UL subband without using at least one symbol for the UL subband that conflicts with at least one time resource for a control signal in the time domain, when at least one symbol for the UL subband conflicts with at least one time resource for a control signal in the time domain and at least one other symbol for the UL subband does not conflict with at least one time resource for a control signal in the time domain, and using at least one other symbol for the UL subband that does not conflict with at least one time resource for a control signal in the time domain.

[0023] The determination may be made when at least one set of time resources for the UL subband conflicts with at least one time resource for a control signal in the time domain, where the at least one set of time resources for the UL subband is transmitted close to the currently selected synchronization signal block of the UE, the camped synchronization signal block of the UE, a synchronization signal block transmitted close to the currently selected synchronization signal block or the camped synchronization signal block of the UE, a reference signal to be used for radio link monitoring or link recovery, or at least one time resource for a control signal that the UE needs to receive.

[0024] When at least one set of time resources for a UL sub-band conflicts with at least one time resource for a control signal in the time domain, at least one symbol for the UL sub-band may at least partially overlap with at least one time resource for the control signal, or the start symbol of at least one set of time resources for the UL sub-band may be less than a predetermined time after the end symbol of at least one time resource for the control signal.

[0025] The predetermined time may be determined based on the timing advance value of the UE.

[0026] In a second aspect, the present disclosure provides a method performed by a user equipment (UE), the method comprising receiving, from an access network node, first information indicating two patterns of time resources for UL communication using an uplink (UL) sub-band, wherein a first pattern of the two patterns includes time resources for UL communication using a UL sub-band that is larger than a second pattern of the two patterns, and the time resources for UL communication using the UL sub-band indicated by the second pattern do not conflict with at least one time resource for a control signal in the time domain, receiving, from the access network node, a control signal using at least one time resource for the control signal, and performing UL communication using time resources for a UL sub-band corresponding to at least one of the first pattern or the second pattern with the access network node.

[0027] The first pattern may be used for at least one period that does not include a duration corresponding to at least one time resource for the control signal.

[0028] A combination of one or more of the first pattern and one or more of the second pattern may form a repeating pattern, and the period of transmission of the control signal may be the same as the period of the repeating pattern or an integer multiple of the period of the repeating pattern.

[0029] The period of the repeating pattern may differ from the period of at least one instance of the time resources for UL communication and time resources for DL ​​communication as shown in the time-division duplex UL / DL configuration.

[0030] The first information may be included in a time-division duplex UL / DL configuration, which may include multiple repeating patterns of time resources for UL communication and time resources for DL ​​communication, each of which repeating patterns of time resources for UL communication and time resources for DL ​​communication may correspond to each combination of one or more first patterns and one or more second patterns that constitute the repeating pattern.

[0031] The control signal may be transmitted via broadcast transmission, and the control signal may include at least one of a synchronization signal block (SSB), a broadcast channel, or a reference signal.

[0032] In a third aspect, the Disclosure provides a method performed by user equipment (UE) which includes performing UL communication with an access network node while restricting UL communication in a time gap between a first time resource configured for uplink (UL) communication or downlink (DL) communication and a second time resource configured for UL communication in a UL subband.

[0033] Restrictions may be implemented based on a configuration sent from the access network node, which may indicate that the UL subband will not be presented within the time gap.

[0034] Restriction can be achieved by having access network nodes not schedule any UL communications within the time gap.

[0035] Restrictions can be implemented by rate-matching UL communications or by discarding time resources for UL communications within a time gap.

[0036] The time gap may exist within the start symbol corresponding to the later of the two time resources (the first and second resources).

[0037] The time gap may occur within the end symbol corresponding to the earlier of the two time resources, the first and second resources.

[0038] A time gap may occur within the start symbol corresponding to the second time resource if the first time resource is before the second time resource, or within the end symbol corresponding to the second time resource if the first time resource is after the second time resource.

[0039] Restrictions may be imposed when the bandwidth of the first time resource differs from the bandwidth of the UL subband.

[0040] The time gap may be represented by one or more flexible symbols or guard periods during which UL communication is not scheduled.

[0041] The method may include receiving information indicating a time gap from an access network node.

[0042] In a fourth aspect, the Disclosure provides a method performed by user equipment (UE), the method comprising: receiving from an access network node a common configuration in a cell of the access network node, which indicates from the access network node a first pattern of at least one of time resources for uplink (UL) communications, time resources for downlink (DL) communications, and time resources for both UL communications and DL communications, and a second pattern of time resources for UL communications using a UL subband; receiving from the access network node a dedicated configuration for the UE, which indicates a third pattern of at least one of time resources for UL communications, time resources for DL ​​communications, and time resources for both UL communications and DL communications; and configuring time resources for UL communications using a UL subband within a duration in which the time resources for both UL communications and DL communications of the first pattern and the time resources for UL communications using a UL subband of the second pattern overlap, based on whether the dedicated configuration includes a fourth pattern of time resources for a UL subband.

[0043] Configuration can be achieved by using time resources to perform UL communications on the UL subband within the fourth pattern, provided that the dedicated configuration includes a fourth pattern of time resources for the UL subband.

[0044] Configuration can be achieved by using time resources for performing UL communications on the UL subband within the second pattern, if the dedicated configuration does not include a fourth pattern of time resources for the UL subband.

[0045] The method may include discarding time resources for UL communications using the UL subband within the duration of time resources for both UL and DL communications in the first pattern and time resources for UL communications in the third pattern.

[0046] In a fifth aspect, the Disclosure provides a method performed by an access network node, the method comprising: transmitting to user equipment (UE) first information indicating at least one repeating pattern of time resources for uplink (UL) communications and time resources for downlink (DL) communications, and at least one set of time resources for a UL subband; transmitting a control signal to the UE; and receiving a UL transmission on the UL subband from the UE using at least one set of time resources for the UL subband, based on a determination of whether at least one set of time resources for the UL subband conflicts in the time domain with at least one set of time resources for the control signal.

[0047] In a sixth aspect, the Disclosure provides a method performed by an access network node, the method comprising transmitting to user equipment (UE) first information indicating two patterns of time resources for UL communications using an uplink (UL) subband, wherein the first pattern of the two patterns includes time resources for UL communications using an UL subband, the first pattern of the two patterns being greater than a second pattern of the two patterns, and the time resources for UL communications using an UL subband indicated by the second pattern do not conflict in the time domain with at least one time resource for control signals, the method comprising transmitting a control signal to the UE using at least one time resource for control signals, and performing UL communications with the UE using time resources using an UL subband corresponding to at least one of the first pattern or the second pattern.

[0048] In a seventh aspect, the Disclosure provides a method performed by an access network node, the method comprising performing UL communication with user equipment (UE) while restricting UL communication in a time gap between a first time resource configured for uplink (UL) communication or downlink (DL) communication and a second time resource configured for UL communication in a UL subband.

[0049] In an eighth aspect, the Disclosure provides a method performed by an access network node, the method comprising: transmitting to user equipment a common configuration in a cell of the access network node, indicating a first pattern of at least one of time resources for uplink (UL) communications, time resources for downlink (DL) communications, and time resources for both UL communications and DL communications, and a second pattern of time resources for UL communications using a UL subband; transmitting to a UE a dedicated configuration for the UE, indicating a third pattern of at least one of time resources for UL communications, time resources for DL ​​communications, and time resources for both UL communications and DL communications; and configuring the UE with time resources for UL communications using a UL subband within a duration in which the time resources for both UL communications and DL communications of the first pattern and the time resources for UL communications using a UL subband of the second pattern overlap, based on whether the dedicated configuration includes a fourth pattern of time resources for a UL subband.

[0050] In the ninth aspect, the Disclosure provides a means for receiving first information from an access network node, which indicates at least one repeating pattern of time resources for uplink (UL) communications and time resources for downlink (DL) communications, and at least one set of time resources for a UL subband; a means for receiving a control signal from an access network node; a means for determining whether at least one set of time resources for a UL subband conflicts in the time domain with at least one set of time resources for a control signal; and, based on the determination of whether at least one set of time resources for a UL subband conflicts in the time domain with at least one set of time resources for a control signal, the Disclosure provides the access network node with at least one set of time resources for a UL subband. The provided user equipment (UE) includes means for determining whether to transmit a UL transmission on a UL subband using a UT; means for instructing an access network node to transmit an uplink transmission on a UL subband using at least one set of time resources for a UL subband if it is determined that at least one of the time resources for a UL subband does not overlap with a broadcast transmission in the time domain at least partially; and means for determining whether to instruct an access network node not to transmit an uplink transmission on a UL subband using at least one of the time resources for a UL subband if it is determined that at least one of the time resources for a UL subband overlaps with a broadcast transmission in the time domain at least one.

[0051] In a tenth aspect, the Disclosure provides user equipment (UE) comprising means for receiving first information from an access network node indicating two patterns of time resources for UL communications using an uplink (UL) subband, wherein the first pattern of the two patterns includes time resources for UL communications using an UL subband, the first pattern of the two patterns being greater than a second pattern of the two patterns, and the time resources for UL communications using an UL subband indicated by the second pattern do not conflict in the time domain with at least one time resource for control signals, the UE comprising means for receiving control signals from an access network node using at least one time resource for control signals, an access network node, and means for performing UL communications using time resources using an UL subband corresponding to at least one of the first pattern or the second pattern.

[0052] In an eleventh aspect, the Disclosure provides user equipment (UE) comprising means for performing UL communication with an access network node while restricting UL communication in a time gap between a first time resource configured for uplink (UL) communication or downlink (DL) communication and a second time resource configured for UL communication in a UL subband.

[0053] In a twelfth aspect, the Disclosure provides a UE comprising: means for receiving a common configuration in a cell of an access network node from an access network node, indicating a first pattern of at least one of time resources for uplink (UL) communication, time resources for downlink (DL) communication, and time resources for both UL and DL communication, and a second pattern of time resources for UL communication using a UL subband; means for receiving a dedicated configuration for user equipment (UE) from an access network node, indicating a third pattern of at least one of time resources for UL communication, time resources for DL ​​communication, and time resources for both UL and DL communication; and means for configuring a time resource for UL communication using a UL subband within a duration in which the time resources for both UL and DL communication of the first pattern and the time resources for UL communication using a UL subband of the second pattern overlap, based on whether the dedicated configuration includes a fourth pattern of time resources for a UL subband.

[0054] In a thirteenth aspect, the Disclosure provides an access network node comprising: means for transmitting to user equipment (UE) first information indicating at least one repeating pattern of time resources for uplink (UL) communications and time resources for downlink (DL) communications and at least one set of time resources for a UL subband; means for transmitting control signals to the UE; and means for receiving UL transmissions on the UL subband from the UE using at least one set of time resources for the UL subband, based on a determination of whether at least one set of time resources for the UL subband conflicts in the time domain with at least one set of time resources for control signals.

[0055] In a fourteenth aspect, the Disclosure provides an access network node comprising means for transmitting to user equipment (UE) first information indicating two patterns of time resources for UL communications using an uplink (UL) subband, wherein the first pattern of the two patterns includes time resources for UL communications using an UL subband, the first pattern of the two patterns being greater than a second pattern of the two patterns, and the time resources for UL communications using an UL subband indicated by the second pattern do not conflict in the time domain with at least one time resource for control signals, the access network node comprising means for transmitting a control signal to the UE using at least one time resource for control signals, and means for the UE and time resources using an UL subband corresponding to at least one of the first pattern or the second pattern.

[0056] In a 15th aspect, the Disclosure provides an access network node comprising means for performing UL communication with user equipment (UE) while restricting UL communication in the time gap between a first time resource configured for uplink (UL) communication or downlink (DL) communication and a second time resource configured for UL communication in a UL subband.

[0057] In a sixteenth aspect, the Disclosure provides an access network node comprising: means for transmitting a common configuration in a cell of an access network node to user equipment, indicating a first pattern of at least one of time resources for uplink (UL) communication, time resources for downlink (DL) communication, and time resources for both UL and DL communication, and a second pattern of time resources for UL communication using a UL subband; means for transmitting a dedicated configuration for a UE to a UE, indicating a third pattern of at least one of time resources for UL communication, time resources for DL ​​communication, and time resources for both UL and DL communication; and means for configuring the UE with time resources for UL communication using a UL subband within a duration in which the time resources for both UL and DL communication of the first pattern and the time resources for UL communication using a UL subband of the second pattern overlap, based on whether the dedicated configuration includes a fourth pattern of time resources for a UL subband. [Brief explanation of the drawing]

[0058] Herein, embodiments of the present disclosure will be described by reference to the accompanying drawings as an example. [Figure 1] Figure 1 is a simplified time-frequency diagram showing a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 2] Figure 2 is a simplified time-frequency diagram showing a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 3] Figure 3 is a simplified time-frequency diagram showing a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 4] Figure 4 is a simplified time-frequency diagram showing a subband non-overlapping full-duplex scheme and various exemplary implementations of such a scheme. [Figure 5] Figure 5 is a schematic diagram illustrating a mobile ("cellular" or "wireless") telecommunications system. [Figure 6]Figure 6 shows a typical frame structure that may be used in the telecommunications system shown in Figure 5. [Figure 7] Figure 7 is a simplified sequence diagram showing different slot configuration procedures that can be used in the telecommunications system shown in Figure 5. [Figure 8] Figure 8 shows an example of a slot configuration constructed according to the procedure in Figure 7. [Figure 9] Figure 9 shows a further example of a slot configuration constructed according to the procedure in Figure 7. [Figure 10] Figure 10 is a simplified time-frequency diagram showing an example of a non-interleaved CORESET design that may be used in the telecommunications system shown in Figure 5. [Figure 11] Figure 11 is a simplified time-frequency diagram showing an example of a full-duplex configuration that may be used in the telecommunications system shown in Figure 5. [Figure 12] Figure 12 is a simplified time-frequency diagram showing another example of a full-duplex configuration that may be used in the telecommunications system shown in Figure 5. [Figure 13] Figure 13 is a simplified time-frequency diagram showing another example of a full-duplex configuration that may be used in the telecommunications system shown in Figure 5. [Figure 14] Figure 14 shows an example where the SSB pattern has a 20ms period and the TDD pattern has a 5ms period. [Figure 15] Figure 15 shows an example where the period of the UL subband is the same as the period of the SSB. [Figure 16] Figure 16 shows an example where the first SBFD pattern is used for TDD opportunities that may overlap with SSB, and the second SBFD pattern is used for TDD opportunities that do not overlap with SSB. [Figure 17] Figure 17 shows an example where the UL subband overlaps with SSB, but competition between the UL subbands still prevents SSB from being transmitted. [Figure 18] Figure 18 shows an example where a common TDD configuration includes UL subband opportunity indication, and a dedicated TDD configuration is also provided. [Figure 19]Figure 19 shows a modified example of the example in Figure 18, in which the dedicated TDD configuration includes UL subband opportunity indication. [Figure 20] Figure 20 shows an example of when retuning may be performed on different UL bandwidth interfaces. [Figure 21] Figure 21 shows an example where a guard period is provided from the start of the first UL-only symbol when a transition occurs from an UL subband slot / symbol to an UL-only slot / symbol, and from the start of the first UL subband symbol when a transition occurs from an UL-only slot / symbol to an UL subband slot / symbol. [Figure 22] Figure 22 shows an example where a guard period is provided at the end of a UL subband slot / symbol when a transition occurs from a UL subband slot / symbol to a UL-only slot / symbol, and at the end of a UL-only slot / symbol when a transition occurs from a UL-only slot / symbol to a UL subband slot symbol. [Figure 23] Figure 23 shows an example where a guard period is provided at the end of the UL subband slot / symbol when a transition occurs from an UL subband slot / symbol to an UL-only slot / symbol, and from the start of the first UL subband symbol when a transition occurs from an UL-only slot / symbol to an UL subband slot / symbol. [Figure 24] Figure 24 is a schematic block diagram showing the main components of the UE for the telecommunications system in Figure 5. [Figure 25] Figure 25 is a schematic block diagram showing the main components of the base station for the telecommunications system shown in Figure 5. [Modes for carrying out the invention]

[0059] overview Here, an exemplary telecommunications system will be described using general terminology, with reference to Figures 5 through 12.

[0060] Figure 5 schematically shows a mobile ("cellular" or "wireless") telecommunications system 1 to which embodiments of the present disclosure can be applied.

[0061] In network 1, user equipment (UE) 3-1, 3-2, 3-3 (e.g., mobile phones and / or other mobile devices) can communicate with each other via radio access network (RAN) nodes 5 operating according to one or more compatible radio access technologies (RATs). In the illustrated example, RAN node 5 comprises an NR / 5G base station or "gNB" 5 operating one or more associated cells 9. Communication via base station 5 is typically routed through a core network 7 (e.g., a 5G core network or evolved packet core network (EPC)).

[0062] As those skilled in the art will understand, Figure 5 shows three UE3s and one base station 5 for illustrative purposes, but the system, when implemented, typically includes other base stations 5 and UE3s.

[0063] Each base station 5 controls one or more associated cells 9 directly or indirectly through one or more other nodes (e.g., home base stations, relays, remote radio heads, distributed units, etc.). It will be understood that base stations 5 may be configured to support 4G, 5G, 6G, and / or any other 3GPP or non-3GPP communication protocols.

[0064] The UE3 and their service-providing base stations 5 are connected via an appropriate air interface (e.g., a so-called "Uu" interface). Neighboring base stations 5 may be connected to each other via appropriate inter-base station interfaces (e.g., a so-called "X2" interface, an "Xn" interface, etc.).

[0065] The core network 7 includes several logical nodes (or "functions") to support communication in the telecommunications system 1. In this example, the core network 7 comprises a control plane function (CPF) 10 and one or more user plane functions (UPF) 11. The CPF 10 includes one or more Access and Mobility Management Functions (AMFs) 10-1, one or more Session Management Functions (SMFs), and several other functions 10-n.

[0066] Base station 5 is connected to the core network nodes via appropriate interfaces (or "reference points"), such as an N2 reference point between base station 5 and AMF10-1 for control signaling communications, and an N3 reference point between base station 5 and each UPF11 for user data communications. Each UE3 is connected to AMF10-1 via a logical non-access stratum (NAS) connection on the N1 reference point (similar to the S1 reference point in LTE). It will be understood that N1 communications are routed transparently through base station 5.

[0067] One or more UPF11s are connected to an external data network (e.g., an IP network such as the Internet) via a reference point N6 for the communication of user data.

[0068] The AMF10-1 performs mobility management-related functions, maintains non-NAS signaling connectivity with each UE3, and manages UE registration. The AMF10-1 is also responsible for managing paging. The SMF10-2 provides session management functions (which form part of the MME function in LTE) and also incorporates several control plane functions (provided by the serving gateway and packet data network gateway in LTE). The SMF10-2 also assigns IP addresses to each UE3.

[0069] The base station 5 of communication system 1 is configured to operate at least one cell 9 on an associated TDD carrier operating in a non-paired spectrum. It will be understood that base station 5 may also operate at least one cell 9 on an associated FDD carrier operating in a paired spectrum.

[0070] Base station 5 is also configured for transmitting control information and user data via several downlink (DL) physical channels, as well as for transmitting several physical signals, and UE3 is configured for receiving control information and user data via several DL physical channels, as well as for transmitting several physical signals. DL physical channels correspond to resource elements (REs) that carry information transmitted from higher layers, and DL physical signals correspond to REs used in the physical layer that do not carry information transmitted from higher layers.

[0071] 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 PDSCH's capacity on a time and frequency basis. The PDSCH can carry various data items, including, for example, user data, UE-specific upper-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 uplink data transmissions on the physical uplink shared channel (PUSCH). The PBCH provides the Master Information Block (MIB) to the UE3. The PBCH also works in conjunction with the PDCCH to support time and frequency synchronization, which helps with cell acquisition, selection, and re-selection. UE3 may receive a Synchronization Signal Block (SSB), and UE3 may assume that the opportunities to receive PBCH, primary synchronization signal (PSS), and secondary synchronization signal (SSS) are within a consecutive symbol, forming an SS / PBCH block. Base station 5 may transmit several synchronization signal (SS) blocks corresponding to different DL beams. The total number of SS blocks may be limited, for example, to a duration of 5 ms as an SS burst. The period of SSB transmission may be indicated to the UE using any appropriate signaling (e.g., per serving cell using ssb-periodicityServingCell). The period value of the SSB may be, for example, 20 ms or more. In the case of initial cell selection, UE3 may be configured to assume that SS bursts occur with a period of 2 frames.UE3 can also provide instructions on which SSBs to send within a 5ms duration (for example, using ssb-PositionsInBurst).

[0072] DL physical signals may include, for example, a reference signal (RS) and a synchronization signal (SS). The reference signal (sometimes also known as a pilot signal) is a signal with a predefined special waveform known to both the UE3 and the base station 5. Reference signals may include, for example, a cell-specific reference signal, a UE-specific reference signal (UE-RS), a downlink demodulation signal (DMRS), and a channel state information reference signal (CSI-RS).

[0073] Similarly, UE3 is configured to transmit control information and user data via several uplink (UL) physical channels corresponding to REs that carry information transmitted from higher layers, as well as UL physical signals used in the physical layer and corresponding to REs that do not carry information transmitted from higher layers. Base station 5 is configured to receive control information and user data via several UL physical channels corresponding to REs that carry information transmitted from higher layers, as well as UL physical signals used in the physical layer and corresponding to REs that do not carry information transmitted from higher layers. Physical channels may include, for example, PUSCH, physical uplink control channel (PUCCH), and / or physical random access channel (PRACH). UL physical signals may include, for example, demodulation reference signal (DMRS) for UL control / data signals, and / or sounding reference signal (SRS) used for UL channel measurement.

[0074] Referring to Figure 6, which shows a typical frame structure that may be used in telecommunications system 1, the base station 5 and UE3 of telecommunications system 1 communicate with each other in the time domain using resources organized into frames of length 10 ms. Each frame contains 10 equally sized subframes of length 1 ms. Each subframe is divided into one or more slots containing 14 Orthogonal frequency-division multiplexing (OFDM) symbols of equal length.

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

[0076] Typical slot configuration Referring to Figures 7 and 8, base station 5 appropriately configures the use of slots within each cell 9 operating on the TDD carrier.

[0077] As can be seen in Figure 7, a simplified sequence diagram showing different slot configuration procedures (S710, S714, S718) that can be used in communication system 1, base station 5 can use several different procedures to configure slot usage in each cell 9 operating on a TDD carrier.

[0078] As seen in procedure S710, for example, base station 5 of communication system 1 is configured to provide each cell 9 operating on a TDD carrier with its own common (or "cell-specific") slot configuration. This common slot configuration can be provided to all UE3s in a cell using system information (for example, in the tdd-UL-DL-ConfigurationCommon information element (IE) of system information block type 1 (SIB1)) as shown in S710a. This common slot configuration can also be provided to a specific UE3 in a cell using dedicated (for example, radio resource control (RRC)) signaling (for example, in the tdd-UL-DL-ConfigurationCommon IE of an RRC message such as an RRC reconfiguration message) as shown in S710b. Thus, upon receiving the common slot configuration, UE3 can set up a common slot format configuration slot by slot across several slots (as seen in S712).

[0079] As can be seen in Figure 8, which shows an example of a slot configuration set up according to the procedure in Figure 7, slots can be configured as downlink-only slots, uplink-only slots, or unassigned or "flexible" slots (which may be downlink or uplink).

[0080] The common slot configuration is defined by several parameters provided by base station 5 as part of the common UL / DL configuration. These parameters include the slot configuration period (e.g., configured by dl-UL-TransmissionPeriodicity IE), the number of slots having only downlink symbols (e.g., configured by nrofDownlinkSlots IE), the number of downlink symbols (e.g., configured by nrofDownlinkSymbols IE), the number of slots having only uplink symbols (e.g., configured by nrofUplinkSlots IE), and the number of uplink symbols (e.g., configured by nrofUplinkSymbols IE). As seen in Figure 8, these effectively constitute a repeating pattern of slot types (repeats in 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 begins with a DL group containing a defined number of DL-only slots followed by a defined number of DL-only symbols in the next slot. The repeating pattern ends in a UL group containing a defined number of UL-only symbols in a preceding slot, followed by a defined number of preceding UL-only slots. Flexible symbols and slots are between DL groups of DL-only slots and symbols and UL groups of UL-only slots and symbols.

[0081] Figure 9 shows a further example in which two TDD patterns are constructed (for example, using the procedure in Figure 7). The first pattern (Pattern 1) has a first period P1, followed by a second pattern having a second period P2. The combined period of the TDD construction is the sum of the first and second periods, P1 + P2. In other words, for each cycle, the first TDD pattern is used for the first duration of P1, and the second TDD pattern is used for the subsequent duration of P2 (resulting in a total periodicity P3 equal to P1 + P2 for the entire sequence). It will be understood that the first period P1 does not necessarily have to be equal to the second period P2.

[0082] As seen in procedure S714, the base station 5 of the communication system 1 is also configured to provide a dedicated (or "UE-specific") slot configuration for a particular UE3, if necessary. This dedicated slot configuration can be provided to a particular UE3 in a cell (for example, in the tdd-UL-DL-ConfigurationDedicated IE of an RRC message such as an RRC reconfiguration message) using dedicated (e.g., radio resource control (RRC)) signaling (as shown in S715). Various cases when a UE3 is provided with a dedicated slot configuration in addition to a common slot configuration correspondence I will explain the method in more detail later.

[0083] A dedicated configuration, if provided, includes individual slot-specific configurations (e.g., using slotSpecificConfigurationsToAddModList IE), each slot configuration containing information that identifies a particular slot within the slot configuration period defined by the common slot configuration (e.g., slotindex IE), and information that defines the symbol structure (e.g., symbols IE). The information defining the symbol structure provides the orientation (downlink or uplink) of the symbols within the particular slot being configured. Information defining the symbol structure may, for example, indicate that all symbols in a particular slot are used for downlinks (for example, by setting symbols IE to "allDownlink"), or indicate that all symbols in a particular slot are used for uplinks (for example, by setting symbols IE to "allUplink"), or explicitly indicate how many symbols are assigned to downlinks and uplinks at the beginning and end of a particular slot, respectively (for example, nrofDownlinkSymbols IE may indicate the number of consecutive downlink symbols at the beginning of the slot identified by the slot index, and nrofUplinkSymbols IE may indicate the number of consecutive uplink symbols at the end of the slot identified by the slot index).

[0084] Therefore, UE3 can configure a dedicated slot format for each slot across several slots (as seen in S716).

[0085] Therefore, UE3 treats symbols in slots designated as downlinks by a common slot configuration or a dedicated slot configuration as available for reception. Similarly, UE3 treats symbols in slots designated as uplinks by a common slot configuration or a dedicated slot configuration as available for transmission.

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

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

[0088] An index for one or more slot format indicators (SFIs) is provided within the DCI payload of one or more UE3s. 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"), to allow one or more UE3s in the group to address and decode the DCI. The same RNTI is assigned to one or more UEs in the group. Each UE3 in the group is configured to extract its own SFI index based on the location of the SFI index in the DCI payload (this location may be, for example, configured by UE-specific RRC signaling). The RRC configuration may also be, for example, by an RRC message that carries a PDCCH serving cell configuration IE having a slot format indicator (SFI) IE that provides an SFI-RNTI for a particular serving cell (identified by a serving cell ID, e.g., servingCellId IE), defines one or more slot format combinations (e.g., slotFormatCombinations IE), and specifies the starting position (bits) in the DCI of the SFI index applicable to the configured UE (e.g., positionInDCI IE).

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

[0090] Therefore, for any slot shown as flexible in UE3 through both common and dedicated slot configurations, DCI can be used to dynamically configure the downlink symbols, uplink symbols, and / or flexible symbols within that slot (as seen in the example in Figure 8). Therefore, UE3 can set a dynamic slot format configuration for each slot across several slots (as seen in the S720).

[0091] Bandwidth Part (BWP) In communication system 1, the cell bandwidth can be divided into multiple bandwidth parts (BWPs), each containing a set of consecutive RBs, each starting in a common resource block (RB) and having 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 slot configuration (e.g., common or dedicated) is common to each configured BWP.

[0092] Therefore, the UE3 and base station 5 of communication system 1 are configured to operate using BWPs. Base station 5 can configure at least one downlink (DL) BWP (e.g., initial DL BWP) for each serving cell of UE3. Base station 5 may configure UE3 with up to a maximum number (typically 4) of DL BWPs, where only one DL BWP is active at a given time. UE3 is not expected to receive PDSCH, PDCCH, or CSI-RS outside of the active bandwidth portion (except for radio resource management (RRM)). If the serving cell is configured uplink (UL), base station 5 can configure at least one UL BWP (e.g., initial UL BWP). Base station 5 may configure UE3 with up to a maximum number (typically 4) of UL BWPs, where only one UL BWP is active at a given time. UE3 does not transmit PUSCH or PUCCH outside of the active bandwidth portion. In the active cell, UE3 does not transmit SRS outside of the active bandwidth portion. It will be understood that the slot format indicator (e.g., SFI index field value) of the Dynamic Slot Configuration DCI format may indicate to UE3 the slot format of each slot within several slots in each DL BWP or each UL BWP.

[0093] The BWP identifier or index (BWP-ID) is used to refer to a BWP (independently in UL and DL). Therefore, various radio resource control (RRC) configuration procedures can use the BWP-ID to associate those procedures with a specific BWP.

[0094] In paired spectrum (FDD), DL BWP and UL BWP are configured separately, but in non-paired spectrum (TDD), DL BWP is effectively linked (paired) with UL BWP, and the paired DL BWP and UL BWP share the same BWP-ID and center frequency (although their bandwidths may differ).

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

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

[0097] The initial DL BWP and UL BWP are used for initial access, at least before the RRC connection is established. The initial BWP has a BWP identifier (or "index") of 0 and is therefore known as BWP#0. Before receiving system information that defines the UE's initial DL BWP, each UE3's DL BWP has a control resource set (CORESET) defined by the master information block (MIB) (or possibly dedicated RRC signaling), with a frequency range and numerology corresponding to, for example, CORESET#0. The CORESET is used to carry downlink control information (DCI) that is sent via the PDCCH to schedule the system information block.

[0098] After receiving system information (e.g., SIB1), UE3 configures the initial DL BWP and initial UL BWP using the BWP configuration defined by that system information. The configured initial UL BWP is then used to initiate the random access procedure for setting up the RRC connection. Base station 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.

[0099] For each DL BWP in the set of DL BWPs for a primary cell (PCell), UE3 can be configured with a CORESET for any type of common search space (CSS) set (sometimes called cell-specific search space (CSS)) and a CORESET for a UE-specific search space (USS) set. For each UL BWP in the set of UL BWPs for a PCell or PUCCH secondary cell, UE3 is configured with a resource set for PUCCH transmissions.

[0100] UE3 is configured to switch its active BWP between its configured BWPs as needed. For example, switching in UE3 may be initiated by receiving a scheduling DCI, by the expiration of an inactivity timer (e.g., BWPInactivityTimer), and / or by the start of a random access procedure.

[0101] PDCCH configuration Each UE3 is configured to monitor a set of PDCCH candidates in one or more CORESETs on the currently active DL BWP, according to its corresponding search space set. This monitoring involves decoding each PDCCH candidate according to the corresponding monitored DCI format.

[0102] Each set of PDCCH candidates monitored by UE3 is defined with respect to a PDCCH search space set, which can be a CSS set or a USS set, as described above. For example, a given UE3 may monitor PDCCH candidates in one or more of the following search space sets: A set of PDCCH CSSs associated with the transmission of a PDCCH for a system information (SI) message (e.g., SIB1 carrying remaining minimum system information ("RMSI")). Such a CSS may be called a Type 0 PDCCH CSS and may be configured on a PCell by an appropriate search space configuration IE for a DCI format having a CRC scrambled by the system information RNTI (SI-RNTI) (e.g., in the so-called "pdcch-ConfigSIB1" IE provided in the MIB, or in the so-called "searchSpaceSIB1" or "searchSpaceZero" within the "PDCCH-ConfigCommon" IE for an appropriate RRC message). A PDCCH CSS set related to the transmission of PDCCH for other system information (e.g., carried by other SIBs). Such a CSS may be called a Type 0A PDCCH CSS set and may be configured on PCell by a suitable search space configuration IE for DCI format having a CRC scrambled by SI-RNTI (e.g., within the so-called "searchSpaceOtherSystemInformation" IE, provided in the "PDCCH-ConfigCommon" IE of the appropriate RRC message). A PDCCH CSS set associated with a random access procedure. Such a CSS may be called a Type 1 PDCCH CSS set and may consist of a suitable search space configuration IE for a DCI format having a CRC scrambled by an appropriate RNTI on the PCell (e.g., random access RNTI (RA-RNTI), random-access response message (RAR / MsgB)RNTI (MsgB-RNTI), or temporary cell RNTI (TC-RNTI). The search space configuration IE may be, for example, the so-called "ra-SearchSpace" IE provided in the "PDCCH-ConfigCommon" IE of an appropriate RRC message. A PDCCH CSS set related to paging. Such CSS may be called a Type 2 PDCCH CSS set and may consist of a suitable search space configuration IE for DCI format having a CRC scrambled by the appropriate RNTI (e.g., paging RNTI (P-RNTI)) on PCell. The search space configuration IE may be the so-called "pagingSearchSpace" IE, provided, for example, in the "PDCCH-ConfigCommon" IE of the appropriate RRC message. A set of PDCCH CSSs related to other procedures (e.g., scheduling, power control). Such CSSs may be called a Type 3 PDCCH CSS set and may consist of a suitable search space configuration IE for DCI format having a CRC scrambled by a suitable RNTI on a SCell or PCell. The RNTI may be, for example, an interruption RNTI (INT-RNTI), SFI-RNTI, PUSCH power control RNTI (TPC-PUSCH-RNTI), PUCCH power control RNTI (TPC-PUCCH-RNTI), SRS trigger and power control RNTI (TPC-SRS-RNTI), cancellation indication RNTI (CI-RNTI), cell RNTI (C-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), one or more configured scheduling CS-RNTIs, or power saving RNTIs (PS-RNTIs). The search space configuration IE may be, for example, the so-called "SearchSpace" IE provided in the "PDCCH-Config" IE of the appropriate RRC message. A set of USS for DCI format having a CRC scrambled by an appropriate RNTI. The RNTI may be, for example, C-RNTI, MCS-C-RNTI, semi-persistent (SP) channel state information (CSI)RNTI (SP-CSI-RNTI), and / or one or more CS-RNTIs. The search space configuration IE may be a so-called "SearchSpace" IE, for example, provided in the "PDCCH-Config" IE of an appropriate RRC message.

[0103] For each exploration space set, UE3 is provided with information to configure the association between the exploration space set and the CORESET, the PDCCH monitoring period and PDCCH monitoring offset, the PDCCH monitoring pattern in the slot, an indication that the exploration space set is either a CSS set or a USS, and / or one or more DCI formats to monitor.

[0104] It will be understood that the CSS set is expected to be used by both older "legacy" UEs not configured for SBFD communication and newer UEs configured to support SBFD communication, at least to monitor broadcast channels.

[0105] Here, we will refer to Figure 10, a simplified time-frequency diagram illustrating an example of a non-interleaved CORESET design, to explain in more detail how a CORESET can be constructed.

[0106] Each CORESET can be described in terms of resource grouping at different levels of granularity, as follows: A resource element (RE) is the smallest unit within a 5G NR resource grid, consisting of one subcarrier in the frequency domain and one symbol in the time domain. A resource element group (REG) containing a single RB in the frequency domain (each RB contains 12 subcarriers / REs in the frequency domain) and one symbol in the time domain. A REG bundle containing multiple REGs. The bundle size is variable (in terms of the number of REGs) (typically specified by a parameter shown in RRC signaling using the appropriate IE (e.g., "reg-bundle-size")). A control channel element (CCE) containing several REGs (six in current 5G systems, but hypothetically variable) in units of one or more REG bundles (depending on the REG bundle size), The aggregation level indicating the number of CCEs assigned to PDCCH. Currently, NR supports both distributed and local resource allocation for DCI within a CORESET. Distributed resource allocation for DCI can be achieved by configuring interleaved CCE-to-REG mapping for each CORESET, while local resource allocation for DCI (as shown in Figure 10) can be achieved by configuring non-interleaved CCE-to-REG mapping for each CORESET.

[0107] In the case of non-interleaved CCE-to-REG mapping, all CCEs in a DCI with a given aggregation level L are mapped to consecutive REG bundles in the CORESET. In the case of interleaved CCE-to-REG mapping, the REG bundles constituting the CCEs for the PDCCH are distributed in the frequency domain on a per-REG bundle basis. To support this, block interleaving is used, where the interleaving spans all REGs present in the CORESET.

[0108] Therefore, a given DCI having a specific aggregation level L may contain L consecutively numbered CCEs, where the CCEs map to several REGs (which may be grouped into discontinuous REG bundles in the case of interleaving) within a given CORESET.

[0109] As mentioned above, a serving cell can have up to four BWPs. Each of these BWPs can currently have up to three CORESETs. Base station 5 provides UE3 with information to configure one or more of the CORESETs.

[0110] This configuration information typically includes information to identify, for example, the number of consecutive symbols representing the duration of the CORESET (e.g., 1, 2, or 3). The configuration information also typically includes information to identify a set of frequency domain resources (e.g., a set of RBs) in the form of, for example, an appropriate frequency domain resource IE (e.g., frequencyDomainResources IE) that defines the resources. The frequency domain resource IE may be in the form of, for example, a bitmap, where each bit corresponds to a group of frequency resources (e.g., a group of six RBs), and the grouping starts with an initial physical frequency resource (e.g., a physical RB (PRB0)) that is entirely contained within the BWP in which the corresponding CORESET is constructed. The term PRB will generally be understood to refer to RBs that are indexed in frequency order in the frequency domain. This is in contrast to virtual RBs (VRBs) that may (but do not necessarily) correspond to physical frequency resources (subcarriers, PRBs, groups thereof, etc.) that are not in frequency order when sorted numerically.

[0111] The configuration information also typically includes CCE-to-REG mapping information for use in identifying each CCE, and therefore each PDCCH candidate, which is formed by the resources. The CCE-to-REG mapping information typically includes information defining the REG bundle size (e.g., "reg-bundle-size") and, if interleaving is used, information identifying the interleaver size and potentially the shift index (which may be physical cell identification information).

[0112] The configuration information that defines a CORESET is typically provided using RRC signaling. However, a CORESET with index 0 (CORESET#0) is a special CORESET configured using a 4-bit information element within the MIB.

[0113] Table 2 below shows an example of interleaved CCE versus REG bundle mapping. The mapping shown is for a CORESET of 48 PRBs, where the PRBs are continuously indexed (from 0 to 47) in the frequency domain. The REG bundle size is 6 REGs (PRBs), the CORESET duration is 1 symbol in the time domain, the interleaver size is 2, and the shift index is 160.

[0114] [Table 2]

[0115] In this example, we can see that all even-numbered CCEs map to the next REG bundle as the frequency increases from the bottom to the center of the available 48RB CORESET frequency range. All odd-numbered CCEs map to the next REG bundle as the frequency increases from the center to the top of the available 48RB CORESET frequency range.

[0116] Therefore, in the case of interleaved CCE vs. REG mapping, the frequency resources of each PDCCH candidate are found to be distributed (essentially randomly) across the CORESET bandwidth. This presents a potential challenge in SBFD implementations where UL communication from one UE3 may interfere with DCI communication within a PDCCH for another UE3.

[0117] PDSCH / PUSCH Resource Allocation Resource allocation for communication on PDSCH or PUSCH in telecommunications system 1 can be based on one of two types of resource allocation schemes.

[0118] In the first type of resource allocation (called Type-0), the allocation is indicated by resource block allocation information, which includes a bitmap showing one or more resource block groups (RBGs) allocated to a scheduled UE. Each RBG is a set of consecutive virtual resource blocks (VRBs). The size of an RBG (number of resource blocks) is defined by a higher-level RBG size parameter (e.g., "rbg-Size") and the size of the BWP to which the allocation is related. The RBG size parameter essentially indicates one of several possible RBG size configurations, and the actual RBG size of each RBG size configuration depends on the BWP bandwidth. For example, with a 36RB bandwidth, the RBG size of the first RBG size configuration could be 2RB, while the RBG size of the second RBG size configuration could be 4RB. In contrast, with a 144RB bandwidth, the RBG size of the first RBG size configuration could be 8RB, while the RBG size of the second RBG size configuration could be 16RB. Therefore, each RBG of a given BWP can be addressed via the bitmap without needing to increase the bitmap size for larger BWPs.

[0119] In the second type of resource allocation (called Type-1), the allocation is indicated by resource block allocation information that shows a set of consecutively allocated non-interleaved or interleaved VRBs within the active BWP. For non-interleaved VRBs, a VRB with index n is mapped to a corresponding PRB with the same index n. For interleaved VRBs, the VRB-to-PRB mapping involves bundling the (both virtual and physical) RBs into an RB bundle (RBB) in ascending order of RB index and RBB index. A virtual RBB (VRBB) is mapped to a physical RBB (PRBB) based on block interleaving, such that a given VRBB index may not be the same as the corresponding PRBB index. Thus, when a set of consecutive VRBBs is allocated to UE3, the corresponding PRBBs may not have consecutive frequencies and may instead be distributed at different (separated) locations within the bandwidth of the corresponding BWP.

[0120] Dynamic switching between different types of resource allocation is made possible by instructions contained within a DCI that have the appropriate DCI format (e.g., DCI format 0_1 ​​(for PUSCH), DCI format 1_1 (for PDSCH), "compact" DCI format 0_2 (for PUSCH), or "compact" DCI format 1_2 (for PDSCH)).

[0121] In the case of multi-slot PUSCH / PDSCH, it will be understood that the frequency domain resource allocation remains the same for all slots. However, if frequency hopping is used (as will be explained in more detail later), the frequency resources for adjacent slots may still differ.

[0122] Therefore, in the second type (Type-1) resource allocation (with interleaving), it can be seen that frequency resources for PDSCH / PUSCH can be distributed (essentially randomly) across the BWP bandwidth. This presents a potential challenge in SBFD implementations where UL / DL communication from one UE3 may interfere with PDSCH / PUSCH communication from another UE3.

[0123] Frequency hopping In the case of communication over PUSCH, the telecommunications system 1 can configure one of several different frequency hopping modes.

[0124] The first hopping mode includes, for example, in-slot frequency hopping, in which frequency hopping can occur within a slot. In-slot frequency hopping is applicable to both single-slot and multi-slot PUSCH transmissions.

[0125] The first hopping mode includes, for example, inter-slot frequency hopping, where frequency hopping can occur between slots. Inter-slot frequency hopping is applicable to multi-slot push transmissions.

[0126] For hopping within a slot, the starting RB for each hop is given as follows:

number

number

[0127] Regarding slot hopping, slots

number

number

number

number

[0128] In the second type of resource allocation (e.g., Type-1), UE3 performs PUSCH frequency hopping if the frequency hopping field of the corresponding detected DCI format (or random access response UL grant) is set to 1. The frequency offset may also be configured by a higher-layer parameter (e.g., the frequencyHoppingOffsetLists parameter), and one of the offsets configured in the higher layer may be indicated in the UL grant.

[0129] Full duplex service is provided. The UE3 and base station 5 of communication system 1 are configured to provide full duplex (FD) communication over a TDD carrier. Specifically, the UE3 and base station 5 of communication system 1 are configured to facilitate subband non-overlapping FD (SBFD) communication.

[0130] For example, as seen in Figure 11, a simplified time-frequency diagram illustrating an example of a full-duplex configuration that may be used in communication system 1, different UE-specific slot configurations allow slots within the cell bandwidth to be configured as effective FD slots, with one slot configured as an uplink slot for one UE and the same slot as a downlink slot for another UE (or vice versa). Thus, UL communication from one UE3 within the cell bandwidth can be performed in parallel with DL communication to another UE3. Although not specifically shown, it will be understood that parallel UL / DL communication can be configured at the symbol level as well as the slot level.

[0131] It will be understood that base station 5 is configured to schedule frequency resources in any slot configured as an FD slot to ensure that the frequency resources scheduled for UL communication by one UE3 are part of a different subband than the frequency resources scheduled for DL ​​communication to another UE3. Thus, base station 5 can perform subband non-overlapping FD communication, while the UE3s perform half-duplex communication.

[0132] Therefore, base station 5 may configure one or more of the TDD carrier slots (and / or symbols) as FD slots (and / or symbols), more specifically as SBFD slots (and / or symbols) when subband non-overlapping full duplex (SBFD) is used in full-duplex operation. For convenience, from the base station's perspective, a slot / symbol containing both the UL subband and DL subband is generally referred to as an "SBFD" slot / symbol, or a slot / symbol with configured UL subband / DL subband. Other slots / symbols containing only single transmit direction (UL or DL) communications are generally referred to as legacy (UL or DL) slots / symbols or non-SBFD (UL or DL) slots / symbols.

[0133] From the UE's perspective, it will be understood that an SBFD slot or symbol may appear to be a legacy UL, DL, or flexible symbol because UE3 is operating using half-duplex on a TDD carrier. That said, UE3 may be implicitly or explicitly notified of an FD / SBFD slot / symbol to allow UE3 to assist in interference avoidance / mitigation. For example, if UE3 can identify an FD / SBFD slot / symbol, UE3 can contribute to implementing a proper frequency gap between frequency resources used by that UE3 (e.g., for UL or DL) and frequency resources used by another UE3 (e.g., for DL ​​or UL), and may avoid, reconfigure, and / or apply updated resources with respect to a particular transmit / receive (e.g., for quasi-static transmits such as SPS).

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

[0135] It will be understood that various variations exist for the implementation of SBFD, and that communication system 1 can be configured to provide support for any suitable SBFD scheme. Such schemes may include, for example, inter-BWP full-duplex and / or intra-BWP full-duplex.

[0136] For example, referring to Figure 12, a simplified time-frequency diagram illustrating an example of a full-duplex BWP-to-BWP type, BWP-to-BWP full-duplex involves parallel UL and DL transmissions across different BWPs, where a specific slot in one BWP may be configured as an uplink slot, while a corresponding (i.e., identically timingd) slot in another BWP may be configured as a downlink slot (or vice versa). Thus, a UL from one UE3 in one BWP can occur in parallel with DL communication to another UE3 in another BWP.

[0137] On the other hand, referring to Figure 13, a simplified time-frequency diagram showing an example of a full-duplex BWP-type configuration, full-duplex within a BWP includes parallel UL and DL transmissions within the same BWP. In the example shown in Figure 13, the UL subband is effectively inserted into a slot / symbol configured as a (legacy) DL or flexible slot / symbol in the BWP. Specifically, each time resource in the BWP is configured as DL, UL, or flexible slot / symbol (for example, using TDD configuration techniques as described with reference to Figures 4 and 5). The UL subband (e.g., a continuous set of UL frequency resources) is then configured within the BWP so that one or more subsets of DL or flexible slot / symbol effectively form a slot / symbol consisting of the UL subband and one or two DL subbands. The configuration of the UL subband can be achieved in any suitable way, for example, by quasi-static and / or dynamic configurations. Between the UL subband and each DL subband, a guard band (frequency gap) may be configured where no transmission is performed, thereby helping to avoid interference. The base station 5 can then schedule UL transmissions in the UL subband and DL transmissions in one or two DL subbands, as needed. Figure 13 shows that the UL subband is inserted into the downlink or flexible slot / symbol, but it will be understood that a similar mechanism may be used to achieve SBFD by inserting DL subbands within the UL or flexible slot / symbol.

[0138] Several procedures that may be implemented in communication system 1 to provide the corresponding benefits are described, but it will be understood that it is not necessary to implement all procedures to achieve beneficial results. Specifically, any one of the procedures may be implemented independently of the others. That being said, many of the procedures are not mutually exclusive and can be implemented together if it is technically appropriate to do so. UL subband and SSB / Type-0 PDDCH / broadcast channels

[0139] The inventors recognized the need for an improved method to address situations where both SSB and SBFD are provided to the UE3. Reception of SSB / Type-0 PDCCH / broadcast channels may be prioritized by the UE, and therefore, the configuration of the UL subband must be carefully considered to achieve full utilization of SBFD while ensuring that there is no conflict with SSB.

[0140] UL subband configuration Figure 14 shows an example where the SSB is configured with a 20ms period and the TDD pattern is configured with a 5ms period. The resources allocated to the UL subband and the configuration of the SSB / Type-0 PDCCH are controlled by the network, which ensures that the UL subband and SSB / Type-0 PDCCH do not overlap in the time domain. The SSB period may be, for example, 20ms or 40ms, and the SSB window (duration) is 5ms. In contrast, the TDD period can be up to 10ms (e.g., 5ms). In the example shown in Figure 14, the TDD has a duration of 5ms, of which 4ms is used for DL ​​and 1ms is used for UL. In this example, the SSB occupies the first 3ms of the TDD pattern, and therefore the UL subband is not configured for the first 3ms of the TDD pattern to avoid conflict with the SSB. If the UL subband overlaps with the SSB, the UE3 cannot use the UL subband if it is configured for half-duplex operation and receiving the SSB or broadcast signal has a higher priority. Since the period of a TDD pattern (5ms) is shorter than the period of an SSB (20ms), the corresponding SSB is not transmitted during many TDD opportunities. However, since only one TDD pattern is used for all TDD opportunities, the UL subband is not configured during the first 3ms of the TDD pattern, even when there is no corresponding SSB to avoid conflict. Thus, there is a problem that SBFD is not fully utilized during periods when there is no SSB transmission. In the example in Figure 14, only 25% of the symbols available for SBFD are utilized during TDD opportunities without SSB. Although Figure 14 is illustrated with reference to SSB, it will be understood that this problem also occurs with any other Type-0 PDCCH or broadcast transmission that should be preferred for reception by UE3.

[0141] Here, an improved method for scheduling the UL subband is described with reference to Figure 15, where the UL subband period is advantageously different from the TDD period. In this example, the UL subband period is the same as the SSB period. Beneficially, as shown in Figure 15, this allows SBFD to be configured so that the UL subband does not overlap with SSB, while improving the utilization of available resources in TDD opportunities where there is no overlapping SSB in the time domain. In the example in Figure 14, only 25% of the symbols available for SBFD are utilized in TDD opportunities without SSB, whereas in the improved configuration in Figure 15, all available symbols are utilized for SBFD in TDD opportunities without SSB, improving the efficiency of communication between UE3 and base station 5. The configuration for the UL subband can be indicated to UE3 using any appropriate signaling or transmission. For example, the network may use RRC signaling to indicate the slots / symbols in which the UL subband occurs.

[0142] Figure 16 shows a further example in which two SBFD patterns are used. In this example, the first SBFD pattern (SBFD pattern 1) is used for TDD opportunities that may overlap with SSB, and the second SBFD pattern (SBFD pattern 2) is used for TDD opportunities that do not overlap with SSB. The second SBFD pattern contains more UL subband symbols than the first SBFD pattern, increasing the use of SBFD in TDD opportunities that do not overlap with SSB, while the configuration of the first SBFD pattern ensures that there is no competition between UL subband occurrences and SSB. The first and second SBFD patterns do not necessarily have to have the same duration, which can be particularly useful when more than one TDD pattern is used (for example, in the example shown in Figure 9). The two SBFD patterns can be associated with (e.g., mapped) their respective TDD patterns (e.g., the first and second TDD patterns shown in tdd-UL-DL-ConfigurationCommon) such that each SBFD pattern has the same duration as the associated TDD pattern.

[0143] Figures 14 to 16 illustrate the relationship between the UL subband in the time domain, the TDD pattern, and SSB, and it will be understood that any suitable configuration for the UL subband in the frequency domain (e.g., one or more of the configurations shown in Figures 1 to 4) can be used.

[0144] UE Procedure Now, referring to Figure 17, we will explain how the UL subband overlaps with SSB, but how competition between the UL subband and SSB is still avoided. As shown in the figure, in this example, the UL subband is configured to span the duration of the DL transmission, achieving full utilization of SBFD in TDD opportunities that do not overlap with SSB. In this example, in TDD opportunities that overlap with SSB, UE3 is configured to determine that there is overlap between the UL subband and SSB, and that the overlapping UL subband should not be used (e.g., the overlapping UL subband is discarded by UE3). UE3 may determine that the UL subband overlaps with SSB (or any other suitable broadcast channel or reference signal) if a subset of the symbols for the UL subband is the same as those used for SSB, or if the UL subband start symbol is less than a threshold duration after the end of the SSB transmission. The threshold duration may be pre-configured by UE3 or determined based on, for example, a UE timing advance value. The threshold duration may be determined by UE3 or indicated to UE3 by the network (via base station 5).

[0145] If UE3 determines that the UL subband overlaps with SSB, UE3 may decide to discard any UL transmits or UL grants associated with the UL subband. UE3 may also decide not to monitor any CORESET / DCI associated with the UL subband.

[0146] UE3 can be configured to discard only the portion of the UL subband that overlaps with SSB in the time domain (e.g., one or more symbols of the UL subband) (e.g., not to be used for uplink transmission) and to use the non-overlapping portion of that UL subband (e.g., symbols that do not overlap with SSB) for UL transmission.

[0147] UE3 can be configured to discard only the UL subbands that overlap with a particular subset of SSBs when those subbands overlap with SSBs. The subset of SSBs may be one or more SSBs currently selected or camped on by UE3, or it may be SSBs transmitted in close proximity to, for example, the SSBs currently selected or camped on by UE3.

[0148] UE3 can be configured to discard only the UL subbands that overlap with the reference signal when the reference signal should be used for radio link monitoring ring or link recovery. UE3 may be configured to discard or utilize UL subbands that overlap with SSB based on the decision that UE3 should receive SSB (or other appropriate broadcast channel or reference signal). For example, if the UL subband overlaps with RMSI, but UE3 does not need to receive RMSI, UE3 may decide not to discard the UL subband and may use the UL subband for uplink transmission.

[0149] Advantageously, as shown in the example in Figure 17, SBFD is efficiently utilized while competition between the UL subband and SSB is beneficially avoided as a result of UE3 detection of overlap between the UL subband and SSB.

[0150] Common TDD configuration and dedicated TDD configuration Here, we describe an example where both a common TDD configuration and a dedicated TDD configuration are provided to UE3. For an example of how a common TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon IE) and a dedicated TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated IE) can be provided, see Figure 7 above.

[0151] The common TDD configuration provided in UE3 may provide UL subband time opportunities that may overlap with the flexible and DL slots / symbols configured by the common TDD configuration. However, in order to achieve a more efficient configuration in the time domain of the UL subband, the inventors have provided both a common TDD configuration and a dedicated TDD configuration to UE3. Process We realized that an improved method was needed.

[0152] In this example, if a slot / symbol is configured with a dedicated TDD configuration as a UL slot / symbol, and those UL slots / symbols include a UL subband configured with a common TDD configuration, UE3 is configured to discard (for example, treat as invalid) the UL subband for those slots / symbols.

[0153] Figure 18 shows an example where a common TDD configuration includes indications for UL subband opportunities, and a dedicated TDD configuration is also provided. The resulting UL subband configuration in the time domain is also shown. In this example, UE3 is configured to treat UL subband opportunities indicated in the common TDD configuration as valid UL subband opportunities (which UE3 can use for subband uplink transmissions) when the corresponding slots / symbols in the dedicated TDD configuration are indicated as DL or flexible slots / symbols. UE3 is configured to discard UL subbands when the corresponding slots / symbols in the dedicated TDD configuration are indicated as UL slots / symbols.

[0154] Figure 19 shows a modified example of the example in Figure 18, where the dedicated TDD configuration includes instructions for UL subband opportunities. Base station 5 provides UE3 with configuration instructions for UL subband time opportunities for slots / symbols configured as DL or flexible slots / symbols. In the example shown in Figure 19, for each TDD period, the dedicated TDD configuration includes instructions for time opportunities for the corresponding UL subband opportunities. As shown in the figure, if the dedicated TDD configuration indicates that slots / symbols are intended for use as DL slots / symbols and also indicates the UL subbands for those slots / symbols, UE3 is configured to use the indicated UL subbands (or treat the indicated UL subbands as valid). If the dedicated TDD configuration indicates that slots / symbols are intended for use as DL slots / symbols but does not indicate that those slots / symbols are for UL subbands, UE3 does not use the UL subbands for those slots / symbols. UE3 may be configured to discard (e.g., not use or treat as invalid) UL subband time opportunities shown in the common TDD configuration for slots / symbols shown as DL or flexible slots / symbols without UL subbands in the dedicated TDD configuration. Alternatively, UE3 may be configured not to discard UL subband time opportunities shown in the common TDD configuration if no UL subband time opportunity configuration is provided in the dedicated TDD configuration.

[0155] Advantageously, as shown in the examples in Figures 18 and 19, the UL subband opportunity can be configured efficiently and uniquely, even when both common and dedicated TDD configurations are provided, and the utilization of available slots / symbols for SBFD is high.

[0156] Transition between UL subband and UL-only slots When a transition occurs between a slot / symbol including a UL subband and a slot / symbol that is UL only, base station 5 may need to reconfigure its filters (e.g., analog filters) to account for the change in UL bandwidth. Figure 20 shows an example of when such retuning may occur on an interface with different UL bandwidths. This reconfiguration may result in interruptions to UL reception, which can negatively impact, for example, physical channel procedures. This is because, if a UL-only slot / symbol and a UL subband slot / symbol are adjacent, base station 5 may not receive UL transmissions during the resulting retuning for the new bandwidth. If UE3 uses similar filters for transmission and / or reception, a corresponding problem may occur in UE3. The inventors recognized the need for an improved method to handle transitions from UL-only slot / symbols to UL subband slot / symbols (and from UL subband slot / symbols to UL-only slot / symbols) in order to improve the efficiency and reliability of communications within the system.

[0157] In one example, base station 5 configures a time gap between a UL subband slot / symbol and a UL-only slot symbol where no UL transmission is scheduled. This time gap may also be called a guard period. Advantageously, base station 5 can perform filter reconfiguration during the guard period, reducing the risk that UE3 will transmit an uplink transmission to base station 5 while the base station is performing the reconfiguration. Base station 5 may provide UE3 with indication of the time gap through any appropriate transmission or signaling (e.g., RRC signaling). Alternatively, a time delay (guard period) may be pre-configured in UE3 for use in transitions from UL-only slot / symbol to UL subband slot / symbol (and from UL subband slot / symbol to UL-only slot / symbol). In a further alternative example, the time gap may be in the form of one or more flexible symbols configured by the base station in transitions from UL-only slot / symbol to UL subband slot / symbol (and / or from UL subband slot / symbol to UL-only slot / symbol). The time gap may be part of a symbol, one or more symbols, or a slot.

[0158] Limiting, preventing, or reducing UL transmissions during guard periods can be achieved in any appropriate way by any appropriate signaling between UE3 and base station 5. Base station 5 may provide UL configurations such that UL subbands are not configured / exist during guard periods. For example, if flexible symbols are used during guard periods, base station 5 may not configure UL subband opportunities within N flexible symbols placed before (or after) the start of UL slots / symbols where UL bandwidth changes occur. Alternatively, base station 5 may simply not schedule any UL transmissions within the time gap. In a further alternative, UE3 may perform rate matching / puncturing on UL transmissions or discard UL resources to avoid UL transmissions during guard periods. If discarding is performed, UE3 may discard only the portion of UL transmissions that overlap with guard periods if the UL transmissions partially overlap with guard periods. Alternatively, UE3 may discard entire UL transmissions if the UL transmissions partially overlap with guard periods.

[0159] Figure 21 shows an example where a guard period is provided from the start of the first UL-only symbol when a transition occurs from an UL subband slot / symbol to an UL-only slot / symbol, and from the start of the first UL subband symbol when a transition occurs from an UL-only slot / symbol to an UL subband slot / symbol.

[0160] Figure 22 shows an example where a guard period is provided at the end of the UL subband slot / symbol when a transition occurs from an UL subband slot / symbol to an UL-only slot / symbol, and at the end of the UL-only slot / symbol when a transition occurs from an UL-only slot / symbol to an UL subband slot symbol.

[0161] Figure 23 shows a particularly advantageous example in which a guard period is provided at the end of a UL subband slot / symbol when a transition occurs from a UL subband slot / symbol to a UL-only slot / symbol, and from the start of the first UL subband symbol when a transition occurs from a UL-only slot / symbol to a UL subband slot / symbol. This configuration is particularly beneficial because it reduces the waste of UL radio resources by providing a guard period at UL subband slot / symbols with relatively low bandwidth rather than at UL-only slot / symbols with relatively high bandwidth.

[0162] Examples in Figures 20 to 23 show guard bands in the frequency domain, but it should be understood that these do not necessarily need to be provided.

[0163] While the guard period is explained with reference to UL transmission, it will be understood that the same principles and methods apply to DL transmission as well. For example, the guard period can be implemented in the same way when a transition occurs between an UL subband slot and a DL-only slot.

[0164] User equipment Figure 24 is a schematic block diagram showing the main components of UE3 as shown in Figure 5.

[0165] As shown in the figure, UE3 has a transceiver circuit 31 that is capable of transmitting signals to and receiving signals from base station 5 via one or more antennas 33 (e.g., having one or more antenna elements). UE3 has a controller 37 that controls the operation of UE3. The controller 37 is associated with memory 39 and connected to the transceiver circuit 31. Although not necessarily required for its operation, UE3 may, of course, have all the usual functions of a conventional UE3 (e.g., a user interface 35 such as a touchscreen / keypad / microphone / speaker to enable direct user control and interaction with the user), which may be provided, as appropriate, by one or any combination of hardware, software, and firmware. The software may be pre-installed in memory 39 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD).

[0166] In this example, the controller 37 is configured to control the overall operation of the UE3 by program instructions or software instructions stored in memory 39. As shown in the figure, these software instructions include, among other things, the operating system 41 and the communication control module 43.

[0167] The communication control module 43 is operable to control communication between each of the UE3 and its service base stations 5 (as well as other communication devices connected to base stations 5, such as further UEs and / or core network nodes). The communication control module 43 is configured for the overall handling of uplink communication via associated uplink channels (e.g., via physical uplink control channel (PUCCH), random access channel (RACH), and / or physical uplink shared channel (PUSCH)), including both dynamic and quasi-static signaling (e.g., SRS). The communication control module 43 is also configured for the overall handling of downlink communication reception via associated downlink channels (e.g., via physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH)), including both dynamic and quasi-static signaling (e.g., CSI-RS). The communication control module 43 is responsible for, for example, determining where downlink control information should be monitored (e.g., the locations of CSS / USS, CORESET, and associated PDCCH candidates to be monitored), determining resources to be used by UE3 for transmitting / receiving UL / DL communications (including interleaved resources and resources subject to frequency hopping), managing frequency hopping on the UE side, determining how slots / symbols should be configured (e.g., for UL, DL, or SBFD communications), determining which one or more bandwidth portions are configured for UE3, determining how uplink transmissions should be encoded, and appropriately applying any SBFD-specific communication configurations. The communication control module 43 may be configured to control communications in any of the above-described ways (e.g., to perform UL subband transmissions).

[0168] base station Figure 25 is a schematic block diagram showing the main components of base station 5 for the communication system 1 shown in Figure 5. As shown, base station 5 has a transceiver circuit 51 for transmitting signals to and receiving signals from communication devices (such as UE3) via one or more antennas 53 (e.g., single or multi-panel antenna array / large antenna), and a core network interface 55 (including, for example, N2, N3, and other reference points / interfaces) for transmitting signals to and receiving signals from network nodes in the core network 7. Not shown, base station 5 may also be connected to other base stations via appropriate interfaces (e.g., so-called "Xn" interfaces in NR). Base station 5 has a controller 57 that controls the operation of base station 5. The controller 57 is associated with memory 59. Software may be pre-installed in memory 59 and / or downloaded, for example, via the communication network 1 or from a removable data storage device (RMD). In this example, the controller 57 is configured to control the overall operation of the base station 5 by program instructions or software instructions stored in memory 59.

[0169] As shown in the figure, these software instructions include, among other things, an operating system 61 and a communication control module 63.

[0170] The communication control module 63 is operable to control communication between the base station 5, the UE3, and other network entities connected to the base station 5. The communication control module 63 is configured to comprehensively control the reception and decoding of uplink communications over associated uplink channels (e.g., via the physical uplink control channel (PUCCH), random-access channel (RACH), and / or physical uplink shared channel (PUSCH)), including both dynamic and quasi-static signaling (e.g., SRS). The communication control module 63 is also configured to comprehensively handle the transmission of downlink communications over associated downlink channels (e.g., via the physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH)), including both dynamic and quasi-static signaling (e.g., CSI-RS). Where appropriate, the communication control module 63 is responsible for managing full-duplex (e.g., SBFD) communications, including the separation of UL and DL communications across different physical antenna elements. 6 3 is responsible for, for example, determining where UE3 should be configured to monitor downlink control information (e.g., the locations of CSS / USS, CORESET, and associated PDCCH candidates to monitor), determining resources to be scheduled for UE transmission / reception of UL / DL communications (including interleaved resources and resources subject to frequency hopping), managing frequency hopping on the base station side, appropriately configuring slots / symbols (e.g., for UL, DL, or SBFD communications), configuring one or more bandwidth portions for UE3, and providing relevant configuration signaling to UE3. 6 3 may be configured to control communications in any of the methods described above (for example, to control transmissions in a dedicated TDD configuration or a common TDD configuration).

[0171] Examples of modifications and alternatives As those skilled in the art will understand, several modifications and substitutions can be made to the embodiments described above while still benefiting from the embodiments of this disclosure.

[0172] For example, for clarity, terminology specific to cellular communication generations (2G, 3G, 4G, 5G, 6G, etc.) may be used to refer to a particular communication entity; however, it should be understood that the technical features described for a given entity are not limited to devices of that particular communication generation. Technical features can be implemented in any functionally equivalent communication entity, regardless of the differences in the terminology used to refer to them.

[0173] In the above description, the UE and base station are described as having several separate functional components or modules for the sake of ease of understanding. These modules may thus be provided for certain applications, for example, where an existing system is modified to implement the present disclosure, but in other applications, for example, in a system designed from the outset with the features of the present invention in mind, these modules may be incorporated into the operating system or the entire code, and therefore these modules may not be identifiable as separate entities.

[0174] In the embodiments described above, several software modules were explained. As those skilled in the art will understand, software modules may be provided in compiled or uncompiled form and may be supplied as signals over 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 because it facilitates updating the base station or UE to update the functions of the base station or UE.

[0175] Each controller may include, but is not limited to, any suitable form of processing circuitry, including, for example, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuits, internal memory / cache (programs and / or data), processing registers, communication buses (e.g., control buses, data buses, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers. Various other modifications are obvious to those skilled in the art and will not be described in further detail here.

[0176] A base station may comprise a "distributed" base station having a central unit "CU" and one or more individual distributed units (DU).

[0177] In this disclosure, User Equipment (or “UE,” “Mobile Station,” “Mobile Device,” or “Radio Device”) is an entity connected to a network via a radio interface.

[0178] Please note that this disclosure is not limited to dedicated communication devices, but can be applied to any device having communication functions as described in the following paragraphs.

[0179] The terms “User Equipment” or “UE,” “Mobile Station,” “Mobile Device,” and “Radio Device” (terms used by 3GPP) 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. The terms “Mobile Station” and “Mobile Device” will be understood to also include devices that remain stationary for extended periods.

[0180] UE may also be, for example, items of equipment for production or manufacturing and / or items of energy-related machinery (e.g., boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermoelectric 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 their application systems, tools, molds or dies, rolls, conveying equipment, elevators, material handling equipment, textile machinery, sewing machinery, printing and / or related machinery, paper conversion machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, machinery and / or equipment for agriculture, forestry and / or fisheries, 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 aforementioned equipment or machinery).

[0181] UE may be, for example, items of transport equipment (e.g., transport equipment such as railway cars, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other vessels, aircraft, rockets, satellites, drones, balloons, etc.).

[0182] UE may be, for example, an item of information and communication equipment (e.g., electronic computers and related equipment, communication and related equipment, electronic components and other information and communication equipment).

[0183] UE may include, for example, refrigerators, refrigerator applications, trading and / or service industry equipment items, vending machines, automated service machines, office machinery or equipment, home appliances and electronic equipment (e.g., home appliances such as audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related equipment, vacuum cleaners, etc.).

[0184] UE may be, for example, an electrical application system or device (e.g., an X-ray system, particle accelerator, radioisotope device, sound wave device, electromagnetic application device, power application device, etc.).

[0185] UE may include, for example, electronic lamps, lighting fixtures, measuring instruments, analyzers, testers, or measuring or detecting equipment (e.g., measuring or detecting equipment such as smoke detectors, human alarm sensors, motion sensors, wireless tags), watches or clocks, laboratory equipment, optical devices, medical equipment and / or systems, weapons, bladed weapons, hand tools, etc.

[0186] The UE may be, for example, a wireless-equipped personal digital assistant or related device (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 instrument).

[0187] The UE may be part of a device or system that uses various wired and / or wireless communication technologies to provide the following applications, services, and solutions related to the Internet of Things (IoT).

[0188] Internet of Things (IoT) devices (or "Things") may be equipped with appropriate electronics, software, sensors, network connectivity, etc., that enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may include automated devices that follow software instructions stored in internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices may also remain stationary and / or inactive for extended periods. IoT devices may be implemented as part of (generally) stationary equipment. IoT devices may also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0189] It will be understood that IoT technology can be implemented on any communication device that can connect to a communication network to send / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0190] It will be understood that IoT devices are sometimes called Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices. It will be understood 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 and is intended to show some examples of machine-type communication applications.

[0191] [Table 3]

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

[0193] Furthermore, the aforementioned UE categories are merely examples of applications of the technical concepts and exemplary embodiments described in this document. Needless to say, these technical concepts and embodiments are not limited to the aforementioned UEs and can be modified in various ways.

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

[0195] This application claims priority to UK Patent Application No. 2216500.5, filed on November 4, 2022, the disclosure thereof, which is incorporated herein by reference in its entirety.

[0196] For example, all or part of the exemplary embodiments disclosed above may be described as follows, but are not limited thereto. (Note 1) A method performed by an access network node to communicate with user equipment (UE), the method being: Sending first information to the UE that shows at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, Sending UL subband configuration information to the UE, including instructions for a first set of at least one time resources for the UL subband where at least one instance of a repeating pattern does not overlap with the repeating broadcast transmission in the time domain, and a second set of at least one time resources for the UL subband where at least one instance of a repeating pattern overlaps with the broadcast transmission in the time domain, The user equipment receives uplink transmissions on the uplink subband. Methods that include... (Note 2) Broadcast transmission is the method described in Appendix 1, including a synchronization signal block (SSB). (Note 3) UL subband configuration information includes instructions for iterative sets of time resources for the UL subband. The repetition period of the repetition set of time resources for the UL subband is the same as the repetition period of the repetition broadcast transmission, or The method described in any of the preceding appendices, wherein the repetition period of a repetitive broadcast transmission is an integer multiple of the repetition period of the repetition set of time resources for the UL subband. (Note 4) The method according to Appendix 3, wherein the repetition period of the repetition set of time resources for the UL subband is different from the duration of the instance of at least one repetition pattern of time resources for UL communication and time resources for DL ​​communication as indicated by the first information. (Note 5) The first piece of information shows multiple repeating patterns of time resources for UL communication and time resources for DL ​​communication. The method described in any of the preceding appendices, wherein the UL subband configuration information indicates multiple sets of time resources for the UL subband, and each set of time resources is intended for use with different repeating patterns from among multiple repeating patterns of time resources for UL communication and time resources for DL ​​communication. (Note 6) A method performed by user equipment (UE) to communicate with an access network node, the method being: Receiving first information from an access network node that shows at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, Receiving UL subband configuration information from an access network node, including instructions for a first set of at least one time resources for the UL subband where at least one instance of a repeating pattern does not overlap with the repeating broadcast transmission in the time domain, and a second set of at least one time resources for the UL subband where at least one instance of a repeating pattern overlaps with the broadcast transmission in the time domain, To send uplink transmissions to the access network node on the uplink subband. Methods that include... (Note 7) Broadcast transmission is the method described in Appendix 6, including a synchronization signal block (SSB). (Note 8) UL subband configuration information includes instructions for iterative sets of time resources for the UL subband. The repetition period of the repetition set of time resources for the UL subband is the same as the repetition period of the repetition broadcast transmission, or The method described in Appendix 6 or 7, wherein the repetition period of the repetitive broadcast transmission is an integer multiple of the repetition period of the repetition set of time resources for the UL subband. (Note 9) The method according to Appendix 8, wherein the repetition period of the repetition set of time resources for the UL subband is different from the duration of the instance of at least one repetition pattern of time resources for UL communication and time resources for DL ​​communication as indicated by the first information. (Note 10) The first piece of information shows multiple repeating patterns of time resources for UL communication and time resources for DL ​​communication. The UL subband configuration information refers to multiple sets of time resources for the UL subband, each set of time resources intended for use with different repeating patterns from multiple repeating patterns of time resources for UL communication and time resources for DL ​​communication, as described in any one of the items in Appendix 6 to 9. (Note 11) A method performed by user equipment (UE) to communicate with an access network node, the method being: Receiving first information from an access network node, which includes at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, and at least one set of time resources for the UL subband, Receiving broadcast transmissions from access network nodes, To determine whether at least one set of time resources for the UL subband overlaps at least partially with broadcast transmissions in the time domain, If it is determined that at least one set of time resources for the UL subband does not overlap with broadcast transmissions in the time domain at least partially, then the access network node will be instructed to use at least one set of time resources for the UL subband to send uplink transmissions on the UL subband, If it is determined that at least one time resource from at least one set of time resources for the UL subband overlaps in the time domain with a broadcast transmission, the access network node will decide not to send an uplink transmission on the UL subband using at least one time resource from at least one set of time resources for the UL subband. Methods that include... (Note 12) The method according to Appendix 11, comprising deciding to discard a UL transmission or UL grant if at least one corresponding time resource for a UL subband overlaps with a broadcast transmission in at least partially in the time domain. (Note 13) The method as described in Appendix 11 or 12, comprising determining not to monitor at least one control resource set (CORESET) or downlink control information (DCI) if at least one corresponding time resource for the UL subband overlaps at least partially with broadcast transmissions in the time domain. (Note 14) The method according to any one of the appendices 11 to 13, wherein if a portion of at least one set of time resources for a UL subband overlaps with broadcast transmissions in the time domain, and a portion of at least one set of time resources for a UL subband does not overlap with broadcast transmissions in the time domain, the method includes deciding to use a portion of at least one set of time resources for a UL subband that does not overlap with broadcast transmissions in the time domain, and not using a portion of at least one set of time resources for a UL subband that overlaps with broadcast transmissions in the time domain for UL transmissions in the UL subband. (Note 15) The method as described in Appendix 14, comprising deciding to use the at least one symbol for the UL subband that does not overlap with the broadcast transmission in the time domain if at least one symbol for the UL subband overlaps with the broadcast transmission in the time domain, and to transmit a UL transmission in the UL subband without using the at least one symbol for the UL subband that overlaps with the broadcast transmission in the time domain for a UL transmission in the UL subband. (Note 16) Broadcast transmission is for wireless link monitoring or link recovery, as described in any one of Annexes 11 to 15. (Note 17) A method performed by user equipment (UE) to communicate with an access network node, the method being: Receiving first information from an access network node that shows a first pattern of at least one of the time resources for uplink (UL) communication, time resources for downlink (DL) communication, and time resources for the UL subband, Receiving second information from an access network node that shows a second pattern of at least one of the time resources for UL communication, time resources for DL ​​communication, and time resources for the UL subband, When the first piece of information indicates that time resources should be used for UL subband and DL communications, the access network node should use the time resources to send uplink transmissions on the UL subband. Methods that include... (Note 18) The method is, If the first piece of information indicates that the time resource should be used for the UL subband, and the second piece of information indicates that the time resource should be used for DL ​​communication, then the access network node should use the time resource to send a UL subband transmission on the UL subband. The method described in Appendix 17, including the method described in Appendix 17. (Note 19) The method is, The first piece of information indicates that the time resource should be used for the UL subband, and the second piece of information indicates that the time resource should be used for DL ​​communication, but the second piece of information does not include an instruction that the time resource should be used for the UL subband, in which case the access network node decides not to use the time resource to send UL subband transmissions on the UL subband. The method described in Appendix 17, including the method described in Appendix 17. (Note 20) The method described in any one of the appendices 17 to 19, wherein the first information indicates a first pattern common to UEs within a cell of an access network node, and the second information indicates a second pattern which is a pattern specific to the UE. (Note 21) A method performed by an access network node to communicate with user equipment (UE), the method being: Transmitting to the user equipment first information that shows a first pattern of at least one of the time resources for uplink (UL) communication, time resources for downlink (DL) communication, and time resources for the UL subband, Transmitting to the user equipment second information indicating at least one second pattern of time resources for UL communication, time resources for DL ​​communication, and time resources for UL subband, When the first piece of information indicates that time resources should be used for UL subband and DL communications, the user equipment will use the time resources to receive uplink transmissions on the UL subband. Methods that include... (Note 22) The method is, When the first piece of information indicates that the time resource should be used for the UL subband, and the second piece of information indicates that the time resource should be used for DL ​​communication, the user equipment will receive the UL subband transmission on the UL subband using the time resource. The method described in Appendix 21, including the method described in Appendix 21. (Note 23) The method as described in Appendix 21 or 22, wherein the first information indicates a first pattern common to UEs within a cell of an access network node, and the second information indicates a second pattern which is a pattern specific to the UE. (Note 24) A method performed by an access network node to communicate with user equipment (UE), the method being: UE, At least one UL communication time gap adjacent to the interface between the UL subband in a first time resource configured for uplink (UL) communication and a second time resource configured for DL ​​communication, or At least one DL communication time gap adjacent to the interface between the DL subband in a third time resource configured for downlink (DL) communication and a fourth time resource configured for UL communication. To send time gap configuration information to configure at least one of the following: Methods that include... (Note 25) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of at least one UL communication time gap that should be in a first time resource, or at least one DL communication time gap that should be in a third time resource. (Note 26) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap which should be in the UL subband of the second time resource, or at least one DL communication time gap which should be in the DL subband of the fourth time resource. (Note 27) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the end of the first time resource when the first time resource is before the second time resource, or at least one DL communication time gap that should be at the end of the third time resource when the third time resource is before the fourth time resource. (Note 28) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the beginning of the second time resource when the first time resource is before the second time resource, or at least one DL communication time gap that should be at the beginning of the fourth time resource when the third time resource is before the fourth time resource. (Note 29) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the beginning of the first time resource when the first time resource is after the second time resource, or at least one DL communication time gap that should be at the beginning of the third time resource when the third time resource is after the fourth time resource. (Note 30) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the end of the second time resource when the first time resource is after the second time resource, or at least one DL communication time gap that should be at the end of the fourth time resource when the third time resource is after the fourth time resource. (Note 31) The method according to Appendix 24, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be in the UL subband within the second time resource, regardless of whether the first time resource is before or after the second time resource, or at least one DL communication time gap that should be in the DL subband within the fourth time resource, regardless of whether the third time resource is before or after the fourth time resource. (Note 32) The time gap configuration information is the method described in Appendix 24, which includes the configuration of one or more flexible symbols. (Note 33) A method performed by user equipment (UE) to communicate with an access network node, the method being: At least one UL communication time gap adjacent to the interface between the UL subband in a first time resource configured for uplink (UL) communication and a second time resource configured for DL ​​communication, or At least one DL communication time gap adjacent to the interface between the DL subband in a third time resource configured for downlink (DL) communication and a fourth time resource configured for UL communication. To obtain time gap configuration information to configure at least one of the following: Methods that include... (Note 34) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of at least one UL communication time gap that should be in a first time resource, or at least one DL communication time gap that should be in a third time resource. (Note 35) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap which should be in the UL subband of the second time resource, or at least one DL communication time gap which should be in the DL subband of the fourth time resource. (Note 36) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the end of the first time resource when the first time resource is before the second time resource, or at least one DL communication time gap that should be at the end of the third time resource when the third time resource is before the fourth time resource. (Note 37) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the beginning of the second time resource when the first time resource is before the second time resource, or at least one DL communication time gap that should be at the beginning of the fourth time resource when the third time resource is before the fourth time resource. (Note 38) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the beginning of the first time resource when the first time resource is after the second time resource, or at least one DL communication time gap that should be at the beginning of the third time resource when the third time resource is after the fourth time resource. (Note 39) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be at the end of the second time resource when the first time resource is after the second time resource, or at least one DL communication time gap that should be at the end of the fourth time resource when the third time resource is after the fourth time resource. (Note 40) The method according to Appendix 33, wherein the time gap configuration information instruction constitutes at least one of the following: at least one UL communication time gap that should be in the UL subband within the second time resource, regardless of whether the first time resource is before or after the second time resource, or at least one DL communication time gap that should be in the DL subband within the fourth time resource, regardless of whether the third time resource is before or after the fourth time resource. (Note 41) The time gap configuration information is the method described in Appendix 33, which includes the configuration of one or more flexible symbols. (Note 42) Obtaining time gap configuration information is the method described in any one of the appendices 33 to 41, which includes receiving time gap configuration information from an access network node. (Note 43) Time gap configuration information is pre-configured in the UE as described in any one of the appendices 33 to 41. (Note 44) An access network node for communicating with user equipment (UE), the access network node is Means for transmitting first information to the UE, which indicates at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, Means for transmitting UL subband configuration information to the UE, including instructions for a first set of at least one time resources for the UL subband where at least one instance of a repeating pattern does not overlap in the time domain with a repeating broadcast transmission, and a second set of at least one time resources for the UL subband where at least one instance of a repeating pattern overlaps in the time domain with a broadcast transmission, A means of receiving uplink transmissions on the uplink subband from user equipment. An access network node equipped with this feature. (Note 45) User equipment (UE) for communicating with access network nodes, where the UE is, Means for receiving first information from an access network node, which shows at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, Means for receiving UL subband configuration information from an access network node, including instructions for a first set of at least one time resources for the UL subband where at least one instance of a repeating pattern does not overlap with the repeating broadcast transmission in the time domain, and a second set of at least one time resources for the UL subband where at least one instance of a repeating pattern overlaps with the broadcast transmission in the time domain, A means for transmitting uplink transmissions on the uplink subband to an access network node. A UE equipped with (Note 46) User equipment (UE) for communicating with access network nodes, where the UE is, Means for receiving first information from an access network node, which includes at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, and at least one set of time resources for the UL subband, Means for receiving broadcast transmissions from access network nodes, A means for determining whether at least one set of time resources for the UL subband overlaps at least partially with broadcast transmissions in the time domain, A means for an access network node to transmit an uplink transmission on the UL subband using at least one set of time resources for the UL subband, when it is determined that at least one set of time resources for the UL subband does not overlap with broadcast transmissions in the time domain at least partially, When it is determined that at least one time resource of at least one set of time resources for the UL sub - band overlaps with broadcast transmission in the time domain, means for determining that the access network node does not transmit an uplink transmission in the UL sub - band using at least one time resource of at least one set of time resources for the UL sub - band A UE comprising (Appendix 47) A user equipment (UE) for communicating with an access network node, wherein the UE Means for receiving, from the access network node, first information indicating at least one first pattern of time resources for uplink (UL) communication, time resources for downlink (DL) communication, and time resources for the UL sub - band Means for receiving, from the access network node, second information indicating at least one second pattern of time resources for UL communication, time resources for DL communication, and time resources for the UL sub - band When the first information indicates that the time resource should be used for the UL sub - band and DL communication, means for transmitting an uplink transmission in the UL sub - band using the time resource to the access network node A UE comprising (Appendix 48) An access network node for communicating with a user equipment (UE), wherein the access network node Means for transmitting, to the user equipment, first information indicating at least one first pattern of time resources for uplink (UL) communication, time resources for downlink (DL) communication, and time resources for the UL sub - band Means for transmitting, to the user equipment, second information indicating at least one second pattern of time resources for UL communication, time resources for DL communication, and time resources for the UL sub - band When the first information indicates that the time resource should be used for UL sub - bands and DL communication, means for receiving an uplink transmission in the UL sub - band using the time resource from a user equipment An access network node comprising (Appendix 49) An access network node for communicating with a user equipment (UE), wherein the access network node To the UE At least one UL communication time gap adjacent to an interface between a UL sub - band within a first time resource configured for uplink (UL) communication and a second time resource configured for DL communication, or At least one DL communication time gap adjacent to an interface between a DL sub - band within a third time resource configured for downlink (DL) communication and a fourth time resource configured for UL communication Means for transmitting time gap configuration information for constituting at least one of An access network node comprising (Appendix 50) A user equipment (UE) for communicating with an access network node, wherein the UE At least one UL communication time gap adjacent to an interface between a UL sub - band within a first time resource configured for uplink (UL) communication and a second time resource configured for DL communication, or At least one DL communication time gap adjacent to an interface between a DL sub - band within a third time resource configured for downlink (DL) communication and a fourth time resource configured for UL communication Means for obtaining time gap configuration information for constituting at least one of A UE comprising

Explanation of Signs

[0197] 1. Mobile (cellular or wireless) telecommunications systems 3. User equipment 5 Base station / radio access network (RAN) node 7 Core Network 9. Associated cells 10 control plane function (CPF) 11. User-Plane Function (UPF) 31 Transceiver Circuit 33 Antennas 35 User Interface 37 Controllers 39 memory 41 Operating Systems 43 Communication control module 51 Transceiver Circuit 53 Antenna 55 Core Network Interfaces 57 Controllers 59 memory 61 Operating Systems 63 Communication control module

Claims

1. Means for receiving first information from an access network node, which includes at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, and at least one set of time resources for the UL subband. Means for receiving a synchronization signal / physical broadcast channel (PBCH) block (SSB) from the aforementioned access network node, Means for determining whether the at least one set of time resources for the UL subband competes in the time domain with the at least one time resource for the SSB, Means for determining whether to transmit a UL transmission on the UL subband using the at least one set of time resources for the UL subband, based on the determination of whether the at least one set of time resources for the UL subband competes in the time domain with the at least one set of time resources for the SSB, and A mobile device equipped with these features.

2. Means for determining to discard the UL transmission or the UL grant for the UL transmission if the at least one set of time resources for the UL subband competes in the time domain with the at least one time resource for the SSB The mobile device according to claim 1, comprising:

3. If a portion of the at least one set of time resources for the UL subband competes with the at least one time resource for the SSB in the time domain, and the other portion of the at least one set of time resources for the UL subband does not compete with the at least one time resource for the SSB in the time domain, Using the other portion of the at least one set of time resources for the UL subband that do not conflict with the at least one time resource for the SSB in the time domain, For the UL transmission in the UL subband, without using the portion of the at least one set of time resources for the UL subband that compete in the time domain with the at least one time resource for the SSB, Means for determining whether to transmit the UL transmission on the UL subband A mobile device according to claim 1 or 2, comprising:

4. If at least one symbol for the UL subband competes with the at least one time resource for the SSB in the time domain, and at least one other symbol for the UL subband does not compete with the at least one time resource for the SSB in the time domain, Using the at least one time resource for the SSB and the at least one other symbol for the UL subband that does not conflict in the time domain, In the UL transmission on the UL subband, without using the at least one symbol for the UL subband that competes with the at least one time resource for the SSB in the time domain, Means for determining whether to transmit the UL transmission on the UL subband The mobile device according to claim 3, comprising:

5. The first information indicates two patterns of time resources for the UL communication using the UL subband, The first of the two patterns includes a time resource for UL communication using the UL subband, which is larger than the second of the two patterns. The time resources for UL communication using the UL subband shown by the second pattern described above do not compete in the time domain with at least one time resource for SSB, The aforementioned mobile device Means for receiving the SSB from the access network node using the at least one time resource for the SSB, The access network node and means for performing the UL communication using the time resources that use the UL subband corresponding to at least one of the first pattern or the second pattern, A mobile device according to claim 1 or 2, comprising:

6. Means for performing UL communication with the access network node while restricting the UL communication in the time gap between a first time resource configured for the UL communication or the DL communication and a second time resource configured for the UL communication in the UL subband. A mobile device according to claim 1 or 2, comprising:

7. From the access network node, A first pattern of time resources for UL communication, time resources for DL ​​communication, and time resources for both UL communication and DL communication, and A second pattern of time resources for UL communication using the UL subband. Means for receiving the common configuration in the cell of the access network node, Means for receiving a dedicated configuration for the mobile device from the access network node, which includes a time resource for UL communication, a time resource for DL ​​communication, and a third pattern of at least one of the time resources for both UL communication and DL communication. Means for configuring the time resources for UL communication using the UL subband within a duration in which the time resources for both UL communication and DL communication in the first pattern and the time resources for UL communication using the UL subband in the second pattern overlap, based on whether the dedicated configuration includes a fourth pattern of time resources for the UL subband; A mobile device according to claim 1 or 2, comprising:

8. A means for transmitting first information to a mobile device, which includes at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, and at least one set of time resources for a UL subband, The means for transmitting a synchronization signal / physical broadcast channel (PBCH) block (SSB) to the aforementioned mobile device, Based on a determination of whether the at least one set of time resources for the UL subband conflicts in the time domain with the at least one set of time resources for the SSB, the mobile device has means to receive UL transmissions on the UL subband using the at least one set of time resources for the UL subband. An access network node equipped with this feature.

9. Receiving first information from an access network node, which includes at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, and at least one set of time resources for the UL subband, Receiving a synchronization signal / physical broadcast channel (PBCH) block (SSB) from the aforementioned access network node, Determining whether the at least one set of time resources for the UL subband competes in the time domain with the at least one time resource for the SSB, Based on the determination of whether the at least one set of time resources for the UL subband competes with the at least one time resource for the SSB in the time domain, the access network node is to determine whether to use the at least one set of time resources for the UL subband to transmit a UL transmission on the UL subband. Methods that are performed by mobile devices, including those mentioned above.

10. Transmitting first information to a mobile device, which includes at least one repeating pattern of time resources for uplink (UL) communication and time resources for downlink (DL) communication, and at least one set of time resources for a UL subband, The mobile device is to transmit a synchronization signal / physical broadcast channel (PBCH) block (SSB), Based on the determination of whether the at least one set of time resources for the UL subband conflicts in the time domain with the at least one set of time resources for the SSB, the mobile device may use the at least one set of time resources for the UL subband to receive UL transmissions on the UL subband. A method that is performed by an access network node, including [this].

Images