Method, device, and system for signal multiplexing in uplink channel repetition

Abstract

A wireless device can receive downlink control information (DCI) that schedules a transmission of a channel state information (CSI) report, one or more first repetitions of a physical uplink shared channel (PUSCH) transmission with a first spatial domain transmission filter, and one or more second repetitions of the PUSCH transmission with a second spatial domain transmission filter. The wireless device can multiplex the CSI report on an earliest repetition of the one or more first repetitions corresponding to the first spatial domain transmission filter and an earliest repetition of the one or more second repetitions corresponding to the second spatial domain transmission filter. The wireless device can transmit the one or more first repetitions and the one or more second repetitions based on the multiplexing of the CSI report.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 130,062, filed December 23, 2020, the entire contents of which are hereby incorporated by reference. TECHNICAL FIELD

[0003] The present disclosure relates generally to wireless communications, including but not limited to methods, devices, and systems for signal multiplexing in uplink channel repetition. BACKGROUND

[0004] In the prior art, a wireless device can multiplex a CSI report in a first / earliest / starting repetition of a transport block. The wireless device can multiplex the CSI report in a first / starting / earliest transmission occasion among one or more first transmission occasions and one or more second transmission occasions. The wireless device can transmit the transport block with / carrying the CSI report in the first / earliest / starting repetition of the transport block (or in the first / starting / earliest transmission occasion). In an example, the first / earliest / starting repetition (or in the first / starting / earliest transmission occasion) can be associated with a first TRP. For example, based on a blockage between the wireless device and the first TRP, the first TRP can not receive the transport block in the first / earliest / starting repetition of the transport block (or in the first / starting / earliest transmission occasion). The base station (or the first TRP) can not receive the CSI report based on not receiving the transport block. Multiplexing the CSI report in the first / earliest / starting repetition (or in the first / starting / earliest transmission occasion) associated with (or monitored by) the first TRP can not be efficient when there is a blockage between the wireless device and the first TRP. This can result in retransmission triggering the DCI of the CSI report. This can increase the latency / delay for successful communication. This can increase the power consumption at the base station and / or the wireless device. SUMMARY

[0005] To address the concerns described above, a first aspect of embodiments of the present disclosure provides a method for signal multiplexing in uplink channel repetition, the method comprising:

[0006] receiving, by a wireless device, a downlink control information (DCI) that schedules:

[0007] a transmission of a channel state information (CSI) report via a cell, wherein the CSI report is transmitted on a physical uplink shared channel (PUSCH) with a transport block;

[0008] one or more first repetitions of the transport block on the PUSCH using a first spatial domain transmission filter; and

[0009] one or more second repetitions of the transport block on the PUSCH using a second spatial domain transmission filter; and

[0010] transmit the CSI report via the cell only on:

[0011] an earliest repetition of the one or more first repetitions of the transport block on the PUSCH; and

[0012] an earliest repetition of the one or more second repetitions of the transport block on the PUSCH.

[0013] A second aspect of the embodiments of the disclosure proposes a wireless device for signal multiplexing in uplink channel repetition, the wireless device comprising:

[0014] one or more processors; and

[0015] memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

[0016] receive a downlink control information, DCI, the DCI scheduling:

[0017] a transmission of a channel state information, CSI, report via a cell, wherein the CSI report is transmitted on an uplink shared channel, PUSCH, using a transport block;

[0018] one or more first repetitions of the transport block on the PUSCH using a first spatial domain transmission filter; and

[0019] one or more second repetitions of the transport block on the PUSCH using a second spatial domain transmission filter; and

[0020] transmit the CSI report via the cell only on:

[0021] an earliest repetition of the one or more first repetitions of the transport block on the PUSCH; and

[0022] an earliest repetition of the one or more second repetitions of the transport block on the PUSCH.

[0023] A third aspect of the embodiments of the disclosure proposes a system for signal multiplexing in uplink channel transmission, comprising

[0024] a base station, the base station comprising:

[0025] one or more first processors; and

[0026] a first memory storing first instructions that, when executed by the one or more first processors, cause the base station to transmit a downlink control information, DCI, that schedules:

[0027] a transmission via a channel state information, CSI, report of a cell, wherein the CSI report is transmitted on an uplink shared channel, PUSCH, with a transport block;

[0028] one or more first repetitions of the transport block on the PUSCH using a first spatial domain transmission filter; and

[0029] one or more second repetitions of the transport block on the PUSCH using a second spatial domain transmission filter; and

[0030] a wireless device, the wireless device comprising:

[0031] one or more second processors; and

[0032] a second memory storing second instructions that, when executed by the one or more second processors, cause the wireless device to:

[0033] receive the DCI; and

[0034] transmit the CSI report via the cell only on:

[0035] an earliest repetition of the one or more first repetitions of the transport block on the PUSCH; and

[0036] an earliest repetition of the one or more second repetitions of the transport block on the PUSCH. BRIEF DESCRIPTION OF DRAWINGS

[0037] Examples of several of the various implementations of the present disclosure are described herein with reference to the accompanying drawings.

[0038] Figure 1A and Figure 1B An exemplary mobile communication network is shown in which implementations of the present disclosure can be implemented.

[0039] Figure 2A and Figure 2B New Radio (NR) user plane and control plane protocol stacks are shown, respectively.

[0040] Figure 3 Examples of services provided between protocol layers of the NR user plane protocol stack of Figure 2A are shown.

[0041] Figure 4A Flow through the Figure 2AAn exemplary downlink data flow for an NR user plane protocol stack.

[0042] Figure 4B An exemplary format of a MAC subheader in a MAC PDU is shown.

[0043] Figure 5A And Figure 5B Mappings between logical channels, transport channels, and physical channels for downlink and uplink are shown.

[0044] Figure 6 An example diagram showing RRC state transitions for a UE.

[0045] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown.

[0046] Figure 8 An exemplary configuration of slots in the time and frequency domain of an NR carrier is shown.

[0047] Figure 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown.

[0048] Figure 10A Three carrier aggregation configurations with two component carriers are shown.

[0049] Figure 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown.

[0050] Figure 11A An example of a SS / PBCH block structure and location is shown.

[0051] Figure 11B An example of a CSI-RS mapped in the time and frequency domain is shown.

[0052] Figure 12A And Figure 12B Examples of three downlink and uplink beam management procedures are shown.

[0053] Figure 13A , Figure 13B And Figure 13C A four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure are shown.

[0054] Figure 14A An example of a CORESET configuration for a bandwidth part is shown.

[0055] Figure 14BAn example of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing is shown.

[0056] Figure 15 An example of a wireless device in communication with a base station is shown.

[0057] Figure 16A 、 Figure 16B 、 Figure 16C and Figure 16D An example structure for uplink and downlink transmissions is shown.

[0058] Figure 17 Multiplexing in uplink channel repetition in accordance with aspects of example embodiments of the present disclosure is shown.

[0059] Figure 18 Multiplexing in uplink channel repetition in accordance with aspects of example embodiments of the present disclosure is shown.

[0060] Figure 19 An uplink repetition scheme in accordance with aspects of example embodiments of the present disclosure is shown.

[0061] Figure 20 A flow diagram of multiplexing in uplink channel repetition in accordance with aspects of example embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0062] In this disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those of ordinary skill in the relevant arts that various changes can be made thereto without departing from scope of the invention. Indeed, after understanding the specification, those of ordinary skill in the relevant arts will be aware of how to implement alternative embodiments. The present embodiments should not be limited by any described example embodiments. Embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features and / or elements from the disclosed example embodiments can be combined to create additional embodiments within the scope of the present disclosure. The diagrams of any highlighted functionality and advantages are given for example purposes only. The disclosed architecture is sufficiently flexible and configurable such that it can be utilized in ways different from the ones shown. For example, the actions listed in any flow diagram can be reordered or only optionally used in certain embodiments.

[0063] Embodiments can be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms can be performed when certain criteria are met. Exemplary criteria can be based at least in part on, for example, a wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, a combination of the above, etc. Various exemplary embodiments can be applied when one or more criteria are met. Thus, exemplary embodiments that selectively implement the disclosed protocols can be implemented.

[0064] A base station can communicate with a mix of wireless devices. A wireless device and / or a base station can support multiple technologies and / or multiple versions of the same technology. A wireless device can have certain specific capabilities depending on the wireless device class and / or capabilities. When the present disclosure refers to a base station communicating with a plurality of wireless devices, the present disclosure can mean a subset of the total wireless devices in a coverage area. For example, the present disclosure can mean a plurality of wireless devices having a given capability and in a given sector of a base station of a given LTE or 5G version. The plurality of wireless devices in the present disclosure can refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in a coverage area performing according to the disclosed methods, etc. There can be a plurality of base stations or a plurality of wireless devices in a coverage area that can not comply with the disclosed methods, for example, these wireless devices or base stations can perform based on an older version of LTE or 5G technology.

[0065] In the present disclosure, "a" and "an" and similar phrases will be interpreted to mean "at least one" and "one or more." Similarly, any term ending in the suffix "(s)" will be interpreted to mean "at least one" and "one or more." In the present disclosure, the term "may" is interpreted to mean "may, for example." In other words, the term "may" indicates one of a number of suitable possibilities that the phrase following the term "may" can or can not be used in one or more of various embodiments. As used herein, the terms "comprises" and "consists of" recite one or more components of the element being described. The term "comprises" is interchangeable with "includes" and does not exclude the inclusion of additional components that are not listed. In contrast, "consists of" provides a complete list of one or more components of the element being described. As used herein, the term "based on" shall mean "based at least in part on" and not "based solely on," for example. As used herein, the term "and / or" means any possible combination of the elements listed. For example, "A, B, and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B, and C.

[0066] A is called a subset of B if every element of A is also an element of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celll, cell2} are: {celll}, {cell2}, and {celll, cell2}. The phrase "based on" (or, equivalently, "at least based on") indicates that the phrase after "based on" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "in response to" (or, equivalently, "at least in response to") indicates that the phrase after "in response to" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "in dependence of" (or, equivalently, "at least in dependence of") indicates that the phrase after "in dependence of" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments. The phrase "employing / using" (or, equivalently, "at least employing / using") indicates that the phrase after "employing / using" is an example of one of a number of suitable possibilities that can or can not be employed in one or more different embodiments.

[0067] The term configured can relate to the capability of a device, whether the device is in an operational state or a non-operational state. Configured can also mean a particular setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. can be "configured" within a device to provide the device with specific characteristics, whether the device is in an operational state or a non-operational state. The term control message "causing" in a device can mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0068] In this disclosure, a parameter (or, equivalently, a field or an information element: IE) can include one or more information objects, and an information object can include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. Then, for example, N includes K, and N includes J. In one example embodiment, when one or more messages include a plurality of parameters, it means that the parameter in the plurality of parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0069] Many of the features presented are described as optional by use of "may" or use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation of the optional features that can be obtained by selecting from among the described set of optional features. The present disclosure should be interpreted to explicitly disclose all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0070] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is herein defined as an element or component that performs a defined function and has a defined interface to other elements or components. Modules described in the present disclosure can be implemented in hardware, software, firmware, wetware, or combinations thereof, all of which are behaviorally equivalent. For example, a module can be implemented as a software routine in a computer language such as C, C++, Fortran, Pascal, Java, Basic, Matlab, or others, which is structured to perform the defined function and is compiled into machine language suitable for execution by the hardware machine. Wetware modules are defined as physical hardware that is not programmable but has specific behavior suitable for the defined function. For example, a wetware module can be a resistor, capacitor, transistor, or others, which are strung together to process input signals to produce output signals in a manner suitable for the defined function. It is noted that the modules described herein can be implemented in software, hardware, and / or a combination thereof. Modules implemented in software can be stored in memory 110, which can be implemented as a computer-readable medium that can be external to or integral with the machine 100. Software modules can be stored on RAM, disk drives, or other computer-readable media, which can be removable and / or integral to the machine 100. The machine 100 can include a file server for transferring the software modules to the machine 100. The machine 100 can include or be connected to a communications network for receiving software modules. The network can be or include the Internet, Local Area Network, Wide Area Network, Wireless Network, or any other communications network or combination of networks. The machine 100 can be connected to the communications network through a wired medium, a wireless medium, or a combination of wired and wireless media. Examples of a wireless medium include cellular phones, Bluetooth, Wi-Fi, and satellite. The machine 100 can be connected to the communications network through a wired medium, a wireless medium, or a combination of wired and wireless media. Examples of a wireless medium include cellular phones, Bluetooth, Wi-Fi, and satellite. The machine 100 can be connected to the communications network through a wired medium, a wireless medium, or a combination of wired and wireless media. Examples of a wireless medium include cellular phones, Bluetooth, Wi-Fi, and satellite.

[0071] Figure 1A An example of a mobile communication network 100 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 100 can be, for example, a public land mobile network (PLMN) operated by a network operator. As shown, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106. Figure 1A The mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0072] CN 102 can provide the wireless device 106 with an interface to one or more data networks (DNs) such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface function, the CN 102 can setup end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functions.

[0073] The RAN 104 can connect the CN 102 to the wireless device 106 through radio communications via an air interface. As part of the radio communications, the RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 via the air interface is known as the downlink, and the communication direction from the wireless device 106 to the RAN 104 via the air interface is known as the uplink. Downlink transmissions can be separated from uplink transmissions using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplex techniques.

[0074] The term “wireless device” can be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device that needs or can use wireless communication. For example, a wireless device can be a telephone, a smartphone, a tablet, a computer, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle road-side unit (RSU), a relay node, an automobile, and / or any combination thereof. The term “wireless device” encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0075] The RAN 104 can include one or more base stations (not shown). The term “base station” can 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 radio head (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, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station can include at least one gNB-central unit (gNB-CU) and at least one gNB-distributed unit (gNB-DU).

[0076] The base stations included in the RAN 104 can include one or more sets of antennas, which can be used to communicate with the wireless devices 106 through the use of the air interface. For example, one or more of the base stations can include three sets of antennas to control three cells (or sectors). The size of a cell can be determined by the range of the transmitters and receivers (e.g., base station receivers) that can successfully communicate with the transmitters (e.g., wireless device transmitters) operating in the cell. The cells of the base stations can together provide radio coverage to the wireless devices 106 over a wide geographic area to support the movement (e.g., roaming) of wireless devices.

[0077] In addition to three-sector sites, other implementations of the base stations are possible. For example, one or more of the base stations in the RAN 104 can be implemented as sectorized sites having more or less than three sectors. One or more of the base stations in the RAN 104 can be implemented as an access point, a baseband processing unit coupled to several remote radio heads (RRHs), and / or a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. A repeater node can amplify and rebroadcast a radio signal received from a donor node. A relay node can perform the same / similar functions as a repeater node but can decode a radio signal received from a donor node to cancel noise before amplifying and rebroadcasting the radio signal.

[0078] The RAN 104 can be deployed as a homogeneous network of macro cell base stations, each having similar antenna patterns and antenna gains, and / or similar transmit power levels. The RAN 104 can be deployed as a heterogeneous network having base stations of different types, such as macro cells, micro cells, femto cells, pico cells, etc. The base stations can be deployed in the RAN 104 to provide coverage for a certain area. The base stations can be macro base stations, small base stations, or the like. The base stations can operate according to a similar or different frequency range. The base stations can operate according to a similar or different air interface.

[0079] The Third Generation Partnership Project (3GPP) was formed in 1998 to provide global specification standards for mobile communication networks 100 similar to the mobile communication network 100. To date, the 3GPP has developed specifications for three generations of mobile networks: third generation (3G) networks known as Universal Mobile Telecommunications System (UMTS), fourth generation (4G) networks known as Long Term Evolution (LTE), and fifth generation (5G) networks known as 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network known as Next Generation RAN (NG-RAN). The embodiments can be applicable to the RAN of other mobile communication networks, such as Figure 1A The Third Generation Partnership Project (3GPP) was formed in 1998 to provide global specification standards for mobile communication networks 100 similar to the mobile communication network 100. To date, the 3GPP has developed specifications for three generations of mobile networks: third generation (3G) networks known as Universal Mobile Telecommunications System (UMTS), fourth generation (4G) networks known as Long Term Evolution (LTE), and fifth generation (5G) networks known as 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network known as Next Generation RAN (NG-RAN). The embodiments can be applicable to the RAN of other mobile communication networks, such as Figure 1A RAN 104, the RANs of earlier 3G and 4G networks, and those of future networks not yet specified (e.g., 3GPP 6G networks). An NG-RAN implements the 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technologies or other radio access technologies, including non-3GPP radio access technologies.

[0080] Figure 1B Another example mobile communication network 150 is shown in which embodiments of the disclosure can be implemented. The mobile communication network 150 can be, for example, a PLMN run by a network operator. As Figure 1B shown in FIG. 1, the 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 can be implemented and operate in a similar manner as described above with regard to the corresponding components of the mobile communication network 100. Figure 1A These components can be implemented and operate in a similar manner as described above with regard to the corresponding components of the mobile communication network 100.

[0081] The 5G-CN 152 provides UEs 156 with an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface function, the 5G-CN 152 can setup end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functions. In contrast to the CN of 3GPP 4G networks, the 5G-CN 152 can be based on a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of the 5G-CN 152 can 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).

[0082] As Figure 1B shown in FIG. 1, the 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are shown in FIG. 1 for ease of reference. Figure 1BThe AMF / UPF 158 can be implemented as one component for clarity. The UPF 158B can act as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B can 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 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 can act as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, a point of interconnect with the one or more DNs, and / or a branching point to support multi-homed PDU session. The UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and a DN.

[0083] The AMF 158A can 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 3 GPP 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 check of roaming rights, mobility management control (subscription and policies), network slice support, and / or session management function (SMF) selection. NAS can mean functionality operating between the CN and the UE, and AS can mean functionality operating between the UE and the RAN.

[0084] The 5G-CN 152 can include one or more additional network functions not shown in Figure 1B FIG. 1 for clarity. For example, the 5G-CN 152 can include one or more of the following: 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).

[0085] The NG-RAN 154 can connect the 5G-CN 152 to the UEs 156 through wireless communication over the air interface. The NG-RAN 154 can 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 can be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 can include one or more sets of antennas, which can be used to communicate with UEs 156 through the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 can include three sets of antennas to respectively control three cells (or sectors). The cells of the gNBs 160 and ng-eNBs 162 can together provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0086] As shown in Figure 1B , the gNBs 160 and / or ng-eNBs 162 can be connected by means of the NG interfaces to the 5G-CN 152, and by means of the Xn interface to other base stations. The NG and Xn interfaces can 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 ng-eNBs 162 can be connected by means of the Uu interface to the UEs 156. For example, as shown in Figure 1B , the gNB 160A can be connected by means of the Uu interface to the UE 156A. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces can be used by the network elements in Figure 1B to exchange data and signaling messages, and can include two planes: the user plane and the control plane. The user plane can handle data of interest to users. The control plane can handle signaling messages of interest to the network elements.

[0087] The gNBs 160 and / or ng-eNBs 162 can 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 can 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 can provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A can be connected to the AMF 158A by means of an NG control plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, transfer of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

[0088] The gNBs 160 can provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol terminations towards the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over the Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B can provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

[0089] The 5G-CN 152 is described as being configured to handle NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to connect to a 4G core network in a mode referred to as “non-standalone.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functionality (e.g., initial access, mobility, and paging). Although Figure 1B Only one AMF / UPF 158 is shown in FIG. 1, but one gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0090] As discussed, Figure 1B Interfaces between network elements in FIG. 1 (e.g., Uu, Xn, and NG interfaces) can be associated with a protocol stack that the network elements use to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane can handle data of interest to the user, while the control plane can handle signaling messages of interest to the network elements.

[0091] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface between the UE 210 and the gNB 220 are shown. Figure 2A and Figure 2B The protocol stacks shown in FIGS. 1A-1C can be the same as or similar to those for the Uu interface between the UE 156A and the gNB 160A shown in Figure 1B FIGS. 1A-1C.

[0092] Figure 2A An NR user plane protocol stack is shown that includes five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, the physical layer (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and can correspond to layer 1 of the open systems interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include the medium access control layer (MAC) 212 and 222, the radio link control layer (RLC) 213 and 223, the packet data convergence protocol layer (PDCP) 214 and 224, and the service data application protocol layer (SDAP) 215 and 225. These four protocols can together make up layer 2 or the data link layer of the OSI model.

[0093] Figure 3 Examples of services provided between the protocol layers of the NR user plane protocol stack are shown. From the top of Figure 2A and Figure 3 The SDAP 215 and 225 can perform QoS flow handling, starting from the top of FIG. 2A. The UE 210 can receive service through a PDU session, which can be a logical connection between the UE 210 and a DN. The PDU session can have one or more QoS flows. A UPF (e.g., UPF 158B) of a CN can 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 SDAP 215 and 225 can perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between QoS flows and data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between QoS flows and data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between QoS flows and data radio bearers.

[0094] The PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from an intended source. The PDCPs 214 and 224 can perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets that are received in duplicate due to, for example, intra-gNB handovers. The PDCPs 214 and 224 can perform packet duplication to improve the likelihood that a packet will be received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0095] Although Figure 3 Although not shown in FIG. 2, the PDCPs 214 and 224 can perform mapping / de-mapping between split radio bearers 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 to 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 the cell groups in dual connectivity. The PDCPs 214 and 224 can map / de-map the split radio bearers between RLC channels that belong to the cell groups.

[0096] The RLCs 213 and 223 can perform segmentation, retransmission by automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode that the RLC is operating in, the RLC can perform one or more of the functions described. The RLC configuration can be on a per logical channel basis, independent of numerology and / or transmission time interval (TTI) duration. As shown in FIG. 2, the RLCs 213 and 223 can provide RLC channels as a service to the PDCPs 214 and 224, respectively. Figure 3

[0097] ​The MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing can include multiplexing / demultiplexing of data units belonging to one or more logical channels into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling can be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 can 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 can support one or more numerologies and / or transmission timings. In an example, mapping restrictions in the logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As Figure 3 shown in FIG. 2, the MACs 212 and 222 can provide logical channels as a service to the RLCs 213 and 223.

[0098] The PHYs 211 and 221 can perform mapping of transport channels to physical channels and of bitmaps to resource elements, as well as the digital and analog signal processing functions used for transmission and reception over the air interface. These digital and analog signal processing functions can include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 can perform multi-antenna mapping. As Figure 3 shown in FIG. 2, the PHYs 211 and 221 can provide one or more transport channels as a service to the MACs 212 and 222.

[0099] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A A downlink data flow through the NR user plane protocol stack to generate three IP packets n , n+1 and m into two TBs at the gNB 220 is shown. Uplink data flow through the NR user plane protocol stack can be similar to the downlink data flow depicted in FIG. 2. Figure 4A

[0100] Figure 4A The downlink data flow of FIG. 2 begins when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to a radio bearer. In Figure 4A FIG. 2, the SDAP 225 maps the IP packets n and n+1 ​Mapped to the first radio bearer 402, and the IP packet... m Mapped to the second radio bearer 404. SDAP header (in Figure 4A Data units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). Figure 4A As shown, the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0101] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 This involves adding the corresponding headers and forwarding their output to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 can optionally perform fragmentation (e.g., as...). Figure 4A Regarding IP packets m (As shown) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

[0102] Figure 4B An exemplary format of the MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a Logical Channel Identifier (LCID) field identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0103] Figure 4B The diagram further illustrates a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B This shows two MAC CEs inserted into the MAC PDU. These can be used at the beginning of downlink transmissions within the MAC PDU (e.g., ...). Figure 4BMAC CEs can be used for in-band control signaling. Exemplary MAC CEs include: scheduling related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. There can be a MAC subheader with a similar format as described with respect to MAC SDUs before the MAC CE, and the MAC CE can be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

[0104] Before describing the NR control plane protocol stack, first describe the logical channels, transport channels, and physical channels and the mapping between the channel types. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack described later below.

[0105] Figure 5A and Figure 5B The mapping between logical channels, transport channels, and physical channels is shown for downlink and uplink, respectively. Information is transferred through the channels between RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between RLC and MAC and can be classified into control channels, which carry control and configuration information in the NR control plane, or traffic channels, which carry data in the NR user plane. Logical channels can be classified as dedicated to a specific UE, or as common logical channels, which can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0106] - a paging control channel (PCCH), which is used to carry paging messages for paging UEs whose location is not known by the network on a cell level;

[0107] - a broadcast control channel (BCCH), which is used to carry system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), where the system information messages can be used by UEs to obtain information about how the cell is configured and how to operate within the cell;

[0108] - a common control channel (CCCH), which is used to carry control messages and random access;

[0109] - a dedicated control channel (DCCH) for carrying control messages to / from specific UEs to configure the UEs;

[0110] - a dedicated traffic channel (DTCH) for carrying user data to / from specific UEs.

[0111] Transport channels are used between the MAC layer and the PHY layer, and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0112] - a paging channel (PCH) for carrying paging messages originating from the PCCH;

[0113] - a broadcast channel (BCH) for carrying the MIB from the BCCH;

[0114] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from the BCCH;

[0115] - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0116] - a random access channel (RACH) for allowing UEs to access the network without any prior scheduling.

[0117] The PHY can use physical channels to communicate information between processing levels of the PHY. A physical channel can have an associated set of time-frequency resources used to carry the information of one or more transport channels. The PHY can generate control information to support low-level operations of the PHY and provide the control information to lower levels of the PHY via physical control channels, referred to as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR includes, for example:

[0118] - a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0119] - a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH;

[0120] - a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which can include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0121] - Physical Uplink Shared Channel (PUSCH), which is used to carry uplink data and signaling messages from the UL-SCH and, in some cases, to carry uplink control information (UCI) as described below;

[0122] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which can include HARQ acknowledgements, Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Scheduling Requests (SRs); and

[0123] - Physical Random Access Channel (PRACH), which is used for random access.

[0124] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figure 5A and Figure 5B The physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS), and phase tracking reference signal (PT-RS). These physical layer signals are described in more detail below.

[0125] Figure 2B An example NR control plane protocol stack is shown. As shown in Figure 2B The first four protocol layers of the NR control plane protocol stack can use the same / similar as the example NR user plane protocol stack. The four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Rather than having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0126] The NAS protocols 217 and 237 can provide control plane functionality between the UE 210 and an AMF 230 (e.g., AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 can 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 NAS messages can pass. The NAS messages can be transported using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 can provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

[0127] The RRC 216 and 226 can provide control plane functionality between the UE 210 and gNB 220, or more generally, between the UE 210 and the RAN. The RRC 216 and 226 can provide control plane functionality between the UE 210 and gNB 220 via signaling messages, referred to as RRC messages. RRC messages can 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 can multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 can provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by a CN or RAN; establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN; security functions including key management; signaling radio bearers and data radio bearers establishment, configuration, maintenance, and release; mobility functions; QoS management functions; 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, the RRC 216 and 226 can establish an RRC context, which can involve configuring parameters for communication between the UE 210 and the RAN.

[0128] Figure 6 is an example diagram illustrating RRC state transitions of a UE. The UE can be the same as or similar to the wireless device 106, Figure 1A depicted in FIG. 1, Figure 2A and Figure 2B depicted in FIG. 2, or any other wireless device described in the present disclosure. As shown in FIG. 6, the UE can be in at least one of three RRC states: RRC connected 602 (e.g., RRC CONNECTED), RRC idle 604 (e.g., RRC IDLE), and RRC inactive 606 (e.g., RRC INACTIVE). Figure 6

[0129] In the RRC connected 602, the UE has an established RRC context and can have at least one RRC connection with a base station. The base station can be similar to one of: Figure 1A the one or more base stations included in the RAN 104 depicted in FIG. 1; Figure 1B one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1; Figure 2A and Figure 2B ​the gNB 220 depicted in the figures herein; or any other base station described in the present disclosure. A base station with which a UE is connected can have an RRC context for the UE. The RRC context, referred to as the UE context, can include parameters for communication between the UE and the base station. These parameters can include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in the RRC connected 602, mobility of the UE can be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE can measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station can request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608, or to RRC inactive 606 through a connection suspend procedure 610.

[0130] In the RRC idle 604, no RRC context can be established for the UE. In the RRC idle 604, the UE can not have an RRC connection with a base station. While in the RRC idle 604, the UE can be in a sleep state for most of the time (e.g., to conserve battery power). The UE can periodically wake up (e.g., once per each discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE can be managed by the UE through a procedure known as cell reselection. The RRC state can transition from the RRC idle 604 to the RRC connected 602 through a connection establishment procedure 612, which can involve a random access procedure, as discussed in more detail below.

[0131] In the RRC inactive 606, a previously established RRC context is maintained in the UE and the base station. This allows for a quick transition to the RRC connected 602 with reduced signaling overhead compared to the transition from the RRC idle 604 to the RRC connected 602. While in the RRC inactive 606, the UE can be in a sleep state, and mobility of the UE can be managed by the UE through cell reselection. The RRC state can transition from the RRC inactive 606 to the RRC connected 602 through a connection resume procedure 614, or to the RRC idle 604 through a connection release procedure 616, which can be the same as or similar to the connection release procedure 608.

[0132] RRC states can be associated with mobility management mechanisms. 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 inform the UE of events via a paging message without having to broadcast the paging message over the entire mobile communication network. The mobility management mechanisms used in RRC idle 604 and RRC inactive 606 can allow the network to track the UE at a cell group level, such that a paging message can be broadcast on a cell in the cell group in which the UE is currently camped rather than over the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE at a cell group level. These mobility management mechanisms can use different granularities of grouping to do so. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN area identifier (RAI); and a group of RAN areas, referred to as tracking areas and identified by a tracking area identifier (TAI).

[0133] Tracking areas can be used to track a UE at a CN level. A CN (e.g., CN 102 or 5G-CN 152) can provide a 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 that is not included in the list of TAIs associated with the UE registration area, the UE can perform a registration update with the CN to allow the CN to update the location of the UE and provide the UE with a new UE registration area.

[0134] RAN areas can be used to track a UE at a RAN level. For a UE in an RRC inactive 606 state, the UE can be assigned a RAN notification area. The RAN notification area can include one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station can belong to one or more RAN notification areas. In an example, a cell can 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 can perform a notification area update with the RAN to update the RAN notification area of the UE.

[0135] A last serving base station of a base station or UE storing an RRC context for the UE can be referred to as an anchor base station. The anchor base station can maintain the RRC context for the UE at least for a period of time that the UE remains in the RAN notification area of the anchor base station and / or for a period of time that the UE remains in RRC inactive 606.

[0136] A gNB, such as gNB 110, can be an anchor base station for a UE in RRC idle 604 or RRC inactive 606. The gNB can maintain an RRC context for the UE while the UE remains in the RAN notification area of the gNB and / or while the UE remains in RRC inactive 606. The gNB can be the last serving base station for the UE in RRC idle 604 or RRC inactive 606. Figure 1BThe gNB 160 can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0137] In NR, physical signals and physical channels (about Figure 5A and Figure 5B The concepts discussed can be mapped to Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that uses... F Data is transmitted via orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM symbols or M-PSK symbols) and divided into... F A parallel symbol stream. F The parallel symbol streams can be viewed as if they were in the frequency domain and used as input to blocks of Inverse Fast Fourier Transform (IFFT) that transform them to the time domain. An IFFT block can take... F Source symbols (from) F One source symbol is taken from each of the parallel symbol streams, and each source symbol is used to modulate the signal. F Corresponding to each orthogonal subcarrier F The amplitude and phase of one of the sinusoidal basis functions. The output of the IFFT block can represent... F The sum of orthogonal subcarriers F One time-domain sample. F Each time-domain sample can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upconversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using an FFT block before being processed by an IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing of the OFDM symbols can be performed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0138] Figure 7An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame can be identified by a system frame number (SFN). The SFN can repeat with a period of 1024 frames. As shown, the duration of one NR frame can be 10 milliseconds (ms), and can include 10 subframes of 1 ms duration. A subframe can be divided into slots, which include, for example, 14 OFDM symbols per slot.

[0139] The duration of a slot can depend on the numerology of the OFDM symbols used for the slot. In NR, flexible numerologies are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). A numerology can be defined in terms of subcarrier spacing and cyclic prefix duration. For numerologies in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the cyclic prefix duration can be scaled down from a baseline cyclic prefix duration of 4.7 μβ by powers of two. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μβ; 30 kHz / 2.3 μβ; 60 kHz / 1.2 μβ; 120 kHz / 0.59 μβ; and 240 kHz / 0.29 μβ.

[0140] A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations, and correspondingly, more slots per subframe. Figure 7 This slot duration and transmission structure per subframe in relation to numerology is shown for illustration, Figure 7 (not shown in FIG. 2B for illustration purposes). Subframes in NR can be used as a time reference independent of numerology, while slots can be used as a unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from slot duration, and start at any OFDM symbol, and continue for as many symbols as needed for the transmission. These partial-slot transmissions can be referred to as mini-slot or sub-slot transmissions.

[0141] Figure 8 An exemplary configuration of a slot in the time and frequency domain of an NR carrier is shown. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one subcarrier in the frequency domain by one OFDM symbol in the time domain, as shown in Figure 8 RB spans twelve consecutive REs in the frequency domain, as shown in Figure 8A NR carrier can be limited to a width of 275 RBs or 275 x 12 = 3300 subcarriers. If such a limit is used, a NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on a per-carrier bandwidth limit of 400 MHz.

[0142] Figure 8 A single numerology is shown to be used across the entire bandwidth of a NR carrier. In other example configurations, multiple numerologies can be supported on the same carrier.

[0143] NR can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs can be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth can be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE can adapt the size of the UE’s receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0144] NR defines bandwidth parts (BWPs) to support UEs that are not able to receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of contiguous RBs on a carrier. A UE can be configured (e.g., via an 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 can be active. The one or more BWPs can be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0145] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs can be linked with an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. For unpaired spectrum, a UE can expect the center frequency of a downlink BWP to be the same as the center frequency of an uplink BWP.

[0146] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station can 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 time and frequency domain where a UE can look for control information. A search space can be a UE-specific search space or a common search space (possibly usable by multiple UEs). For example, a base station can configure a UE with a common search space on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

[0147] For an uplink BWP in a set of configured uplink BWPs, a BS can configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE can receive a downlink reception (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured set of parameters for the downlink BWP (e.g., subcarrier spacing and cyclic prefix duration). A UE can transmit an uplink transmission (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured set of parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0148] One or more BWP indicator fields can be provided in downlink control information (DCI). A value of a BWP indicator field can indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. A value of the one or more BWP indicator fields can indicate an active uplink BWP for one or more uplink transmissions.

[0149] A base station can semi-statically configure a default downlink BWP for a UE within a set of configured downlink BWPs associated with a PCell. If a base station does not provide a default downlink BWP for a UE, the default downlink BWP can be an initial active downlink BWP. A UE can determine which BWP is an initial active downlink BWP based on a CORESET configuration obtained using a PBCH.

[0150] A base station can configure a UE with a BWP inactivity timer value for a PCell. A UE can start or restart a BWP inactivity timer at any appropriate time. For example, a UE can start or restart a BWP inactivity timer when the UE detects a DCI for a paired spectrum operation indicating an active downlink BWP other than a default downlink BWP; or a b ​) When the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or the default uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can run the BWP inactivity timer towards expiration (e.g., 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 can switch from the active downlink BWP to the default downlink BWP.

[0151] In an example, a base station can semi-statically configure a UE with one or more BWPs. The UE can switch the active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as the active BWP and / or in response to expiration of a BWP inactivity timer (e.g., in a case where the second BWP is the default BWP).

[0152] Downlink and uplink BWP switching (where BWP switching refers to switching from a current active BWP to a non-current active BWP) can be performed independently in paired spectrum. In unpaired spectrum, downlink and uplink BWP switching can be performed simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or initiation of random access.

[0153] Figure 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. A UE configured with the three BWPs can switch from one BWP to another BWP at a switching point. In this example, the UE can switch from BWP 1 to BWP 2 to BWP 3, and then back to BWP 2. Figure 9 In the example shown, the BWPs include: BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 can be the initial active BWP, and BWP 904 can be the default BWP. The UE can switch between the BWPs at a switching point. In this example, the UE can switch from BWP 902 to BWP 904 to BWP 906, and then back to BWP 904. Figure 9In the example of FIG. 9, the UE can switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 can occur for any suitable reason, such as in response to an expiration of a BWP inactivity timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 906 at switch point 910 in response to receiving a DCI indicating that BWP 906 is the active BWP. The UE can switch from active BWP 906 to BWP 904 at switch point 912 in response to an expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 902 at switch point 914 in response to receiving a DCI indicating that BWP 902 is the active BWP.

[0154] If a UE is configured for a secondary cell with a default downlink BWP and a timer value in a set of configured downlink BWPs, the UE procedures for switching BWPs on the secondary cell can be the same / similar to those on the primary cell. For example, the UE can use the timer value and default downlink BWP for the secondary cell in the same / similar manner that the UE would use those values for the primary cell.

[0155] To provide higher data rates, two or more carriers can be aggregated and transmitted to / from the same UE simultaneously using carrier aggregation (CA). The aggregated carriers in CA can be referred to as component carriers (CCs). When using CA, there are many serving cells for the UE, one for each CC. The CCs can have three configurations in the frequency domain.

[0156] Figure 10A Three CA configurations with two CCs are shown. In an intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are positioned directly adjacent to each other within the band. In an intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated by a gap in the band. In an inter-band configuration 1006, the two CCs are in frequency bands (frequency band A and frequency band B).

[0157] In an example, up to 32 CCs can be aggregated. The aggregated CCs can have the same or different bandwidth, subcarrier spacing, and / or duplexing scheme (TDD or FDD). A serving cell for a UE using CA can have downlink CCs. For FDD, one or more uplink CCs can optionally be configured for the serving cell. The ability to aggregate more downlink carriers than uplink carriers can be useful, for example, when a UE has more data traffic in the downlink than in the uplink.

[0158] When using CA, one of the aggregated cells for a UE can be referred to as a primary cell (PCell). The PCell can be the serving cell to which the UE initially connects at RRC connection setup, reestablishment, and / or handover. The PCell can provide NAS mobility information and security input to the UE. A UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as an uplink primary CC (UL PCC). Other aggregated cells for a UE can be referred to as secondary cells (SCells). In an example, SCells can be configured after the PCell is configured for a UE. For example, SCells can be configured through an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to an SCell can be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to an SCell can be referred to as an uplink secondary CC (UL SCC).

[0159] Configured SCells for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Configured SCells can be activated and deactivated using a MAC CE, for example, with respect to Figure 4B For example, a MAC CE can indicate which SCells for a UE (e.g., in a subset of configured SCells) are activated or deactivated using a bitmap (e.g., one bit per SCell). Configured SCells can be deactivated in response to expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0160] Downlink control information for a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, a process known as self-scheduling. A cell's DCI can be transmitted on another cell, a process known as cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0161] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10B In the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

[0162] A physical cell ID and a cell index can be assigned for a cell comprising a downlink carrier and an optional uplink carrier. The physical cell ID or the cell index can identify the downlink carrier and / or the uplink carrier of the cell, e.g., depending on the context in which the physical cell ID is used. The physical cell ID can be determined using a synchronization signal transmitted on a downlink component carrier. The cell index can be determined using an RRC message. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure refers to a first physical cell ID of a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell comprising the first downlink carrier. The same / similar concept can apply to, e.g., carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell comprising the first carrier is activated.

[0163] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, a HARQ entity can operate on a serving cell. Transport blocks can be generated according to assignments / grants of each serving cell. A transport block and potential HARQ retransmissions of the transport block can be mapped to a serving cell.

[0164] In the downlink, a base station can transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as Figure 5A shown) to a UE. In the uplink, a UE can transmit one or more RSs (e.g., DMRS, PT-RS, and / or SRS, as Figure 5B shown) to a base station. The PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block including the PSS, the SSS, and the PBCH. The base station can periodically transmit a burst of SS / PBCH blocks.

[0165] Figure 11A Examples of structures and locations of SS / PBCH blocks are shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as Figure 11A shown). The burst can be periodically transmitted (e.g., every 2 frames or 20 ms). The burst can be limited to a half frame (e.g., a first half frame with a duration of 5 ms). It should be understood that Figure 11Aare examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst location within a frame) can be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH blocks are transmitted; a numerology or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, a UE can assume a subcarrier spacing of SS / PBCH blocks based on a carrier frequency being monitored, unless the radio network configures the UE to assume a different subcarrier spacing.

[0166] An SS / PBCH block can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 3A) and can span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). A PSS, a SSS, and a PBCH can have a common center frequency. The PSS can be transmitted first and can span, for example, 1 OFDM symbol and 127 subcarriers. The SSS can be transmitted after the PSS (e.g., two symbols later) and can span 1 OFDM symbol and 127 subcarriers. The PBCH can be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and can span 240 subcarriers. Figure 11A

[0167] A UE can not know the location of an SS / PBCH block in the time and frequency domains (e.g., in the case that the UE is searching for a cell). To find and select a cell, the UE can monitor a carrier for a PSS. For example, the UE can monitor a frequency location within the carrier. If a PSS is not found after a certain duration (e.g., 20 ms), the UE can search for a PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If a PSS is found at a certain location in the time and frequency domains, the UE can determine the location of a SSS and a PBCH based on a known structure of the SS / PBCH block, respectively. The SS / PBCH block can be a cell-defining SS block (CD-SSB). In an example, a primary cell can be associated with a CD-SSB. The CD-SSB can be located on a synchronization raster. In an example, cell selection / searching and / or reselection can be based on a CD-SSB.

[0168] An SS / PBCH block can be used by a UE to determine one or more parameters of a cell. For example, the UE can determine a physical cell identifier (PCI) of the cell based on sequences of a PSS and a SSS, respectively. The UE can determine a location of a frame boundary of the cell based on a location of the SS / PBCH block. For example, the SS / PBCH block can indicate that it has been transmitted according to a transmission pattern in which the SS / PBCH block in the transmission pattern is a known distance from a frame boundary.

[0169] ​PBCH can use QPSK modulation and can use forward error correction (FEC). The FEC can use polar coding. One or more symbols spanned by the PBCH can carry one or more DMRS for demodulating the PBCH. The PBCH can include an indication of a current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters can help a UE synchronize in time with the base station. The PBCH can include a master information block (MIB) for providing one or more parameters to the UE. The MIB can be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI can include a system information block type 1 (SIB1). The SIB1 can contain information needed by the UE to access the cell. The UE can use one or more parameters of the MIB to monitor PDCCH that can be used to schedule PDSCH. The PDSCH can include the SIB1. The SIB1 can be decoded using parameters provided in the MIB. The PBCH can indicate that the SIB1 is not present. Based on the PBCH indicating that the SIB1 is not present, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency to which the UE points.

[0170] A UE can assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., have a same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameter). The UE can not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indexes.

[0171] SS / PBCH blocks (e.g., those within a half frame) can be transmitted in spatial directions (e.g., using different beams spanning a coverage area of a cell). In an example, a first SS / PBCH block can be transmitted in a first spatial direction using a first beam and a second SS / PBCH block can be transmitted in a second spatial direction using a second beam.

[0172] In an example, a base station can transmit a plurality of SS / PBCH blocks within a frequency range of a carrier. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks can be different than 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 can be different or the same.

[0173] A CSI-RS can be transmitted by a base station and used by a UE to acquire channel state information (CSI). A base station can configure a UE with one or more CSI-RS for channel estimation or any other suitable purpose. A base station can configure a UE with one or more of the same / similar CSI-RS. A UE can measure the one or more CSI-RS. A UE can estimate a downlink channel state and / or generate a CSI report based on measurements of the one or more downlink CSI-RS. A UE can provide a CSI report to a base station. A base station can use feedback provided by a UE (e.g., estimated downlink channel state) to perform link adaptation.

[0174] A base station can semi-statically configure a UE with one or more CSI-RS resource sets. A CSI-RS resource can be associated with a location in time and frequency domain and periodicity. A base station can selectively activate and / or deactivate a CSI-RS resource. A base station can indicate to a UE that a CSI-RS resource in a CSI-RS resource set is activated and / or deactivated.

[0175] A base station can configure a UE to report CSI measurements. A base station can configure a UE to provide a CSI report periodically, aperiodically, or semi-persistently. For periodic CSI reporting, a UE can be configured with a timing and / or periodicity of multiple CSI reports. For aperiodic CSI reporting, a base station can request a CSI report. For example, a base station can order a UE to measure a configured CSI-RS resource and provide a CSI report related to the measurements. For semi-persistent CSI reporting, a base station can configure a UE to periodically transmit and selectively activate or deactivate a periodic report. A base station can configure a UE with a CSI-RS resource set and a CSI report using RRC signaling.

[0176] A CSI-RS configuration can include one or more parameters indicating, for example, up to 32 antenna ports. A UE can 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 the CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource blocks (PRBs) configured for the CORESET. A UE can be configured to employ the same OFDM symbols for a downlink CSI-RS and a SS / PBCH block when the downlink CSI-RS and the SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH block.

[0177] A downlink DMRS can be transmitted by a base station and used by a UE for channel estimation. For example, a downlink DMRS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network can support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station can semi-statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. A radio network can support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, where a DMRS location, a DMRS pattern, and / or a scrambling sequence can be the same or different. A base station can transmit a downlink DMRS and a corresponding PDSCH using a same precoding matrix. A UE can use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0178] In an example, a transmitter (e.g., a base station) can use a precoder matrix for a portion of a transmission bandwidth. For example, the transmitter can 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 can be different based on the first bandwidth being different than the second bandwidth. A UE can assume a same precoding matrix is used across a set of PRBs. The set of PRBs can be denoted as a precoding resource block group (PRG).

[0179] A PDSCH can include one or more layers. A UE can assume that at least one symbol with a DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer can configure up to 3 DMRSs for a PDSCH.

[0180] Downlink PT-RS can be transmitted by a base station and used by a UE for phase noise compensation. Whether or not a downlink PT-RS is present can depend on RRC configuration. The presence and / or pattern of a downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of a downlink PT-RS can be associated with one or more DCI parameters including at least MCS. An NR network can support multiple PT-RS densities defined in time / frequency domain. When present, a frequency domain density can be associated with at least one configuration of a scheduled bandwidth. A UE can take a same precoding for a DMRS port and a PT-RS port. The number of PT-RS ports can be fewer than the number of DMRS ports in a scheduled resource. A downlink PT-RS can be confined in a scheduled time / frequency duration for a UE. A downlink PT-RS can be transmitted on a symbol to facilitate phase tracking at a receiver.

[0181] A UE can transmit an uplink DMRS to a base station for channel estimation. For example, a base station can use an uplink DMRS for consistent demodulation of one or more uplink physical channels. For example, a UE can transmit an uplink DMRS with a PUSCH and / or a PUCCH. An uplink DM-RS can span a similar frequency range as a frequency range associated with a corresponding physical channel. A base station can configure a UE with one or more uplink DMRS configurations. At least one DMRS configuration can support a front-loaded DMRS pattern. A front-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs can be configured to be transmitted at one or more symbols of a PUSCH and / or a PUCCH. A base station can semi-statically configure a UE with a number (e.g., a maximum number) of front-loaded DMRS symbols of a PUSCH and / or a PUCCH that the UE can use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network can support a common DMRS structure (e.g., for cyclic prefix orthogonal frequency-division multiplexing (CP-OFDM)) for downlink and uplink, where a DMRS location, a DMRS pattern, and / or a scrambling sequence for a DMRS can be the same or different.

[0182] A PUSCH can include one or more layers, and a UE can transmit at least one symbol with a DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer can configure up to three DMRSs for a PUSCH.

[0183] Uplink PT-RS (which can be used by a base station for phase tracking and / or phase noise compensation) can or can not be present depending on the UE's RRC configuration. The presence and / or pattern of uplink PT-RS can be configured on a UE- specific basis by a combination of RRC signaling and / or one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI. When configured, the dynamic presence of uplink PT-RS can be associated with one or more DCI parameters including at least MCS. A radio network can support multiple uplink PT-RS densities defined in time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can take a same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be fewer than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS can be confined in the scheduled time / frequency duration for the UE.

[0184] A UE can transmit SRS to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. SRS transmitted by a UE can allow a base station to estimate the uplink channel state at one or more frequencies. A scheduler at the base station can employ the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmissions from the UE. A base station can semi-statically configure a UE with one or more SRS resource sets. For an SRS resource set, the base station can configure the UE with one or more SRS resources. SRS resource set applicability can be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, SRS resources in an SRS resource set of the one or more SRS resource sets (e.g., with same / similar time domain behavior, periodic, aperiodic, etc.) can be transmitted at a time (e.g., simultaneously). A UE can transmit one or more SRS resources in an SRS resource set. An NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. A UE can transmit SRS resources based on one or more trigger types, where the one or more trigger types can include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format can be employed for a UE to select at least one configured SRS resource set of one or more configured SRS resource sets. SRS trigger type 0 can refer to SRS triggered based on higher layer signaling. SRS trigger type 1 can refer to SRS triggered based on one or more DCI formats. In an example, a UE can be configured to transmit SRS after the transmission of PUSCH and corresponding uplink DMRS when PUSCH and SRS are transmitted in a same slot.

[0185] A base station can semi-statically configure a UE with one or more SRS configuration parameters indicating at least one of: an SRS resource configuration identifier; a number of SRS ports; a time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); a slot, mini-slot, and / or subframe level periodicity; a slot of periodic and / or aperiodic SRS resources; 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.

[0186] An antenna port is defined such that a channel through which a symbol on an antenna port is conveyed can be inferred from a channel through 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, a receiver can infer a channel (e.g., a fading gain, a multipath delay, etc.) used to convey the second symbol on the antenna port from a channel used to convey the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi co-located (QCLed) if one or more large scale properties of a channel through which a first symbol on the first antenna port is conveyed can be inferred from a channel through which a second symbol on the second antenna port is conveyed. The one or more large scale properties can include at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or a spatial receive (Rx) parameter.

[0187] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamformed reference signals. A UE can perform downlink beam measurements based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)) and generate a beam measurement report. A UE can perform a downlink beam measurement procedure after setting up an RRC connection with a base station.

[0188] Figure 11B An example of a channel state information reference signal (CSI-RS) mapped in time and frequency domain is shown. Figure 11BThe squares shown in the middle can represent resource blocks (RBs) within a bandwidth of a cell. A base station can transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters can be configured for a CSI-RS resource configuration by higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), CSI-RS power parameter, CSI-RS sequence parameter, code division multiplexing (CDM) type parameter, frequency density, 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.

[0189] Figure 11B The three beams shown can be configured for the UE in a UE-specific configuration. Figure 11B Three beams (Beam #1, Beam #2, and Beam #3) are illustrated in the middle, more or fewer beams can be configured. Beam #1 can be assigned a CSI-RS 1101, which can be transmitted in one or more subcarriers in the RBs of the first symbol. Beam #2 can be assigned a CSI-RS 1102, which can be transmitted in one or more subcarriers in the RBs of the second symbol. Beam #3 can be assigned a CSI-RS 1103, which can be transmitted in one or more subcarriers in the RBs of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (e.g., those not used to transmit the CSI-RS 1101) to transmit another CSI-RS associated with a beam of another UE. By using time division multiplexing (TDM), the beams for a UE can be configured such that the beams for the UE use symbols from the beams of other UEs.

[0190] CSI-RS, such as Figure 11BThose illustrated in FIG. 11 (e.g., CSI-RSs 1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurements. For example, a UE can measure a reference signal received power (RSRP) of a configured CSI-RS resource. A base station can configure a UE with a reporting configuration, and the UE can report the RSRP measurement to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, a base station can determine one or more transmission configuration indication (TCI) states including a plurality of reference signals based on the reported measurements. In an example, a base station can indicate the one or more TCI states to a UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). A UE can receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, a UE can or can not have a beam correspondence capability. If a UE has a beam correspondence capability, the UE can determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of a corresponding Rx beam. If a UE does not have a beam correspondence capability, the UE can perform an uplink beam selection procedure to determine a spatial domain filter of a Tx beam. The UE can perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by a base station. The base station can select and indicate an uplink beam of the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0191] In a beam management procedure, a UE can assess (e.g., measure) a channel quality of one or more beam pair links, including a transmission beam transmitted by a base station and a receive beam received by the UE. Based on the assessment, the UE can transmit a beam measurement report indicating one or more beam pair quality parameters including, for example, one or more beam identifications (e.g., beam indices, reference signal indices, etc.), an RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (RI).

[0192] Figure 12AExamples of three downlink beam management procedures are shown: PI, P2, and P3. Procedure PI can enable UE measurements of transmission (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of PI, respectively). Beamforming at the TRP can include a Tx beam sweep for a set of beams (shown as ellipses rotating in a counterclockwise direction, indicated by dashed arrows, in the top row of PI and P2). Beamforming at the UE can include an Rx beam sweep for a set of beams (shown as ellipses rotating in a clockwise direction, indicated by dashed arrows, in the bottom row of PI and P3). Procedure P2 can be used to enable UE measurements of Tx beams of a TRP (shown as ellipses rotating in a counterclockwise direction, indicated by dashed arrows, in the top row of P2). The UE and / or base station can perform procedure P2 using a smaller set of beams than used in procedure PI, or using narrower beams than used in procedure PI. This can be referred to as beam refinement. The UE can perform procedure P3 for Rx beam determination by using the same Tx beams at the base station and sweeping Rx beams at the UE.

[0193] Figure 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements of Tx beams of a UE, e.g., to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE can include, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotating in a clockwise direction, indicated by dashed arrows, in the bottom row of U1 and U3). Beamforming at the base station can include, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotating in a counterclockwise direction, indicated by dashed arrows, in the top row of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beams when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller set of beams than used in procedure PI, or using narrower beams than used in procedure PI. This can be referred to as beam refinement. The UE can perform procedure U3 to adjust its Tx beams when the base station uses a fixed Rx beam.

[0194] A UE can initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE can transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, etc.) based on initiation of the BFR procedure. The UE can detect a beam failure based on a determination that a quality of a beam pair link of an associated control channel is not satisfactory (e.g., has an error rate above an error rate threshold, has a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0195] A UE can measure a quality of a beam pair link using one or more reference signals (RSs) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam pair link can 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 the RS resource. A base station can indicate that a 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, etc.). The one or more DMRSs of the RS resource and the channel can be QCLed when channel properties (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from transmissions to the UE via the RS resource are similar or the same as channel properties from transmissions to the UE via the channel.

[0196] A network (e.g., a gNB and / or an ng-eNB of the network) and / or a UE can initiate a random access procedure. A UE in an RRC_IDLE state and / or an RRC_INACTIVE state can initiate a random access procedure to request a connection setup to the network. A UE can initiate a random access procedure from an RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for an uplink transmission of an SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when an uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for a beam failure recovery request. A network can initiate a random access procedure for a handover and / or for establishing a time alignment of an SCell addition.

[0197] Figure 13A A four-step contention-based random access procedure is shown. Prior to initiating the procedure, a base station can transmit a configuration message 1310 to a UE. Figure 13AThe illustrated procedure includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 can include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 can include and / or be referred to as a random access response (RAR).

[0198] The configuration message 1310 can be transmitted, for example, using one or more RRC messages. The one or more RRC messages can indicate, to a UE, one or more random access channel (RACH) parameters. The one or more RACH parameters can include at least one of: 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 one or more RRC messages can be broadcast or multicast by a base station to one or more UEs. The one or more RRC messages can be UE-specific (e.g., a dedicated RRC message transmitted to a UE in an RRC CONNECTED state and / or an RRC INACTIVE state). The UE can determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313. Based on the one or more RACH parameters, the UE can determine a reception timing and a downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0199] The one or more RACH parameters provided in the configuration message 1310 can indicate one or more physical RACH (PRACH) occasions available for transmitting Msg 1 1311. The one or more PRACH occasions can be predefined. The one or more RACH parameters can indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters can indicate an association between: (a) one or more PRACH occasions, and (b) one or more reference signals. The one or more RACH parameters can indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals can be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters can indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH block.

[0200] The one or more RACH parameters provided in the configuration message 1310 can be used to determine an uplink transmission power for Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., a received target power and / or an initial power for preamble transmission). There can be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters can indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmission of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters can indicate one or more thresholds based on which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

[0201] Msg 1 1311 can include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group can include one or more preambles. The UE can determine a preamble group based on a path loss measurement value and / or a size of Msg 3 1313. The UE can measure an RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, the UE can select at least one preamble associated with the one or more reference signals and / or a selected preamble group if an association between the one or more preambles and the at least one reference signal is configured by the RRC message.

[0202] The UE can determine a preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE can determine a preamble based on a path loss measurement, an RSRP measurement, and / or a size of Msg 3 1313. As another example, the one or more RACH parameters can 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). The base station can 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 can determine a preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH occasions. The UE can use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selecting a preamble and for determining a PRACH occasion. The one or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate an association between a PRACH occasion and the one or more reference signals.

[0203] If a response is not received after a preamble transmission, the UE can perform a preamble retransmission. The UE can increase an uplink transmission power for the preamble retransmission. The UE can select an initial preamble transmission power based on a path loss measurement value and / or a target received preamble power configured by the network. The UE can determine a retransmission preamble and can ramp up the uplink transmission power. The UE can receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step can be an amount of incremental increase of the uplink transmission power for the retransmission. If the UE determines a same reference signal (e.g., SSB and / or CSI-RS) as a previous preamble transmission, the UE can ramp up the uplink transmission power. The UE can count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold (e.g., preambleTransMax) configured by the one or more RACH parameters, the UE can determine that the random access procedure is not successfully completed.

[0204] Msg 2 1312 received by the UE can include a RAR. In some scenarios, Msg 2 1312 can include multiple RARs corresponding to multiple UEs. Msg 2 1312 can be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 can be scheduled on a DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 can indicate that Msg 1 1311 was received by the base station. Msg 2 1312 can include a time alignment command that can be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmission of Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting a preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to start the time window based on the PRACH occasion used by the UE to transmit the preamble. For example, the UE can start the time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH occasion starting from the end of the preamble transmission). The one or more symbols can be determined based on a numerology. The PDCCH can be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE can identify the RAR based on a radio network temporary identifier (RNTI). The RNTI can be used depending on one or more events that initiated the random access procedure. The UE can use a random access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH occasion in which the UE transmitted the preamble. For example, the UE can 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 occasion. An example of the RA-RNTI can be as follows:

[0205] RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id

[0206] where s_id can be an index of the first OFDM symbol of the PRACH occasion (e.g., 0 ≤ s_id < 14), t_id can be an index of the first slot of the PRACH occasion in a system frame (e.g., 0 ≤ t_id < 80), f_id can be an index of the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be a UL carrier used for the preamble transmission (e.g., 0 for a NUL carrier and 1 for a SUL carrier).

[0207] The UE can transmit Msg 3 1313 in response to successfully receiving Msg 2 1312 (e.g., using the resources identified in Msg 2 1312). Msg 3 1313 can be used, for example, to Figure 13A contention resolution in the contention-based random access procedure shown in FIG. 13B. In some scenarios, multiple UEs can transmit the same preamble to the base station, and the base station can provide a RAR corresponding to the UEs. If the multiple UEs interpret the RAR as corresponding to themselves, a collision can occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE does not use the identity of another UE by mistake. To perform contention resolution, the UE can include a device identifier in Msg 3 1313 (e.g., a TC-RNTI included in Msg 2 1312 and / or any other suitable identifier if a C-RNTI is assigned).

[0208] Msg 4 1314 can be received after or in response to the transmission of Msg 3 1313. If a C-RNTI is included in 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, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE can determine that contention resolution is successful and / or the UE can determine that the random access procedure is successfully completed.

[0209] A UE can be configured with a supplemental uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., a random access procedure) can be supported in an uplink carrier. For example, a base station can configure a UE with two separate RACH configurations: one for a SUL carrier and another for a NUL carrier. To randomly access in a cell configured with a SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, a UE can determine a SUL carrier if a quality of a measurement of one or more reference signals is below a broadcast threshold. Uplink transmissions of a random access procedure (e.g., Msg 1 1311 and / or Msg 3 1313) can be reserved on the selected carrier. In one or more cases, a UE can switch uplink carriers during a random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, a UE can determine and / or switch an uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on a clear channel assessment (e.g., listen before talk).

[0210] Figure 13B A two-step contention-free random access procedure is shown. Similar to the four-step contention-based random access procedure shown in Figure 13A The base station can transmit a configuration message 1320 to the UE prior to initiation of the procedure. The configuration message 1320 can be similar in some aspects to the configuration message 1310. Figure 13B The procedure shown includes two messages of transmission: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some aspects to Msg 1 1311 and Msg 2 1312, respectively. Figure 13A The procedure shown includes two messages of transmission: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some aspects to Msg 1 1311 and Msg 2 1312, respectively. Figure 13A and Figure 13B It will be appreciated that the contention-free random access procedure can not include a message similar to Msg 3 1313 and / or Msg 4 1314.

[0211] The contention-free random access procedure shown can be initiated for beam failure recovery, other SI request, SCell addition, and / or handover. Figure 13B For example, the base station can indicate or assign a preamble to the UE to use for Msg 1 1321. The UE can receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0212] After transmitting the preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for a RAR. In the case of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. For example, the UE can determine that the random access procedure successfully completes if the PDCCH transmission is addressed to a C-RNTI. For example, the UE can determine that the random access procedure successfully completes if the UE receives a RAR that includes a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC subPDU with the preamble identifier. The UE can determine that the response is an indication of an acknowledgement of the SI request.

[0213] Figure 13C Another two-step random access procedure is shown. Similar to the random access procedures shown in Figure 13A and Figure 13B Similar to the random access procedures shown in Figure 13C The procedure shown includes transmission of two messages: Msg A 1331 and Msg B 1332.

[0214] Msg A 1331 can be transmitted by the UE in an uplink transmission. Msg A 1331 can include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 can include content similar to and / or equivalent to the content of Msg 3 1313 shown. Figure 13A The transport block 1342 can include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE can receive Msg B 1332 after or in response to transmitting Msg A 1331. Msg B 1332 can include content similar to and / or equivalent to the content of Msg 2 1312 (e.g., RAR) and / or Figure 13A and Figure 13B Msg 4 1314 shown. Figure 13A

[0215] The UE can initiate the random access procedure for a licensed spectrum and / or an unlicensed spectrum​ Figure 13C The UE can determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors can be: a radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; a cell size; an RRC state of the UE; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factor.

[0216] The UE can determine radio resources and / or uplink transmission power for the preamble 1341 and / or the transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters can indicate a modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or the transport block 1342. The time-frequency resources used for transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources used for transmission of the transport block 1342 (e.g., PUSCH) can be multiplexed using FDM, TDM, and / or CDM. The RACH parameters can enable the UE to determine a reception timing and a downlink channel for monitoring and / or receiving Msg B 1332.

[0217] The transport block 1342 can include 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 can transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 can include at least one of: 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 can determine that the two-step random access procedure is successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., the transport block 1342).

[0218] The UE and the base station can exchange control signaling. The control signaling can be referred to as L1 / L2 control signaling and can originate from a PHY layer (e.g., layer 1) and / or a MAC layer (e.g., layer 2). The control signaling can include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0219] Downlink control signaling can include: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; time slot format information; pre-emption indication; power control command; and / or any other suitable signaling. A UE can receive downlink control signaling in a payload transmitted by a base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH can be referred to as downlink control information (DCI). In some scenarios, the PDCCH can be a group common PDCCH (GC-PDCCH) common to a group of UEs.

[0220] A base station can attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When a DCI is intended for a UE (or a group of UEs), the base station can scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with an identifier can include a Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of a radio network temporary identifier (RNTI).

[0221] DCIs can be used for different purposes. The purpose can be indicated by a type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or a system information change notification. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or a trigger of PDCCH-ordered random access. A DCI with CRC parity check bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate a contention resolution (e.g., similar to a PDCCH order response). Figure 13AMsg 3 1313 (e.g., Msg 3 of the Msg 3 1313 shown). Other RNTIs configured to the UE by the base station can include: configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), and / or the like.

[0222] Depending on the purpose and / or content of the DCI, the base station can transmit DCI having one or more DCI formats. For example, DCI format 0_0 can be used for scheduling of PUSCH in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 can be used for scheduling of PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for scheduling of PDSCH in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for scheduling of PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used for providing slot format indication to a group of UEs. DCI format 2_1 can be used for informing a group of UEs of physical resource blocks and / or OFDM symbols where the UE can assume no transmission is expected to the UE. DCI format 2_2 can be used for transmission of transmission power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used for transmission of a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions can be defined in future releases. DCI formats can have different DCI sizes, or can share the same DCI size.

[0223] After scrambling the DCI with the RNTI, the base station can process the DCI with channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station can map the coded and modulated DCI on resource elements used and / or configured for the PDCCH. Based on a payload size of the DCI and / or a coverage range of the base station, the base station can transmit the DCI via the PDCCH occupying a number of contiguous control channel elements (CCEs). The number of contiguous CCEs, referred to as an aggregation level, can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE can include a number (e.g., 6) of resource element groups (REGs). A REG can include a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements can be based on a mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

[0224] Figure 14A An example of CORESET configuration of a bandwidth part is shown. The base station can transmit DCI via the PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources in which a UE attempts to decode DCI using one or more search spaces. The base station can configure a CORESET in the time-frequency domain. In an example, a first CORESET 1401 and a second CORESET 1402 occur at a 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 a seventh symbol in the slot. CORESETs can have different numbers of resource blocks in the frequency domain. Figure 14A

[0225] Figure 14B An example of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference coordination and / or frequency-selective transmission of control channels). The base station can perform different or the same CCE-to-REG mapping for different CORESETs. A CORESET can be associated with a CCE-to-REG mapping by RRC configuration. A CORESET can be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter can indicate QCL information for a demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0226] ​A base station can transmit, to a UE, an RRC message including configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters can indicate an association between a search space set and a CORESET. A search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can 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 a common search space set can be predefined and known to the UE. A set of CCEs in a UE-specific search space set can be configured based on an identity (e.g., C-RNTI) of the UE.

[0227] As shown in Figure 14B , a UE can determine time-frequency resources of a CORESET based on the RRC message. The UE can determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) of the CORESET based on the configuration parameters of the CORESET. The UE can determine a number (e.g., up to 10) of search space sets configured on the CORESET based on the RRC message. The UE can monitor a set of PDCCH candidates according to the configuration parameters of the search space sets. The UE can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. The monitoring can include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI formats. The monitoring can include decoding DCI contents of the one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., a number of CCEs, a number of PDCCH candidates in a common search space, and / or a number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. The decoding can be referred to as blind decoding. The UE can determine that a DCI is valid for the UE in response to a CRC check (e.g., a scrambled bit of CRC parity bits of the DCI matching an RNTI value). The UE can process information (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.) contained in the DCI.

[0228] A UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. Uplink control signaling transmissions can include a hybrid automatic repeat request (HARQ) acknowledgement for a received DL-SCH transport block. The UE can transmit the HARQ acknowledgement after receiving the DL-SCH transport block. Uplink control signaling can include channel state information (CSI) indicating a channel quality of a physical downlink channel. The UE can transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multi-antenna and beamforming schemes) for downlink transmissions. Uplink control signaling can include a scheduling request (SR). The UE can transmit an SR indicating that uplink data is available for transmission to the base station. The UE can transmit UCI (e.g., HARQ-ACK, CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE can transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0229] There can be five PUCCH formats, and the UE can determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of the UCI transmission and a number of UCI bits). PUCCH format 0 can have a length of one or two OFDM symbols and can include two or fewer bits. A wireless device can use PUCCH format 0 to transmit UCI in a PUCCH resource if more than one or two symbols are transmitted and a number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two. PUCCH format 1 can occupy a number between four and fourteen OFDM symbols and can include two or fewer bits. The UE can use PUCCH format 1 if four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. The UE can use PUCCH format 2 if more than one or two symbols are transmitted and the number of UCI bits is two or more. PUCCH format 3 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. The UE can use PUCCH format 3 if four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code. PUCCH format 4 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. The UE can use PUCCH format 4 if four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code.

[0230] The base station can transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, RRC messages. The multiple PUCCH resource sets (e.g., up to four sets) can be configured on an uplink BWP of a cell. A PUCCH resource set can be configured with: a PUCCH resource set index; a plurality of PUCCH resources (e.g., pucch-Resourceid) with a PUCCH resource identified by a PUCCH resource identifier; and / or a number (e.g., a maximum number) of UCI information bits that the UE can transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, the UE can select one of the multiple PUCCH resource sets (e.g., HARQ-ACK, SR, and / or CSI) based on a total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE can select a first PUCCH resource set with a PUCCH resource set index equal to “0”. If the total bit length of the UCI information bits is greater than two and less than or equal to a first configured value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to “1”. If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to “2”. If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to “3”.

[0231] After determining the PUCCH resource set from the multiple PUCCH resource sets, the UE can determine a PUCCH resource for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE can determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with DCI format 1_0 or 1_1) received on the PDCCH. The three-bit PUCCH resource indicator in the DCI can indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE can transmit the UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0232] Figure 15 An example of a wireless device 1502 in communication with a base station 1504 is shown in accordance with embodiments of the present disclosure. The wireless device 1502 and the base station 1504 can be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1. Figure 1A The mobile communication network 100, Figure 1B The mobile communication network 150 or any other communication network shown. Figure 15 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 can include more than one UE and / or more than one base station, with each having the same or similar configuration as those shown. Figure 15 The mobile communication network 150 or any other communication network shown.

[0233] The base station 1504 can connect the wireless device 1502 to a core network (not shown) through radio communication 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 the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions can be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0234] In the downlink, data to be sent from the base station 1504 to the wireless device 1502 can be provided to a processing system 1508 of the base station 1504. The data can be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent from the wireless device 1502 to the base station 1504 can be provided to a processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 can implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 can include, for example, an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer with respect to Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A Layer 3 can include an RRC layer with respect to Figure 2B .

[0235] After processing by the processing system 1508, the data to be sent to the wireless device 1502 can be provided to a transmission processing system 1510 of the base station 1504. Similarly, after processing by the processing system 1518, the data to be sent to the base station 1504 can be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 can implement layer 1 OSI functionality. Layer 1 can include a PHY layer with respect to Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A For transmission processing, the PHY layer can perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0236] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

[0237] like Figure 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. These multiple antennas can 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, wireless device 1502 and / or base station 1504 may have a single antenna.

[0238] Processing systems 1508 and 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more of the functions discussed in this application. Although Figure 15 Although not shown, the transmission processing system 1510, transmission processing system 1520, receiving processing system 1512 and / or receiving processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

[0239] The processing system 1508 and / or the processing system 1518 can include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors can include, 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, on-board components, or any combination thereof. The processing system 1508 and / or the processing system 1518 can perform at least one of the following: signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that can enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0240] The processing system 1508 and / or the processing system 1518 can be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touchpad, a power supply, 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, etc.). The processing system 1508 and / or the processing system 1518 can receive user input data from and / or provide user output data to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power supply and / or can be configured to distribute the power to the other components in the wireless device 1502. The power supply can include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0241] Figure 16AAn exemplary structure for uplink transmission is shown. A baseband signal representing a physical uplink shared channel can perform one or more functions. The one or more functions can include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and so on. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission can be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission can be generated by Figure 16A mapping of complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols for transmission on layers on an antenna port; mapping of complex-valued modulation symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for an antenna port; and so on. These functions are shown as examples, and other mechanisms can be implemented in various embodiments.

[0242] Figure 16B Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

[0243] Figure 16C An exemplary structure for downlink transmission is shown. A baseband signal representing a physical downlink channel can perform one or more functions. The one or more functions can include: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulating scrambled bits to generate complex-valued modulation symbols; mapping complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols for layers on an antenna port for transmission; mapping of complex-valued modulation symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for an antenna port; and so on. These functions are shown as examples, and other mechanisms can be implemented in various embodiments.

[0244] Figure 16D Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for an antenna port. Filtering can be employed prior to transmission.

[0245] A wireless device can receive, from a base station, one or more messages (e.g., RRC messages) that include configuration parameters for a plurality of cells (e.g., primary cells, secondary cells). The wireless device can 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 part of the configuration parameters) can include parameters of physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer for configuring the wireless device. For example, the configuration parameters can include parameters for configuring physical layer and MAC layer channels, bearers, and the like. For example, the configuration parameters can include parameters that indicate values of timers for physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0246] A timer can start running once it is started and continue running until it is stopped or until it expires. A timer can be started if it is not running or restarted if it is running. A timer can be associated with a value (e.g., a timer can start or restart from a certain value or can start from zero and expire once it reaches the value). The duration of a timer can not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer can be used to measure a time period / window of a procedure. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways of implementing the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing a timer can be used to measure a time period / window of a procedure. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In an example, instead of the start and expiration of a random access response window timer, a time difference between two timestamps can be used. When a timer is restarted, the measurement process of the time window can be restarted. Other example implementations can be provided to restart the measurement of the time window.

[0247] A wireless device can receive, for example, from a base station, downlink control information (DCI). The DCI can trigger / schedule a report, such as a channel state information (CSI) report. The CSI report can be, for example, an aperiodic CSI report. The CSI report can be, for example, a semi-persistent CSI report. The DCI can schedule repetitions of a transport block (e.g., PUSCH). In existing technologies, a wireless device can multiplex a CSI report in a first / earliest / starting repetition of a transport block. The wireless device can transmit the transport block with / carrying the CSI report in the first / earliest / starting repetition of the transport block.

[0248] In an example, a wireless device can be served (e.g., transmit to / receive from) by multiple TRPs including a first TRP and a second TRP. The wireless device can receive, among the first TRP and the second TRP, a DCI that schedules repetitions of a transport block (e.g., a PUSCH). The wireless device can transmit the transport block toward / to / for the first TRP in one or more first transmission occasions and toward / to / for the second TRP in one or more second transmission occasions. This can increase reliability of transmission of the transport block. For example, when the first TRP experiences blockage (e.g., due to a tree, a building, etc.), the second TRP can receive the transport block. The DCI can schedule / trigger a CSI report (e.g., an aperiodic CSI report). In prior art implementations, the wireless device can multiplex the CSI report in a first / earliest / starting repetition of the transport block. The wireless device can multiplex the CSI report in a first / starting / earliest transmission occasion among the one or more first transmission occasions and the one or more second transmission occasions. The wireless device can transmit the transport block with / carrying the CSI report in the first / earliest / starting repetition of the transport block (or in the first / starting / earliest transmission occasion). In an example, the first / earliest / starting repetition (or in the first / starting / earliest transmission occasion) can be associated with the first TRP. For example, based on blockage between the wireless device and the first TRP, the first TRP can not receive the transport block in the first / earliest / starting repetition of the transport block (or in the first / starting / earliest transmission occasion). The base station (or the first TRP) can not receive the CSI report based on not receiving the transport block. Multiplexing the CSI report in the first / earliest / starting repetition (or in the first / starting / earliest transmission occasion) associated with (or monitored by) the first TRP can not be efficient when there is blockage between the wireless device and the first TRP. This can result in retransmission of the DCI that triggers the CSI report. This can increase latency / delay of successful communication. This can increase power consumption at the base station and / or the wireless device.

[0249] Exemplary implementations enhance / improve CSI report multiplexing when a wireless device transmits repetitions of a transport block toward / toward / for multiple TRPs. In exemplary implementations, a wireless device can multiplex a CSI report in multiple repetitions (e.g., one or more first repetitions and one or more second repetitions) of a transport block, e.g., when a cyclic (beam) mapping is configured / activated. The wireless device can transmit a transport block with / carrying the CSI report in the first and second repetitions of the transport block, for example. In a cyclic (beam) mapping, the first and second repetitions can be associated with a first TRP and a second TRP, respectively. In exemplary implementations, a wireless device can multiplex a CSI report in a first repetition and a third repetition of a transport block, e.g., when a sequential (beam) mapping is configured / activated. The wireless device can transmit a transport block with / carrying the CSI report in the first and third repetitions of the transport block. In a sequential (beam) mapping, the first and third repetitions can be associated with a first TRP and a second TRP, respectively.

[0250] Multiplexing a CSI report in at least two repetitions of a transport block can be effective when there is a blockage between a wireless device and one of a first TRP and a second TRP. For example, when there is a blockage between the first TRP and the wireless device, the second TRP can receive the CSI report. This can increase the reliability of successful reception of the CSI report. This can reduce latency of successful communication. This can reduce power consumption at the base station and / or the wireless device.

[0251] In an example, a base station can configure one or more aperiodic trigger states (e.g., 1, 64, 128 aperiodic trigger states) for a wireless device using an information element (IE) CSI-AperiodicTriggerStateList. A codepoint of a CSI request field in a DCI can be associated with (or indicate) an aperiodic trigger state of the one or more aperiodic trigger states. In an example, an aperiodic trigger state can include one or more report configurations (e.g., 1, 8, 16 report configurations provided by a higher layer parameter associatedReportConfigInfoList). Based on receiving a DCI with the CSI request field indicating the aperiodic trigger state, the wireless device can perform measurements of CSI-RS and an aperiodic report according to the one or more report configurations (e.g., in associatedReportConfigInfoList) for the aperiodic trigger state.

[0252] In one example, a reporting configuration (e.g., provided by a higher layer parameter CSI-AssociatedReportConfigInfo) of the one or more reporting configurations can be identified / associated with a reporting configuration index (e.g., provided by a higher layer parameter CSI-ReportConfigId). In one example, a reporting configuration can include one or more CSI resources (e.g., 1, 8, 16 CSI resources). In one example, an aperiodic CSI resource of the one or more CSI resources can be associated with one or more TCI-State configured TCI states (provided by a higher layer parameter qcl-info in an IE CSI-AperiodicTriggerStateList). A TCI state can provide a QCL assumption (e.g., RS, RS source, SS / PBCH block, CSI-RS). A TCI state can provide a QCL type (e.g., QCL-TypeA, QCL-TypeD, etc.).

[0253] In an example, a wireless device can receive, from a base station, a DCI with a CSI request field. The wireless device can receive the DCI in a PDCCH. The wireless device can receive the DCI while monitoring the PDCCH. In an example, the DCI with the CSI request field can initiate / indicate / trigger an aperiodic trigger state of the one or more aperiodic trigger states. In an example, a codepoint of the CSI request field in the DCI can indicate the aperiodic trigger state. In one example, the aperiodic trigger state can include one or more reporting configurations (e.g., a list of NZP-CSI-RS-ResourceSet). In one example, a reporting configuration (e.g., NZP-CSI-RS-ResourceSet) of the one or more reporting configurations can include one or more CSI resources (e.g., aperiodic CSI-RS resources, NZP-CSI-RS-Resources).

[0254] In one example, the base station can not configure a higher layer parameter trs-Info for the reporting configuration. In one example, configuring the reporting configuration without the higher layer parameter trs-Info can include a first antenna port for a first aperiodic CSI resource of the one or more CSI resources being different from a second antenna port for a second aperiodic CSI resource of the one or more CSI resources. In one example, configuring the reporting configuration without the higher layer parameter trs-Info can include the antenna port for each aperiodic CSI-RS resource of the one or more CSI resources being different. In one example, the base station can not configure a higher layer parameter repetition for the reporting configuration. In one example, a scheduling offset between a last symbol of a PDCCH carrying the DCI and a first symbol of the one or more CSI resources in the reporting configuration can be less than a second threshold (e.g., beamSwitchTiming). In one example, the wireless device can report the second threshold. In one example, the second threshold can be a first value (e.g., 14, 28, 48 symbols).

[0255] In one example, an aperiodic CSI resource of the one or more CSI resources can be associated with a first TCI state of the one or more TCI-State configurations. In one example, the first TCI state can indicate at least one first RS. In one example, the first TCI state can indicate at least one first QCL type. In one example, the aperiodic CSI resource being associated with the first TCI state can include the wireless device receiving an aperiodic CSI-RS of the aperiodic CSI resource, the aperiodic CSI-RS having the at least one first RS (indicated by the first TCI state) with respect to the at least one first QCL type indicated by the first TCI state.

[0256] In one example, the base station can transmit a downlink signal with a second TCI state. In an example, the second TCI state can indicate at least one second RS. In an example, the second TCI state can indicate at least one second QCL type. The wireless device can receive the downlink signal in one or more first symbols. The wireless device can receive an aperiodic CSI-RS for an aperiodic CSI resource in one or more second symbols. In one example, the one or more first symbols and the one or more second symbols can overlap (e.g., in whole or in part). In an example, the downlink signal and the aperiodic CSI-RS (or aperiodic CSI-RS resource) can overlap based on the one or more first symbols and the one or more second symbols overlapping.

[0257] In an example, the downlink signal and the aperiodic CSI-RS (or aperiodic CSI-RS resource) can overlap in time duration. In an example, the time duration can be at least one symbol. In an example, the time duration can be at least one slot. In an example, the time duration can be at least one subframe. In an example, the time duration can be at least one mini-slot. In an example, the time duration can be the one or more second symbols. In an example, the time duration can be the one or more first symbols.

[0258] In an example, the downlink signal can be a PDSCH scheduled with an offset greater than or equal to a first threshold (e.g., Threshold-Sched-Offset, timeDurationForQCL). In an example, the downlink signal can be a second aperiodic CSI-RS scheduled with an offset greater than or equal to a second threshold (e.g., beamSwitchTiming) when the second threshold is a first value (e.g., 14, 28, 48 symbols). In an example, the downlink signal can be an RS (e.g., periodic CSI-RS, semi-persistent CSI-RS, SS / PBCH block, etc.).

[0259] In an example, the wireless device can apply the QCL assumption provided / indicated by the second TCI state when receiving the aperiodic CSI-RS based on the downlink signal with the second TCI state overlapping with the aperiodic CSI-RS (or aperiodic CSI-RS resource) when a scheduling offset between a last symbol and a first symbol of the PDCCH is less than a second threshold. In an example, applying the QCL assumption (provided / indicated by the second TCI state) when receiving the aperiodic CSI can include: the wireless device receiving the aperiodic CSI-RS, the aperiodic CSI-RS having the at least one second RS (indicated by the second TCI state) with respect to the at least one second QCL type (indicated by the second TCI state).

[0260] In one example, a scheduling offset between a last symbol of the PDCCH carrying the DCI and a first symbol of the one or more CSI resources in the reporting configuration can be equal to or greater than a second threshold (e.g., beamSwitchTiming). In one example, the wireless device can report the second threshold. In one example, the second threshold can be a first value (e.g., 14, 28, 48 symbols). Based on the scheduling offset being equal to or greater than the second threshold, the wireless device can apply the QCL assumption (provided by the first TCI state) for an aperiodic CSI resource of the one or more CSI resources in the reporting configuration. In an example, applying the QCL assumption (provided by the first TCI state) for the aperiodic CSI resource can include the wireless device receiving an aperiodic CSI-RS for the aperiodic CSI resource, the aperiodic CSI-RS having the at least one first RS (indicated by the first TCI state) with respect to the at least one first QCL type (indicated by the first TCI state).

[0261] Figure 17 and Figure 18 are examples of multiplexing in uplink channel repetition in accordance with aspects of the implementations of this disclosure.

[0262] Figure 19 are examples of uplink repetition schemes in accordance with aspects of the implementations of this disclosure.

[0263] The wireless device can receive one or more messages. In an example, the wireless device can receive the one or more messages from a base station. The one or more messages can include one or more configuration parameters. In an example, the one or more configuration parameters can be RRC configuration parameters. In an example, the one or more configuration parameters can be RRC reconfiguration parameters.

[0264] In an example, the one or more configuration parameters can be for a cell. In an example, at least one configuration parameter of the one or more configuration parameters can be for a cell. In an example, the cell can be a primary cell (PCell). In an example, the cell can be a secondary cell (SCell). The cell can be a PUCCH-configured secondary cell (e.g., PUCCH SCell). In an example, the cell can be an unlicensed cell operating, for example, in an unlicensed band. In an example, the cell can be a licensed cell operating, for example, in a licensed band. In an example, the cell can operate in a first frequency range (FR1). For example, FR1 can include frequency bands below 6 GHz. In an example, the cell can operate in a second frequency range (FR2). For example, FR2 can include frequency bands from 24 GHz to 52.6 GHz.

[0265] In an example, the wireless device can perform uplink transmission (e.g., PUSCH, PUCCH, SRS) via the cell at a first time and at a first frequency. The wireless device can perform downlink reception (e.g., PDCCH, PDSCH) via the cell at a second time and at a second frequency. In an example, the cell can operate in a time division duplex (TDD) mode. In the TDD mode, the first frequency and the second frequency can be the same. In the TDD mode, the first time and the second time can be different. In an example, the cell can operate in a frequency division duplex (FDD) mode. In the FDD mode, the first frequency and the second frequency can be different. In the FDD mode, the first time and the second time can be the same.

[0266] In an example, the wireless device can be in an RRC connected mode. In an example, the wireless device can be in an RRC idle mode. In an example, the wireless device can be in an RRC inactive mode.

[0267] In an example, the cell can include a plurality of BWPs. The plurality of BWPs can include one or more uplink BWPs including the uplink BWPs of the cell. The plurality of BWPs can include one or more downlink BWPs including the downlink BWPs of the cell.

[0268] In an example, a BWP of the plurality of BWPs can be in one of an active state and an inactive state. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, the wireless device can monitor for / over / via the downlink BWP a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH). In an example, in the active state of a downlink BWP of the one or more downlink BWPs, the wireless device can receive a PDSCH over / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can not monitor for / over / via the downlink BWP a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH). In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can stop monitoring (or receiving) a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) over / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can not receive a PDSCH over / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device can stop receiving a PDSCH over / via / for the downlink BWP.

[0269] In an example, in the active state of an uplink BWP of the one or more uplink BWPs, the wireless device can transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) over / via the uplink BWP. In an example, in the inactive state of an uplink BWP of the one or more uplink BWPs, the wireless device can not transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) over / via the uplink BWP.

[0270] In an example, the wireless device can activate a downlink BWP of the one or more downlink BWPs of the cell. In an example, activating the downlink BWP can include the wireless device setting (or switching) the downlink BWP to be an active downlink BWP of the cell. In an example, activating the downlink BWP can include the wireless device setting the downlink BWP to be in an active state. In an example, activating the downlink BWP can include switching the downlink BWP from an inactive state to an active state.

[0271] In an example, the wireless device can activate the uplink BWP of the one or more uplink BWPs of the cell. In an example, activating the uplink BWP can comprise the wireless device setting (or switching) the uplink BWP to be an active uplink BWP of the cell. In an example, activating the uplink BWP can comprise the wireless device setting the uplink BWP to be in an active state. In an example, activating the uplink BWP can comprise switching the uplink BWP from an inactive state to an active state.

[0272] In an example, the one or more configuration parameters can be for an (active) downlink BWP of the cell. In an example, at least one of the one or more configuration parameters can be for a downlink BWP of the cell.

[0273] In an example, the one or more configuration parameters can be for an (active) uplink BWP of the cell. In an example, at least one of the one or more configuration parameters can be for an uplink BWP of the cell.

[0274] In an example, the wireless device can transmit, e.g., to the base station, a UE capability message comprising the UE capability information.

[0275] In an example, the UE capability information can indicate / comprise support of beam correspondence without uplink beam sweeping (e.g., beamCorrespondenceWithoutUL-BeamSweeping). In an example, the wireless device can set a value of beamCorrespondenceWithoutUL-BeamSweeping in the UE capability message to a first value (e.g., one) to indicate support of beam correspondence without uplink sweeping. Based on the UE capability information indicating support of beam correspondence without uplink beam sweeping, the wireless device can determine / select a (suitable) beam (or spatial domain transmission filter) for uplink transmission based on downlink measurement values without relying on uplink beam sweeping. The wireless device can not determine / select a (suitable) beam (or spatial domain transmission filter) for uplink transmission based on uplink beam sweeping.

[0276] In an example, the UE capability information can indicate support of repetition of transmission of an uplink signal (e.g., PUCCH, PUSCH, transport block, SRS). For example, the repetition can be in TDM. For example, the repetition can be in FDM. For example, the repetition can be in SDM / SFN (e.g., spatial domain / time division multiplexing). For example, the repetition can be in CDM (e.g., code domain / time division multiplexing). The wireless device can repeat the transmission of the uplink signal, for example, based on the UE capability information indicating support of repetition of the uplink signal.

[0277] In an example, the wireless device can receive / detect a DCI (e.g., at time T0 in Figures 17 to 18

[0278] For example, the DCI can be DCI format 0-0. For example, the DCI can be DCI format 0-1. For example, the DCI can be DCI format 0-2. For example, the DCI can be DCI format 0-x, x = 0, 1, 2, 3,....

[0279] For example, the DCI can be DCI format 1-0. For example, the DCI can be DCI format 1-1. For example, the DCI can be DCI format 1-2. For example, the DCI can be DCI format 1-x, x = 0, 1, 2, 3,....

[0280] For example, the DCI can be DCI format 2-0. For example, the DCI can be DCI format 2-1. For example, the DCI can be DCI format 2-2. For example, the DCI can be DCI format 2-x, x = 0, 1, 2, 3,....

[0281] In an example, the DCI can schedule transmission of a transport block (e.g., PUSCH transmission). The DCI can schedule transmission of the transport block (e.g., the TB in Figures 17 to 18 In an example, the DCI can schedule transmission of a transport block (e.g., PUSCH transmission). The DCI can schedule transmission of the transport block (e.g., the TB in Figures 17 to 18 In an example, the DCI can schedule transmission of a transport block (e.g., PUSCH transmission). The DCI can schedule transmission of the transport block (e.g., the TB in

[0282] ​In an example, the one or more configuration parameters can indicate one or more configured uplink grants (e.g., by a higher layer parameter ConfiguredGrantConfig). The one or more configured uplink grants can comprise a configured uplink grant. In an example, the configured uplink grant can be a Type 2 configured uplink grant (or Configured Grant Type 2). In a Type 2 configured uplink grant, a PDCCH can indicate / provide an uplink grant. A DCI (or Layer 1 signaling) can indicate a configured uplink grant activation. Based on receiving the DCI indicating the configured uplink grant activation, the wireless device can store the uplink grant as the configured uplink grant. In an example, the DCI can activate the configured uplink grant. In an example, the wireless device can transmit a transport block (e.g., a TB in PUSCH) on / via an uplink channel (e.g., PUSCH, PUCCH) for the configured uplink grant. The wireless device can transmit the transport block (e.g., a PUSCH transmission) via one or more periodic uplink resources of the configured uplink grant. The one or more periodic uplink resources can comprise uplink resources (e.g., PUSCH resources, PUCCH resources, SRS resources). The uplink channel can comprise the one or more periodic uplink resources. The (active) uplink BWP can comprise the uplink resources. Figures 17 to 18

[0283] In an example, the one or more configuration parameters can comprise a repetition type indicator parameter (e.g., pusch-RepTypeIndicator, pusch-RepTypeIndicatorDCI-0-2, pusch-RepTypeIndicatorDCI-0-1 in PUSCH-Config). The repetition type indicator parameter can be / indicate (or be set to) a repetition type. The repetition type can be, for example, a first repetition type (e.g., pusch-RepTypeA, PUSCH repetition type A). The repetition type can be, for example, a second repetition type (e.g., pusch-RepTypeB, PUSCH repetition type B).

[0284] In an example, for a configured uplink grant, the one or more configuration parameters can comprise a repetition type indicator parameter (e.g., pusch-RepTypeIndicator in rrc-ConfiguredUplinkGrant).

[0285] The wireless device can apply the repetition type to determine a time domain resource allocation for the transport block. The wireless device can determine the time domain resource allocation for the transport block based on the repetition type.

[0286] ​The DCI can comprise a time domain resource alignment (TDRA) field. The TDRA field can indicate a resource allocation table. The resource allocation table can be indicated, e.g., by one or more configuration parameters. The resource allocation table can be, e.g., pre-configured / fixed. The TDRA field can indicate a number of repetitions (e.g., numberofrepetitions) of a transport block. The resource allocation table can comprise the number of repetitions (e.g., numberofrepetitions). The number of repetitions (e.g., numberofrepetitions) can be present in the resource allocation table. In an example, the number of repetitions is equal to four (e.g., numberofrepetitions = 4). Figures 17 to 18 In an example, the number of repetitions is equal to four (e.g., pusch-AggregationFactor = 4).

[0287] In an example, the number of repetitions can be used for repetitions of a transport block via an uplink resource (or uplink channel) (e.g., PUCCH resource, SRS resource, PUSCH resource). In an example, one or more configuration parameters can indicate a plurality of uplink signal / channel transmission / repetition occasions (e.g., PUCCH transmission occasions, slots, nominal / actual PUSCH repetitions) for a transmission / repetition of a transport block. In an example, the DCI can indicate a plurality of uplink signal / channel transmission / repetition occasions (e.g., PUSCH transmission occasions, PUCCH transmission occasions) for a transmission / repetition of a transport block. In an example, the DCI can indicate a first / starting / earliest uplink signal / channel transmission / repetition occasion. Based on the first / starting / earliest uplink signal / channel transmission / repetition occasion, the wireless device can determine, for a transmission / repetition of a transport block, a plurality of uplink signal / channel transmission / repetition occasions comprising the first / starting / earliest uplink signal / channel transmission / repetition occasion. The wireless device can determine the first / starting / earliest uplink signal / channel transmission / repetition occasion, e.g., based on one or more fields (e.g., TDRA, FDRA, etc.) in the DCI. The number of uplink signal / channel transmission occasions can be, e.g., equal to the number of repetitions. Figures 17 to 18 In an example, the number of repetitions is equal to four (e.g., pusch-AggregationFactor = 4).

[0288] In an example, the number of repetitions can be used for repetitions of a transport block via an uplink resource (or uplink channel) (e.g., PUCCH resource, SRS resource, PUSCH resource). In an example, one or more configuration parameters can indicate a plurality of uplink signal / channel transmission / repetition occasions (e.g., PUCCH transmission occasions, slots, nominal / actual PUSCH repetitions) for a transmission / repetition of a transport block. In an example, the DCI can indicate a plurality of uplink signal / channel transmission / repetition occasions (e.g., PUSCH transmission occasions, PUCCH transmission occasions) for a transmission / repetition of a transport block. In an example, the DCI can indicate a first / starting / earliest uplink signal / channel transmission / repetition occasion. Based on the first / starting / earliest uplink signal / channel transmission / repetition occasion, the wireless device can determine, for a transmission / repetition of a transport block, a plurality of uplink signal / channel transmission / repetition occasions comprising the first / starting / earliest uplink signal / channel transmission / repetition occasion. The wireless device can determine the first / starting / earliest uplink signal / channel transmission / repetition occasion, e.g., based on one or more fields (e.g., TDRA, FDRA, etc.) in the DCI. The number of uplink signal / channel transmission occasions can be, e.g., equal to the number of repetitions.

[0289] In an example, the multiple uplink signal / channel transmission / repetition occasions can be / may include multiple PUSCH transmission occasions. Each of the multiple uplink signal / channel transmission / repetition occasions can be a respective PUSCH transmission occasion of the multiple PUSCH transmission occasions.

[0290] In an example, the multiple uplink signal / channel transmission / repetition occasions can be / may include multiple slots. Each of the multiple uplink signal / channel transmission / repetition occasions can be a respective slot of the multiple slots.

[0291] In an example, the multiple uplink signal / channel transmission / repetition occasions can be / may include multiple nominal PUSCH repetitions (or nominal PUSCH repetition transmission occasions). Each of the multiple uplink signal / channel transmission / repetition occasions can be a respective nominal PUSCH repetition of the multiple nominal PUSCH repetitions.

[0292] In an example, the multiple uplink signal / channel transmission / repetition occasions can be / may include multiple actual PUSCH repetitions (or actual PUSCH repetition transmission occasions). Each of the multiple uplink signal / channel transmission / repetition occasions can be a respective actual PUSCH repetition of the multiple actual PUSCH repetitions.

[0293] In an example, the multiple uplink signal / channel transmission / repetition occasions can be / may include multiple PUSCH repetitions (or PUSCH repetition transmission occasions). Each of the multiple uplink signal / channel transmission / repetition occasions can be a respective PUSCH repetition of the multiple PUSCH repetitions.

[0294] In an example, the wireless device can transmit the transport block across / multiple uplink signal / channel transmission / repetition occasions (e.g., at times T la–T ld in Figures 17 to 18 In an example, the wireless device can transmit the transport block across / multiple uplink signal / channel transmission / repetition occasions (e.g., at times T la–T ld in

[0295] The wireless device can repeat (transmission of) the transport block across / on / in multiple uplink signal / channel transmission / repetition occasions, for example, based on the TDRA field indicating the number of repetitions.

[0296] The wireless device can repeat (transmission of) the transport block across / on / in multiple uplink signal / channel transmission / repetition occasions, for example, based on the one or more configuration parameters indicating the number of repetitions.

[0297] For example, the one or more configuration parameters can indicate a repetition scheme (e.g., FDM scheme, TDM scheme, SFN scheme, SDM scheme, CDM scheme, etc.). In an example, the DCI can indicate the repetition scheme. The DCI can include one or more fields (e.g., SRI field, TCI field, antenna port field, etc.) indicating the repetition scheme. The repetition scheme can be for repetition of transmission (e.g., PUSCH transmission) of the transport block via an uplink resource (e.g., PUCCH resource, SRS resource, PUSCH resource). The repetition scheme can be (set to) e.g., time domain repetition (e.g., TDM in Figure 19 ). The repetition scheme can be (set to) e.g., frequency domain repetition (e.g., FDM in Figure 19 ). The repetition scheme can be (set to) e.g., code / spatial domain repetition (e.g., SDM / SFN in Figure 19 ). In an example, the repetition scheme is time domain repetition. Figures 17 to 18

[0298] The wireless device can repeat (transmission of) the transport block across / on / in multiple uplink signal / channel transmission / repetition occasions, for example, based on the one or more configuration parameters indicating the repetition scheme.

[0299] The repetition of the transport block can be e.g., time domain repetition (e.g., Figure 19 ​TDM, TDMSchemeA, TDMSchemeB). In time domain repetition, multiple uplink signal / channel transmission occasions can not overlap in time. Each of the multiple uplink signal / channel transmission occasions can have a non-overlapping time domain resource allocation with respect to other of the multiple uplink signal / channel transmission occasions. For example, a first uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can not overlap in time with a second uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions. The first uplink signal / channel transmission occasion and the second uplink signal / channel transmission occasion can be different. In time domain repetition, the multiple uplink signal / channel transmission occasions can or can not overlap in frequency. The multiple uplink signal / channel transmission / repetition occasions are Figure 19 a first TX occasion, a second TX occasion, a third TX occasion, and a fourth TX occasion in time domain repetition (e.g., TDM) in. In time domain repetition, the repetition of the transport block can be, for example, in / on a time unit (e.g., TDMed) in / on a time unit. For example, the wireless device can repeat transmission of the transport block across / on / in the time unit. For example, the time units can be consecutive. For example, the time units can not be consecutive (e.g., can have a time / symbol / slot gap). The number of time units can be equal to the number of repetitions. For example, the time unit can be a slot. For example, the time unit can be a mini-slot. For example, the time unit can be a time symbol (e.g., OFDM symbol). For example, the time unit can be a subframe. For example, the time unit can be an actual / nominal repetition. The multiple uplink signal / channel transmission occasions can be in / on a time unit. For example, a first uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can be in / on a first time unit of the time units. A second uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can be in / on a second time unit of the time units, and so on. The first time unit can be different from the second time unit. The first time unit can not overlap in time with the second time unit.

[0300] The repetition of the transport block can be, for example, a frequency domain repetition (e.g., Figure 19FDM, FDMSchemeA, FDMSchemeB, etc.) In frequency domain repetition, multiple uplink signal / channel transmission occasions can or can not overlap in time. In frequency domain repetition, multiple uplink signal / channel transmission occasions can not overlap in frequency. Each of the multiple uplink signal / channel transmission occasions can have non-overlapping frequency domain resource allocation with respect to other of the multiple uplink signal / channel transmission occasions. For example, a first uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can not overlap in frequency with a second uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions. The first uplink signal / channel transmission occasion and the second uplink signal / channel transmission occasion can overlap in time. The first uplink signal / channel transmission occasion and the second uplink signal / channel transmission occasion can be different. The multiple uplink signal / channel transmission / repetition occasions are Figure 19 a first TX occasion and a second TX occasion in frequency domain repetition (e.g., FDM) in. In frequency domain repetition, the repetitions of a transport block can occur, for example, in / on a frequency unit (e.g., a frequency, a PRB, a frequency band, a sub-band, a bandwidth part, a cell). For example, a wireless device can repeat a transmission of a transport block across / on / in a frequency unit. For example, the frequency units can be contiguous. For example, the frequency units can not be contiguous (e.g., can have frequency / PRB gaps). The number of frequency units can be equal to the number of repetitions. For example, the frequency unit can be a frequency band. For example, the frequency unit can be a physical resource block (PRB). For example, the frequency unit can be a BWP. For example, the frequency unit can be a cell. The multiple uplink signal / channel transmission occasions can occur in / on a frequency unit. For example, a first uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can occur in / on a first frequency unit of the frequency units. A second uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can occur in / on a second frequency unit of the frequency units, and so on. The first frequency unit can be different from the second frequency unit. The first frequency unit and the second frequency unit can not overlap in frequency.

[0301] The repetitions of a transport block can be, for example, code domain / spatial domain repetition (e.g., Figure 19SDM / SFN, SDM scheme, CDM scheme, SDMScheme, CDMScheme, etc. in the 3GPP specifications). In code / spatial domain repetition, the multiple uplink signal / channel transmission occasions can overlap in time. In code / spatial domain repetition, the multiple uplink signal / channel transmission occasions can overlap in frequency. In code / spatial domain repetition, the multiple uplink signal / channel transmission occasions can be an uplink signal / channel transmission occasion (e.g., or a single uplink signal / channel transmission occasion). Each of the multiple uplink signal / channel transmission occasions can be the same (or the same as the uplink signal / channel transmission occasion or the single uplink signal / channel transmission occasion). Each of the multiple uplink signal / channel transmission occasions can have an overlapping frequency domain resource allocation with respect to the other uplink signal / channel transmission occasions of the multiple uplink signal / channel transmission occasions. Each of the multiple uplink signal / channel transmission occasions can have an overlapping time domain resource allocation with respect to the other uplink signal / channel transmission occasions of the multiple uplink signal / channel transmission occasions. For example, a first uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions can overlap in time and frequency with a second uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions. The first uplink signal / channel transmission occasion (e.g., first TX occasion) and the second uplink signal / channel transmission occasion (e.g., second TX occasion) can be the same. The multiple uplink signal / channel transmission / repetition occasions are Figure 19 a first TX occasion and a second TX occasion in code / spatial domain repetition (e.g., SDM / SFN) in the 3GPP specifications). In code / spatial domain repetition, the first TX occasion and the second TX occasion can be the same (e.g., can overlap in time and frequency). In code / spatial domain repetition, the multiple uplink signal / channel transmission occasions can occur in a same frequency unit (e.g., frequency, PRB, frequency band, bandwidth part, cell). For example, a first frequency unit of the first uplink signal / channel transmission occasion and a second frequency unit of the second uplink signal / channel transmission occasion can overlap in frequency. The multiple uplink signal / channel transmission occasions can occur in a same time unit (e.g., symbol, actual / nominal repetition, mini-slot, slot, subframe, etc.). For example, a first time unit of the first uplink signal / channel transmission occasion and a second time unit of the second uplink signal / channel transmission occasion can overlap in time.

[0302] For example, in the 3GPP specifications Figures 17 to 18In an example, the multiple uplink signal / channel transmission occasions include a first uplink signal / channel transmission occasion (e.g., a first TX occasion, a first slot, a first actual / nominal repetition), a second uplink signal / channel transmission occasion (e.g., a second TX occasion, a second slot, a second actual / nominal repetition), a third uplink signal / channel transmission occasion (e.g., a third TX occasion, a third slot, a third actual / nominal repetition), and a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion, a fourth slot, a fourth actual / nominal repetition).

[0303] In an example, the wireless device can determine multiple spatial domain transmission filters. The wireless device can determine the multiple spatial domain transmission filters for transmission of the transport block.

[0304] The wireless device can perform transmission of the transport block with / using the multiple spatial domain transmission filters. The wireless device can transmit the transport block with / using the multiple spatial domain transmission filters.

[0305] The wireless device can determine multiple spatial domain transmission filters, e.g., for repetitions of the transport block. The wireless device can repeat transmission of the transport block with / using the multiple spatial domain transmission filters (e.g., at times T la–T ld in Figures 17 to 18 The wireless device can transmit the repetitions of the transport block with / using the multiple spatial domain transmission filters.

[0306] In an example, the wireless device can transmit the transport block across multiple uplink signal / channel transmission / repetition occasions (e.g., at times T la–T ld in Figures 17 to 18 The wireless device can transmit the transport block across / multiple uplink signal / channel transmission / repetition occasions with / using the multiple spatial domain transmission filters. The wireless device can transmit the transport block across / a respective uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions with / using a respective spatial domain transmission filter of the multiple spatial domain transmission filters. The wireless device can transmit the transport block in each uplink signal / channel transmission occasion of the multiple uplink signal / channel transmission occasions with / using a respective spatial domain transmission filter of the multiple spatial domain transmission filters.

[0307] The wireless device can transmit the transport block across / over / using one or more first uplink signal / channel transmission occasions of the plurality of uplink signal / channel transmission occasions with / using a first spatial domain transmission filter of the plurality of spatial domain transmission filters. The wireless device can transmit the transport block across / over / using one or more second uplink signal / channel transmission occasions of the plurality of uplink signal / channel transmission occasions with / using a second spatial domain transmission filter of the plurality of spatial domain transmission filters.

[0308] In Figure 17 , the one or more first uplink signal / channel transmission occasions are a first uplink signal / channel transmission occasion (e.g., a first TX occasion, a first slot, a first actual / nominal repetition at time T la) and a third uplink signal / channel transmission occasion (e.g., a third TX occasion, a third slot, a third actual / nominal repetition at time T lc). The one or more second uplink signal / channel transmission occasions are a second uplink signal / channel transmission occasion (e.g., a second TX occasion, a second slot, a second actual / nominal repetition at time T lb) and a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion, a fourth slot, a fourth actual / nominal repetition at time T ld).

[0309] In Figure 18 , the one or more first uplink signal / channel transmission occasions are a first uplink signal / channel transmission occasion (e.g., a first TX occasion, a first slot, a first actual / nominal repetition at time T la) and a second uplink signal / channel transmission occasion (e.g., a second TX occasion, a second slot, a second actual / nominal repetition at time T lb). The one or more second uplink signal / channel transmission occasions are a third uplink signal / channel transmission occasion (e.g., a third TX occasion, a third slot, a third actual / nominal repetition at time T lc) and a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion, a fourth slot, a fourth actual / nominal repetition at time T ld).

[0310] In an example, the number of repetitions can be two. The multiple uplink signal / channel transmission occasions can include a first uplink signal / channel transmission occasion (e.g., a first TX occasion) and a second uplink signal / channel transmission occasion (e.g., a second TX occasion). The wireless device can transmit the transport block in the first uplink signal / channel transmission occasion with / using the first spatial domain transmission filter. The wireless device can apply the first spatial domain transmission filter to the first uplink signal / channel transmission occasion. The wireless device can transmit the transport block in the second uplink signal / channel transmission occasion with / using the second spatial domain transmission filter. The wireless device can apply the second spatial domain transmission filter to the second uplink signal / channel transmission occasion.

[0311] In an example, the number of repetitions can be greater than (or more than) two. For example, the one or more configuration parameters can indicate / enable a circular mapping. The circular mapping can, for example, circularly enable / indicate mapping of the plurality of spatial domain transmission filters to the plurality of uplink signal / channel transmission occasions (e.g., circularly switch the spatial domain transmission filters). The wireless device can transmit the transport block in a first uplink signal / channel transmission occasion (e.g., a first TX occasion) of the plurality of uplink signal / channel transmission occasions with / using a first spatial domain transmission filter. The wireless device can apply the first spatial domain transmission filter to the first uplink signal / channel transmission occasion. The wireless device can transmit the transport block in a second uplink signal / channel transmission occasion (e.g., a second TX occasion) of the plurality of uplink signal / channel transmission occasions with / using a second spatial domain transmission filter. The wireless device can apply the second spatial domain transmission filter to the second uplink signal / channel transmission occasion. The same spatial domain transmission filter mapping pattern can continue to remaining uplink signal / channel transmission occasions of the plurality of uplink signal / channel transmission occasions, for example, based on the one or more configuration parameters indicating the circular mapping. The remaining uplink signal / channel transmission occasions can exclude the first uplink signal / channel transmission occasion and the second uplink signal / channel transmission occasion. For example, when the number of repetitions is equal to four, the plurality of uplink signal / channel transmission occasions can include the first uplink signal / channel transmission occasion, the second uplink signal / channel transmission occasion, a third uplink signal / channel transmission occasion (e.g., a third TX occasion), and a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion). The wireless device can transmit the transport block in the first uplink signal / channel transmission occasion and the third uplink signal / channel transmission occasion with / using the first spatial domain transmission filter. The wireless device can transmit the transport block in the second uplink signal / channel transmission occasion and the fourth uplink signal / channel transmission occasion with / using the second spatial domain transmission filter. For example, when the number of repetitions is equal to eight, the plurality of uplink signal / channel transmission occasions can include a first uplink signal / channel transmission occasion (e.g., a first TX occasion), a second uplink signal / channel transmission occasion (e.g., a second TX occasion), a third uplink signal / channel transmission occasion (e.g., a third TX occasion), a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion), a fifth uplink signal / channel transmission occasion (e.g., a fifth TX occasion), a sixth uplink signal / channel transmission occasion (e.g., a sixth TX occasion), a seventh uplink signal / channel transmission occasion (e.g., a seventh TX occasion), and an eighth uplink signal / channel transmission occasion (e.g., an eighth TX occasion).The wireless device can transmit the transport blocks in the first uplink signal / channel transmission occasion, the third uplink signal / channel transmission occasion, the fifth uplink signal / channel transmission occasion, and the seventh uplink signal / channel transmission occasion with / using the first spatial domain transmission filter. The wireless device can transmit the transport blocks in the second uplink signal / channel transmission occasion, the fourth uplink signal / channel transmission occasion, the sixth uplink signal / channel transmission occasion, and the eighth uplink signal / channel transmission occasion with / using the second spatial domain transmission filter. Figure 17 An example of a circular mapping is shown (e.g., the first spatial domain transmission filter is used for the first uplink signal / channel transmission occasion and the third uplink signal / channel transmission occasion, and the second spatial domain transmission filter is used for the second uplink signal / channel transmission occasion and the fourth uplink signal / channel transmission occasion).

[0312] In an example, the number of repetitions can be greater than (or more than) two. For example, the one or more configuration parameters can indicate / enable sequential mapping. The sequential mapping can enable, for example, sequentially mapping multiple spatial domain transmission filters to multiple uplink signal / channel transmission occasions (e.g., sequentially switching spatial domain transmission filters). The wireless device can transmit a transport block in a first uplink signal / channel transmission occasion (e.g., a first TX occasion) of the multiple uplink signal / channel transmission occasions and a second uplink signal / channel transmission occasion (e.g., a second TX occasion) of the multiple uplink signal / channel transmission occasions with / using a first spatial domain transmission filter. The wireless device can apply the first spatial domain transmission filter for the first uplink signal / channel transmission occasion and for the second uplink signal / channel transmission occasion. The wireless device can transmit a transport block in a third uplink signal / channel transmission occasion (e.g., a third TX occasion) of the multiple uplink signal / channel transmission occasions and a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion) of the multiple uplink signal / channel transmission occasions with / using a second spatial domain transmission filter. The wireless device can apply the second spatial domain transmission filter for the third uplink signal / channel transmission occasion and for the fourth uplink signal / channel transmission occasion. The same spatial domain transmission filter mapping pattern can continue to remaining uplink signal / channel transmission occasions of the multiple uplink signal / channel transmission occasions, for example, based on the one or more configuration parameters indicating sequential mapping. The remaining uplink signal / channel transmission occasions can not include the first uplink signal / channel transmission occasion, the second uplink signal / channel transmission occasion, the third uplink signal / channel transmission occasion, and the fourth uplink signal / channel transmission occasion. For example, when the number of repetitions is equal to four, the multiple uplink signal / channel transmission occasions can include the first uplink signal / channel transmission occasion, the second uplink signal / channel transmission occasion, the third uplink signal / channel transmission occasion (e.g., a third TX occasion), and the fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion). The wireless device can transmit a transport block in the first uplink signal / channel transmission occasion and the second uplink signal / channel transmission occasion with / using the first spatial domain transmission filter. The wireless device can transmit a transport block in the third uplink signal / channel transmission occasion and the fourth uplink signal / channel transmission occasion with / using the second spatial domain transmission filter.For example, when the number of repetitions is equal to eight, the multiple uplink signal / channel transmission occasions can include a first uplink signal / channel transmission occasion (e.g., a first TX occasion), a second uplink signal / channel transmission occasion (e.g., a second TX occasion), a third uplink signal / channel transmission occasion (e.g., a third TX occasion), a fourth uplink signal / channel transmission occasion (e.g., a fourth TX occasion), a fifth uplink signal / channel transmission occasion (e.g., a fifth TX occasion), a sixth uplink signal / channel transmission occasion (e.g., a sixth TX occasion), a seventh uplink signal / channel transmission occasion (e.g., a seventh TX occasion), and an eighth uplink signal / channel transmission occasion (e.g., an eighth TX occasion). The wireless device can transmit the transport block in the first uplink signal / channel transmission occasion, the second uplink signal / channel transmission occasion, the fifth uplink signal / channel transmission occasion, and the sixth uplink signal / channel transmission occasion with / using the first spatial domain transmission filter. The wireless device can transmit the transport block in the third uplink signal / channel transmission occasion, the fourth uplink signal / channel transmission occasion, the seventh uplink signal / channel transmission occasion, and the eighth uplink signal / channel transmission occasion with / using the second spatial domain transmission filter. Figure 18 An example of sequential mapping is shown (e.g., the first spatial domain transmission filter is used for the first uplink signal / channel transmission occasion and the second uplink signal / channel transmission occasion, and the second spatial domain transmission filter is used for the third uplink signal / channel transmission occasion and the fourth uplink signal / channel transmission occasion).

[0313] In an example, the wireless device can transmit the transport block across / over / in multiple uplink signal / channel transmission occasions with / using multiple spatial domain transmission filters based on the one or more configuration parameters indicating the repetition scheme.

[0314] In an example, the one or more configuration parameters can include an enabling parameter (e.g., PUSCH repetition, PUCCH repetition, enableTwoPLForPUSCH repetition, enableTwoPowerControlForPUSCH repetition, etc.). The enabling parameter can be set to “enabled.” The one or more configuration parameters can indicate “enabled” for the enabling parameter. The value of the enabling parameter can indicate / be “enabled.” The enabling parameter can be for the cell. The enabling parameter can enable determining / selecting multiple spatial domain transmission filters for a repetition of a transport block (e.g., a PUSCH transmission). The enabling parameter can enable determining / selecting multiple spatial domain transmission filters for a transmission of a transport block (e.g., a PUSCH transmission). The enabling parameter can enable determining / selecting multiple spatial domain transmission filters for a transmission of a transport block toward / toward multiple TRPs. In an example, the wireless device can transmit a transport block across / multiple uplink signal / channel transmission occasions with / using multiple spatial domain transmission filters based on the one or more configuration parameters including the enabling parameter set to “enabled.” In an example, the wireless device can transmit a transport block across / multiple uplink signal / channel transmission occasions with / using multiple spatial domain transmission filters based on the one or more configuration parameters including the enabling parameter.

[0315] In an example, the wireless device can transmit a transport block across / multiple uplink signal / channel transmission occasions with / using multiple spatial domain transmission filters based on the one or more configuration parameters indicating at least two SRS resource sets, where the SRS usage parameter is set to codebook. For each SRS resource set of the at least two SRS resource sets, the one or more configuration parameters can indicate the SRS usage parameter set to codebook.

[0316] In an example, the wireless device can transmit a transport block across / multiple uplink signal / channel transmission occasions with / using multiple spatial domain transmission filters based on the one or more configuration parameters indicating at least two SRS resource sets, where the SRS usage parameter is set to non-codebook. For each SRS resource set of the at least two SRS resource sets, the one or more configuration parameters can indicate the SRS usage parameter set to non-codebook.

[0317] In an example, the one or more configuration parameters can indicate (or one or more) CSI trigger states. The one or more configuration parameters can comprise a higher layer parameter CSI-AperiodicTriggerStateList indicating the one or more CSI trigger states. The one or more CSI trigger states can be one or more aperiodic CSI trigger states.

[0318] In an example, the DCI can schedule / trigger / indicate the CSI report. The DCI can comprise a CSI request field (e.g., CSI request in Figure 17 and Figure 18 ) scheduling / triggering the CSI report. A value (or a codepoint) of the CSI request field can indicate a CSI trigger state of the one or more CSI trigger states.

[0319] The CSI report can be, for example, an aperiodic CSI report. The CSI report can be, for example, a semi-persistent CSI report.

[0320] In an example, the CSI report can comprise one or more CSI reports.

[0321] The CSI trigger state can be associated with a CSI resource set. For the CSI trigger state, the one or more configuration parameters can indicate the CSI resource set. The one or more configuration parameters can comprise one or more CSI resource configuration parameters. For the CSI resource set, the one or more CSI resource configuration parameters can indicate a resource type. The resource type can be (or be set to) aperiodic (e.g., a time domain behavior of the resource configuration). The CSI resource set can comprise one or more reference signals (e.g., aperiodic CSI-RS, NZP CSI-RS, CSI-RS, CSI-IM, and / or SSB). The wireless device can measure, for example, the one or more reference signals for the CSI report. The wireless device can measure, for example, the one or more reference signals for channel measurement. The wireless device can measure a radio link quality (e.g., L1-RSRP, L3-RSRP, BLER, SINR, SNR, etc.) of the one or more reference signals. The wireless device can measure the one or more reference signals, for example, based on receiving the DCI scheduling / triggering the CSI report. The wireless device can include / add a measurement result (e.g., the radio link quality) of the one or more reference signals in the CSI report.

[0322] The one or more configuration parameters can indicate one or more CSI reporting configurations (e.g., CSI-ReportConfig). The CSI trigger state can be associated with a CSI reporting configuration of the one or more CSI reporting configurations. For the CSI reporting configuration, the one or more configuration parameters can indicate a reporting configuration type. The reporting configuration type can be (or be set to) aperiodic (e.g., time domain behavior of CSI reporting).

[0323] The wireless device can multiplex the CSI report in / on a first / starting / earliest uplink signal / channel transmission / repetition occasion (e.g., a first TX occasion) of the multiple uplink signal / channel transmission / repetition occasions at time T la in Figure 17 and Figure 18 Multiplexing the CSI report in the first / starting / earliest uplink signal / channel transmission / repetition occasion can include multiplexing the CSI report in / on a first / starting / earliest repetition of a transport block. The wireless device can transmit the first / starting / earliest repetition of the transport block in the first / starting / earliest uplink signal / channel transmission / repetition occasion.

[0324] The wireless device can multiplex the CSI report in / on a second / second starting / second earliest uplink signal / channel transmission / repetition occasion (e.g., a second TX occasion) of the multiple uplink signal / channel transmission / repetition occasions at time T lb in Figure 17 Multiplexing the CSI report in the second / second starting / second earliest uplink signal / channel transmission / repetition occasion can include multiplexing the CSI report in / on a second / second starting / second earliest repetition of a transport block. The wireless device can transmit the second / second starting / second earliest repetition of the transport block in the second / second starting / second earliest uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can multiplex the CSI report in / on the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0325] The wireless device can transmit the transport block across / on the multiple uplink signal / channel transmission / repetition occasions (e.g., at times T la - T ld in Figure 17 The wireless device can transmit the transport block in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion (e.g., at times T la and T lb in Figure 17transmit a transport block multiplexed with the CSI report in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion. The wireless device can transmit the transport block with the CSI report in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion. The wireless device can transmit the transport block and the CSI report in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion. The wireless device can transmit the transport block carrying / having the CSI report, for example, on / using the PUSCH. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can transmit the transport block carrying / having the CSI report (multiplexed with the CSI report) in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion.

[0326] The wireless device can not multiplex the CSI report in the third uplink signal / channel transmission / repetition occasion (or third repetition of the transport block, Figure 17 at time T_1c in the third TX occasion) and the fourth uplink signal / channel transmission / repetition occasion (or fourth repetition of the transport block, Figure 17 at time T_1d in the fourth TX occasion) in the time period T_1a–T_1b. The plurality of uplink signal / channel transmission / repetition occasions can include the third uplink signal / channel transmission / repetition occasion and the fourth uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not multiplex the CSI report in the third uplink signal / channel transmission / repetition occasion and the fourth uplink signal / channel transmission / repetition occasion.

[0327] For example, based on the one or more configuration parameters indicating the repetition scheme, the wireless device can multiplex the CSI report in / on the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0328] For example, based on the one or more configuration parameters including the enabling parameter set to “enabled”, the wireless device can multiplex the CSI report in / on the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0329] For example, based on the one or more configuration parameters including the enabling parameter, the wireless device can multiplex the CSI report in / on the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0330] For example, based on the one or more configuration parameters indicating the at least two SRS resource sets (where the SRS usage parameter is set to non-codebook), the wireless device can multiplex the CSI report in / on the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0331] For example, based on the one or more configuration parameters indicating the at least two SRS resource sets (where the SRS usage parameter is set to non-codebook), the wireless device can multiplex the CSI report in / on the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0332] The wireless device can multiplex the CSI report in / on a third / third starting / third earliest uplink signal / channel transmission / repetition occasion (e.g., a third TX occasion at time T_1c in Figure 18 The multiplexing of the CSI report in the third / third starting / third earliest uplink signal / channel transmission / repetition occasion can include multiplexing the CSI report in / on a third / third starting / third earliest repetition of a transport block. The wireless device can transmit the third / third starting / third earliest repetition of the transport block in the third / third starting / third earliest uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can multiplex the CSI report in / on the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0333] The wireless device can transmit the transport block across / multiple uplink signal / channel transmission / repetition occasions (e.g., at times T_1a - T_1d in Figure 18 The wireless device can transmit the transport block across / multiple uplink signal / channel transmission / repetition occasions (e.g., at times T_1a - T_1d in Figure 18transmit the transport block carrying the CSI report in the first uplink signal / channel transmission / repetition occasion and the third uplink signal / channel transmission / repetition occasion. The wireless device can transmit the transport block with the CSI report in the first uplink signal / channel transmission / repetition occasion and the third uplink signal / channel transmission / repetition occasion. The wireless device can transmit the transport block and the CSI report in the first uplink signal / channel transmission / repetition occasion and the third uplink signal / channel transmission / repetition occasion. The wireless device can transmit the transport block carrying / having the CSI report, e.g., on / using the PUSCH. For example, based on the one or more configuration parameters indicating / enabling the sequential mapping, the wireless device can transmit the transport block carrying / having the CSI report (multiplexed with the CSI report) in the first uplink signal / channel transmission / repetition occasion and the third uplink signal / channel transmission / repetition occasion.

[0334] The wireless device can not multiplex the CSI report in the second uplink signal / channel transmission / repetition occasion (or the second repetition of the transport block, Figure 18 at the second TX occasion at time T_1b in the second uplink signal / channel transmission / repetition occasion) and the fourth uplink signal / channel transmission / repetition occasion (or the fourth repetition of the transport block, Figure 18 at the fourth TX occasion at time T_1d in the fourth uplink signal / channel transmission / repetition occasion). The plurality of uplink signal / channel transmission / repetition occasions can comprise the second uplink signal / channel transmission / repetition occasion and the fourth uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling the sequential mapping, the wireless device can not multiplex the CSI report in the second uplink signal / channel transmission / repetition occasion and the fourth uplink signal / channel transmission / repetition occasion.

[0335] For example, based on the one or more configuration parameters indicating the repetition scheme, the wireless device can multiplex the CSI report in / on the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0336] For example, based on the one or more configuration parameters comprising the enabling parameter being set to “enabled”, the wireless device can multiplex the CSI report in / on the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0337] For example, based on the one or more configuration parameters comprising the enabling parameter, the wireless device can multiplex the CSI report in / on the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0338] For example, based on the one or more configuration parameters indicating the at least two SRS resource sets (with the SRS usage parameter set to non-codebook), the wireless device can multiplex the CSI report in / on the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0339] For example, based on the one or more configuration parameters indicating the at least two SRS resource sets (with the SRS usage parameter set to non-codebook), the wireless device can multiplex the CSI report in / on the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0340] Figure 20 is an example flow diagram of multiplexing in uplink channel repetition as aspects of embodiments of the present disclosure.

[0341] In an example, the wireless device can receive one or more messages. In an example, the wireless device can receive the one or more messages from a base station. The one or more messages can include one or more configuration parameters (e.g., RRC configuration parameters, RRC reconfiguration parameters) of a cell.

[0342] The one or more configuration parameters can indicate at least two SRS resource sets. In an example, for the at least two SRS resource sets, the one or more configuration parameters can indicate a SRS usage parameter set to codebook. In an example, for the at least two SRS resource sets, the one or more configuration parameters can indicate a SRS usage parameter set to non-codebook.

[0343] The one or more configuration parameters can indicate a first SRS usage parameter of a first SRS resource set of the at least two SRS resource sets. The first SRS usage parameter may, for example, be (set to) codebook. The first SRS usage parameter may, for example, be (set to) non-codebook. A second SRS usage parameter may, for example, be (set to) codebook. The second SRS usage parameter may, for example, be (set to) non-codebook. The first SRS usage parameter and the second SRS usage parameter can be the same (e.g., both codebook or both non-codebook).

[0344] The one or more configuration parameters can indicate a repetition type (e.g., PUSCH repetition type A, PUSCH repetition type B).

[0345] A wireless device can transmit a transport block. The wireless device can transmit the transport block via an active uplink BWP of a cell. The wireless device can repeat transmission of the transport block. The wireless device can transmit a repetition of the transport block. The wireless device can transmit the transport block across / on / in multiple uplink signal / channel transmission / repetition occasions (e.g., slots, sub-slots, PUSCH transmission / repetition occasions, nominal / actual repetitions, symbols). For a repetition of the transport block, the wireless device can transmit the transport block across / on / in multiple uplink signal / channel transmission / repetition occasions.

[0346] For example, a wireless device can receive a DCI.

[0347] For example, the DCI can schedule a transport block. The DCI can schedule a repetition of a transport block. The DCI can indicate a repetition of a transport block.

[0348] For example, the DCI can activate a configured uplink grant (e.g., a Type 2 configured uplink grant). The wireless device can transmit a transport block of the configured uplink grant. The DCI can indicate a repetition of a transport block.

[0349] In an example, the DCI can include a CSI request field that schedules / indicates / triggers a CSI report. The CSI report can be, for example, an aperiodic CSI report.

[0350] In an example, the wireless device can multiplex the CSI report in a first / starting / earliest repetition of the transport block. The wireless device can multiplex the CSI report in / on a first / starting / earliest uplink signal / channel transmission / repetition occasion of the multiple uplink signal / channel transmission / repetition occasions. The wireless device can transmit the first / starting / earliest repetition of the transport block in the first / starting / earliest uplink signal / channel transmission / repetition occasion.

[0351] In an example, one or more configuration parameters indicate / enable cyclic mapping. The one or more configuration parameters indicate / enable cyclic mapping of, for example, a PUSCH repetition. The one or more configuration parameters can not indicate / enable sequential mapping. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can multiplex the CSI report in a second / second starting / second earliest repetition of the transport block. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can multiplex the CSI report in / on a second / second starting / second earliest uplink signal / channel transmission / repetition occasion of the multiple uplink signal / channel transmission / repetition occasions. The wireless device can transmit the second / second starting / second earliest repetition of the transport block in the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0352] For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not multiplex the CSI report in the third / third- starting / third-earliest repetition of the transport block. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not multiplex the CSI report in / on the third / third- starting / third-earliest uplink signal / channel transmission / repetition occasion of the plurality of uplink signal / channel transmission / repetition occasions. The wireless device can transmit the third / third- starting / third- earliest repetition of the transport block in the third / third- starting / third- earliest uplink signal / channel transmission / repetition occasion.

[0353] For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not multiplex the CSI report in the fourth / fourth- starting / fourth-earliest repetition of the transport block. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not multiplex the CSI report in / on the fourth / fourth- starting / fourth-earliest uplink signal / channel transmission / repetition occasion of the plurality of uplink signal / channel transmission / repetition occasions. The wireless device can transmit the fourth / fourth- starting / fourth- earliest repetition of the transport block in the fourth / fourth- starting / fourth- earliest uplink signal / channel transmission / repetition occasion.

[0354] The wireless device can transmit a transport block multiplexed with (or carrying) the CSI report in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can transmit a transport block multiplexed with (or carrying) the CSI report in the first uplink signal / channel transmission / repetition occasion and the second uplink signal / channel transmission / repetition occasion.

[0355] The wireless device can not transmit the CSI report (or a transport block carrying the CSI report) in the third uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not transmit the CSI report (or a transport block carrying the CSI report) in the third uplink signal / channel transmission / repetition occasion.

[0356] The wireless device can not transmit the CSI report (or a transport block carrying the CSI report) in the fourth uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling cyclic mapping, the wireless device can not transmit the CSI report (or a transport block carrying the CSI report) in the fourth uplink signal / channel transmission / repetition occasion.

[0357] In an example, the one or more configuration parameters indicate / enable sequential mapping. The one or more configuration parameters indicate / enable sequential mapping of PUSCH repetition, for example. The one or more configuration parameters can not indicate / enable circular mapping. For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can multiplex the CSI report in a third / third starting / third earliest repetition of the transport block. For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can multiplex the CSI report in / on a third / third starting / third earliest uplink signal / channel transmission / repetition occasion of the plurality of uplink signal / channel transmission / repetition occasions. The wireless device can transmit the third / third starting / third earliest repetition of the transport block in the third / third starting / third earliest uplink signal / channel transmission / repetition occasion.

[0358] For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can not multiplex the CSI report in a second / second starting / second earliest repetition of the transport block. For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can not multiplex the CSI report in / on a second / second starting / second earliest uplink signal / channel transmission / repetition occasion of the plurality of uplink signal / channel transmission / repetition occasions. The wireless device can transmit the second / second starting / second earliest repetition of the transport block in the second / second starting / second earliest uplink signal / channel transmission / repetition occasion.

[0359] For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can not multiplex the CSI report in a fourth / fourth starting / fourth earliest repetition of the transport block. For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can not multiplex the CSI report in / on a fourth / fourth starting / fourth earliest uplink signal / channel transmission / repetition occasion of the plurality of uplink signal / channel transmission / repetition occasions. The wireless device can transmit the fourth / fourth starting / fourth earliest repetition of the transport block in the fourth / fourth starting / fourth earliest uplink signal / channel transmission / repetition occasion.

[0360] The wireless device can transmit the transport block multiplexed with (or carrying) the CSI report in the first uplink signal / channel transmission / repetition occasion and the third uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling sequential mapping, the wireless device can transmit the transport block multiplexed with (or carrying) the CSI report in the first uplink signal / channel transmission / repetition occasion and the third uplink signal / channel transmission / repetition occasion.

[0361] The wireless device can not transmit the CSI report (or the transport block carrying the CSI report) in the second uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling the sequential mapping, the wireless device can not transmit the CSI report (or the transport block carrying the CSI report) in the second uplink signal / channel transmission / repetition occasion.

[0362] The wireless device can not transmit the CSI report (or the transport block carrying the CSI report) in the fourth uplink signal / channel transmission / repetition occasion. For example, based on the one or more configuration parameters indicating / enabling the sequential mapping, the wireless device can not transmit the CSI report (or the transport block carrying the CSI report) in the fourth uplink signal / channel transmission / repetition occasion.

[0363] For the transmission of the transport block (e.g., the PUSCH transmission), the wireless device can determine one or more nominal repetitions (e.g., K nominal repetitions) of a second repetition type (e.g., a PUSCH repetition type B). The wireless device can determine a respective invalid symbol (e.g., a downlink symbol, a flexible symbol, and / or the like) of each of the one or more nominal repetitions. For example, a first nominal repetition of the one or more nominal repetitions can include a plurality of symbols of the transmission of the transport block. The wireless device can determine a first invalid symbol of the plurality of symbols in the first nominal repetition. For the transmission of the transport block, the wireless device can determine a first valid symbol of the plurality of symbols that is different from the first invalid symbol. In an example, a quantity (or a length / size) of the first valid symbol can be greater than zero. For example, based on the quantity of the first valid symbol being greater than zero, the first nominal repetition can include (or consist of) one or more actual repetitions. The one or more actual repetitions can include the first valid symbol. Each of the one or more actual repetitions can include a respective valid symbol of the first valid symbol. Each of the one or more actual repetitions can include a respective contiguous set of valid symbols of the first valid symbol. The wireless device can transmit the transport block in the respective contiguous set of valid symbols of each actual repetition within the slot. In an example, the wireless device can omit an actual repetition having a single symbol. The one or more actual repetitions can include the actual repetition.

[0364] A quantity of the one or more nominal repetitions can be equal to the quantity of repetitions (e.g., 4 nominal repetitions in the 4 repetitions). Figure 17 and Figure 18 4 nominal repetitions in the 4 repetitions).

Claims

1. A method for signal multiplexing in uplink channel repetition, the method comprising: receiving, by a wireless device, a downlink control information (DCI) that schedules: a transmission of a channel state information (CSI) report via a cell, wherein the CSI report is transmitted on a physical uplink shared channel (PUSCH) with a transport block; one or more first repetitions of the transport block on the PUSCH using a first spatial domain transmission filter; and one or more second repetitions of the transport block on the PUSCH using a second spatial domain transmission filter; and transmitting the CSI report via the cell only on: an earliest repetition of the one or more first repetitions of the transport block on the PUSCH; and an earliest repetition of the one or more second repetitions of the transport block on the PUSCH. multiplexing the CSI report on: the earliest repetition of the one or more first repetitions; and the earliest repetition of the one or more second repetitions, wherein the transmission of the CSI report via a cell is in response to the multiplexing.

2. The method of claim 1, further comprising:

3. The method of claim 2, further comprising skipping multiplexing the CSI report on one or more remaining repetitions of the one or more first repetitions and the one or more second repetitions of the transport block on the PUSCH, wherein the one or more remaining repetitions do not include: the earliest repetition of the one or more first repetitions; and the earliest repetition of the one or more second repetitions.

4. The method of claim 1, wherein the DCI further schedules a repetition of the transport block on the PUSCH in a transmission occasion, wherein each repetition of the one or more first repetitions and the one or more second repetitions is associated with a respective transmission occasion of the transmission occasion.

5. The method of claim 1, further comprising receiving, by the wireless device, one or more messages comprising one or more configuration parameters, wherein the one or more configuration parameters indicate one of PUSCH repetition Type A or PUSCH repetition Type B for one or more first repetitions of the transport block on the PUSCH and one or more second repetitions of the transport block on the PUSCH.

6. The method of claim 1, further comprising receiving, by the wireless device, one or more messages comprising one or more configuration parameters, wherein the one or more configuration parameters indicate a cyclic beam mapping.

7. The method of claim 1, wherein the CSI report is one of an aperiodic CSI report or a semi-persistent CSI report.

8. The method of claim 1, wherein a number of repetitions of the transport block on the PUSCH is equal to two, wherein the repetitions of the transport block on the PUSCH include: the one or more first repetitions; and the one or more second repetitions.

9. The method of claim 1, wherein: ​ ​ ​ ​ ​ ​ the earliest repetition of the one or more first repetitions is an earliest repetition of a plurality of first repetitions of a transport block on the PUSCH; and the earliest repetition of the one or more second repetitions is an earliest repetition of a plurality of second repetitions of a transport block on the PUSCH.

10. A wireless device for signal multiplexing in uplink channel repetition, the wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive a downlink control information (DCI) that schedules: a transmission of a channel state information (CSI) report via a cell, wherein the CSI report is transmitted on an uplink shared channel (PUSCH) with a transport block; one or more first repetitions of a transport block on the PUSCH using a first spatial domain transmission filter; and one or more second repetitions of a transport block on the PUSCH using a second spatial domain transmission filter; and transmit the CSI report via the cell only on: an earliest repetition of the one or more first repetitions of a transport block on the PUSCH; and an earliest repetition of the one or more second repetitions of a transport block on the PUSCH.

11. The wireless device of claim 10, wherein the instructions further cause the wireless device to multiplex the CSI report on: the earliest repetition of the one or more first repetitions; and the earliest repetition of the one or more second repetitions, wherein the transmission of the CSI report via a cell is in response to the multiplexing.

12. The wireless device of claim 11, wherein the instructions further cause the wireless device to skip multiplexing the CSI report on one or more remaining repetitions of the one or more first repetitions and the one or more second repetitions of the PUSCH, wherein the one or more remaining repetitions do not include: the earliest repetition of the one or more first repetitions; and the earliest repetition of the one or more second repetitions.

13. The wireless device of claim 10, wherein the DCI further schedules a repetition of a transport block on the PUSCH in a transmission occasion, wherein each repetition of the one or more first repetitions and the one or more second repetitions is associated with a respective transmission occasion of the transmission occasion.

14. The wireless device of claim 10, wherein the instructions further cause the wireless device to receive one or more messages comprising one or more configuration parameters, wherein the one or more configuration parameters indicate one of PUSCH repetition Type A or PUSCH repetition Type B for one or more first repetitions of a transport block on the PUSCH and one or more second repetitions of a transport block on the PUSCH. ​ ​ 15. The wireless device of claim 10, wherein the instructions further cause the wireless device to receive one or more messages comprising one or more configuration parameters, wherein the one or more configuration parameters indicate a cyclic beam mapping.

16. The wireless device of claim 10, wherein the CSI report is one of an aperiodic CSI report or a semi-persistent CSI report.

17. The wireless device of claim 10, wherein a number of repetitions of a transport block on the PUSCH is equal to two, wherein the repetitions of the transport block on the PUSCH comprise: the one or more first repetitions; and the one or more second repetitions.

18. A system for signal multiplexing for uplink channel transmission, comprising a base station, the base station comprising: one or more first processors; and a first memory storing first instructions that, when executed by the one or more first processors, cause the base station to transmit a downlink control information (DCI), the DCI scheduling: a transmission of a channel state information (CSI) report via a cell, wherein the CSI report is transmitted on an uplink shared channel (PUSCH) with a transport block; one or more first repetitions of the transport block on the PUSCH using a first spatial domain transmission filter; and one or more second repetitions of the transport block on the PUSCH using a second spatial domain transmission filter; and a wireless device, the wireless device comprising: one or more second processors; and a second memory storing second instructions that, when executed by the one or more second processors, cause the wireless device to: receive the DCI; and transmit the CSI report via the cell only on: an earliest repetition of the one or more first repetitions of the transport block on the PUSCH; and an earliest repetition of the one or more second repetitions of the transport block on the PUSCH. ​ ​ ​

Images