OPERA TION OF WIRELESS DEVICE AND NETWORK NODE IN UNLICENSED

SPECTRUM

Related Applications

[0001] This application claims the benefit of provisional patent application serial number 62/755,156, filed November 2, 2018, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure relates to the operation of a wireless device and a network node in unlicensed spectrum.

Background

[0003] The next generation mobile wireless communication system, which is referred to as Fifth Generation (5G) or New Radio (NR), supports a diverse set of use cases and a diverse set of deployment scenarios. The latter includes deployment at both low frequencies, i.e., 100s of Megahertz (MHz) similar to Long Term Evolution (LTE) today, and very high frequencies, i.e., millimeter (mm) waves in the tens of Gigahertz (GHz).

[0004] Similar to LTE, NR uses Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) from a network node (i.e., NR Node B (gNB), enhanced or evolved Node B (eNB), or base station) to a User Equipment (UE). The basic NR physical resource over an antenna port can thus be seen as a time-frequency grid as illustrated in Figure 1, where a Resource Block (RB) in a 14-symbol slot is shown. A RB corresponds to twelve contiguous subcarriers in the frequency domain. RBs are numbered in the frequency domain, starting with zero from one end of the system bandwidth. Each Resource Element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval.

[0005] Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values, which are also referred to as different numerologies, are given by Af = (15 x 2“) kilohertz (kHz) where a e (0,1, 2, 3, 4). Af = 15 kHz is the basic, or reference, subcarrier spacing that is also used in LTE.

[0006] In the time domain, DL and uplink (UL) transmissions in NR will be organized into equally-sized subframes of 1 millisecond (ms) each, similar to LTE. A subframe is further divided into multiple slots of equal duration. The slot length for subcarrier spacing Af = (15 x 2“) kHz is l/2“ ms. There is only one slot per subframe at Af =

15 kHz, and a slot consists of fourteen (14) OFDM symbols.

[0007] DL transmissions are dynamically scheduled, i.e., in each slot the gNB transmits Downlink Control Information (DCI) that indicates the UE to which data is transmitted and the RBs in the current DL slot on which the data is transmitted. In NR, this DCI is typically transmitted in the first one or two OFDM symbols in each slot. DCI is carried on the Physical Downlink Control Channel (PDCCFI), and data is carried on the Physical Downlink Shared Channel (PDSCFI). A UE first detects and decodes PDCCFI and, if a PDCCFI is decoded successfully, the UE then decodes the corresponding PDSCFI based on the decoded DCI in the PDCCFI.

[0008] In addition to PDCCFI and PDSCFI, there are also other channels and reference signals transmitted in the DL.

[0009] UL data transmissions, carried on Physical Uplink Shared Channel (PUSCFI), are also dynamically scheduled by the gNB by transmitting a DCI. In case of Time Division Duplexing (TDD) operation, the DCI, which is transmitted in the DL region, always indicates a scheduling offset so that the PUSCFI is transmitted in a slot in the UL region.

TDD UL-DL Configuration in NR

[0010] In regard to TDD UL-DL configuration in NR, both semi-statically configured TDD and dynamic TDD are supported. For the latter, the scheduling DCI (i.e., DL assignment or UL grant) indicates which symbols within a slot are to be used for DL reception or UL transmission by the UE.

[0011] For semi-static TDD, the configuration of UL-DL patterns is very flexible. For a particular slot within the TDD pattern, symbols may be configured as either DL (denoted 'D'), UL (denoted 'U'), or flexible (denoted ' ). One use of symbols classified as 'F' is to create a guard period for DL to UL (denoted DL-UL) or UL to DL (denoted UL- DL) transitions for half-duplex devices. A cell-specific TDD pattern is either provided by a System Information Block (SIB) for the case of standalone operation or by Radio Resource Control (RRC) signaling for the case of non-standalone operation.

Additionally, a UE specific TDD pattern can be configured to override symbols of the cell-specific configuration is classified as flexible ( '). [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 patern looks like for the current and potentially future slots. This is achieved through Group Common PDCCH (GC-PDCCH) signaling carrying a DCI message with Format 2_0. DCI Format 2_0 contains one or more Slot Format Indicators (SFIs) indicating which symbols are classified as 'D', 'U', or 'F' within each of the indicated slots.

[0013] In regarding to semi-static UL-DL configuration, cell-specific semi-static configuration of the TDD patern(s) is provided from the network to the UE by the Information Element (IE) TDD-UL -DL -ConfigCommon [ 1 ] :

This IE provides the option to provide up to two concatenated TDD patterns (patern 1, pattern2) each with their own periodicity. There is a constraint that the concatenated pattern must have a total periodicity that divides 20 ms evenly in order to align with the default Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block periodicity of 20 ms assumed by the UE upon accessing a cell.

[0014] For each of the one or two concatenated patterns, the above IE defines the TDD patern as follows: • Number of full DL slots, where all symbols of these slots are classified as 'D';

• Number of symbols classified as 'D' in a partial DL slot following the last full DL slot;

• Number of symbols classified as 'U' in a partial UL slot preceding the first full UL; · Number of full UL slots, where all symbols of these slots are classified as 'U';

• Periodicity, in ms, after which the pattern repeats.

All symbols not classified as either 'D' or 'U' are assumed to be classified as 'F'.

[0015] Figure 2 shows a few exemplary cell-specific TDD patterns that can be configured semi-statically by TDD-UL-DL-ConfigCommon.

[0016] As mentioned above, an individual UE can be semi-statically configured with a

UE-specific TDD pattern that overrides parts of the ce I l-specif ica I ly configured pattern. UE-specific semi-static configuration of a TDD pattern is provided from the network to the UE by the IE TDD-UL-DL-ConfigDedicated [1]:

This IE contains a list of slots within the cell-specific TDD pattern for which the symbol classification should be overridden; however, this override can only be applied to symbols classified as flexible ('F'). For each indicated slot, the flexible symbols can be re-classified as 'allDownlink', 'allUplink', or 'explicit'. For 'explicit', 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.

[0017] In regard to dynamic indication of UL-DL configuration, in the case of 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 by signaling of one or more SFIs in DCI Format 2_0 carried by the so-called GC-PDCCFI. Each SFI indicates which symbols in a slot are classified as 'D', 'U', or 'F'. The indicated SFI(s) cannot override symbols that are already semi-statically 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 PDCCFI does not schedule any data or trigger reference signals in those symbols, then the UE neither transmits or receives on those symbols. This can be useful to cancel an instance of a periodically transmitted/received reference signal (e.g., Sounding Reference Signal (SRS), Channel State Information Reference Signal (CSI-RS)) to create 'reserved resources' for use by another technology, e.g., LTE.

[0018] The table below from Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.213 V15.3.0 [2] contains a list of possible SFIs. An SFI is an integer that takes a value from the range [0 ... 55] or the value 255. Values in the range [56 ... 254] are reserved for future use. A particular integer points to a row in the table, where each row indicates the classification for all 14 OFDM symbols of a slot. Table 1: Reproduction of Table 11.1.1-1 (Slot formats for normal cyclic prefix) from

3GPP TS 38.213 V15.3.0

[0019] As mentioned above, DCI Format 2_0 can contain an indication of SFIs for multiple slots, including the current and future slots. To limit the DCI overhead, a table of slot format combinations is preconfigured semi -statically by RRC from the gNB to the UE. A particular row in the table contains 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 is illustrated in Table 2 below, where SFIn,m is the SFI for the mth slot (mth column) of the nth slot format combination (nth row).

Table 2: RRC configuration of slot format combination table (maximal configuration). Each entry in the table is an SFI pointing to a row in Table 11 .1 .1 -1 . The maximum number of combinations is 512, and the maximum number of slots for a given combination is 256.

[0020] DCI Format 2_0 signals the slot format combination Identifier (ID) (i.e., the row number) in Table 2 for up to sixteen (16) serving cells. It is noted that this table shows the maximal configuration. A typical configuration may include many fewer rows and columns.

[0021] In regard to NR in Unlicensed Spectrum (NR-U), for a node (e.g., NR-U gNB/UE, LTE License Assisted Access (LAA) eNB/UE, or WiFi Access Point (AP) /

Station (STA)) to be allowed to transmit in unlicensed spectrum (e.g., 5 GFIz band), the node typically needs to perform a Clear Channel Assessment (CCA). This procedure typically includes sensing the medium to be idle for a number of time intervals. Sensing the medium to be idle can be done in different ways, e.g. using energy detection, using preamble detection, or using virtual carrier sensing, where the latter implies that the node reads control information from other transmitting nodes informing the node about when a transmission ends. After sensing the medium to be idle, the node is typically allowed to transmit for a certain amount of time, which is sometimes referred to as a Transmission Opportunity (TXOP). The length of the TXOP depends on regulation and type of CCA that has been performed, but typically ranges from 1 ms to 10 ms. This duration is often referred to as a Channel Occupancy Time (COT).

[0022] In WiFi, feedback of data reception Acknowledgements (ACKs) is transmitted without performing CCA. Preceding feedback transmission, a small time duration, which is called Short Interframe Space (SIFS), is introduced between the data transmission and the corresponding feedback, which does not include actual sensing of the channel. In IEEE 802.11, the SIFS period (16 microseconds (ps) for 5 GFIz OFDM Physical (PHY) layer) is defined as:

aSIFSTime = aRxPHYDelay + aMACProcessingDelay + aRxTxTurnaroundTime, where:

• aRxPHYDelay defines the duration needed by the PHY layer to deliver a

packet to the Medium Access Control (MAC) layer,

• aMACProcessingDelay defines the duration that the MAC layer needs to

trigger the PHY layer transmitting a response, and

• aRxTxTurnaroundTime defines the duration needed to turn the radio from reception into transmit mode.

Therefore, the SIFS duration is used to accommodate for the hardware delay to switch the direction from reception to transmission.

[0023] It is anticipated that, for NR-U, a similar gap to accommodate for the radio turnaround time will be allowed. For example, this will enable the transmission of Physical Uplink Control Channel (PUCCH) carrying Uplink Control Information (UCI) feedback as well as PUSCH carrying data and possible UCI within the same TXOP acquired by the initiating gNB without the UE performing CCA before PUSCH/PUCCH transmission as long as the gap between DL and UL transmission is less than or equal to 16 ps. Operation in this manner is typically called "COT sharing." Figure 3 illustrates a TXOP both with and without COT sharing after CCA is successful at the gNB. For the case of COT sharing, the gap between DL and UL transmission is less than 16 ps.

[0024] In the 3GPP RANl#94b meeting, the following agreement was made [3]:

[0025] There currently exist certain challenge(s). As described previously, NR Release 15 signaling includes a mechanism for indicating which slots and symbols within a slot are classified as DL (O'), UL ('Ll'), or flexible ( '). However, in NR-U operations, it is beneficial to signal more than just the transmission direction for each slot, as indicated in the above 3GPP RANI agreement. For example, it is beneficial to signal the duration of the COT and/or the location within a COT of the DL-UL switch within in a shared COT. This can be useful for UEs to make decisions on deferring PDCCH monitoring and/or to defer sensing the medium for the purposes of UL transmissions, e.g., transmission of Scheduling Requests (SRs). This can lead to power savings. It is an open problem of how to signal such information.

Summary

[0026] Systems and methods for operating a wireless device and a network node (e.g., a base station) in unlicensed spectrum are disclosed. In particular, systems and methods are disclosed herein for signaling a marker within a Channel Occupancy Time (COT). In some embodiments, a method performed by a wireless device for operating in unlicensed spectrum comprises obtaining a configuration of one or more slot format combinations. The slot format combinations comprise a slot format combination that comprises a value that indicates a marker within a COT comprising a plurality of slots. The marker identifies a specific time instance within the COT. The method further comprises receiving control information that identifies the slot format combination from within the obtained configuration and determining a type of the marker in the identified slot format combination from the value that indicates the marker. The method further comprises performing at least one of uplink (UL) transmission or downlink (DL) listening during the COT in accordance with the determined type of the marker and the specific time instance identified by the marker.

[0027] In some embodiments, the specific time instance within the COT is a slot. In some other embodiments, the specific time instance within the COT is a symbol. In some other embodiments, the specific time instance within the COT is a number (N) of symbols, where N is an integer number within a range of and including 1 to 14. In some other embodiments, the marker identifies the specific time instance as a starting point of the specific time instance and either: (a) a duration of the specific time instance or (b) an ending point of the specific time instance.

[0028] In some embodiments, the determined type of the marker indicates information conveyed by the marker. The information conveyed by the marker relates to a structure of the COT, wireless device behavior before, during, or after the time instance identified by the marker, or both the structure of the COT and the wireless device behavior before, during, or after the specific time instance identified by the marker.

[0029] In some embodiments, the determined type of the marker is one of a set of marker types. The set of marker types includes: (a) an end-of-COT marker type, (b) an end-of-COT UL slot marker type, (c) a DL-to-UL switch marker type, (d) an UL-to-DL switch marker type, (e) a Listen Before Talk (LBT) -not-required marker type, (f) an LBT-required marker type, (g) a Physical Downlink Control Channel (PDCCH) monitoring marker type, or any combination of any two or more of (a), (b), (c), (d), (e), (f), and

(g)·

[0030] In some embodiments, the COT comprises a COT with sharing of DL and UL transmission opportunities or a COT without sharing of DL and UL transmission opportunities.

[0031] In some embodiments, the slot format combination comprises two or more slot format indicators for two or more respective slots, and a slot format indicator from among the two or more slot format indicators is the value that indicates the marker within the COT. Further, in some embodiments, the specific time instance identified by the marker is a respective slot of the slot format indicator that is the value that indicates the marker within the COT. Further, in some embodiments, the slot format indicator that is the value that indicates the marker within the COT is mapped to one of a set of marker types. Further, in some embodiments, the set of marker types includes: (a) an end-of-COT marker type, (b) an end-of-COT UL slot marker type, (c) a DL-to-UL switch marker type, (d) an UL-to-DL switch marker type, (e) an LBT-not-required marker type, (f) an LBT-required marker type, (g) a PDCCH monitoring marker type, or any combination of any two or more of (a), (b), (c), (d), (e), (f), and (g). In some embodiments, the slot format indicator that is the value that indicates the marker within the COT is a value in a range of and including 56 to 254, wherein at least some of the values in the range are mapped to different marker types.

[0032] In some embodiments, the slot format combination comprises two or more slot format indicators for two or more respective slots, and a slot format indicator from among the two or more slot format indicators is the value that indicates the marker within the COT. Further, in some embodiments, the specific time instance identified by the marker is an identified symbol or an identified group of symbols in the respective slot of the slot format indicator that is the value that indicates the marker within the COT. Further, in some embodiments, the slot format indicator that is the value that indicates the marker within the COT is mapped to: (a) the identified symbol or the identified group of symbols in the respective slot and (b) one of a set of marker types. Further, in some embodiments, the set of marker types includes: (a) an end-of-COT marker type, (b) an end-of-COT UL slot marker type, (c) a DL-to-UL switch marker type, (d) an UL-to-DL switch marker type, (e) an LBT-not-required marker type, (f) an LBT- required marker type, (g) a PDCCFI monitoring marker type, or any combination of any two or more of (a), (b), (c), (d), (e), (f), and (g). In some embodiments, the slot format indicator that is the value that indicates the marker within the COT is a value in a range of and including 56 to 254, wherein at least some of the values in the range are mapped to different combinations of (a) marker type and (b) symbol or group of symbol positions within a slot.

[0033] In some embodiments, a second slot format indicator, from among the two or more slot format indicators comprised in the slot format combination, is a second value that indicates a second marker within the COT, wherein the second marker identifies a second specific time instance within the COT and is mapped to a second type of marker.

[0034] In some embodiments, the two or more slot format indicators comprised in the slot format combination comprise one or more slot format indicators that do not serve as markers.

[0035] In some embodiments, the two or more slot format indicators comprised in the slot format combination comprise one or more slot format indicators having values that are in a set of values consisting of {0...55, 255}.

[0036] In some embodiments, the slot format combination comprises two or more slot format indicators for two or more respective slots, and the value that indicates the marker within the COT is associated with one of the two or more slot format indicators for a respective one of the two or more respective slots. Further, in some

embodiments, the specific time instant is the respective one of the two or more respective slots, and the value is mapped to one of a set of one or more marker types. In some other embodiments, the specific time instant is a symbol or group of symbols within the respective one of the two or more respective slots, and the value is mapped to: (a) the symbol or group of symbols and (b) one of a set of marker types. In some embodiments, the set of marker types includes: (a) an end-of-COT marker type, (b) an end-of-COT UL slot marker type, (c) a DL-to-UL switch marker type, (d) an UL-to-DL switch marker type, (e) an LBT-not-required marker type, (f) an LBT-required marker type, (g) a PDCCH monitoring marker type, or any combination of any two or more of (a), (b), (c), (d), (e), (f), and (g).

[0037] In some embodiments, the slot format combination consists of a single slot format indicator for a respective slot, and the single slot format indicator is the value that indicates the marker within the COT. Further, in some embodiments, the specific time instance is a future slot, a symbol in a future slot, or a group of symbols in a future slot. In some embodiments, the single slot format indicator is mapped to one of a set of marker types.

[0038] In some embodiments, the slot format combination consists of a slot format indicator having two sub-values for a single slot, and the slot format indicator serves as the value that indicates the marker within the COT. Further, in some embodiments, the two sub-values comprise a first sub-value that indicates a reference point as a number of slots in the future relative to the single slot and a second sub-value that indicates the specific time instant as being located a number of symbols in the future relative to the reference point. In some embodiments, together, the first and second sub-values are mapped to one of a set of marker types.

[0039] In some embodiments, the slot format combination consists of a single slot format indicator for a respective slot, the single slot format indicator is the value that indicates the marker within the COT, and the marker identifies a plurality of time instances, including the time instance, within the COT. Further, in some embodiments, the plurality of time instances comprise two or more slots. In some embodiments, the slot format indicator is mapped to a first value that indicates the plurality of time instances as an offset relative to the respective slot and a duration.

[0040] In some embodiments, obtaining a configuration of at least one slot format combination comprises at least one of receiving the configuration from a network node in Radio Resource Control (RRC) signaling, or retrieving the configuration from a memory.

[0041] In some embodiments, the control information is a Downlink Control

Information (DCI).

[0042] In some embodiments, receiving the control information comprises receiving the control information from a network node on a PDCCH. In some embodiments, the PDCCH is a Group Common PDCCH (GC-PDCCH) comprising DCI Format 2_0.

[0043] In some embodiments, a method performed by a network node for operating in unlicensed spectrum comprises providing, to a wireless device, a configuration of one or more slot format combinations. The one or more slot format combinations comprise a slot format combination that comprises a value that indicates a marker within a COT comprising a plurality of slots. The marker identifies a specific time instance within the COT. The method further comprises sending, to the wireless device, a control information that identifies the slot format combination from within the obtained configuration.

[0044] In some embodiments, the specific time instance within the COT is a slot. In some other embodiments, the specific time instance within the COT is a symbol. In some other embodiments, the specific time instance within the COT is a number (N) of symbols, where N is an integer number within a range of and including 1 to 14. In some other embodiments, the marker identifies the specific time instance as a starting point of the specific time instance and either: (a) a duration of the specific time instance or (b) an ending point of the specific time instance.

[0045] In some embodiments, the marker further indicates a marker type, and the indicated marker type indicates information conveyed by the marker. The information conveyed by the marker relates to: a structure of the COT, wireless device behavior before, during, or after the time instance identified by the marker, or both the structure of the COT and the wireless device behavior before, during, or after the specific time instance identified by the marker.

[0046] In some embodiments, the marker further indicates a marker type, where the marker type is one of a set of marker types including: (a) the symbol or group of symbols and (b) one of a set of marker types. In some embodiments, the set of marker types includes: (a) an end-of-COT marker type, (b) an end-of-COT UL slot marker type, (c) a DL-to-UL switch marker type, (d) an UL-to-DL switch marker type, (e) an LBT-not- required marker type, (f) an LBT-required marker type, (g) a PDCCH monitoring marker type, or any combination of any two or more of (a), (b), (c), (d), (e), (f), and (g).

[0047] In some embodiments, the COT comprises a COT with sharing of DL and UL transmission opportunities or a COT without sharing of DL and UL transmission opportunities.

[0048] Embodiments of a wireless device are also disclosed. In some embodiments, a wireless device for operating in unlicensed spectrum comprises radio frequency transceiver circuitry and processing circuitry. The processing circuitry is configured to cause the wireless device to obtain a configuration of one or more slot format combinations comprising a slot format combination. The slot format combination comprises a value that indicates a marker within a COT comprising a plurality of slots. The marker identifies a specific time instance within the COT. The processing circuitry is further configured to cause the wireless device to receive control information that identifies the slot format combination from within the obtained configuration and determine a type of the marker in the identified slot format combination from the value that indicates the marker. The processing circuitry is further configured to cause the wireless device to perform at least one of UL transmission or DL listening during the COT in accordance with the determined type of the marker and the specific time instance identified by the marker.

[0049] Embodiments of a network node are also disclosed. In some embodiments, a network node for operating in unlicensed spectrum comprises an interface and processing circuitry configured to cause the network node to provide, to a wireless device, a configuration of one or more slot format combinations comprising a slot format combination. The slot format combination comprises a value that indicates a marker within a COT comprising a plurality of slots. The marker identifies a specific time instance within the COT. The processing circuitry is further configured to cause the network node to send, to the wireless device, control information that identifies the slot format combination from within the obtained configuration.

Brief Description of the Drawings

[0050] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0051] Figure 1 illustrates the basic New Radio (NR) resource over an antenna port;

[0052] Figure 2 illustrates four exemplary semi-statically controlled cell-specific Time Division Duplexing (TDD) patterns;

[0053] Figure 3 illustrates a Transmit Opportunity (TXOP) with and without Channel Occupancy Time (COT) sharing where Clear Channel Assessment (CCA) is performed by the initiating node (NR base station, denoted gNB);

[0054] Figure 4 illustrates one example of a wireless network in which embodiments of the present disclosure may be implemented;

[0055] Figure 5 illustrates one embodiment of a User Equipment (UE) in accordance with various aspects described herein;

[0056] Figure 6 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0057] Figure 7 illustrates an exemplary communication system in which

embodiments of the present disclosure may be implemented;

[0058] Figure 8 illustrates example implementations, in accordance with an embodiment, of the UE, base station, and host computer of Figure 7;

[0059] Figures 9 through 12 are flow charts illustrating methods implemented in a communication system in accordance with embodiments of the present disclosure;

[0060] Figure 13 depicts a method in accordance with particular embodiments;

[0061] Figure 14 illustrates a schematic block diagram of an apparatus in a wireless network (for example, the wireless network shown in Figure 4);

[0062] Figure 15 depicts a method in accordance with particular embodiments; and

[0063] Figure 16 illustrates a schematic block diagram of an apparatus in a wireless network (for example, the wireless network shown in Figure 4).

Detailed Description

[0064] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing 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 disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0065] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0066] As described previously, New Radio (NR) Release 15 (Rel-15) signaling includes a mechanism for indicating which slots and symbols within a slot are classified as downlink CD'), uplink (O'), or flexible ('F'). However, in NR in Unlicensed Spectrum (NR-U) operations, it is beneficial to signal more than just the transmission direction for each slot. For example, it is beneficial to signal the duration of the Channel Occupancy Time (COT) and/or the location within a COT of the Downlink (DL) - Uplink (UL) switch within in a shared COT. Currently, there is no mechanism for signaling such information.

[0067] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. In the present disclosure, a method of signaling a marker point within a COT is proposed. The marker point can in some examples be the end of the COT, a DL-to-UL switch point, an UL-to-DL switch point, or another type of marker point. The method of signaling may be based on existing Group Common Physical Downlink Control Channel (PDCCH) (GC-PDCCH) signaling structure, based on Downlink Control Information (DCI) Format 2_0, but may make use of reserved values in Table 11.1.1-1 in Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.213 V15.3.0 to indicate the marker point.

[0068] According to examples of the present disclosure, there is disclosed a method implemented in a User Equipment (UE) to determine one or more marker points within a COT, or shared COT. In one example, the method comprises obtaining a

configuration of one or more slot format combinations wherein a slot format

combination contains an indication of one or more marker points. The method may further comprise receiving a PDCCH comprising a DCI (also referred to herein as a DCI message) which indicates one of the configured slot format combinations. The method may further comprise determining the marker point type from the one more indications of the maker points. The method may further comprise the UE performing subsequent actions in accordance with the marker point and its determined marker point type.

Such additional actions may include changing control channel monitoring periodicity, performing or not performing a Listen-Before-Talk (LBT) procedure prior to an UL transmission, or skipping control channel monitoring during one or more clots within the COT. A slot format combination may contain one or more Slot Format Indicators (SFIs). The PDCCFI may be a GC-PDCCFI comprising DCI Format 2_0. The marker point may be at slot level granularity or may be at symbol level granularity within a slot. Determining the maker point type may comprise determining that the maker point indicates an end- of-COT indication. Determining the marker point type may comprise determining that the marker point indicates a DL-to-UL switch in a shared COT. Determining the marker point type may additionally comprise determining that the UE is not required to perform a LBT procedure prior to UL transmission. Determining the marker point type may additionally comprise determining that the UE is required to perform a LBT procedure for a fixed time duration prior to UL transmission. The fixed time duration may be 25 microseconds (ps). Determining the marker point type may comprise determining that the marker point indicates a UL-to-DL switch in a shared COT.

[0069] Certain embodiments may provide one or more of the following technical advantage(s). Examples of methods disclosed herein represent a low overhead approach for signaling a marker point within a COT. Examples of methods disclosed herein make use of existing GC-PDCCH signaling, thus having minimal specification impact. Signaling of a marker point may be beneficial to inform UEs of what type of LBT to apply prior to UL transmissions in a shared COT. Signaling of a marker point may be beneficial for UEs to make decisions on deferring PDCCH monitoring and/or to defer sensing the medium for the purposes of UL transmissions, e.g., transmission of Scheduling Requests (SRs). This can lead to power savings. [0070] According to one aspect of the present disclosure, there is provided a method performed by a wireless device for operating in unlicensed spectrum, the method comprising:

- obtaining a configuration of at least one slot format combination, wherein a slot format combination comprises a value indicating a marker within a COT comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT;

- receiving control information identifying a slot format combination from within the obtained configuration;

- determining a type of the marker in the identified slot format combination from the value indicating the marker; and

- performing at least one of UL transmission or DL listening during the COT in accordance with the determined type of the marker and the time instance identified by the marker.

The wireless device may for example comprise a UE.

[0071] According to examples of the present disclosure, the marker type may indicate information conveyed by the marker, the information relating to at least one of a structure of the COT and/or wireless device behavior before, during, or after the time instance identified by the marker. Information relating to a structure of the COT may for example include information about when the COT ends, or when a DL-to-UL or UL- to-DL transition occurs within a shared COT, or whether a particular time slot within a COT is a DL or UL slot. Information relating to wireless device behavior before, during, or after the time instance identified by the marker may include whether or not the wireless device should perform a LBT procedure prior to UL transmission, and for how long this procedure should be performed, and/or monitoring periodicity for PDCCH monitoring, for example including whether such monitoring may be skipped for a specific time instance or multiple time instances.

[0072] Actions comprised within the step of performing at least one of UL transmission or DL listening during the COT in accordance with the determined type of the marker and the time instance identified by the marker may vary according to the type of the marker and thus the information conveyed by the marker. Thus for the example of a marker indicating an end-of-COT, one example wireless device behavior in response to the end-of-COT, which behavior may be encompassed within the final step of the above described method, is to change its control channel (PDCCH) monitoring periodicity. For example, the UE may monitor once per slot within the COT, and then monitor multiple times per slot after the COT ends. Another example wireless device behavior which may be compassed within the final step of the above described method is that, in response to one type of marker (an LBT-required marker as described below and illustrated as example value R5), the wireless device performs a 25 ps LBT prior to an UL transmission. Another example wireless device behavior which may be compassed within the final step of the above described method is that, in response to another type of marker (an LBT-not-required marker as described below and illustrated as example value R4), the wireless device does not perform LBT prior to the UL transmission. Another example wireless device behavior which may be compassed within the final step of the above described method is that, in response to another type of marker (a PDCCH monitoring marker as described below and illustrated as example value R8), the wireless device skips control channel (PDCCH) monitoring during one more slots within the COT indicated by the slot format combination.

[0073] According to examples of the present disclosure, the COT may comprise at least one of a COT with sharing of DL and UL transmission opportunities and/or a COT without sharing of DL and UL transmission opportunities.

[0074] According to examples of the present disclosure, a slot format combination may comprise at least one SFI. According to some examples of the present disclosure, the at least one SFI may comprise the value indicating a marker. According to further examples, the SFI may be in addition to the value indicating a marker. According to still further examples, a slot format combination may comprise a plurality of SFIs, one or more of which may comprise value indicating markers, and one or more of which may comprise SFIs that do not indicate markers. For example, a slot format combination may comprise one or more SFIs selected from the range [56 ... 254], reserved for future use according to 3GPP TS 38.213 V15.3.0 [2] and used to indicate a marker according to examples of the present disclosure, and one or more SFIs selected from the range [0 ... 55] and specified in 3GPP TS 38.213 V15.3.0 [2].

[0075] According to examples of the present disclosure, obtaining a configuration of at least one slot format combination may comprise at least one of receiving the configuration from a base station in Radio Resource Control (RRC) signaling, or retrieving the configuration from a memory. Thus for example, the wireless device may initially receive the configuration from a base station in RRC signaling, and may store the received configuration in a memory. The wireless device may then retrieve the configuration from the memory at a later time.

[0076] According to examples of the present disclosure, the control information may comprise a DCI. According to further examples of the present disclosure, receiving control information may comprise receiving the control information from a base station on a PDCCH. The PDCCH may be a GC-PDCCH comprising DCI Format 2_0.

[0077] According to examples of the present disclosure, determining a type of the marker may comprise using a mapping to translate the value indicating the marker to the type of marker indicated. In some examples, the mapping may comprise a table and may comprise Table 11.1.1-1 from 3GPP TS 38.213 V15.3.0, reproduced above, amended to include mappings between values reserved for future use in the version reproduced above and marker types, as discussed in further detail below. Thus in certain examples, the value indicating a marker may comprise a SFI value that is reserved for future use according to 3GPP TS 38.213 V15.3.0 [2], and may therefore comprise a value in the range [56 ... 254].

[0078] The following examples illustrate different options for ways in which the value indicating the marker may be included in the configuration of at least one slot format combination, ways in which the value may indicate the marker, information that may be conveyed by the marker through different marker types, etc. In the following examples, the terms "marker" and "marker point" may be used interchangeably to refer to the "marker" discussed above and set out in the numbered embodiments below.

Example 1: Marker point signaled with slot-level granularity

[0079] Within a slot format combination signaled by DCI Format 2_0, the marker point is indicated at slot-level granularity, such that the time instance identified by the marker comprises a time slot. The marker slot is indicated by use of a reserved value in the range [56 ... 254] of Table 11.1.1.1 of 3GPP TS 38.213 V15.3.0. The reserved value indicating a marker is written into the slot format combination at a positon corresponding to the time slot that is identified by the marker. A different reserved value can be used to indicate different marker types, e.g. :

1. Reserved value Rl : Indicates that end-of-COT occurs in a slot

2. Reserved value R2: Indicates that a slot is an UL slot and that end-of-COT occurs in that slot

3. Reserved value R3: Indicates that a DL-to-UL switch occurs in a slot of a shared COT

4. Reserved value R4: Indicates that a DL-to-UL switch occurs in a slot of a shared COT and that the UE is not required to perform LBT prior to the start of the UL transmission, e.g., since the switching gap is less than 16 ps

5. Reserved value R5: Indicates that a DL-to-UL switch occurs in a slot of a shared COT and that the UE is required to perform a 25 ps LBT prior to start of the UL transmission, e.g., since the switching gap is more than 16 ps

6. Reserved value R6: Indicates that an UL-to-DL switch occurs in a slot of a shared COT

7. Reserved value R8: Indicates that a UE may skip PDCCH monitoring in a slot of a COT unless it has received a dedicated DL and/or UL grant in a prior slot within the COT

[0080] Exemplary slot format combinations for the marker slot could be configured as follows (as shown in Table 3), where the reserved value Ri in any row of the table can be any one of the values from the above list:

Table 3: RRC configured slot format combination table for dynamic indication of a marker slot up to 3 slots in advance

[0081] In this example shown in Table 3, the reserved value R in any given row is configured depending on what marker slot type is desired for a particular slot. With this exemplary configuration, the marker slot can be signaled up to three slots in advance. If it is desired to signal further in advance, then the number of columns in the slot format configuration table can be increased. For example, the number of columns could be increased to the maximum number of slots in a Maximum COT (MCOT) length, so that one of the rows in the table effectively signals the COT duration.

[0082] In a variation of this example, a slot format combination (row of the table) can be configured with more than one reserved value in different columns meaning that two or more marker slots are indicated, e.g., DL-to-UL switch and end-of-COT.

[0083] In another variation of this example, any of the non-reserved SFI values, i.e. SFNm,n, can be configured with the value 255 such that the UE "...determines the slot format for the slot based on TDD-UL-DL-ConfigurationCommon, or TDD-UL-DL- Con fig Dedicated and, if any, on detected DCI formats" as shown in Table 11.1.1-1 from 3GPP TS 38.213 V15.3.0 and reproduced above in Table 1. In this case, the slot format combination (row of the table) only indicates the marker slot. No other indication of slot format is given to the UE other than that which it already assumes, e.g., through RRC configuration or prior SFI signaling.

[0084] In another variation of this example, the reserved value R and an SFI corresponding to the marker slot are jointly configured for a particular slot within a slot format combination, such that both the reserved value and the SFI corresponding to the marker slot are written into a position of the slot format combination that corresponds to the same time slot. An example of this is as follows in Table 4:

Table 4: RRC configured slot format combination table for dynamic indication of a marker slot up to 3 slots in advance. In this configuration, both the marker slot type and the slot format are configured for a particular slot.

Example 2: Marker point signaled with Orthogonal Frequency Division Multiplexing

(OFDM) symbol level granularity [0085] Example 2 is very similar to Example 1, except that within a slot format combination signaled by DCI Format 2_0, the marker point is indicated at symbol-level granularity within a slot instead of at slot-level granularity. In this manner, the time instance identified by the marker comprises a symbol within a time slot. The marker symbol is indicated by use of a reserved value in the range [56 ... 254] of Table 11.1.1.1, and the value indicating the marker is configured at a position within the slot format combination that corresponds to the time slot within which the symbol occurs. A difference from Example 1 is that multiple reserved values are used to indicate different symbols within a slot for a particular marker type, rather than just a single reserved value. For example, if the desired granularity is three symbols per slot, then R1 indicates a first symbol within the slot, R2 indicates a second symbol, and R3 indicates a third symbol, where all of Rl, R2, and R3 indicate the same marker type. In general, any granularity from 1 up to 14 symbols per slot may be used. Accordingly, determining a type of the marker in the identified slot format combination from the value indicating the marker may comprise using a mapping to translate the value indicating the marker to the type of marker indicated and to the symbol within the time slot at which the marker is positioned. The same marker types listed for Example 1 apply to this Example, and for a given marker type, a plurality of values may correspond to the same marker type positioned at different symbols within a given time slot. The variations discussed above with respect to Example 1 also apply to this Example, such that multiple markers may be indicated within a single slot format combination, which markers may be of different types, non-reserved values in the slot format combination may be configured with the value 255, and both a reserved value indicating a marker and an SFI corresponding to the slot in which the marker occurs may be jointly configured for the slot in which the marker occurs.

Example 3: Explicit indication marker point position

[0086] As an alternative to Examples 1 and 2, a marker point position with slot or symbol-level granularity can be explicitly indicated using a reserved value in the range [56 ... 254] of Table 11.1.1.1. In this Example, rather than configuring a reserved value at a particular position in an RRC configured slot format combination, a slot format combination with only one slot is configured and the reserved value itself encodes the specific time instance identified by the marker, e.g., for a time instance of a time slot, value Ri indicates that the time instance is N slots in the future, Rj in N+l slots, Rk in N+2 slots, etc., as illustrated in Table 5 below. Depending upon the type of the marker, this may indicate that the COT ends N slots in the future, Rj in N+l slots, Rk in N+2 slots, etc., or that a DL-to-UL transition occurs N slots in the future, Rj in N+l slots, Rk in N+2 slots, etc. Determining a type of the marker in the identified slot format combination from the value indicating the marker may therefore comprise using a mapping (such as the Table 11.1.1-1 suitable updated) to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker. The same marker types listed for Example 1 apply to this Example.

Table 5: RRC configured slot format combination table for explicit indication of a marker point position with slot-level granularity

[0087] In a variation of the description above for Example 3, two reserved values can be configured in a given row to indicate the marker point position with symbol-level granularity, such that the time instance identified by the marker is a symbol within a time slot. In such a variation, the value Ri may indicate that the time instance is N symbols in the future, Rj in N+l symbols, Rk in N+2 symbols, etc., the symbols counted from a reference point. In such a variation, the value indicating the marker may comprise two sub values as illustrated in Table 6 below, and a first of which may be translated via the mapping to a number of slots, the number of slots, when counted from the present slot, indicating a reference point, and a second of which may translated via the mapping to a number of symbols, the number of symbols, when counted from the reference point, indicating the symbol identified by the marker. The reference point may thus comprise a beginning of the first slot after the end of the slots indicated by the first sub value.

Table 6: RRC configured slot format combination table for explicit indication of a marker point position with symbol-level granularity

[0088] For example, ,o and ,i in Table 6 together indicate that the COT ends (or a DL-to-UL transition etc. occurs) at a particular symbol position within a partial slot following a number of full slots. Ri,o indicates the number of full slots and R,i indicates the number of symbols in the partial slot after the last full slot.

Example 4: Explicit indication of a subset of slots within a COT

[0089] In a variation of Example 3, the marker may identify a plurality of time instances, and may identify a subset of slots within the COT. The subset may be identified via a mapping from the value indicating the marker to an indication of at least one of a start point and end point for the subset, or a start point and duration of the subset. A particular reserved value R may thus jointly encode both an offset and a duration for a particular subset of slots of a COT. For example, R indicates that the subset of slots starts N slots in the future and has a duration of D slots. Alternatively, R indicates that the subset starts Ni slots in the future and ends N ₂ slots in the future where N ₂ > Ni. Different reserved values indicate different combinations, respectively, of N and D or of Ni and N ₂ . The different marker types described above with reference to Example 1 also apply to this example, such that a different range of reserved values may be used to indicate different UE behavior. For example, one range of reserved values may be used to indicate to the UE that it may perform 25 ps LBT for all UL transmissions in a shared COT in the slots within the indicated subset (similar functionality as reserved value R5 in Example 1). Another range could be used to indicate to the UE that it may skip PDCCFI monitoring in the slots within the indicated subset (similar functionality as reserved value R7 in Example 1).

Additional Aspects

[0090] According to another aspect of the present disclosure, there is provided a method performed by a base station for operating in unlicensed spectrum, the method comprising:

- providing to a wireless device a configuration of at least one slot format

combination, wherein a slot format combination comprises a value indicating a marker within a COT comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT;

- sending to the wireless device a control information identifying a slot format combination from within the obtained configuration;

- identifying a type of the marker in the identified slot format combination from the value indicating the marker; and

- performing at least one of DL transmission or UL listening during the COT in accordance with the identified type of the marker and the time instance identified by the marker.

[0091] Examples of the method performed by the base station may compliment examples of the method performed by a wireless device described above, such that the base station and wireless device together operate in unlicensed spectrum, in accordance with the various examples and embodiments of the present disclosure. The above discussion, including inter alia the discussion of different examples for the incorporation of a value indicating a marker into a slot format combination, the types of marker and information that may be conveyed by the marker, and actions encompassed within the final step of the method ("performing at least one of..."), etc., apply equally to the method performed by a base station set out above.

[0092] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 4. For simplicity, the wireless network of Figure 4 only depicts network 406, network nodes 460 and 460b, and Wireless Devices (WDs) 410, 410b, and 410c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 460 and WD 410 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network. In some examples, the WDs 410, 410b, and 410c may operate similarly to the wireless device or UE described previously and set out below in the numbered embodiments, and the network nodes 460 and 460b may operate similarly to the base station described previously and set out below in the numbered embodiments.

[0093] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or

procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards; Wireless Local Area Network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0094] Network 406 may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, Public Switched Telephone Networks (PSTNs), packet data networks, optical networks, Wide Area etworks (WANs), Local Area Networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0095] Network node 460 and WD 410 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

[0096] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, Access Points (APs) (e.g., radio access points), Base Stations (BSs) (e.g., radio base stations, Node Bs, enhanced or evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay.

A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS). Yet further examples of network nodes include Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), core network nodes (e.g., Mobile Switching Centers (MSCs), Mobility Management Entities (MMEs)), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[0097] In Figure 4, network node 460 includes processing circuitry 470, device readable medium 480, interface 490, auxiliary equipment 484, power source 486, power circuitry 487, and antenna 462. Although network node 460 illustrated in the example wireless network of Figure 4 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 460 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 480 may comprise multiple separate hard drives as well as multiple Random Access Memory (RAM) modules).

[0098] Similarly, network node 460 may be composed of multiple physically separate components (e.g., a Node B component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.

In certain scenarios in which network node 460 comprises multiple separate

components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique Node B and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 460 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 480 for the different RATs) and some components may be reused (e.g., the same antenna 462 may be shared by the RATs). Network node 460 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 460.

[0099] Processing circuitry 470 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 470 may include processing information obtained by processing circuitry 470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0100] Processing circuitry 470 may comprise a combination of one or more of a microprocessor, controller, microcontroller, Central Processing Unit (CPU), Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 460 components, such as device readable medium 480, network node 460 functionality. For example, processing circuitry 470 may execute instructions stored in device readable medium 480 or in memory within processing circuitry 470. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 470 may include a System on a Chip (SOC).

[0101] In some embodiments, processing circuitry 470 may include one or more of Radio Frequency (RF) transceiver circuitry 472 and baseband processing circuitry 474.

In some embodiments, RF transceiver circuitry 472 and baseband processing circuitry 474 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 472 and baseband processing circuitry 474 may be on the same chip or set of chips, boards, or units.

[0102] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 470 executing instructions stored on device readable medium 480 or memory within processing circuitry 470. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 470 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 470 alone or to other components of network node 460, but are enjoyed by network node 460 as a whole, and/or by end users and the wireless network generally.

[0103] Device readable medium 480 may comprise any form of volatile or non- volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, Read Only Memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 470. Device readable medium 480 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 470 and, utilized by network node 460. Device readable medium 480 may be used to store any calculations made by processing circuitry 470 and/or any data received via interface 490. In some embodiments, processing circuitry 470 and device readable medium 480 may be considered to be integrated.

[0104] Interface 490 is used in the wired or wireless communication of signaling and/or data between network node 460, network 406, and/or WDs 410. As illustrated, interface 490 comprises port(s)/terminal(s) 494 to send and receive data, for example to and from network 406 over a wired connection. Interface 490 also includes radio front end circuitry 492 that may be coupled to, or in certain embodiments a part of, antenna 462. Radio front end circuitry 492 comprises filters 498 and amplifiers 496. Radio front end circuitry 492 may be connected to antenna 462 and processing circuitry 470. Radio front end circuitry may be configured to condition signals communicated between antenna 462 and processing circuitry 470. Radio front end circuitry 492 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 492 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 498 and/or amplifiers 496. The radio signal may then be transmitted via antenna 462. Similarly, when receiving data, antenna 462 may collect radio signals which are then converted into digital data by radio front end circuitry 492. The digital data may be passed to processing circuitry 470. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0105] In certain alternative embodiments, network node 460 may not include separate radio front end circuitry 492, instead, processing circuitry 470 may comprise radio front end circuitry and may be connected to antenna 462 without separate radio front end circuitry 492. Similarly, in some embodiments, all or some of RF transceiver circuitry 472 may be considered a part of interface 490. In still other embodiments, interface 490 may include one or more ports or terminals 494, radio front end circuitry 492, and RF transceiver circuitry 472, as part of a radio unit (not shown), and interface 490 may communicate with baseband processing circuitry 474, which is part of a digital unit (not shown).

[0106] Antenna 462 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 462 may be coupled to radio front end circuitry 490 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 462 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 gigahertz (GHz) and 66 GHz. An omni-directional antenna may be used to transmit/ receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to

transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as Multiple Input Multiple Output (MIMO).

In certain embodiments, antenna 462 may be separate from network node 460 and may be connectable to network node 460 through an interface or port.

[0107] Antenna 462, interface 490, and/or processing circuitry 470 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 462, interface 490, and/or processing circuitry 470 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[0108] Power circuitry 487 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 460 with power for performing the functionality described herein. Power circuitry 487 may receive power from power source 486. Power source 486 and/or power circuitry 487 may be configured to provide power to the various components of network node 460 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 486 may either be included in, or external to, power circuitry 487 and/or network node 460. For example, network node 460 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 487. As a further example, power source 486 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 487. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[0109] Alternative embodiments of network node 460 may include additional components beyond those shown in Figure 4 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 460 may include user interface equipment to allow input of information into network node 460 and to allow output of information from network node 460. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 460.

[0110] As used herein, WD refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with UE. Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a

predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a Personal Digital Assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a Laptop Embedded Equipment (LEE), a Laptop Mounted Equipment (LME), a smart device, a wireless Customer Premise Equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Vehicle-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a Machine-to-Machine (M2M) device, which may in a 3GPP context be referred to as an Machine Type Communication (MTC) device. As one particular example, the WD may be a UE implementing the 3GPP Narrowband IoT (NB- IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0111] As illustrated, wireless device 410 includes antenna 411, interface 414, processing circuitry 420, device readable medium 430, user interface equipment 432, auxiliary equipment 434, power source 436 and power circuitry 437. WD 410 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 410.

[0112] Antenna 411 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 414.

In certain alternative embodiments, antenna 411 may be separate from WD 410 and be connectable to WD 410 through an interface or port. Antenna 411, interface 414, and/or processing circuitry 420 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 411 may be considered an interface.

[0113] As illustrated, interface 414 comprises radio front end circuitry 412 and antenna 411. Radio front end circuitry 412 comprise one or more filters 418 and amplifiers 416. Radio front end circuitry 414 is connected to antenna 411 and processing circuitry 420, and is configured to condition signals communicated between antenna 411 and processing circuitry 420. Radio front end circuitry 412 may be coupled to or a part of antenna 411. In some embodiments, WD 410 may not include separate radio front end circuitry 412; rather, processing circuitry 420 may comprise radio front end circuitry and may be connected to antenna 411. Similarly, in some embodiments, some or all of RF transceiver circuitry 422 may be considered a part of interface 414. Radio front end circuitry 412 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 412 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 418 and/or amplifiers 416. The radio signal may then be transmitted via antenna 411. Similarly, when receiving data, antenna 411 may collect radio signals which are then converted into digital data by radio front end circuitry 412. The digital data may be passed to processing circuitry 420. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0114] Processing circuitry 420 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 410 components, such as device readable medium 430, WD 410 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 420 may execute instructions stored in device readable medium 430 or in memory within processing circuitry 420 to provide the functionality disclosed herein.

[0115] As illustrated, processing circuitry 420 includes one or more of RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426. In other embodiments, the processing circuitry may comprise different

components and/or different combinations of components. In certain embodiments processing circuitry 420 of WD 410 may comprise a SOC. In some embodiments, RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 424 and application processing circuitry 426 may be combined into one chip or set of chips, and RF transceiver circuitry 422 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 422 and baseband processing circuitry 424 may be on the same chip or set of chips, and application processing circuitry 426 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 422, baseband processing circuitry 424, and application processing circuitry 426 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 422 may be a part of interface 414. RF transceiver circuitry 422 may condition RF signals for processing circuitry 420.

[0116] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 420 executing instructions stored on device readable medium 430, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 420 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 420 alone or to other components of WD 410, but are enjoyed by WD 410 as a whole, and/or by end users and the wireless network generally.

[0117] Processing circuitry 420 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 420, may include processing information obtained by processing circuitry 420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 410, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0118] Device readable medium 430 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 420. Device readable medium 430 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a CD or a DVD), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 420. In some embodiments, processing circuitry 420 and device readable medium 430 may be considered to be integrated.

[0119] User interface equipment 432 may provide components that allow for a human user to interact with WD 410. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 432 may be operable to produce output to the user and to allow the user to provide input to WD 410. The type of interaction may vary depending on the type of user interface equipment 432 installed in WD 410. For example, if WD 410 is a smart phone, the interaction may be via a touch screen; if WD 410 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 432 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 432 is configured to allow input of information into WD 410, and is connected to processing circuitry 420 to allow processing circuitry 420 to process the input information. User interface equipment 432 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a Universal Serial Bus (USB) port, or other input circuitry. User interface equipment 432 is also configured to allow output of information from WD 410, and to allow processing circuitry 420 to output information from WD 410. User interface equipment 432 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 432, WD 410 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[0120] Auxiliary equipment 434 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 434 may vary depending on the embodiment and/or scenario.

[0121] Power source 436 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 410 may further comprise power circuitry 437 for delivering power from power source 436 to the various parts of WD 410 which need power from power source 436 to carry out any functionality described or indicated herein. Power circuitry 437 may in certain embodiments comprise power management circuitry. Power circuitry 437 may additionally or alternatively be operable to receive power from an external power source; in which case WD 410 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 437 may also in certain embodiments be operable to deliver power from an external power source to power source 436. This may be, for example, for the charging of power source 436. Power circuitry 437 may perform any formatting, converting, or other modification to the power from power source 436 to make the power suitable for the respective components of WD 410 to which power is supplied.

[0122] Figure 5 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 500 may be any UE identified by the 3GPP, including a NB-IoT UE, a MTC UE, and/or an enhanced MTC (eMTC) UE. UE 500, as illustrated in Figure 5, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3GPP, such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 5 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa. The UE 500 may comprise a wireless device or UE as described with respect to any of the examples and

embodiments described above and set out in the numbered embodiments below.

[0123] In Figure 5, UE 500 includes processing circuitry 501 that is operatively coupled to input/output interface 505, RF interface 509, network connection interface 511, memory 515 including RAM 517, ROM 519, and storage medium 521 or the like, communication subsystem 531, power source 533, and/or any other component, or any combination thereof. Storage medium 521 includes operating system 523, application program 525, and data 527. In other embodiments, storage medium 521 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 5, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0124] In Figure 5, processing circuitry 501 may be configured to process computer instructions and data. Processing circuitry 501 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware- implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or DSP, together with appropriate software; or any combination of the above. For example, the processing circuitry 501 may include two CPUs. Data may be information in a form suitable for use by a computer.

[0125] In the depicted embodiment, input/output interface 505 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 500 may be configured to use an output device via input/output interface 505. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 500. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 500 may be configured to use an input device via input/output interface 505 to allow a user to capture information into UE 500. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0126] In Figure 5, RF interface 509 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 511 may be configured to provide a communication interface to network 543a. Network 543a may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 543a may comprise a Wi-Fi network. Network connection interface 511 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, Transmission Control Protocol (TCP) /IP, Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), or the like. Network connection interface 511 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[0127] RAM 517 may be configured to interface via bus 502 to processing circuitry 501 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 519 may be configured to provide computer instructions or data to processing circuitry 501. For example, ROM 519 may be configured to store invariant low-level system code or data for basic system functions such as basic Input and Output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non- volatile memory. Storage medium 521 may be configured to include memory such as RAM, ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 521 may be configured to include operating system 523, application program 525 such as a web browser application, a widget or gadget engine or another application, and data file 527. Storage medium 521 may store, for use by UE 500, any of a variety of various operating systems or combinations of operating systems.

[0128] Storage medium 521 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini-Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM

(SDRAM), external micro-DIMM SDRAM, smartcard memory such as a Subscriber Identity Module (SIM) or a Removable User Identity Module (RUIM), other memory, or any combination thereof. Storage medium 521 may allow UE 500 to access computer- executable instructions, application programs or the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of

manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 521, which may comprise a device readable medium.

[0129] In Figure 5, processing circuitry 501 may be configured to communicate with network 543b using communication subsystem 531. Network 543a and network 543b may be the same network or networks or different network or networks.

Communication subsystem 531 may be configured to include one or more transceivers used to communicate with network 543b. For example, communication subsystem 531 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a Radio Access Network (RAN) according to one or more communication protocols, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, Universal Terrestrial Radio Access Network (UTRAN), WiMax, or the like. Each transceiver may include transmitter 533 and/or receiver 535 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 533 and receiver 535 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0130] In the illustrated embodiment, the communication functions of

communication subsystem 531 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 531 may include cellular communication, WiFi communication, Bluetooth communication, and GPS

communication. Network 543b may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 543b may be a cellular network, a WiFi network, and/or a near-field network. Power source 513 may be configured to provide Alternating Current (AC) or Direct Current (DC) power to components of UE 500.

[0131] The features, benefits, and/or functions described herein may be

implemented in one of the components of UE 500 or partitioned across multiple components of UE 500. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem 531 may be configured to include any of the components described herein. Further, processing circuitry 501 may be configured to communicate with any of such components over bus 502. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 501 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 501 and communication subsystem 531. In another example, the non-computationally intensive functions of any of such

components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[0132] Figure 6 is a schematic block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0133] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 600 hosted by one or more of hardware nodes 630. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[0134] The functions may be implemented by one or more applications 620 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Applications 620 are run in virtualization environment 600 which provides hardware 630 comprising processing circuitry 660 and memory 690. Memory 690 contains instructions 695 executable by processing circuitry 660 whereby application 620 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[0135] Virtualization environment 600, comprises general-purpose or special-purpose network hardware devices 630 comprising a set of one or more processors or processing circuitry 660, which may be Commercial Off-the-Shelf (COTS) processors, dedicated ASICs, or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 690-1 which may be non-persistent memory for temporarily storing instructions 695 or software executed by processing circuitry 660. Each hardware device may comprise one or more Network Interface Controllers (NICs) 670, also known as network interface cards, which include physical network interface 680. Each hardware device may also include non-transitory, persistent, machine-readable storage media 690-2 having stored therein software 695 and/or instructions executable by processing circuitry 660. Software 695 may include any type of software including software for instantiating one or more virtualization layers 650 (also referred to as hypervisors), software to execute virtual machines 640 as well as software allowing it to execute functions, features and/or benefits described in relation with some

embodiments described herein. [0136] Virtual machines 640, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 650 or hypervisor. Different embodiments of the instance of virtual appliance 620 may be implemented on one or more of virtual machines 640, and the implementations may be made in different ways.

[0137] During operation, processing circuitry 660 executes software 695 to instantiate the hypervisor or virtualization layer 650, which may sometimes be referred to as a Virtual Machine Monitor (VMM). Virtualization layer 650 may present a virtual operating platform that appears like networking hardware to virtual machine 640.

[0138] As shown in Figure 6, hardware 630 may be a standalone network node with generic or specific components. Hardware 630 may comprise antenna 6225 and may implement some functions via virtualization. Alternatively, hardware 630 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via Management and Orchestration (MANO) 6100, which, among others, oversees lifecycle management of applications 620.

[0139] Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and CPE.

[0140] In the context of NFV, virtual machine 640 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of virtual machines 640, and that part of hardware 630 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 640, forms a separate Virtual Network Elements (VNE).

[0141] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 640 on top of hardware networking infrastructure 630 and corresponds to application 620 in Figure 6.

[0142] In some embodiments, one or more radio units 6200 that each include one or more transmitters 6220 and one or more receivers 6210 may be coupled to one or more antennas 6225. Radio units 6200 may communicate directly with hardware nodes 630 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0143] In some embodiments, some signaling can be effected with the use of control system 6230 which may alternatively be used for communication between the hardware nodes 630 and radio units 6200.

[0144] With reference to Figure 7, in accordance with an embodiment, a

communication system includes telecommunication network 710, such as a 3GPP-type cellular network, which comprises access network 711, such as a radio access network, and core network 714. Access network 711 comprises a plurality of base stations 712a, 712b, 712c, such as Node Bs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 713a, 713b, 713c. Each base station 712a, 712b, 712c is connectable to core network 714 over a wired or wireless connection 715. Each base station 712a, 712b, 712c may be configured to operate as described with respect to any of the base stations in the embodiments described above and set out in the numbered embodiments below. A first UE 791 located in coverage area 713c is configured to wirelessly connect to, or be paged by, the corresponding base station 712c. A second UE 792 in coverage area 713a is wirelessly connectable to the corresponding base station 712a. While a plurality of UEs 791, 792 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 712. Each of the UEs 791, 792 may be configured to operate as described with respect to any of the UEs or wireless devices in the embodiments described above and set out in the numbered embodiments below.

[0145] Telecommunication network 710 is itself connected to host computer 730, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 730 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.

Connections 721 and 722 between telecommunication network 710 and host computer 730 may extend directly from core network 714 to host computer 730 or may go via an optional intermediate network 720. Intermediate network 720 may be one of, or a combination of more than one of, a public, private, or hosted network; intermediate network 720, if any, may be a backbone network or the Internet; in particular, intermediate network 720 may comprise two or more sub-networks (not shown).

[0146] The communication system of Figure 7 as a whole enables connectivity between the connected UEs 791, 792 and host computer 730. The connectivity may be described as an Over-the-Top (OTT) connection 750. Host computer 730 and the connected UEs 791, 792 are configured to communicate data and/or signaling via OTT connection 750, using access network 711, core network 714, any intermediate network 720 and possible further infrastructure (not shown) as intermediaries. OTT connection 750 may be transparent in the sense that the participating communication devices through which OTT connection 750 passes are unaware of routing of uplink and downlink communications. For example, base station 712 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 730 to be forwarded (e.g., handed over) to a connected UE 791. Similarly, base station 712 need not be aware of the future routing of an outgoing uplink communication originating from the UE 791 towards the host computer 730.

[0147] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 8. In communication system 800, host computer 810 comprises hardware 815 including communication interface 816 configured to set up and maintain a wired or wireless connection with an interface of a different

communication device of communication system 800. Host computer 810 further comprises processing circuitry 818, which may have storage and/or processing capabilities. In particular, processing circuitry 818 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. Host computer 810 further comprises software 811, which is stored in or accessible by host computer 810 and executable by processing circuitry 818. Software 811 includes host application 812. Host application 812 may be operable to provide a service to a remote user, such as UE 830 connecting via OTT connection 850 terminating at UE 830 and host computer 810. In providing the service to the remote user, host application 812 may provide user data which is transmitted using OTT connection 850.

[0148] Communication system 800 further includes base station 820 provided in a telecommunication system and comprising hardware 825 enabling it to communicate with host computer 810 and with UE 830. Hardware 825 may include communication interface 826 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 800, as well as radio interface 827 for setting up and maintaining at least wireless connection 870 with UE 830 located in a coverage area (not shown in Figure 8) served by base station 820. Communication interface 826 may be configured to facilitate connection 860 to host computer 810. Connection 860 may be direct or it may pass through a core network (not shown in Figure 8) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 825 of base station 820 further includes processing circuitry 828, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 820 further has software 821 stored internally or accessible via an external connection.

[0149] Communication system 800 further includes UE 830 already referred to. Its hardware 835 may include radio interface 837 configured to set up and maintain wireless connection 870 with a base station serving a coverage area in which UE 830 is currently located. Hardware 835 of UE 830 further includes processing circuitry 838, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 830 further comprises software 831, which is stored in or accessible by UE 830 and executable by processing circuitry 838.

Software 831 includes client application 832. Client application 832 may be operable to provide a service to a human or non-human user via UE 830, with the support of host computer 810. In host computer 810, an executing host application 812 may communicate with the executing client application 832 via OTT connection 850 terminating at UE 830 and host computer 810. In providing the service to the user, client application 832 may receive request data from host application 812 and provide user data in response to the request data. OTT connection 850 may transfer both the request data and the user data. Client application 832 may interact with the user to generate the user data that it provides.

[0150] It is noted that host computer 810, base station 820 and UE 830 illustrated in Figure 8 may be similar or identical to host computer 730, one of base stations 712a, 712b, 712c and one of UEs 791, 792 of Figure 7, respectively. This is to say, the inner workings of these entities may be as shown in Figure 8 and independently, the surrounding network topology may be that of Figure 7.

[0151] In Figure 8, OTT connection 850 has been drawn abstractly to illustrate the communication between host computer 810 and UE 830 via base station 820, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 830 or from the service provider operating host computer 810, or both. While OTT connection 850 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0152] Wireless connection 870 between UE 830 and base station 820 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 830 using OTT connection 850, in which wireless connection 870 forms the last segment. More precisely, the teachings of these embodiments may facilitate operation in the unlicensed spectrum and may improve power consumption when doing so. The teachings of these embodiments may thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime.

[0153] A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT

connection 850 between host computer 810 and UE 830, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 850 may be implemented in software 811 and hardware 815 of host computer 810 or in software 831 and hardware 835 of UE 830, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 850 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 811, 831 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 820, and it may be unknown or imperceptible to base station 820. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 810's measurements of throughput, propagation times, latency and the like. The

measurements may be implemented in that software 811 and 831 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 850 while it monitors propagation times, errors etc.

[0154] Figure 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section. In step 910, the host computer provides user data. In substep 911 (which may be optional) of step 910, the host computer provides the user data by executing a host application. In step 920, the host computer initiates a transmission carrying the user data to the UE. In step 930 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 940 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0155] Figure 10 is a flowchart illustrating a method implemented in a

communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section. In step 1010 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1020, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1030 (which may be optional), the UE receives the user data carried in the transmission.

[0156] Figure 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section. In step 1110 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1120, the UE provides user data. In substep 1121 (which may be optional) of step 1120, the UE provides the user data by executing a client application. In substep 1111 (which may be optional) of step 1110, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1130 (which may be optional), transmission of the user data to the host computer. In step 1140 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0157] Figure 12 is a flowchart illustrating a method implemented in a

communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In step 1210 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE.

In step 1220 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1230 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0158] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0159] Figure 13 depicts a method in accordance with particular embodiments, the method begins at step 1302 with obtaining a configuration of at least one slot format combination, wherein a slot format combination comprises a value indicating a marker within a COT comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT. The method then comprises, at step 1304, receiving a control information identifying a slot format combination from within the obtained configuration. The method then comprises, at step 1306, determining a type of the marker in the identified slot format combination from the value indicating the marker. The method then comprises, at step 1308, performing at least one of uplink

transmission or downlink listening during the COT in accordance with the determined type of the marker and the time instance identified by the marker.

[0160] Figure 14 illustrates a schematic block diagram of an apparatus 1400 in a wireless network (for example, the wireless network shown in Figure 4). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 410 or network node 460 shown in Figure 4). Apparatus 1400 is operable to carry out the example method described with reference to Figure 13 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 13 is not necessarily carried out solely by apparatus 1400. At least some operations of the method can be performed by one or more other entities.

[0161] Virtual Apparatus 1400 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause obtaining unit 1402, receiving unit 1404, determining unit 1406, and performing unit 1408, and any other suitable units of apparatus 1400 to perform corresponding functions according one or more embodiments of the present disclosure.

[0162] As illustrated in Figure 14, apparatus 1400 includes obtaining unit 1402, receiving unit 1404, determining unit 1406, and performing unit 1408. Obtaining unit 1402 is configured to obtain a configuration of at least one slot format combination, wherein a slot format combination comprises a value indicating a marker within a COT comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT. Receiving unit 1404 is configured to receive control information identifying a slot format combination from within the obtained configuration.

Determining unit 1406 is configured to determine a type of the marker in the identified slot format combination from the value indicating the marker. Performing unit 1408 is configured to perform at least one of uplink transmission or downlink listening during the COT in accordance with the determined type of the marker and the time instance identified by the marker.

[0163] Figure 15 depicts a method in accordance with particular embodiments, the method begins at step 1502 with providing to a wireless device a configuration of at least one slot format combination, wherein a slot format combination comprises a value indicating a marker within a COT comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT. The method then comprises, at step 1504, sending to the wireless device a control information identifying a slot format combination from within the obtained configuration. The method then comprises, at step 1506, identifying a type of the marker in the identified slot format combination from the value indicating the marker. The method then comprises, at step 1508, performing at least one of downlink transmission or uplink listening during the COT in accordance with the identified type of the marker and the time instance identified by the marker.

[0164] Figure 16 illustrates a schematic block diagram of an apparatus 1600 in a wireless network (for example, the wireless network shown in Figure 4). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 410 or network node 460 shown in Figure 4). Apparatus 1600 is operable to carry out the example method described with reference to Figure 15 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 15 is not necessarily carried out solely by apparatus 1600. At least some operations of the method can be performed by one or more other entities.

[0165] Virtual apparatus 1600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause providing unit 1602, sending unit 1604, identifying unit 1606, and performing unit 1608, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure.

[0166] As illustrated in Figure 16, apparatus 1600 includes providing unit 1602, sending unit 1604, identifying unit 1606, and performing unit 1608. Providing unit 1602 is configured to provide to a wireless device a configuration of at least one slot format combination, wherein a slot format combination comprises a value indicating a marker within a COT comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT. Sending unit 1604 is configured to send to the wireless device control information identifying a slot format combination from within the obtained configuration. Identifying unit 1606 is configured to identify a type of the marker in the identified slot format combination from the value indicating the marker. Performing unit 1608 is configured to perform at least one of uplink transmission or downlink listening during the COT in accordance with the identified type of the marker and the time instance identified by the marker.

[0167] The term "unit" may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

EMBODIMENTS

Group A Embodiments

1. A method performed by a wireless device for operating in unlicensed spectrum, the method comprising:

- obtaining a configuration of at least one slot format combination, wherein a slot format combination comprises a value indicating a marker within a Channel Occupancy Time (COT) comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT;

- receiving a control information identifying a slot format combination from within the obtained configuration;

- determining a type of the marker in the identified slot format combination from the value indicating the marker; and

- performing at least one of uplink transmission or downlink listening during the COT in accordance with the determined type of the marker and the time instance identified by the marker.

2. The method of embodiment 1, wherein a marker type indicates information conveyed by the marker, the information relating to at least one of:

a . structu re of the COT ;

b. wireless device behavior before, during or after the time instance identified by the marker.

3. The method of embodiment 1 or 2, wherein the COT comprises at least one of: a. a COT with sharing of DL and UL transmission opportunities;

b. a COT without sharing of DL and UL transmission opportunities.

4. The method of any one of the preceding embodiments, wherein a slot format combination comprises at least one Slot Format Indicator. 5. The method of any one of the preceding embodiments, wherein obtaining a configuration of at least one slot format combination comprises at least one of receiving the configuration from a base station in RRC signaling, or retrieving the configuration from a memory.

6. The method of any one of the preceding embodiments, wherein the control information is a Downlink Control Information, DCI.

7. The method of any one of the preceding embodiments, wherein receiving a control information comprises receiving the control information from a base station on a PDCCH.

8. The method of embodiment 7, wherein the PDCCH is a group common PDCCH comprising DCI Format 2_0.

9. The method of any one of the preceding embodiments, wherein determining a type of the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated.

10. The method of embodiment 9, wherein the mapping comprises a table.

11. The method of any one of the preceding embodiments, wherein the value indicating a marker comprises a Slot Format Indicator value that is reserved for future use according to 3GPP TS 38.213.

12. The method of embodiment 11, wherein the value indicating a marker comprises a value in the range [56 .. 254].

13. The method of any one of the preceding embodiments, wherein the value indicating the marker is configured at a position within the slot format combination that corresponds to the specific time instance that is identified by the marker. 14. The method of any one of the preceding embodiments, wherein the specific time instance within the COT that is identified by the marker comprises a time slot.

15. The method of embodiment 13, wherein the value indicating the marker is configured at a position within the slot format combination that corresponds to the time slot.

16. The method of any one of embodiments 1 to 13, wherein the specific time instance within the COT that is identified by the marker comprises a symbol within a time slot.

17. The method of embodiment 16, wherein the value indicating the marker is configured at a position within the slot format combination that corresponds to the time slot within which the symbol occurs.

18. The method of embodiment 17, wherein determining a type of the marker in the identified slot format combination from the value indicating the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated and to the symbol within the time slot at which the marker is positioned.

19. The method of embodiment 18, wherein for a given marker type, a plurality of values correspond to the same marker type positioned at different symbols within a given time slot.

20. The method of any one of the preceding embodiments, wherein a slot format combination comprises a plurality of values, and wherein at least one of the values indicates a marker.

21. The method of embodiment 20 wherein at least two of the plurality of values in the slot format combination indicate a marker.

22. The method of embodiment 21, wherein each one of the values that indicate a marker indicates a marker at a different position in the COT. 23. The method of embodiment 21 or 22, wherein each one of the values that indicate a marker indicates a marker of a different type.

24. The method of any one of the preceding embodiments, wherein a slot format combination comprises a Slot Format Indicator specifying that the wireless device is to determine slot format.

25. The method of embodiment 24, wherein a slot format combination comprises a Slot Format Indicator of value 255.

26. The method of any one of the preceding embodiments, wherein in a slot format combination, the value indicating a marker and an additional Slot Format Indicator are configured at a position within the slot format combination that corresponds to the same time slot.

27. The method of embodiment 26, wherein the value indicating a marker comprises a Slot Format Indicator value that is reserved for future use according to 3GPP TS 38.213[2] and is in the range [56 .. 254], and wherein the additional Slot Format Indicator comprises a Slot Format Indicator that is specified in 3GPP TS 38.213[2] and is in the range [0 .. 55].

28. The method of any one of the preceding embodiments, wherein determining a type of the marker in the identified slot format combination from the value indicating the marker comprises determining that the marker is of at least one of:

a. an end-of-COT marker

b. an end-of-COT UL slot marker

c. a DL-to-UL marker

d. a UL-to-DL marker

e. an LBT-not-required marker

f. an LBT-required marker

g. a PDCCFI monitoring marker. 29. The method of embodiment 28, wherein an end-of-COT marker indicates that the COT ends in the time instance indicated by the marker.

30. The method of embodiment 28, wherein an end-of-COT UL slot marker indicates that the COT ends in the time instance indicated by the marker and that the slot of the time instance is a UL slot.

31. The method of embodiment 28, wherein a DL-to-UL marker indicates that a DL- to-UL switch occurs in the time instance indicated by the marker.

32. The method of embodiment 28, wherein a UL-to-DL marker indicates that a UL- to-DL switch occurs in the time instance indicated by the marker.

33. The method of embodiment 28, wherein an LBT-not-required marker indicates that the wireless device is not required to perform a listen-before-talk procedure prior to UL transmission.

34. The method of embodiment 28, wherein an LBT-required marker indicates that the wireless device is required to perform a listen-before-talk procedure for a predetermined time duration prior to UL transmission.

35. The method of embodiment 34, wherein the predetermined time duration comprises 25 microseconds.

36. The method of embodiment 28, wherein a PDCCH monitoring marker indicates that the wireless device may skip PDCCH monitoring in the time instance indicated by the marker unless it has received at least one of a dedicated DL or UL grant in a prior slot within the COT.

37. The method of any one of embodiments 1 to 12, wherein the value indicating the marker encodes the specific time instance identified by the marker.

38. The method of embodiment 37, wherein the specific time instance within the COT that is identified by the marker comprises at least one of a time slot or a symbol within a time slot.

39. The method of embodiment 37 or 38, wherein a slot format combination comprises configuration of only a single slot.

40. The method of embodiment 39 wherein the single slot configured is the current slot.

41. The method of any one of embodiments 37 to 40, wherein determining a type of the marker in the identified slot format combination from the value indicating the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker.

42. The method of any one of embodiments 37 to 41, wherein determining a type of the marker in the identified slot format combination from the value indicating the marker comprises determining that the marker is at least one of:

a. an end-of-COT marker

b. an end-of-COT UL slot marker

c. a DL-to-UL marker

d. a UL-to-DL marker

e. an LBT-not-required marker

f. an LBT required marker

g. a PDCCH monitoring marker.

43. The method of embodiment 42, wherein the marker types indicate information according to any one of embodiments 29 to 36.

44. The method of any one of embodiments 37 to 43, wherein using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker comprises using the mapping to translate the value to a number of slots, the number of slots, when counted from the present slot, indicating the slot identified by the marker. 45. The method of any one of embodiments 37 to 44 wherein using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker comprises using the mapping to translate the value to a number of symbols, the number of symbols, when counted from a reference point, indicating the symbol identified by the marker.

46. The method of embodiment 45, wherein the value indicating a marker comprises two sub values, and wherein using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker comprises using the mapping to translate a first of the sub values to a number of slots, the number of slots, when counted from the present slot, indicating a reference point, and to translate a second of the sub values to a number of symbols, the number of symbols, when counted from the reference point, indicating the symbol identified by the marker, wherein the reference point comprises a beginning of the first slot after the end of the slots indicated by the first sub value.

47. The method of any one of the preceding embodiments, wherein the marker identifies a plurality of time instances.

48. The method of embodiment 47, wherein the marker identifies a subset of slots within the COT and wherein the subset is identified via at least one of a start point and end point of the subset or a start point and a duration of the subset.

49. The method of embodiment 48 wherein the marker identifies the subset of slots via a mapping from the value indicating the marker to an indication of at least one of a start point and end point of the subset or a start point and duration of the subset.

50. The method of embodiment 48 or 49, wherein determining a type of the marker in the identified slot format combination from the value indicating the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated and to the time instances identified by the marker. 51. The method of any one of embodiments 47 to 50, wherein determining a type of the marker in the identified slot format combination from the value indicating the marker comprises determining that the marker is at least one of:

a. an end-of-COT marker

b. an end-of-COT UL slot marker

c. a DL-to-UL marker

d. a UL-to-DL marker

e. an LBT-not-required marker

f. an LBT required marker

g. a PDCCH monitoring marker.

52. The method of embodiment 51, wherein the marker types indicate information according to any one of embodiments 28 to 36.

53. The method of any of the previous embodiments, further comprising:

a. providing user data; and

b. forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

54. A method performed by a base station for operating in unlicensed spectrum, the method comprising:

- providing to a wireless device a configuration of at least one slot format

combination, wherein a slot format combination comprises a value indicating a marker within a Channel Occupancy Time (COT) comprising a plurality of slots, and wherein the marker identifies a specific time instance within the COT;

- sending to the wireless device a control information identifying a slot format combination from within the obtained configuration;

- identifying a type of the marker in the identified slot format combination from the value indicating the marker; and

- performing at least one of downlink transmission or uplink listening during the COT in accordance with the identified type of the marker and the time instance identified by the marker.

55. The method of embodiment 54, wherein a marker type indicates information conveyed by the marker, the information relating to at least one of:

- structure of the COT ;

- wireless device behavior before, during or after the time instance identified by the marker.

56. The method of embodiment 54 or 55, wherein the COT comprises at least one of:

- a COT with sharing of DL and UL transmission opportunities;

- a COT without sharing of DL and UL transmission opportunities.

57. The method of any one of the preceding embodiments, wherein a slot format combination comprises at least one Slot Format Indicator.

58. The method of any one of the preceding embodiments, wherein providing to a wireless device a configuration of at least one slot format combination comprises at sending the configuration to the wireless device in RRC signaling.

59. The method of any one of the preceding embodiments, wherein the control information is a Downlink Control Information, DCI.

60. The method of any one of the preceding embodiments, wherein sending a control information comprises sending the control information on a PDCCH.

61. The method of embodiment 60, wherein the PDCCH is a group common PDCCH comprising DCI Format 2_0.

62. The method of any one of the preceding embodiments, wherein identifying a type of the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated. 63. The method of embodiment 62, wherein the mapping comprises a table.

64. The method of any one of the preceding embodiments, wherein the value indicating a marker comprises a Slot Format Indicator value that is reserved for future use according to 3GPP TS 38.213.

65. The method of embodiment 64, wherein the value indicating a marker comprises a value in the range [56 .. 254].

66. The method of any one of the preceding embodiments, wherein the value indicating the marker is configured at a position within the slot format combination that corresponds to the specific time instance that is identified by the marker.

67. The method of any one of the preceding embodiments, wherein the specific time instance within the COT that is identified by the marker comprises a time slot.

68. The method of embodiment 67, wherein the value indicating the marker is configured at a position within the slot format combination that corresponds to the time slot.

69. The method of any one of embodiments 54 to 67, wherein the specific time instance within the COT that is identified by the marker comprises a symbol within a time slot.

70. The method of embodiment 69, wherein the value indicating the marker is configured at a position within the slot format combination that corresponds to the time slot within which the symbol occurs.

71. The method of embodiment 70, wherein identifying a type of the marker in the identified slot format combination from the value indicating the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated and to the symbol within the time slot at which the marker is positioned. 72. The method of embodiment 71, wherein for a given marker type, a plurality of values correspond to the same marker type positioned at different symbols within a given time slot.

73. The method of any one of the preceding embodiments, wherein a slot format combination comprises a plurality of values, and wherein at least one of the values indicates a marker.

74. The method of embodiment 73 wherein at least two of the plurality of values in the slot format combination indicate a marker.

75. The method of embodiment 74, wherein each one of the values that indicate a marker indicates a marker at a different position in the COT.

76. The method of embodiment 73 or 74, wherein each one of the values that indicate a marker indicates a marker of a different type.

77. The method of any one of the preceding embodiments, wherein a slot format combination comprises a Slot Format Indicator specifying that the wireless device is to determine slot format.

78. The method of embodiment 77, wherein a slot format combination comprises a Slot Format Indicator of value 255.

79. The method of any one of the preceding embodiments, wherein in a slot format combination, the value indicating a marker and an additional Slot Format Indicator are configured at a position within the slot format combination that corresponds to the same time slot.

80. The method of embodiment 79, wherein the value indicating a marker comprises a Slot Format Indicator value that is reserved for future use according to 3GPP TS 38.213[2] and is in the range [56 .. 254], and wherein the additional Slot Format Indicator comprises a Slot Format Indicator that is specified in 3GPP TS 38.213[2] and is in the range [0 .. 55].

81. The method of any one of the preceding embodiments, wherein identifying a type of the marker in the identified slot format combination from the value indicating the marker comprises identifying that the marker is of at least one of:

- an end-of-COT marker

- an end-of-COT UL slot marker

- a DL-to-UL marker

- a UL-to-DL marker

- an LBT-not-required marker

- an LBT-required marker

- a PDCCH monitoring marker.

82. The method of embodiment 81, wherein an end-of-COT marker indicates that the COT ends in the time instance indicated by the marker.

83. The method of embodiment 81, wherein an end-of-COT UL slot marker indicates that the COT ends in the time instance indicated by the marker and that the slot of the time instance is a UL slot.

84. The method of embodiment 81, wherein a DL-to-UL marker indicates that a DL- to-UL switch occurs in the time instance indicated by the marker.

85. The method of embodiment 81, wherein a UL-to-DL marker indicates that a UL- to-DL switch occurs in the time instance indicated by the marker.

86. The method of embodiment 81, wherein an LBT-not-required marker indicates that the wireless device is not required to perform a listen-before-talk procedure prior to UL transmission.

87. The method of embodiment 81, wherein an LBT-required marker indicates that the wireless device is required to perform a listen-before-talk procedure for a predetermined time duration prior to UL transmission.

88. The method of embodiment 87, wherein the predetermined time duration comprises 25 microseconds.

89. The method of embodiment 81, wherein a PDCCH monitoring marker indicates that the wireless device may skip PDCCH monitoring in the time instance indicated by the marker unless it has received at least one of a dedicated DL or UL grant in a prior slot within the COT.

90. The method of any one of embodiments 54 to 66, wherein the value indicating the marker encodes the specific time instance identified by the marker.

91. The method of embodiment 90, wherein the specific time instance within the COT that is identified by the marker comprises at least one of a time slot or a symbol within a time slot.

92. The method of embodiment 90 or 91, wherein a slot format combination comprises configuration of only a single slot.

93. The method of embodiment 92 wherein the single slot configured is the current slot.

94. The method of any one of embodiments 90 to 93, wherein identifying a type of the marker in the identified slot format combination from the value indicating the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker.

95. The method of any one of embodiments 90 to 94, wherein identifying a type of the marker in the identified slot format combination from the value indicating the marker comprises identifying that the marker is at least one of:

- an end-of-COT marker

- an end-of-COT UL slot marker - a DL-to-UL marker

- a UL-to-DL marker

- an LBT-not-required marker

- an LBT required marker

- a PDCCH monitoring marker.

96. The method of embodiment 95, wherein the marker types indicate information according to any one of embodiments 82 to 89.

97. The method of any one of embodiments 90 to 96, wherein using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker comprises using the mapping to translate the value to a number of slots, the number of slots, when counted from the present slot, indicating the slot identified by the marker.

98. The method of any one of embodiments 90 to 97 wherein using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker comprises using the mapping to translate the value to a number of symbols, the number of symbols, when counted from a reference point, indicating the symbol identified by the marker.

99. The method of embodiment 98, wherein the value indicating a marker comprises two sub values, and wherein using a mapping to translate the value indicating the marker to the type of marker indicated and to the specific time instance identified by the marker comprises using the mapping to translate a first of the sub values to a number of slots, the number of slots, when counted from the present slot, indicating a reference point, and to translate a second of the sub values to a number of symbols, the number of symbols, when counted from the reference point, indicating the symbol identified by the marker, wherein the reference point comprises a beginning of the first slot after the end of the slots indicated by the first sub value.

100. The method of any one of the preceding embodiments, wherein the marker identifies a plurality of time instances. 101. The method of embodiment 100, wherein the marker identifies a subset of slots within the COT and wherein the subset is identified via at least one of a start point and end point of the subset or a start point and a duration of the subset.

102. The method of embodiment 101 wherein the marker identifies the subset of slots via a mapping from the value indicating the marker to an indication of at least one of a start point and end point of the subset or a start point and duration of the subset.

103. The method of embodiment 101 or 102, wherein identifying a type of the marker in the identified slot format combination from the value indicating the marker comprises using a mapping to translate the value indicating the marker to the type of marker indicated and to the time instances identified by the marker.

104. The method of any one of embodiments 100 to 103, wherein identifying a type of the marker in the identified slot format combination from the value indicating the marker comprises identifying that the marker is at least one of:

- an end-of-COT marker

- an end-of-COT UL slot marker

- a DL-to-UL marker

- a UL-to-DL marker

- an LBT-not-required marker

- an LBT required marker

- a PDCCH monitoring marker.

105. The method of embodiment 104, wherein the marker types indicate information according to any one of embodiments 82 to 89.

106. The method of any of the previous embodiments, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer or a wireless device.

Group C Embodiments 107. A wireless device for operating in unlicensed spectrum, the wireless device comprising:

- processing circuitry configured to perform any of the steps of any of the

Group A embodiments; and

- power supply circuitry configured to supply power to the wireless device.

108. A base station for operating in unlicensed spectrum, the base station comprising:

- processing circuitry configured to perform any of the steps of any of the

Group B embodiments;

- power supply circuitry configured to supply power to the base station.

109. A user equipment (UE) for operating in unlicensed spectrum the UE comprising:

- an antenna configured to send and receive wireless signals;

- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

- a battery connected to the processing circuitry and configured to supply

power to the UE.

110. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

111. The communication system of the previous embodiment further including the base station.

112. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

113. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE comprises processing circuitry configured to execute a client

application associated with the host application.

114. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

115. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

116. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

117. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

118. A communication system including a host computer comprising: - processing circuitry configured to provide user data; and

- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

- wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.

119. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

120. The communication system of the previous 2 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE's processing circuitry is configured to execute a client application associated with the host application.

121. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

122. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

123. A communication system including a host computer comprising:

- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

- wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments. 124. The communication system of the previous embodiment, further including the UE.

125. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

126. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application; and

- the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

127. The communication system of the previous 4 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

- the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

128. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

129. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

130. The method of the previous 2 embodiments, further comprising:

- at the UE, executing a client application, thereby providing the user data to be transmitted; and - at the host computer, executing a host application associated with the client application.

131. The method of the previous 3 embodiments, further comprising:

- at the UE, executing a client application; and

- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,

- wherein the user data to be transmitted is provided by the client application in response to the input data.

132. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

133. The communication system of the previous embodiment further including the base station.

134. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

135. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application;

- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

136. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

137. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

138. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

[0168] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

ps Microsecond

2G Second Generation

3G Third Generation

3GPP Third Generation Partnership Project

4G Fourth Generation

5G Fifth Generation

AC Alternating Current

ACK Acknowledgement

AP Access Point

ASIC Application Specific Integrated Circuit

ATM Asynchronous Transfer Mode

BS Base Station

BSC Base Station Controller

BTS Base Transceiver Station

CCA Clear Channel Assessment

CD Compact Disk

CDMA Code Division Multiple Access

COT Channel Occupancy Time

COTS Commercial Off-the-Shelf

CPE Customer Premise Equipment • CPU Central Processing Unit

• CSI-RS Channel State Information Reference Signal

• D2D Device-to-Device

• DAS Distributed Antenna System

• DC Direct Current

• DCI Downlink Control Information

• DIMM Dual In-line Memory Module

• DL Downlink

• DSP Digital Signal Processor

• DVD Digital Video Disk

• EEPROM Electrically Erasable Programmable Read Only Memory

• eMTC Enhanced Machine Type Communication

• eNB Enhanced or Evolved Node B

• EPROM Erasable Programmable Read Only Memory

• E-SMLC Evolved Serving Mobile Location Center

• FPGA Field Programmable Gate Array

• GC-PDCCH Group Common Physical Downlink Control Channel

• GHz Gigahertz

• gNB New Radio Base Station

• GPS Global Positioning System

• GSM Global System for Mobile Communications

• HDDS Holographic Digital Data Storage

• HD-DVD High-Density Digital Versatile Disc

• ID Identifier

• IE Information Element

• I/O Input and Output

• IoT Internet of Things

• IP Internet Protocol

• kHz Kilohertz

• LAA License Assisted Access

• LAN Local Area Network

• LBT Listen-Before-Talk

• LEE Laptop Embedded Equipment • LME Laptop Mounted Equipment

• LTE Long Term Evolution

• M2M Machine-to-Machine

• MAC Medium Access Control

• MANO Management and Orchestration

• MCE Multi-Cell/Multicast Coordination Entity

• MCOT Maximum Channel Occupancy Time

• MDT Minimization of Drive Tests

• MHz Megahertz

• MIMO Multiple Input Multiple Output

• mm Millimeter

• MME Mobility Management Entity

• ms Millisecond

• MSC Mobile Switching Center

• MSR Multi-Standard Radio

• MTC Machine Type Communication

• NB-IoT Narrowband Internet of Things

• NFV Network Function Virtualization

• NIC Network Interface Controller

• NR New Radio

• NR-U New Radio in Unlicensed Spectrum

• O&M Operation and Maintenance

• OFDM Orthogonal Frequency Division Multiplexing

• OSS Operations Support System

• OTT Over-the-Top

• PBCH Physical Broadcast Channel

• PDA Personal Digital Assistant

• PDCCH Physical Downlink Control Channel

• PDSCH Physical Downlink Shared Channel

• PHY Physical

• PROM Programmable Read Only Memory

• PSTN Public Switched Telephone Network

• PUCCH Physical Uplink Control Channel • PUSCH Physical Uplink Shared Channel

• RAID Redundant Array of Independent Disks

• RAM Random Access Memory

• RAN Radio Access Network

• RAT Radio Access Technology

• RB Resource Block

• RE Resource Element

• Rel-15 Release 15

• RF Radio Frequency

• RNC Radio Network Controller

• ROM Read Only Memory

• RRC Radio Resource Control

• RRH Remote Radio Flead

• RRU Remote Radio Unit

• RUIM Removable User Identity Module

• SDRAM Synchronous Dynamic Random Access Memory

• SFI Slot Format Indicator

• SIB System Information Block

• SIFS Short Interface Space

• SIM Subscriber Identity Module

• SOC System on a Chip

• SON Self-Organizing Network

• SONET Synchronous Optical Networking

• SR Scheduling Request

• SRS Sounding Reference Signal

• SS Synchronization Signal

• STA Station

• TCP Transmission Control Protocol

• TDD Time Division Duplexing

• TS Technical Specification

• TXOP Transmission Opportunity

• UCI Uplink Control Information

• UE User Equipment • UL Uplink

• UMTS Universal Mobile Telecommunications System

• USB Universal Serial Bus

• UTRAN Universal Terrestrial Radio Access Network

• V2I Vehicle-to-Infrastructure

• V2V Vehicle-to-Vehicle

• V2X Vehicle-to-Everything

• VMM Virtual Machine Monitor

• VNE Virtual Network Element

• VNF Virtual Network Function

• VoIP Voice over Internet Protocol

• WAN Wide Area Network

• WCDMA Wideband Code Division Multiple Access

• WD Wireless Device

• WiMax Worldwide Interoperability for Microwave Access

• WLAN Wireless Local Area Network

[0169] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

REFERENCES

[1] 3GPP TS 38.331 "Radio Resource Control (RRC) Protocol Specification," V15.3.0, September 2018. [2] 3GPP TS 38.213, "Physical Layer Procedures for Control," V15.3.0, September

2018.

[3] Chairman's notes, 3GPP RAN WG1 Meeting #94b, Chengdu, China, October 2018.