WO2023287329A1 - Sélection de motif tdd pour un nœud de réseau d'accès - Google Patents

Sélection de motif tdd pour un nœud de réseau d'accès Download PDF

Info

Publication number
WO2023287329A1
WO2023287329A1 PCT/SE2021/050724 SE2021050724W WO2023287329A1 WO 2023287329 A1 WO2023287329 A1 WO 2023287329A1 SE 2021050724 W SE2021050724 W SE 2021050724W WO 2023287329 A1 WO2023287329 A1 WO 2023287329A1
Authority
WO
WIPO (PCT)
Prior art keywords
slots
tdd pattern
access network
tdd
node
Prior art date
Application number
PCT/SE2021/050724
Other languages
English (en)
Inventor
Sara SANDBERG
Peter De Bruin
Arne Simonsson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/SE2021/050724 priority Critical patent/WO2023287329A1/fr
Publication of WO2023287329A1 publication Critical patent/WO2023287329A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2643—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA]
    • H04B7/2656—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA] for structure of frame, burst

Definitions

  • Embodiments presented herein relate to a method, a network management node, a computer program, and a computer program product for selecting a time-division duplex pattern for an access network node.
  • TDD time-division duplex
  • the switch between downlink and uplink occurs in so- called special subframes (using Long Term Evolution (LTE), or fourth generation telecommunication systems, terminology) or so-called flexible subframes (using new radio (NR), or fifth generation telecommunication systems, terminology).
  • LTE Long Term Evolution
  • NR new radio
  • Table 1 which is identical to Table 4.2-2 in 3GPP TS 36.211 V15.2.0, in LTE, and where “D” denotes downlink subframes, “U” denotes uplink subframes, and “S” denotes flexible subframes, seven different uplink-downlink configurations are provided.
  • 3GPP is short for third generation partnership project and TS is short for technical specification.
  • the size of the guard period (as defined by the number of uplink and downlink symbols in the flexible slot(s)) and hence the number of symbols for the downlink pilot time slot (DwPTS), and uplink pilot time slot (UwPTS) in the special subframe, can also be configured from a set of possible selections.
  • NR on the other hand provides many different uplink-downlink configurations.
  • Each slot can be configured with a slot format as shown in Table 11.1.1-1 in 3GPP TS 38.212, V16.4.0.
  • a semi-static TDD uplink-downlink configuration may be used where the TDD configuration is provided via radio resource control (RRC) configuration using the information element (IE) denoted TDD-UL-DL-ConfigCommon as specified in 3GPP TS 38.331, V15.2.1.
  • RRC radio resource control
  • IE information element
  • the number of uplink and downlink slots, as well as the guard period may be almost arbitrarily configured within the TDD periodicity. This allows for very flexible uplink-downlink configurations.
  • existing communications networks using TDD are typically dimensioned for services that are DL heavy.
  • a TDD pattern is seen as DL heavy when the fraction of DL TDD slots is higher than the fraction of UL TDD slots for that TDD pattern.
  • MBB mobile broadband
  • many industrial applications both massive machine-type-communications (mMTC) and critical MTC (cMTC) are expected to be UL heavy, in terms of both performance and capacity requirements.
  • streaming of high-quality video (or lidar data or radar data) from a remotely controlled machine, or vehicle might require higher UL throughput than the DL throughput required for control of the machine, or vehicle.
  • sensors might be configured to continuously transmit updates in UL whilst DL transmission occurs only when the operation of the sensor needs adjustment.
  • the UL traffic from a single sensor may be reasonably limited in transferred data size, but might occur with very frequent (periodic or aperiodic) transmissions.
  • sensor platforms aggregating the information from multiple sensors, yielding large amounts of data to be transmitted in UL from the sensor platforms. It can therefore be desirable to use an UL-heavy TDD pattern in industrial networks or non-public networks (NPNs).
  • Using a UL heavy TDD pattern in a part of a communications network might be cumbersome if the same, or adjacent, frequency band is used for the UL heavy TDD pattern as for a neighboring part of the communications (or even another communications network) where a DL heavy TDD pattern is used, because of possible cross-link interference.
  • Neighboring access network nodes serving different cells should therefore generally be time synchronized with slot border starting at the same time and have the same uplink-downlink configuration in order to avoid severe interference between uplink and downlink transmissions. This could make it difficult in the network to dynamically switch between different uplink-downlink configurations in order to adapt to current uplink and downlink traffic patterns and traffic distributions.
  • a first user equipment (UE) on a cell edge of a first access network node receiving downlink transmission from the first access network node might be significantly interfered by a nearby second UE simultaneously transmitting in uplink to a second access network node serving a neighboring cell with a different uplink- downlink configuration.
  • UE user equipment
  • An object of embodiments herein is to provide mechanisms that enable flexible selection of TDD patterns in a communications network, not suffering from the issues noted above or where the issues noted above at least are mitigated or reduced.
  • a method for selecting a first TDD pattern for a first access network node comprises first DL slots for DL communication and first UL slots for UL communication.
  • the method comprises obtaining information of a second TDD pattern used by a second access node neighboring the first access network node and comprises second DL slots and second UL slots, each of which is composed of symbols.
  • the method comprises obtaining information of UL/DL traffic distribution of the first access network node.
  • the method comprises selecting the first TDD pattern so as to match the second TDD pattern in terms of DL and UL, except that in at least one of the first UL slots, a UL symbol block, composed of at least one UL symbol, overlaps in time with at least one of the second DL slots but spans less than all symbols of said at least one of the second DL slots. How many symbols the UL symbol block is composed of is determined as a function of the information of UL/DL traffic distribution.
  • a network management node for selecting a first TDD pattern for a first access network node.
  • the first TDD pattern comprises first DL slots for DL communication and first UL slots for UL communication.
  • the network management node comprises processing circuitry.
  • the processing circuitry is configured to cause the network management node to obtain information of a second TDD pattern used by a second access node neighboring the first access network node and comprises second DL slots and second UL slots, each of which is composed of symbols.
  • the processing circuitry is configured to cause the network management node to obtain information of UL/DL traffic distribution of the first access network node.
  • the processing circuitry is configured to cause the network management node to select the first TDD pattern so as to match the second TDD pattern in terms of DL and UL, except that in at least one of the first UL slots, a UL symbol block, composed of at least one UL symbol, overlaps in time with at least one of the second DL slots but spans less than all symbols of said at least one of the second DL slots. How many symbols the UL symbol block is composed of is determined as a function of the information of UL/DL traffic distribution.
  • a network management node for selecting a first TDD pattern for a first access network node.
  • the first TDD pattern comprises first DL slots for DL communication and first UL slots for UL communication.
  • the network management node comprises an obtain module configured to obtain information of a second TDD pattern used by a second access node neighboring the first access network node and comprises second DL slots and second UL slots, each of which is composed of symbols.
  • the network management node comprises an obtain module configured to obtain information of UL/DL traffic distribution of the first access network node.
  • the network management node comprises a select module configured to select the first TDD pattern so as to match the second TDD pattern in terms of DL and UL, except that in at least one of the first UL slots, a UL symbol block, composed of at least one UL symbol, overlaps in time with at least one of the second DL slots but spans less than all symbols of said at least one of the second DL slots. How many symbols the UL symbol block is composed of is determined as a function of the information of UL/DL traffic distribution.
  • a computer program for selecting a first TDD pattern for a first access network node comprising computer program code which, when run on a network management node 200, causes the network management node to perform a method according to the first aspect.
  • a computer program product comprising a computer program according to the fourth aspect and a computer readable storage medium on which the computer program is stored.
  • the computer readable storage medium could be a non-transitory computer readable storage medium.
  • these aspects provide flexible selection of the first TDD pattern.
  • the average round-trip time (RTT) latency can be reduced for the UEs served by the first access network node.
  • the first TDD pattern can be selected to be suited for short delay ultra-reliable low latency communication (URLLC) and UL heavy traffic.
  • URLLC ultra-reliable low latency communication
  • the first TDD pattern can be selected to be almost identical to the second TDD pattern, very little additional interference toward neighboring access network nodes where the second TDD pattern is used is caused due to the differences between the first and the second TDD pattern.
  • Fig. 1 is a schematic diagram illustrating a communications network according to embodiments presented herein;
  • Figs. 2, 3, 5, 6, 7, and 8 schematically illustrate TDD patterns according to embodiments;
  • Fig. 4 is a flowchart of methods according to embodiments;
  • Fig. 9 is a schematic diagram showing functional units of a network management node according to an embodiment;
  • Fig. to is a schematic diagram showing functional modules of a network management node according to an embodiment
  • Fig. li shows one example of a computer program product comprising computer readable storage medium according to an embodiment
  • Fig. 12 is a schematic diagram illustrating a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments; and Fig. 13 is a schematic diagram illustrating host computer communicating via a radio base station with a terminal device over a partially wireless connection in accordance with some embodiments.
  • the wording that a certain data item or piece of information, or the like, is obtained by a first device, entity, or the like, should be construed as that data item or piece of information being retrieved, fetched, received, or otherwise made available to the first device.
  • the data item or piece of information might either be pushed to the first device from a second device, entity, or the like, or pulled by the first device from the second device.
  • the first device might be configured to perform a series of operations, possible including interaction with the second device.
  • Such operations, or interactions might involve a message exchange comprising any of a request message for the data item or piece of information, a response message comprising the data item or piece of information, and an acknowledge message of the data item or piece of information.
  • the request message might be omitted if the data item or piece of information is neither explicitly nor implicitly requested by the first device.
  • a certain data item or piece of information, or the like, is provided by a first device, entity, or the like, to a second device, entity, or the like should be construed as that data item or piece of information being sent or otherwise made available to the second device by the first device.
  • the data item or piece of information might either be pushed to the second device from the first device or pulled by the second device from the first device.
  • the first device and the second device might be configured to perform a series of operations in order to interact with each other.
  • Such operations, or interaction might involve a message exchange comprising any of a request message for the data item or piece of information, a response message comprising the data item or piece of information, and an acknowledge message of the data item or piece of information.
  • the request message might be omitted if the data item or piece of information is neither explicitly nor implicitly requested by the second device.
  • Fig. 1 is a schematic diagram illustrating a communications network 100 where embodiments presented herein can be applied.
  • the communications network 100 comprises cells 110a, 110b.
  • Each cell 110a, 110b is served by a respective (radio) access network node 120a, 120b.
  • UEs 130a, 130b operatively connected to any of the access network node 120a, 120b are thereby provided network access.
  • Examples of (radio) access network nodes 120a, 120b are radio base stations, base transceiver stations, Node Bs, evolved Node Bs, g NBs, access points, access nodes, radio dot nodes, and backhaul nodes.
  • the access network nodes 120a, 120b could be placed indoors or outdoors; some access network nodes 120a, 120b could be placed indoors whilst other are placed outdoors, etc.
  • Access network node 120a will hereinafter be denoted a first access network node 120a whereas access network nodes 120b will hereinafter be denoted second access network node(s) 120b. However, this does not imply that there is any hierarchical relation between the access network nodes 120a, 120b.
  • the first access network node 120a is part of an industrial communication network or a local network, such as a non-public network (NPN).
  • NPN non-public network
  • UEs 130a, 130b are mobile stations, mobile phones, handsets, wireless local loop phones, smartphones, laptop computers, tablet computers, network equipped sensors (such as network equipped cameras, e.g. in terms of surveillance cameras or vehicle-mounted cameras), network equipped vehicles, and so-called Internet of Things devices.
  • UEs 130b will hereinafter represent a typical UE using a DL heavy service such as a mobile broadband service
  • UEs 130a will hereinafter represent a typical UE using a UL heavy service such as an industrial network service.
  • the first access network nodes 120a and the second access network nodes 120b are neighbors. This might imply that there are not any other access network nodes placed physically in between the first access network node 120a and the second access network nodes 120b, or at least not any other such other access network nodes operating in the same, or adjacent frequency band as the first access network node 120a. This might further imply that the cells 110a, 110b are adjacent each other, possibly even overlapping at the cell edges. That is, a UE 130a, 130b located at the cell edge between cell 110a and cell 110b might be able to receive signals from both the first access network nodes 120a and the second access network nodes 120b above a signal threshold level.
  • TDD is used for DL and UL communication between the access network nodes 120a, 120b and the UEs 130a, 130b. In some aspects it is further assumed that DL and UL communication is performed on component carriers.
  • a first TDD pattern is used for communication in the cell 110a.
  • a second TDD pattern is used for communication in the cells 110b.
  • the first TDD pattern 140 is preferably UL heavy (as indicated by the bold arrow from UE 130a towards access network node 120a) whereas the second TDD pattern 150 preferably is DL heavy (as indicated by the bold arrow from access network nodes 120b towards UEs 130b).
  • One reason for using a DL heavy TDD pattern 150 is to serve UEs 130b using a mobile broadband service that is mainly DL heavy with for example video downloads.
  • One reason for using a UL heavy TDD pattern 140 is to serve UEs 130a using an mMTC or cMTC service that is mainly UL heavy with for example sensor uploads. The latter could be the case where the UEs 130a operate in an industrial network, such as remote-controlled vehicles equipped with video cameras that produce video streams that need to be transmitted in UL to a central control room for monitoring of the remote-controlled vehicles.
  • the operation of at least access network node 120a, and thus at least of cell 110a, is controlled by a network management node 200.
  • the network management node 200 is configured to select, and thereby control, which TDD pattern that is to be used for DL and UL communication in the cell 110a.
  • the network management node 200 is integrated with, collocated with, or part of access network node 120a serving cell 110a with a first TDD pattern.
  • the network management node 200 is integrated with, collocated with, or part of a network-centric node controlling access network node 120a serving the cell 110a as well as at least one other access network node (such as any of access network node 120b).
  • TDD patterns 140, 150 are focused on providing flexible selection of the first TDD pattern 140.
  • this can be regarded as defining a subset of TDD patterns to select from that limits the CLI. This implies that the flexibility is restricted for the benefit of enabling selection of TDD patterns that can be used in practical network deployments.
  • complete time synchronisation, or even exclusion zones, between cells 110a, 110b, and thus between access network nodes 120a, 120b, is required to avoid large guard bands for filter roll off.
  • the first TDD pattern 140 should be UL/DL-aligned with the DL-heavy second TDD pattern 150 of the surrounding cells 110b.
  • the first TDD pattern 140 and the second TDD pattern 150 to be fully UL/DL-aligned, the first TDD pattern 140 needs to comprise DL slots when the second TDD pattern 150 comprises DL slots, and the first TDD pattern 140 needs to comprise UL slots when the second TDD pattern 150 comprises UL slots.
  • Fig. 2 shows an example where the first TDD pattern 140 is fully UL/DL-aligned with the second TDD pattern 150, although the first TDD pattern 140 is a TDD pattern used for NR and the second TDD pattern 150 is a TDD pattern used for LTE, and hence the sub-carrier spacing (SCS) is different (30 kHz compared to 15 kHz) and the total number of slots is different (10 slots compared to 5 slots).
  • SCS sub-carrier spacing
  • the UEs 130a served in the cell 110a are assumed to be UL heavy and hence would benefit from a TDD pattern that offers more UL slots than the example of Fig. 2.
  • a UL heavy first TDD pattern 140 is illustrated in Fig. 3.
  • the UEs 130a might benefit from a TDD pattern that gives low average RTT latency.
  • first TDD pattern 140 illustrated in Fig. 3 With the second TDD pattern 150 illustrated in Fig. 2. This since the TDD patterns will no longer be UL/DL-aligned, which might cause cross-link interference (CLI), both in co-channel and adjacent channel and especially for frequencies in mid band. Hence, the flexibility offered by the first TDD pattern 140 in Fig. 3 might be difficult to utilize. A consequence of this might be that the first TDD pattern 140 illustrated in Fig. 2 must be used in the cell 110a. As such, this TDD pattern is optimized for DL heavy traffic.
  • CLI cross-link interference
  • the embodiments disclosed herein therefore relate to mechanisms for selecting a first TDD pattern 140 for a first access network node 120a.
  • a network management node 200 a method performed by the network management node 200, a computer program product comprising code, for example in the form of a computer program, that when run on a network management node 200, causes the network management node 200 to perform the method.
  • the TDD pattern can be selected almost arbitrarily on symbol level. This flexibility can be used to set up the first TDD pattern 140 (e.g.
  • first TDD patterns 140 that, for example, can be used in deployments requiring low latency or increased uplink capacity.
  • the first TDD patterns 140 are selected so that partial UL/DL- alignment (in terms of UL and DL symbols) with the second TDD pattern 140 is achieved.
  • Fig. 4 is a flowchart illustrating embodiments of methods for selecting a first TDD pattern 140 for a first access network node 120a.
  • the first TDD pattern 140 comprises first DL slots for DL communication and first UL slots for UL communication.
  • the methods might be performed by the network management node 200.
  • the methods are advantageously provided as computer programs 1120.
  • At least some of the herein disclosed embodiments are based on that the first TDD pattern 140, as used by the first access network node 120a, is selected to be similar to the second TDD pattern 150 used by a neighbouring second access network node 120b, but with symbol(s) for UL available within long periods of DL-only slots.
  • the network management node 200 obtains information of a second TDD pattern 150 used by a second access node 120b.
  • the second access node 120b neighbors the first access network node 120a.
  • the second TDD pattern 150 comprises second DL slots and second UL slots, each of which being composed of symbols.
  • the network management node 200 obtains information of UL/DL traffic distribution of the first access network node 120a.
  • the network management node 200 selects the first TDD pattern 140 so as to match the second TDD pattern 150 in terms of DL and UL, except that in at least one of the first UL slots, a UL symbol block, composed of at least one UL symbol, overlaps in time with at least one of the second DL slots but spans less than all symbols of the at least one of the second DL slots. How many symbols the UL symbol block is composed of is determined as a function of the information of UL/DL traffic distribution.
  • the information of the second TDD pattern 150 used by the second access node 120b might be obtained by the network management node 200 directly from the second access network node 120b, possibly via a further entity, node, or device.
  • the information of the second TDD pattern 150 might be obtained by the network management node 200 from a data repository, or other type of storage medium, where such information is collected and stored.
  • the information of the second TDD pattern 150 might be the second TDD pattern 150 itself.
  • the information of the second TDD pattern 150 constitutes information that unambiguously identifies the second TDD pattern 150.
  • the information of UL/DL traffic distribution of the first access network node 120a might be obtained by the network management node 200 directly from the first access network node 120a, possibly via a further entity, node, or device.
  • the information of UL/DL traffic distribution of the first access network node 120a might be obtained by the network management node 200 from a data repository, or other type of storage medium, where such information is collected and stored.
  • the information of UL/DL traffic distribution might be obtained by studying the amount of UL and DL traffic of the first access network node 120a. Such information might be available from a scheduler of the UL and DL traffic of the first access network node 120a.
  • the first TDD pattern 140 and the second TDD pattern 150 might be used for communication in any of: adjacent frequency bands, adjacent (or at least very close) frequency allocations within same frequency band, or at least partly overlapping frequency bands.
  • the second TDD pattern 150 might be specified by a UL-DL configuration used by a second access node 120b. This UL-DL configuration might be selected from one of the UL-DL configurations listed in table 1.
  • the first TDD pattern 140 might be time synchronized with the second TDD pattern 150 so that a slot of the first TDD pattern 140 starts simultaneously with a slot in the second TDD pattern 150.
  • the first TDD pattern 140 is selected also based on data traffic delay requirements and/or quality of service (QoS) requirements. Therefore, these parameters might be obtained by the network management node 200.
  • the method further comprises:
  • the network management node 200 obtains information of data traffic delay requirement for the user equipment 130a served by the first access network node 120a and/or QoS requirement for the user equipment 130a served by the first access network node 120a.
  • the information of data traffic delay requirement might be obtained by the network management node 200 directly from the first access network node 120a, possibly via a further entity, node, or device.
  • the information of data traffic delay requirement might be obtained by the network management node 200 from a data repository, or other type of storage medium, where such information is collected and stored.
  • the information of data traffic delay requirement might be obtained by the first access network node 120a from the user equipment 130a.
  • the information of data traffic delay requirement might either be pushed by the user equipment 130a to the first access network node 120a or be pulled by the first access network node 120a from the user equipment 130a.
  • such information is provided by an external entity to the data repository.
  • This external entity might be controlled by the network operator of the first access network node 120a, where the network operator has knowledge of the type of user equipment 130a to be served and also of the data traffic delay requirement of the type of user equipment 130a. Then, how far spaced in time two UL symbol blocks are to be might be determined as a function of the information of data traffic delay requirement and/or QoS requirement. The higher the data traffic delay requirement and/or QoS requirement, the shorter two UL symbol blocks should be separated in time.
  • the first TDD pattern 140 is selected also based on a tolerable CLI level. That is, how many symbols the UL symbol block is composed of might further be determined as a function of a CLI threshold value.
  • the slots of the first TDD pattern 140 might be transmitted on subcarriers. These subcarriers might have a subcarrier spacing (SCS) determined as a function of the information of data traffic delay requirements. Radio delay spread might be obtained and the SCS might be selected based on a combination of radio delay spread and delay requirements.
  • the radio delay spread generally represents a measure of the multipath profile of a radio propagation channel (in the present case between the first access network node 120a and its served user equipment 130a). It is generally defined as the difference between the time of arrival of the earliest component (e.g., the line- of-sight wave, if there exists) and the time of arrival of the latest multipath component, Particularly, in some embodiments, the method further comprises:
  • the network management node 200 obtains information of radio delay spread for the first access network node 120a.
  • the information of radio delay spread for the first access network node 120a might be obtained by the network management node 200 directly from the first access network node 120a, possibly via a further entity, node, or device.
  • the information of radio delay spread of the first access network node 120a might be obtained by the network management node 200 from a data repository, or other type of storage medium, where such information is collected and stored.
  • the first access network node 120a might obtain an estimate of the radio delay spread from measurements on signals received from the user equipment 130a, where such measurements capture the difference between the time of arrival of the earliest component (e.g., the line-of-sight wave, if there exists) and the time of arrival of the latest multipath component. Then, the subcarrier spacing is further determined as a function of the radio delay spread.
  • the earliest component e.g., the line-of-sight wave, if there exists
  • the subcarrier spacing is further determined as a function of the radio delay spread.
  • UL transmissions suffering from surrounding DL interference are identified and transmitted with a more robust transmission format.
  • the UL symbol block might be assigned lower coding rate and/or higher transmission power than symbols of first UL slots that do not overlap in time with any of the second DL slots.
  • a lower modulation and coding scheme (MCS) than what would otherwise have been selected can be used for the UL symbol block. This can for example be implemented by subtracting a margin from the estimated SINR before calculating what MCS to use, based on the estimated signal to interference plus noise ratio (SINR).
  • SINR signal to interference plus noise ratio
  • the first TDD pattern 140 is selected to be similar to the second TDD pattern 150.
  • the difference between the first TDD pattern 140 and the second TDD pattern 150 is defined by the UL symbol block.
  • the first TDD pattern 140 might be identical to the second TDD pattern 150 except for the UL symbol block in the first TDD pattern 140 that overlaps in time with the at least one of the second DL slots in the second TDD pattern 150. Examples of how many symbols there could be in the UL symbol block will be disclosed below.
  • the first TDD pattern 140 might match the second TDD pattern 150 such that the first TDD pattern 140 is composed of first DL slots when the second TDD pattern 150 is composed of second DL slots and the first TDD pattern 140 is composed of first UL slots when the second TDD pattern 150 is composed of second UL slots.
  • the UL symbol block is composed of a single symbol. This is the case for the first TDD pattern 140 illustrated in Fig. 7(a) which will be described in more detail below.
  • the UL symbol block is composed of less than all symbols in a slot.
  • the UL symbol block is composed of all symbols in a slot. It is here noted that also combinations of the above are possible. That is, the UL symbol block might be composed of all symbols in a slot and one or more adjacent symbols in an adjacent slot. This is the case for the first TDD pattern 140 illustrated in Fig. 7(c) which will be described in more detail below.
  • Fig. 5 shows a first TDD pattern 140 for 60 kHz SCS that is fully time-synchronized and almost UL/DL-aligned with a second TDD pattern 150 (corresponding to uplink- downlink configuration 2 in Table 1) with 15 kHz SCS.
  • the TDD patterns are UL/DL- aligned, except for additional UL symbols introduced in the first TDD pattern 140 to break up long periods of only DL transmissions. By introducing only as little as one UL symbol within the DL period of the second TDD pattern 150, the average latency can be significantly reduced. In this respect, although the one single UL symbol is added at the end of the slot, one (or more) UL symbol(s) could be added anywhere within the slot.
  • the second TDD pattern 150 if the UE 130a already at the start of the 5 ms period shown in Fig. 5 has UL data to transmit, it is not possible for the UE 130a to transmit UL data until in the first UL symbol. This means a delay of almost two slots (i.e., around 2 ms). But with the proposed first TDD pattern 140, the delay is only around 1 ms. Even if the UL period is only one symbol, some payload data as well as buffer status reports, HARQ ACK/NACKs, etc., can still be transmitted. For example, on a 90 MHz wide carrier there are 150060 kHz sub carriers.
  • the average UL latency can be further reduced if even more DL slots are exchanged to non-aligned slots (i.e., slots that are not UL/DL-aligned) with one or more UL symbols.
  • the DL slot of the second TDD pattern with a SCS 15 kHz corresponds to four slots in the first TDD pattern and one of them (the last one in Fig. 5) contains at least one UL symbol.
  • Fig. 6 shows a first TDD pattern 140 for 60 kHz SCS that is fully time-synchronized but less UL/DL-aligned with a second TDD pattern 150 (corresponding to uplink- downlink configuration 2 in Table 1) with 15 kHz SCS than in Fig. 5.
  • a larger number of consecutive UL symbols are added into otherwise long DL periods compared to in Fig. 5.
  • the total UL capacity of the cell 110a is increased in addition to reducing the average UL latency.
  • non-aligned UL symbols i.e., symbols designated for UL in the first TDD pattern 140 but designated for DL in the second TDD pattern 150
  • the frequency of occurrence of the non-aligned UL symbols i.e., how to time-wise distribute the non-aligned UL symbols
  • Fig. 7 is at (a), (b), and (c) shown, for different NR slot formats, how large fraction of the symbols in the neighboring cells 110b using a second TDD pattern 150 that is impacted by CLI due to the additional non-aligned UL symbols. It is hence assumed that for the time period shown in Fig. 7, the second TDD pattern 150 only contains DL symbols. If only 1 UL symbol is added to every fourth slot, as shown in Fig.
  • a first TDD pattern 140 based on this example will affect cells 120b using the second TDD pattern 150 only in 1 out of 14 symbols, and only in one out of four slots.
  • the symbol duration for 60 kHz SCS is shorter in time than the symbol duration of the symbol it interferes (with 15 kHz SCS)
  • the interference will only impact the DL symbol during 1/4 of the time.
  • this generates low additional interference noise, it is most likely still possible to decode the downlink transmission in the cells 110b.
  • more symbols are interfered, it becomes more probable that DL transmissions in the cells 110b using the second TDD pattern 150 cannot be successfully decoded after the first transmission attempt.
  • the UEs 130b served in the cells 110b where the second TDD pattern 150 is used typically carries MBB traffic with very relaxed latency bounds, any decoding failures can easily be handled through HARQ retransmissions.
  • a non-aligned slot is in the first TDD pattern 140 introduced also within the longer period of UL transmission.
  • the average latency is further reduced for UEs 130a in the cell 110a where the first TDD pattern 140 is used.
  • at least one of the first DL slots in a DL symbol block is selected to overlap in time with at least one of the second UL slots but to span less than all symbols of the at least one of the second UL slots.
  • a retransmission can be scheduled quickly in case of a decoding failure.
  • An example of this is shown in Fig. 8 where in the first TDD pattern 140, one non-aligned UL symbol is introduced in every second DL slot and one non-aligned DL symbol is introduced in one of the UL slots.
  • the thus far disclosed embodiments, aspects, and examples are equally applicable for outdoor and indoor network deployments, e.g. for local networks along roads or railways supporting foreseen future uplink heavy video or lidar upload to clouds from ordinary cars, trucks and trains.
  • the isolation between the road-near network (or road-near part of a macro network) and the surrounding macro network may have to be improved in addition to applying the thus far disclosed embodiments, aspects, and examples.
  • Increased isolation between a macro network and a local network outdoors can for example be achieved through beamforming or through the use of an exclusion zone where the carriers used by the local network are not used by the closest surrounding macro network access network nodes 120b.
  • Fig. 9 schematically illustrates, in terms of a number of functional units, the components of a network management node 200 according to an embodiment.
  • Processing circuitry 210 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1110 (as in Fig. 11), e.g. in the form of a storage medium 230.
  • the processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the processing circuitry 210 is configured to cause the network management node 200 to perform a set of operations, or steps, as disclosed above.
  • the storage medium 230 may store the set of operations
  • the processing circuitry 210 may be configured to retrieve the set of operations from the storage medium 230 to cause the network management node 200 to perform the set of operations.
  • the set of operations may be provided as a set of executable instructions.
  • the processing circuitry 210 is thereby arranged to execute methods as herein disclosed.
  • the storage medium 230 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the network management node 200 may further comprise a communications interface 220 at least configured for communications with the access network nodes 120a, 120b.
  • the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components.
  • the processing circuitry 210 controls the general operation of the network management node 200 e.g. by sending data and control signals to the communications interface 220 and the storage medium 230, by receiving data and reports from the communications interface 220, and by retrieving data and instructions from the storage medium 230.
  • Other components, as well as the related functionality, of the network management node 200 are omitted in order not to obscure the concepts presented herein.
  • Fig. 10 schematically illustrates, in terms of a number of functional modules, the components of a network management node 200 according to an embodiment.
  • the network management node 200 of Fig. 10 comprises a number of functional modules; an obtain module 210a configured to perform step S102, an obtain module 210b module configured to perform step S104, and a select module 2ioe configured to perform step Sno.
  • the network management node 200 of Fig. 10 may further comprise a number of optional functional modules, such as any of an obtain module 210c configured to perform step S106, and an obtain module 2iod configured to perform step S108.
  • each functional module 210a: 2ioe may in one embodiment be implemented only in hardware and in another embodiment with the help of software, i.e., the latter embodiment having computer program instructions stored on the storage medium 230 which when run on the processing circuitry makes the network management node 200 perform the corresponding steps mentioned above in conjunction with Fig 10.
  • the modules correspond to parts of a computer program, they do not need to be separate modules therein, but the way in which they are implemented in software is dependent on the programming language used.
  • one or more or all functional modules 2ioa:2ioe may be implemented by the processing circuitry 210, possibly in cooperation with the communications interface 220 and/or the storage medium 230.
  • the processing circuitry 210 may thus be configured to from the storage medium 230 fetch instructions as provided by a functional module 2ioa:2ioe and to execute these instructions, thereby performing any steps as disclosed herein.
  • the network management node 200 may be provided as a standalone device or as a part of at least one further device.
  • the network management node 200 may be provided in a node of the radio access network or in a node of the core network.
  • functionality of the network management node 200 may be distributed between at least two devices, or nodes. These at least two nodes, or devices, may either be part of the same network part (such as the radio access network or the core network) or may be spread between at least two such network parts.
  • instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the cell than instructions that are not required to be performed in real time.
  • a first portion of the instructions performed by the network management node 200 may be executed in a first device, and a second portion of the of the instructions performed by the network management node 200 may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the network management node 200 may be executed.
  • the methods according to the herein disclosed embodiments are suitable to be performed by a network management node 200 residing in a cloud computational environment. Therefore, although a single processing circuitry 210 is illustrated in Fig. 9 the processing circuitry 210 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 2ioa:2ioe of Fig. 10 and the computer program 1120 of Fig. 11.
  • Fig. 11 shows one example of a computer program product 1110 comprising computer readable storage medium 1130.
  • a computer program 1120 can be stored, which computer program 1120 can cause the processing circuitry 210 and thereto operatively coupled entities and devices, such as the communications interface 220 and the storage medium 230, to execute methods according to embodiments described herein.
  • the computer program 1120 and/or computer program product 1110 may thus provide means for performing any steps as herein disclosed.
  • the computer program product 1110 is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc.
  • the computer program product 1110 could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Fig. 12 is a schematic diagram illustrating a telecommunication network connected via an intermediate network 420 to a host computer 430 in accordance with some embodiments.
  • a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, and core network 414.
  • Access network 411 comprises a plurality of radio access network nodes 412a, 412b, 412c, such as NBs, eNBs, gNBs (each corresponding to one of the access network nodes 120a, 120b of Fig. 1) or other types of wireless access points, each defining a corresponding coverage area, or cell, 413a, 413b, 413c.
  • Each radio access network nodes 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415.
  • a first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding network node 412c.
  • a second UE 492 in coverage area 413a is wirelessly connectable to the corresponding network node 412a. While a plurality of UE 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole terminal device is connecting to the corresponding network node 412.
  • the UEs 491, 492 correspond to the UEs 130a, 130b of Fig. 1.
  • Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420.
  • Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).
  • the communication system of Fig. 12 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430.
  • the connectivity may be described as an over-the-top (OTT) connection 450.
  • Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signalling via OTT connection
  • OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications.
  • network node 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491.
  • network node 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.
  • Fig. 13 is a schematic diagram illustrating host computer communicating via a radio access network node with a UE over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with an embodiment, of the UE, radio access network node and host computer discussed in the preceding paragraphs will now be described with reference to Fig. 13.
  • host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500.
  • Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities.
  • processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518.
  • Software 511 includes host application 512.
  • Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510.
  • the UE 530 corresponds to the UEs 130a, 130b of Fig. 1.
  • host application 512 may provide user data which is transmitted using OTT connection 550.
  • Communication system 500 further includes radio access network node 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530.
  • the radio access network node 520 corresponds to the access network nodes 120a, 120b of Fig. 1.
  • Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in Fig. 13) served by radio access network node 520.
  • Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in Fig.
  • radio access network node 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Radio access network node 520 further has software 521 stored internally or accessible via an external connection.
  • Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a radio access network node serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510.
  • an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510.
  • client application 532 may receive request data from host application 512 and provide user data in response to the request data.
  • OTT connection 550 may transfer both the request data and the user data.
  • Client application 532 may interact with the user to generate the user data that it provides.
  • host computer 510, radio access network node 520 and UE 530 illustrated in Fig. 13 may be similar or identical to host computer 430, one of network nodes 412a, 412b, 412c and one of UEs 491, 492 of Fig. 12, respectively.
  • OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via network node 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 570 between UE 530 and radio access network node 520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may reduce interference, due to improved classification ability of airborne UEs which can generate significant interference.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect network node 520, and it may be unknown or imperceptible to radio access network node 520.
  • measurements may involve proprietary UE signalling facilitating host computer’s 510 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des mécanismes pour sélectionner un premier motif TDD pour un premier nœud de réseau d'accès sont divulgués. Le premier motif TDD comprend des premiers créneaux DL pour une communication DL et des premiers créneaux UL pour une communication UL. Un procédé comprend l'obtention d'informations d'un second motif TDD utilisé par un second nœud d'accès voisin du premier nœud de réseau d'accès et comprend des seconds créneaux DL et des seconds créneaux UL, dont chacun est composé de symboles. Le procédé comprend l'obtention d'informations de distribution de trafic UL/DL par le premier nœud de réseau d'accès. Le procédé comprend la sélection du premier motif TDD de façon à correspondre au second motif TDD en termes de DL et UL, sauf que dans au moins l'un des premiers créneaux UL, un bloc de symboles UL, composé d'au moins un symbole UL, se chevauche dans le temps avec au moins l'un des seconds créneaux DL mais s'étend sur moins de tous les symboles dudit au moins un des seconds créneaux DL. Le nombre de symboles dont le bloc de symboles UL est composé est déterminé en fonction des informations de distribution de trafic UL/DL.
PCT/SE2021/050724 2021-07-13 2021-07-13 Sélection de motif tdd pour un nœud de réseau d'accès WO2023287329A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2021/050724 WO2023287329A1 (fr) 2021-07-13 2021-07-13 Sélection de motif tdd pour un nœud de réseau d'accès

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2021/050724 WO2023287329A1 (fr) 2021-07-13 2021-07-13 Sélection de motif tdd pour un nœud de réseau d'accès

Publications (1)

Publication Number Publication Date
WO2023287329A1 true WO2023287329A1 (fr) 2023-01-19

Family

ID=84919551

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/050724 WO2023287329A1 (fr) 2021-07-13 2021-07-13 Sélection de motif tdd pour un nœud de réseau d'accès

Country Status (1)

Country Link
WO (1) WO2023287329A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020032842A1 (fr) * 2018-08-10 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) Configuration de rapport de csi basée sur un intervalle pour tdd dynamique
WO2020033513A1 (fr) * 2018-08-07 2020-02-13 Idac Holdings, Inc. Transmission et détection d'informations de commande dans des systèmes sans fil
WO2020074079A1 (fr) * 2018-10-11 2020-04-16 Nokia Technologies Oy Configuration de trame radio pour tdd coordonné dynamique
US20200205102A1 (en) * 2018-12-20 2020-06-25 Qualcomm Incorporated Flexible configuration of synchronization signal block time locations
US20200313793A1 (en) * 2019-03-25 2020-10-01 Lenovo (Singapore) Pte. Ltd. Method and apparatus for determining a duration of a repetition of a transport block

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020033513A1 (fr) * 2018-08-07 2020-02-13 Idac Holdings, Inc. Transmission et détection d'informations de commande dans des systèmes sans fil
WO2020032842A1 (fr) * 2018-08-10 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) Configuration de rapport de csi basée sur un intervalle pour tdd dynamique
WO2020074079A1 (fr) * 2018-10-11 2020-04-16 Nokia Technologies Oy Configuration de trame radio pour tdd coordonné dynamique
US20200205102A1 (en) * 2018-12-20 2020-06-25 Qualcomm Incorporated Flexible configuration of synchronization signal block time locations
US20200313793A1 (en) * 2019-03-25 2020-10-01 Lenovo (Singapore) Pte. Ltd. Method and apparatus for determining a duration of a repetition of a transport block

Similar Documents

Publication Publication Date Title
US10644777B2 (en) Channel state information reference signal (CSI-RS) for layer-3 (L3) mobility
CN108667591B (zh) 异构网络中的自适应ul-dl tdd配置
US8942758B2 (en) Method and device for link-characteristic based selection of supporting access nodes
US11943037B2 (en) Method and apparatus for beam failure recovery in a wireless communication system
KR20210006403A (ko) 하이브리드 자동 반복 요청(harq)을 위한 방법 및 장치
US20230388047A1 (en) Sidelink feedback
EP3711252B1 (fr) Configuration de "coreset" d'information système minimale restante dans un nouveau canal de diffusion physique radio
WO2019092859A1 (fr) Terminal utilisateur et procédé de communication sans fil
US11362716B2 (en) Extrapolated CSI report based on a multi-symbol reference signal
WO2014113941A1 (fr) Allocation de ressources dans un réseau de radiocommunication
EP3028397A1 (fr) Retransmission de communications dans un réseau mobile au moyen de groupes de petites cellules
JP7318703B2 (ja) 参照信号の送受信方法及び装置
EP3190850B1 (fr) Procédé d'ordonnancement de réseau sans fil et dispositif d'accès
CN113330788A (zh) 用于在功率节省模式下控制信道接收的系统和方法
US11622333B2 (en) User equipment group selection for direct link or sidelink packet transmission in broadcast
US11552691B2 (en) Beam recovery grouping
JP7313369B2 (ja) 端末、無線通信方法及びシステム
WO2021053006A1 (fr) Changement de profil de qualité de service d'une session à plusieurs profils qos
CN112997433B (zh) 用于harq传输的方法以及通信设备
US11411689B2 (en) Dynamic user grouping in non-orthogonal multiple access (NOMA)—networks
WO2021077372A1 (fr) Procédé et nœud de réseau d'accès pour gestion de faisceaux
US11240817B2 (en) Bandwidth allocation request in cellular mesh networks
WO2023287329A1 (fr) Sélection de motif tdd pour un nœud de réseau d'accès
CN115997427A (zh) 集成接入和回传(iab)节点之间的功率控制
CN114208058A (zh) 针对具有不同层数的bwp的自适应csi测量和报告

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21950307

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE