Data communication in SBFD configured cell

Abstract

A method performed by a wireless device is disclosed. The method comprises the steps of: receiving one or more messages indicating different sets of parameters for a cell, wherein each of the different sets of parameters indicates: a starting physical resource block, PRB, index for a frequency hopping of an uplink transmission; and a number of PRBs available for the frequency hopping of the uplink transmission; and transmitting a preamble via a random access resource of the cell; receiving a downlink data comprising a UE contention resolution identity; based on the receiving, selecting, from among the different sets of parameters, a set of parameters to use for a first uplink transmission and / or a first downlink data reception, based on: whether the random access resource is from a first set of random access resources of the cell or a second set of random access resources of the cell, wherein: each, of the first set of random access resources, overlaps with uplink and / or flexible symbols; and each, of the second set of random access resources, overlaps with subband full duplex, SBFD, symbols; whether resources of the first uplink transmission and / or resources of the first downlink data reception overlap, in time, with one or more SBFD symbols of the cell; and transmitting the first uplink transmission, comprising a feedback for the downlink data, using the selected set of parameters; and / or receiving the first downlink data reception.

Description

Data Communication in SBFD Configured CellFIELD OF THE INVENTIONThis invention relates to wireless communication, and in particular to data communication techniques in mobile communication networks that support subband full duplex (SBFD) operation in a wireless system such as a cellular system, a Wi-Fi network or the like.BACKGROUND OF THE INVENTIONIn conventional cellular networks, a primary station serves a plurality of secondary stations located within a cell served by this primary station. Wireless communication from the primary station towards each secondary station is done on downlink channels. Conversely, wireless communication from each secondary towards the primary station is done on uplink channels. The wireless communication can include data traffic (sometimes referred to User Data), and control information (also referred sometimes as signalling). This control information typically comprises information to assist the primary station and / or the secondary station to exchange data traffic (e.g. resource allocation / requests, physical transmission parameters, information on the state of the respective stations).In the context of cellular networks as standardized by 3GPP, the primary station is referred to a base station, or a gNodeB (or gNB) in 5G (NR) or an eNodeB (or eNB) in 4G (LTE). The eNB / gNB is part of the Radio Access Network RAN, which interfaces to functions in the Core Network (CN). In the same context, the secondary station corresponds to a mobile station, or a User Equipment (or a UE) in 4G / 5G, which is a wireless client device or a specific role played by such device. The term "node" is also used to denote either a UE or a gNB / eNB.Additionally, for example, in the case of PC5 interface or Sidelink communication, it is possible to have Direct communication between secondary stations, here UEs. It is then also possible for UEs to operate as Relays to allow for example out of coverage UEs to get an inter-mediate (or indirect) connection to the eNB or gNB. To be able to work as a relay, a UE may use discovery messages to establish new connections with other UEs.In the domain of wireless communication, the advent of full-duplex (FD) technology has introduced the potential for simultaneous transmission and reception of signals on the same frequency channel, effectively doubling spectral efficiency and reducing latency.Despite extensive configuration options in current standards, existing approaches fall short when applied to SBFD-configured cells and / or SBFD-capable UEs. For instance, traditional random access schemes assume distinct uplink and downlink symbol sets, obscuring opportunities for concurrent transmission and reception on shared resources. Likewise, uplink scheduling grants and downlink control information formats are designed for either TDD or FDD operation, lacking mechanisms to select and / or agree on different parameter sets when SBFD symbols are active.SUMMARY OF THE INVENTIONEmbodiments of the present disclosure are related to an approach for solving the problems described above.A first aspect of the present disclosure provides a method performed by a wireless device, the method comprises the steps of:receiving one or more messages indicating different sets of parameters for a cell, wherein each of the different sets of parameters indicates:a starting physical resource block, PRB, index for a frequency hopping of an uplink transmission; anda number of PRBs available for the frequency hopping of the uplink transmission; and transmitting a preamble via a random access resource of the cell;receiving a downlink data comprising a UE contention resolution identity; based on the receiving, selecting, from among the different sets of parameters, a set of parameters to use for a first uplink transmission and / or a first downlink data reception, based on:whether the random access resource is from a first set of random access resources of the cell or a second set of random access resources of the cell, wherein:each, of the first set of random access resources, overlaps with uplink and / or flexible symbols; andeach, of the second set of random access resources, overlaps with subband full duplex, SBFD, symbols;whether resources of the first uplink transmission and / or resources of the first downlink data reception overlap, in time, with one or more SBFD symbols of the cell; andtransmitting the first uplink transmission, comprising a feedback for the downlink data, using the selected set of parameters; and / or receiving the first downlink data reception.In an example of the present disclosure, the different sets of parameters comprise a first set of parameters and a second set of parameters.In an example of the present disclosure, the one or more messages indicates an uplink bandwidth part, BWP, wherein the starting PRB index, of the first set of parameters, is determined based on the uplink BWP.In an example of the present disclosure, the one or more messages indicates an uplink subband, wherein the starting PRB index, of the second set of parameters, is determined based on the uplink BWP and the uplink subband.In an example of the present disclosure, the first uplink transmission is a physical uplink control channel, PUCCH, comprising a feedback corresponding to the downlink data.In an example of the present disclosure, the method further comprises determining a first hop of the first uplink transmission based on the starting PRB index.In an example of the present disclosure, the method further comprises determining a second hop of the first uplink transmission based on the starting PRB index and the number of PRBs.In an example of the present disclosure, the set of parameters is:the second set of parameters in response to the random access resource being from the second set of random access resources and the resources of the first uplink transmission overlapping with the one or more SBFD symbols; andthe first set of parameters in response to the random access resource being from the first set of random access resources or the resources of the first uplink transmission not overlapping with the one or more SBFD symbols.In an example of the present disclosure, the first set of random access resources and the second set of random access resources are associated with a same set of features.In an example of the present disclosure, the same set of features comprises one or more of reduced capability, small data transmission, msg3 repetition, and msgl repetition.In an example of the present disclosure, the one or more messages indicates a feature combination preambles (e.g., FeatureCombinationPreambles IE) comprising a feature combination (e.g., Featurecombination) indicating the set of features, a start preamble for this partition (e.g., startPreambleForThisPartition), and optionally one or more msgl repetition numbers.In an example of the present disclosure, the method further comprises determining the first set of random access resources and the second set of random access resources based on the feature combination preambles, wherein the feature combination, the start preamble for this partition and optionally the one or more msgl repetition numbers are commonly applied for the first set of random access resources and the second set of random access resources.In an example of the present disclosure, the one or more messages comprise one or more system information blocks, SIBs.In an example of the present disclosure, the one or more messages indicate an initial uplink BWP, wherein the initial uplink BWP is the uplink BWP.In an example of the present disclosure, the method further comprises the following steps prior to receiving the downlink data comprising a UE contention resolution identity:receiving, by the wireless device, a random access response, RAR, message comprising an uplink, UL, grant for a third uplink transmission,in response to the receiving, selecting, from among the different sets of parameters, a set of parameters to use for the third uplink transmission, based on:whether the random access resource is from the first set of random access resources of the cell or the second set of random access resources of the cell,whether resources of the UL grant for the third uplink transmission overlap, in time, with one or more SBFD symbols of the cell; andtransmitting the third uplink transmission comprising UE contention resolution identity using the selected set of parameters.In an example of the present disclosure, the method further comprises performing, by the wireless device, the first downlink data reception using the selected set of parameters.In an example of the present disclosure, the first uplink transmission is performed by means of a first uplink frequency hopping pattern, and the first downlink data reception is performed using a first downlink frequency hopping pattern; and wherein:the one or more messages indicate a first uplink set of parameters determining the first uplink frequency hopping pattern and a first downlink set of parameters determining a first downlink frequency hopping pattern; and / orthe selected set of parameters comprise the first uplink set of parameters and / or the first downlink set of parameters; and / orthe first downlink set of parameters comprise a downlink bandwidth part, and a downlink subband, and / orthe first uplink set of parameters comprise an uplink bandwidth part, and an uplink subband; and / orthe wireless device obtains or derives the first downlink set of parameters from the first uplink set of parameters; or the first uplink set of parameters is derived from the first downlink set of parameters; and / orthe first uplink frequency hopping pattern and the first downlink frequency hopping pattern are complementary.A second aspect of the present disclosure provides a method performed by a base station in a wireless communication system, the method comprising:transmitting, to a wireless device, one or more messages indicating different sets of parameters, wherein each of the different sets of parameters indicates:a starting physical resource block (PRB) index for frequency hopping of an uplink transmission by the wireless device; anda number of PRBs available for the frequency hopping of the uplink transmission; configuring, for a cell, a first set of random access resources (ROs) and a second set of random access resources, wherein:each of the first set of ROs overlaps with uplink and / or flexible symbols; and each of the second set of ROs overlaps with subband full duplex (SBFD) symbols; receiving, from the wireless device, a preamble via a random access resource of the cell; transmitting, to the wireless device, downlink data comprising a UE contention resolution identity;transmitting, to the wireless device, an uplink grant for a first uplink transmission, the uplink grant indicating a set of parameters selected from among the different sets of parameters, based on:whether the random access resource is from the first set of random access resources or the second set of random access resources;whether resources of the first uplink transmission overlap, in time, with one or more SBFD symbols of the cell;receiving, from the wireless device, the first uplink transmission comprising feedback for the downlink data, wherein the first uplink transmission uses the selected set of parameters.A third aspect of the present disclosure provides a wireless device comprising a processor configured for performing the method according to the first aspect of the present disclosure.A fourth aspect of the present disclosure provides a base station comprising a processor configured for performing the method of the second aspect of the present disclosure.A fifth aspect of the present disclosure provides a computer-readable medium storing computer program instructions that, when executed by a processor of a wireless device, cause the wireless device to execute the steps of the methods of the first aspect of the present disclosure.A sixth aspect of the present disclosure provides a computer-readable medium storing computer program instructions that, when executed by a processor of a base station, cause the base station to execute the steps of the methods of the second aspect of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGSExamples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.FIG. 6 is an example diagram showing RRC state transitions of a UE.FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.FIG. 10A illustrates three carrier aggregation configurations with two component carriers. FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.FIG. 11A illustrates an example of an SS / PBCH block structure and location.FIG. 11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.FIG. 15 illustrates an example of a wireless device in communication with a base station. FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.FIG. 17 illustrates an aspect of an example embodiment according to the present disclosure.FIG. 18A illustrates an aspect of an example embodiment according to the present disclosure.FIG. 18B illustrates an aspect of an example embodiment according to the present disclosure.FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure.FIG. 20 illustrates an aspect of an example embodiment according to the present disclosure.FIG. 21 illustrates an aspect of an example embodiment according to the present disclosure.FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.FIG. 23 illustrates an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTIONIn the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exampleembodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.In this disclosure, "a" and "an" and similar phrases are to be interpreted as "at least one" and "one or more." Similarly, any term that ends with the suffix "(s)" is to be interpreted as "at least one" and "one or more." In this disclosure, the term "may" is to be interpreted as "may, for example." In other words, the term "may" is indicative that the phrase following the term "may" is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms "comprises" and "consists of", as used herein, enumerate one or more components of the element being described. The term "comprises" is interchangeable with "includes" and does not exclude unenumerated components from being included in the element being described. By contrast, "consists of" provides a complete enumeration of the one or more components of the element being described. The term "based on", as used herein, should be interpreted as "based at least in part on" rather than, for example, "based solely on". The term "and / or" as used herein represents any possible combination of enumerated elements. For example, " A, B, and / or C" may represent A; B; C; A and B; A and C; B and C; or A, B, and C.If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B ={cell 1, cell2} are: {celll}, {cell2}, and {cell 1, cell2}. The phrase "based on" (or equally "based at least on") is indicative that the phrase following the term "based on" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase "in response to" (or equally "in response at least to") is indicative that the phrase following the phrase "in response to" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase "depending on" (or equally "depending at least to") is indicative that the phrase following the phrase "depending on" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase "employing / using" (or equally "employing / using at least") is indicative that the phrase following the phrase "employing / using" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be "configured" within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as "a control message to cause in a device" may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.Many features presented are described as being optional through the use of "may" or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implementedas a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and / or some combination of the two duplexing techniques.The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radiohead (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called "hotspots") or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 1042024P00718WQ11in FIG. 1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.FIG. IB illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. IB, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A.The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).As illustrated in FIG. IB, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158Aand a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. IB for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.The AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and / or session management function (SMF) selection.NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. IB for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.As shown in FIG. IB, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. IB, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. IB to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.The gNBs 160 and / or the ng-eNBs 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP2024P00718WQ134G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as "non-standalone operation." In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. IB, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. IB may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. IB.FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise medium access control (MAC) layers (MACs) 212 and 222 (also referred to as media access control layers), radio link control (RLC) layers (RLCs) 213 and 223, packet data convergence protocol (PDCP) layers (PDCPs) 214 and 224, and service data application protocol (SDAP) layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator2024P00718WQ14(Q. FI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map / de-map the split radio bearer between RLC channels belonging to cell groups.The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air2024P00718WQ15interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an " H" in FIG. 4A) is added to an IP packet. The data unit from / to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to / from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timingadvance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:-- a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;-- a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;-- a common control channel (CCCH) for carrying control messages together with random access;-- a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and-- a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE. Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:-- a paging channel (PCH) for carrying paging messages that originated from the PCCH; -- a broadcast channel (BCH) for carrying the MIB from the BCCH;-- a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;-- an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and -- a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support thelow-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:-- a physical broadcast channel (PBCH) for carrying the MIB from the BCH;-- a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;-- a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;-- a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;-- a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ. acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and-- a physical random access channel (PRACH) for random access.Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as2024P00718WQ18RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and / or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRCJDLE), and RRC inactive 606 (e.g., RRCJNACTIVE).In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. IB, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new the UE registration area.RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE's RAN notification area.A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 606.A gNB, such as gNBs 160 in FIG. IB, may be split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an Fl interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ps; 30 kHz / 2.3 ps; 60 kHz / 1.2 ps; 120 kHz / 0.59 ps; and 240 kHz / 0.29 ps.A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbolsas needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275x12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing andcyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.A base station may semi-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and / or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or an initiation of random access.FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response toreceiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same / similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values for a primary cell.To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCellis stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as selfscheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and / or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same / similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment / grant per servingcell. A transport block and potential HARQ. retransmissions of the transport block may be mapped to a serving cell.In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG.5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. 5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS / PBCH blocks.FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a halfframe (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection / search and / or reselection may be based on the CD-SSB.The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cellbased on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS / PBCH block in the transmission pattern is a known distance from the frame boundary.The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.The UE may assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions having different SS / PBCH block indices.SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the plurality of SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations may be different or the same.The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same / similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and / or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and / or deactivate a CSI-RS resource. The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and / or deactivated.1The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and / or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence for the DMRS may be the same or different.A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a numberof DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and / or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same / similar time domain behavior, periodic, aperiodic, and / or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and / or subframe level periodicity; offset for a periodic and / or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and / or an SRS sequence ID.An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with oneor more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.The three beams illustrated in FIG. 11B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11B (beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have thecapability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (Rl).FIG. 12A illustrates examples of three downlink beam management procedures: Pl, P2, and P3. Procedure Pl may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of Pl). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of Pl and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of Pl and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure Pl, or using narrower beams than the beams used in procedure Pl. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.FIG. 12B illustrates examples of three uplink beam management procedures: Ul, U2, and U3. Procedure Ul may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of Ul). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of Ul and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of Ul and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure Pl, or using narrower beams than the beams used in procedure Pl. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and / or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a2024P00718WQ32determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRCJDLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 21312 may include and / or be referred to as a random access response (RAR).The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRCJNACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission ofthe Msg 1 1311 and / or the Msg 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 41314.The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-Configlndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and / or a size of the Msg 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and / or a size of the Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 basedon the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMsklndex and / or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:RA-RNTI= 1 + sjd + 14 x t Jd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier Jd, where sjd may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequencydomain (e.g., 0 < fjd < 8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 21312 (e.g., using resources identified in the Msg 2 1312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 3 1313 and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 21312, and / or any other suitable identifier).The Msg 41314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 3 1313 (e.g., if the UE is in an RRCJDLE state or not otherwise connected to the base station), Msg 41314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 11311 and / or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 11311 and / or the Msg 3 1313 based on a channel clear assessment (e.g., a listen-before-talk).FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 11321 and a Msg 2 1322. The Msg 11321 and the Msg 21322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS.13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 41314.The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and / or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 11321. The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e.g., ra-Preamblelndex).After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow] to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceld). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 11321 and reception of a corresponding Msg 21322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 21312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 41314 illustrated in FIG. 13A.The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and / or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and / or the like); whether the UE has valid TA or not; a cell size; the UE's RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and / or an uplink transmit power for the preamble 1341 and / or the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A timefrequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and / or CDM. TheRACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).A UE and a base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a power control command; and / or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as " FFFE" in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as " FFFF" in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI ), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_l may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format l_0 may be used for scheduling of PDSCH in a cell. DCI format l_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format l_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and / or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and / or configured for a PDCCH. Based on a payload size of the DCI and / or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate anassociation between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).The UE may transmit uplink control signaling (e.g., uplink control information (UCI )) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCHformat 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to "0". If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format l_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and / or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. IB, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and thecommunication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG.2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG.2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.As shown in FIG. 15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and / or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.A wireless device may receive from a base station one or more messages (e.g., RRC messages) comprising configuration parameters of a plurality of cells (e.g., primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g., as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.In an example, a base station and a wireless device may use a plurality of downlink control information (DCI) formats to schedule downlink data and / or uplink data or to deliver control information. For example, a DCI format 0_0 may be used to schedule an uplink resource for a PUSCH over a cell. A DCI format 0_l may be used to schedule one or more PUSCHs in one cell or may be used to indicate downlink feedback information for configured grant PUSCH (CG-DFI). A DCI format 0_2 may be used to schedule a resource for a PUSCH in one cell. Similarly, for downlink scheduling, a DCI format l_0 may schedule a resource for a PDSCH in one cell. A DCI format 1_1 may be used to schedule a PDSCH in one cell or trigger one shot HARQ-ACK feedback. A DCI format 1_2 may beused to schedule a resource for a PDSCH in one cell. There are one or more DCI formats carrying non-scheduling information. For example, a DCI format 2_0 may be used to indicate a slot formation information for one or more slots of one or more cells. A DCI format 2_2 may be used to indicate one or more transmit power control commands for PUCCH and PUSCH. A DCI format 2_3 may be used to indicate one or more transmit power control for SRS. A DCI format 2_4 may be used to indicate an uplink cancellation information. A DCI format 2_5 may be used to indicate a preemption information. A DCI format 2_6 may be used to indicate a power saving state outside of DRX active time. A DCI format 3_0 or 3_1 may be used to schedule NR sidelink resource or LTE sidelink resource in one cell.A DCI format may comprise one or more DCI fields, wherein a DCI field may have a DCI size. A wireless device may determine each DCI size of each DCI field of the DCI format based on one or more radio resource control (RRC) configuration parameters by a base station. For example, the one or more RRC configuration parameters may be transmitted via master information block (MIB). For example, the one or more RRC configuration parameters may be transmitted via system information blocks (SIBs). For example, the one or more RRC configuration parameters may be transmitted via one or more a wireless device specific (RRC) messages. For example, the wireless device may determine one or more DCI sizes of one or more DCI fields of a DCI format 0_0 based on the one or more RRC configuration parameters transmitted via the MIB and / or the SIBs. The wireless device may be able to determine the one or more DCI sizes of the DCI format 0_0 without receiving any the wireless device specific message. Similarly, the wireless device may determine one or more DCI sizes of one or more second DCI fields of a DCI format l_0 based on the one or more RRC configuration parameters transmitted via the MIB and / or the SIBs. For example, the DCI format 0_0 and the DCI format l_0 may be called as fallback DCI for scheduling uplink data and downlink data respectively. The wireless device may determine one or more DCI fields of the fallback DCI based on configuration parameters transmitted via MIB and / or SIBs.For example, the wireless device may determine one or more first DCI sizes of one or more first DCI fields of a DCI format 0_l based on one or more RRC configuration parameters transmitted via the MIB and / or the SIBs and / or the wireless device specific RRC message(s). The wireless device may determine each DCI size of the one or more first DCI fields based on the one or more RRC configuration parameters. For example, FIG. 17 may illustrate the one or more first DCI fields of the DCI format 0_l. In FIG. 17, there are one or more second DCI fields that may present in the DCI format 0_l regardless of the wireless device specific RRC message(s). For example, the DCI format 0_l may comprise a 1-bit DL / UL indicator where the bit is configured with zero ('0') to indicate an uplink grant for the DCI format 0_l. DCI field(s) shown in dotted boxes may not be present or a size of the DCI field(s) may be configured as zero. For example, a carrier indicator may be present when the DCI format 0_l is used to schedule a cell based on cross-carrier scheduling. The carrier indicator may indicate a cell index of a scheduled cell by the cross-carrier scheduling. For example, UL / SUL indicator (shown UL / SUL in FIG. 17) may indicate whether a DCI based the DCI format 0_l schedules a resource for an uplink carrier or a supplemental uplink. The UL / SUL indicator field may be present when the wireless device is configured with a supplemental uplink for a scheduled cell of the DCI. Otherwise, the UL / SUL indicator field is not present.A field of BWP index may indicate a bandwidth part indicator. The base station may configure one or more uplink BWPs for the scheduled cell. The wireless device may determine a bit size of the field of BWP index based on a number of the one or more uplink BWPs. For example, 1 bit may be used wherein the number of the one or more uplink BWPs (excluding an initial UL BWP) is two. The field of BWP index may be used to indicate an uplinkBWP switching. The wireless device may switch to a first BWP in response to receiving the DCI indicating an index of the first BWP, wherein the first BWP is different from an active uplink BWP (active before receiving the DCI).A DCI field of frequency domain resource allocation (frequency domain RA in FIG. 17) may indicate uplink resource(s) of the scheduled cell. For example, the base station may configure a resource allocation type 0, wherein a bitmap over one or more resource block groups (RBGs) may schedule the uplink resource(s), or a resource allocation type 1, wherein a starting PRB index and a length of the scheduled uplink resource(s) may be indicated, or a dynamic change between the resource allocation type 0 and the resource allocation type 1. The wireless device may determine a field size of the frequency domain RA field based on the configured resource allocation type and a bandwidth of an active UL BWP of the scheduled cell. For example, when the resource allocation type 0 is configured, the bitmap may indicate each of the one or more RBGs covering the bandwidth of the active UL BWP. A size of the bitmap may be determined based on a number of the one or more RBGs of the active UL BWP. For example, the wireless device may determine the size of the frequency domain RA field based on the resource allocation type 1 based on the bandwidth of the active uplink BWP (e.g., ceil (log2(BW(BW+l) / 2), wherein BW is the bandwidth of the active uplink BWP).The wireless device may determine a resource allocation indicator value (RIV) table, where an entry of the table may comprise a starting PRB index and a length value. For example, when the dynamic change between the resource allocation type 0 and the resource allocation type 1 is used, a larger size between a first size based on the resource allocation type 0 (e.g., the bitmap size) and a second size based on the resource allocation type 1 (e.g., the RIV table size) with additional 1 bit indication to indicate either the resource allocation type 0 or the resource allocation type 1. For example, the frequency domain RA field may indicate a frequency hopping offset. The base station may use K (e.g., 1 bit for two offset values, 2 bits for up to four offset values) bit(s) to indicate the frequency hopping offset from one or more configured offset values, based on the resource allocation type 1. The base station may use ceil(log2(BW(BW+l) / 2) - K bits to indicate the uplink resource(s) based on the resource allocation type 1, when frequency hopping is enabled.A DCI field of time domain resource allocation (time domain RA shown in FIG. 17) may indicate time domain resource of one or more slots of the scheduled cell. The base station may configure one or more time domain resource allocation lists of a time domain resource allocation table for an uplink BWP of the scheduled cell. The wireless device may determine a bit size of the time domain RA field based on a number of the one or more time domain resource allocation lists of the time domain resource allocation table. The base station may indicate a frequency hopping flag by a FH flag (shown as FH in FIG. 17), wherein the FH flag may present when the base station may enable a frequency hopping of the scheduled cell or the active UL BWP of the scheduled cell. A DCI field of modulation and coding scheme (MCS) (shown as MCS in FIG. 17) may indicate a coding rate and a modulation scheme for the scheduled uplink data. A new data indicator (NDI) field may indicate whether the DCI schedules the uplink resource(s) for a new / initial transmission or a retransmission. A redundancy version (RV) field may indicate one or more RV values (e.g., a RV value may be 0, 2, 3, or 1) for one or more PUSCHs scheduled over the one or more slots of the scheduled cells. For example, the DCI may schedule a single PUSCH via one slot, a RV value is indicated. For example, the DCI may schedule two PUSCHs via two slots, two RV values may be indicated. A number of PUSCHs scheduled by a DCI may be indicated in a time domain resource allocation list of the one or more time domain resource allocation lists.A DCI field of hybrid automatic repeat request (HARQ) process number (HARQ process # in FIG. 17) may indicate an index of a HARQ process used for the one or more PUSCHs. The wireless device may determine one or more HARQ processes for the one or more PUSCHs based on the index of the HARQ process, wherein the wireless device may determine the index for a first HARQ process of a first PUSCH of the one or more PUSCHs and select a next index as a second HARQ process of a second PUSCH of the one or more PUSCHs and so on. The DCI format 0_l may have a first downlink assignment index (1stDAI) and / or a second DAI (2ndDAI). The first DAI may be used to indicate a first size of bits of first HARQ-ACK codebook group. The second DAI may be present when the base station may configure a plurality of HARQ-ACK codebook groups. When there is no HARQ-ACK codebook group configured, the wireless device may assume the first HARQ-ACK codebook group only. The second DAI may indicate a second size of bits of second HARQ-ACK codebook group. The first DAI may be 1 bit when a semi-static HARQ-ACK codebook generation mechanism is used. The first DAI may be 2 bits or 4 bits when a dynamic HARQ-ACK codebook generation mechanism is used.A field of transmission power control (TPC shown in FIG. 17) may indicate a power offset value to adjust transmission power of the one or more scheduled PUSCHs. A field of sounding reference signal (SRS) resource indicator (SRI) may indicate an index of one or more configured SRS resources of an SRS resource set. A field of precoding information and number of layers (shown as PMI in FIG. 17) may indicate a precoding and a MIMO layer information for the one or more scheduled PUSCHs. A field of antenna ports may indicate DMRS pattern(s) for the one or more scheduled PUSCHs. A field of SRS request may indicate to trigger a SRS transmission of a SRS resource or skip SRS transmission. A field of CSI request may indicate to trigger a CSI feedback based on a CSI-RS configuration or skip CSI feedback. A field of code block group (CBG) transmission information (CBGTI) may indicate HARQ-ACK feedback(s) for one or more CBGs. A field of phase tracking reference signal (PTRS)-demodulation reference signal (DMRS) association (shown as PTRS in FIG. 17) may indicate an association between one or more ports of PTRS and one or more ports of DM-RS, wherein the one or more ports may be indicated in the field of antenna ports. A field of beta_offset indicator (beta offset in FIG. 17) may indicate a code rate for transmission of uplink control information (UCI) via a PUSCH of the one or more scheduled PUSCHs. A field of DMRS sequence initialization (shown as DMRS in FIG. 17) may present based on a configuration of transform precoding. A field of UL-SCH indicator (UL-SCH) may indicate whether a UCI may be transmitted via a PUSCH of the one or more scheduled PUSCHs or not. A field of open loop power control parameter set indication (open loop power in FIG. 17) may indicate a set of power control configuration parameters, wherein the wireless device is configured with one or more sets of power control configuration parameters. A field of priority indicator (priority) may indicate a priority value of the one or more scheduled PUSCHs. A field of invalid symbol pattern indicator (invalid OS) may indicate one or more unava il able / not-ava il able OFDM symbols to be used for the one or more scheduled PUSCHs. A field of SCell dormancy indication (Scell dormancy) may indicate transitioning between a dormant state and a normal state of one or more secondary cells.Note that additional DCI field(s), though not shown in FIG. 17, may present for the DCI format 0_l. For example, a downlink feedback information (DFI) field indicating for one or more configured grant resources may present for an unlicensed / shared spectrum cell, wherein the unlicensed / shared spectrum cell is a scheduled cell. When the DCI format 0_l is used for indicating downlink feedback information for the one or more configured grantresources, other DCI fields may be used to indicate a HARQ-ACK bitmap for the one or more configured grant resources and TPC commands for a scheduled PUSCH. Remaining bits may be reserved and filled with zeros ('0's).A similar DCI format may be present for scheduling uplink grant and / or downlink scheduling (e.g., DCI format 0_0, 0_2, 0_3, or DCI format l_0, 1_1, 1_2, 1_3). For example, the DCI format 1_1 may schedule a downlink resource for a scheduled downlink cell. The DCI format 1_1 may comprise one or more DCI fields such as an identifier for DCI formats (DL / UL), a carrier indicator, bandwidth part indicator (BWP index), a frequency domain resource assignment (frequency domain RA), a time domain resource assignment (time domain RA), a virtual resource block to physical resource block mapping (VRB-PRB), Physical resource block (PRB) bundling size indicator (PRB bundle), rate matching indicator (rate matching), zero power CSI-RS (ZP-CSI), a MCS, a NDI, a RV, a HARQ process number, a downlink assignment index (DAI), a TPC command for a PUCCH, a PUCCH resource indicator (PUCCH-RI), a PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ in FIG. 17), an antenna ports, a transmission configuration indication (TCI), a SRS request, a CBG transmission information (CBGTI), a CBG flushing out information (CBGFI), DMRS sequence initialization (DMRS), a priority indicator (priority), and a minimum applicable scheduling offset indicator.For an uplink transmission, a few resource allocation types are supported. For the uplink transmission, a resource allocation type 0, resource allocation type 1 or resource allocation type 2 may be supported. The resource allocation type 0 may be used wherein a transform precoding is disabled. The resource allocation type 1 or the resource allocation type 2 may be used wherein the transform precoding is enabled or disabled. For the uplink transmission, a 'dynamicswitch' may be configured, wherein the wireless device may switch between the resource allocation type 0 and the resource allocation type 1 based on a DCI. The base station may configure a resource allocation type via an RRC signaling wherein the 'dynamicswitch' has not been enabled. The resource allocation type 2 may be used wherein an interlaced PUSCH is enabled. The wireless device may apply the resource allocation type 1 for a DCI based on a fallback DCI format such as a DCI format 0_0, wherein the interlaced PUSCH is disabled. When the interlaced PUSCH is enabled, the wireless device may apply the resource allocation type 2 for the DCI. The wireless device may determine a frequency domain resource based on a frequency domain resource allocation field of a DCI based on an active uplink BWP of a scheduled cell, wherein the DCI may not comprise a BWP index. The wireless device may determine the frequency domain resource based on an indicated BWP wherein the DCI may comprise the BWP index.In an example, a resource allocation type 0 for an uplink transmission may use a bitmap indicating one or more RBGs within an active UL BWP of a scheduled cell. One RBG may represent a set of consecutive virtual resource blocks defined by a rgb-Size, wherein the rbg-Size may be indicated as a parameter of a PUSCH-Config under a servingCellConfig. For example, the rbg-Size may be determined based on a parameter of 'Configuration 1' or 'Configuration 2' and a bandwidth of an active UL BWP of a scheduled cell. For example, when the bandwidth of the active UL BWP is between 1 to 36 RBs, 'Configuration 1' indicates the rbg-Size of 2 and 'Configuration 2' indicates the rbg-Size of 4. For example, when the bandwidth of the active UL BWP is between 37 to 72 RBs, 'Configuration 1' indicates the rbg-Size of 4 and 'Configuration 2' indicates the rbg-Size of 8. For example, when the bandwidth of the active UL BWP is between 73 to 144 RBs, 'Configuration 1' indicates the rbg-Size of 8 and 'Configuration 2' indicates the rbg-Size of 16. For example, when the bandwidth of the active UL BWP is between 145 to 275 (or 550) RBs, 'Configuration 1' indicates the rbg-Size of 16 and 'Configuration 2' indicates the rbg-Size of16. A number of RBGs (N_RBG) for a uplink BWP may present. Determination of a bit of the bitmap of the uplink resource allocation type 1 is same as that of the downlink resource allocation type 1. In frequency range 1 (e.g., below 7GHz), almost contiguous allocation may be supported. In frequency range 2 (e.g., above 7GHz and below 52.6 GHz), contiguous resource allocation may be supported.The resource allocation type 0 for an uplink transmission may follow similar procedure to the resource allocation type 0 for an downlink transmission.The resource allocation type 2 may be used to indicate an interlaced resource allocation, wherein M is a number of interlaces. For example, a frequency domain resource allocation field may comprise a RIV. For the RIV between 0 and M (M+l) / 2 (e.g., 0<=RIV< M(M+l) / 2), the RIV may indicate a starting interlace index m_0 and a number of contiguous interlace indices L (L >=1). For example, when (L-l) <= floor (M / 2), the RIV may define M (L -1) + m_0. Otherwise, the RIV may define M (M-L+l) + (M-l-m_0). For the RIV larger than or equal to M(M+l) / 2 (e.g., RIV >= M(M+l) / 2), the RIV may indicate a starting interlace index m_0 and a set of values I based on one or more set of values. For example, an entry may represent {RIV-M(M+l) / 2, m_0, 1}. For example, the one or more set of values may comprise {0, 0, {0, 5}}, {1, 0, {0, 1, 5, 6}}, {2, 1, {0, 5}}, {3, 1, {0, 1, 3, 5, 6, 7, 8}}, {4, 2, {0, 5}}, {5, 2, {0, 1, 2, 5, 6, 7}}, {6, 3, {0, 5}}, and / or {7, 4, {0, 5}}.Resource allocation type and mechanism based on a DCI may be also applied to a configured grant configuration or semi-persistent scheduling configuration.In an example, a base station may configure a frequencyHoppingOffset, a frequency offset between a first frequency location of a first hop in a slot and a second frequency location of a second hop in the slot for a PUSCH transmission via the slot for an uplink carrier. For example, a wireless device may determine the first frequency location based on a frequency domain resource allocation field indicated by a scheduling DCI or based on one or more configuration parameters of a configured grant resource configuration. The wireless device may determine the second frequency location by adding the first frequency location and the frequency offset.In an example, a base station may transmit a DCI, wherein the DCI may comprise a time domain resource allocation field. A value of the time domain resource allocation field (e.g., m) may indicate a row index m+1 of a time domain resource allocation lists / a time domain resource allocation table. The base station may configure one or more time domain resource allocation tables. For example, a first time domain resource allocation table may be used for a fallback DCI format scheduled via a CSS. For example, a second time domain resource allocation table may be used for a fallback DCI format and / or a non-fallback DCI format via a USS. The wireless device may determine a time domain resource allocation table from the one or more time domain resource allocation tables for the DCI in response to receiving the DCI. The base station may configure one or more time domain resource allocation entries for a time domain resource allocation table. One time domain resource allocation entry may comprise a starting and a length indicator value (SLIV), a PUSCH mapping type, and K2 value, wherein the K2 may represent a scheduling offset between a scheduling DCI of a PUSCH and a starting slot index of the PUSCH. The one time domain resource allocation (TDRA) entry may comprise a repetition number (numberOfRepetitions). The one TDRA entry may comprise a starting symbol (startsymbol) and a length addition to the SLIV. For a PUSCH, scheduled by a non-fallback DCI format such as DCI format 0_l, a base station may configure PUSCHRepTypelndicaor-ForDCIFormatO_l to 'puschRepTypeB' indicating a repetition type B. In response to being configured with 'puschRepTypeB', the wireless device may determine a resource based on a procedure for therepetition type B and a time domain resource allocation field of a DCI based on the DCI format 0_l. Similarly, the base station may configure PUSCHRepTypelndicator-ForDCIformatO_2 to 'puschRepTypeB' to apply the repetition type B for a second DCI based on a DCI format 0_2. When the base station may not configure PUSCHRepTypelndicaor-ForDCIFormatO_l indicating 'puschRepTypeB', the wireless device may determine a time domain resource based on a DCI based on a repetition type A.For example, when the repetition type A is configured / enabled, the wireless device may determine a starting symbol S in a starting slot and a number of consecutive symbols L from the starting symbol S based on a SUV value. For example, the SUV value may define SUV = 14 * (L -1) + S wherein (L -1) is smaller than or equal to 7 (half slot based on a normal CP). The SLF value may define SUV = 14 * (14 -L+l)+(14-l-S) when (L-l) is larger than 7. For example, L would be greater than 0, and may be smaller than or equal to 14 -S. In an uplink BWP with an extended CP, 12 OFDM symbols may be assumed for a slot, wherein SUV value may be determined by 12 * (L-l)+S or 12 * (12-L+1)+(14-1-S) respectively based on L-l being smaller than / equal to 6 or larger than 6. For the repetition type A, the base station may configure a TypeA or Type B for a PUSCH mapping type. For example, the base station may determine a first OFDM symbol comprising a DM-RS based on a fixed location (e.g., a first symbol of a slot) wherein the TypeA is configured for the PUSCH mapping type. For example, the base station may determine a first OFDM symbol comprising a DM-RS based on a starting OFDM symbol of the PUSCH wherein the typeB is configured for the PUSCH mapping type.For example, when the repetition type B is configured / enabled, the wireless device may determine a starting OFDM symbol S in a starting slot, and a number of consecutive OFDM symbols L based on a row of a time domain resource allocation table. For example, the row of the time domain resource allocation table may comprise startsymbol for the starting OFDM symbol S and length for the number of consecutive OFDM symbols L. For the repetition type B, the wireless device may assume that the TypeB is configured for the PUSCH mapping type. For example, when a TypeA is configured for a PUSCH mapping type, a staring OFDM symbol S, a length L, and S+L may represent one or more values. For example, {S, L, S+L} may be {0, {4,..., 14}, {4,..., 14}} for a normal CP, and {0, {4,..., 12}, {4,..., 12}} for an extended CP. When a TypeB is configured for the PUSCH mapping type, {S, L, S+L} may be {{0,..., 13}, {1,..., 14}, {1,..., 14} for a repetition type A, {1,..., 27} for a repetition type B} for the normal CP, and {{0,..., 11}, {1,..., 12}, {1,..., 12}} for the extended CP.For a repetition type A, a wireless device may determine a repetition number K based on a row of a time domain resource allocation table, wherein the row may comprise a number of repetitions. The wireless device may determine based on a RRC parameter, 'pusch-AggregationFactor' wherein the row may not comprise the number of repetitions. The wireless device may determine a single transmission wherein the row may not comprise the number of repetitions nor the 'pusch-AggregationFactor' is not configured. The wireless device may determine the single transmission for a PUSCH scheduled by a fallback DCI such as a DCI format 0_0.For a repetition type A with a repetition number K being larger than 1, a wireless device may apply a starting OFDM symbol S and a length L in a slot across K consecutive slots based on a single transmission layer. The wireless device may repeat a TB across the K consecutive slots applying same OFDM symbols in each slot. A redundancy version (RV) applied on a i-th transmission of the K consecutive slots may be determined based on a repetition type. For example, when a RV value indicated by a DCI is 0, a second RV value for i-th transmission occasion (wherein a repetition type A is configured) or i-th actual repetition (wherein a repetition type B isconfigured) may be determined as 0 for i mod 4 = 0, 2 for i mod 4 = 1, 3 for i mod 4 = 1, 4 for i mod 4 = 3. When the RV value is 2, the second RV value may be determined as 2 for i mod 4 = 0, 3 for i mod 4 = 1, 1 for i mod 4 = 2, 0 for i mod 4 = 3. When the RV value is 3, the second RV value may be determined as 3 for i mod 4 = 0, 1 for i mod 4 = 1, 0 for i mod 4 = 2, 0 for i mod 4 = 2. When the RV value is 1, the second RV value may be determined as 1 for i mod 4 = 0, 0 for i mod 4 = 1, 2 for i mod 4 = 2, 3 for i mod 4 = 3.For a repetition type A, a PUSCH transmission of a slot over a plurality of slots may be omitted wherein the slot may not have a sufficient number of uplink OFDM symbols for the PUSCH transmission. For a repetition type B, a wireless device may determine one or more slots for a number of nominal repetition number N. For a i-th nominal repetition, wherein i is 0, N-l, wherein N may be configured by a base station via a RRC signaling or a time domain resource allocation of a DCI. The wireless device may determine a slot, wherein the i-th nominal repetition may start, wherein a slot index would be Ks + floor ( (S + il_) / N_slot_symbol ), and a starting symbol in the slot may be given by mod (S + il_, N_slot_symbol). The N_slot_symbol may be 14 with a normal CP and 12 with an extended CP. The S may represent a starting OFDM symbol indicated by a time domain resource allocation field of a DCI and L may represent a length indicated by the time domain resource allocation field of the DCI. The wireless device may determine a second slot wherein the i-th nominal repetition may end wherein a second slot index of the second slot may be determined as Ks + floor ( (S + (i+l)*L -l) / N_slot_symbol), and an ending symbol in the second slot may be determined as mod (S + (i+l)*L -1, N_slot_symbol). The Ks may be determined as a starting slot indicated by the time domain resource allocation field of the DCI.When the wireless device is configured with the repetition type B, the wireless device may determine invalid OFDM symbol for PUSCH repetitions based on a tdd-UL-DL-ConfigurationCommon / a tdd-UL-DL-ConfigurationDedicated and / or an InvalidSymbolPattern indicated by an RRC signaling. For example, the wireless device may determine a downlink symbol based on the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated as an invalid OFDM symbol for the repetition type B. The base station may transmit the InvalidSymbolPattern, a bitmap of OFDM symbols over one slot or two slots. A bit of the bitmap may indicate '1' to invalidate a corresponding OFDM symbol. The base station may further configure periodicityAndPattern, wherein a bit of the periodicityAndPattern may correspond to a unit equal to a duration of the bitmap of the InvalidSymbolPattern. The wireless device may determine invalid OFDM symbol(s) based on the InvalidSymbolPattern and the periodicityAndPattern. For example, when a PUSCH is scheduled / activated by a nonfallback DCI format such as a DCI format 0_l / 0_2 and lnvalidSymbolPatternlndicator-ForDCIFormat0_l / 0_2 is configured, a invalid symbol pattern indicator field may indicate 1, the wireless device may apply an invalid symbol pattern (e.g., InvalidSymbolPattern). Otherwise, the wireless device may not apply the invalid symbol pattern. When the lnvalidSymbolPatternlndicator-ForDCIFormat0_l / 0_2 is not configured, the wireless device may not apply the invalid symbol pattern. The wireless device may determine remaining OFDM symbols, wherein the remaining OFDM symbols may not comprise invalid OFDM symbol(s), the wireless device may consider the remaining OFDM symbols as valid OFDM symbols. When there is a sufficient number of valid OFDM symbols in a slot to transmit a PUSCH based on a scheduling DCI, the wireless device may determine an actual repetition of a slot wherein the slot may have consecutive sufficient valid consecutive OFDM symbols. The wireless device may skip the actual repetition based on a slot formation indication. The wireless device may apply a redundancy version based on the actual repetition.In an example, a row of a time domain resource allocation may comprise one or more resource assignments for one or more contiguous PUSCHs, wherein a K2 of the row may indicate a first PSCH of the one or more contiguous PUSCHs. Each PUSCH of the one or more contiguous PUSCHs may be indicated / scheduled with a separate SLIV value and a PUSCH mapping type.The PUSCH-Config IE may comprise a first parameter [frequencyHopping,frequencyHoppingDCi-0-1, frequencyHoppingDCI-0-2) indicating whether a frequency hopping is enabled or disabled, and / or whether the frequency hopping is an intra slot hopping or an inter-slot hopping. The first parameter may, if present, indicate one of {intraSlot, interSlot}. If the first parameter is present, a wireless device may determine to apply a frequency hopping for an uplink channel (e.g. a PUSCH, a PUCCH, a SRS) corresponding to a pusch-Config (based on the PUSCH-Config) comprised in configuration parameters of an uplink BWP. In the example, the uplink BWP is an active uplink BWP of a cell. In the example, the pusch-Config may be configured for the active uplink BWP. Based on the first parameter indicating 'intraSlot', the wireless device may determine an intra slot frequency hopping for the PUSCH, where a frequency hopping occurs within a slot. Based on the first parameter indicating 'interSlot', the wireless device may determine an inter slot frequency hopping, where a frequency hopping occurs across a plurality of slots. The value intraSlot enables ’I ntra-slot frequency hopping1and the value interSlot enables 'Inter-slot frequency hopping'. If the first parameter is absent, frequency hopping is not configured for 'pusch-RepTypeA'. The first parameter frequencyHopping applies to DCI formats 0_0, 0_l and 0_3 for 'pusch-RepTypeA'.A field frequencyHoppingDCI-0-1 may indicate the frequency hopping scheme for DCI format 0_l when pusch-RepTypelndicatorDCI-0-1 is set to 'pusch-RepTypeB', The value interRepetition enables 'Interrepetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for DCI format 0_l for 'pusch-RepTypeB'.Afield frequencyHoppingDCI-0-2 may indicate the frequency hopping scheme for DCI format 0_2. The value intraSlot enables 'intra-slot frequency hopping', and the value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. When pusch-RepTypelndicatorDCI-0-2 is not set to 'pusch-RepTypeB', the frequency hopping scheme may be chosen between 'intra-slot frequency hopping and 'inter-slot frequency hopping' if enabled. When pusch-RepTypelndicatorDCI-0-2 is set to 'pusch- RepTypeB', the frequency hopping scheme may be chosen between 'inter-repetition frequency hopping' and 'inter-slot frequency hopping' if enabled. If the field is absent, frequency hopping is not configured for DCI format 0_2.The PUSCH-Config IE (e.g., the pusch-Config of the uplink BWP) may comprise a second parameter indicating a list of frequency hopping offset values [frequencyHoppingOffsetLists,frequencyHoppingOffsetListsDCI-0-2). A number of the list may be up to K (e.g., K = 4), where the number may be determined based on a bandwidth size of the uplink BWP. The list of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation. A ie\dfrequencyHoppingOffsetLists applies to DCI formats 0_0, 0_l and 0_3, and a f'\e\dfrequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2.The PUSCH-Config IE (e.g., the pusch-Config of the uplink BWP) may comprise a third parameter indicating whether to enable a slot counting based on available slots (availableSlotCounting). The third parameter may indicate whether PUSCH repetitions counted on the basis of available slots is enabled. If the field is absent, PUSCH repetitions counted on the basis of available slots is disabled.The PUSCH-Config IE (e.g., the pusch-Config of the uplink BWP) may comprise a fourth parameter indicating one or more beta offset values via one or more fields (betaOffsetsCrossPriO, betaOffsetsCrossPril, betaOffsetsCrossPriODCI-O-2, betaOffsetsCrossPrilDCI-O-2). A field betaOffsetsCrossPrioO may indicate multiplexing low priority (LP) HARQ-ACK on dynamically scheduled high priority (HP) PUSCH. The field betaOffsetsCrossPrioO may be used when the wireless device multiplex LP HARQ-ACK on HP PUSCH. Each field may comprise one or more beta offset values. In an example, low priority may be indicated based on a priority index = 0 (or Cl). High priority may be indicated based on a second priority index = 1 (or C2). A field betaOffsetsCrossPriol may indicate multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH. A field betaOffsetsCrossPrioODCI-O-2 may indicate multiplexing LP HARQ-ACK on dynamically scheduled HP PUSCH by DCI format 0_2. A field betaOffsetsCrossPriolDCI-O-2 may indicate multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH by DCI format 0_2.The PUSCH-Config IE (e.g., the pusch-Config of the uplink BWP) may comprise a fifth parameter (e.g., dmrs-BundlingPUSCH-Config) indicating a DM-RS bundling for PUSCH transmissions based on the pusch-Config in the uplink BWP.The PUSCH-Config IE (e.g., the pusch-Config of the uplink BWP) may comprise a sixth parameter (e.g., pusch-RepTypelndicatorDCI-0-1, pusch-RepTypelndicatorDCI-0-2) indicating a repetition type. The sixth parameter may indicate whether the wireless device follows the behavior for " PUSCH repetition type A" or the behavior for " PUSCH repetition type B" for the PUSCH scheduled by DCI format 0_l / 0_2 and for Type 2 CG associated with the activating DCI format 0_l / 0_2. The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B'. The field pusch-RepTypelndicatorDCI-0-1 applies to DCI format 0_l and the field pusch-RepTypelndicatorDCI-0-2 applies to DCI format 0_2.The PUSCH-Config may comprise a seventh parameter indicating a field transformPrecoder, where the field indicates a UE-specific selection of transform precoder for PUSCH. When the field is absent, the wireless device may apply a value of the field msg3-transformPrecoder from rach-ConfigCommon included directly within an uplink BWP configuration (i.e., not included in additional RACH-ConfigList).The PUSCH-Config may comprise an eighth parameter indicating one or more fields of (transformPrecoder uci-OnPUSCH-ListDCI-O-1, uci-OnPUSCH-ListDCI-O-2). The one or more fields may provide configurations for up to 2 HARQ-ACK codebooks specific to DCI format 0_l / 0_2. The field uci-OnPUSCH-ListDCI-O-1 applies to DCI format 0_l and the field uci-OnPUSCHListDCI-O-2 applies to DCI format 0_2. The field uci-OnPUSCH-ListDCI-0-1 may comprise one or more UCI-OnPUSCH configurations. Each UCI-OnPUSCH may comprise / indicate parameters of i) beta offsets (betaOffsets) indicating selection between and configuration of dynamic and semistatic beta-offset for DCI formats other than DCI format 0_2. If the field (betaOffsets) is not configured, the UE applies the value 'semiStatic' to determine a beta offset value for a PUSCH transmission via the uplink BWP; and ii) scaling indicating a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI formats other than DCI format 0_2. Value fOp5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. The value configured herein is applicable for PUSCH with configured grant.The field uci-OnPUSCH-ListDCI-O-2 may comprise one or more UCI-OnPUSCH-DCI-O-2 configurations. Each UCI-OnPUSCH-DCI-O-2 may comprise / indicate parameters of beta offsets (betaOffsetsDCI-O-2) indicating selection between and configuration of dynamic and semi-static beta-offset for DCI formats 0_2. If semiStaticDCI-0-2 is chosen, the wireless device may apply the value of 0 bit for the field of beta offset indicator inDCI format 0_2. If dynamicDCI-0-2 is chosen, the wireless device may apply the value of 1 bit or 2 bits for the field of beta offset indicator in DCI format 0_2. The field dynamicDCI-0-2 may indicate the wireless device applies the value 'dynamic' for DCI format 0_2. The field semiStaticDCI-0-2 may indicate the wireless device applies the value 'semiStatic' for DCI format 0_2. The parameters of the beta offsets betaOffsetsDCI-O-2] may further comprise a field scalingDCI-0-2 indicating a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI format 0_2. Value fOp5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on.In an example, for a PUSCH scheduled by RAR UL grant, fall backRAR UL grant, or by DCI format 0_0 with CRC scrambled by TC-RNTI, frequency offsets are obtained based on a frequency hopping determination procedure described in below. Otherwise, for a PUSCH scheduled by DCI format 0_0 / 0_l / 0_3 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_0 / 0_l and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config. For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetListsDCI-O-2 in pusch-Config.When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in the UL grant. When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant.For PUSCH based on a Typel configured UL grant the frequency offset is provided by the higher layer parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.For a MsgA PUSCH the frequency offset is provided by the higher layer parameter as described in the frequency hopping determination procedure described in below.In case of intra-slot frequency hopping, the starting RB in each hop is given bywhere RBstart is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 and RBotfset is the frequency offset in RBs between the two frequency hops.In case of inter-slot frequency hopping, the starting RB during slot follows that of inter-slot frequency hopping for PUSCH Repetition Type A.In an example, the frequency hopping determination procedure may be as follows. This may be applied to a PUSCH scheduled by RAR UL grant, fal I backRAR UL grant, or by DCI format 0_0 with CRC scrambled by TC-RNTI. An active UL BWP with SCS configuration p for a PUSCH transmission scheduled by a RAR UL grant is indicated by higher layers. If uselnterlacePUCCH-PUSCH is not provided by BWP-UplinkCommon and BWP-UplinkDedicated, for determining the frequency domain resource allocation for the PUSCH transmission within the active UL BWP, i) if the active UL BWP and the initial UL BWP have same SCS and same CP length and the active UL BWP includes all RBs of the initial UL BWP, or the active UL BWP is the initial UL BWP, the initial UL BWP is used; ii) else if the PUSCH is during SBFD symbols, the RB numbering starts from the first RB of the active UL BWP + a frequency offset and the maximum number of RBs for frequency domain resource allocation equals the number of RBs in the initial UL BWP; iii) else the PUSCH is during non-SBFD symbols, the RB numbering starts from the first RB of the active UL BWP and the maximum number of RBs for frequency domain resource allocation equals thenumber of RBs in the initial UL BWP. The frequency offset may be provided in a rach-ConfigCommon for one or more random access resources for SBFD-aware UEs.The frequency domain resource allocation is by uplink resource allocation type 1. For an initial UL BWP size of AQePRBs, a wireless device processes the frequency domain resource assignment field as follows: i) if WBswp < 180, or for operation with shared spectrum channel access in FR1 or for FR2-2 when ChannelAccessMode2-rl7 is provided if WBS™P< 90, truncate the frequency domain resource assignment field to its[log2( / VBswp ■ (Wpwp + l) / 2)] least significant bits and interpret the truncated frequency resource assignment field as for the frequency resource assignment field in DCI format 0_0; ii) else insert [log2(NB“P■ (NB™P+ l) / 2)] - 14 most significant bits with value set to 'O' after the NULhopbits to the frequency domain resource assignment field, where NuL,hop=0 if the frequency hopping flag is set to 'O' and NuL,hop 'sprovided in Table A if the hopping flag bit is set to '1', and interpret the expanded frequency resource assignment field as for the frequency resource assignment field in DCI format 0_0.For a PUSCH transmission with frequency hopping scheduled by RAR UL grant or for a Msg3 PUSCH retransmission, the frequency offset for the second hop is given in the Table A below.Table A: Frequency offset for second hop of PUSCH transmission with frequency hopping scheduled by RAR UL grant or of Msg3 PUSCH retransmissionNumber of PRBs in initial UL BWP Value of / VUL|,,,pHopping Bits Frequency offset for 2ndhop0 I^BWP / 2];Mv size> 50BWPD U1 [<eP / 4]00 I^BWP / 2]01 [<eP / 4]1 M’BsWizeP > — 5010 -LWWP / 4]11 ReservedA SCS for the PUSCH transmission is provided by subcarrierSpacing in BWP-UplinkCommon. A wireless device transmits PRACH and the PUSCH on a same uplink carrier of a same serving cell. A wireless device transmits a transport block in a PUSCH scheduled by a RAR UL grant in a corresponding RAR message using redundancy version number 0, if the PUSCH transmission is without repetitions. If a TC-RNTI is provided by higher layers, the scrambling initialization of the PUSCH corresponding to the RAR UL grant is by TC-RNTI. Otherwise, the scrambling initialization of the PUSCH corresponding to the RAR UL grant is by C-RNTI. If a wireless device is provided tag2-ld, the UE transmits a transport block in a PUSCH scheduled by a RAR UL grant in a corresponding RAR message with timing advance corresponding to a TAG indicated by the RAR message. Msg3 PUSCH retransmissions, if any, of the transport block, are scheduled by a DCI format 0_0 with CRC scrambled by a TC-RNTI provided in the corresponding RAR message.A wireless device may be provided in BWP-UplinkCommon a set of numbers of repetitions for a PUSCH transmission with PUSCH repetition Type A that is scheduled by a RAR UL grant or by a DCI format 0_0 with CRC scrambled by a TC-RNTI. If the wireless device requests repetitions for the PUSCH transmission, the wireless device transmits the PUSCH oversi ots, where ^5^ is indicated by the 2 MSBs of the MCS field in the RAR UL grant or in the DCI format 0_0 from a set of four values provided by numberOfMsg3-RepetitionsList or from {1, 2, 3, 4} if numberOfMsg3-RepetitionsList is not provided. The wireless device may determine an MCS for the PUSCHtransmission by the 2 LSBs of the MCS field in the RAR UL grant or by the 3 LSBs of the MCS field in the DCI format 0_0, and determines a redundancy version and RBs for each repetition. For unpaired spectrum operation, the wireless device may determine thesl°ts asf'rstnjsaHs'ots startinS from slot n + / r2+ A + 2 ■ #celloffset where a repetition of the PUSCH transmission does not include a symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon or indicated as a symbol of an SS / PBCH block with index provided by ssb-PositionsInBurst, and where #cen,offsetis provided by cellSpecificKoffset; otherwise, if not provided, #cen,offset= 0. For paired spectrum operation, the wireless device may determine theslots as the first ^5^ slots starting from slot n + k2+ A + 2 ■ A'ceuoffset where ^cell, offset is provided by cellSpecificKoffset; otherwise, if not provided, ^cell, offset=0- The wireless device may assume a minimum time between the last symbol of a PDSCH reception conveying a RAR message with a RAR UL grant and the first symbol of a corresponding PUSCH transmission scheduled by the RAR UL grant is equal to NT 1+ NT 2+ 0.5 msec, where NT 1is a time duration of symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured, NT 2is a time duration of N2symbols corresponding to a PUSCH preparation time for UE processing capability 1 and, for determining the minimum time, the wireless device may consider that Nrand N2correspond to the smaller of the SCS configurations for the PDSCH and the PUSCH. For p = 0, the UE assumes N10= 14.Frequency hopping for PUSCH repetition Type A and for TB processing over multiple slots For PUSCH repetition Type A other than the PUSCH scheduled by RAR UL grant or fal I backRAR UL grant or by DCI format 0_0 with CRC scrambled by TC-RNTI and for TB processing over multiple slots, a wireless device is configured for frequency hopping by the higher layer parameter frequencyHoppingDCI-0-2 in pusch-Config for PUSCH transmission scheduled by DCI format 0_2, and b frequencyHopping provided in pusch-Config for PUSCH transmission scheduled by a DCI format other than 0_2, and b frequencyHopping provided in configuredGrantConfig for configured PUSCH transmission. For PUSCH repetition Type A scheduled by RAR UL grant or by DCI format 0_0 with CRC scrambled by TC-RNTI, a UE is configured for frequency hopping by the frequency hopping flag information field of the RAR UL grant, and by the frequency hopping flag information field of DCI format 0_0 with CRC scrambled by TC-RNTI, respectively.One of two frequency hopping modes may be configured: i) I ntra-sl ot frequency hopping, applicable to single slot and multi-slot configured PUSCH transmission, multi-slot PUSCH transmission scheduled by DCI format 0_1, 0_2 or 0_3, each of multiple PUSCH transmissions on a serving cell scheduled by a DCI if the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH is configured and each of multiple configured grant PUSCH transmissions in a configuration where the higher layer parameters cg-nrofSIots and cg-nrofPUSCH-InSlot are provided; and ii) Inter-slot frequency hopping, applicable to multi-slot PUSCH transmission.In case of resource allocation type 2, the wireless device transmits PUSCH without frequency hopping.In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the wireless device may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format or in a random access response UL grant is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter frequencyHoppingOffset is provided, otherwise no PUSCH frequency hopping is performed. For a PUSCH scheduled by RAR UL grant, fall backRAR UL grant, or by DCI format 0_0 with CRC scrambled by TC-RNTI, frequency offsets are obtained as described in the frequency hoppingdetermination procedure in the above. Otherwise, for a PUSCH scheduled by DCI format 0_0 / 0_l / 0_3 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_0 / 0_l and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config. For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetListsDCI-O-2 in pusch-Config.1) When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in the UL grant.2) When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant.For PUSCH based on a Typel configured UL grant the frequency offset is provided by the higher layer parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant. For a MsgA PUSCH the frequency offset is provided by the higher layer parameter.In case of intra-slot frequency hopping, the starting RB in each hop is given by:, where / =0 and / =1 are the first hop and the second hop respectively, and is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 or as calculated from the resource assignment for MsgA PUSCH and is the frequency offset in RBs between the two frequency hops. The number of symbols in the first hop is given by, the number of symbols in the second hop is given by, where^symbH'S'slength of the PUSCH transmission in OFDM symbols in one slot.In case of inter-slot frequency hopping and when pusch-DMRS-Bundling is not enabled, or for inter-slot frequency hopping for a PUSCH scheduled by RAR UL grant or DCI format 0_0 with CRC scrambled by TC- RNTI, the starting RB during slot is given by:, where is the current slot number within a system radio frame, where a multi-slot PUSCH transmission can take place, is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 and is the frequency offset in RBs between the two frequency hops.In case of inter-slot frequency hopping and when pusch-DMRS-Bundling is enabled, and when a PUSCH is not scheduled by RAR UL grant or DCI format 0_0 with CRC scrambled by TC-RNTI, the starting RB during slot is given by:sRestart mod 2=0NFHRestart II, where is the current slot number within a system (RBstartn+ RBoffset)mod / VB^cp s mod 2=1NFHradio frame, NFHis the value of the higher layer parameter pusch-FrequencyHopping-lnterval, is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and is the frequency offset in RBs between the two frequency hops.Frequency hopping for PUSCH repetition Type B.For PUSCH repetition Type B, a wireless device is configured for frequency hopping by the higher layer parameter frequencyHoppingDCI-0-2 in pusch-Config for PUSCH transmission scheduled by DCI format 0_2, by frequencyHoppingDCI-0-1 provided in pusch-Config for PUSCH transmission scheduled by DCI format 0_l, and by frequencyHoppingPUSCH-RepTypeB provided in rrc-ConfiguredUplinkGrant for Type 1 configured PUSCH transmission. The frequency hopping mode for Type 2 configured PUSCH transmission follows the configuration of the activating DCI format. One of two frequency hopping modes can be configured, between inter-repetition frequency hopping and inter-slot frequency hopping.In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the wireless device may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter frequencyHoppingPUSCH-RepTypeB is provided, otherwise no PUSCH frequency hopping is performed.For a PUSCH scheduled by DCI format 0_l or a PUSCH based on a Type 2 configured UL grant activated by DCI format 0_l and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config. For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a Type 2 configured UL grant activated by DCI format 0_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetListsDCI-O-2 in pusch-Config.1) When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in the UL grant.2) When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant.For PUSCH based on a Typel configured UL grant the frequency offset is provided by the higher layer parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.In case of inter-repetition frequency hopping, the starting RB for an actual repetition within the n- th nominal repetition (as defined in Clause 6.1.2.1) is given by| IIHlOC12S0......RB (») = <, where RBstart is the starting RB within the UL BWP, ascalculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and RBotfset is the frequency offset in RBs between the two frequency hops.In case of inter-slot frequency hopping, the starting RB during slot follows that of inter-slot frequency hopping for PUSCH Repetition Type A.UE procedure for determining time domain windows for bundling DM-RSFor PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0_1, 0_2 or 0_3, PUSCH repetition Type A with a configured grant, PUSCH repetition Type B and TB processing over multiple slots, when pusch-DMRS-Bundling is enabled, and for PUCCH transmissions of PUCCH repetition, when PUCCH-DMRS- Bundling is enabled, the UE determines one or multiple nominal TDWs, as follows.A) For PUSCH transmissions of repetition Type A, PUSCH repetition Type B and TB processing over multiple slots, the duration of each nominal TDW except the last nominal TDW, in number of consecutive slots, isA-l) Given by pusch-TimeDomainWindowLength, if configuredA-2) Computed as min (maxDurationDMRS-Bundling, M), if pusch-TimeDomainWindowLength is not configured, where maxDurationDMRS-Bundling is maximum duration for a nominal TDW subject to UE capability [13, TS 38.306], M is the time duration in consecutive slots of N ■ K PUSCH transmissions, and where A-2-1) For PUSCH transmissions of PUSCH repetition Type A, N=1 and K is the number of repetitionsA-2-2) For PUSCH transmissions of PUSCH repetition Type B, N=1 and K is the number of nominal repetitionsA-2-3) For PUSCH transmissions of TB processing over multiple slots, N is the number of slots used for TBS determination and K is the number of repetitions of the number of slots N used for TBS determination B) For PUCCH transmissions of PUCCH repetition, the duration of each nominal TDW except the last nominal TDW, in number of consecutive slots, isB-l) Given by pucch-TimeDomainWindowLength, if configuredB-l-1) Computed as min (maxDurationDMRS-Bundling, M), if pucch-TimeDomainWindowLength is not configured, where maxDurationDMRS-Bundling is maximum duration for a nominal TDW subject to UE capability, M is the time duration in consecutive slots from the first slot determined for PUCCH transmissions of PUCCH repetition to the last slot determined for PUCCH transmissions of PUCCH repetitionC) For PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0_1, 0_2 or 0_3 and PUSCH repetition Type A with a configured grant, when AvailableSlotCounting is enabled, and for TB processing over multiple slots:C-l) The start of the first nominal TDW is the first slot determined for the first PUSCH transmission;C-2) The end of the last nominal TDW is the last slot determined for the last PUSCH transmission; C-3) The start of any other nominal TDWs is the first slot determined for PUSCH transmission after the last slot determined for PUSCH transmission of a previous nominal TDW.D) For PUSCH transmissions of a PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3 and PUSCH repetition Type A with a configured grant, when the UE is not configured with AvailableSlotCounting and for PUSCH repetition type B:D-l) The start of the first nominal TDW is the first slot for the first PUSCH transmission.D-2) The end of the last nominal TDW is the last slot for the last PUSCH transmission.D-3) The start of any other nominal TDWs is the first slot after the last slot of a previous nominal TDW.E) For PUCCH transmissions of a PUCCH repetition:E-l) The start of the first nominal TDW is the first slot determined for the first PUCCH transmission.E-2) The end of the last nominal TDW is the last slot determined for the last PUCCH transmission. E-3) The start of any other nominal TDWs is the first slot determined for PUCCH transmission after the last slot determined for PUCCH transmission of a previous nominal TDW.For PUSCH transmissions of a PUSCH repetition Type A scheduled by DCI format 0_1, 0_2 or 0_3, PUSCH repetition Type A with a configured grant, PUSCH repetition Type B and TB processing over multiple slots, a nominal TDW consists of one or multiple actual TDWs. The UE determines the actual TDWs as follows:A) The start of the first actual TDW is the first symbol of the first PUSCH transmission in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW.B) The end of an actual TDW isB-l) The last symbol of the last PUSCH transmission in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B orTB processing over multiple slots within the nominal TDW, if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW.B-2) The last symbol of a PUSCH transmission before the event, if an event occurs which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots.C) When pusch-WindowRestart is enabled, the start of a new actual TDW is the first symbol of the PUSCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots.For PUCCH transmissions of PUCCH repetition, a nominal TDW consists of one or multiple actual TDWs. The UE determines the actual TDWs as follows:A) The start of the first actual TDW is the first symbol of the first PUCCH transmission in a slot determined for PUCCH transmission within the nominal TDW.B) The end of an actual TDW isB-l) The last symbol of the last PUCCH transmission in a slot determined for transmission of the PUCCH within the nominal TDW, if the actual TDW reaches the end of the last PUCCH transmission within the nominal TDW.B-2) The last symbol of a PUCCH transmission before the event, if an event occurs which causes power consistency and phase continuity not be maintained across PUCCH transmissions of PUCCH repetition within the nominal TDW, and the PUCCH transmission is in a slot determined for transmission of the PUCCH.C) When pucch-WindowRestart is enabled, the start of a new actual TDW is the first symbol of the PUCCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUCCH transmissions of PUCCH repetition within the nominal TDW, and the PUCCH transmission is in a slot determined for transmission of the PUCCH.Events which cause power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B orTB processing over multiple slots, or PUCCH transmissions of PUCCH repetition, within the nominal TDW, are:A) A downlink slot or downlink reception or downlink monitoring based on tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated for unpaired spectrum.B) For the UE indicating the capability dmrs-BundlingNonBackToBackTX or dmrs-BundlingNonBackToBackTX-PerBC in [13, TS 38.306], the gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, exceeds 13 symbols for normal cyclic prefix or exceeds 11 symbols for extended cyclic prefix.C) For the UE not indicating either of the capabilities dmrs-BundlingNonBackToBackTX or dmrs-BundlingNonBackToBackTX-PerBC in [13, TS 38.306], a non-zero symbol gap is scheduled between any two consecutive PUSCH transmissions or between any two consecutive PUCCH transmissions.D) The gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, does not exceed 13 symbols but other uplink transmissions are scheduled between the two consecutive PUSCH transmissions or the two consecutive PUCCH transmissions.E) For PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B or TB processing over multiple slots, a dropping or cancellation of a PUSCH transmission according to clause 9, clause 11.1 and clause 11.2A of [6, TS 38.213] or due to cell DRX operation.F) For PUCCH transmissions of PUCCH repetition, a dropping or cancellation of a PUCCH transmission according to clause 9, clause 9.2.6 and clause 11.1 of [6, TS 38.213] or due to cell DRX operation.G) For any two consecutive PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, and when neither multipanelSchemeSDM nor multipanelSchemeSFN is configured and two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with higher layer parameter usage in SRS-ResourceSet set to 'codebook' or 'nonCodebook', a different SRS resource set association is used for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, according to Clause 6.1.2.1.H) For any two consecutive PUCCH transmissions of PUCCH repetition, and when a PUCCH resource used for repetitions of a PUCCH transmission by a UE includes first and second spatial relations or first and second sets of power control parameters, as described in [10, TS 38.321] and in clause 7.2.1 of [6, TS 38.213], different spatial relations or different power control parameters are used for the two PUCCH transmissions of PUCCH repetition, according to Clause 9.2.6 of [6, TS 38.213],I) Uplink timing adjustment in response to a timing advance command according to clause 4.2 of [6, TS 38.213],J) Frequency hoppingH) For reduced capability half-duplex UEs, a dropping or cancellation of a PUSCH or PUCCH transmission according to clause 17.2 of [6, TS 38.213] or an overlapping of the gap between two consecutive PUSCH or two consecutive PUCCH transmissions and any symbol of downlink reception or downlink monitoring.The wireless device may maintain power consistency and phase continuity within an actual TDW, across PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or across PUCCH transmissions of PUCCH repetition, in case the actual TDW is created in response to frequency hopping, or in response to the use of a different SRS resource set association for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, or in response to the use of different spatial relations or different power control parameters for the two PUCCH transmissions of PUCCH repetition, or in response to any event not triggered by DCI or MAC-CE. The UE maintains power consistency and phase continuity within an actual TDW, across PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0_1, 0_2 or 0_3, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or across PUCCH transmissions of PUCCH repetition, in case the actual TDW is created in response to an event triggered by DCI other than frequency hopping or the use of a different SRS resource set association for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, or the use of different spatial relations or different power control parameters for the two PUCCH transmissions of PUCCH repetition, or in response to an event triggered by MAC-CE, subject to UE capability, of dmrs-BundlingRestart and when pusch-WindowRestart or pucch-WindowRestart is enabled.In an example, a wireless device may receive one or more RRC / SIB messages indicating configuration parameters. The configuration parameters may comprise one or more UL / DLTDD (or TDD) configurations of / for a cell. The one or more UL / DL TDD configurations of / for the cell may be (or comprise) a cellspecific UL / DLTDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) of / for the cell. The one or more UL / DL TDD configuration of / for the cell may be (or comprise) a UE-specific UL / DL TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated). In an example, the cell-specific UL / DLTDD configuration for the cell may be broadcasted via a SIB1 or a SIB message. In an example, the UE-specific UL / DL TDD configuration for the cell may be transmitted via one or more messages (e.g., RRC, MAC CE, DCI).The configuration parameters may be / comprise one or more TDD configuration parameters. The one or more TDD configuration parameters may comprise one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon) and / or one or more UE-specific TDD configuration parameters (e.g. TDD-UL-DL-ConfigurationDeicated).For a serving cell (of the one or more serving cells), one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon) may indicate / configure slot format(s) of a plurality of slots.The one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon) may indicate / configure the plurality of slots. The plurality of slots may comprise one or more consecutive slots. The plurality of slots may comprise one or more DL slots / symbols. The plurality of slots may comprise one or more UL slots / symbols. The plurality of slots may comprise one or more flexible slots / symbols.A first symbol / slot of the plurality of slots may be an Uplink ('U' / UL) symbol. An UL symbol may be used by the wireless device for uplink transmission(s), e.g., via the serving cell. The one or more UL slots / symbols may comprise the first symbol / slot.A second symbol / slot of the plurality of slots may be a downlink ('D' / DL). A DL symbol may be used by the wireless device for downlink reception(s), e.g., via the serving cell. The one or more DL slots / symbols may comprise the second symbol / slot.In some implementations, a third symbol in a slot of the plurality of slots may be a flexible ('F') symbol. The one or more flexible slots / symbols may comprise the third symbol / slot. Slot format / direction of the flexible symbol may be determined (by the wireless device and / or the base station) by other signaling, e.g., DCI format 2_0 and / or UL / DL grants and / or the one or more UE-specific TDD configuration parameters. The format 'F' is used by the network to control UL / DL transmission / reception of each wireless device flexibly. For example, the network may assign a symbol with 'F' for a wireless device not to transmit to or receive from a base station, e.g., for interference control and / or power saving purposes. For example, the network may use a slot format 'F' on one or more symbols to selectively initiate / trigger random access (RA) for a particular wireless device. Other wireless devices may not be allowed to transmit or receive on the one or more symbols, resulting in reduced interference for the wireless device.The one or more common TDD configuration parameters may comprise at least one of: a reference subcarrier spacing (SCS) / zreand / or at least one TDD pattern. The at least one TDD pattern may comprise a first TDD pattern (e.g., pattern!.} and / or a second TDD pattern (e.g., pattern2}. A TDD pattern of the at least one TDD pattern may be a TDD-UL-DL patternA TDD pattern (e.g., the first TDD pattern or the second TDD pattern) of the at least one TDD pattern may comprise at least one of: a slot configuration period of P msec (e.g., a TDD periodicity); a number of slots dslotswith only downlink symbols (e.g., DL slot(s)); a number of downlink symbols dsym(e.g., DL symbol(s)); a number of slots uslotswith only uplink symbols (e.g., UL slot(s)); a number of uplink symbols usym(e.g., UL symbol(s)). The one or more DL symbols / slots may comprise the number of slots dslotsand / or the number of downlink symbols dsym. The one or more UL symbols / slots may comprise the number of slots uslotsand / or the number of uplink symbols usym. For example, the rest of slots / symbols in the TDD pattern (withing the slot configuration period P) not indicated by the TDD pattern as DL / UL slots / symbols may be flexible slots / symbols. The one or more flexible slots / symbols may comprise the rest of slots / symbols in the TDD pattern (withing the slot configuration period P) not indicated by the TDD pattern as DL / UL slots / symbols.Corresponding to each TDD pattern of the at least one TDD pattern, a TDD periodicity (e.g., the corresponding slot configuration period of the TDD pattern) may comprise S = P·2^μref(consecutive) slots with SCS configurationref. The one or more consecutive slots may comprise S1= P1·2^μref(consecutive) slots (of the first TDD pattern) and / or= P- - ^f (consecutive) slots (of the second TDD pattern). The TDD periodicity P may be a summation of a first TDD periodicity Pr(of the first TDD pattern) and a second TDD periodicity P2(of the first TDD pattern), e.g., P = Pr+ P2.From slots (i=l corresponding to the first TDD pattern or i=2 corresponding to the second TDD pattern), a first / initial / starting / earliest dslotsslots may comprise the one or more DL slots / symbols. From S slots, a last / final / ending / latest uslotsslots may comprise the one or more UL slots / symbols. A dsymsymbols after the first dslotsslots may comprise the one or more DL symbols. A usymsymbols before the last uslotsslots may comprise the one or more UL symbols. A remaining (S - dslots- uslots). N^yi^h- dsym- usymsymbols may comprise the one or more flexible symbols / slots.FIGs. 18A and 18B show an example of subband full-duplex (SBFD) operation as per an aspect of an embodiment of the present disclosure. FIGs. 18A and 18B show two examples of SBFD operations in a carrier. Other examples are also possible. The carrier may be a TDD carrier. The carrier may be an FDD carrier.In an example, a SBFD operation of a cell may be referred as (or interchangeably used in some embodiments) a SBFD mode of the cell, a new enhanced duplex mode of the cell, a hybrid TDD / FDD mode of the cell, an enhanced duplexing operation of the cell, configuration one or more UL subbands (and / or one or more DL subbands) via the cell, and / or the like. Using the SBFD operation, a wireless device and / or a base station may reduce UL transmission latency or UL transmission capacity, as the wireless device may be allowed / configured to transmit UL signals / channels in / during SBFD symbols / slots.In an example, a SBFD symbol may be referred as (or interchangeably used with) a flexible symbol in a SBFD carrier / serving cell / cell, a SBFD symbol of a carrier / serving cell / cel I, a downlink / flexible symbol with a UL subband configured, a symbol (e.g., a downlink or a flexible symbol) with a UL subband configured, a time unit configured with a UL subband, a symbol referred as a SBFD operation, a symbol where a wireless device operates a SBFD operation, a symbol indicated to apply a SBFD operation or a UL band by one or more SBFD configuration parameters and one or more RRC messages indicating to enable the SBFD operation on the symbol, and / or the like. For example, a downlink symbol may be referred as a symbol indicated as downlink via one or more UL / DL TDD configurations. An uplink symbol may be referred as a symbol indicated as uplink via the one or more UL / DL TDD configurations. A flexible symbol may be referred as a symbol indicted as flexible via the one or more UL / DL TDD configurations. A non-SBFD symbol may refer a uplink symbol, a downlink symbol or a flexible symbol based on the one or more UL / DL TDD configurations, but not indicated as a SBFD symbol based on the one or more SBFD configuration parameters. A SBFD symbol may refer a symbol indicated for a SBFD operation based on the one or more SBFD configuration parameters.In an example, a SBFD symbol may refer a symbol on a cel l / carrier / serving cell. In the example, the cell / carrier / serving cell is enabled / indicated / configured with a SBFD operation. The symbol may be indicated as a downlink symbol or a flexible symbol on the cell / carrier / serving cell via one or more messages (e.g., tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated).The SBFD symbols / slots are the DL slots / symbols (configured by the one or more configuration parameters) configured / indicated for the SBFD operation.The one or more configuration parameters may configure a wireless device with the SBFD operation in the carrier. The one or more configuration parameters may comprise one or more SBFD configuration parameters. The one or more TDD configuration parameters may comprise one or more SBFD configuration parameters.The wireless device may be in an RRC connected state. For example, the one or more SBFD configuration parameters may indicate / configure / enable the wireless device for the SBFD operation only when the wireless device is in the RRC connected state. The wireless device may perform a handover procedure (to handover from a source cell of the one or more serving cells to a target cell) based on the one or more SBFD configuration parameters.The wireless device may be in an RRC idle / inactive state. For example, the one or more SBFD configuration parameters may indicate / configure / enable the wireless device for the SBFD operation when thewireless device is in the RRC idle / inactive state. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform an initial access procedure (e.g., a random access procedure for the initial access) based on the one or more SBFD configuration parameters. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform a small data transmission (SDT) procedure based on the one or more SBFD configuration parameters. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform SRS transmission for positioning procedure based on the one or more SBFD configuration parameters.The one or more SBFD configuration parameters may comprise one or more cell-specific (or common) SBFD configuration parameters.The one or more SBFD configuration parameters may comprise one or more UE-specific (or dedicated) SBFD configuration parameters.The one or more SBFD configuration parameters may configure one or more SBFD or uplink (UL) subbands. In an example, the wireless device may determine one or more DL subbands based on the one or more UL subbands (e.g., frequency regions of an active downlink BWP excluding the one or more UL subbands and guard band(s) is considered as the one or more DL subbands). The one or more SBFD configuration parameters may configure / indicate a SBFD / UL subband time locations of a SBFD / UL subband (of the one or more SBFD / UL subbands). The one or more SBFD configuration parameters may configure / indicate a SBFD / UL subband frequency locations of the SBFD / UL subband. For example, the SBFD / UL subband time locations may be within a first period. The first period may be a SBFD period (or a SBFD periodicity). In an example, a set of contiguous PRBs are configured as a SBFD or UL subband, where the wireless device may determine SBUL (UL subband) based on the set of contiguous PRBs and SBUL (DL subband) based on the active downlink BWP and the set of contiguous PRBs.The one or more SBFD configuration parameters may configure / indicate a set of SBFD symbols in time locations. The one or more SBFD configuration parameters may configure / indicate one or more DL subbands in a SBFD symbol, and / or one or more UL subbands in a SBFD symbol. The wireless device may determine one or more guard frequency region between a DL subband of the one or more DL subbands and a UL subband of the one or more UL subbands based on the one or more SBFD configuration parameters, e.g., remaining PRBs not belonging to any DL subband or any UL subband, between two adjacent DL subband and UL subband, may be considered as a guard PRB for the guard frequency region.The first period may be based on the at least one TDD pattern. For example, the first period may be the TDD periodicity. The first period may be larger than the TDD periodicity. The first period may be smaller than the TDD periodicity. The one or more SBFD configuration parameters may indicate / configure the first period.The first period may be equal to a multiplication of a second value and the TDD periodicity. The one or more SBFD configuration parameters may indicate / configure the second value.The first period may be based on the first TDD pattern. For example, the first period may be the first TDD periodicity (of the first TDD pattern). Based on the one or more SBFD configuration parameters not indicating the first period, the wireless device may set the first period to a default value. The default value may be the first TDD periodicity.The first period may be based on the second TDD pattern. For example, the first period may be the second TDD periodicity P2(of the second TDD pattern). Based on the one or more SBFD configurationparameters not indicating the first period, the wireless device may set the first period to the default value. The default value may be the second TDD periodicity.In some examples, the default value may be a summation of the first TDD periodicity Prand the second TDD periodicity P2.The one or more SBFD configuration parameters may further configure / indicate a second period. The second period may correspond to the second TDD pattern. The first period may correspond to the first TDD pattern. When the second period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the first TDD pattern.It is noted that a SBFD subband, SBUL and UL subband are used interchangeably throughout the specification. SBFD subband DL, SBDL, and DL subband are used interchangeably throughout the specification.In another example, when the second period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is configured within / correspond to the first TDD pattern and the second TDD pattern.In another example, when the first period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the second TDD pattern and the second TDD pattern.In another example, when the first period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the second TDD pattern.The one or more SBFD configuration parameters may indicate that a slot / symbol of a set of slots / symbols comprise of at least one SBFD slot / symbol. The one or more SBFD configuration parameters may indicate that a slot / symbol of the set of slots / symbols comprise of at least one non-SBFD slot / symbol. The plurality of slots may comprise the set of slots / symbols. A slot / symbols of the set of slots / symbols may be a DL slot (of the one or more DL slots) or a flexible slot (of the one or more flexible slots / symbols).An SBFD slot / symbol of the at least one SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols) configured for the SBFD operation. The SBFD slot / symbol may be within the SBFD time locations.A non-SBFD slot / symbol of the at least one non-SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots) or an ULslots / symbol (of the one or more UL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols). The non-SBFD symbol / slot may not be within the SBFD time locations.For the SBFD subband frequency locations, FIGs. 18A and 18B provide two examples (or configurations). As shown in FIG. 18A / 18B, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is one.A first example may correspond to a first (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at one side (e.g., a lowest frequency region or a highest frequency region of a carrier frequency range) of the first carrier. The first example may be referred to by a first type of SBFD operation. In the first type ofthe SBFD operation, the SBFD symbol / slot (e.g., a first type of SBFD symbol / slot) may correspond to / comprise a D-U or a U-D partitioning / configuration of frequency resources of the SBFD symbol / slot. The carrier may be the first carrier.A second example may correspond to a second (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at the middle part of the second carrier. The second example may be referred to by a second type of SBFD operation. In the second type of the SBFD operation, the SBFD symbol / slot (e.g., a second type of SBFD symbol / slot) may correspond to / comprise a D-U-D partitioning / configuration of frequency resources of the SBFD symbol. The carrier may be the second carrier.The D-U or the U-D or the D-U-D partitioning of the frequency resources of the SBFD symbol may provide / indicate examples of the SBFD subband frequency location(s). The one or more SBFD configuration parameters may indicate / configure the SBFD subband frequency location(s). The SBFD subband frequency location(s) may correspond to each SBFD symbol / slot within the SBFD subband time locations. In an example, the one or more SBFD configuration parameters may be received via a cell-specific signaling such as SIB, MIB or via a common search space or via a group-common DCI.The SBFD symbol / slot may comprise an UL subband and at least one DL subband. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations. The SBFD subband frequency locations may comprise frequency locations of UL subband and / or frequency locations of DL subband(s) (e.g., the at least one DL subband). The frequency locations of the UL subband may comprise at least one subband frequency-domain resources (e.g., PRBs or REs or subcarriers).The frequency locations of UL subband may comprise a first set of resource blocks (RBs). The first set of RBs may comprise a first set of resource elements (REs) or a first set of subcarriers. The first set of resource blocks may comprise / be UL subband frequency resources (subcarriers). The first set of resource blocks may correspond to at least a cell-specific UL subband and / or a UE-specific UL subband. The UL subband frequency resources for each SBFD symbol / slot within the SBFD subband time locations may be the first set of RBs.In the present disclosure, a set of RBs may interchangeably be used / referred to by "a set of PRBs" or "a set of subcarriers" or "a set of REs" or "a set of frequency resources".The frequency locations of DL subband(s) may comprise a second set of resource blocks (RBs). The second set of RBs may comprise a second set of resource elements (REs) or a second set of subcarrers. The second set of resource blocks may comprise / be DL subband frequency resources. The second set of resource blocks may correspond to at least cell-specific DL subband(s) and / or UE-specific DL subband(s). The DL subband(s) frequency resources may comprise / indicate (or be) the frequency locations of DL subband(s). The DL subband frequency resources for each SBFD symbol / slot within the SBFD subband time locations may be the second set of RBs.In one example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the second set of RBs. The wireless device may determine / derive a third set of resource blocks (RBs) corresponding to frequency locations of Guardband(s). The frequency locations of Guardband(s) are not within the UL subband or DL subband(s). The third set of RBs may comprise a third set of REs or a third set of subcarriers.In another example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the third set of RBs. The wireless device may determine / derive the second set of resource blocks (RBs), e.g., by excluding the first set of RBs and the third set of RBs from RBs of an active DL BWP (or the carrier).In yet another example, the one or more SBFD configuration parameters may configure / indicate the second set of RBs and the third set of RBs. The wireless device may determine / derive the first set of resource blocks (RBs), e.g., by excluding the second set of RBs and the third set of RBs from RBs of an active UL BWP (or the carrier). The active UL BWP may correspond to / associated with the active DL BWP.The frequency locations of Guardband(s)f or each SBFD symbol / slot within the SBFD subband time locations may be the third set of RBs.One or more RBs of the active RBs of the active DL BWP (or the carrier) may comprise a set of (e.g., sum, union) the first set of RBs, the second set of RBs, and the third set of RBs. The first set of RBs may belong to RBs of the active UL BWP.The second set of resource blocks / resource elements may comprise contiguous resource blocks / elements (e.g., for the D-U or U-D partitioning of the frequency resources) or non-contiguous blocks / elements (e.g., D-U-D partitioning of the frequency resources).The third set of resource blocks / elements may be contiguous, e.g., when only one Guardband (e.g., the D-U or U-D partitioning of the frequency resources) is configured in the SBFD symbol / slot. The set of third resource blocks / elements may be non-contiguous, e.g., when at least two Guardbands (e.g., D-U-D partitioning of the frequency resources) are configured in the SBFD symbol / slot.The one or more SBFD configuration parameters may indicate / configure Guardband(s) to reduce interference leakage between / among UL transmissions in the UL subband frequency resources in the SBFD symbol(s) / slot(s) (at a wireless device or a base station) and DL receptions in the DL subband frequency resources in the SBFD symbol(s) / slot(s) (at the wireless device or the base station).As also shown in FIG. 20, the UL subband frequency resources (e.g., the first set of RBs) within the active UL BWP may also be referred to by UL usable PRBs. The UL usable PRBs may comprise UL usable resource blocks / elements. The wireless device may determine the UL usable PRBs (or the first set of RBs) as an intersection between the UL subband frequency resources configured via the SBFD configuration and the active UL BWP in the SBFD symbol(s) / slot(s). In an example, the wireless device may determine the UL usable PRBs based on the one or more SBFD configuration (e.g., frequency location of a UL subband) and one or more guardbands that the wireless device is required for supporting a SBFD operation.The DL subband(s) frequency resources (e.g., the second set of RBs) within the active DL BWP may also be referred to by DL usable PRBs. The DL usable PRBs may comprise DL usable resource blocks / elements. The wireless device may determine the DL usable PRBs as an intersection between the DL subband(s) frequency resources and active DL BWP in the SBFD symbol(s) / slot(s).In some examples, the one or more SBFD configuration parameters may (explicitly or implicitly) configure / indicate the UL / DL usable PRBs within the active UL / DL BWP in the SBFD symbol(s) / slot(s).The wireless device may use the UL usable PRBs for UL transmissions (e.g., transmission of UL signals / channels) during the at least one SBFD symbol / slot. During the at least one SBFD symbol / slot, DL receptions outside of the DL usable PRBs may not be allowed, e.g., the wireless device may not use the UL usable PRBs and / or the Guardband(s) for DL receptions during the at least one SBFD symbol / slot.The wireless device may use the DL usable PRBs for DL receptions (e.g., reception of DL signals / channels) during at least one SBFD symbol / slot. UL transmissions outside the UL usable PRBs may not beallowed, e.g., the wireless device may not use the DL usable PRBs and / or the Guardband(s) for UL transmissions during at least one SBFD symbol / slot.For example, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is a first number. The one or more SBFD configuration parameters may configure / indicate the first number. When the first number is absent / missing from the one or more SBFD configuration parameters, the wireless device may consider a default value for the first number. The default value may be one.For example, the first number may be one. The first number may be more than one. The first number may be greater than or equal to one. In one example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol / slot as a DL symbol / slot or a flexible symbol / slot. In another example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol / slot as an UL symbol / slot.In an example, the wireless device may receive one or more cell-specific configuration parameters comprising time and frequency location of SBFD subbands supported within a TDD carrier. For example, the wireless device may receive the one or more cell-specific configuration parameters via a SI Bl, a SIBx, and / or RRC messages. In an example, the SBFD subband time locations may be configured within a period. For example, when the one or more common TDD configuration parameters are provided, the period may be same as a periodicity indicated by the one or more common TDD configuration parameters. In case, the one or more common TDD configuration comprises a first periodicity (e.g., comprised in the first TDD pattern, patternl) and a second periodicity (e.g., comprised in the second TDD pattern, pattern2), the period may be equal to a sum of the first periodicity and the second periodicity. In an example, when the one or more common TDD configuration parameters are not given for a TDD carrier, the wireless device may assume the period is determined based on one or more of: i) SSB periodicity of the TDD carrier, ii) a default value e.g., 20msec, iii) infinite i.e., no SBFD operation is allowed when the one or more common TDD configuration parameters are not configured / given / provided; iv) additional periodicity configuration parameter comprised in the one or more SBFD configuration parameters. For time domain configuration of the SBFD subbands (e.g., configuration of SBFD symbols), one or more parameters may be received by the wireless device. The one or more parameters may comprise one or more of: i) an index of a starting slot, an index of a starting symbol within the starting slot, an index of an ending slot, and an index of an ending symbol within the ending slot. One or more symbols between the starting symbol of the starting slot and the ending symbol of the ending slot may be considered as one or more SBFD symbols.In an example, a slot may comprise one or more SBFD symbols and one or more non-SBFD symbols. A second slot may comprise a plurality of SBFD symbols. A third slot may comprise a plurality of non-SBFD symbols. A SBFD symbol may be determined based on the time and frequency location of SBFD subbands. The SBFD subbands may comprise one or more downlink subbands and one uplink subband. Frequency locations of the SBFD subbands may be same across different slots of the TDD carrier. Frequency locations of the SBFD subbands may be indicated / configured based on a common RB grid (e.g., offset from a CRB #0, a first CRB). The frequency location of SBFD subbands may be configured via a cel l-speicfic configuration parameter (e.g., via SI Bl, SIBx, and / or RRC). The frequency location of SBFD subbands may comprise {a subcarrier spacing, a reference starting PRB that is an offset from a CRB#0} for each of one or more subcarrier spacings supported for the TDD carrier. The frequency location of the UL subband, for each subcarrier spacing (e.g., one of SCS-SpecificCarrierList} may comprise / indicate a starting RB and a bandwidth of the UL subband. The starting RB may be an offset from a CRB#0. The frequency location(s) ofthe one or more DL subbands, for the each subcarrier spacing (e.g., one of SCS-SpecificCarrierList), may comprise a starting RB and a bandwidth for each DL subband of the one or more DL subbands. The starting RB of the each DL subband may be an offset from the CRB#0.In an example, one or more RBs that are comprised in an uplink subband and also comprised in an active UL BWP may be referred as UL usable PRBs. One or more second RBs that are comprised in one or more downlink subbands and also comprised in an active DL BWP may be referred as DL useable PRBs. For example, the wireless device may determine the UL usable PRBs and / or the DL usable PRBs based on the time and frequency location of SBFD subbands of the TDD carrier. For the frequency locations of the SBFD subbands, frequency locations of the UL subband and the one or more DL subbands may be configured via cell-specific configuration parameters. The wireless device may determine guard-band(s), where each RB of the guard-band(s) may not be comprised in the UL subband and the one or more DL subband(s).For a wireless device that supports a SBFD operation (e.g., a SBFD-aware UE), the wireless device may transmit uplink signal(s) via the UL usable PRBs during one or more SBFD symbols, may receive downlink signal(s) via the DL usable PRBs during one or more second SBFD symbols, may not transmit uplink signal(s) outside of UL usable PRBs during one or more third SBFD symbols, may not receive downlink signal(s) outside of DL usable PRBs during one or more fourth SBFD symbols, except for receiving RSs for cross-link interference (e.g., a zeropower CSI-RS, a SRS, etc).During one or more SBFD symbols, a wireless device (a SBFD-aware UE) may determine a link direction (e.g., whether to receive downlink signal(s) or transmit uplink signal(s)) based on configured / scheduled transmission / reception. For example, if the wireless device receives a UL grant during the one or more SBFD symbols, the wireless device may transmit an uplink transmission during the one or more SBFD symbols.For frequency resource allocation Type 0 for PDSCH or PUSCH in a single slot by DCI based scheduling (without repetition or TBoMS), when an assigned RBG overlaps with the subband boundary, only the PRBs within DL usable PRBs may be considered to be valid for PDSCH reception and only the PRBs within UL usable PRBs are considered to be valid for PUSCH transmission. SBFD aware UE does not expect to be assigned with a RBG for PDSCH which is fully outside DL usable PRBs or a RBG for PUSCH which is fully outside UL usable PRBs.For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots (each transmission / reception within a slot has either all SBFD or all non-SBFD symbols) for an SBFD aware UE, the SBFD-aware UE may be configured with one of the configurations per each uplink BWP and / or each downlink BWP: i) Configuration 1 -- The transmissions / receptions are restricted to SBFD symbols only or non-SBFD symbols only; and ii) Configuration 2 -- The transmissions / receptions may be in SBFD symbols and non-SBFD symbols.For example, with the Configuration 1, the following behavior may be applied.A) if a DCI schedules a PUSCH without a repetition, the DCI may indicate resources during either one or more SBFD symbols or one or more non-SBFD symbols;B) if a DCI schedules a PUSCH with a repetition or a TB over multiple slot (TBoMS), each transmission of the repetition or TBoMS PUSCH may occur either during one or more SBFD symbols or non-SBFD symbols, where the wireless device may determine a symbol type (e.g., SBFD or non-SBFD) used for the each transmission based on a first (actual) PUSCH transmission indicated / scheduled by the DCI; The each transmission may follow the symbol type determined / indicated for the first PUSCH transmission.C) for a configured grant configuration (e.g., Type 1) configured via RRC without activation DCI, a higher layer may indicate which symbol type to use, or follow a symbol type of a first CG occasion;D) for a CG configuration (e.g., Type 2) configured via RRC with activation DCI, a symbol type may be determined based on the activation DCI. A first CG PUSCH activated by the activation DCI may determine the symbol type.For a frequency hopping, the wireless device may receive one or more RRC messages indicating a first list of frequency hopping offsets and a second list of frequency hopping offsets for an UL carrier of the TDD carrier. The first list of frequency hopping offsets may be used for UL signals / PUSCHs during one or more non-SBFD symbols. The second list of frequency hopping (FH) offsets may be used for UL signals / PUSCHs during one or more SBFD symbols. The wireless device may receive one or more RRC messages indicating a first FH offset for SBFD symbols and a second FH offset for non-SBFD symbols, for a type 1 CG PUSCH with Configuration 2. For example, for the type 1 CG PUSCH, a first parameter (e.g., frequencyHoppingOffset) indicates the second FH offset and a second parameter (e.g., frequencyHoppingOffset2] may indicate the first FH offset. For a type 2 CG PUSCH, a pusch-Config may comprise a first list (e.g.,frequencyHoppingOffsetLists) for the first list of FH offsets and a second list (e.g., frequencyHoppingOffsetLists2) for the second list of FH offsets. The wireless device may determine a FH offset based on a symbol type of a PUSCH. The number of configured FH offsets of FH offset list for SBFD symbols may be the same as the number of FH offsets of FH offset list for non-SBFD symbols.For frequency resource allocation Type 0 for PDSCH or PUSCH in a single slot by DCI based scheduling (without repetition or TBoMS), when an assigned RBG overlaps with the subband boundary, the number of PRBs for TBS determination is based on the assigned PRBs within DL usable PRBs only and assigned PRBs within UL usable PRBs only for PDSCH and PUSCH respectively.For UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots with Configuration 1, i) for PUSCH repetition type A with available slot counting, TBoMS and PUCCH repetitions, the wireless device may postpone transmissions in the invalid symbol type; ii) for CG PUSCH and SPS PDSCH, P / SP SRS, P / SP CSI-RS, P / SP PUCCH, SP-CSI on PUSCH, PUSCH repetition type A without available slot counting, multi-PUSCH / PDSCH scheduled by a single DCI, and PDSCH repetitions, transmissions / receptions in the invalid symbol type are dropped.For a CG PUSCH configuration without repetitions, if the transmission occasions are across SBFD symbols and non-SBFD symbols where each transmission occasion has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), for PUSCH repetition type-A across SBFD symbols and non-SBFD symbols in different slots where each repetition has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), and for multi-PUSCH scheduled by a single DCI across SBFD symbols and non-SBFD symbols, where each PUSCH within a slot has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), and for TBoMS across SBFD symbols and non-SBFD symbols in different slots, where each transmission within a slot has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), single resource configuration / indication for non-SBFD symbols and RB offset(s) configuration / indication / determination to determine frequency resource for SBFD symbols and the numbers of PRBs are the same for PUSCH transmissions in SBFD symbols and PUSCH transmissions in non-SBFD symbols.An information element (IE) AdvancedReceiver-MU-MIMO is used to provide a set of assistance information for R-ML (reduced complexity ML) receivers with enhanced inter-user interference suppression for MU-MIMO transmissions. AdvancedReceiver-MU-MIMO IE may comprise a parameter indicating a MCS table that is one of {QAM1024, QAM256, QAM 64, sparel}.A PDSCH-Config IE is used to configure the UE specific PDSCH parameters. The PDSCH-Config IE may be comprised in an UE-dedicated downlink BWP (e.g., BWP-DownlinkDedicated IE). If this IE is used for MBS CFR, the following fields may be absent: tci-StatesToAddModList, tci-StatesToReleaseList, zp-CSI-RS-ResourceToAddModList, minimumSchedulingOffsetKO, antennaPortsFieldPresenceDCI-1-2, aperiodicZP-CSI-RSResourceSetsToAddModListDCI- 1-2, aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2, dmrs-DownlinkForPDSCH MappingTypeA-DCI-1-2, dmrs- DownlinkForPDSCH-MappingTypeB-DCI-1-2, dmrs SeguencelnitializationDCI-1-2, harg-ProcessNumberSizeDCI-1-2, mcs-TableDCI-1-2, numberOfBitsForRV-DCI-1-2, pdsch-AggregationFactor, pdsch TimeDomainAllocationListDCI-1-2, prb-BundlingTypeDCI-1-2, prioritylndicatorDCI-1-2, rateMatchPatternGrouplDCI-1-2, rateMatchPatternGroup2DCI-l-2, resourceAllocationTypelGranularityDCI-1-2, vrb-ToPRB-lnterleaverDCI-1-2, referenceOfSLIVDCI-1-2, resourceAllocationDCI-1-2, dataScramblingldentityPDSCH2-rl6, repetitionSchemeConfig, pdsch-ConfigDCI-1-3.The PDSCH-Config IE may comprise a first parameter (mcs-Table) indicating a MCS table used for receiving UE specific PDSCHs via an active downlink BWP. The first parameter may indicate one of {QAM256, QAM64LowSE}. The first parameter may indicate which MCS table the wireless device needs to use for PDSCH for DCI formats l_0, 1_1 and 1_3. If any MCS table is not explicitly indicated (e.g., the first parameter, a second parameter of a second MCS table, a third parameter of a third MCS table in the PDSCH-Config IE), the wireless device may apply the value 64QAM (e.g., use 64QAM based MCS table). If the second parameter (e.g., a field mcs-Table-rl7) is present, in the PDSCH-Config IE, for DCI formats 1_1 and 1_3, the network / base station may not configure the first parameter (e.g., the field mcs-Table (without suffix)). For an (e)RedCap wireless device, the 256QAM MCS table for PDSCH is only supported if the wireless device indicates support of 256QAM for PDSCH. The second parameter (the field of mcs-Table-rl7) of the second MCS table may indicate a QAM1024. The wireless device may use the second MCS table that is determined based on the QAM1024 based on the second parameter indicating the QAM1024. The third parameter (e.g., a field of mcs-TableDCI-1-2) of the third MCS table may indicate which MCS table the wireless device needs to use for PDSCH for DCI format 1_2. If any MCS table is not explicitly indicated (e.g., the first parameter, the second parameter of the second MCS table, the third parameter of the third MCS table in the PDSCH-Config IE), the wireless device may apply the value 64QAM. If the field mcs-TableDCI-1-2-rl7 is present, the network / base station may not configure the field mcs-TableDCI-l-2-rl6. For an (e)RedCap wireless device, the 256QAM MCS table for PDSCH is only supported if the wireless device indicates support of 256QAM for PDSCH. The third parameter, based on the mcs-TableDCI-l-2-rl6, may indicate one of {QAM256, QAM64lowSE}. The third parameter, based on the mcs-TableDCI-l-2-rl7, may indicate QAM1024. Based on QAM value (e.g., one of QAM64, QAM64lowSE, QAM256, QAM1024}, the wireless device may determine a MCS table for receiving a PDSCH, wherein the QAM value is indicated for the PDSCH. For example, if a DCI schedules the PDSCH, and the DCI is based on a DCI format 1-2, and the third parameter is present in the PDSCH-Config IE, the wireless device may determine the MCS table for the PDSCH based on the third parameter. Otherwise, the wireless device may determine the MCS table based on the either the second parameter or the first parameter that is present in the PDSCH-Config IE. Otherwise, the wireless device may determine the MCS table based on the QAM value as 64QAM.A PUSCH-Config IE may be used to configure the UE specific PUSCH parameters applicable to a particular BWP. The PUSCH-Config IE may be comprised in a UE-dedicated uplink BWP (e.g., BWP-UplinkDedicated IE).The PUSCH-Config may comprise a first parameter (mcs-Table) indicating a MCS table used for receiving UE specific PUSCHs via an active uplink BWP. The first parameter may indicate one of {QAM256, QAM64LowSE}. The first parameter may indicate which MCS table the wireless device needs to use for PUSCH without transform precoder. The PUSCH-Config may comprise a second parameter (mcs-TableTransformPrecoder) indicating a MCS table used for receiving UE specific PUSCHs via an active uplink BWP. If the parameter (e.g., the field mcs-Table) is absent, the wireless device may apply the value 64QAM for determining a MCS table for the PUSCH without transform precoder. The PUSCH-Config may comprise a fourth parameter (a field mcs-TableTransformPrecoderDCI-0-2), wherein the third parameter or the fourth parameter may be used for a PUSCH scheduled via a DCI format 0_2. The first parameter (e.g., the field mcs-Table) may apply to DCI formats 0_0, 0_l and 0_3, and a third parameter (e.g., field mcs-TableDCI-0-2) may apply to DCI format 0_2. The wireless device may determine a MCS table for a PUSCH based on a DCI format scheduling the PUSCH without transform precoder, where a value of the first parameter is used for the determining based on the DCI format is one of DCI Formats 0_0, 0_l and 0_3, and a value of the third parameter is used for the determining based on the DCI format is DCI format 0_2. The second parameter (e.g., the field mcs-TableTransformPrecoder) may apply to DCI formats 0_0, 0_l and 0_3, and the fourth parameter (e.g., field mcs-TableTransformPrecoderDCI-0-2) may apply to DCI format 0_2. The wireless device may determine a MCS table for a PUSCH based on a DCI format scheduling the PUSCH with transform precoder, where a value of the second parameter is used for the determining based on the DCI format is one of DCI Formats 0_0, 0_l and 0_3, and a value of the fourth parameter is used for the determining based on the DCI format is DCI format 0_2. The first parameter may indicate one of {QAM256, QAM64LowSE}. The second parameter may indicate one of {QAM256, QAM64LowSE}. The third parameter may indicate one of {QAM256, QAM64LowSE}. The fourth parameter may indicate one of {QAM256, QAM64LowSE}. The PUSCH-Config may comprise a field transformPrecoder, where the field indicates a UE-specific selection of transform precoder for PUSCH. When the field is absent, the wireless device may apply a value of the field msg3-transformPrecoder from rach-ConfigCommon included directly within an uplink BWP configuration (i.e., not included in additionalRACH-ConfigList).In an example, the wireless device may receive one or more RRC messages indicating a SPS configuration (e.g., SPS-Config IE). The SPS-Config IE may comprise parameters indicating a periodicity of the SPS configuration, a MCS table (a field mcs-Table) used for SPS PDSCH(s) based on the SPS configuration, and / or a number of HARQ processes. The mcs-Table may indicate a value of QAM64LowSE. The mcs-Table may indicate a MCS table the wireless device needs to use for downlink semi-persistent-scheduling (SPS). If the mcs-Table is present in the SPS configuration, the wireless device needs to use the MCS table of low-SE (spectral efficiency) 64QAM table indicated in Table 5.1.3.1-3 ofTS 38.214. If this field is absent and field mcs-table in the PDSCH-Config is set to 'QAM256' and the activating DCI is of format 1_1, the wireless device applies the 256QAM table indicated in Table 5.1.3.1-2 of TS 38.214 If this field is absent and the field mcs-Table-rl7\n the PDSCH-Config is set to 'QAM1024' and the activating DCI is format 1_1, the wireless device may apply the 1024QAM table indicated in Table 5.1.3.1-4 of TS 38.214. Otherwise, the wireless device may apply the non-low-SE 64QAM table indicated inTable 5.1.3.1-1 of TS 38.214. The PDSCH-Config is for the active downlink BWP where the SPS configuration is applied / activated / performed.In an example, the wireless device may receive one or more RRC messages indicating a ConfiguredGrant configuration (e.g., ConfiguredGrantConfig IE). The ConfiguredGrantConfig IE may comprise parameters indicating a periodicity of the Configured Grant (CG) configuration. The ConfiguredGrantConfig IE may comprise a first parameter (a field mcs-Table) and / or a second parameter (a field mcs-TableTransformPrecoder). The first parameter (the field mcs-Table) may indicates a MCS table the wireless device needs to use for a PUSCH without transform precoding. If the field is absent the wireless device may apply the value QAM64. The second parameter (the field mcs-TableTransformPrecoder) may indicate a MCS table the wireless device needs to use for a PUSCH with transform precoding. If the field is absent the wireless device may apply the value QAM64.In an example, PUSCH transmission(s) may be dynamically scheduled by an UL grant in a DCI, or the transmission may correspond to a configured grant Type 1 or Type 2. The configured grant Type 1 PUSCH transmission may be semi-statical ly configured to operate upon the reception of higher layer parameter of ConfiguredGrantConfig including rrc-ConfiguredUplinkGrant without the detection of an UL grant in a DCI.For the PUSCH transmission corresponding to a Type 1 configured grant or a Type 2 configured grant activated by DCI format 0_0 or 0_l, the parameters applied for the transmission are provided by ConfiguredGrantConfig except for dataScramblingldentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI OnPUSCH, which are provided by pusch-Config of an active BWP, where PUSCH transmissions is via / occurring. A configured grant PUSCH may be transmitted with at most 4 layers. For the PUSCH transmission corresponding to a Type 2 configured grant activated by DCI format 0_2, the parameters applied for the transmission are provided by ConfiguredGrantConfig except for dataScramblingldentityPUSCH, txConfig, codebookSubsetDCI-0-2, maxRankDCI-0-2, scaling of UCI-OnPUSCH, resourceAllocationTypelGranularityDCI-0-2 provided by pusch-Config. If the wireless device is provided with transformPrecoder in ConfiguredGrantConfig, the wireless device may apply the higher layer parameter tppi2BPSK, if provided in pusch-Configtor the PUSCH transmission corresponding to a configured grant.For the PUSCH retransmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI=1 (e.g., a DCI via the PDCCH indicating a NDI value as 1), the parameters in pusch-Config may be applied for the PUSCH transmission except for pO-NominalWithoutGrant, pO-PUSCH-Alpha, powerControlLoopToUse, pathlossReferencelndex mcs-Table, mcs- TableTransformPrecoder and transformPrecoder. For a wireless device configured with two uplinks in a serving cell, PUSCH retransmission for a transport block (TB) on the serving cell may not be expected to be on a different uplink than the uplink used for the PUSCH initial transmission of that TB (e.g., SUL for the transmission while the UL for the initial transmission or vice versa).The wireless device may, upon detection of a PDCCH with a configured DCI format 0_0, 0_l, 0_2 or 0_3, transmit the corresponding PUSCH as indicated by that DCI unless the wireless device does not generate a transport block. Upon detection of a DCI format 0_l or 0_2 with 'UL-SCH indicator' set to 'O' and with a non-zero 'CSI request' where the associated reportQuantity in CSI-ReportConfig set to 'none' for all CSI report(s) triggered by 'CSI reguest' in this DCI format 0_l or 0_2, the wireless device may ignore all fields in this DCI except the 'CSI request' and the wireless device may not transmit the corresponding PUSCH as indicated by this DCI format 0_l or 0_2. Upon detection of a DCI format 0_3 with 'UL-SCH indicator' set to 'O' and with a non-zero 'CSI request' where the associated reportQuantity in CSI-ReportConfig set to 'none' for all CSI report(s) triggered by 'CSI reguest' in thisDCI format 0_3, the wireless device may ignore all fields for the scheduled cell with the smallest serving cell index in this DCI except the 'CSI request' and the wireless device may not transmit the corresponding PUSCH on the serving cell with the smallest serving cell index as indicated by this DCI format 0_3.For PUSCH scheduled by DCI format 0_0 on a cell, the wireless device may transmit PUSCH according to the spatial relation, if applicable, corresponding to the dedicated PUCCH resource with the lowest ID within the active UL BWP of the cell. If the dedicated PUCCH resource with the lowest ID within the active UL BWP of the cell corresponds to two spatial relations, the wireless device may transmit the PUSCH according to the spatial relation with the lower ID.For PUSCH scheduled by DCI format 0_0 on a cell and if the higher layer parameter enableDefaultBeamPLForPUSCHO-O is set 'enabled', the wireless device is configured with PUCCH resources on the active UL BWP where all the PUCCH resource(s) are not configured with any spatial relation and the wireless device is in RRC connected mode, the wireless device may transmit PUSCH according to the spatial relation, if applicable, with a reference to the RS configured with qcl-Type set to 'typeD' corresponding to the QCL assumption of the CORESET with the lowest ID on the active DL BWP of the cell in case CORESET(s) are configured on the cell. If the CORESET is indicated with two TCI states, sfnSchemePdcch is configured and the wireless device supports sfn-DefaultUL-BeamSetup-rl7, the wireless device may use the first TCI state as the QCL assumption. For uplink, 16 HARQ processes per cell are supported by the wireless device, or subject to wireless device capability, a maximum of 32 HARQ processes per cell. The number of processes the wireless device may assume will at most be used for the uplink is configured to the UE for each cell separately by higher layer parameter nrofHARQ-ProcessesForPUSCH, or nrofHARQ-ProcessesForPUSCH, and when no configuration is provided the wireless device may assume a default number of 16 processes.When the wireless device is configured with the higher layer parameter txConfig set to 'Noncodebook', the wireless device is configured with at least one SRS resource. Each of the indicated one or two SRI(s) in slot n is associated with the most recent transmission of SRS resource of associated SRS resource set identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with higher layer parameter usage in SRSResourceSet set to 'Noncodebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets.In an example, when a wireless device is configured with the higher layer parameter txConfig set to 'Noncodebook' and not configured / enabled with an uplink subband in a serving cell, the wireless device is configured with at least one SRS resource. Each of the indicated one or two SRI(s) in slot n is associated with the most recent transmission of SRS resource of associated SRS resource set identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with higher layer parameter usage in SRSResourceSet set to 'Noncodebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets. When a wireless device is configured with the higher layer parameter txConfig set to 'Noncodebook' and configured / enabled with an uplink subband in a serving cell, the wireless device is configured with at least one SRS resource. For an SRI in slot n is associated with the most recent transmission ofSRS resource of associated a SRS resource set, where the SRS resource is prior to the PDCCH carrying the SRI, and the SRS resource set is identified by a symbol type of a PUSCH scheduled by the PDCCH.Resource allocation in time domainWhen the wireless device is scheduled to transmit a transport block and no CSI report by a DCI or by a RAR UL grant or fall backRAR UL grant, or the UE is scheduled to transmit a transport block and a CSI report(s) on PUSCH by a DCI, the 'Time domain resource assignment' field value m for the scheduled PUSCH on the serving cell of the DCI or the PUSCH time resource allocation field value m of the RAR UL grant or of the fal I backRAR UL grant provides a row index m + 1 to a resource allocation table. The wireless device may determine the resource allocation table based on a time domain resource allocation rule. The indexed row defines the slot offset K2, the start and length indicator SLIV, or directly the start symbol S and the allocation length L, the PUSCH mapping type, the number of slots used for TBS determination (if numberOfSIotsTBoMS is present in the resource allocation table), and the number of repetitions (if numberOfRepetitions is present in the resource allocation table) to be applied in the PUSCH transmission.For example, the time domain resource allocation rule comprises one or more of: i) determining to use a default A table based on a PUSCH is scheduled by a MAC RAR (e.g., RAR MAC CE comprises UL grant for the PUSCH, the PUSCH is a Msg3 PUSCH)) or by a MAC fall backRAR or is for a MsgA PUSCH, and a pusch-ConfigCommon not comprising / indicating a TimeDomainAllocationList. If pusch-TimeDomainAllocationList is present / comprised in a pusch-Config, the wireless device may determine to use the pusch-TimeDomainAllocationList for a PUSCH scheduled by one or more DCI formats via a USS. For a PUSCH scheduled via a CSS, the default A table may be used. If pusch-TimeDomainAllocationListDCI-0-1 is configured or present or comprised in the pusch-Config and the PUSCH is scheduled by a DCI format 0_l or 0_3, the wireless device determines to use pusch-TimeDomainAllocationListDCI-O-1. If pusch-TimeDomainAllocationListDCI-0-2 is configured or present or comprised in the pusch-Config and the PUSCH is scheduled by a DCI format 0_2, the wireless device determines to use pusch-TimeDomainAllocationListDCI-0-2. If pusch-TimeDomainAllocationListForMultiPUSCH is configured or present or comprised in the pusch-Config, and the PUSCH is scheduled by a DCI format scheduling one or more PUSCHs (multiple PUSCHs), the wireless device determines to use the pusch-TimeDomainAllocationListForMultiPUSCH. The field pusch-TimeDomainAllocationList applies to DCI format 0_0, or DCI formats 0_l and 0_3 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured. The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-rl6 or the pusch-TimeDomainAllocationListDCI-0-rl6 or the pusch-TimeDomainAllocationListForMultiPUSCH-rl6.For a PUSCH scheduled by RAR UL grant, or for a PUSCH scheduled by fall backRAR UL grant, or for a PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the wireless device may consider the transform precoding either 'enabled' or 'disabled' according to the higher layer configured parameter msg3-transformPrecoder in the pusch-Config. For a MsgA PUSCH, the wireless device may consider the transform precoding either 'enabled' or 'disabled' according to the higher layer configured parameter msgA-TransformPrecoder. If higher layer parameter msgA-TransformPrecoder is not configured, the wireless device may consider the transform precoding either 'enabled' or 'disabled' according to the higher layer configured parameter msg3-transformPrecoder.For PUSCH transmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI=1, C-RNTI, or MCS-CRNTI or SP-CSI-RNTI: a) If the DCI with the scheduling grant was received with DCI format 0_0, the wireless device may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoder.a-1) if the DCI with the scheduling grant was not received with DCI format 0_0; and b-1) if the DCI with the scheduling grant was received with DCI format 0_l or 0_2 with CRC scrambled by CRNTI, MCS-RNTI, or CS-RNTI with NDI=1 and if the wireless device is configured with a higher layer parameter [dynamicTransformPrecoderlndicationDCI-0-1] in pusch-Config for DCI format 0_l or [dynamicTransformPrecoderlndicationDCI-0-2] in pusch-Config for DCI format 0_2 and the higher layer parameter is set to 'enabled',a-1-1) the wireless device may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the Transform precoder indicator field in the DCI with the scheduling grant;a-1-2) for pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config, the wireless device may, for all PUSCH transmissions, consider the transform precoding either enabled or disabled according to Transform precoder indicator field in the DCI format 0_l with the scheduling grant;a-1-3) If resourceAllocation in pusch-Config for DCI format 0_l or resourceAllocationDCI-0-2 in pusch-Config for DCI format 0_2 is set to resourceAllocationTypeO, or if the resource allocation is set to resource allocation type 0 according to the DCI configuration, or if dmrs-Type in DMRS-UplinkConfig is set to 'type 2' for this PUSCH transmission, the wireless device does not expect that the Transform precoder indicator field in the DCI with the scheduling grant indicates that transform precoding is enabled.a-1-4) if the wireless device is configured with the higher layer parameter dmrs-TypeEnh in DMRS-UplinkConfig, and if the scheduling grant indicates that transform precoding is enabled for the scheduled PUSCH transmission, the wireless device ignores the higher layer parameters dmrs-TypeEnh in DMRS-UplinkConfig, if configured, for the DM-RS transmission of the scheduled PUSCH transmission.a-2) Otherwise (of b-1) condition)a-2-1) If the wireless device is configured with the higher layer parameter transformPrecoder in pusch-Config, the wireless device may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter;a-2-2) If the wireless device is not configured with the higher layer parameter transformPrecoder in pusch-Config, the wireless device may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoder.For PUSCH transmission with a configured grant, a) If the wireless device is configured with the higher layer parameter transformPrecoder in configuredGrantConfig, the wireless device may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter; b) If the wireless device is not configured with the higher layer parameter transformPrecoder in configuredGrantConfig, the wireless device may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoderTo determine the modulation order, target code rate, redundancy version and transport block size for the physical uplink shared channel, the wireless device may firsta) read the 5-bit modulation and coding scheme field in the DCI scheduling PUSCH or provided in a DCI activating a configured grant Type 2 PUSCH, or as provided by mcsAndTBS comprised in ConfiguredGrantConfig for a configured grant Type 1 PUSCH to determine the modulation order and target code rate (R); and b) read redundancy version field (rv) in the DCI to determine the redundancy version for PUSCH scheduled by DCI, or determine the redundancy version or configured grant Type 1 and Type 2 PUSCH; and seconda) use the number of layers, the total number of allocated PRBs to determine the transport block size.When the wireless device is scheduled with multiple PUSCHs on a serving cell by a DCI, the bits of rv field and NDI field, respectively, in the DCI are one to one mapped to the scheduled PUSCH(s) indicated by the TDRA information field with the corresponding transport block(s) in the scheduled order where the LSB bits of the rv field and NDI field, respectively, correspond to the last scheduled PUSCH indicated by the TDRA information field.In the specification QAM and qam are interchangeably used. QAM256 is equal to qam256, QAM64 is equal to qam64.For a PUSCH scheduled by RAR UL grant or for a PUSCH scheduled by a fal I backRAR UL grant or for a MsgA PUSCH transmission, or for a PUSCH scheduled by a DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or for a PUSCH scheduled by a DCI format 0_l or DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, SP-CSI-RNTI, or for a PUSCH scheduled by a DCI format 0_3 with CRC scrambled by C-RNTI, MCS-C-RNTI, or for a PUSCH with configured grant using CS-RNTI, andi) if transform precoding is disabled for this PUSCH transmission:a) if mcs-TableDCI-0-2 in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use IMCS and Table A (QAM256-MCS-Table) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;b) elseif the wireless device is not configured with MCS-C-RNTI, mcs-TableDCI-0-2 in pusch-Config is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH by a PDCCH with DCI format 0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use IMCS and Table B (QAM64-LowSE) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;c) elseif mcs-Table in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0_l or 0_3with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use IMCS and Table A to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;d) elseif the wireless device is not configured with MCS-C-RNTI, mcs-Table in pusch-Config is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with a DCI format other than DCI format 0_2 in a UE-specific search space with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use IMCS and Table B (QAM64-LowSE) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;e) elseif the wireless device is configured with MCS-C-RNTI, and the PUSCH is scheduled by a PDCCH with CRC scrambled by MCS-C-RNTI, the wireless device may use IMCS and Table B (QAM64-LowSE) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;f) elseif mcs-Table in configuredGrantConfig is set to 'qam256',f-1) if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or if PUSCH is transmitted with configured grant, the wireless device may use IMCS and Table A to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;g) elseif mcs-Table in configuredGrantConfig is set to 'qam64LowSE;g-1) if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or if PUSCH is transmitted with configured grant, the wireless device may use lMcs and Table B (QAM64-LowSE) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;h) elseif for a MsgA PUSCH transmission, the wireless device may use higher layer parameter msgA-MCS for lMcs and a default Table to determine the Target code rate (R) used in the physical uplink shared channel;j) elseif the wireless device requests repetition of PUSCH scheduled by RAR UL grant, when transmitting PUSCH scheduled by RAR UL grant, the 2 LSBs of the MCS information field of the RAR UL grant provide a codepoint to determine the MCS index lMcs according to Table C, based on whether or not the higher layer parameter mcs-Msg3-Repetitions is configured. The wireless device may use the determined lMcs and the default Table to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;k) elseif the wireless device requests repetition of PUSCH scheduled by RAR UL grant, when transmitting PUSCH scheduled by DCI format 0_0 with CRC scrambled by the TC-RNTI, the 3 LSBs of the MCS information field of the DCI format 0_0 with CRC scrambled by the TC-RNTI provide a codepoint to determine the MCS index lMcs according to Table D, based on whether or not the higher layer parameter mcs-Msg3-Repetitions is configured. The wireless device may use the determined lMcs and the default Table to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;ii) if transform precoding is enabled for this PUSCH transmission:a) if mcs-TableTransformPrecoderDCI-0-2 in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use IMCS and Table A (QAM256-MCS-Table) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;b) elseif the UE is not configured with MCS-C-RNTI, mcs-TableTransformPrecoderDCI-0-2 in pusch-Config is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with DCI format 0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use lMcs and UL-Table B (QAM64-LowSE for UL) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;c) elseif mcs-TableTransformPrecoder in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0_l or 0_3 with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may use IMCS and Table A (QAM256-MCS-Table) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;d) elseif the wireless device is not configured with MCS-C-RNTI, mcs-TableTransformPrecoder in pusch-Config is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with a DCI format other than DCI format 0_2 in a UE-specific search space with CRC scrambled by C-RNTI or SP-CSI-RNTI, the wireless device may useIMCS and UL-Table B (QAM64-LowSE for UL)to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;e) elseif the UE is configured with MCS-C-RNTI, and the PUSCH is scheduled by a PDCCH with CRC scrambled by MCS-C-RNTI, the wireless device may use lMcs and UL-Table B (QAM64-LowSE for UL) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;f) elseif mcs-TableTransformPrecoder in configuredGrantConfig is set to 'qam256', f-1) if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or if PUSCH is transmitted with configured grant, the wireless device may use lMcs and Table A (QAM256-MCS-Table) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;g) elseif mcs-TableTransformPrecoder in configuredGrantConfig is set to 'qam64LowSE';g-1) if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or if PUSCH is transmitted with configured grant, the wireless device may use lMcs and UL-Table B (QAM64-LowSE for UL) to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;h) elseif for a MsgA PUSCH transmission, the wireless device may use higher layer parameter MsgA-MCS for lMcs and UL default Table to determine the Target code rate (R) used in the physical uplink shared channel;j) elseif the wireless device requests repetition of PUSCH scheduled by RAR UL grant, when transmitting PUSCH scheduled by RAR UL grant, the 2 LSBs of the MCS information field of the RAR UL grant provide a codepoint to determine the MCS index lMcs according to Table C, based on whether or not the higher layer parameter mcs-Msg3-Repetitions is configured. The UE shall use the determined lMcs and UL default Table to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel;k) elseif the wireless device requests repetition of PUSCH scheduled by RAR UL grant, when transmitting PUSCH scheduled by DCI format 0_0 with CRC scrambled by the TC-RNTI, the 3 LSBs of the MCS information field of the DCI format 0_0 with CRC scrambled by the TC-RNTI provide a codepoint to determine the MCS index lMcs according to Table D, based on whether or not the higher layer parameter mcs-Msg3-Repetitions is configured. The UE shall use the determined lMcs and UL default Table to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channell) else, the wireless device may use lMcs and UL default Table to determine the modulation order (Qm) and Target code rate (R) used in the physical uplink shared channel. For a Msg3 PUSCH (re)transmission, the UE shall use g=2 for determining modulation order (Qm) in UL default Table.Default Table (used for both DL and UL)MCS Index Modulation Order „, „ „ _ _ Spectral Target code Rate R x

[1024] iMCS Qin efficiency 0 2 120 0.2344 1 2 157 0.3066 2 2 193 0.3770 3 2 251 0.4902 4 2 308 0.6016 5 2 379 0.7402 6 2 449 0.8770 7 2 526 1.0273 8 2 602 1.1758 9 2 679 1.3262 10 4 340 1.3281 11 4 378 1.4766 12 4 434 1.6953 13 4 490 1.9141 14 4 553 2.1602 15 4 616 2.4063 16 4 658 2.5703 17 6 438 2.5664 18 6 466 2.7305 19 6 517 3.0293 20 6 567 3.3223 21 6 616 3.6094 22 6 666 3.9023 23 6 719 4.2129 24 6 772 4.5234 25 6 822 4.8164 26 6 873 5.1152 27 6 910 5.3320 28 6 948 5.5547 29 2 reservec 30 4 reserved31 6 reservedTable A (256QAM-MCS-Table): used for both DL and ULMCS Index Modulation OrderTarget code Rate R x

[1024] ^GGtra' IMCS Qm efficiency 0 2 120 0.2344 1 2 193 0.3770 2 2 308 0.6016 3 2 449 0.8770 4 2 602 1.1758 5 4 378 1.4766 6 4 434 1.6953 7 4 490 1.9141 8 4 553 2.1602 9 4 616 2.4063 10 4 658 2.5703 11 6 466 2.7305 12 6 517 3.0293 13 6 567 3.3223 14 6 616 3.6094 15 6 666 3.9023 16 6 719 4.2129 17 6 772 4.5234 18 6 822 4.8164 19 6 873 5.1152 20 8 682.5 5.3320 21 8 711 5.5547 22 8 754 5.8906 23 8 797 6.2266 24 8 841 6.5703 25 8 885 6.9141 26 8 916.5 7.1602 27 8 948 7.4063 28 2 reservec 29 4 reserved 30 6 reserved31 8 reservedTable B (64QAM-LowSE): used for both DL and ULMCS Index Modulation Order „, „ „.. _ _ Spectral, „ Target code Rate R x [1024. IMCS Qm efficiency 0 2 30 0.0586 1 2 40 0.0781 2 2 50 0.0977 3 2 64 0.1250 4 2 78 0.1523 5 2 99 0.1934 6 2 120 0.2344 7 2 157 0.3066 8 2 193 0.3770 9 2 251 0.4902 10 2 308 0.6016 11 2 379 0.7402 12 2 449 0.8770 13 2 526 1.0273 14 2 602 1.1758 15 4 340 1.3281 16 4 378 1.4766 17 4 434 1.6953 18 4 490 1.9141 19 4 553 2.1602 20 4 616 2.4063 21 6 438 2.5664 22 6 466 2.7305 23 6 517 3.0293 24 6 567 3.3223 25 6 616 3.6094 26 6 666 3.9023 27 6 719 4.2129 28 6 772 4.5234 29 2 reserved 30 4 reserved31 6 reservedUL Default TableMCS Index Modulation Order Spectral Target code Rate R x 1024IMCS II Qm efficiency 0 q 240 / q 0.2344 1 q 314 / q 0.3066 2 2 193 0.3770 3 2 251 0.4902 4 2 308 0.6016 5 2 379 0.7402 6 2 449 0.8770 7 2 526 1.0273 8 2 602 1.1758 9 2 679 1.3262 10 4 340 1.3281 11 4 378 1.4766 12 4 434 1.6953 13 4 490 1.9141 14 4 553 2.1602 15 4 616 2.4063 16 4 658 2.5703 17 6 466 2.7305 18 6 517 3.0293 19 6 567 3.3223 20 6 616 3.6094 21 6 666 3.9023 22 6 719 4.2129 23 6 772 4.5234 24 6 822 4.8164 25 6 873 5.1152 26 6 910 5.3320 27 6 948 5.5547 28 q reserved29 2 reserved30 4 reserved31 6 reserved U L-Table B (QAM64-LowSE for UL)MCS Index Modulation Order Spectral Target code Rate R x 1024....IMCS Qm efficiency 0 q 60 / q 0.05861 q 80 / q 0.07812 q 100 / q 0.09773 q 128 / q 0.12504 q 156 / q 0.15235 q 198 / q 0.19346 2 120 0.23447 2 157 0.30668 2 193 0.37709 2 251 0.490210 2 308 0.601611 2 379 0.740212 2 449 0.877013 2 526 1.027314 2 602 1.175815 2 679 1.326216 4 378 1.476617 4 434 1.695318 4 490 1.914119 4 553 2.160220 4 616 2.406321 4 658 2.570322 4 699 2.730523 4 772 3.015624 6 567 3.322325 6 616 3.609426 6 666 3.902327 6 772 4.523428 q reserved29 2 reserved30 4 reserved31 6 reservedTable Cmcs-Msg3-Repetitions is configured mcs-Msg3-Repetitions is not configured Codepoint IMCS Codepoint IMCS First value of mcs-Msg3- 00 00 0 RepetitionsSecond value of mcs- 01 01 1 Msg3-RepetitionsThird value of mcs-Msg3- 10 10 2 RepetitionsFourth value of mcs- 11 11 3Msg3-RepetitionsTable Dmcs-Msg3-Repetitions is configured mcs-Msg3-Repetitions is not configured Codepoint IMCS Codepoint IMCS First value of mcs-Msg3- 000 000 0 RepetitionsSecond value of mcs- 001 001 1 Msg3-RepetitionsThird value of mcs-Msg3- 010 010 2 RepetitionsFourth value of mcs- Oil Oil 3 Msg3-RepetitionsFifth value of mcs-Msg3- 100 100 4 RepetitionsSixth value of mcs-Msg3- 101 101 5 RepetitionsSeventh value of mcs- 110 110 6 Msg3-RepetitionsEighth value of mcs-Msg3- 111 111 7RepetitionsFor eight antenna ports PUSCH transmission, when the number of PUSCH transmission layers is greater than 4, two codewords are transmitted. If the higher layer parameter maxRank or maxMlMO-Layers in PUSCH-config is greater than 4, then one of the two transport blocks is disabled by DCI format 0_l if lMcs= 26 and if rvid = 1 for the corresponding transport block. If both transport blocks are enabled, transport block 1 and 2 are mapped to codeword 0 and 1 respectively. If only one transport block is enabled, then the enabled transport block is always mapped to the first codeword.For a PUSCH scheduled by RAR UL grant or for a PUSCH scheduled by fal I backRAR UL grant or for a PUSCH scheduled by a DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or for a PUSCH scheduled by a DCI format 0_l or DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or for a PUSCH scheduled by a DCI format 0_3 with CRC scrambled by C-RNTI, MCS-C-RNTI, or for a PUSCH transmission with configured grant, or for a MsgA PUSCH transmission;I) If and transform precoding is disabled and Table A is used, or and transform precoding is disabled and a table other than A is used, or and transform precoding is enabled, the wireless device may first determine the TBS based on a number of REs scheduled and overhead.For a PUSCH scheduled by fal I backRAR UL grant, UE assumes the TB size determined by the UL grant in the fal IbackRAR shall be the same as the TB size used in the corresponding MsgA PUSCH transmission.II) else if and transform precoding is disabled and Table 5.1.3.1-2 is used, or and transform precoding is enabled, the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using. If there is no PDCCH for the same transport block using, and if the initial PUSCH for the same transport block is scheduled by a RAR UL grant, the TBS shall be determined from the RAR UL grant. If there is no PDCCH for the same transport block using, and if the initial PUSCH for the same transport block is transmitted with configured grant, the TBS shall be determined from configuredGrantConfig for a configured grant Type 1 PUSCH. Alternatively, the TBS may be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH.III) else the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using. If there is no PDCCH for the same transport block using, and if the initial PUSCH for the same transport block is scheduled by a RAR UL grant, the TBS shall be determined from the RAR UL grant. If there is no PDCCH for the same transport block using, and if the initial PUSCH for the same transport block is transmitted with configured grant, the TBS may be determined from configuredGrantConfig for a configured grant Type 1 PUSCH. Alternatively, the TBS may be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH.Similar procedure occurs for a downlink PDSCH reception and its MCS and TBS determination. In the present disclosure, a temporary cell-RNTI (TC-RNTI) may refer an identifier carried via a MAC payload during a random access procedure. A size of the TC-RNTI is 16 bits. A random access response corresponding to a PRACH transmission with a preamble may comprise the MAC payload comprising the temporary C-RNTI (TC-RNTI) during an initial access procedure. Once a wireless device is received / configured with a C-RNTI, a RAR for the wireless device may not comprise a TC-RNTI. Based on whether a contention resolution is needed or not, a RAR for a preamble may comprise a TC-RNTI or not. A TC-RNTI may be referred as a temporary C-RNTI, temporary_C-RNTI, and / or the like.In the present disclosure, a RACH resource may be referred as a PRACH resource, a RACH resource, a RO, a PRACH occasion, a rach resource, a RACH RO, a RACH occasion and / or the like. A set of RACH resources may be referred as a set of ROs, a set of rach resources, a set of PRACH occasions, a list of ROs, a list of RACH resources, a group of ROs, a group of RACH resources, ROs based on a prach-Configurationlndex, ROs based on a rach-Config, a group of preambles, a set of preambles, one or more ROs, one or more preambles, a plurality of ROs, a plurality of preambles, etc.In the specification, a set of ROs may comprise a first set of ROs and a second set of ROs.Alternatively, the set of ROs may comprise either the first set of ROs or the second set of ROs.In the specification, the first set of ROs may be referred as a legacy RO set, a legacy set of ROs, a common set of ROs, a default set of ROs, legacy ROs, non-SBFD ROs, common ROs, a set of ROs, and / or the like. In an example, a first RO of the first set of ROs or the legacy set of ROs may be during or overlap, in time, with) one or more uplink symbols and / or one or more flexible symbols (based on TDD-UL-DL-ConfigurationCommon). More specifically, in this disclosure, a legacy set of ROs may refer to a set of ROs that overlaps, in time, with one or more uplink symbols and / or one or more flexible symbols.The second set of ROs may be referred as an additional RO set for a SBFD-aware UE, an additional set of ROs for a SBFD operation, SBFD-ROs, ROs for a SBFD, SBFD operation ROs, a SBFD set of ROs, and / or the like. A second RO of the second set of ROs (or a SBFD set of ROs) is in one or more SBFD symbols (based on SBFD configuration parameters) (and / or the one or more SBFD symbols are downlink symbols and / or flexible symbols (based on TDD-UL-DL-ConfigurationCommon)). More specifically, in this disclosure, an SBFD set of ROs may refer to a set of ROs that overlaps, in time, with one or more SBFD symbols.In the specifications, a 4-step legacy set of ROs may refer a set of ROs used for 4-step RA procedure and / based on a legacy set of ROs. A 4-step SBFD set of ROs may refer a set of ROs used for 4-step RA procedure and / based on a SBFD set of ROs. A 2-step legacy set of ROs may refer a set of ROs used for 2-step RAprocedure and / based on a legacy set of ROs. A 2-step SBFD set of ROs may refer a set of ROs used for 2-step RA procedure and / based on a SBFD set of ROs.In the specification, a random access procedure is referred or initiated by transmitting a preamble or a PRACH via a RO. The RO is from the first set of ROs (or a legacy set of ROs, 4-step legacy RO set, 2-step legacy RO set) may refer that a RA symbol type of the random access procedure is a 'non-SBFD' 'type A' or 'legacy'. The RO is from the second set of ROs (or a SBFD set of ROs, 4-step SBFD RO set, 2-step SBFD RO set) may refer that a RA type of the random access procedure is a 'SBFD' or 'type B'. When the RO is from the first set of ROs, a RACH symbol type of the random access procedure may be set to 'legacy' or 'type A1or 'non-SBFD'. When the RO is from the second set of ROs, a RACH symbol type of the random access procedure may be set to 'SBFD' or 'type B'. The RACH symbol type is 'SBFD' or 'type B' may refer that the random access procedure is based on the SBFD set of ROs / the second set of ROs or the preamble is from the SBFD set of ROs / the second set of ROs. The RACH symbol type is 'non-SBFD' or 'legacy' may refer that the random access procedure is based on the legacy set of ROs / the first set of ROs or the preamble is from the legacy set of ROs / the first set of ROs.In the specification, a RACH symbol type of a random access procedure may be determined based on a set of ROs that the random access procedure is based on. The RACH symbol type of a random access procedure being 'non-SBFD' or 'type A' or 'legacy' may refer that the random access procedure has initiated based on a legacy set of ROs or a set of ROs that are common to a plurality of wireless devices of a cell, regardless of whether the plurality of wireless devices support a SBFD operation of the cell or not. The RACH symbol type of a random access procedure being 'SBFD' or 'type B' may refer that the random access procedure has initiated based on a SBFD set of ROs that are common to one or more wireless devices of the plurality of wireless devices of a cell, where each of the one or more...

Claims

Claims1. A method performed by a wireless device and comprising the steps of:receiving one or more messages indicating different sets of parameters for a cell, wherein each of the different sets of parameters indicates:a starting physical resource block, PRB, index for a frequency hopping of an uplink transmission; anda number of PRBs available for the frequency hopping of the uplink transmission; and transmitting a preamble via a random access resource, in particular a RO, of the cell; receiving a downlink data comprising a UE contention resolution identity;based on the receiving, selecting, from among the different sets of parameters, a set of parameters to use for a first uplink transmission and / or a first downlink data reception, based on: whether the random access resource is from a first set of random access resources of the cell or a second set of random access resources of the cell, wherein:each, of the first set of random access resources, overlaps with uplink and / or flexible symbols; andeach, of the second set of random access resources, overlaps with subband full duplex, SBFD, symbols;whether resources of the first uplink transmission and / or resources of the first downlink data reception overlap, in time, with one or more SBFD symbols of the cell; andtransmitting the first uplink transmission, comprising a feedback for the downlink data, using the selected set of parameters; and / or receiving the first downlink data reception.

2. The method of claim 1, wherein the different sets of parameters comprise a first set of parameters and a second set of parameters.

3. The method of claim 2, wherein the one or more messages indicates an uplink bandwidth part, BWP, wherein the starting PRB index, of the first set of parameters, is determined based on the uplink BWP.

4. The method of claim 3, wherein the one or more messages indicates an uplink subband, wherein the starting PRB index, of the second set of parameters, is determined based on the uplink BWP and the uplink subband.

5. The method of any of previous claims, wherein the first uplink transmission is a physical uplink control channel, PUCCH, comprising a feedback corresponding to the downlink data.

6. The method of any of previous claims, further comprising determining a first hop of the first uplink data transmission based on the starting PRB index.

7. The method of any of previous claims, further comprising determining a second hop of the first uplink transmission based on the starting PRB index and the number of PRBs.

8. The method of claim 6 or 7, wherein the set of parameters is:the second set of parameters in response to the random access resource being from the second set of random access resources and the resources of the first uplink transmission overlapping with the one or more SBFD symbols; andthe first set of parameters in response to the random access resource being from the first set of random access resources or the resources of the first uplink transmission not overlapping with the one or more SBFD symbols.

9. The method of any of previous claims, wherein the first set of random access resources and the second set of random access resources are associated with a same set of features.

10. The method of claim 9, wherein the same set of features comprises one or more of reduced capability, small data transmission, msg3 repetition, and msgl repetition.

11. The method of claim 10, wherein the one or more messages indicates a feature combination preambles (e.g., FeatureCombinationPreambles IE) comprising a feature combination (e.g., Featurecombination) indicating the set of features, a start preamble for this partition (e.g., startPreambleForThisPartition), and optionally one or more msgl repetition numbers.

12. The method of claim 11, further comprising determining the first set of random access resources and the second set of random access resources based on the feature combination preambles, wherein the feature combination, the start preamble for this partition and optionally the one or more msgl repetition numbers are commonly applied for the first set of random access resources and the second set of random access resources.

13. The method of any of previous claims, wherein the one or more messages comprise one or more system information blocks, SIBs.

14. The method of any of previous claims, wherein the one or more messages indicate an initial uplink BWP, wherein the initial uplink BWP is the uplink BWP.

15. The method of claim 1, further comprising the following steps prior to receiving the downlink data comprising a UE contention resolution identity:receiving, by the wireless device, a random access response, RAR, message comprising an uplink, UL, grant for a third uplink transmission,in response to the receiving, selecting, from among the different sets of parameters, a set of parameters to use for the third uplink transmission, based on:whether the random access resource is from the first set of random access resources of the cell or the second set of random access resources of the cell,whether resources of the UL grant for the third uplink transmission overlap, in time, with one or more SBFD symbols of the cell; andtransmitting the third uplink transmission comprising UE contention resolution identity using the selected set of parameters.

16. The method of any of previous claims, further comprising performing, by the wireless device, the first downlink data reception using the selected set of parameters17. The method of any of the previous claims, wherein the first uplink transmission is performed by means of a first uplink frequency hopping pattern, and the first downlink data reception is performed using a first downlink frequency hopping pattern; and wherein:the one or more messages indicate a first uplink set of parameters determining the first uplink frequency hopping pattern and a first downlink set of parameters determining a first downlink frequency hopping pattern; and / orthe selected set of parameters comprise the first uplink set of parameters and / or the first downlink set of parameters; and / orthe first downlink set of parameters comprise a downlink bandwidth part, and a downlink subband, and / orthe first uplink set of parameters comprise an uplink bandwidth part, and an uplink subband; and / orthe first downlink set of parameters are derived or obtained, by the wireless device, from the first uplink set of parameters; or the first uplink set of parameters are derived from the first downlink set of parameters; and / orthe first uplink frequency hopping pattern and the first downlink frequency hopping pattern are complementary.

18. A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a wireless device, one or more messages indicating different sets of parameters, wherein each of the different sets of parameters indicates:a starting physical resource block (PRB) index for frequency hopping of an uplink transmission by the wireless device; anda number of PRBs available for the frequency hopping of the uplink transmission; configuring, for a cell, a first set of random access resources (ROs) and a second set of random access resources, wherein:each of the first set of ROs overlaps with uplink and / or flexible symbols; andeach of the second set of ROs overlaps with subband full duplex (SBFD) symbols; receiving, from the wireless device, a preamble via a random access resource, in particular a RO, of the cell;transmitting, to the wireless device, downlink data comprising a UE contention resolution identity;transmitting, to the wireless device, an uplink grant for a first uplink transmission, the uplink grant indicating a set of parameters selected from among the different sets of parameters, based on:whether the random access resource is from the first set of random access resources or the second set of random access resources;whether resources of the first uplink transmission overlap, in time, with one or more SBFD symbols of the cell;receiving, from the wireless device, the first uplink transmission comprising feedback for the downlink data, wherein the first uplink transmission uses the selected set of parameters.

19. A wireless device comprising a processor configured for performing the method of any of the previous claims 1 to 17.

20. A base station comprising a processor configured for performing the method of claim 19.

21. A computer-readable medium storing computer program instructions that, when executed by a processor of a wireless device, cause the wireless device to execute the steps of the methods of claims 1 to 17.

22. A computer-readable medium storing computer program instructions that, when executed by a processor of a base station, cause the base station to execute the steps of the methods of claim 19.

Images