OA20678A - DCI signalling including at least one slot format indicator, SFI, field, and a frequency resource indicator field. - Google Patents
DCI signalling including at least one slot format indicator, SFI, field, and a frequency resource indicator field. Download PDFInfo
- Publication number
- OA20678A OA20678A OA1202200059 OA20678A OA 20678 A OA20678 A OA 20678A OA 1202200059 OA1202200059 OA 1202200059 OA 20678 A OA20678 A OA 20678A
- Authority
- OA
- OAPI
- Prior art keywords
- frequency resource
- wireless device
- sfi
- indicator
- dci
- Prior art date
Links
- VKMGSWIFEHZQRS-NSHDSACASA-N (1R)-1-(3,4-dichlorophenyl)-2-(propan-2-ylamino)ethanol Chemical compound CC(C)NC[C@H](O)C1=CC=C(Cl)C(Cl)=C1 VKMGSWIFEHZQRS-NSHDSACASA-N 0.000 title claims 14
- 230000011664 signaling Effects 0.000 title description 26
- 239000000969 carrier Substances 0.000 claims description 92
- 230000000875 corresponding Effects 0.000 claims description 60
- 230000005540 biological transmission Effects 0.000 claims description 45
- 238000004891 communication Methods 0.000 description 21
- 238000005259 measurement Methods 0.000 description 16
- 238000000034 method Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 9
- 239000003550 marker Substances 0.000 description 8
- 101710040583 Pbsn Proteins 0.000 description 6
- 241000700159 Rattus Species 0.000 description 4
- 238000001228 spectrum Methods 0.000 description 4
- 230000001413 cellular Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000001702 transmitter Effects 0.000 description 3
- 101710012765 45 Proteins 0.000 description 2
- 241001623015 Candidatus Bathyarchaeota Species 0.000 description 2
- 108060003189 GLE1 Proteins 0.000 description 2
- 101710027422 MAB_4487c Proteins 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 101700005582 apaH Proteins 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000006011 modification reaction Methods 0.000 description 2
- 201000001845 syndromic X-linked intellectual disability Snyder type Diseases 0.000 description 2
- LYBMHAINSFEHRL-UHFFFAOYSA-N 7-(diethylamino)-2-oxochromene-3-carbohydrazide Chemical compound C1=C(C(=O)NN)C(=O)OC2=CC(N(CC)CC)=CC=C21 LYBMHAINSFEHRL-UHFFFAOYSA-N 0.000 description 1
- 241000760358 Enodes Species 0.000 description 1
- 201000000194 ITM2B-related cerebral amyloid angiopathy 2 Diseases 0.000 description 1
- 101710036068 KIN7A Proteins 0.000 description 1
- 102100018193 PRAG1 Human genes 0.000 description 1
- 101700081364 PRAG1 Proteins 0.000 description 1
- 229940040608 SPS Drugs 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000002457 bidirectional Effects 0.000 description 1
- 101710014494 celI Proteins 0.000 description 1
- 230000020411 cell activation Effects 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- RQXLSXSKRKTNTK-UHFFFAOYSA-N diethyl 5-oxo-3-phenylpyrrolidine-2,2-dicarboxylate Chemical compound CCOC(=O)C1(C(=O)OCC)NC(=O)CC1C1=CC=CC=C1 RQXLSXSKRKTNTK-UHFFFAOYSA-N 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000003365 glass fiber Substances 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- -1 noise power Proteins 0.000 description 1
- 230000003287 optical Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static Effects 0.000 description 1
- 235000019527 sweetened beverage Nutrition 0.000 description 1
Abstract
Systems and methods for indicating availability of one or more frequency resources are provided herein. A wireless device receives a control message including at least one of a slot format indicator (SFI) field and a frequency resource indicator field. The wireless device can determine whether a particular frequency resource is available for operation in accordance with the frequency resource indicator.
Description
PCI SIGNALLING 1NCLLIHNG AT LEAST ON FORMAT INDICATOR. SFL FIELD. AND A FREQUENCY RE SOURCE INDICATOR FIELD
TECHNICAL FIELD
[0001] The présent disclosure general ly relates to wireless communications and wireless communication networks.
INTRODUCTION
[0002] Standard izati on bodies such as Third Génération Partnership Project (3GPP) are studying potential solutions for efficient operation of wireless communication in new radio (NR) networks. The next génération mobile wireless communication System 5G/NR will support a diverse set of use cases and a diverse set of deployment scénarios. The later includes deployment at both low frequencies (e.g. lOOsof MHz), similarto LTE today, and very high frequencies (e.g. mm waves in the tens of GHz).
[0003] Similarto LTE, NR uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (i.e. from a network node, gNB, eNB, or base station, to a user equipment or UE). In the uplink (i.e. from UE to gNB), both DFT-spread OFDM and OFDM can be supported.
[0004] The basic NR physical resource over an antenna port can thus be seen as a tîmefrequency grid as illustrated in Figure 1, where a resource block (RB) in a 14-symbol slot ts shown. A resource block corresponds to 12 contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the System bandwidth. Each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval.
[0005] Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (also referred to as different numerologies) are given by Δί=(15χ2Λα) kHz where cÆ(0,1,2,3,4). Af=15kHz is the basic (or reference) subcarrier spacing that is also used in LTE.
[0006] In the time domain, downlink and uplink transmissions in NR will be organized into equally-sized subframes of 1ms each, similarto LTE. A subframe can be furtherdivided into multiple slots of equal duration. The slot length for subcarrier spacing Af=(15x2Aa) kHz is 1/2Λα ms. There is only one slot per subframe for Af=15kHz and a slot consists of 14 OFDM symbols.
[0007] Downlink (DL) transmissions are dynamically scheduled, î.e., in each slot the gNB transmits downlink control information (DCI) about which UE data is to be transmitted to and which resource blocks in the current downlink slot the data is transmitted on. This control information is typically transmitted in the first one or two OFDM symbols in each slot in NR. The control information is carried on the Physical Downlink Control Channel (PDCCH) and the data is carried on the Physical Downlink Shared Channel (PDSCH). A UE first detects and décodés PDCCH and if a PDCCH is decoded successfully, it then décodés the corresponding PDSCH based on the downlink assignment provided by decoded control information in the PDCCH.
[0008] In addition to PDCCH and PDSCH, there are also other channels and reference signais transmitted in the downlink, including SSB, CS1-RS, etc.
[0009] Uplink (UL) data transmissions, carried on Physical Uplînk Shared Channel (PUSCH), are also dynamically scheduled by the gNB by transmitting a DCI. The DCI, which is transmitted in the DL région, always indicates a scheduling offset so that the PUSCH is transmitted in a slot in the UL région.
[0010] In NR, both semi-statically configured time division duplex (TDD) and dynamic TDD are supported. For the latter, the scheduling DCI (e.g. DL assignment / UL grant) indicates which symbols within a slot are to be used for DL réception and UL transmission by the UE.
[0011] For semi-static TDD, the configuration of uplink-downlink patterns is flexible. For a particular slot within the TDD pattern, symbols may be configured as eîther downlink (denoted ‘D’), uplink (denoted ‘U’), or flexible (denoted ‘F’). One use of symbols classified as T’is to create a guard period for DL-to UL or UL-DL transitions for half-duplex devices (e.g. half-duplex FDD or TDD). A cell spécifie TDD pattern is either provided by System information block (SIB) (standalone operation) or by radio resource control (RRC) (nonstandalone operation) signaiing. Additionally, a UE-specific TDD pattern can be configured to override symbols of the cell-specific configuration which are classified as flexible (‘F’). [0012] For dynamic TDD where the UL/DL allocation may vary depending on the scheduling DCI, it can be useful to indicate to a group of UEs what the instantaneous TDD pattern looks like for the current and potentially future slots. This is achieved through group common sîgnaling (GC-PDCCH) carrying a DCI message with Format 2_0. DCI Format 2_0 contains one or more Slot Format Indicators (SF1) indicating which symbols are classified as ‘D’, ‘U’, or ‘F’ within each ofthe indicated slots.
[0013| Semi-static Uplink-Downlink Configuration
[0014] Cell-specific semi-static configuration of the TDD pattern(s) is provided from the network to the UE by the information element (IE) TDD-UL-DL-ConfigCommon, as described in 3GPP TS 38.331 “Radio Resource Control (RRC) Protocol Spécification”:
TDD-UL-DL~ConfigCommon ::= referenceSubcarrierSpacing patternl pattern2
OPTIONAL, -- Need R
SEQUENCE {
SubcarrierSpacing, TDD-UL-DL-Pattern, TDD-UL-DL-Pattern
TDD-UL-DL-Pattern ::= dl-UL-TransmissionPeriodicity mslp25, ms2 , ms2p5, ms5, mslO), nrofDownlinkSlots nrofDownlinkSymbols nrofUplinkSlots nrofUpl·LnkSyIπbols
SEQUENCE {
ENUMERATED {ms0p5, ms0p625, msl
INTEGER (0..maxNrofSlots),
INTEGER (0..maxNrofSymbol·s-1),
INTEGER (0..maxNrofSlots),
INTEGER (0..maxNrofSymbols-1),
[ [ dl-UL-TransmissionPeriodl·cl·ty-vl530 ENUMERATED (ms3, msl) OPTIONAL — Need R
[0015] This IE provides the option to provide up to two concatenated TDD patterns (patternl, pattem2) each with their own periodicity. There is a constraint that the concatenated pattern must hâve a total periodicity that divides 20ms evenly in order to align with the default SS/PBCH block periodicity of 20ms assumed by the UE upon accessing a cel! i.e. devices that are doing initia! cell search or devices in inactive/ïdle State doing cell search for mobility.
[0016] For each of the one or two concatenated patterns, the above IE defines the TDD pattern as follows;
[0017] Number of full DL slots, where ail symbols of these slots are classified as ‘D’ by nrojDownlinkSlots.
[0018] Number of symbols classifîed as ‘D’ in a partial DL slot following the last full DL slot by nrofDownlinkSymbols.
[0019] Number of symbols classifîed as ‘U’ in a partial LJL slot preceding the first full UL by nrofUplinkSymbols.
[0020] Number of full UL slots, where ail symbols of these slots are classifîed as 4U’ by nrofidplinkSlots.
|0021] Periodicity, in ms, after which the pattern repeats by dl-ULTransmissionPeriodicity.
[0022] Ail symbols not classifîed as either ‘D’ or 4 U’ are assumed to be classifîed as 4F’. [0023] Figure 2 illustrâtes some example cell-specîfic TDD patterns that can be configured semi-statically by the TDD-UL-DL-ConfigCommon IE.
[0024] As mentioned, an individual UE can be semi-statically configured with a UEspeciflc TDD pattern that overrides parts of the ce 11-specifically configured pattern. UEspecific semi-static configuration of a TDD pattern is provided from the network to the UE by the information element TDD-UL-DL-ConfigDedicated·.
TDD-UL-DL-ConfigDedicated ::= SEQUENCE { slotSpecificConfigurationsToAddModList SEQUENCE (SIZE (1..maxNrofSlotsH OF TDD-UL-DL-SlotConfig OPTIONAL, — Need N slotSpecificConfigurationsToreleaseList SEQUENCE (SIZE (1..maxNrofSlotsH OF TDD-UL-DL-Slotlndex OPTIONAL, — Need N
TDD-UL-DL-SlotConfig ::= slotlndex symbols allDownlink allUplink explicit nrofDownlinkSymbols (1..maxNrofSymbols-1)
Need S nrofUplinkSymbols (1..maxNrofSymbols-1)
Need S
SEQUENCE {
TDD-UL~DL~SlotIndex, CHOICE {
NULL,
NULL, SEQUENCE (
INTEGER
OPTIONAL, —
INTEGER
OPTIONAL — } }
TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrcfSlots-11
[0025] This IE contains a list of slots within the cell spécifie TDD pattern for which the symbol classification should be overrîdden. However, this override can only be applied to symbols classified as flexible (‘F’). For each indicated slot, the flexible symbols can be reclassîfied as ‘allDownlink’, ‘ailUplink’, or ‘explicit’. For ‘explîcif, the number of symbols at the beginning of the slot classified as ‘D’is configured, and the number of symbols at the end of the slot classified as ‘U’ is configured.
[0026] Dynamic Indication of Uplink-Downlink Configuration by PCI format 2 0 [0027] As mentioned, in the case of dynamic TDD where the UL/DL allocation may vary depending on the scheduiing DCI, it can be useful to indicate to a group of UEs what the înstantaneous TDD pattern looks like for the current and potentially future slots. This is achieved by signaling of one or more slot format indicators (SFI) in DCI Format 2_0 carrîed by the group common control channel (GC-PDCCH). Each SFI indicates which symbols in a slot are classified as ‘D’, ‘U’, or T’. The indicated SFI(s) cannot override symbols that are already semi-statîcally configured as ‘D’ or ‘U’; however, an SFI can indicate the direction (‘D’ or ‘U’) for symbols classified as flexible (‘F’). If the SFI indicates ‘F’ for symbols already classified as ‘F’, and PDCCH does not schedule any data or trigger reference signais in those symbols, then the UE shall neither transmit nor receive on those symbols. This can be useful to cancel an instance of a periodically transmitted/received reference signais (e.g. SRS, CSI-RS) to croate “reserved resources” for use by another technology, e.g., LTE. It can also be useful to create reserved resources (e.g. no transmission or réception by any UE) in the case that the SFI indicates ‘F’ for a symbol that is already semi-statically configured.
[0028] in NR, a semi-static/static indication of direction of transmission is not a viable option since the transmission from gNB dépends on the Listen-Before-Talk (LBT) outcome and the gNB does not know when it can acquire the channel. The transmission direction would be decided on the spot and according to LBT success occasion. Thus. ail the symbols can be considered as F before the channel is captured.
[0029] As described in 3GPP TS 38.212 15.2.0 (2018-06), clause 7.3.1.3.1, SFI is carried by DCI format 2_0 containing the following information:
Slot format indicator 1, Slot format indicator 2,Slot format indicator N.
[0030] The sîze of DCI format 2_0 is configured by higher layer parameter up to 128 bits.
[0031] Further, as described in 3GPP TS 38.213 15.2.0 (2018-06), clause 11.1.1., each “Slot format îndicator” or “SFI index” field in DCI format 2_0 indicates to a group of UEs a “s lot format” of each s lot for a period of transmission in each DL or UL bandwidth part (BWP) or UL BWP, starting from the slot where UEs detect PDSCH carrying the DCI format 2_0. This clause applies a set of serving cells configured by higher layer parameter SlotFormatlndicator:
-- ASN1START
-- TAG-SLOTFORMATINDICATOR-START
SlotFormatlndicator ::= SEQUENCE { sfi-RNTI RNTI-Value, dci-PayloadSize INTEGER (1..maxSFI-DCI-PayloadSize), slotFormatCombToAddModList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup}} OF SlotFormatCombinationsPerCe11
OPTIONAL, — Need N slotFormatCombToReleaseList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, — Need N )
— TAG-SLOTFORMATINDICATOR-STOP — ASN1ST0P
[0032] As shown in the above IE, the LJE îs provided with sfï-RNTl and the payload size of DCI format 2_0 by dci-payloadSize.
[0033] Further, for each serving cell in the set of serving cells indicated in SlotFormatlndicator, the UE is provided with slotFormalCombinationsPercell which configures the parameters used for interprétation of each SFI-îndex fîeld for the corresponding serving cell.
— ASN1START — TAG-S LOTFORMAT COMBINATION S PERCE L L-S TART
SlotFormatCornbinationsPerCell : := SEQUENCE { servingCellId ServCellIndex, subcarrierSpacing SubcarrierSpacing, subcarrierSpacing2 SubcarrierSpacing
OPTIONAL, — Need R slotFormatCombinatiens SEQUENCE (SIZE (1..maxNrofSlotFormatCombinationsPerSet}) OF SlotFormatCombination
OPTIONAL, — Need M positionlnDCI
PayloadSi ze-1)
INTEGER(0..maxSFI-DCIOPTIONAL, — Need M }
SlotFormatCombination ::= SEQUENCE { siotFormatCombinationld SlotFormatCombinationld, slotFormats SEQUENCE (SIZE (1..maxNrofSlotFormatsPerCombination)) OF INTEGER (0..255) }
SiotFormatCombinationld INTEGER (0..maxNrofSlotFormatCombinatiensPerSet-1) — TAG-SLOTFORMATCOMBINATIONSPERCELL-STOP — ASN1STOP
[0034] According to above IE. the following parameters are configured for each serving ce!I using the SlotFormatCornbinationsPerCell:
[0035] - An identity of the serving ce 11 by servingCelllD.
[0036] - The location of SFI-index field in the DCT (i.e. “slot format îndicator x” in DCI format 2_0) by positionlnDCI for correspond ing servingCelllD.
[0037] - A set of slot format combinations by slotFormatCombinations which comprise a sequence of SlotFormatCombinations. This can be interpreted as hash table where each “key” here indicated by SlotFormatCombinationID refèrring to a spécifie “slotFormatCombinatiorF in the table, and each SlotFormatCombination îtself includes two parameters:
[0038] (1) One or more slot formats (configured by maxNrofSlotFormatCombinationsPerSet whîch could be up to 256 slots) îndicated by 5 slotFormats.
[0039] (2) The slotFormats comprise of sequence of indices from 0,..., 256. Each index refers to a slot format in the table 11.1.1-1 in clause 11.1.1. in 3GPP TS 38.213 as will be explained below.
[0040] - A mapping for the slot format combination provided by slotFormats to a corresponding SFI-index field value in DCI format 2_0 provided by the slotFormatCombinationlD.
[0041] Table 11.1.1-1 below from 3GPP TS 38.213 contaîns a list of possible slot formats. An SFI is simply an integer that takes a value from the range (0 ... 55) or the value 255. Values in the range (56 ... 254) are currently reserved for future use. Each integer value 15 points to a row in the table, where each row indicates the classification for ail 14 OFDM symbols in a slot.
| Format | 0 | 1 | 2 | 3 | 4 | Symbc 5 | >l num 6 | ber in 7 | a stot 8 | 9 | 10 | 11 | 12 | 13 |
| 0 | D | D | D | D | D | D | D | D | D | D | D | D | D | D |
| 1 | U | U | U | U | U | U | U | U | U | U | U | U | U | U |
| 2 | F | F | F | F | F | F | F | F | F | F | F | F | F | F |
| 3 | D | D | D | D | D | D | D | D | D | D | D | □ | □ | F |
| 4 | D | D | D | D | D | D | D | D | D | D | D | D | F | F |
| 5 | D | D | D | D | D | D | D | D | D | D | D | F | F | F |
| 6 | D | D | D | D | D | D | D | D | D | D | F | F | F | F |
| 7 | D | D | D | D | D | D | D | D | D | F | F | F | F | F |
| 8 | F | F | F | F | F | F | F | F | F | F | F | F | F | U |
| 9 | F | F | F | F | F | F | F | F | F | F | F | F | U | U |
| 10 | F | U | U | U | U | U | U | U | U | U | U | U | U | U |
| 11 | F | F | U | U | U | U | U | U | U | U | U | U | U | U |
| 12 | F | F | F | U | U | U | U | U | U | U | U | U | U | U |
| 13 | F | F | F | F | U | U | U | U | U | U | U | U | U | U |
| 14 | F | F | F | F | F | U | U | U | U | U | U | U | U | U |
| 15 | F | F | F | F | F | F | U | U | U | U | U | U | U | U |
| 16 | D | F | F | F | F | F | F | F | F | F | F | F | F | F |
| 17 | D | D | F | F | F | F | F | F | F | F | F | F | F | F |
| 18 | D | D | D | F | F | F | F | F | F | F | F | F | F | F |
| 19 | 0 | F | F | F | F | F | F | F | F | F | F | F | F | U |
| 20 | D | D | F | F | F | F | F | F | F | F | F | F | F | U |
| 21 | D | D | D | F | F | F | F | F | F | F | F | F | F | U |
| 22 | D | F | F | F | F | F | F | F | F | F | F | F | U | U |
| 23 | 0 | D | F | F | F | F | F | F | F | F | F | F | U | U |
| 24 | D | D | D | F | F | F | F | F | F | F | F | F | U | U |
| 25 | D | F | F | F | F | F | F | F | F | F | F | U | U | U |
| 26 | D | D | F | F | F | F | F | F | F | F | F | U | U | U |
| 27 | D | D | D | F | F | F | F | F | F | F | F | U | U | U |
| 28 | D | D | D | D | D | D | D | D | □ | D | D | D | F | U |
| 29 | D | D | D | D | D | D | D | □ | □ | D | D | F | F | U |
| 30 | D | D | D | D | D | D | D | D | □ | D | F | F | F | U |
| 31 | D | D | D | D | D | D | D | D | D | D | D | F | U | U |
| 32 | D | D | D | D | D | D | D | D | D | D | F | F | U | U |
| 33 | D | D | D | D | D | 0 | 0 | D | D | F | F | F | U | U |
| 34 | D | F | U | U | U | U | U | U | U | U | U | U | U | U |
| 35 | D | D | F | U | U | U | U | U | U | U | U | U | U | U |
| 36 | D | D | D | F | U | U | U | U | U | U | U | U | U | U |
| 37 | □ | F | F | U | U | U | U | U | U | U | U | U | U | U |
| 38 | D | D | F | F | U | U | U | U | U | U | U | U | U | U |
| 39 | D | D | D | F | F | U | U | U | U | U | U | U | U | U |
| 40 | D | F | F | F | U | U | U | U | U | U | U | U | U | U |
| 41 | D | D | F | F | F | U | U | U | U | U | U | U | U | U |
| 42 | D | D | D | F | F | F | U | U | U | U | U | U | U | U |
| 43 | D | D | D | D | 0 | D | D | D | D | F | F | F | F | U |
| 44 | D | D | D | D | D | D | F | F | F | F | F | F | U | U |
| 45 | D | D | D | D | D | D | F | F | U | U | U | U | U | U |
| 46 | D | D | D | D | D | F | U | D | D | D | D | D | F | U |
| 47 | D | D | F | U | U | U | U | D | D | F | U | U | U | U |
| 48 | D | F | U | U | U | U | U | D | F | U | U | U | U | U |
| 49 | D | D | D | D | F | F | U | D | D | D | D | F | F | U |
| 50 | D | D | F | F | U | U | U | D | D | F | F | U | U | U |
| 51 | D | F | F | U | U | U | U | D | F | F | U | U | U | U |
| 52 | D | F | F | F | F | F | U | D | F | F | F | F | F | U |
| 53 | D | D | F | F | F | F | U | D | D | F | F | F | F | U |
| 54 | F | F | F | F | F | F | F | D | D | D | D | D | D | D |
| 55 | D | D | F | F | F | U | U | U | D | D | D | D | D | D |
| 56 - 254 | Reserved | |||||||||||||
| 255 | UE détermines the slot format for the slot based on TDD-UL-DL-ConfigurationCommon, or TDD-UL-DL-ConfigDedicated and, if any, on detected DCI formats |
3GPP TS 38.213 Table 11.1.1-1: Slot formats for normal cyciic prefix
[0042] According to the spécification as described above, DCI Format 2_0 carries slot format indicators (SFIs) to a group of UEs for the current slot and possibly a number of future slots. To limitthe DCI overhead, atable of slot format combinations ispre-confîgured 5 semi-statically by RRC signaling. A particular row in the table contaîns SFIs for up to a maximum of 256 slots. The number of slot-format combinations in the table (rows) is up to a maximum of 512. The maximal configuration for the table îs illustrated in Table 1 where SFIm n is the SF1 for the nth slot (nth column) of the mth slot format combination (m* row). [0043] Table 1 illustrâtes an example RRC configuration of slot format combination table (maximal configuration). Each entry in the table is an SFI pointing to a row in 3GPP TS 38.213 Table 11.1.1-1. The maximum number of combinations is 512, and the maximum number of slots for a gîven combination îs 256.
| Slot Format Combinations ID | Slot-0 | Slot-1 | Slot0255 | |
| 0 | SFI 0,0 | SFIo.. | sfU5 |
| 1 | SF1u | |||
| : | : | ; | ||
| 511 | Sn 5!l,0 | SF’51U | SFI 511,255 |
Table 1
[0044] As explained, the DCI Format 2_0 message indicates (e.g. points to) a slotFormatCombinationID (the row number in the table) for a spécifie serving cell în corresponding SFI-Index field. The position of the SFI-Index field for the corresponding serving cell starts from the “positionlnDCF bit in the DCI configured in SlotFormatCombinationsPerCell and ends at the begînnîng of the position of the next SFIindex in DCI.
[0045] Note that this table shows the maximal configuration. A typical configuration may include many fewer rows and columns.
[0046] Figure 3 illustrâtes an example of configuration for a serving cell with ServmgCellID = 3 where thepositîonlnDCIvalue for this serving cell equals 8 which means that the SFI-index for the serving cell starts at bit 8 (counting from 0). It is noted that 4 slot format combinations are configured for this cell each with a slotformats indicatîng 6 consecutive slot patterns. This means the LJE should assume a format will be indicated în the DCI by SFl-index for the next 6 slots from the point of detecting the GC-PDDCH carrying the DCL For this example, the DCI is indicating the last slotFormatCombination in the SloiFormatCombinations which is indicated by slotFormatCombinationID = 3, therefore the SFI index corresponds to bit values “11”. And the DCI becomes xxxxxxxxl Ixx... (the x’s are SFI-indices set for other serving cells).
[0047] NR. în Unlicensed Spectrum (NR-O
[0048] For a node (e.g., NR-U gNB/UE, LTE-LAA eNB/UE, or WiFi AP/STA)) to be allowed to transmit in unlicensed spectrum (e.g., 5GHz band), it typically needs to perform a clear channel assessment (CCA). This procedure typîcally includes sensing the medium to be îdle for a number of time intervals. Sensing the medium to be idle can be done in different ways, e.g. by using energy détection, preamble détection and/or using Virtual carrier sensing. The latter implies that the node reads control information from other transmitting nodes informing when a transmission end. After sensing the medium to be idle, the node is typîcally allowed to transmit for a certain amount of time, sometimes referred to as transmission opportunity (TXOP). The length of the TXOP dépends on régulation and type of CCA that has been performed, but typically ranges from 1 ms to 1 Oms. This duration is often referred to as a COT (Channei Occupancy Time), as shown in 3GPP TS 37.213 “Physical layer procedures for shared spectrum channei access” Tables 4.1.1-1 and 4.2.1-1. [0049] In Wi-Fi, feedback of data réception acknowledgements (ACKs) is transmitted without performîng clear channei assessment. Preceding feedback transmission, a small duration (called SIFS) is introduced between the data transmission and the corresponding feedback which does not include actual sensing of the channei. In 802.11, the SIFS perîod (16 ps for 5 GHz OFDM PHYs) is defined as:
aSIFSTime = aRxPHYDelay + aMACProcessingDelay + aRxTxTurnaroundTime [0050] · aRxPHYDelay deftnes the duration needed by the PH Y layer to deltver a packet to the MAC layer
[0051] aMACProcessingDelay deftnes the duration that the MAC layer needs to trigger the PHY layer transmitting a response
[0052] · aRxTxTurnarottndTime de fi nés the duration needed to turn the radio from réception into transmit mode
[0053] Therefore, the SIFS duration is used to accommodate for the hardware delay to switch the direction from réception to transmission.
[0054] In NR-U bands, a similar gap to accommodate for the radio turnaround time can be allowed, as per 3GPP TR 38.899 16.0.0 (2018-02) “Study on NR-based access to unlicensed spectrum”. This can enable the transmission of PUCCH carryîng UCI feedback as well as PUSCH carryîng data and possible UCI within the same transmit opportunity (TXOP) acquired by the initiatîng gNB. For example, the UE can transmit feedback without performîng clear channei assessment before PUSCH/PUCCH transmission as long as the gap between DL and UL transmission is less than or equal to 16 us. When the gap between DL and UL is largerthan 25 us, the UE can transmit feedback after 25 us CCA is successful. Operation in this manner is referred to as “COT sharing.”
[0055] Figure 4 illustrâtes example TXOPs both with and without COT sharing after CCA ïs successful at the gNB.
From SHARP: Downlink structure and procedure for NR-U operation, vol. RAN WG1, no. Reno, USA; 20190513 - 20190517, (20190513), 3GPP DRAFT; Rl-1907210, 3RD GENERATION PARTNERSH1P PROJECT (3GPP), MOBILE COMPETENCE
CENTRE; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG 1, no. Reno, USA; 20190513 - 20190517 13 May 2019 it is known to support frequency domain occupancy indication for NR-U. An easiest way is to put SFI PDCCH in every LBT bandwidth. and each indicates ail or a part of the COT structure in the respective LBT bandwidth. Another option is to put a single SFI PDCCH which indicates time and frequency domain occupancy in the BWP.
SUMMARY
[0056] It îs an object of the présent disclosure to obviate or mitigate at least one disadvantage of the prior art.
[0057] There are provided Systems and methods for indicating avaîlability of configured resources.
[0058] In a first aspect there is provided a method performed by a wireless device. The wireless device comprises a radio interface and processing circuitry and can be configured to configure the wireless device with a piuraiity of frequency resources. The wireless device receives a downlink control information (DCI) message including at least one slot format indicator (SFI) field and a frequency resource indicator field. The SFI indicates a slot format for a corresponding frequency resource. The frequency resource indicator indicates whether the corresponding frequency resource is available for operation. The wireless device détermines whether the corresponding frequency resource is available for operation in accordance with the frequency resource indicator.
[0059] In some embodiments, configuring the wireless device includes receiving configuration information from a network node. The piuraiity of frequency resources can include one or more of: a carrier, a sub-band of a carrier, a set of resource blocks (RBs) on a carrier, a listen before taîk (LBT) bandwidth, and a bandwidth part (BWP).
[0060] In some embodiments, the DCI message is à DCI format 2_0.
[0061] In some embodiments, determining whether the corresponding frequency resource is available for operation can include determining if the çorresponding frequency resource is available for operation durîng a duration of the SFI in accordance with the frequency resource indicator.
[0062] In some embodiments, the DCI message further includes an associated channel occupancy time (COT) duration field. The wireless device can détermine whether the corresponding frequency resource is available for operation during the COT duration in accordance with the frequency resource indicator.
[0063J In some embodiments. the wireless device identifies the corresponding frequency resource based at least in part on a bit position of the frequency resource indicator field in the received DCI message. In some embodiments, the frequency resource indicator comprises a plurality of bits wherein each bit corresponds to one of the plurality of frequency resources.
[0064] In some embodiments, responsive to determining that the corresponding frequency resource is availabié for operation, the wireless device monitors the frequency resource. The wireless device can monitor the frequency resource for a physical downlink control channel (PDCCH). In some embodiments, responsive to determining that the corresponding frequency resource is availabie for operation, the wireless device receives a channel-state information reference signal (CSI-RS) on the frequency resource.
[0065] In some embodiments, responsive to determining that the corresponding frequency resource is not availabie for transmission/receptîon, the wireless device does not monitor the frequency resource.
[0066] In some embodiments, the wireless device détermines that the SFI field corresponds to a reserved value in a frequency resource configuration; and déterminés a number of slots for which the frequency resource is unavaîlable in accordance with the reserved value.
[0067] In another aspect there is provided a method performed by a network node. The network node comprises a radio interface and processing circuitry and can be configured to generate a downlink control information (DCI) message including at least one slot format indicator (SFI) field and a frequency resource indicator field. The SFI indicates a slot format for a corresponding frequency resource. The frequency resource indicator indicates whether the corresponding frequency resource is availabie for operation. The network node transmits the generated DCI message to one or more wireless devices.
[0068] In some embodiments, the network node configures one or more wireless devices with a plurality of frequency resources. Configuring the one or more wireless devices can include transmitting configuration information. In some embodiments, the plurality of frequency resources can include one or more of: a carrier, a sub-band of a carrier, a set of resource blocks (RBs) on a carrier, a listen before talk (LBT) bandwidth, and a bandwidth part (B WP).
[0069] In some embodiments, the DCI message is a DCI format 2_0.
[0070] In some embodiments, a bit position of the frequency resource indicator field in the received DCI message identifies a corresponding frequency resource.
[0071] In some embodiments, the network node transmits a channel-State information reference signal (CSI-RS) on an availabié frequency resource.
[0072] Other aspects and features of the présent disclosure will become apparent to those ordinarily skilled in the art upon review of the following description of spécifie embodiments in conjunction with the accompanying figures.
[0073] BRIEF DESCRIPTION OF THE DRAWINGS
[0074] Embodiments of the présent disclosure will now be described, by way of example only, with reference to the attached Figures, wherein:
[0075] Figure 1 illustrâtes an example of NR physical resources;
[0076] Figure 2 illustrâtes example semi-statîcally configured cell-specific TDD patterns;
[0077] Figure 3 illustrâtes an example slot format combination;
[0078] Figure 4 illustrâtes example transmit opportunities;
[0079] Figure 5 illustrâtes an example wireless network;
[0080] Figure 6 illustrâtes an example of signaling in a wireless network;
]0081] Figure 7 is an example signaling diagram;
[0082] Figure 8 is a flow chart illustrating a method which can be performed in a wireless device;
[0083] Figure 9 is a flow chart illustrating a method which can be performed in a network node;
[0084] Figure 10 is a block diagram of an example wireless device;
[0085] Figure 11 is a block diagram of an example wireless device with modules;
[0086] Figure 12 is a block diagram of an example network node;
[0087] Figure 13 is a block diagram of an example network node with modules; and
[0088] Figure 14 is a block diagram of an example virtualized processing node.
DETAILED DESCRIPTION
[0089] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein.
[0090] In the following description, numerous spécifie details are set forth. However, it is understood that embodiments may be practiced without these spécifie details. In other instances, well-known circuits, structures, and techniques hâve not been shown in detail in order not to obscure the understandîng of the description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue expérimentation.
[0091] Référencés in the spécification to “one embodiment,” “an embodiment,” “an example embodiment.” etc., indicate that the embodiment described may include a partîcular feature, structure, or characteristic, but every embodiment may not necessarily include the partîcular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a partîcular feature, structure, or characteristic is described in connection with an embodiment, it is submîtted that it is wîthin the knowledge of one ski lied in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0092] In some embodiments, the non-limiting term “user equipment” (UE) is used and it can refer to any type of wireless device which can communicate with a network node and/or with another UE in a cellular or mobile or wireless communication System. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, personal digital assistant, tabiet, mobile terminal, smart phone, laptop embedded equîpped (LEE), laptop mounted equipment (LME), USB dongles, ProSe UE, V2V UE, V2X UE, MTC UE, eMTC UE, FeMTC UE, UE Cat 0, UE Cat Ml, narrow band ioT (NB-IoT) UE, UE Cat NB1, etc. Example embodiments of a UE are described in more detail herein with respect to Figure 10.
[0093] In some embodiments, the non-limiting term “network node” is used and it can correspond to any type of radio access node (or radio network node) or any network node, which can communicate with a UE and/or with another network node in a cellular or mobile or wireless communication System. Examples of network nodes are NodeB, MeNB, SeNB, a network node belonging to MCG or SCG, base station (BS), muIti-standard radio (MSR) radio access node such as MSR BS, eNodeB, network control 1er, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna System (DAS), core network node (e.g. MSC, MME, etc.), O&M, OSS, Self-organizing Network (SON), positioning node (e.g. E-SMLC), MDT, test equipment, etc. Example embodiments of a network nodeare described in more detail below with respect to Figure 12.
[0094] In some embodiments, the term “radio access technology” (RAT) refers to any RAT e.g. UTRA, E-UTRA, narrow band internet of things (NB-ïoT), WiFi, Bluetooth, next génération RAT (NR), 4G, 5G, etc. Any of the first and the second nodes may be capable of supporting a single or multiple RATs.
[0095] The term “radio node” used herein can be used to dénoté a wireiess device or a network node.
[0096] In some embodiments, a UE can be configured to operate in carrier aggregation (CA) implying aggregation of two or more carriers in at least one of downlink (DL) and uplink (UL) directions. With CA, a UE can hâve multiple serving cells, wherein the term ‘serving’ herein means that the UE is configured with the correspondîng serving cell and may receîve from and/or transmit data to the network node on the serving cell e.g. on PCell or any of the SCells. The data is transmitted or received via physical channels e.g. PDSCH în DL, PUSCH in UL, etc. A component carrier (CC) also interchangeably called as carrier or aggregated carrier, PCC or SCC is configured at the UE by the network node using higher layer signaling e.g. by sending RRC configuration message to the UE. The configured CC is used by the network node for serving the UE on the serving cell (e.g. on PCell, PSCell, SCeil, etc.) of the configured CC. The configured CC is also used by the UE for performîng one or more radio measurements (e.g. RSRP, RSRQ, etc.) on the cells operatîng on the CC, e.g. PCell, SCell or PSCell and neighboring cells.
[0097] In some embodiments, a UE can also operate in dual connectivity (DC) or multîconnectivity (MC). The multicarrier or multicarrier operation can be any of CA, DC, MC, etc. The term “multicarrier’ can also be interchangeably called a band combination.
[0098] The terni “radio measurement” used herein may refer to any measurement performed on radio signais. Radio measurements can be absolute or relative. Radio measurements can be e.g. intra-frequency, inter-frequency, CA, etc. Radio measurements can be unîdirectional (e.g., DL or UL or in either direction on a sidelink) or bidirectional (e.g., RTT, Rx-Tx, etc.). Some examples of radio measurements: timing measurements (e.g., propagation delay, TOA, timing advance, RTT, RSTD, Rx-Tx, etc.), angle measurements (e.g., angle of arrivai), power-based or channel quality measurements (e.g..
path loss, received signal power, RSRP, received signal quality, RSRQ, SINR, SNR, interférence power, total interférence plus noise, RSS1, noise power, CS1, CQI, PM], etc.), cell détection or cell identification, R LM, SI reading, etc. The measu rement may be performed on one or more links in each direction, e.g., RSTD or relative RSRP or based on signais from different transmission points of the same (shared) cell.
[0099] The term “signaling” used herein may comprise any of: high-layer signaling (e.g., via RRC or a like), lower-layer signaling (e.g., via a physical control channel or a broadcast channel), or a combination thereof. The signaling may be implicit or explicit. The signaling may further be unicast, multicast or broadcast. The signaling may also be directly to another node or via a third node.
[0100] The term “time resource” used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources include: symbol, time slot, sub-frame, radio frame, TTI, interleaving time, etc. The term “frequency resource” may refer to sub-band within a channel bandwîdth, subcarrier, carrier frequency, frequency band. The term “time and frequency resources” may refer to any combination of time and frequency resources.
[0101] Some examples of UE operation include: UE radio measurement (see the term “radio measurement” above), bidîrectîonal measurement with UE transmitting, cell détection or identification, beam détection or identification, system information reading, channel receiving and decoding, any UE operation or activity involving at least receiving of one or more radio signais and/or channels, cell change or (re)selection, beam change or (re)selection, a mobility-related operation, a measurement-related operation, a radio resource management (RRM)-related operation, a positioning procedure, a timing related procedure, a timing adjustment related procedure, UE location tracking procedure, time trackîng related procedure, synchronization related procedure, MDT-like procedure, measurement collection related procedure, a CA-related procedure, serving cell activation/deactivation, CC configuration/de-configuration, etc.
[0102] Note that the description given herein focuses on a 3GPP cellular communications System and, as such, 3 G PP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.
[0103] Note that, in the description herein, reference may be made to the term “cell”. However, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.
[0104] Figure 5 illustrâtes an example of a wireless network 100 that can be used for wireless communications. Wireless network 100 includes wireless devices, such as LJEs 110A-110B, and network nodes, such as radio access nodes 120A-120B (e.g. eNBs, gNBs, etc.), connected to one or more core network nodes 130 via an interconnecting network 125. The network 100 can use any suitable deployment scénarios. UEs 110 within coverage area 115 can each be capable of communicating directly with radio access nodes 120 over a wireless interface. In some embodiments, UEs 110 can also be capable of communicating with each other via D2D communication.
[0105] As an example, UE 110A can communicate with radio access node 120A over a wireless interface. That îs, UE 110A can transmit wireless signais to and/or receive wireless signais from radio access node 120A. The wireless signais can contain voice traffic, data traffic, control signais, and/or any other suîtabie information. In some embodiments, an area of wireless signal coverage 115 associated with a radio access node 120 can be referred to as a celi.
[0106] The interconnecting network 125 can refer to any interconnecting System capable of transmitting audio, video, signais, data, messages, etc., or any combination of the preceding. The interconnecting network 125 can include ail or a portion of a public swïtched téléphoné network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, régional, or global communication or computer network such as the Internet, a wîreline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof.
[0107] In some embodiments, the network node 130 can be a core network node 130, managing the establishment of communication sessions and other varions other functionalities for UEs 110. Examples of core network node 130 can include mobile switching center (MSC), MME, servîng gateway (SGW), packet data network gateway (PGW), operation and maintenance (O&M), operations support System (OSS), SON, positionîng node (e.g., Enhanced Servîng Mobile Location Center, E-SMLC), MDT node, etc. UEs 110 can exchange certain signais with the core network node using the non-access stratum layer. In non-access stratum signaling, signais between UEs 110 and the core network node 130 can be transparently passed through the radio access network. In some embodiments, radio access nodes 120 can interface with one or more network nodes 130 over an internode interface.
[0108] In some embodiments, radio access node 120 can be a “distributed” radio access node in the sense that the radio access node 120 components, and their associated fonctions, can be separated into two main units (or sub-radio network nodes) which can be referred to as the centra! unît (CU) and the distrîbuted unit (DU). Different dîstributed radio network node architectures are possîbie. For instance, in some architectures, a DU can be connected to a CU via dedicated wired or wireless lînk (e.g., an optical fiber cable) while in other architectures, a DU can be connected a CU via a transport network. Also, how the various fonctions of the radio access node 120 are separated between the CU(s) and DU(s) may vary depending on the chosen architecture.
[0109] Figure 6 illustrâtes an example of signaling in wireless network 100. As i 1 lustrated, the radio interface generally enables the UE 110 and the radio access node 120 to exchange signais and messages in both a downlink direction (from the radio access node 120 to the UE 110) and in an uplink direction (from the UE 110 to the radio access node 120).
[0110] The radio interface between the wireless device 110 and the radio access node 120 typically enables the UE 110 to access various applications or services provided by one or more servers 140 (also referred to as application server or host computer) located in an external network(s) ï 35. The connectîvity between the UE 110 and the server 140, enabled at least in part by the radio interface between the UE 110 and the radio access node 120, can be described as an “over-the-top” (OTT) or “application layer” connection. In such cases, the UE 110 and the server 140 are configured to exchange data and/or signaling via the OTT connection, using the radio access network 100, the core network 125, and possîbly one or more intermedîate networks (e.g. a transport network, not shown). The OTT connection may be transparent in the sense that the particîpating communication devices or nodes (e.g., the radio access node 120, one or more core network nodes 130, etc.) through which the OTT connection passes may be unaware of the actual OTT connection they enable and support. For example, the radio access node 120 may not or need not be informed about the previous handling (e.g., routing) of an incoming downlink communication with data originating from the server 140 to be forwarded or transmitted to the UE 110. Similarly, the radio access node 120 may not or need not be aware of the subséquent handling of an outgoîng uplink communication originating from the UE 110 towards the server 140.
10111] In conventional networks, such as NR Release 15, DCI formai 2_0 is used for indication of the transmission direction per symbol in time domain up to 256 slots period ically. As explained, the time domain slot format indication is carried in DCI format 2_0 by corresponding bit(s) for each serving cell. However, beside this indication, there is no other information being transmitted regarding structure/status of the transmission în the frequency domain.
[0112] In some cases, it may be bénéficiai to transmit some additional information regarding the state of the frequency domain to a group of one or more UEs. For example, it may be bénéficiai to indicate the avaîlability of a carrier and/or LBT bandwidth via DCI format 2_0 carried by GC-PDCCH explicitly.
[0113] Accordingly, some embodiments described herein inciude mechanisms for signaling an indication of avaîlability and/or unavaîlability of frequency resource (e.g. carriers and/or LBT bandwidth). The indication can be based on one or more of following: defining a marker signaled using SFI index in DCI format 2_0, reinterpreting or adding new slot format combination, and/or defining a new field în DCI format 2_0.
[0114] Some embodiments will be described based on the exîstîng GC-PDCCH signaling structure carrying DCI Format 2_0 and in some examples can make use of the reserved values in Table 11.1.1-1 în 3GPP TS 38.213 to provide additional information.
[0115] In one embodiment, a marker signaled using SFI index in DCI format 2_0 can indicate that the corresponding frequency resources are not available for any DL and/or UL operation in a spécifie cell or group of celIs.
[0116] The marker can be indicated usîng one of remaining reserved values [56 ... 254] in the SFI formats table 11.1.1-1. The marker is configured and assigned to one or some of the slots in a “slot Format Combination” and indicates that the corresponding slots are not available for transmission for corresponding serving cell.
[0117] An example of configuring a marker is ihustrated in Table 2, where the marker is indicated by “Reserved value R” and is assigned to one or more slots as a “Slot Format Combination” which is mapped to a “slot Formai Combination ID” labeled as “x” în the table. For example. in Table 2 “reserved value R” is assigned to slot-O, slot-1, and slot-2 which means that the frequency resources are not available for transmission corresponding serving cell for the period indicated by these 3 slots.
| Slot Format Combinations 1D | Slot-0 (Current Slot) | Slot-1 | Slot-2 | Slot-3 |
| 0 | SFIo,o | SFIq.i | ^FI0,3 | |
| 1 | $^ι,ι | ^^1,2 | ||
| î | ||||
| x | Reserved value R | Reserved value R | Reserved value R | |
| y | Reseved value R2 | |||
| î | ||||
| Table 2: Example marker for configuration of availability of carrier/LBT bandwic | th |
or BWP
[0118] In this embodiment, examples of “frequency resources” among others are carrier(s)/LBT bandwidth(s)/subband(s)/BWP(s). Furthermore, one or some of the frequency resources may be within a BWP and may be assocîated with one or more of: a bandwidth and carrier or relative frequency shîft with respect to a pre-defined reference such as a carrier or a B WP.
[0119] In this embodiment, example of the “ceII” or “group of cells”, are the cell(s) that transmit the correspond! ng DCI format 2_0 or another servi ng ce U for UE in carrier aggregated (CA) or dual connected (DC) modes other than the cell on which the indication is carried.
[0120] In a variation of thîs embodiment, a different reserved value can be used to indicate that frequency resources are unavailable for the duration in terms of number of slots equai to the maximum duration for which slot information is provided in the current GCPDCCH message for any of the frequency resources. As an example, in Table 2, Reserved value R2 can indicate that the frequency resources are not available for the maximum number of slots for which slot information is provided across ali the frequency resources.
[0121] In another embodiment, similar to as describe above, the different reserved values can indicate different numbers of slots for which the frequency resources are unavailable for DL or UL transmission. For example, in Table 3, reserved value RI indicates 1 slot, reserved value R2 indicates 2 slots, and reserved value R3 indicates 3 slots, and so on.
| Slot Format Combinations ID | Slot-0 (Current Slot) | Slot-l | Slot-2 | Slot-3 |
| 0 | SFI 0,0 | SFI 0J | SF1o,2 | SFL,3 |
| X | Reserved value R1 | |||
| x+1 | Reserved value R2 | |||
| x+2 | Reserved value R3 | |||
| : | ; |
Table 3: Example marker for configuration of availability of carrier/LBT bandwidth or BWP
[0122] In one variation, a set of SFI index bits in the DCI format 2_0 can be înterpreted as the indicator for LBT bandwidth(s)/LBT subband(s)/subband(s)/channel(s).
[0123] In another variation, a set of SFI-index bits in the DCI format 2_0 can correspond to a specified PRB range of a carrier. Using the same example from Figure 3, the DCI can indicate the last slotFormatCombination in the SloiFormatCombinations which is indicated by slotFormatCombinationID = 3, therefore the SFI index corresponds to bit values “11”. The DCI becomes xxxxxxxxl 1xx. In this example, the bits ‘11’ correspond to PRB range NI :N2 of the serving cell with ServingCelHD = 3. The PRB index NI is greater than or equal to 0 and the PRB index N2 is less than the number of PRBs of a BWP of the serving cell. Here the x’s correspond to other PRB ranges of the same or other serving cells. The PRB range N1 :N2 is indicated to the UE by radio resource control (RRC) signaling. In one non-limiting embodiment, the PRB range is indicated as a new field within the information element SlotFormatCombinationsPerCell.
[0124] In another variation, a set of SFI index bits in the DCI format 2_0 can be înterpreted as the indicator for a BWP.
[0125] In another embodiment. the indication of whether frequency resources are not available can be signaled using SFI-index în DCI format 2_0 for any DL and/or UL operation în a spécifie cell or group of cells by reinterpreting one or some values of “Slot Format Indicator” and/or, “slot Format Combination” and/or “Slot Format Combination ID”.
[0126] In this embodiment, example of “frequency resources” among others are carrier(s)/LBT bandwidth(s)/subband(s)/BWP(s). Furthermore, one or some of the frequency resources may be withîn a BWP and may be associated with one or more of: a bandwidth and carrier or relative frequency shîft with respect to a pre-defined reference such as a carrier or a BWP.
10127] In this embodiment, example of the “cell” or “group of cells”, are the cell(s) that transmit the corresponding DCI format 2_0 or another serving cell for UE in carrier aggregated (CA) or dual connected (DC) modes or than the cell on which the indication is carried.
[0128] In one example of this embodiment, setting ail the slots which are not available for spécifie duration in a “Slot Format Combination” to UL, would be an indication that the frequency resources are not available DL or UL transmission for this duration. This is shown in Table 4a where slot-O, slot-1 and siot-2 are not available for any DL or UL transmission. Note that value 2 is SFI for slot with ail UL symbols.
| Slot Format Combinations ID | Slot-0 (Current Slot) | Slot-1 | Slot-2 | Slot-3 |
| 0 | SFI - ri0.0 | SF1O1 | sfi02 | SFI0J |
| : | ||||
| x | 2 | 2 | 2 | |
| * | ||||
| Table 4a: Indication that frequency resources are unavailable if ail s | ot formats are |
set to uplink
[0129] In another example, one or more of the Slot Format Combinations IDs can be predefined to indicate that the frequency resources are not available for any transmission. In this example, there may be several options to indicate for how long perîod the frequency resources are not available, some options are listed in the following.
[0130] One option is that the different “Slot Format Combination ID”s indicate different number of slots for which the frequency resources are unavailable for DL or UL transmission. For example, in Table 4b, “Slot Format Combination ID” = “n” is predefined to indicate that the frequency resource are unavailable for slot 0, “Slot Format Combination
ID” = “n+1” is predefîned to indicate that the frequency resource are unavaîlable for slots 0, and 1, “Slot Format Combination ID” = “n+2” is predefîned to indicate that the frequency resource are unavaîlable for slots 0, 1 and 2, and so on. This can be considered different from the previously described embodiment where the reserved value in SF1 table is assigned to “Slot Format Combination ID” of choice.
[0131] In another option, an empty slot format combination can be configured to indicate that the UE is not expected to be scheduled on the corresponding frequency resources (e.g. carriers/BWP/subband/LBT bandwidth) for a duration équivalent to the longest indicated slot format combination ID for the other frequency resources (e.g. carriers/BWP/LBT bandwidth).
[0132| Example RR.C configuration:
Siotformatcombination(7) = {slotFormatCombinationlD = 7 slotformats = {}
[0133] In another option, the period during which the frequency resources are not avaîlable is equal to the number of slots that other “slot format combination” is applicable to (for example, assuming ail format combinations associated with a cell/carrîer/BWP/LBT subband/channel comprise the same number of slotFormats).
| Slot Format Combinations ID | Slot-0 (Current Slot) | SIot-1 | Slot-2 | SIot-3 |
| 1 | SFI10 | SFIU | SF1|3 | |
| * | ||||
| n | unavaîlable | |||
| n+1 | unavaîlable | unavaîlable | ||
| n+2 | unavaîlable | unavaîlable | unavaîlable | |
| : | : |
Table 4b: Indication that carrier is unavaîlable by predefinition of one or more of the slotFormatCombinatîonlDs
[0134] In one variation, a set of SFI index bits in the DCI format 2_0 can be interpreted as the indicator for LBT bandwidth(s) / LBT subband(s) ! subband(s) / channel(s).
[0135] In another variation, a set of SFI-index bits in the DCI format 2_0 can correspond to a specified PRB range of a carrier.
[0136] In another variation, the corresponding SFI index field in the DCI format 2_0 can be interpreted as the indicator for a BWP.
[0137] in some embodiments, as a signaling option, in the RRC 1E SlotFormatCombinationsPerCeil, the slot format combinations can be sorted following an increasing order of the LBT bandwidth /LBT subband/channel index. In an example, there are N slot format combinations in the set, and the cell/BWP is divided into M LBT bandwidths/LBT subbands/channels. In this case, each LBT bandwidth/LBT subband/channel would then include N/M slot format combination éléments. In this way, the gNB uses the slot format combination ID range to explicitly indicate LBT bandwidth/LBT subband/channel.
[0138] In other embodiments, a field in a DCI format 2_0 message can be defined or added to indicate whether frequency resources are availabie, or not availabie, for any DL and/or UL operation in a spécifie cell or group of cells.
[0139) In this embodiment, example of “frequency resources” among others are carrier(s)/LBT bandwidth(s)/subband(s)/BWP(s). Furthermore, one or some of the frequency resources may be within a BWP and may be associated with one or more of: a bandwidth and carrier or relative frequency shift with respect to a pre-defîned reference such as a carrier or a BWP.
[0140] In this embodiment, example of the “cell” or “group of cells”, are the cell(s) that transmit the corresponding DCI format 2_0 or another serving cell for UE in carrier aggregated (CA) or dual connected (DC) modes or than the cell on which the indication is carried.
[0141] In an example embodiment, a field “frequency resource indicator” of one or more extra bit(s) can be defined for each SFI-index to indicate whether the corresponding frequency resources are availabie or not. Example of a modified DCI format 2_0:
Slot format indicator 1 + frequency resource indicator 1, Slot format indicator 2 + frequency resource indicator 2, ..., Slot format indicator N + frequency resource indicator N
[0142| In the above example, if it is indicated that the frequency resources of corresponding cell are not available by the “frequency resource indicator” the duration for which the cell is not available can be indicated by the corresponding SFI.
[0143] In a variation of this example, an extra field can be defined and added to the DCI format 2_0 where each bit in the field indicates avaîlability of ali frequency resources. Example of a modified DCI format 2_0:
Frequency resource indicator, Slot format indicator 1, Slot format indicator 2, Slot format indicator N
[0144] In another example, a carrier can contain 2 LBT-bandwidths and 4 such carriers overall. In this case, for indication of availabîlity/unavailability of each LBT bandwidth of each carrier a field with length of 2 bits is defined for each carrier after the corresponding SFI field, for example in the followîng:
Slot format indicator 1 + PL Slot format indicator 2 + 01. Slot format indicator 3 + 10. Slot format indicator 4 + 11
[0145] For the first carrier and second carriers, the second LBT bandwidths (01) are available, for the third carrier the first LBT bandwidth (10) is available, and both LBT bandwidths (11) are available for fourth carrier.
[0146] The followîng example is for the case where each slot format indicator is used for an LBT bandwidth:
Slot format indicator 1 + Slot format indicator 2 + L Slot format indicator 3 -ΙΟ, Slot format indicator 4 + 0, Slot format indicator 5+0, Slot format indicator 6 + 1
[0147] In the above example the first, second and last (e.g. 6th) LBT bandwidths are available.
[0148] The followîng example is for the case where ail carriers are addressed using one field in DCI and indicate the same pattern as the previous example, i.e. the first, second and last (6th) LBT bandwidths are available:
110001 + Slot format indicator 1, Slot format indicator 2, Slot format indicator 3, Slot format indicator 4, Slot format indicator 5, Slot format indicator 6
[0149] In one variation, ail frequency resources (e.g. ail carriers/BWPs/LBT BWPs) can hâve the same COT structure. Then the gNB can signal to the UE the same SFI indicator for ail carriers/BWPs/LBT BWPs that are available at the time. The requîred modifications would include: i) the servingcelllD in RRC will include the list of ail candidate cells, ii) DCI carries available carriers/BWPs/LBT BWPs indicators.
[0150] In an exemplary embodiment, the gNB can skip the SF1 bits in DCI format 2_0 for the carrîer/LBT bandwidth/subband/group of PRBs on which the DCI is transmitted, since that carrier/LBT bandwidth/subband/group of PRBs must be available for the duration indicated by the SFI.
[0151] In some embodiments, the gNB and UE(s) behavîors can be configured accordingly.
[0152] !n some embodiments, in the first slot(s) of the COT, when the gNB does not hâve enough time to préparé the COT structure indicators after LBT, UEs can monîtor the DL burst by monitoring (GC-)PDCCH over all carriers/BWPs/LBT BWPs as in NR Rel15.
[0153] Some embodiments include self-contained carrier indicators. The gNB can préparé and send COT structure indicators per carrier/BWP/LBT B WP (send COT structure indicators using different DCIs over different carriers). The UE(s) can monîtor ail carriers/BWP/LBT BWP at least until receiving correctly the COT structure indicators from gNB. Optionally, a UE can stop monitoring on unavaîlable carriers for power saving if ît is configured as such.
[0154] Some embodiments include cross-carrier indicators over single carrier. The gNB can préparé and send a single/joint COT structure îndicator for all carriers/BWPs/LBT BWPs in a single DCI over a single carrier, e.g., DL carrier with smallest index. The UE(s) can monîtor all carriers/BWP/LBT BWP at least untîl receiving correctly the COT structure indicators from gNB.
[0155] Some embodiments include cross-carrier indicators, répétition over all available carriers. The gNB can préparé a single/joint COT structure îndicator for all carrier/BWP/LBT BWP and send the same copy of the COT structure indicators over all available (or a subset of) DL carriers. The UE(s) can monîtor all carriers/BWP/LBT BWP at least until receiving correctly at least one COT structure indicators from gNB.
[0156] Some embodiments include cross-carrier indicators, over primary carrier. The gNB can préparé a single/joint COT structure îndicator for all carriers/BWPs/LBT BWPs and send the joint COT structure îndicator over primary DL carrier. The UE(s) can monîtor only the primary DL carrier at least until receiving correctly COT structure îndicator from a gNB. Then, the UE can monîtor all available carriers based on COT structure îndicator.
[0157] Some embodiments include retrying LBT (on not free carriers) in middle of the COT. in this embodiment, the gNB can overwrite the COT structure of an ongoing COT if gNB re-tries LBT on unav ai labié carrier(s) and determîne if it ts available. Then, a gNB may schedule UEs (that are active or not sleeping) on those carrier(s) in the remaining of the COT.
[0158| Some embodiments described herein include configuration of frequency resources.
[0159| Some embodiments described herein hâve suggested a variety of methods for indicating avaîlability/unavailability of frequency resources (cell, carrier, LBT bandwidth/subband, BWP, etc.) în DCI Format 2_0. A frequency resource can be a cell, carrier, LBT bandwidth/subband or BWP. The configuration of the frequency resources, such as PRB range and any other information, can be specified in the spécification, or communicated to UEs by System broadçasting, or by dedicated RRC signaling.
[0160] In an exemplary implémentation, a UE can be configured with multiple serving cells/carrîers. For each configured serving cell, the UE is provided with the number of LBT bandwidth/subband and the corresponding PRB allocation. A bit in frequency resource indication in DCI Format 2_0 can indicate whether the associated PRBs for the corresponding LBT bandwidth/subband are available for transmission and réception during the duration indicated by the SFI.
[0161] In another exemplary implémentation, the LBT bandwidth/subband to PRB mapping can be predefined in the spécification. A bit in the frequency resource indication in DCI Format 2_0 can indicate whether the corresponding LBT, LBT bandwidth/subband is available for transmission and réception during the duration indicated by the SFI, while the exact PRBs în question can be derived from the spécification.
[0162] Some embodiments include a slot format combination table that incorporâtes inputs from multiple tables in each entry of each row.
[0163] In this embodiment, a set of properties, or values or parameters that are defined separate from the slot format table (e.g. Table 11.1.1-1 in TS 38.213) can be encoded together with the SFI information from Table 11.1.1-1 în the slot format combination table. In a first table, a set of properties, values or parameters are indexed. The slot format combination table is then modified so that each entry of the table can indicate an SFI value and an index from the first table in which properties, values or parameters are indexed. This index can then indicate information in addition to the SFI information in Table 11.1.1-1 in
TS 38.213. This structure provides a very general Framework by which the DCI signaling currently defined for DCI format 2_0 can be used unchanged to communicate information în addition to the SFI information defined in Rel-15 NR. An example of this embodiment is shown în Tables 5 and 6 below.
| Index | Property |
| 0 | Frequency resources corresponding to this slot format combination table are unavailable in this slot |
| 1 | Frequency resources corresponding to this slot format combination table are unavailable for the maximum number of slots for which SFI information has been provided on any frequency resources in this DCI message |
| 2 | Ail DL to UL swîtches în this slot requires no LBT for the UL transmission |
| 3 | Ail DL to UL switch occurs în this slot require a 25 microsecond LBT for the UL transmission |
| 4 | The channel occupancy initiated by the gNB ends at the end of this slot |
Table 5: General properties, values of parameters of various types that are assigned an index
| Slot Format Combination | Slot-0 | Slot-1 | Slot-2 | Slot-3 |
| 0 | SFlo,o+ 1 | SFIo.i | SFIo,2 | SFIo,3 |
| 1 | SFh.o + 2 | SFIi.i + 3 | SFIi(2 + 4 | SF1i,3 |
| 2 | SFI2.0 | SFbj | SFÏ2.2 + 0 | SFI2,3 + 4 |
| ** |
Table 6: Slot format combination table that includes SFI information with an index from the table above to in d ica te a property, value or parameter associated with the slot.
[0164] According to sonie of the embodiments described herein, it is possible to inform a device about the availability of part of a frequency domain resource (e.g. other carriers or LBT bandwidths or a PRB range) by detecting the control information on other parts of frequency resources (e.g. one of the carriers or LBT bandwidths or a PRB range). This can be bénéficiai for a UE to defer PDCCH monitoring and/or defer sensing of the medium on other carriers or LBT bandwidth which can resuit în power savîng. Some of these embodiments can provide a low-overhead approach to signaling availability of carrier and or LBT bandwidth by using the existing fields in DCI format 2_0 carried by GC-PDCCH, thus causing minimal impact on the specification(s).
[0165] Figure 7 is an example signaling diagram. Wireless device 110 is configured with a plurality of frequency resources (step 200). In some embodiments, the frequency resource configuration can be obtained from an access node, such as gNB 120. In some embodiments, wireless device 110 can be pre-configured with the frequency resource configuration information.
[0166] Access node 120 can generate parameters for a control message, such as a DCI message (step 201). In some embodiments, the control message can be a DCI format 2_0 message as described herein. The control message can include slot format information and/or frequency domain information, such as an indication of availability of frequency resource(s). The message can îndicate if one or more frequency resources are avaîlable/unavailable for DL or UL transmission. For example, the control message can îndicate a number of slots and/or duration for which resources are not available. The resources can correspond to resources blocks (e.g. PRBs) and/or a resource block range.
[0167] Access node 120 transmits the configured control message to the wireless device 110 (step 202). Wireless device 110 can détermine available resources in accordance with the received control message (step 203). In some embodiments, this can include determining frequency resources that are avaîlable/unavailable for DL or UL transmission. Wireless device 110 can then optionally transmit data to (step 204) and/or receive data from (step 205) access node 120, in accordance with the determined resource(s).
[0168] Figure 8 is a flow chart illustrating a method which can be performed in a wireless device, such as UE 110 as described herein. The method can include:
[0169] Step 300: Configurîng the wireless device with a plurality of frequency resources. In some embodiments, frequency resource configuration can be obtained from a network node, such as gNB 120. This can include receivîng configuration information vîa System broadcast, via RRC signaling, etc. In some embodiments, the wireless device can be preconfigured w'ith the frequency resource configuration information. The frequency resources can include one or more of: a carrier, a sub-band of a carrier, a set of resource blocks (RBs) on a carrier, a listen before talk (LBT) bandwidth, and a bandwidth part (BWP).
(0170] Step 310: Receivîng a control message. The control message can be receîved from a network node, such as gNB 120. The control message can include an indication of availability and/or unavailable frequency resource(s) for UL and/or DL transmission. In some embodiments, the control message can be a DCI message, such as a DCI format 2_0. [0171] The control message can include at least one slot format indicator (SFI) field indicating a slot format for a corresponding frequency resource. The control message can include at least one frequency resource indicator indicating whether a corresponding frequency resource is available for operation (e.g. transmission/reception). In some embodiments, a frequency resource indicator can be associated with one or more SFIs. In some embodiments, the control message can further include at least one associated channel occupancy time (COT) duration field.
[0172] Step 320: Determining available/unavailable frequency resource(s) in accordance with the receîved control message. In some embodiments, the availability of operation of a frequency resource can be detennîned in accordance with the frequency resource indicator. [0173] In some embodiments, the wireless device identifies the corresponding frequency resource (e.g. from the plurality of configured frequency resources) based at least in part on a bit position of the frequency resource indicator field in the receîved DCI message. Similarly. in some embodiments, the wireless device can identify the corresponding frequency resource based at least in part on a bit position of the SFI field in the receîved DCI message.
[0174] In some embodiments, the frequency resource indicator can comprise a plurality of bits (e.g. bit field or bit map) wherein each bit (or set of bits) corresponds to one of the plurality of configured frequency resources. In some embodiments, each SFI field in the DCI can hâve an associated frequency resource indicator field. In other embodiments, the DCI can include a single frequency resource indicator field that is associated with a plurality ofSFlfields.
[0175] In some embodiments, a spécifie value carried in a frequency resource indicator field in the control message can indicate an available bandwidth (e.g. a spécifie LBT bandwidth or BWP, etc.) for the correspond!ng frequency resource.
[0176] In some embodiments, a spécifie value (e.g. a reserved value) carried in an SFI field in the control message can indicate a number of slots for which a frequency resource is unavailable.
[0177] In alternative embodiments, the wireless device can receive a control message (e.g. DCI) that includes at least one of an SFI field and/or an available resource indicator field. The wireless device can détermine available/unavailable frequency resource(s) in accordance with the received control message, based on the SFI and/or the available resource indicator and/or a combination of both fields and/or other parameters as hâve been described in the various embodiments herein.
[0178] Step 330: The wireless device can optionally transmit and/or receive data in accordance with the determined available frequency resource(s). For example, responsîve to determining that a frequency resource is available for operation, the wireless device monitors the available frequency resource. The wireless device can monitor the frequency resource for a PDCCH. The wireless device can receive a transmission such as a CSI-RS on the frequency resource.
[0179] Responsîve to determining that a frequency resource is unavailable for operation, the wireless device does not monitor the frequency resource. Accordingly, the wireless device would not transmit or receive on the unavailable frequency resource. For example, the wireless device does not receive a CSI-RS on the unavailable frequency resource.
[0180] It will be appreciated that one or more of the above steps can be performed simultaneously and/or in a different order. Also, steps iIkistrated in dashed Unes are optional and can be omitted in some embodiments.
[0181] Figure 9 îs a flow chart îllustrating a method which can be performed in a network node, such as access node/gNB 120 as described herein. The method can include:
[0182] Step 400: Optionally, the network node can configure a wireless device with a plurality of frequency resources. This can include transmitting configuration information via System broadeast, via RRC signaling, etc. The frequency resources can include one or more of: a carrier, a sub-band of a carrier, a set of resource blocks (RBs) on a carrier, a listen before talk (LBT) bandwidth, and a bandwîdth part (BWP).
[0183] Step 410: Generating a control message. This can include one or more of generating/configuring/modifying/adding parameters or other information in a control message. The control message can include an indication of availability and/or unavailable frequency resource(s) for UL and/or DL transmission. In some embodiments, the control message can be a DCI message, such as a DCI format 2_0.
[0184] The control message can include at least one SFI field indicatîng a slot format for a corresponding frequency resource. The control message can include at least one frequency resource indicator indicating whether a corresponding frequency resource îs available for operation (e.g. transmiss ion/réception). In some embodiments, a frequency resource indicator can be associated with one or more SFIs.
[0185] Step 420: Transmitting the generated control message. The control message can be transmitted to one or more wireless devices, such as UE 110.
[0186] Step 430: The network node optionally transmits and/or reçoives data in accordance with the available frequency resource(s). This can include, for example, transmitting a CSI-RS on an available frequency resource to one or more wireless device(s). [0187] It will be appreciated that one or more of the above steps can be performed simultaneously and/or in a different order. Also, steps illustrated in dashed Unes are optional and can be omitted in some embodiments.
|0188] Figure 10 is a block diagram of an example wireless device, UE 110, in accordance with certain embodiments. UE 110 includes a transceiver 510, processor 520, and memory 530. In some embodiments, the transceiver 510 facilitâtes transmitting wireless signais to and receiving wireless signais from radio access node 120 (e.g., via transmitter(s) (Tx), receiver(s) (Rx) and antenna(s)). The processor 520 executes instructions to provide some or ah of the functionalities described above as being provided by UE, and the memory 530 stores the instructions executed by the processor 520. In some embodiments, the processor 520 and the memory 530 fonn processing circuitry.
[0189] The processor 520 can include any suitable combination of hardware to execute instructions and manipulate data to perform some or ail of the described functions of a wireless device, such as the functions of UE 110 described above. In some embodiments, the processor 520 may include, for example, one or more computers, one or more central processing un ifs (CPUs), one or more microprocessors, one or more application spécifie integrated circuits (ASICs), one or more field programmable gâte arrays (FPGAs) and/or other logic.
[0190| The memory 530 is generally opérable to store instructions, such as a computer program, software, an application includîng one or more of logic, rules, algorîthms, code, tables, etc. and/or other instructions capable of being executed by a processor 520. Examples of memory 530 include computer memory (for example, Random Access Memory (RAM) 5 or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readable and/or computerexecutable memory devices that store information, data, and/or instructions that may be used by the processor 520 of UE 110.
[0191] Other embodiments of UE 110 may include additional components beyond those shown in Figure 5 that may be responsible for providing certain aspects of the wireless device’s functionalities, includîng any of the functionalities described above and/or any additional functionalities (includîng any functionality necessary to support the solution described above). As just one example, UE 110 may include input devices and circuits, 15 output devices, and one or more synchronîzation units or circuits, which may be part of the processor 520. Input devices include mechanisms for entry of data into UE 110. For example, input devices may include input mechanisms, such as a microphone, input éléments, a display, etc. Output devices may include mechanisms for outputting data in audio, video and/or hard copy format. For example, output devices may include a speaker, 20 a display, etc.
[0192] In some embodiments, the wireless device UE 110 may comprise a sériés of modules configured to implement the functionalities ofthe wireless device described above. Referring to Figure 11, in some embodiments, the wireless device 110 may comprise a control module 550 for receiving and interpreting control information and a transceiver 25 module 560 for transmîtting/receiving data transmissions in accordance with the control information.
[0193] It will be appreciated that the varions modules may be implemented as combination of hardware and software, for instance, the processor, memory and transceiver(s) of UE 110 shown in Figure 10. Some embodiments may also include 30 additional modules to support additional and/or optîonal functionalities.
[0194] Figure 12 is a block diagram of an exemplary network node, such as radio access node 120, in accordance with certain embodiments. Network node 120 may include one or more of a transceiver 610, processor 620, memory 630, and network interface 640. In some embodiments. the transceiver 610 facilitâtes transmitting wireless signais to and receiving wireless signais from wireless devices, such as UE 110 (e.g., via transmitter(s) (Tx), receiver(s) (Rx), and antenna(s)). The processor 620 executes instructions to provide some or ail of the functionalîties described above as being provided by a radio access node 120, the memory 630 stores the instructions executed by the processor 620. In some embodiments, the processor 620 and the memory 630 form processing circuitry. The network interface 640 can communicate signais to backend network components, such as a gateway, switch, router, Internet, Public Switched Téléphoné Network (PSTN), core network nodes or radio network controllers, etc.
[0195] The processor 620 can include any suitable combination of hardware to execute instructions and manipulate data to perform some or ail of the described functions of radio access node 120, such as those described above. In some embodiments, the processor 620 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application spécifie integrated circuits (ASICs), one or more field programmable gâte arrays (FPGAs) and/or other logic.
[0196] The memory 630 is generally opérable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithme, code, tables, etc. and/or other instructions capable of being executed by a processor 620. Examples of memory 630 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readabie and/or computerexecutable memory devices that store information.
[0197] In some embodiments, the network interface 640 is communicatively coupled to the processor 620 and may refer to any suitable device opérable to receive input for node 120, send output from node 120, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding. The network interface 640 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilîties, to communicate through a network.
[0198] Other embodiments of network node 120 can include additional components beyond those shown in Figure 12 that may be responsîble for providing certain aspects of the node’s functionalîties, including any of the functionalîties described above and/or any additional functionalities (including any functionality necessary to support the solutions described above). The varions different types of network nodes may include components having the same physical hardware but configured (e.g., via programming) to support different radio access technologies, or may represent partly or entirely different physical 5 components.
[0199] Processors, interfaces, and memory similar to those described with respect to Figure 12 may be included in other network nodes (such as UE 110, core network node 130, etc.). Other network nodes may optionally include or not include a wireless interface (such as the transceiver described in Figure 12).
[0200] In some embodiments, the network node 120, may comprise a sériés of modules configured to implement the functionalities of the network node described above. Referring to Figure 13, in some embodiments, the network node 120 can comprise a control module 650 for generatîng and iransmîttîng control information and a transceiver module 660 for transmitting/receivîng data transmissions in accordance with the control information.
[0201] It will be appreciated that the varions modules may be implemented as combination of hardware and software, for instance, the processor, memory and transceiver(s) of network node 120 shown in Figure 12. Some embodiments may also include additional modules to support additional and/or optional functionalities.
[0202] Turning now to Figure 14, some network nodes (e.g. UEs 110, radio access nodes 20 120, core network nodes 130, etc.) in the wireless communication network 100 may be partially or even entirely virtualized. As a virtualized entity, some or all the fonctions of a given network node are implemented as one or more virtual network fonctions (VNFs) running in virtual machines (VMs) hosted on a typically generic processing node 700 (or server).
[0203] Processing node 700 generaliy comprises a hardware infrastructure 702 supporting a virtualization environment 704.
[0204] The hardware infrastructure 702 generaliy comprises processing circuitry 706, a memory 708, and communication interface(s) 710.
[0205] Processing circuitry 706 typically provides overall control of the hardware 30 infrastructure 702 of the virtualized processing node 700. Hence, processing circuitry 706 is generaliy responsible for the various functions of the hardware infrastructure 702 either directly or indirectly via one or more other components of the processing node 700 (e.g. sending or receiving messages via the communication interface 710). The processing circuitry 706 is also responsible for enabling, supporting and managing the Virtual ization environment 704 in which the various VNFs are run. The processing circuitry 706 may include any suitable combination of hardware to enable the hardware infrastructure 702 of the virtualized processing node 700 to perform its functions.
[0206] In some embodiments. the processing circuitry 706 may comprise at least one processor 712 and at least one memory 714. Examples of processor 712 include, but are not limited to, a central processing unit (CPU), a graphical processing unit (GPU), and other forms of processing unît. Examples of memory 714 include, but are not limited to, Random Access Memory (RAM) and Read Only Memory (ROM). When processing circuitry 706 comprises memory 714, memory 714 is generally configured to store instructions or codes exécutable by processor 712, and possibly operational data. Processor 712 is then configured to execute the stored instructions and possibly create, transform, or otherwise manipulate data to enable the hardware infrastructure 702 of the virtualized processing node 700 to perform its functîons.
[0207] Additionally, or alternatively, in some embodiments, the processing circuity 706 may comprise, or further comprise, one or more application-specifîc integrated circuits (ASICs), one or more complex programmable logic device (CPLDs), one or more fieldprogrammable gâte arrays (FPGAs), or other forms of application-specifîc and/or programmable circuitry. When the processing circuitry 706 comprises application-specifîc and/or programmable circuitry (e.g., ASICs, FPGAs), the hardware infrastructure 702 ofthe virtualized processing node 700 may perform its functions without the need for instructions or codes as the necessary instructions may already be hardwired or preprogrammed into processing circuitry 706. Understandably, processing circuitry 706 may comprise a combination of processor(s) 712, memory(ies) 714, and other application-specifîc and/or programmable circuitry.
[0208] The communication interface(s) 710 enable the virtualized processing node 700 to send messages to and receive messages from other network nodes (e.g., radio network nodes, other core network nodes, servers, etc.). In that sense, the communication interface 710 generally comprises the necessary hardware and software to process messages receîved from the processing circuitry 706 to be sent by the virtualized processing node 700 into a format appropriate for the underlying transport network and, conversely, to process messages receîved from other network nodes over the underlying transport network into a format appropriate for the processing circuitry 706. Hence, communication interface 710 may comprise appropriais hardware, such as transport network interface(s) 716 (e.g., port, modem, network interface card, etc.), and software, including protocol conversion and data processing capabilities, to communîcate with other network nodes.
[0209] The virtualization environment 704 is enabled by instructions or codes stored on memory 708 and/or memory 714. The virtualization environment 704 generally comprises a virtualization layer 718 (also referred to as a hypervîsor), at least one Virtual machine 720, and at least one VNF 722. The functions of the processing node 700 may be implemented by one or more VNFs 722.
[0210] Some embodiments may be represented as a software product stored in a machine-readable medium (also referred to as a computer-readable medium, a processorreadable medium, or a computer usable medium having a computer readable program code embodied therein). The machine-readable medium may be any suitable tangible medium including a magnetic, optical, or electrica! storage medium including a diskette, compact disk read only memory (CD-ROM), digital versatile dise read only memory (DVD-ROM) memory device (volatile or non-volatile), or similar storage mechanism. The machinereadable medium may contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause processing circuitry (e.g. a processor) to perform steps in a method according to one or more embodiments. Those of ordinary ski 11 in the art will appreciate that other instructions and operations necessary to implement the described embodiments may also be stored on the machine-readable medium. Software running from the machine-readable medium may interface with circuitry to perform the described tasks.
[0211] The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skîll in the art without départing from the scope of the description.
GLOSSARY
The présent description may comprise one or more of the following abbreviation:
| 3GPP | Third Génération Partnership Project |
| ACK | Acknowledgement |
| AP | Access point |
| ARQ | Automatic Repeat Request |
| BS | Base Station |
| BSC | Base station controller |
| BSR | Buffer Status Report |
| BTS | Base transceiver station |
| CA | Carrier Aggregatîon |
| CC | Component carrier |
| CCCH SDU | Common Control Channel SDU |
| CG | Cell group |
| CGI | Cell Global Identifier |
| CM | Core network |
| CQI | Channel Quality information |
| CSI | Channel State Information |
| eu | Central Unit |
| DA S | Distrîbuted antenna System |
| DC | Dual connectivity |
| DCCH | Dedicated Control Channel |
| DCI | Downlink Control Information |
| DL | Downlink |
| DM RS | Démodulation Reference Signal |
| DU | Distrîbuted Unit |
| eMBB | Enhanced Mobile Broadband |
| eNB | E-UTRAN NodeB or evolved NodeB |
| ePDCCH | enhanced Physical Downlink Control Channel |
| E-SMLC | evolved Serving Mobile Location Center |
| E-UTRA | Evolved UTRA |
| E-UTRAN | Evolved UTRAN |
| FDM | Frequency Division Multiplexing |
| HARQ | Hybrîd Automatic Repeat Request |
| HO | Handover |
| IAB | Integrated Access Backhaul |
| loT | Internet of Thîngs |
| 5 LTE | Long-Term Evolution |
| M2M | Machine to Machine |
| MAC | Medium Access Control |
| MBMS | Multimedia Broadcast Multicast Services |
| MCG | Master cell group |
| 10 MDT | Minimization of Drive Tests |
| MeNB | Master eNode B |
| MME | Mobility Management Entity |
| MSC | Mobile Swîtchîng Center |
| MSR | Multi-standard Radio |
| 15 MTC | Machine Type Communication |
| NACK | Négative acknowledgement |
| NDI | Next Data Indicator |
| NR | New Radio |
| O&M | Operation and Maintenance |
| 20 OFDM | Orthogonal Frequency Division Multiplexing |
| OFDMA | Orthogonal Frequency Division Multiple Access |
| oss | Operations Support System |
| PCC | Primary Component Carrier |
| P-CCPCH | Primary Common Control Physical Channel |
| 25 PCell | Primary Cell |
| PCG | Primary Cell Group |
| PCH | Pagîng Channel |
| PCI | Physical Cell Identîty |
| PDCCH | Physical Downlink Control Channel |
| 30 PDCP | Packet Data Convergence Protocol |
| PDSCH | Physical Downlink Shared Channel |
| PDU | Protocol Data Unit |
| PGW | Packet Gateway |
| PH1CH | Physical FIARQ indication channei |
| PMI | Precoder Matrix Indicator |
| ProSe | Proximity Service |
| PSC | Primary serving cell |
| 5 PSCell | Primary SCell |
| PUCCH | Physical Uplink Control Channei |
| PUSCH | Physical Uplink Shared Channei |
| RAT | Radio Access Technology |
| RB | Resource Block |
| 10 RF | Radio Frequency |
| RLC | Radio Uînk Control |
| RLM | Radio Uink Management |
| RNC | Radio Network Controller |
| RRC | Radio Resource Control |
| 15 RRH | Remote Radio Head |
| RRM | Radio Resource Management |
| RRU | Remote Radio Unît |
| RS RP | Reference Signal Received Power |
| RSRQ | Référence Signal Received Qualîty |
| 20 RSS1 | Received Signal Strength Indicator |
| RSTD | Reference Signal Time Différence |
| RTT | Round Trip Time |
| SCC | Secondary Component Carrier |
| SCell | Secondary Cell |
| 25 SCG | Secondary Cell Group |
| SCH | Synchronization Channei |
| SDU | Service Data Unît |
| SeNB | Secondary eNodeB |
| SGW | Serving Gateway |
| 30 SI | System Information |
| S1B | System Information Block |
| SINR | Signal to Interférence and Noise Ratio |
| SNR | Signal Noise Ratio |
| SPS | Semi-persistent Schedulîng |
| SON | Self-organîzing Network |
| SR | Scheduling Request |
| SRS | Sounding Référencé Signal |
| 5 SSC | Secondary Serving Cell |
| TTI | Transmission Time Interval |
| Tx | Transmitter |
| UE | User Equipment |
| UL | Uplink |
| 10 URLLC | Ultra-Reiiable Low Latency Communication |
| UTRA | Universal Terrestrial Radio Access |
| UTRAN | Universal Terrestrial Radio Access Network |
| V2V | Vehicle-to-vehicle |
| V2X | Vehicle-to-everything |
| 15 WLAN | Wireless Local Area Network |
Claims (18)
1. A method performed by a wireless device ( 11 OA, 11OB), comprising:
configuring the wireless device (110A, 110B) with a plurality of frequency resources;
receiving a downlink control information, DCI, message including at least one slot format indicator, SFI, field and a frequency resource indicator field, wherein the SFI indicates a slot format for a corresponding frequency resource, and the frequency resource indicator indicates whether the corresponding frequency resource is available for operation; and determining whether the corresponding frequency resource is available for operation in accordance with the frequency resource indicator;
wherein the frequency resource indicator comprises a plurality of bits wherein each bit corresponds to one of the plurality of frequency resources.
2. A method performed by a network node (120A, 120B), comprising:
configuring one or more wireless devices(11 OA, 110B) with a plurality of frequency resources, generating a downlink control information, DCI, message including at least one slot format indicator, SFI, field and a frequency resource indicator field, wherein the SFI indicates a slot format for a corresponding frequency resource, and the frequency resource indicator indicates whether the corresponding frequency resource is available for operation; and transmitting the generated DCI message to one or more wireless devices (110A, 110B);
wherein the frequency resource indicator comprises a plurality of bits wherein each bit corresponds to one of the plurality of frequency resources.
3. A wireless device (110A, 110B) comprising a radio interface and processing circuitry configured to:
configure the wireless device (110A, 1 10B) with a plurality of frequency resources;
receive a downlink control information, DCI, message including at least one slot format indicator, SFI, field and a frequency resource indicator field, wherein the SFI indicates a slot format for a corresponding frequency resource, and the frequency resource indicator indicates whether the corresponding frequency resource is available for operation; and déterminé whether the corresponding frequency resource is availabie for operation in accordance with the frequency resource indicator;
wherein the frequency resource indicator comprises a plurality of bits wherein each bit corresponds to one of the plurality of frequency resources.
4. The wireless device (11 OA, 11OB) of claim 3, wherein configuring the wireless device includes receiving configuration information from a network node.
5. The wireless device (110A, 110B) of any one of daims 3 to 4, wherein the plurality of frequency resources include one or more of: a carrier, a sub-band of a carrier, a set of resource blocks , RBs, on a carrier, a listen before talk, LBT, bandwidth, and a bandwidth part, BWP,.
6. The wireless device (110A, 110B) of any one of daims 3 to 5, wherein the DCI message is a DCI format 2_0.
7. The wireless device ( 11 OA, 11 OB) of any one of daims 3 to 6, further configured to détermine whether the corresponding frequency resource is availabie for operation during a duration of the SFI in accordance with the frequency resource indicator.
8. The wireless device (110A, 110B) of any one of daims 3 to 7, wherein the DCI message further includes an associated channel occupancy time, COT, duration field; and optionally, further configured to détermine whether the corresponding frequency resource is availabie for operation during the COT duration in accordance with the frequency resource indicator.
9. The wireless device (110A, 110B) of any one of claîms 3 to 8, wherein the wireless device (11 OA, 1ÏOB) identifies the corresponding frequency resource based at least in part on a bit position of the frequency resource indicator field in the received DCI message.
10. The wireless device (11 OA, 110Β) of any one of daims 3 to 9, wherein, responsive to determining that the corresponding frequency resource is availabie for operation, the wireless device (110A, 110Β) monitors the frequency resource;
and optionally, wherein the wireless device (110A, 110B) monitors the frequency resource for a physical downlink control channel, PDCCH.
11. The wireless device (110A, 110B) of any one of claîms 3 to 10 wherein, responsive to determining that the corresponding frequency resource is availabie for operation, the wireless device (110Α, 11OB) receives a channel-state information reference signal, CSI-RS, on the frequency resource.
12. The wireless device (110A, 110B) of any one of daims 3 to 11, wherein, responsive to determining that the corresponding frequency resource is not available for transmission/reception, the wireless device does not monîtor the frequency resource.
13. The wireless device ( 11 OA, 11 OB) of any one of daims 3 to 12, further configured to:
détermine that the SFI field corresponds to a reserved value in a frequency resource configuration; and détermine a number of slots for which the frequency resource is unavailable in accordance with the reserved value.
14. A network node (120A, 120B) comprising a radio interface and processing circuitry configured to:
generate a downlink control information , DCI, message including at least one slot format îndicator, SFI, field and a frequency resource îndicator field, wherein the SFI indicates a slot format for a corresponding frequency resource, and the frequency resource îndicator indicates whether the corresponding frequency resource is available for operation; and transmit the generated DCI message to the one or more wireless devices:
the network node being further configured to configure one or more wireless devices with a pluralîty of frequency resources;
wherein a bit position of the frequency resource îndicator field in the received DCI message identifies a corresponding frequency resource.
15. The network node (120A, 120B) of claim 14, wherein confîguring the one or more wireless devices includes transmitting configuration information.
16. The network node ( 120A, 120B) of any one of daims 14 to 15, wherein the pluralîty of frequency resources include one or more of: a carrier, a sub-band of a carrier, a set of resource blocks , RBs, on a carrier, a listen before talk, LBT, bandwidth, and a bandwidth part, BWP.
17. The network node (120A, 120B) of any one of daims 14 to 16, wherein the DCI message is a DCI format 2_0.
18. The network node (120A, 120B) ofany one of claims 14 to 17, further comprising, transmitting a channel-state information reference signal, CS1-RS, on an available frequency resource.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US62/888,215 | 2019-08-16 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| OA20678A true OA20678A (en) | 2022-12-30 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7084988B2 (en) | PUCCH resource instructions for CSI and HARQ feedback | |
| EP4084381B1 (en) | Prioritization of scheduling request and ack/nack | |
| US20240080701A1 (en) | Methods and procedures for channel measurements and reporting mechanisms | |
| US20220295560A1 (en) | Dci signalling including at least one slot format indicator, sfi, field, and a frequency resource indicator field | |
| US9674727B2 (en) | Indication of cell mode and CSI feedback rules for cell on-off procedure | |
| JP2022078322A (en) | Terminal, base station, communication method and system | |
| EP3639591B1 (en) | System and methods for configuring user equipments with overlapping pucch resources for transmitting scheduling requests | |
| WO2012111625A1 (en) | Aperiodic channel state information reporting method, wireless base station device, and user terminal | |
| WO2015174328A1 (en) | Radio base station, user equipment, and radio communication method | |
| AU2017245037A1 (en) | User terminal, radio base station and radio communication method | |
| US11950185B2 (en) | Wake-up signal configuration | |
| CN114651406B (en) | Timer handling in multiple active authorization configurations | |
| US20230179385A1 (en) | Enhanced scheduling for beam based transmission | |
| JPWO2017033840A1 (en) | User terminal, radio base station, and radio communication method | |
| JP2017520137A (en) | Activation command for fast cell on / off function | |
| OA20678A (en) | DCI signalling including at least one slot format indicator, SFI, field, and a frequency resource indicator field. |