Method for random access procedure in multiple transmission and reception points

Abstract

A wireless device receives, via a first control resource set (coreset) of a first cell, a command to transmit a preamble via a second cell. Downlink control information (DCI) of a response to the preamble is received via a second coreset of the second cell. The reception of the DCI is based on a transmission configuration indicator (TCI) state of the second coreset in response to the first cell being different from the second cell.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefits of U.S. Provisional Application No. 62 / 880,880, filed July 31, 2019, and U.S. Provisional Application No. 62 / 882,069, filed August 2, 2019, the entire contents of which are hereby incorporated by reference. Attached Figure Description

[0003] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B An exemplary mobile communication network in which embodiments of the present disclosure may be implemented is shown.

[0005] Figure 2A and Figure 2B The new radio (NR) user plane and control plane protocol stacks are shown respectively.

[0006] Figure 3 It shows in Figure 2A An example of the services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A It shows the flow through Figure 2A An example downlink data stream of the NR user plane protocol stack.

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

[0009] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink.

[0010] Figure 6 This is an example diagram illustrating the RRC state transition of the UE.

[0011] Figure 7 An exemplary configuration is shown in which OFDM symbols are grouped into NR frames.

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

[0013] Figure 9 An example of bandwidth adaptation using three configured BWPs with NR carriers is shown.

[0014] Figure 10AThree carrier aggregation configurations with two component carriers are shown.

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

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

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

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

[0019] Figure 13A , Figure 13B and Figure 13C The four-step contention-based random access procedure, the two-step contention-free random access procedure, and another two-step random access procedure are shown respectively.

[0020] Figure 14A An example of the CORESET configuration for the bandwidth portion is shown.

[0021] Figure 14B An example of CCE-to-REG mapping for DCI transport is shown on CORESET and PDCCH processing.

[0022] Figure 15 An example of a wireless device communicating with a base station is shown.

[0023] Figure 16A , Figure 16B , Figure 16C and Figure 16D An exemplary structure for uplink and downlink transmission is shown.

[0024] Figure 17 An example of a configuration of a transmission configuration instruction according to an embodiment of this disclosure is shown.

[0025] Figure 18 Random access procedures according to an exemplary embodiment of this disclosure are shown.

[0026] Figure 19 Random access procedures according to an exemplary embodiment of this disclosure are shown.

[0027] Figure 20 Random access procedures according to an exemplary embodiment of this disclosure are shown.

[0028] Figure 21 A flowchart of a random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0029] Figure 22 A random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0030] Figure 23 A flowchart of a random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0031] Figure 24 A random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0032] Figure 25 A flowchart of a random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0033] Figure 26 A flowchart of a random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0034] Figure 27 A flowchart of a random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0035] Figure 28 A random access procedure in accordance with aspects of example embodiments of the present disclosure is shown.

[0036] Figure 29 A flowchart in accordance with aspects of example embodiments of the present disclosure is shown.

[0037] Figure 30 A flowchart in accordance with aspects of example embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0038] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented in various environments and scenarios and / or how the disclosed technology can be practiced. It will be apparent to those skilled in the relevant arts that various changes in form and detail can be made without departing from the scope of the present disclosure. Indeed, after reading the present disclosure, it will be apparent to one skilled in the relevant arts how to implement alternative embodiments. The embodiments of the present disclosure should not be limited by any of the described exemplary embodiments. Embodiments of the present disclosure will be described with reference to the drawings. Limitations, features and / or elements from the disclosed exemplary embodiments can be combined to form further embodiments within the scope of the present disclosure. The drawings are only for purposes of illustrating exemplary embodiments and are not to scale with the actual dimensions. The disclosed architecture is sufficiently flexible and configurable, such that it can be utilized in ways different from shown. For example, the actions listed in any flowchart can be reordered or used only optionally in some embodiments.

[0039] Embodiments can be configured to operate as desired. The disclosed mechanisms can be performed when certain criteria are met, e.g., in a wireless device, a base station, a radio environment, a network, a combination of the above, etc. Exemplary criteria can be based at least in part on, e.g., 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 the one or more criteria are met. Thus, exemplary embodiments that selectively implement the disclosed protocols can be implemented.

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

[0041] In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term ending in “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” indicates that one or more embodiments of the various embodiments can or can not employ a particular aspect set forth after the term “may.” As used herein, the terms “comprises” and “consists of’ recite one or more components of what is being described. The term “comprises” is interchangeable with “includes” and does not exclude that which is not listed from being included in what is being described. In contrast, “consists of’ provides a complete listing of one or more components of what is being described. As used herein, the term “based on” is to be interpreted as “based, at least in part, on,” and not, for example, “based solely on.” 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.

[0042] 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, the possible subsets of B = {celll, cell2} are: {celll}, {cell2}, and {celll, cell2}. The expression “based on” (or equivalently “at least based on”) indicates that the expression after the term “based on” is an example of one of a number of suitable possibilities that can or can not be employed in one or more of the various embodiments. The expression “in response to” (or equivalently “at least in response to”) indicates that the expression after the term “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 of the various embodiments. The expression “in dependence of” (or equivalently “at least in dependence of”) indicates that the expression after the term “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 of the various embodiments. The expression “employ / using” (or equivalently “at least employ / using”) indicates that the expression after the term “employ / using” is an example of one of a number of suitable possibilities that can or can not be employed in one or more of the various embodiments.

[0043] The term "configured" can relate to the capability of the device, whether the device is in an operational state or a non-operational state. "Configured" can mean a particular setting in the 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 the device to provide the device with particular characteristics, whether the device is in an operational state or a non-operational state. Terms such as "control message that causes in the device" can mean that the control message has parameters that can be used to configure a particular characteristic in the device or parameters that can be used to cause certain actions in the device, whether the device is in an operational state or a non-operational state.

[0044] In this disclosure, a parameter (or equivalently, a field or 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 example embodiments, 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.

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

[0046] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in the disclosure can be implemented in hardware and / or software (including firmware, resident software, micro-code, etc.) and / or wetware (i.e., humans and / or animals) and / or combinations thereof. For example, a module can be implemented in hardware, software / firmware (including a software routine, a software / firmware module, a software / firmware unit, etc.), or any combination thereof. It will be appreciated that a software module can reside in memory such as RAM, flash memory, or the like, and that the memory can be internal to or external to a processor or other element. A software module can be moved between storage devices and machines connected by various communications media as will be appreciated by those skilled in the art. A "processor" includes any hardware system, mathematics processing device, or related components that can include one or more central processing units (CPUs), microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or any other integrated circuits for controlling processing and computing arithmetic functions. The disclosure can also be implemented in software and / or firmware, including electronic structures formed using transistors, logic gates, and / or other circuitry, as will be appreciated by those skilled in the art. The results of the disclosed techniques are frequently used in conjunction with one another.

[0047] Figure 1A An example of a mobile communication network 100 in which embodiments of the 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 in Figure 1A the mobile communication network 100 comprises a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0048] The CN 102 can provide an interface for the wireless device 106 to one or more data networks (DN) 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 establish end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functions.

[0049] The RAN 104 can connect the CN 102 to wireless devices 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The direction of communication from the RAN 104 to the wireless devices 106 via the air interface is referred to as the downlink, and the direction of communication from the wireless devices 106 to the RAN 104 via the air interface is referred to 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 duplexing techniques.

[0050] The term “wireless device” can be used throughout this disclosure to refer to and encompass any mobile or fixed (non-mobile) device for which wireless communication is needed or is usable. For example, a wireless device can be a telephone, smartphone, tablet, computer, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle road-side unit (RSU), relay node, 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 / receive unit (WTRU), and / or wireless communication device.

[0051] 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 with 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 one 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).

[0052] The base stations included in the RAN 104 can include one or more sets of antennas for communicating with the wireless devices 106 over the air interface. For example, one or more base stations can include three sets of antennas to control three cells (or sectors), respectively. The size of a cell can be determined according to a range of a receiver (e.g., a base station receiver) that is capable of successfully receiving transmissions from a transmitter (e.g., a wireless device transmitter) operating in that cell. The cells of the base stations can together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0053] In addition to the three-sector site, other implementations of base stations are possible. For example, one or more base stations in the RAN 104 can be implemented as a sectored site with more or fewer than three sectors. One or more base stations in the RAN 104 can be implemented as an access point, as a baseband processing unit coupled with a number of remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. The baseband processing unit coupled with 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 retransmit radio signals received from a donor node. A relay node can perform the same / similar functions as a repeater node but can decode radio signals received from a donor node to remove noise before amplifying and retransmitting the radio signals.

[0054] The RAN 104 can be implemented as a homogeneous network of macro cell base stations, each having a similar antenna mode and a similar high level of transmit power. The RAN 104 can be implemented as a heterogeneous network of eNBs including macro eNBs, pico eNBs, femto eNBs, and / or other types of eNBs. A macro eNB can have a high level of transmit power and can be coupled with a full set of channels (e.g., one or more of a downlink shared channel, a downlink control channel, an uplink shared channel, and an uplink control channel). A pico eNB can have a lower level of transmit power than a macro eNB and can be coupled with a partial set of channels (e.g., one or more of a downlink shared channel, a downlink control channel, and an uplink shared channel). A femto eNB can have a lower level of transmit power than a macro eNB and can be coupled with a partial set of channels (e.g., one or more of a downlink shared channel and a downlink control channel). A femto eNB can be coupled with a full set of channels (e.g., one or more of a downlink shared channel, a downlink control channel, an uplink shared channel, and an uplink control channel) in a small cell network. A femto eNB can be coupled with a full set of channels (e.g., one or more of a downlink shared channel, a downlink control channel, an uplink shared channel, and an uplink control channel) in a small cell network.

[0055] The Third Generation Partnership Project (3GPP) was founded in 1998 to produce global specifications standardizing mobile communication networks, similar to the mobile communication network 100 in Figure 1A To date, 3GPP has produced specifications for three generations of mobile networks: third generation (3G) networks, referred to as Universal Mobile Telecommunications System (UMTS), fourth generation (4G) networks, referred to as Long Term Evolution (LTE), and fifth generation (5G) networks, referred to as 5G System (5GS). Embodiments of the present disclosure are described with reference to a RAN of a 3GPP 5G network, referred to as Next Generation RAN (NG-RAN). These embodiments can be applicable to RANs of other mobile communication networks, such as the RAN 104 in Figure 1A

[0056] Figure 1B ​Another exemplary mobile communication network 150 in which embodiments of the present disclosure can be implemented is shown. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). This can be compared with... Figure 1A These components are implemented and operated in the same or similar ways as the corresponding components described.

[0057] 5G-CN 152 provides UE 156 with interfaces to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. As part of the interface functionality, 5G-CN 152 can establish end-to-end connections between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs in 3GPP 4G networks, the foundation of 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of 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).

[0058] like Figure 1B As shown, 5G-CN 152 includes Access and Mobility Management Functions (AMF) 158A and User Plane Functions (UPF) 158B. For ease of explanation, in Figure 1B These are shown as a single component, AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. Functions that UPF 158B can perform include: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting the routing of service flows to the one or more DNs, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with the one or more DNs, and / or a pivot point supporting multihomed PDU sessions. UE 156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0059] 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 slicing support, and / or session management function (SMF) selection. NAS can mean functionality operating between a CN and a UE, and AS can mean functionality operating between a UE and a RAN.

[0060] The 5G-CN 152 can include one or more additional network functions not shown in FIG. 1 for the sake of 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). Figure 1B

[0061] 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, as shown by gNBs 160A and 160B (collectively, gNBs 160), and / or one or more ng-eNBs, as shown by ng-eNBs 162A and 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 for communicating with UEs 156 over 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 control three cells (or sectors), respectively. 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.

[0062] As Figure 1B ​As shown in FIG. 1, gNBs 160 and / or ng-eNBs 162 can be connected to 5G-CN 152 by means of NG interfaces and to other base stations over Xn interfaces. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections over a potential transport network, such as an Internet Protocol (IP) transport network. gNBs 160 and / or ng-eNBs 162 can be connected to UEs 156 by means of Uu interfaces. For example, as shown in FIG. 1, gNB 160A can be connected to UE 156A by means of a Uu interface. 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 As shown in FIG. 1, gNBs 160 and / or ng-eNBs 162 can be connected to 5G-CN 152 by means of NG interfaces and to other base stations over Xn interfaces. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections over a potential transport network, such as an Internet Protocol (IP) transport network. gNBs 160 and / or ng-eNBs 162 can be connected to UEs 156 by means of Uu interfaces. For example, as shown in FIG. 1, gNB 160A can be connected to UE 156A by means of a Uu interface. 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 The network elements in FIG. 1 are configured to exchange data and signaling messages and can include two planes: a user plane and a control plane. The user plane can handle data of interest to a user. The control plane can handle signaling messages of interest to network elements.

[0063] As shown in FIG. 1, gNBs 160 and / or ng-eNBs 162 can be connected to 5G-CN 152 by means of NG interfaces and to other base stations over Xn interfaces. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections over a potential transport network, such as an Internet Protocol (IP) transport network. gNBs 160 and / or ng-eNBs 162 can be connected to UEs 156 by means of Uu interfaces. For example, as shown in FIG. 1, gNB 160A can be connected to UE 156A by means of a Uu interface. 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

[0064] As shown in FIG. 1, gNBs 160 and / or ng-eNBs 162 can be connected to 5G-CN 152 by means of NG interfaces and to other base stations over Xn interfaces. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections over a potential transport network, such as an Internet Protocol (IP) transport network. gNBs 160 and / or ng-eNBs 162 can be connected to UEs 156 by means of Uu interfaces. For example, as shown in FIG. 1, gNB 160A can be connected to UE 156A by means of a Uu interface. 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

[0065] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those 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 operation.” 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.

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

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

[0068] Figure 2A An NR user plane protocol stack is shown in FIG. 4 that includes the five layers implemented in UE 210 and gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 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 PHYs 211 and 221 include medium access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. These four protocols can together make up layer 2 or the data link layer of the OSI model.

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

[0070] 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. PDCPs 214 and 224 can perform retransmission of undelivered packets, in-order delivery and reordering of packets, and removal of packets that are received in duplicate due to, for example, intra-gNB handover. PDCPs 214 and 224 can perform packet duplication to improve the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0071] Although Figure 3 Although not shown in FIG. 2, 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 a split bearer when a single radio bearer, such as one of the radio bearers provided by PDCPs 214 and 224 as a service to SDAPs 215 and 225, is handled by cell groups in dual connectivity. PDCPs 214 and 224 can map / de-map split radio bearers between RLC channels that belong to cell groups.

[0072] 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). Depending on the transmission mode the RLC is operating, the RLC can perform one or more of the functions described. The RLC configuration can be per logical channel, independent of numerologies and / or transmission time interval (TTI) duration. As Figure 3 indicated in FIG. 20, the RLCs 213 and 223 can provide RLC channels as a service to the PDCPs 214 and 224, respectively.

[0073] The MACs 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing can include multiplexing / demultiplexing of data units belonging to one or more logical channels into / from Transport Blocks (TB) 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 by means of 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 indicated in FIG. 20, the MACs 212 and 222 can provide logical channels as a service to the RLCs 213 and 223, respectively.

[0074] 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 necessary for transmission and reception of information 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 indicated in FIG. 20, the PHYs 211 and 221 can provide one or more transport channels as a service to the MACs 212 and 222, respectively.

[0075] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4AA downlink data flow is shown that flows through the NR user plane protocol stack to generate three IP packets (n, n+1, and m) that are two TBs at the gNB 220. An uplink data flow that flows through the NR user plane protocol stack can be similar to Figure 4A the downlink data flow depicted in

[0076] Figure 4A The downlink data flow begins when the SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A , the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in Figure 4A ) is added to the IP packets. Data units from / to higher protocol layers are referred to as service data units (SDUs) of the lower protocol layer, and data units to / from the lower protocol layer are referred to as protocol data units (PDUs) of the higher protocol layer. As shown in Figure 4A , a data unit from the SDAP 225 is an SDU of the lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

[0077] Figure 4A The remaining protocol layers in Figure 3 can perform their associated functions (e.g., as described with respect to Figure 4A ), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 can perform IP header compression and encryption and forward its output to the RLC 223. The RLC 223 can optionally perform segmentation (e.g., as shown with respect to IP packet m in Figure 4A ) and forward its output to the MAC 222. The MAC 222 can multiplex many RLC PDUs and can attach a MAC subheader to the RLC PDUs to form a transport block. In NR, the MAC subheader can be distributed throughout the MAC PDU, as shown in

[0078] Figure 4BAn exemplary format of a MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field to indicate the length of the MAC SDU to which the MAC subheader corresponds (e.g., in bytes); a logical channel identifier (LCID) field to identify the logical channel from which the MAC SDU originates to assist the process of demultiplexing; a flag (F) to indicate the size of the SDU length field; and a reserved bit (R) field for future use.

[0079] Figure 4B A MAC control element (CE) inserted by a MAC (such as MAC 223 or MAC 222) into a MAC PDU is further shown. For example, Figure 4B Two MAC CEs inserted into a MAC PDU are shown. The MAC CEs can be inserted at the beginning of a MAC PDU for downlink transmission (as shown in Figure 4B ) and at the end of a MAC PDU for uplink transmission. The MAC 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 CEs, and the MAC CEs can be identified with a reserved value in the LCID field to indicate the type of control information included in the MAC CEs.

[0080] 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.

[0081] Figure 5A and Figure 5BThe mapping between logical channels, transport channels, and physical channels is shown separately for the downlink and uplink. Information transfer takes place through 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, which are specific to a certain UE, or Common, 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:

[0082] - 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;

[0083] - 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;

[0084] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0085] - Dedicated Control Channel (DCCH), which is used to carry control messages to / from specific UEs to configure the UEs; and

[0086] - Dedicated Traffic Channel (DTCH), which is used to carry user data to / from specific UEs.

[0087] 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:

[0088] - Paging Channel (PCH), which is used to carry paging messages originating from the PCCH;

[0089] - Broadcast Channel (BCH), which is used to carry the MIB from the BCCH;

[0090] - Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from the BCCH;

[0091] - Uplink Shared Channel (UL-SCH), which is used to carry uplink data and signaling messages; and

[0092] - Random Access Channel (RACH), which is used to allow a UE to touch the network without any prior scheduling.

[0093] The PHY can use physical channels to pass information between the processing stages of the PHY. A physical channel can have a set of associated time-frequency resources that carry the information of one or several 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 include, for example:

[0094] - Physical Broadcast Channel (PBCH), which is used to carry the MIB from the BCH;

[0095] - Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH;

[0096] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI) that can include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

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

[0098] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI that can include HARQ acknowledgements, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and scheduling requests (SRs); and

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

[0100] Similar to physical control channels, the physical layer generates physical signals to support low-level operations of the physical layer. As Figure 5A and Figure 5B indicated in , the set of physical layer signals defined by NR includes: 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.

[0101] Figure 2B An exemplary NR control plane protocol stack is shown. As Figure 2BAs shown in the middle, the NR control plane protocol stack can use the same / similar first four protocol layers as the example NR user plane protocol stack. The four protocol layers include PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224. Rather than having SDAPs 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 controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0102] The NAS protocols 217 and 237 can provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 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.

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

[0104] Figure 6 is an example diagram illustrating RRC state transitions of a UE. The UE can be the UE 210. Figure 1A the wireless device 106, Figure 2A and Figure 2B the UE 210 depicted in FIGS. Figure 6 As shown in FIG. 6, a 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).

[0105] In 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. Figure 1B one of the gNBs 160 or ng-eNBs 162 depicted in FIG. Figure 2A and Figure 2B the gNB 220 depicted in FIG. 2; 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., related 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. Mobility of a UE while in RRC connected 602 can be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE can measure signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station 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 inactivation procedure 610.

[0106] In RRC idle 604, no RRC context can be established for the UE. In RRC idle 604, the UE can have no RRC connection with the base station. While in 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 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 RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which can involve a random access procedure, as discussed in more detail below.

[0107] In RRC inactive 606, a previously established RRC context is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in 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 RRC inactive 606 to RRC connected 602 through a connection resume procedure 614, or to RRC idle 604 through a connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0108] The 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 a 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 a UE at a cell group level, such that a paging message can be broadcast on cells 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 a 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 identified by a tracking area identifier (TAI), which are referred to as tracking areas.

[0109] A tracking area can be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) can provide the UE with a list of TAIs associated with the UE's registration area. If the UE moves to a cell associated with a TAI not included in the list of TAIs associated with the UE's registration area via cell reselection, the UE can perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0110] RAN areas can be used to track UEs at the RAN level. For a UE in an RRC inactive 606 state, a RAN notification area can be assigned to that UE. A RAN notification area can include one or more cell identities, a list of RAIs, or a list of TAIs. In the example, a base station can belong to one or more RAN notification areas. In the example, a cell can belong to one or more RAN notification areas. If a UE moves via cell reselection to a cell not included in its assigned RAN notification area, the UE can perform a notification area update to update its RAN notification area.

[0111] The base station that stores the RRC context for the UE, or the UE's last serving base station, can be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period when the UE remains in the anchor base station's RAN notification area and / or during the period when the UE remains in RRC inactivity 606.

[0112] gNB, such as Figure 1B The 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.

[0113] In NR, physical signals and physical channels (about Figure 5A and Figure 5BThe discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Prior to transmission, data can be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and split into F parallel symbol streams. The F parallel symbol streams can be treated as if they are in the frequency domain, and used as inputs to an inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. The F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at a carrier frequency. The F parallel symbol streams can be mixed using an FFT block prior to being processed by the IFFT block. This operation results in a discrete Fourier transform (DFT) precoded OFDM symbol, and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The inverse processing can be performed on the OFDM symbol at the receiver using an FFT block to recover the data mapped to the source symbols.

[0114] Figure 7 An example 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. The subframes can be divided into slots, which include, for example, 14 OFDM symbols per slot.

[0115] The duration of a time slot can depend on the set of parameters used for the OFDM symbols in that time slot. In NR, flexible parameter sets 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). Parameter sets can be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing can be scaled up by two powers from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration can be scaled down by two powers from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following combinations of subcarrier spacing / cyclic prefix duration: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0116] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with a higher subcarrier spacing has a shorter time slot duration and correspondingly more time slots per subframe. Figure 7 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). Figure 7 (The parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slot or sub-time slot transmissions.

[0117] Figure 8 An exemplary configuration of a time slot in the time and frequency domains of an NR carrier is shown. This time slot includes a resource element (RE) and a resource block (RB). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain via a subcarrier in the frequency domain, such as... Figure 8 As shown. RB spans twelve consecutive REs in the frequency domain, as... Figure 8 As shown. The NR carrier can be limited to a width of 275 RB or 275 × 12 = 3300 subcarriers. If this limitation is used, the NR carrier can be limited to 50, 100, 200, and 400 MHz for subcarrier spacing of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on the limitation of 400 MHz bandwidth per carrier.

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

[0119] 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.

[0120] 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.

[0121] 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.

[0122] For a downlink BWP from 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 the 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.

[0123] 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 numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. A UE can transmit an uplink transmission (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length) for the uplink BWP.

[0124] 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.

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

[0126] A base station can configure a UE with a BWP inactivity timer value for a PCell. A UE can start or restart the BWP inactivity timer at any appropriate time. For example, a UE can start or restart the BWP inactivity timer when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectrum operation or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than a default downlink BWP or an uplink BWP for an 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 an active downlink BWP to a default downlink BWP.

[0127] 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 an expiration of a BWP inactivity timer (e.g., in a case where the second BWP is a default BWP).

[0128] 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 a paired spectrum. In an 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.

[0129] 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 Figure 9 In the example shown in FIG. 9, 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 an initial active BWP, and BWP 904 can be a default BWP. The UE can switch between the BWPs at a switching point. In Figure 9 In the example of FIG. 9, the UE can switch from BWP 902 to BWP 904 at switching point 908. The switch at switching 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 BWP 904 as the active BWP. The UE can switch from active BWP 904 to BWP 906 at switching point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE can switch from active BWP 906 to BWP 904 at switching point 912 in response to an expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE can switch from active BWP 904 to BWP 902 at switching point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0130] 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 BWP 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 way that the UE would use those values for the primary cell.

[0131] 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 a UE, one serving cell per CC. A CC can have three configurations in the frequency domain.

[0132] 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 (band A) and positioned directly adjacent to each other within the band. In an intra-band non-contiguous configuration 1004, the two CCs are aggregated in the band (band A) and separated by a gap in the band. In an inter-band configuration 1006, the two CCs are in different bands (band A and band B).

[0133] 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 schemes (TDD or FDD). The 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.

[0134] When using CA, one of the aggregated cells for a UE can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE initially connects at RRC connection setup, re-establishment, 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 the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells for a UE can be referred to as secondary cells (SCells). In an example, an SCell can be configured after the PCell is configured for a UE. For example, an SCell 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).

[0135] 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 MAC CEs for SCell Activation / Deactivation. Figure 4B For example, a MAC CE can indicate which SCells (e.g., in a subset of configured SCells) for a UE 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).

[0136] 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, which is referred to as self-scheduling. DCI for a cell can be transmitted on another cell, which is referred to as cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ acknowledgements and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PUCCH of the PCell. For a large number of aggregated downlink CCs, the PUCCH of the PCell can become overloaded. Cells can be grouped into multiple PUCCH groups.

[0137] Figure 10B Examples of how aggregated cells can be configured into one or more PUCCH groups are shown. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In an example, PUCCH group 1010 can include PCell 1012 and SCell 1014. In an example, PUCCH group 1050 can include PCell 1052 and SCell 1054. Figure 10B In the example of PUCCH group 1010, the PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes, in this example, 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 CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In an example, if the aggregation unit depicted in FIG. 10 were not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell would transmit UCI related to the downlink CCs, and that PCell can become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, overloading can be prevented. Figure 10B In the example of PUCCH group 1010, the PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes, in this example, 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 CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In an example, if the aggregation unit depicted in FIG. 10 were not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell would transmit UCI related to the downlink CCs, and that PCell can become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, overloading can be prevented.

[0138] A physical cell ID and a cell index can be assigned for a cell that includes a downlink carrier and optional uplink carriers. The physical cell ID or cell index can identify the downlink carrier and / or uplink carriers of a cell, depending on the context in which the physical cell ID is used, for example. 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. By way of 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 for a cell that includes the first downlink carrier. The same / similar concept can apply to carrier activation, for example. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell that includes the first carrier is activated.

[0139] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, a HARQ entity can work on a serving cell. A transmission module can be generated according to the assignment / grant of each serving cell. The transmission module and potential HARQ retransmissions of the transmission module can be mapped to the serving cells.

[0140] 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). In the uplink, a UE can transmit one or more RSs to a base station (e.g., DMRS, PT-RS, and / or SRS, as Figure 5B shown). The PSS and SSS can be transmitted by a base station and used by a 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 a PSS, an SSS, and a PBCH. A base station can periodically transmit a burst of SS / PBCH blocks.

[0141] Figure 11A Examples of the structure and location 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 transmitted periodically (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 11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, location of the burst within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the numerology or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factors. In an example, a UE can assume a subcarrier spacing of SS / PBCH blocks based on the carrier frequency being monitored, unless the radio network configures the UE to assume a different subcarrier spacing.

[0142] An SS / PBCH block can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as Figure 11APSS, SSS, and 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.

[0143] A UE can not know the location of an SS / PBCH block in time and frequency domains (e.g., in a 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 the PSS is not found after a certain duration (e.g., 20 ms), the UE can search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a certain location in time and frequency domains, the UE can determine the locations of the SSS and 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 the CD-SSB.

[0144] 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 the PSS and SSS, respectively. The UE can determine a location of a frame boundary of the cell based on a location of the SS / PBCH block. By way of example, an SS / PBCH block can indicate that it has been transmitted according to a transmission mode in which SS / PBCH blocks in the transmission mode are a known distance from a frame boundary.

[0145] 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.

[0146] 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 delay, average gain, and / or spatial Rx parameter). The UE can not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indexes.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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 the time and frequency domain and a 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.

[0151] 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 instruct 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.

[0152] 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.

[0153] 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.

[0154] 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).

[0155] 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 a PDSCH with up to 3 DMRSs.

[0156] 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 by 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.

[0157] 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.

[0158] 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, an upper layer can configure a PUSCH with up to three DMRSs.

[0159] 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 indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). 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. By way of example, uplink PT-RS can be confined in the scheduled time / frequency duration of the UE.

[0160] 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 the higher layer parameter indicates beam management, SRS resources (e.g., with same / similar time domain behavior, periodic, aperiodic, etc.) in a set of SRS resources in the one or more SRS resource sets 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, which 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 from 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, when PUSCH and SRS are transmitted in a same slot, a UE can be configured to transmit SRS after the transmission of PUSCH and corresponding uplink DMRS.

[0161] 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.

[0162] 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 used to convey the second symbol on the antenna port from a channel used to convey the first symbol on the antenna port (e.g., a fading gain, a multipath delay, etc.). 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.

[0163] 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.

[0164] 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 the 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.

[0165] Figure 11B The three beams shown can be configured for a UE in a UE-specific configuration. Figure 11B Three beams (Beam #1, Beam #2, and Beam #3) are shown 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.

[0166] 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 multiple 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, MAC CE, and / or DCI). The 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 the 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 the 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.

[0167] 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.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0168] 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 rows 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 rows 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.

[0169] 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 rows 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 rows 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.

[0170] 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.).

[0171] 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 a RS resource. A base station can indicate that a RS resource is quasi co-located (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, etc.). The one or more DMRS 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.

[0172] 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 status 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 for an SCell addition.

[0173] 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).

[0174] 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.

[0175] 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.

[0176] 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).

[0177] 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). By way of 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.

[0178] 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.

[0179] 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.

[0180] 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 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 transmission timing of the UE, a scheduling grant for transmission of Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmission of a preamble, the UE can start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for Msg 2 1312. The UE can determine when to start the time window based on a 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 a last symbol of the preamble (e.g., at a first PDCCH occasion starting from an 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 a 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 an UL carrier indicator of the PRACH occasion. An example of the RA-RNTI can be as follows: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, 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 a frequency domain (e.g., 0 ≤ f_id<8), and ul_carrier_id can be an UL carrier used for the preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0181] 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. 13. 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).

[0182] 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 in Msg 3 1313, the UE can determine that contention resolution is successful and the UE can determine that the random access procedure is successfully completed.

[0183] 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 to use (NUL or SUL). For example, a UE can determine a SUL carrier if the 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).

[0184] Figure 13B A two-step contention-free random access procedure is shown. Similar to the four-step contention-based random access procedure shown, 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 transmission of two messages: 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 transmission of two messages: 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 As will be appreciated, a contention-free random access procedure can not include a message similar to Msg 3 1313 and / or Msg 4 1314.

[0185] 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, a base station can indicate or assign a preamble to a UE to use for Msg 1 1321. A UE can receive an indication of a preamble (e.g., ra-PreambleIndex) from a base station via PDCCH and / or RRC.

[0186] 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 is successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, the UE can determine that the random access procedure is successfully completed if the PDCCH transmission is addressed to a C-RNTI. For example, the UE can determine that the random access procedure is successfully completed 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.

[0187] Figure 13C Another two-step random access procedure is shown. Similar to the random access procedure shown in Figure 13A and Figure 13B The base station can transmit a configuration message 1330 to the UE prior to the initiation of the procedure. The configuration message 1330 can be similar in some aspects to the configuration message 1310 and / or the configuration message 1320. Figure 13C The procedure shown includes the transmission of two messages: Msg A 1331 and Msg B 1332.

[0188] The Msg A 1320 can be transmitted by the UE in an uplink transmission. The Msg A 1320 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 similar and / or equivalent content to the content of the Msg 3 1313 shown. Figure 13A The transport block 1342 can include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE can receive the Msg B 1350 after or in response to the transmission of the Msg A 1320. The Msg B 1350 can include similar and / or equivalent content to the content of the Msg 2 1312 (e.g., RAR) and / or the Msg 4 1314 shown. Figure 13A and Figure 13B The Msg B 1350 can include similar and / or equivalent content to the content of the Msg 2 1312 (e.g., RAR) and / or the Msg 4 1314 shown. Figure 13A The Msg B 1350 can include similar and / or equivalent content to the content of the Msg 2 1312 (e.g., RAR) and / or the Msg 4 1314 shown.

[0189] A UE can initiate a two-step random access procedure in 1330 for a licensed spectrum and / or an unlicensed spectrum. 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 factors. Figure 13C

[0190] The UE can determine radio resources and / or uplink transmission power for the preamble 1341 and / or 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 transport block 1342. Time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 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 1350.

[0191] 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).

[0192] 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.

[0193] ​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.

[0194] 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 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).

[0195] 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 bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate a contention resolution (e.g., with a PDCCH-ordered random access). Figure 13AThe 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 the like.

[0196] Depending on the purpose and / or content of the DCI, the base station can transmit DCI with one or more DCI formats. For example, DCI format 0_0 can be used for scheduling of PDSCH 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 a transmission power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 can be used for transmission of a set 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.

[0197] 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 of groups of resource elements (REGs) (e.g., 6). 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).

[0198] 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

[0199] 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.

[0200] ​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.

[0201] 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 of search space sets configured on the CORESET (e.g., up to 10) 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 contained in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

[0202] 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 acknowledgements (HARQ-ACK), CSI reports, 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.

[0203] 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 a 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 a 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, a number of UCI bits is two or more, and a 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, a number of UCI bits is two or more, and a PUCCH resource includes an orthogonal cover code.

[0204] 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 based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of 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”.

[0205] 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.

[0206] Figure 15 An example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the disclosure is shown. 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. Figure 1A The mobile communication network 100, Figure 1B The mobile communication network 150 shown or any other communication network. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

[0207] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 is referred to as the downlink, while the communication direction from wireless device 1502 to base station 1504 via air interface 1506 is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using some combination of FDD, TDD, and / or two duplex technologies.

[0208] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 can be provided to processing system 1508 of base station 1504. This data can be provided to processing system 1508 via, for example, a core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 can be provided to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The three layers are SDAP, PDCP, RLC, and MAC. These three layers may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer. Figure 2B The RRC layer.

[0209] After being processed by processing system 1508, data to be transmitted to wireless device 1502 can be provided to transmission processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be transmitted to base station 1504 can be provided to transmission processing system 1520 of wireless device 1502. Transmission processing systems 1510 and 1520 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 transmission processing, the PHY layer can perform operations such as forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] 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 signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that can allow the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0214] 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 modulation (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.

[0215] 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 the following: 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 transforming the baseband signal. These functions are shown by way of example, and it is contemplated that other mechanisms can be implemented in various embodiments.

[0216] 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.

[0217] 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 on layers for transmission 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 by way of example, and it is contemplated that other mechanisms can be implemented in various embodiments.

[0218] 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.

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

[0220] 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 of the time window can be restarted. Other example implementations can be provided to restart the measurement of the time window.

[0221] In an example, a wireless device can receive, e.g., from a base station, a PDCCH order initiating a random access procedure (e.g., a contention-free random access procedure) for a cell (e.g., a PCell, a SCell). The wireless device can receive the PDCCH order via a coreset of the cell.

[0222] In an example, a base station can configure, by RRC, a coreset with a TCI state indicating a reference signal (e.g., a CSI-RS, a SSB). In an example, a base station can activate, by MAC CE, a coreset with a TCI state indicating a reference signal (e.g., a CSI-RS, a SSB). The reference signal can be a downlink reference signal.

[0223] In an example, based on receiving the PDCCH order, the wireless device can transmit a random access preamble of a random access procedure.

[0224] In an example, based on transmitting the random access preamble, the wireless device can start monitoring for a PDCCH scheduling / indicating a random access response. The PDCCH can include a DCI (e.g., DCI format 1 0) with a CRC scrambled by a RA-RNTI. In existing systems, the wireless device can receive the PDCCH scheduling / indicating the random access response based on a reference signal indicated by a TCI state of a coreset receiving the PDCCH order. In an example, the wireless device can receive the PDCCH scheduling / indicating the random access response via a second coreset of the cell. In an example, the second coreset receiving the PDCCH order and the coreset can be the same. In an example, the second coreset receiving the PDCCH order and the coreset can be different.

[0225] In an example, a wireless device can be served by multiple TRPs. The wireless device can receive / transmit via the multiple TRPs. A TRP of the multiple TRPs can be associated with a coreset group including one or more coresets. In an example, a TRP associated with a coreset group can transmit via the one or more coresets of the coreset group. In an example, a TRP not associated with a coreset group can not transmit via the one or more coresets of the coreset group.

[0226] In an example, a wireless device can receive a PDCCH order indicating a random access procedure via a first coreset of a first coreset group associated with a first TRP. In an example, a base station can configure (e.g., by RRC) or activate (e.g., by MAC CE) the first coreset with a TCI state indicating a reference signal (e.g., CSI-RS, SSB). The wireless device can transmit a random access preamble of a random access procedure. In an example, based on transmitting the random access preamble, the wireless device can start monitoring a second coreset of a second coreset group associated with a second TRP for a PDCCH scheduling / indicating a random access response.

[0227] When a wireless device receives a PDCCH order via a first core set group and receives a PDCCH scheduling / indicating a random access response via a second core set group different from the first core set group, existing PDCCH reception techniques for the PDCCH scheduling / indicating the random access response can be inefficient. For example, the first and second TRPs can use different beams (or reference signals) to serve (or transmit to) the wireless device. Based on a reference signal (or beam) indicated by a TCI state of a first core set in the first core set group, the wireless device can not receive a downlink signal (e.g., PDCCH) via a second core set in the second core set group. In an example, the wireless device can not receive the PDCCH scheduling / indicating the random access response via the second core set based on the first and second TRPs using different beams. In an example, the wireless device can receive the PDCCH scheduling / indicating the random access response via the second core set with an error based on the first and second TRPs using different beams. This can cause one or more retransmissions of the PDCCH scheduling / indicating the random access response, resulting in increased power consumption at the base station due to the retransmissions, increased power source / battery consumption at the wireless device due to increased monitoring durations, and increased latency of the random access procedure.

[0228] Exemplary embodiments implement an enhanced procedure for receiving a PDCCH indicating / scheduling a random access response when a wireless device receives a PDCCH order, initiating a random access procedure via a first core set in a first core set group, and initiating the random access response via a second core set in a second core set group different from the first core set group. In an example, a base station can configure / activate the second core set with a second TCI state indicating a second reference signal (e.g., CSI-RS, SSB). The second core set can be associated with a search space set (e.g., Type 1 CSS, ra-search space set, etc.). In an embodiment, the wireless device can receive the PDCCH indicating / scheduling the random access response based on the second reference signal of the second core set. In another embodiment, the base station can transmit the PDCCH indicating / scheduling the random access response via the second core set in the first core set group that received the PDCCH order. The base station can not transmit the PDCCH indicating / scheduling the random access response via the second core set in the second core set group different from the first core set group that the wireless device received the PDCCH order.

[0229] This enhanced procedure improves power control signaling, reduces uplink overhead / retransmissions and interference, reduces wireless device and base station power consumption, and reduces latency of the random access procedure.

[0230] Figure 17An example of a TCI state information element (IE) for downlink beam management in accordance with aspects of the present disclosure is shown.

[0231] In an example, a base station can configure one or more TCI states for a wireless device through a higher layer parameter PDSCH-Config for a serving cell (e.g., PCell, SCell). In an example, a wireless device can detect a PDCCH with DCI for the serving cell. The wireless device can use the one or more TCI states to decode a PDSCH scheduled by the PDCCH. The DCI can be intended for the wireless device and / or the serving cell of the wireless device.

[0232] In an example, a TCI state of the one or more TCI states can include one or more parameters (e.g., qcl-Type1, qcl-Type2, reference signal, etc.). In an example, the TCI state can be identified through a TCI state index (e.g., tci-StateId in Figure 17 ). The wireless device can use the one or more parameters in the TCI state to configure one or more quasi-co-location relationships between at least one downlink reference signal (e.g., SS / PBCH block, CSI-RS) and DM-RS ports of the PDSCH. In Figure 17 , a first quasi-co-location relationship of the one or more quasi-co-location relationships can be configured by a higher layer parameter qcl-Type1 for a first DL RS of the at least one downlink reference signal (e.g., indicated by a reference signal in Figure 17 ). In Figure 17 , a second quasi-co-location relationship of the one or more quasi-co-location relationships can be configured by a higher layer parameter qcl-Type2 (if configured) for a second DL RS of the at least one downlink reference signal (e.g., indicated by a reference signal in Figure 17 ).

[0233] In an example, the one or more TCI states can be configured through Figure 17A higher layer parameter qcl-Type in QCL-Info in the provides at least one quasi-co-location type of at least one downlink reference signal (e.g., the first DL RS, the second DL RS) to the wireless device. In an example, when at least two quasi-co-location relationships (including a first QCL type and a second QCL type) between at least two downlink reference signals and DM-RS ports of a PDSCH are configured, a first QCL type (e.g., QCL-TypeA, QCL-TypeB) of a first DL RS of the at least two downlink reference signals and a second QCL type (e.g., QCL-TypeC, QCL-TypeD) of a second DL RS of the at least two downlink reference signals can be different. In an example, the first DL RS and the second DL RS can be the same. In an example, the first DL RS and the second DL RS can be different.

[0234] Figure 18 is an example of a random access procedure in accordance with aspects of embodiments of the present disclosure.

[0235] In an example, a 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 comprise one or more configuration parameters. The one or more configuration parameters can comprise physical random access channel (PRACH) transmission parameters (e.g., a PRACH preamble format, time resources, and frequency resources for a PRACH transmission). The one or more configuration parameters can be for a cell (e.g., Figure 18 In an example, the PRACH transmission parameters can be (configured / indicated) for a PRACH transmission via the cell of the cell. In an example, the PRACH transmission parameters can be (configured / indicated) for a random access procedure of the cell. The cell can be a primary cell (PCell). The cell can be a secondary cell (SCell). The cell can be a PUCCH-configured secondary cell (e.g., a PUCCH SCell). In an example, the cell can be an unlicensed cell. In an example, the cell can be a licensed cell.

[0236] In an example, the one or more configuration parameters can indicate one or more control resource sets (coresets) for the cell. In an example, the one or more coresets can comprise a first coreset (e.g., Figure 18 In an example, the one or more coresets can comprise a second coreset (e.g., Figure 18 In an example, the one or more coresets can comprise a second coreset (e.g.,

[0237] In an example, the one or more configuration parameters can indicate a search space set index of the one or more search space sets (e.g., provided by a higher layer parameter searchSpaceld). In an example, each search space set of the one or more search space sets can be identified by a respective search space set index of the search space set indexes. In an example, a first search space set of the one or more search space sets can be identified by a first search space set index of the search space set indexes. In an example, a second search space set of the one or more search space sets can be identified by a second search space set index of the search space set indexes.

[0238] In an example, the one or more configuration parameters can indicate one or more search space sets of a downlink BWP of a cell (e.g., by a higher layer parameter SearchSpace). In an example, the one or more configuration parameters can indicate one or more search space sets of a cell (e.g., by a higher layer parameter SearchSpace).

[0239] In an example, the one or more configuration parameters can indicate a search space set index of the one or more search space sets (e.g., provided by a higher layer parameter searchSpaceld). In an example, each search space set of the one or more search space sets can be identified by a respective search space set index of the search space set indexes. In an example, a first search space set of the one or more search space sets can be identified by a first search space set index of the search space set indexes. In an example, a second search space set of the one or more search space sets can be identified by a second search space set index of the search space set indexes.

[0240] In an example, a search space set of the one or more search space sets can be associated with (or linked to) a core set of the one or more core sets. In an example, the one or more configuration parameters can indicate a core set (or a core set index of a core set) of a search space set (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). In an example, the association (or linkage) can be one-to-one. “One-to-one” can include that a search space set associated with (or linked to) a core set can not be associated with (or linked to) a second core set different from the core set.

[0241] In an example, the one or more configuration parameters can indicate a core set index of the one or more search space sets (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). In an example, each of the one or more search space sets can be associated with (or linked to) a core set of the one or more core sets identified by a respective one of the core set indexes. In an example, the one or more configuration parameters can indicate a first core set index of a first core set of a first search space set. The one or more configuration parameters can indicate the first core set index of the first core set in a first core set index field of the first search space set (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). Based on the one or more configuration parameters indicating the first core set index of the first core set of the first search space set, the first search space set can be associated with (or linked to) the first core set. In an example, the one or more configuration parameters can indicate a first core set index of a first core set of a second search space set. The one or more configuration parameters can indicate the first core set index of the first core set in a second core set index field of the second search space set (e.g., provided by a higher layer parameter controlResourceSetld in a higher layer parameter SearchSpace). Based on the one or more configuration parameters indicating the first core set index of the first core set of the second search space set, the second search space set can be associated with (or linked to) the first core set. In an example, the one or more configuration parameters can indicate a second core set index of a second core set of the first search space set. Based on the one or more configuration parameters indicating the second core set index of the second core set of the first search space set, the first search space set can be associated with (or linked to) the second core set. In an example, the one or more configuration parameters can indicate a second core set index of a second core set of the second search space set. Based on the one or more configuration parameters indicating the second core set index of the second core set of the second search space set, the second search space set can be associated with (or linked to) the second core set.

[0242] In an example, based on a search space set associated with (or linked to) a coreset, a wireless device can monitor a PDCCH candidate (e.g., DCI, PDCCH, RS, GC-PDCCH, DMRS, etc.) of a downlink control signal / channel in a PDCCH monitoring occasion for the search space set associated with (or linked to) the coreset. In an example, based on a search space set associated with (or linked to) a coreset, a wireless device can monitor a PDCCH candidate of a DCI in a PDCCH monitoring occasion for a search space set of the coreset associated with (or linked to) the search space set. In an example, based on a search space set associated with (or linked to) a coreset, a wireless device can monitor a PDCCH for a DCI of a search space set of the coreset associated with (or linked to) the search space set.

[0243] In an example, a wireless device can monitor a PDCCH for a DCI via one or more coresets based on one or more antenna port quasi-co-location properties (e.g., DM-RS antenna port quasi-co-location properties, such as antenna port QCL property 1, antenna port QCL property 2 in Figure 18 In an example, a wireless device can receive / detect a PDCCH containing a DCI via the one or more coresets based on the one or more antenna port quasi-co-location properties. In an example, a wireless device can receive / detect a PDCCH containing a DCI via each of the one or more coresets based on a respective antenna port quasi-co-location property of the one or more antenna port quasi-co-location properties. In an example, receiving / detecting a PDCCH via a coreset of the one or more coresets based on an antenna port quasi-co-location property of the one or more antenna port quasi-co-location properties can include at least one DM-RS port of the PDCCH being quasi-co-located (QCL-ed) with a reference signal indicated by (or in) the antenna port quasi-co-location property. An antenna port quasi-co-location property can include / indicate a reference signal (e.g., a Synchronization Signal (SS), a Channel State Information Reference Signal (CSI-RS), a Demodulation Reference Signal (DM-RS), etc.). Figure 18The antenna port quasi-colocation properties can include / indicate a reference signal index (e.g., ssb-index, csi-rs index, etc.) of the reference signal. The at least one DM-RS port of the PDCCH can be quasi-colocated (QCL-ed) with the reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters. The at least one DM-RS port of the PDCCH can be quasi-colocated (QCL-ed) with the reference signal with respect to a quasi-colocation type (e.g., QCL-TypeA, QCL-TypeB, QCL-TypeC, QCL-TypeD). The antenna port quasi-colocation properties can include / indicate the quasi-colocation type. The antenna port quasi-colocation properties can include / indicate the quasi-colocation type of the reference signal. In an example, when the at least one DM-RS port of the PDCCH is quasi-colocated (QCL-ed) with the reference signal with respect to QCL-TypeA, the at least one DM-RS port of the PDCCH can be quasi-colocated (QCL-ed) with the reference signal with respect to Doppler shift, Doppler spread, average delay, and delay spread. In an example, when the at least one DM-RS port of the PDCCH is quasi-colocated (QCL-ed) with the reference signal with respect to QCL-TypeB, the at least one DM-RS port of the PDCCH can be quasi-colocated (QCL-ed) with the reference signal with respect to Doppler shift and Doppler spread. In an example, when the at least one DM-RS port of the PDCCH is quasi-colocated (QCL-ed) with the reference signal with respect to QCL-TypeC, the at least one DM-RS port of the PDCCH can be quasi-colocated (QCL-ed) with the reference signal with respect to Doppler shift and average delay. In an example, when the at least one DM-RS port of the PDCCH is quasi-colocated (QCL-ed) with the reference signal with respect to QCL-TypeD, the at least one DM-RS port of the PDCCH can be quasi-colocated (QCL-ed) with the reference signal with respect to spatial RX parameters.

[0244] In an example, the wireless device can monitor the first PDCCH for the first DCI in the first coreset / via the first coreset based on a first antenna port quasi-colocation property (e.g., antenna port QCL property 1 in Figure 18 In an example, the wireless device can monitor the first PDCCH for the first DCI in the first coreset / via the first coreset based on a first antenna port quasi-colocation property (e.g., antenna port QCL property 1 in Figure 18 RS 1) quasi co-located (QCL-ed). Receiving / detecting the first PDCCH based on the first antenna port quasi co-location property in the first coreset / via the first coreset can include (the wireless device determining) that at least one first DM-RS port of the first PDCCH is received / used to receive the first PDCCH is quasi co-located with (or in) a first reference signal indicated by the first antenna port quasi co-location property (e.g., Figure 18 RS 1) quasi co-located (QCL-ed). The at least one first DM-RS port of the first PDCCH can be QCL-ed with the first reference signal with respect to a first quasi co-location type (e.g., QCLTypeD, QCL TypeA, etc.). The first antenna port quasi co-location property can include / indicate the first quasi co-location type. The first antenna port quasi co-location property can include / indicate the first quasi co-location type of the first reference signal.

[0245] In an example, the wireless device can monitor the second PDCCH for the second DCI in the second coreset / via the second coreset based on a second antenna port quasi co-location property (e.g., Figure 18 RS 2) quasi co-located (QCL-ed). Receiving / detecting the second PDCCH based on the second antenna port quasi co-location property in the second coreset / via the second coreset can include (the wireless device determining) that at least one second DM-RS port of the second PDCCH is received / used to receive the second PDCCH is quasi co-located with (or in) a second reference signal indicated by the second antenna port quasi co-location property (e.g., Figure 18 RS 2) quasi co-located (QCL-ed). Receiving / detecting the second PDCCH based on the second antenna port quasi co-location property in the second coreset / via the second coreset can include (the wireless device determining) that at least one second DM-RS port of the second PDCCH is received / used to receive the second PDCCH is quasi co-located with (or in) a second reference signal indicated by the second antenna port quasi co-location property (e.g., Figure 18 RS 2) quasi co-located (QCL-ed). The at least one second DM-RS port of the second PDCCH can be QCL-ed with the second reference signal with respect to a second quasi co-location type (e.g., QCLTypeD, QCL TypeA, etc.). The second antenna port quasi co-location property can include / indicate the second quasi co-location type. The second antenna port quasi co-location property can include / indicate the second quasi co-location type of the second reference signal.

[0246] In an example, the first antenna port quasi-co-location property and the second antenna port quasi-co-location property can be the same. In an example, the first antenna port quasi-co-location property and the second antenna port quasi-co-location property can be different.

[0247] In an example, the one or more configuration parameters can indicate one or more transmission configuration indicator (TCI) states of the one or more coresets. In an example, the one or more TCI states can include one or more first TCI states of the first coreset. The one or more TCI states can include one or more second TCI states of the second coreset.

[0248] In an example, the wireless device can receive one or more MAC CEs (e.g., TCI state indication for UE-specific PDCCH MAC CEs) activating one or more activated TCI states of the one or more TCI states of the one or more coresets. In an example, each of the one or more MAC CEs can activate a respective TCI state of a respective coreset of the one or more coresets. In an example, the wireless device can activate / use each of the one or more activated TCI states for a respective coreset of the one or more coresets. In an example, the wireless device can activate / use each of the one or more activated TCI states for a (single, only one) coreset of the one or more coresets. In an example, the (activated) one or more activated TCI states can be applicable for PDCCH reception (in the one or more coresets) in an active downlink BWP of the cell.

[0249] In an example, each TCI state of the one or more activated TCI states can include / indicate a respective antenna port quasi-co-location property of a respective coreset of the one or more coresets. In an example, a TCI state of the one or more activated TCI states can include / indicate an antenna port quasi-co-location property of a coreset among the one or more coresets. In an example, the TCI state and the antenna port quasi-co-location property of the coreset can be the same. The TCI state can include / indicate a reference signal of the antenna port quasi-co-location property of the coreset. The TCI state can include / indicate a quasi-co-location type of the antenna port quasi-co-location property of the coreset. The TCI state can include / indicate a quasi-co-location type of a reference signal.

[0250] In the example, the radio device may receive a first Medium Access Control (MAC) Element (e.g., a TCI state indication for a UE-specific PDCCH MAC CE) of the first TCI state in one or more first TCI states activating the first core set. In the example, the first MAC CE may have a field indicating a first TCI state index (e.g., provided by a higher-layer parameter tci-StateID). Based on this field indicating the first TCI state, the radio device may activate the first TCI state of the first core set. Receiving / detecting the first PDCCH in the first core set / via the first core set based on the quasi-co-addressable nature of the first antenna port may include receiving / detecting the first PDCCH in the first core set / via the first core set based on the first TCI state. Receiving / detecting the first PDCCH in the first core set / via the first core set based on the first TCI state may include (determined by the radio device) at least one DM-RS port of the first PDCCH and a first reference signal (e.g., in the first TCI state) indicated by the first TCI state. Figure 18 RS 1) Quasi-co-addressable (QCL-ed). The at least one first DM-RS port of the first PDCCH may be QCL-ed with respect to the first quasi-co-addressable type indicated by the first TCI state and the first reference signal. In the example, the first TCI state may include / indicate the quasi-co-addressable nature of the first antenna port of the first core set. In the example, the first TCI state and the quasi-co-addressable nature of the first antenna port of the first core set may be the same. The first TCI state may include / indicate / a first reference signal in / for the quasi-co-addressable nature of the first antenna port of the first core set. The first TCI state may include / indicate / a first quasi-co-addressable type in / for the quasi-co-addressable nature of the first antenna port of the first core set. The first TCI state may include / indicate the first quasi-co-addressable type of the first antenna port of the first core set.

[0251] In the example, the radio device can receive a second MAC CE (e.g., a TCI state indication for a UE-specific PDCCH MAC CE) of the second TCI state in one or more second TCI states activating the second core set. In the example, the second MAC CE may have a field indicating a second TCI state index of the second TCI state. Based on this field indicating the second TCI state, the radio device can activate the second TCI state of the second core set. Receiving / detecting the second PDCCH in the second core set / via the second core set based on the quasi-co-addressable nature of the second antenna port may include receiving / detecting the second PDCCH in the second core set / via the second core set based on the second TCI state. Receiving / detecting the second PDCCH in the second core set / via the second core set based on the second TCI state may include (determined by the radio device) at least one second DM-RS port of the second PDCCH and a second reference signal (e.g., indicated by the second TCI state or in the second TCI state) Figure 18 RS 2) QCL-ed. The at least one second DM-RS port of the second PDCCH may be QCL-ed with respect to the second quasi-co-address type indicated by the second TCI state. In the example, the second TCI state may include / indicate the quasi-co-address nature of the second antenna port of the second core set. In the example, the second TCI state and the quasi-co-address nature of the second antenna port of the second core set may be the same. The second TCI state may include / indicate / for the second reference signal in / for the quasi-co-address nature of the second antenna port of the second core set. The second TCI state may include / indicate / for the second quasi-co-address type in / for the quasi-co-address nature of the second antenna port of the second core set. The second TCI state may include / indicate / for the second quasi-co-address type of the second antenna port of the second core set.

[0252] In the example, the one or more active TCI states may include a first TCI state of a first core set and a second TCI state of a second core set.

[0253] In the example, the (activated) first TCI state can be applied to / used for the first PDCCH in the first core set of the (active) downlink BWP for the receiving cell. The (activated) first TCI state can be applied to / used for the first PDCCH in the first core set of the (active) downlink BWP for the receiving cell, which may include at least one first DM-RS port of the first PDCCH with respect to the first quasi-co-address type (e.g., QCL Type D) indicated by the first TCI state and the first reference signal (e.g., ...) indicated by the first TCI state. Figure 18RS-1) quasi co-located (QCL-ed). In an example, the (activated) first TCI state applicable / for receiving the first PDCCH in the first coreset can include the wireless device receiving the first PDCCH in / via the first coreset based on the first TCI state.

[0254] In an example, the (activated) second TCI state can be applicable / for receiving the second PDCCH in a second coreset of the (active) downlink BWP of the cell. The (activated) second TCI state applicable / for receiving the second PDCCH in the second coreset can include (the wireless device determining) at least one second DM-RS port of the second PDCCH is quasi co-located (QCL-ed) with a second reference signal (e.g., RS-2) indicated by the second TCI state. Figure 18 In an example, the (activated) second TCI state applicable / for receiving the second PDCCH in the second coreset can include the wireless device receiving the second PDCCH in / via the second coreset based on the second TCI state.

[0255] In an example, the one or more configuration parameters can not indicate a coreset (e.g., Figure 18one or more transmission configuration indicator (TCI) states (e.g., through higher layer parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) of one or more of the coresets (e.g., coreset 1, coreset 2) in the one or more configuration parameters. Based on the one or more TCI states of the coreset(s) not being indicated by the one or more configuration parameters, the wireless device can monitor PDCCH for the DCI in / via the coreset based on one or more of the antenna port quasi-co-location properties (e.g., DM-RS antenna port quasi-co-location properties) in the one or more configuration parameters. In an example, the wireless device can receive the PDCCH containing the DCI in / via the coreset based on the antenna port quasi-co-location property. Receiving the PDCCH in / via the coreset based on the antenna port quasi-co-location property can include (the wireless device determining) at least one DM-RS port of the PDCCH being quasi-co-located (QCL-ed) with a reference signal (e.g., SS / PBCH block, CSI-RS). The at least one DM-RS port of the PDCCH being quasi-co-located (QCL-ed) with the reference signal can include receiving the at least one DM-RS port of the PDCCH being quasi-co-located (QCL-ed) with the reference signal. The at least one DM-RS port of the PDCCH can be quasi-co-located (QCL-ed) with the reference signal with respect to a quasi-co-location type (e.g., QCL-TypeA, QCL-TypeD, etc.). In an example, the wireless device can use / identify the reference signal during a random access procedure. In an example, the wireless device can initiate a random access procedure of an initial access procedure. The random access procedure can be (initiated) for the initial access procedure. In an example, the one or more configuration parameters can not indicate one or more first TCI states of a first coreset. When the coreset is the first coreset, the reference signal can be a first reference signal (e.g., RS 1 in FIG. 6) and the antenna port quasi-co-location property can be a first antenna port quasi-co-location property of the first coreset. The one or more configuration parameters can not indicate one or more second TCI states of a second coreset. When the coreset is the second coreset, the reference signal can be a second reference signal (e.g., RS 2 in FIG. 6) and the antenna port quasi-co-location property can be a second antenna port quasi-co-location property of the second coreset. Figure 18 Figure 18

[0256] ​​In an example, the one or more configuration parameters can indicate a plurality of transmission TCI states (e.g., by higher layer parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) of a core set of the one or more core sets. In an example, the one or more configuration parameters can indicate the plurality of transmission TCI states of the core set for reconfiguration with a synchronization procedure (e.g., handover). In an example, the wireless device can not receive a MAC CE (e.g., TCI state indication for UE-specific PDCCH MAC CE) activating a TCI state of the plurality of TCI states of the core set. Based on the one or more configuration parameters indicating the plurality of transmission TCI states and not receiving the MAC CE, the wireless device can monitor PDCCH in / via the core set for DCI based on an antenna port quasi-co-location property (e.g., DM-RS antenna port quasi-co-location property). In an example, the wireless device can receive PDCCH in / via the core set with DCI based on the antenna port quasi-co-location property. Receiving PDCCH in / via the core set based on the antenna port quasi-co-location property can include (the wireless device determining) at least one DM-RS port of the PDCCH is quasi-co-located (QCL-ed) with a reference signal (e.g., SS / PBCH block, CSI-RS). The at least one DM-RS port of the PDCCH can be quasi-co-located (QCL-ed) with the reference signal with respect to a quasi-co-location type (e.g., QCL-TypeA, QCL-TypeD, etc.). In an example, the wireless device can use / identify the reference signal during / for a random access procedure. The random access procedure can be (initiated) for an initial access procedure. The random access procedure can be (initiated) by reconfiguration with a synchronization procedure. In an example, when the core set is a first core set, the reference signal can be a first reference signal (e.g., RS 1 in FIG. 7), and the antenna port quasi-co-location property can be a first antenna port quasi-co-location property of the first core set. In an example, when the core set is a second core set, the reference signal can be a second reference signal (e.g., RS 2 in FIG. 7), and the antenna port quasi-co-location property can be a second antenna port quasi-co-location property of the second core set. Figure 18 Figure 18

[0257] ​​In an example, the (or indicated) first reference signal in the first antenna port quasi-co-location property of the first coreset can be a reference signal used / identified by the wireless device during / for a random access procedure (e.g., initial access, reconfiguration with synchronization procedure). In an example, the (or indicated) second reference signal in the second antenna port quasi-co-location property of the second coreset can be a reference signal used / identified by the wireless device during / for a random access procedure (e.g., initial access, reconfiguration with synchronization procedure).

[0258] In an example, the one or more configuration parameters can indicate a coreset (e.g., a first coreset, a second coreset) in the one or more coresets. Figure 18a plurality of transmission TCI states (e.g., by higher layer parameters tci- StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) of a coreset (e.g., coreset 1, coreset 2) in a set of coresets. In an example, a coreset can be identified by a coreset index equal to zero. In an example, a coreset can be identified by a coreset index not equal to zero (e.g., non-zero). In an example, the wireless device can receive a MAC CE (e.g., TCI state indication for UE-specific PDCCH MAC CE) that activates a TCI state of the plurality of TCI states of the coreset. The TCI state can include / indicate a reference signal (e.g., SS / PBCH block, CSI-RS). The TCI state can include / indicate a quasi-co-location type (e.g., QCL TypeD, QCL TypeD). In an example, based on the one or more configuration parameters indicating the plurality of transmission TCI states and receiving the MAC CE that activates the TCI state, the wireless device can monitor PDCCH for DCI in the coreset / via the coreset based on an antenna port quasi-co-location property (e.g., DM-RS antenna port quasi-co-location property). Monitoring PDCCH for DCI in the coreset / via the coreset based on the antenna port quasi-co-location property can include monitoring PDCCH for DCI in the coreset / via the coreset based on the TCI state. In an example, the wireless device can receive / detect PDCCH with DCI in the coreset / via the coreset based on the antenna port quasi-co-location property. Receiving / detecting PDCCH in the coreset / via the coreset based on the TCI state can include (the wireless device determining) that at least one DM-RS port of the PDCCH is QCL-ed with a reference signal (in the TCI state) indicated by the TCI state. The at least one DM-RS port of the PDCCH can be QCL-ed with the reference signal with respect to a quasi-co-location type indicated by the TCI state. In an example, the TCI state can include / indicate an antenna port quasi-co-location property of the coreset. In an example, the TCI state and the antenna port quasi-co-location property of the coreset can be the same. The TCI state can include / indicate a reference signal of the antenna port quasi-co-location property of the coreset. The TCI state can include / indicate a quasi-co-location type of the antenna port quasi-co-location property of the coreset. The TCI state can include / indicate a quasi-co-location type of the reference signal. In an example, when the coreset is a first coreset, the reference signal can be a first reference signal (e.g., Figure 18 RS 1), the quasi-co-location type can be a first quasi-co-location type, the TCI state signal can be a first TCI state, and the antenna port quasi-co-location property can be a first antenna port quasi-co-location property of the first coreset. In an example, when the coreset is a second coreset, the reference signal can be a second reference signal (e.g., Figure 18 In RS 2), the quasi-co-address type can be the second quasi-co-address type, the TCI status signal can be the second TCI status, and the antenna port quasi-co-address property can be the second antenna port quasi-co-address property of the second core set.

[0259] In the example, the one or more configuration parameters can indicate the core set in the one or more core sets (e.g., Figure 18 The TCI states of core sets 1 and 2 (e.g., via higher-layer parameters tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) are considered. A TCI state can be a single TCI state of a core set. The number of TCI states in a core set can be one. A TCI state can include / indicate a reference signal (e.g., SS / PBCH block, CSI-RS). A TCI state can include / indicate a quasi-co-address type (e.g., QCL TypeD). In the example, based on the TCI states of the core sets indicated by one or more configuration parameters, the wireless device can monitor the PDCCH for DCI in / via the core set based on the antenna port quasi-co-address nature (e.g., DM-RS antenna port quasi-co-address nature). In the example, the wireless device can receive a PDCCH with DCI in / via the core set based on the antenna port quasi-co-address nature. In the example, receiving a PDCCH in the core set / via the core set based on the antenna port quasi-co-addressability may (determined by the radio device) include at least one DM-RS port of the PDCCH with reference signal quasi-co-addressability (QCL-ed) indicated / configured by the TCI status. Receiving a PDCCH in the core set / via the core set based on the antenna port quasi-co-addressability may (determined by the radio device) include at least one DM-RS port of the PDCCH with reference signal quasi-co-addressability (QCL-ed) indicated / configured by the TCI status regarding the quasi-co-addressability type indicated / configured by the TCI status.

[0260] In an example, the core set can be a first core set. In an example, a first TCI state of the first core set can comprise / indicate a first antenna port quasi-co-location property. In an example, the first TCI state of the first core set and the first antenna port quasi-co-location property can be the same. In an example, the wireless device can monitor, based on the first antenna port quasi-co-location property, a first PDCCH in / via the first core set for a first DCI. Monitoring the first PDCCH in / via the first core set based on the first antenna port quasi-co-location property can comprise the wireless device monitoring the first PDCCH in / via the first core set for the first DCI based on the first TCI state. The first TCI state can comprise / indicate a first reference signal in / for the first antenna port quasi-co-location property of the first core set. The first TCI state can comprise / indicate a first quasi-co-location type in / for the first antenna port quasi-co-location property of the first core set. Monitoring the first PDCCH in / via the first core set based on the first TCI state can comprise (the wireless device determining) that at least one first DM-RS port of the first PDCCH is quasi co-located (QCL-ed) with the first reference signal indicated / configured by the first TCI state with respect to the first quasi-co-location type indicated / configured by the first TCI state.

[0261] In an example, the core set can be a second core set. In an example, a second TCI state of the second core set can comprise / indicate a second antenna port quasi-co-location property. In an example, the second TCI state of the second core set and the second antenna port quasi-co-location property can be the same. In an example, the wireless device can monitor, based on the second antenna port quasi-co-location property, a second PDCCH in / via the second core set for a second DCI. Monitoring the second PDCCH in / via the second core set based on the second antenna port quasi-co-location property can comprise the wireless device monitoring the second PDCCH in / via the second core set for the second DCI based on the second TCI state. The second TCI state can comprise / indicate a second reference signal in / for the second antenna port quasi-co-location property of the second core set. The second TCI state can comprise / indicate a second quasi-co-location type in / for the second antenna port quasi-co-location property of the second core set. Monitoring the second PDCCH in / via the second core set based on the second TCI state can comprise (the wireless device determining) that at least one second DM-RS port of the second PDCCH is quasi co-located (QCL-ed) with the second reference signal indicated / configured by the second TCI state with respect to the second quasi-co-location type indicated / configured by the second TCI state.

[0262] In an example, a core set of the one or more core sets can be identified with a core set index equal to zero. The wireless device can monitor PDCCH for the DCI in / via the core set based on the antenna port quasi-co-location property. In an example, the wireless device can receive the PDCCH containing / including / having the DCI in / via the core set based on the antenna port quasi-co-location property. Receiving the PDCCH in / via the core set based on the antenna port quasi-co-location property can include (the wireless device determining) that at least one DM-RS port of the PDCCH is quasi co-located (QCL-ed) with a reference signal. The wireless device can use / identify the reference signal in / during a recent random access procedure. In an example, the recent random access procedure can not be initiated based on receiving the PDCCH command. In an example, the wireless device can not initiate the recent random access procedure based on receiving the PDCCH command. In an example, the latest / recent random access procedure can not be initiated based on receiving the PDCCH command triggering a non-contention based random access procedure. In an example, the wireless device can not receive a MAC CE (e.g., TCI state indication for UE-specific PDCCH MAC CE) activating a TCI state of the plurality of TCI states of the core set after the recent random access procedure. In an example, based on not receiving the MAC CE activating the TCI state of the core set after the recent random access procedure, the at least one DM-RS port of the PDCCH via the core set can be quasi co-located (QCL-ed) with the reference signal used / identified in / during the recent random access procedure. In an example, when the core set is a first core set (e.g., a first core set index equal to zero), the reference signal can be a first reference signal (e.g., RS 1 in FIG. 1), and the antenna port quasi-co-location property can be a first antenna port quasi-co-location property of the first core set. In an example, when the core set is a second core set (e.g., a second core set index equal to zero), the reference signal can be a second reference signal (e.g., RS 2 in FIG. 1), and the antenna port quasi-co-location property can be a second antenna port quasi-co-location property of the second core set. Figure 18 Figure 18

[0263] 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.

[0264] In an example, the one or more configuration parameters can indicate the one or more core sets on / for the downlink BWPs of the cell.

[0265] ​​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, an active state of a downlink BWP of the one or more downlink BWPs can include monitoring a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In an example, an active state of a downlink BWP of the one or more downlink BWPs can include receiving a PDSCH on / via the downlink BWP. In an example, an inactive state of a downlink BWP of the one or more downlink BWPs can include not monitoring a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for the downlink BWP. In an example, an inactive state of a downlink BWP of the one or more downlink BWPs can include not receiving a PDSCH on / via the downlink BWP.

[0266] In an example, an active state of an uplink BWP of the one or more uplink BWPs can include transmitting an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) via the uplink BWP. In an example, an inactive state of an uplink BWP of the one or more uplink BWPs can include not transmitting an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) via the uplink BWP.

[0267] 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 the downlink BWP as an active downlink BWP of the cell. In an example, activating the downlink BWP can include the wireless device setting the downlink BWP as 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.

[0268] In an example, the wireless device can activate an uplink BWP of the one or more uplink BWPs of the cell. In an example, activating the uplink BWP can include the wireless device setting the uplink BWP as an active uplink BWP of the cell. In an example, activating the uplink BWP can include the wireless device setting the uplink BWP as in an active state. In an example, activating the uplink BWP can include switching the uplink BWP from an inactive state to an active state.

[0269] In an example, a wireless device can receive a physical downlink control channel (PDCCH) order (e.g., a PDCCH order in Figure 18 ). The wireless device can receive the PDCCH order via a first core set (e.g., core set 1 in Figure 18 ) of the one or more core sets. The random access procedure can be a contention-free random access procedure (e.g., a contention-based random access procedure). The wireless device can initiate the random access procedure based on receiving the PDCCH order. The wireless device can initiate the random access procedure for a cell. The PDCCH order can initiate / trigger the random access procedure for the cell.

[0270] In an example, a wireless device can monitor a first PDCCH for a first DCI in a first core set based on a first antenna port quasi-co-location property (e.g., antenna port QCL property 1 in Figure 18 ). Monitoring the first PDCCH for the first DCI in the first core set based on the first antenna port quasi-co-location property can include the wireless device attempting to detect / receive the first PDCCH in the first core set based on the first antenna port quasi-co-location property. Monitoring the first PDCCH for the first DCI in the first core set based on the first antenna port quasi-co-location property can include at least one first DM-RS antenna port of the first PDCCH being quasi-co-located with a first reference signal (of the first antenna port quasi-co-location property) indicated by the first antenna port quasi-co-location property. The at least one first DM-RS port of the first PDCCH can be QCL-ed with the first reference signal with respect to a first quasi-co-location type (e.g., QCL TypeD, QCL TypeA, etc.). The first antenna port quasi-co-location property can include / indicate the first quasi-co-location type. The first antenna port quasi-co-location property can include / indicate the first quasi-co-location type of the first reference signal.

[0271] In an example, a wireless device can receive / detect a first PDCCH including a first DCI via a first coreset based on the first antenna port quasi-co-location property. In an example, the first DCI can indicate a PDCCH order to initiate a random access procedure. In an example, the wireless device can receive / detect a first PDCCH including a first DCI indicating a PDCCH order via a first coreset based on the first antenna port quasi-co-location property. The wireless device can receive the PDCCH order in / via the first coreset based on the first antenna port quasi-co-location property. In an example, based on the first DCI indicating the PDCCH order, the wireless device can receive the PDCCH order in / via the first coreset based on the first antenna port quasi-co-location property. Receiving / detecting the first PDCCH in / via the first coreset based on the first antenna port quasi-co-location property can include (the wireless device determining) that the at least one first DM-RS port of the first PDCCH is quasi co-located (QCLed) with a first reference signal (e.g., RS 1 in Figure 18 QCL TypeD, QCL TypeA, etc.) indicated by the first antenna port quasi-co-location property (in the first antenna port quasi-co-location property). The at least one first DM-RS port of the first PDCCH can be QCLed with the first reference signal with respect to a first quasi-co-location type (e.g., QCL TypeD, QCL TypeA, etc.).

[0272] In an example, based on receiving the PDCCH order, the wireless device can transmit a random access preamble of a random access procedure (e.g., Figure 18PDCCH order (e.g., preamble transmission in FIG. 16). The wireless device can transmit a random access preamble via at least one random access resource (e.g., PRACH occasion) of an active uplink BWP of a cell. The at least one random access resource can comprise at least one time resource. The at least one random access resource can comprise at least one frequency resource. A PRACH mask index field of the PDCCH order can indicate the at least one random access resource (e.g., PRACH occasion). The at least one random access resource can be associated with a reference signal index (e.g., SS / PBCH block index) of a reference signal indicated by a / PDCCH order reference signal index field in the PDCCH order. In an example, the wireless device can select the at least one random access resource indicated by the PRACH mask index field to transmit the random access preamble. In an example, a value of a random access preamble index field in the PDCCH order can not be zero (e.g., non-zero). In an example, the value of the random access preamble index field in the PDCCH order can be zero. The random access preamble index can indicate / identify a random access preamble. The wireless device can transmit the random access preamble indicated by the random access preamble index based on a reference signal identified by the reference signal index indicated by the / PDCCH order reference signal index field in the PDCCH order. In an example, the wireless device can transmit the random access preamble with a spatial transmission filter that is based on a spatial reception filter used to receive the reference signal.

[0273] In an example, based on transmitting the random access preamble, the wireless device can monitor (or start monitoring) for a second DCI (e.g., DCI format 1_0, DCI) in the cell. In an example, the second DCI can schedule a random access response (e.g., Msg2) containing a random access response (e.g., Msg2) to the random access preamble. In an example, the second DCI can schedule a random access response (e.g., Msg2) containing a random access response (e.g., Msg2) to the random access preamble. Figure 18 In an example, based on transmitting the random access preamble, the wireless device can monitor (or start monitoring) for a second DCI (e.g., DCI format 1_0, DCI) in the cell. In an example, the second DCI can schedule a random access response (e.g., Msg2) containing a random access response (e.g., Msg2) to the random access preamble. In an example, the second DCI can schedule a random access response (e.g., Msg2) containing a random access response (e.g., Msg2) to the random access preamble. Figure 18The PDSCH of the random access response (in the random access response). The random access response may be against a random access preamble. The CRC of the second DCI may be scrambled by an RNTI (e.g., RA-RNTI, C-RNTI, CS-RNTI, MCS-C-RNTI, TC-RNTI, etc.). The RNTI may be an RA-RNTI. In the example, the RA-RNTI may be based on the at least one random access resource. In the example, the base station and / or the radio device may determine the RA-RNTI based on the at least one random access resource. Monitoring of the second DCI may include the radio device attempting to detect / receive the second DCI during a response window (e.g., provided by the higher-layer parameter ra-ResponseWindow). The one or more configuration parameters may indicate the response window. The radio device may initiate the response window based on the transmitted random access preamble. The radio device may attempt to detect / receive the second DCI while the response window is running. In the example, the radio device may attempt to detect / receive the second DCI in the second core set (e.g., in the one or more core sets). Figure 18 In the core set 2), the second PDCCH is monitored for the second DCI. In the example, the second core set and the first core set that receive the PDCCH command can be different. In the example, the second core set and the first core set that receive the PDCCH command can be the same. Monitoring the second PDCCH for the second DCI in the second core set can include monitoring the second PDCCH for the second DCI in the search space set in the second core set (or associated with or linked to the second core set). In the example, the search space set can be a Type1-PDCCH CSS set. In the example, the search space set can be a common search space set. In the example, the search space set can be associated with (or linked to) the second core set. Associating (or linking) the search space set with the second core set can include the core set index field of the search space set indicating the second core set index of the second core set. Associating (or linking) the search space set with the second core set can include one or more configuration parameters that can indicate the second core set index of the second core set in the core set index field of the search space set (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). In the example, the value of the / core set index field of the search space set can be equal to the second core set index of the second core set. In the example, the association (or link) between the search space set and the second core set can include one or more configuration parameters that can indicate the second core set index of the second core set of the search space set.

[0274] In an example, a wireless device can monitor a PDCCH (or a PDCCH candidate) in a Type1-PDCCH CSS set on a cell (e.g., a PCell, an SCell) for a DCI format with CRC scrambled by an RNTI (e.g., a RA-RNTI or a TC-RNTI). The Type1-PDCCH CSS set can be configured by a ra-SearchSpace in a PDCCH-ConfigCommon. The ra-SearchSpace can identify an index of a search space of a random access procedure. The ra-SearchSpace can be an index of a search space of a random access procedure. The ra-SearchSpace can be an identity of a search space of a random access procedure.

[0275] In an example, the one or more configuration parameters can indicate a ra-search space of an active downlink BWP of a cell. In an example, the one or more configuration parameters can indicate a ra-search space of a search space set. The one or more configuration parameters indicating the ra-search space of the search space set can comprise a search space set index of the search space set being equal to the ra-search space. The one or more configuration parameters indicating the ra-search space of the search space set can comprise the search space set being identified by the ra-search space.

[0276] In an example, a wireless device can monitor a second PDCCH in a second core set for a second DCI based on a first antenna port quasi-co-location property of a first core set on which a PDCCH order is received. In an example, based on monitoring the second PDCCH in the second core set for the second DCI, the wireless device can update (replace / assume) a second antenna port quasi-co-location property of the second core set to be the first antenna port quasi-co-location property of the first core set. In an example, based on monitoring the second PDCCH in the second core set for the second DCI, the wireless device can determine that the second antenna port quasi-co-location property of the second core set is the same as the first antenna port quasi-co-location property of the first core set on which the PDCCH order is received. Based on the determination, the wireless device can monitor the second PDCCH in the second core set for the second DCI based on the first antenna port quasi-co-location property. Monitoring the second PDCCH in the second core set for the second DCI based on the first antenna port quasi-co-location property can comprise at least one second DM-RS port of the second PDCCH being quasi-co-located with a first reference signal (e.g., a Synchronization Signal (SS) or a Channel State Information Reference Signal (CSI-RS)) indicated by the first antenna port quasi-co-location property (in the first antenna port quasi-co-location property). Figure 18The at least one second DM-RS port of the second PDCCH can be QCL-ed with the first reference signal with respect to a first quasi co-location type (e.g., QCL TypeD, QCL TypeA, etc.). The first antenna port quasi co-location property can include / indicate the first quasi co-location type. The first antenna port quasi co-location property can include / indicate the first quasi co-location type of the first reference signal.

[0277] In an example, based on monitoring the second PDCCH for the second DCI in the second coreset, the wireless device can determine that the first antenna port quasi co-location property of the first PDCCH indicating / containing the PDCCH order is the same as the second antenna port quasi co-location property of the second PDCCH containing the second DCI. Based on the determination, the wireless device can set the second antenna port quasi co-location property to be the same as the first antenna port quasi co-location property. Based on the setting, the second antenna port quasi co-location property can include the first reference signal in the first antenna port quasi co-location property. Based on the setting, the second antenna port quasi co-location property can include the first quasi co-location type in the first antenna port quasi co-location property.

[0278] In an example, the wireless device can monitor a third PDCCH for a third DCI in the second coreset. The CRC of the third DCI can not be scrambled by the RA-RNTI. The CRC of the third DCI can be scrambled by a second RNTI (e.g., C-RNTI, CS-RNTI) different from the RA-RNTI. Based on the CRC not being scrambled by the RA-RNTI, the wireless device can monitor the third PDCCH for the third DCI in the second coreset based on the second antenna port quasi co-location property. The wireless device can receive the third PDCCH containing / comprising the third DCI via the second coreset based on the second antenna port quasi co-location property. Monitoring (or receiving) the third PDCCH in the second coreset / via the second coreset based on the second antenna port quasi co-location property can include (the wireless device determining) that at least one third DM-RS port of the third PDCCH is quasi co-located (QCL-ed) with the second reference signal indicated / configured by the second antenna port quasi co-location property. The at least one third DM-RS port of the third PDCCH can be QCL-ed with the second reference signal with respect to a second quasi co-location type (e.g., QCL TypeD, QCL TypeA, etc.). The second antenna port quasi co-location property can include / indicate the second quasi co-location type.

[0279] In an example, the wireless device can receive a second PDCCH containing / including a second DCI of a search space set (e.g., a Type1-PDCCH CSS set) in a second coreset. In an example, the wireless device can receive the second PDCCH based on (or concurrently with) monitoring the second PDCCH for the second DCI of the search space set in the second coreset. In an example, the wireless device can receive the second PDCCH containing / including a second DCI of a search space set (e.g., a Type1-PDCCH CSS set) in a second coreset based on the first antenna port quasi-co-location property of the first coreset on which the PDCCH order is received.

[0280] In an example, the second DCI (e.g., CRC scrambled by a RA-RNTI) can schedule a PDSCH containing a random access response (e.g., a random access response in Figure 18 corresponding to a preamble transmission in Figure 18 In an example, the wireless device can receive the PDSCH based on the first antenna port quasi-co-location property of the first coreset on which the PDCCH order is received. Receiving the PDSCH based on the first antenna port quasi-co-location property can include at least one DM-RS port of the PDSCH being quasi co-located (QCL-ed) with a first reference signal (e.g., RS 1 in Figure 18 ) indicated by the first antenna port quasi-co-location property of the first coreset on which the PDCCH order is received. Receiving the PDSCH based on the first antenna port quasi-co-location property can include at least one DM-RS port of the PDSCH and the at least one first DM-RS port of the first PDCCH containing the first DCI indicating the PDCCH order being quasi co-located (QCL-ed) with a first reference signal (e.g., RS 1 in Figure 18 ) indicated by the first antenna port quasi-co-location property. Receiving the PDSCH based on the first antenna port quasi-co-location property can include at least one DM-RS port of the PDSCH and the at least one first DM-RS port of the first PDCCH containing the first DCI indicating the PDCCH order being quasi co-located (QCL-ed) with a same reference signal (e.g., first reference signal RS 1 in Figure 18 ) indicated by the first antenna port quasi-co-location property of the first coreset on which the PDCCH order is received.

[0281] In an example, the at least one DM-RS port of the PDSCH can be QCL-ed with the first reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter. In an example, the at least one DM-RS port of the PDSCH can be QCL-ed with the first reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameter (when applicable). In an example, the at least one DM-RS port of the PDSCH can be QCL-ed with the first reference signal with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter (when applicable).

[0282] In an example, the at least one DM-RS port of the PDSCH can be QCL-ed with the first reference signal with respect to a first QCL type (e.g., QCLTypeD, QCL TypeA, etc.). The first antenna port QCL property can include / indicate the first QCL type. The first antenna port QCL property can include / indicate the first QCL type of the first reference signal.

[0283] In an example, the wireless device can complete the random access procedure based on receiving the PDSCH including a random access response corresponding to the random access preamble. The random access response corresponding to the random access preamble can include that the random access response can indicate the random access preamble (or a random access preamble index of the random access preamble).

[0284] In an example, the wireless device can receive a second PDSCH scheduled by a third DCI based on a second antenna port QCL property of a second coreset. Receiving the second PDSCH based on the second antenna port QCL property can include that at least one DM-RS port of the second PDSCH is QCL-ed with a second reference signal (e.g., RS 2 in Figure 18 In an example, the at least one DM-RS port of the second PDSCH can be QCL-ed with the second reference signal with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameter (when applicable).

[0285] Figure 19 is an example of a random access procedure in accordance with aspects of embodiments of the present disclosure.

[0286] In the example, the wireless device can receive one or more messages. In the example, the wireless device can receive these one or more messages from a base station. The one or more messages may include one or more configuration parameters. These one or more configuration parameters may include Physical Random Access Channel (PRACH) transmission parameters (e.g., PRACH preamble format, time resources, and frequency resources for PRACH transmission). These one or more configuration parameters may be used to include a first cell (e.g., Figure 19 The first cell in the middle) and the second cell (e.g., Figure 19 (The second community in the middle) and several communities.

[0287] In the example, PRACH transmission parameters can be (configured / indicated) for PRACH transmission via the first cell / first cell's PRACH (e.g., preamble transmission). In the example, PRACH transmission parameters can be (configured / indicated) for receiving a random access response via the second cell. In the example, PRACH transmission parameters can be (configured / indicated) for the random access procedure of the first cell. The first cell can be a primary cell (PCell). The first cell can be a secondary cell (SCell). The second cell can be a primary cell (PCell). The second cell can be a secondary cell. In the example, the first cell can be an unlicensed cell. In the example, the first cell can be a licensed cell. In the example, the second cell can be an unlicensed cell. In the example, the second cell can be a licensed cell.

[0288] In the example, one or more configuration parameters can indicate the cell indexes of the multiple cells (e.g., provided by the higher-level parameter ServCellID). In the example, each of the multiple cells can be identified by the corresponding cell index in the cell index. In the example, the first cell can be identified by the first cell index in the cell index. In the example, the second cell can be identified by the second cell index in the cell index.

[0289] In the example, the one or more configuration parameters may indicate one or more first core sets of the first cell. The one or more first core sets may include first core sets (e.g., Figure 19 Core set 1 in the example. In this example, the one or more configuration parameters can indicate one or more second core sets for the second cell. These one or more second core sets may include a second core set (e.g., ...). Figure 19 Core set 2).

[0290] In the example, the wireless device may be based on the quasi-co-location nature of the first antenna port (e.g., Figure 19Antenna port QCL property 1) Monitoring the first PDCCH for the first DCI in the first core set / via the first core set. Monitoring the first PDCCH for the first DCI in the first core set / via the first core set based on the first antenna port quasi-co-location property may include (determined by the wireless device) at least one first DM-RS port of the first PDCCH and a first reference signal (e.g., in the first antenna port quasi-co-location property) indicated by the first antenna port quasi-co-location property. Figure 19 RS 1) Quasi-co-addressable (QCL-ed). The at least one first DM-RS port of the first PDCCH may be QCL-ed with respect to a first quasi-co-addressable type (e.g., QCL Type D, QCL Type A, etc.). The quasi-co-addressable nature of the first antenna port may include / indicate the first quasi-co-addressable type. The quasi-co-addressable nature of the first antenna port may include / indicate the first quasi-co-addressable type of the first reference signal.

[0291] In the example, the wireless device can be based on the quasi-co-located nature of the second antenna port (e.g., Figure 19 Antenna port QCL property 2) Monitoring the second PDCCH for the second DCI in the second core set / via the second core set. Monitoring the second PDCCH for the second DCI in the second core set / via the second core set based on the second antenna port quasi-co-location property may include (determined by the radio device) at least one second DM-RS port of the second PDCCH and a second reference signal (e.g., in the second antenna port quasi-co-location property) indicated by the second antenna port quasi-co-location property. Figure 19 In the second PDCCH, at least one second DM-RS port can be QCL-ed with respect to a second quasi-co-address type (e.g., QCL Type D, QCL Type A, etc.) and a second reference signal QCL-ed. The quasi-co-address nature of the second antenna port can include / indicate the second quasi-co-address type. The quasi-co-address nature of the second antenna port can include / indicate the second quasi-co-address type of the second reference signal.

[0292] In the example, the wireless device can receive a Physical Downlink Control Channel (PDCCH) command that initiates a random access procedure (e.g., Figure 19 The PDCCH command in the first cell). The radio device can be transmitted via the first core set of the first cell (e.g., Figure 19The core set 1) receives PDCCH commands. The random access procedure can be a contention-free random access procedure (e.g., a contention-free based random access procedure). The radio device can initiate a random access procedure for the first cell. The radio device can initiate a random access procedure based on receiving a PDCCH command. The PDCCH command can initiate / trigger a random access procedure for the first cell. The radio device can initiate the random access procedure via the first core set of the first cell to which the random access procedure is targeted (e.g., ...). Figure 19 The core set 1) receives PDCCH commands.

[0293] In the example, the wireless device can receive / detect a first PDCCH containing a first DCI via a first core set based on the quasi-co-location nature of the first antenna port. In the example, the first DCI can indicate a PDCCH command that initiates / triggers a random access procedure. In the example, the wireless device can receive / detect a first PDCCH containing a first DCI indicating a PDCCH command via a first core set based on the quasi-co-location nature of the first antenna port. The wireless device can receive PDCCH commands in the first core set / via the first core set based on the quasi-co-location nature of the first antenna port. Receiving / detecting the first PDCCH in the first core set / via the first core set based on the quasi-co-location nature of the first antenna port may include (determined by the wireless device) at least one first DM-RS port of the first PDCCH and a first reference signal (e.g., indicated by the quasi-co-location nature of the first antenna port) (within the quasi-co-location nature of the first antenna port). Figure 19 RS 1) Quasi-co-address (QCL-ed). The at least one first DM-RS port of the first PDCCH may be associated with the first reference signal QCL-ed with respect to the first quasi-co-address type (e.g., QCL Type D, QCL Type A, etc.).

[0294] In the example, based on the received PDCCH command, the wireless device can transmit the random access preamble of the random access procedure (e.g., Figure 19 (Preamble transmission in the first cell). The radio device may transmit the random access preamble via at least one random access resource (e.g., PRACH timing) of the uplink BWP (e.g., active uplink BWP) of the first cell.

[0295] In the example, based on the transmission random access preamble, the wireless device can target the second DCI (e.g., Figure 19 The second DCI (DCI format 1_0, DCI) is used for monitoring (or to start monitoring). In the example, the second DCI can be scheduled to include a random access response (e.g., Figure 19PDSCH carrying a random access response). The random access response can be for the random access preamble. The CRC of the second DCI can be scrambled by a RNTI (e.g., RA-RNTI, C-RNTI, CS-RNTI, MCS-C-RNTI, TC-RNTI, etc.). The RNTI can be a RA-RNTI. The monitoring for the second DCI can comprise the wireless device attempting to detect / receive the second DCI during a response window (e.g., provided by a higher layer parameter ra-ResponseWindow). In an example, the wireless device can monitor for the second DCI a second PDCCH in a second core set (e.g., CORESET 2) of the one or more second cores of the second cell. Monitoring for the second DCI a second PDCCH in a second core set can comprise monitoring for the second DCI a second PDCCH in a search space set (or in a search space set associated with or linked to the second core set) of the second core set. In an example, the search space set can be a Type1-PDCCH CSS set. In an example, the search space set can be a common search space set. In an example, the one or more configuration parameters can indicate a ra-SearchSpace of the search space set. In an example, the search space set can be associated (or linked) with the second core set. In an example, the wireless device can monitor for the second DCI a second PDCCH in the second core set based on the second core set being associated (or linked) with the search space set being a Type1-PDCCH CSS set. In an example, the wireless device can determine to monitor for the second DCI a second PDCCH in the second core set based on the second core set being associated (or linked) with the search space set being a Type1-PDCCH CSS set. Figure 19

[0296] In an example, the first cell and the second cell can be different. The first cell and the second cell can be different can comprise a first cell index of the first cell being different from a second cell index of the second cell.

[0297] In an example, the wireless device can monitor for the second DCI a second PDCCH in the second core set based on a second antenna port quasi-co-location property of the second core set being associated (or linked) with the search space set. In an example, the wireless device can monitor for the second DCI a second PDCCH in the second core set based on a second antenna port quasi-co-location property of the second core set being associated (or linked) with the search space set (or Type1-PDCCH CSS set). Monitoring for the second DCI a second PDCCH in the second core set based on the second antenna port quasi-co-location property can comprise at least one second DM-RS port of the second PDCCH carrying the second DCI being quasi co-located with a second reference signal (e.g.,​ Figure 19 The at least one second DM-RS port of the second PDCCH can be QCL-ed with a second reference signal with respect to a second quasi co-location type (e.g., QCL TypeD, QCL TypeA, etc.). The second antenna port quasi co-location property can include / indicate the second quasi co-location type. The second antenna port quasi co-location property can include / indicate the second quasi co-location type of the second reference signal.

[0298] In an example, the wireless device can receive a second PDCCH containing / including a second DCI of a search space set (e.g., Type1-PDCCH CSS set) in a second coreset. In an example, the wireless device can receive the second PDCCH based on (or concurrently with) monitoring the search space set for the second DCI in the second coreset. In an example, the wireless device can receive the second PDCCH containing / including a second DCI of a search space set (e.g., Type1-PDCCH CSS set) in a second coreset based on a second antenna port quasi co-location property of the second coreset associated (or linked) with the search space set.

[0299] In an example, the second DCI (e.g., CRC scrambled by RA-RNTI) can schedule a PDSCH containing a random access response (e.g., RAR) corresponding to a preamble transmission in Figure 19 In an example, the wireless device can receive the PDSCH based on a second antenna port quasi co-location property of the second coreset associated (or linked) with the search space set. Receiving the PDSCH based on the second antenna port quasi co-location property can include at least one DM-RS port of the PDSCH being QCL-ed with a second reference signal (e.g., RS 2 in Figure 19 In an example, the wireless device can receive the PDSCH based on a second antenna port quasi co-location property of the second coreset associated (or linked) with the search space set. Receiving the PDSCH based on the second antenna port quasi co-location property can include at least one DM-RS port of the PDSCH being QCL-ed with a second reference signal (e.g., RS 2 in Figure 19 In an example, the wireless device can receive the PDSCH based on a second antenna port quasi co-location property of the second coreset associated (or linked) with the search space set. Receiving the PDSCH based on the second antenna port quasi co-location property can include at least one DM-RS port of the PDSCH being QCL-ed with a second reference signal (e.g., RS 2 in Figure 19 In an example, the wireless device can receive the PDSCH based on a second antenna port quasi co-location property of the second coreset associated (or linked) with the search space set. Receiving the PDSCH based on the second antenna port quasi co-location property can include at least one DM-RS port of the PDSCH being QCL-ed with a second reference signal (e.g., RS 2 in Figure 19a second reference signal (RS 2) in the PDSCH.

[0300] In an example, the at least one DM-RS port of the PDSCH can be quasi co-located (QCL-ed) with the second reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter. In an example, the at least one DM-RS port of the PDSCH can be quasi co-located (QCL-ed) with the second reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter (when applicable). In an example, the at least one DM-RS port of the PDSCH can be quasi co-located (QCL-ed) with the second reference signal with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter (when applicable).

[0301] In an example, the at least one DM-RS port of the PDSCH can be QCL-ed with the second reference signal with respect to a second quasi co-location type (e.g., QCLTypeD, QCL TypeA, etc.). The second antenna port quasi co-location property can include / indicate the second quasi co-location type. The second antenna port quasi co-location property can include / indicate the second quasi co-location type of the second reference signal.

[0302] In an example, the wireless device can complete the random access procedure based on receiving the PDSCH including a random access response corresponding to the random access preamble. The random access response corresponding to the random access preamble can include that the random access response can indicate the random access preamble (or a random access preamble index of the random access preamble).

[0303] In an example, the wireless device can receive a PDCCH order from a base station to initiate a random access procedure (e.g., a contention-free random access procedure) of a primary cell (PCell). The wireless device can receive the PDCCH order via a first coreset of the primary cell. The wireless device can receive the PDCCH order via the first coreset based on a first TCI state (or a first receive beam).

[0304] A wireless device can transmit a random access preamble of a random access procedure initiated by a PDCCH order. The wireless device can start monitoring a second coreset of a primary cell for a DCI scheduling a random access response corresponding to the random access preamble, e.g., based on transmitting the random access preamble. In the prior art, the wireless device can monitor the second coreset for the DCI based on a first TCI state of the first coreset of the wireless device receiving the PDCCH order. In the prior art, the wireless device can receive the random access response via the primary cell based on the first TCI state of the first coreset of the wireless device receiving the PDCCH order. In an example, the second coreset and the first coreset can be the same. In an example, the second coreset and the first coreset can be different.

[0305] In an example, a wireless device can be configured with carrier aggregation. In an example, the wireless device can receive a PDCCH order initiating a random access procedure of a primary cell via a first coreset of a secondary cell. In an example, the wireless device can receive the PDCCH order via the first coreset of the secondary cell based on a first TCI state (e.g., a first receive beam). The wireless device can transmit a random access preamble of the random access procedure initiated by the PDCCH order via the primary cell. In an example, based on transmitting the random access preamble, the wireless device can start monitoring a second coreset of the primary cell for a DCI scheduling a random access response corresponding to the random access preamble. In an implementation of the prior art, the wireless device monitors the second coreset of the primary cell for the DCI based on a first TCI state of the first coreset of the secondary cell of the wireless device receiving the PDCCH order. This can not be efficient when the primary cell and the secondary cell operate at different frequencies. The primary cell and the secondary cell can use different beams to serve (or transmit to) the wireless device. In an example, the wireless device can not receive the DCI in the second coreset of the primary cell based on the first TCI state used to receive the PDCCH order in the first coreset of the secondary cell. The wireless device can not receive / detect the DCI via the second coreset of the primary cell based on the first TCI state of the first coreset of the secondary cell. This can cause retransmission of the DCI, resulting in increased battery consumption at the base station; and increased latency of the random access procedure.

[0306] Example embodiments implement an enhanced procedure for receiving a DCI scheduling a random access response when a wireless device receives a PDCCH order via a first coreset of a secondary cell and monitors for the DCI in a second coreset of a primary cell. In example embodiments, the one or more configuration parameters or the activation command can indicate / activate the second coreset with a second TCI state. The wireless device can receive the DCI based on the second TCI state of the second coreset. The wireless device can not override the second TCI state of the second coreset with the first TCI state of the first coreset.

[0307] This enhancement procedure can reduce uplink overhead / retransmission and interference, reduce battery power consumption at the wireless device and the base station, and reduce latency / wait time for the random access procedure.

[0308] In an example, the wireless device can receive the DCI scheduling the random access response. In prior art implementations, the wireless device receives the random access response via the primary cell based on the first TCI state of the first coreset of the secondary cell on which the wireless device receives the PDCCH order. This can not be efficient when the primary cell and the secondary cell operate at different frequencies. The primary cell and the secondary cell can use different beams to serve (or transmit to) the wireless device. In an example, the wireless device can not receive the random access response via the primary cell based on the first TCI state used to receive the PDCCH order in the first coreset of the secondary cell. The wireless device can not receive the random access response via the primary cell based on the first TCI state of the first coreset of the secondary cell. This can cause retransmission of the random access response, resulting in increased battery power consumption at the base station; and increased latency for the random access procedure.

[0309] Exemplary embodiments implement an enhancement procedure for receiving a random access response of a random access procedure of a primary cell when a wireless device receives a PDCCH order initiating the random access procedure of the primary cell via a first coreset of a secondary cell. In exemplary embodiments, the one or more configuration parameters or the activation command can indicate / activate a second coreset of the secondary cell with a second TCI state. The wireless device can receive the random access response based on the second TCI state of the second coreset. The wireless device can not override the second TCI state of the second coreset with the first TCI state of the first coreset.

[0310] This enhancement procedure can reduce uplink overhead / retransmission and interference, reduce battery power consumption at the wireless device and the base station, and reduce latency / wait time for the random access procedure.

[0311] In an example, the wireless device can receive a PDCCH order initiating a random access procedure (e.g., a contention-free random access procedure) for a cell (e.g., a PCell, a SCell), e.g., from a base station. The wireless device can receive the PDCCH order via a coreset of the cell. The wireless device can receive the PDCCH order via the coreset based on a TCI state (or receive beam).

[0312] A wireless device can transmit a random access preamble of a random access procedure initiated by a PDCCH order. The wireless device can start monitoring a second coreset for DCI scheduling a random access response corresponding to the random access preamble based on transmitting the random access preamble, for example. In the prior art, the wireless device can monitor the second coreset for the DCI based on a TCI state of a coreset in which the wireless device receives the PDCCH order. In an example, the second coreset and the coreset can be the same. In an example, the second coreset and the coreset can be different.

[0313] In an example, a wireless device can be served by a plurality of TRPs including a first TRP and a second TRP. The wireless device can receive / transmit downlink / uplink signals from / to the plurality of TRPs. The first TRP can be associated with a first coreset group including one or more first coresets. The first TRP being associated with the first coreset group can include the TRP transmitting DCI via the one or more first coresets in the first coreset group. The first TRP being associated with the first coreset group can include the first TRP not transmitting DCI via one or more second coresets in a second coreset group different from the first coreset group. The second TRP can be associated with a second coreset group.

[0314] In an example, a wireless device can receive a PDCCH order initiating a random access procedure via a first core set in a first core set group associated with a first TRP. In an example, the wireless device can receive the PDCCH order via the first core set based on a TCI state (e.g., receive beam) of the first core set. The wireless device can transmit a random access preamble of the random access procedure initiated by the PDCCH order. In an example, based on transmitting the random access preamble, the wireless device can start monitoring a second core set in a second core set group associated with a second TRP for DCI scheduling a random access response corresponding to the random access preamble. In prior art implementations, the wireless device monitors the second core set in the second core set group for the DCI based on a TCI state of the first core set in the first core set group in which the wireless device received the PDCCH order. This can not be efficient when the first core set group and the second core set group are different (e.g., different TRPs). In an example, the wireless device can not receive the DCI in the second core set based on the TCI state used to receive the PDCCH order in the first core set. In an example, the first TRP and the second TRP can be positioned in different directions. The first TRP and the second TRP can use different beams to serve (or transmit to) the wireless device. The wireless device can not receive / detect the DCI via the second core set in the second core set group based on the TCI state of the first core set in the first core set group. This can cause retransmission of the DCI, resulting in increased battery consumption at the base station; and increased latency of the random access procedure.

[0315] Exemplary embodiments implement an enhanced procedure for receiving DCI scheduling a random access response when a wireless device receives a PDCCH order via a first core set in a first core set group and monitors for the DCI in a second core set in a second core set group different from the first core set group. In exemplary embodiments, the one or more configuration parameters or the activation command can indicate / activate the second core set with a second TCI state. The wireless device can receive the DCI based on the second TCI state of the second core set. The wireless device can not override the second TCI state of the second core set with the TCI state of the first core set. In exemplary embodiments, the base station can transmit the DCI scheduling the random access response via the second core set in the first core set group in which the PDCCH order is received. The base station can not transmit the PDCCH indicating / scheduling the random access response via the second core set in the second core set group different from the first core set group.

[0316] This enhanced procedure can reduce uplink overhead / retransmission and interference, reduce station battery power consumption at the wireless device and the base station, and reduce latency of the random access procedure.

[0317] Figure 20is an example of a random access procedure in accordance with aspects of an embodiment of the present disclosure. Figure 21 is Figure 20 an example flowchart of a random access procedure disclosed in

[0318] In an example, a 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 comprise one or more configuration parameters. The one or more configuration parameters can comprise physical random access channel (PRACH) transmission parameters (e.g., a PRACH preamble format, time resources, and frequency resources for a PRACH transmission). The one or more configuration parameters can be for a plurality of cells comprising a first cell (e.g., a first cell in Figure 20 ) and a second cell (e.g., a second cell in Figure 20 ). In an example, the PRACH transmission parameters can be (configured / indicated) for a PRACH transmission (e.g., a preamble transmission) via the second cell. In an example, the PRACH transmission parameters can be (configured / indicated) for receiving a random access response via the second cell. In an example, the PRACH transmission parameters can be (configured / indicated) for a random access procedure of the second cell.

[0319] In an example, the second cell can be a primary cell (PCell or SpCell). The first cell can be a secondary cell (SCell). In an example, the second cell can be a secondary cell (SCell). The first cell can be a primary cell (PCell or SpCell).

[0320] In an example, the one or more configuration parameters can indicate one or more first coreset(s) of the first cell. The one or more first coreset(s) can comprise a first coreset (e.g., coreset 1 in Figure 20 ). In an example, the one or more configuration parameters can indicate one or more second coreset(s) of the second cell. The one or more second coreset(s) can comprise a second coreset (e.g., coreset 2 in Figure 20 ).

[0321] In an example, the second cell can be a scheduled cell. In an example, the second cell can be a PUCCH SCell. A secondary cell is a PUCCH SCell when the secondary cell is configured with PUCCH resources, e.g., by a base station. In an example, the first cell can be a scheduling cell.

[0322] In an example, the second cell can not comprise a control resource set (coreset). In an example, the one or more configuration parameters can not indicate a coreset for the second cell. In an example, the one or more configuration parameters can not indicate a coreset of an active downlink BWP of the second cell.

[0323] In an example, when the second cell is a scheduled cell, the second cell can be cross-carrier scheduled by a scheduling cell (e.g., the first cell). The cell being cross-carrier scheduled by the scheduling cell can include the wireless device monitoring a downlink control channel (or a coreset) of the scheduling cell for a downlink control information (DCI) of a transport block (TB) of the scheduling cell. The TB can be a PDSCH. The TB can be a PUSCH. The wireless device can transmit / receive the TB via the second cell.

[0324] In an example, the wireless device can monitor a first PDCCH in / via a first coreset of the first cell for a first DCI based on a first antenna port quasi co-location property (e.g., AntennaPortQCL-Info1 in Figure 20 The monitoring the first PDCCH in / via the first coreset for the first DCI based on the first antenna port quasi co-location property can include (the wireless device determining) that at least one first DM-RS port of the first PDCCH containing the first DCI is quasi co-located (QCL-ed) with a first reference signal (e.g., RS1 in Figure 20 AntennaPortQCL-Info1) indicated by the first antenna port quasi co-location property. The at least one first DM-RS port of the first PDCCH can be QCL-ed with the first reference signal with respect to a first quasi co-location type (e.g., QCL TypeD, QCL TypeA, etc.). The first antenna port quasi co-location property can include / indicate the first quasi co-location type. The first antenna port quasi co-location property can include / indicate the first quasi co-location type of the first reference signal.

[0325] In an example, the wireless device can receive a physical downlink control channel (PDCCH) order (e.g., PDCCH order in Figure 20 ) to initiate a random access procedure. The wireless device can receive the PDCCH order via a first coreset (e.g., coreset 1 in Figure 20 ) of the first cell. The random access procedure can be a contention-free random access procedure (e.g., a random access procedure based on contention-free). The PDCCH order can indicate the second cell. In an example, the PDCCH order can indicate a second cell index of the second cell. The wireless device can initiate the random access procedure of the second cell. The PDCCH order can initiate / trigger the random access procedure of the second cell. Based on the PDCCH order indicating the second cell, the wireless device can initiate the random access procedure of the second cell.

[0326] In an example, the second cell can be a SpCell. In an example, the second cell can be a PCell. The first cell can be a secondary cell (SCell).

[0327] In an example, the wireless device can receive / detect, based on the first antenna port quasi-co-location property, a first PDCCH including a first DCI via the first coreset. In an example, the first DCI can indicate a PDCCH order to initiate a random access procedure. In an example, the wireless device can receive / detect, based on the first antenna port quasi-co-location property, a first PDCCH including a first DCI indicating a PDCCH order via the first coreset. The wireless device can receive the PDCCH order in / via the first coreset based on the first antenna port quasi-co-location property.

[0328] In an example, based on receiving the PDCCH order, the wireless device can transmit a random access preamble (e.g., a preamble transmission) of a random access procedure. The wireless device can transmit the random access preamble via at least one random access resource (e.g., a PRACH occasion) of an uplink BWP (e.g., an active uplink BWP) of the second cell. Figure 20

[0329] In an example, based on transmitting the random access preamble, the wireless device can monitor (or start monitoring) for a second DCI (e.g., a DCI format 1 0, DCI, in Figure 20 In an example, the second DCI can schedule a PDSCH including a random access response (e.g., a random access response in Figure 20 The random access response can be for the random access preamble. A CRC of the second DCI can be scrambled by a RNTI. The RNTI can be a RA-RNTI.

[0330] In an example, the wireless device can monitor (or start monitoring) for a second DCI (e.g., a DCI format 1 0, DCI, in Figure 20 ​monitor a second PDCCH for a second DCI in a second coreset of the one or more coresets. In an example, the one or more configuration parameters can indicate a search space set for which the wireless device is to monitor the second PDCCH for the second DCI. In an example, the search space set can be a Type1-PDCCH CSS set. In an example, the search space set can be a common search space set. In an example, the one or more configuration parameters can indicate a ra-searchSpace of the search space set. In an example, the search space set can be associated with (or linked to) the second coreset. In an example, the wireless device can monitor the second PDCCH for the second DCI in the second coreset based on the second coreset being associated with (or linked to) the search space set that is a Type1-PDCCH CSS set. In an example, the wireless device can determine to monitor the second PDCCH for the second DCI in the second coreset based on the second coreset being associated with (or linked to) the search space set that is a Type1-PDCCH CSS set.

[0331] In an example, the wireless device can determine that the first cell and the second cell are different. The first cell and the second cell being different can comprise a first cell index of the first cell and a second cell index of the second cell being different. In an example, when the first cell and the second cell are different, the wireless device can monitor a second DCI via a second coreset of a second cell different from a first cell in which the PDCCH order is received based on a second antenna port quasi co-location property (e.g., AntennaPortQCL-Property2) of the second coreset. In an example, the wireless device can monitor the second PDCCH for the second DCI in the second coreset based on the second antenna port quasi co-location property of the second coreset being associated with (or linked to) a search space set (or a Type1-PDCCH CSS set). Figure 20 In an example, the wireless device can determine that the first cell and the second cell are different. The first cell and the second cell being different can comprise a first cell index of the first cell and a second cell index of the second cell being different. In an example, when the first cell and the second cell are different, the wireless device can monitor a second DCI via a second coreset of a second cell different from a first cell in which the PDCCH order is received based on a second antenna port quasi co-location property (e.g., AntennaPortQCL-Property2) of the second coreset. In an example, the wireless device can monitor the second PDCCH for the second DCI in the second coreset based on the second antenna port quasi co-location property of the second coreset being associated with (or linked to) a search space set (or a Type1-PDCCH CSS set). Figure 20 In an example, the wireless device can determine that the first cell and the second cell are different. The first cell and the second cell being different can comprise a first cell index of the first cell and a second cell index of the second cell being different. In an example, when the first cell and the second cell are different, the wireless device can monitor a second DCI via a second coreset of a second cell different from a first cell in which the PDCCH order is received based on a second antenna port quasi co-location property (e.g., AntennaPortQCL-Property2) of the second coreset. In an example, the wireless device can monitor the second PDCCH for the second DCI in the second coreset based on the second antenna port quasi co-location property of the second coreset being associated with (or linked to) a search space set (or a Type1-PDCCH CSS set). Figure 20QCL-ed with a second reference signal. The second antenna port quasi co-location property can include / indicate the second quasi co-location type. The second antenna port quasi co-location property can include / indicate the second quasi co-location type of the second reference signal.

[0332] In an example, the wireless device can determine that the first cell and the second cell are the same (e.g., similar to Figure 18 For example, the cell in which the PDCCH order is received, the random access preamble is transmitted, and the random access response is received are the same). The first cell and the second cell being the same can include a first cell index of the first cell and a second cell index of the second cell being the same. In an example, when the first cell and the second cell are the same, the wireless device can monitor for the second DCI via a second coreset of the second cell that is the same as the first cell in which the PDCCH order is received based on the first antenna port quasi co-location property of the first coreset in which the PDCCH order is received. In an example, based on the first cell and the second cell being the same, the wireless device can monitor for the second PDCCH for the second DCI in the second coreset based on the first antenna port quasi co-location property of the first coreset in which the PDCCH order is received. In an example, based on monitoring for the second PDCCH for the second DCI in the second coreset, the wireless device can update (replace / assume) the second antenna port quasi co-location property of the second coreset to be the first antenna port quasi co-location property of the first coreset. In an example, based on monitoring for the second PDCCH for the second DCI in the second coreset, the wireless device can determine that the second antenna port quasi co-location property of the second coreset is the same as the first antenna port quasi co-location property of the first coreset in which the PDCCH order is received. Based on the determination, the wireless device can monitor for the second PDCCH for the second DCI in the second coreset based on the first antenna port quasi co-location property. Monitoring for the second PDCCH for the second DCI in the second coreset based on the first antenna port quasi co-location property can include at least one second DM-RS port of the second PDCCH being QCL-ed with a first reference signal (e.g., Figure 20RS 1) Quasi-co-addressable (QCL-ed). The at least one second DM-RS port of the second PDCCH may be QCL-ed with respect to a first quasi-co-addressable type (e.g., QCL Type D, QCL Type A, etc.). The quasi-co-addressable nature of the first antenna port may include / indicate the first quasi-co-addressable type. The quasi-co-addressable nature of the first antenna port may include / indicate the first quasi-co-addressable type of the first reference signal. In the example, the first core set and the second core set may be the same. The first core set and the second core set being the same may include the first core set index of the first core set and the second core set index of the second core set being the same. In the example, the first core set and the second core set may be different. The first core set and the second core set being different may include the first core set index of the first core set and the second core set index of the second core set being different.

[0333] In the example, the second cell can be a secondary cell (SCell). The first cell can be a primary cell (PCell or SpCell).

[0334] In the example, the wireless device can be in the second core set of one or more first core sets of the first cell (e.g., Figure 20 The core set 1) monitors the second PDCCH for the second DCI. Monitoring the second PDCCH for the second DCI in the second core set can include monitoring the second PDCCH for the second DCI within a search space set in the second core set (or associated with or linked to the second core set). In the example, the search space set can be a Type1-PDCCH CSS set. In the example, the search space set can be a common search space set. In the example, one or more configuration parameters can indicate the ra-search space of the search space set.

[0335] In the example, the wireless device can monitor the second PDCCH for the second DCI via the second core set of the first cell that received the PDCCH command. In the example, the wireless device can monitor the second PDCCH for the second DCI via the first cell and receive PDCCH commands. In the example, the wireless device can base its monitoring on the quasi-co-location nature of the first antenna port of the first core set that received the second PDCCH (e.g., ...). Figure 20the second antenna port quasi-co-location property of the second coreset can be the same as the first antenna port quasi-co-location property of the first coreset in which the PDCCH order is received. In an example, monitoring the second PDCCH for the second DCI in the second coreset based on the first antenna port quasi-co-location property can include at least one second DM-RS port of the second PDCCH being QCL-ed with a first reference signal (e.g., SSB, CSI-RS, etc.) indicated by the first antenna port quasi-co-location property (in the first antenna port quasi-co-location property). In an example, the first reference signal can be a first reference signal (e.g., SSB, CSI-RS, etc.) indicated by the first antenna port quasi-co-location property (in the first antenna port quasi-co-location property) in which the PDCCH order is received. In an example, the first reference signal can be a first reference signal (e.g., SSB, CSI-RS, etc.) associated with the search space set in which the PDCCH order is received. Figure 20 In an example, the at least one second DM-RS port of the second PDCCH can be QCL-ed with the first reference signal with respect to a first quasi-co-location type (e.g., QCL TypeD, QCL TypeA, etc.).

[0336] In an example, the wireless device can receive a second PDCCH containing / including a second DCI of a search space set (e.g., a Type1-PDCCH CSS set) in a second coreset. In an example, the wireless device can receive the second PDCCH based on (or concurrently with) monitoring the second PDCCH for the second DCI of the search space set in the second coreset. In an example, the wireless device can receive the second PDCCH containing / including a second DCI of a search space set (e.g., a Type1-PDCCH CSS set) in a second coreset based on a second antenna port quasi-co-location property of the second coreset associated (or linked) with the search space set. In an example, the wireless device can receive the second PDCCH containing / including a second DCI of a search space set (e.g., a Type1-PDCCH CSS set) in a second coreset based on a first antenna port quasi-co-location property of a first coreset in which the PDCCH order is received.

[0337] In an example, the second DCI can schedule a random access response (e.g., a PDCCH order) corresponding to a preamble transmission (e.g., Figure 20 In an example, the second DCI can schedule a random access response (e.g., a PDCCH order) corresponding to a preamble transmission (e.g., Figure 20PDSCH in the PDCCH order. In an example, the wireless device can determine that the PDCCH order and the second DCI scheduling the PDSCH are received via a same cell (e.g., the first cell). In an example, the wireless device can receive the PDCCH order via the first cell. In an example, the wireless device can receive the second PDCCH scheduling the PDSCH via the first cell. In an example, the wireless device can receive the PDSCH via the first cell. In an example, the wireless device can receive the PDSCH based on the first antenna port quasi-co-location property of the first coreset on which the PDCCH order is received. In an example, based on the determination, the wireless device can receive the PDSCH based on the first antenna port quasi-co-location property of the first coreset on which the PDCCH order is received. Receiving the PDSCH based on the first antenna port quasi-co-location property can include at least one DM-RS port of the PDSCH being quasi-co-located (QCL-ed) with a first reference signal (e.g., RS 1 in Figure 20 FIG. 1) indicated by the first antenna port quasi-co-location property. Receiving the PDSCH based on the first antenna port quasi-co-location property can include at least one DM-RS port of the PDSCH and the at least one first DM-RS port of the first PDCCH containing the first DCI indicating the PDCCH order being quasi-co-located (QCL-ed) with a first reference signal (e.g., RS 1 in Figure 20 FIG. 1) indicated by the first antenna port quasi-co-location property. Receiving the PDSCH based on the first antenna port quasi-co-location property can include at least one DM-RS port of the PDSCH and the at least one first DM-RS port of the first PDCCH containing the first DCI indicating the PDCCH order being quasi-co-located (QCL-ed) with a first reference signal (e.g., RS 1 in Figure 20 FIG. 1) indicated by the first antenna port quasi-co-location property.

[0338] In an example, the at least one DM-RS port of the PDSCH can be quasi-co-located (QCL-ed) with the first reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter. In an example, the at least one DM-RS port of the PDSCH can be quasi-co-located (QCL-ed) with the first reference signal with respect to at least one of: Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter (when applicable). In an example, the at least one DM-RS port of the PDSCH can be quasi-co-located (QCL-ed) with the first reference signal with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameter (when applicable).

[0339] In an example, the at least one DM-RS port of the PDSCH can be QCL-ed with the first reference signal with respect to a first quasi-co-location type (e.g., QCL TypeD, QCL TypeA, etc.). The first antenna port quasi-co-location property can include / indicate the first quasi-co-location type. The first antenna port quasi-co-location property can include / indicate the first quasi-co-location type of the first reference signal.

[0340] In an example, a wireless device can complete a random access procedure based on receiving a PDSCH including a random access response corresponding to a random access preamble. The random access response corresponding to the random access preamble can include that the random access response can indicate the random access preamble (or a random access preamble index of the random access preamble).

[0341] Figure 22 is an example of a random access procedure in accordance with aspects of embodiments of the present disclosure.

[0342] In an example, a 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. The one or more configuration parameters can include physical random access channel (PRACH) transmission parameters (e.g., a PRACH preamble format, time resources, and frequency resources for a PRACH transmission). The one or more configuration parameters can be for a cell. In an example, the PRACH transmission parameters can be (configured / indicated) for a PRACH transmission via the cell. In an example, the PRACH transmission parameters can be (configured / indicated) for a random access procedure of the cell. The cell can be a primary cell (PCell). The cell can be a secondary cell (SCell). The cell can be a PUCCH-configured secondary cell (e.g., a PUCCH SCell). In an example, the cell can be an unlicensed cell. In an example, the cell can be a licensed cell.

[0343] In an example, the one or more configuration parameters can indicate a plurality of core set groups (e.g., a core set group 1, a core set group 2) in Figure 22 In an example, the plurality of core set groups can include a plurality of coresets (e.g., a coreset 1, a coreset 2) in Figure 22Core set 1, core set 2, core set 3, and core set 4 in the example. In the example, the one or more configuration parameters can indicate the multiple core cluster groups of the cell's downlink BWP. In the example, the one or more configuration parameters can indicate the multiple core sets of the cell's downlink BWP. Each of the multiple core cluster groups may contain one or more corresponding core sets (e.g., core set 1 and core set 3 for core cluster group 1; core set 2 and core set 4 for core cluster group 2). In the example, the one or more configuration parameters can indicate the multiple core sets grouped into the multiple core cluster groups.

[0344] In the example, the multiple core cluster groups may include a first core cluster group (e.g., Figure 22 Core cluster group 1) and second core cluster group (e.g., Figure 22 The first core cluster group (2) may contain one or more first core sets (e.g., Figure 22 Core set 1 and core set 3 in the example). In the example, the one or more first core sets may include a first core set (e.g., core set 1). The one or more first core sets may include a second core set (e.g., core set 3). The second core cluster group may contain one or more second core sets (e.g., core set 1 and core set 3). Figure 22 (Core set 2 and core set 4 in the example). In the example, the one or more second core sets may include a second core set (e.g., core set 2). The one or more second core sets may include a fourth core set (e.g., core set 4).

[0345] In the example, a cell may include multiple Transmit and Receive Points (TRPs). These multiple TRPs may include a first TRP (e.g., Figure 22 TRP 1) and the second TRP (e.g., Figure 22The first TRP can transmit downlink signals / channels (e.g., PDSCH, PDCCH, DCI) via the first coreset group. Transmitting downlink signals / channels (e.g., PDCCH, DCI) via the first coreset group can include that the first TRP can transmit the downlink signals / channels via a coreset within the first coreset group. The first TRP can not transmit downlink signals / channels (e.g., PDSCH, PDCCH, DCI) via the second coreset group. Not transmitting downlink signals / channels (e.g., PDSCH, PDCCH, DCI) via the second coreset group can include that the first TRP can not transmit the downlink signals / channels via a coreset within the second coreset group. The second TRP can transmit downlink signals / channels (e.g., PDSCH, PDCCH, DCI) via the second coreset group. Transmitting downlink signals / channels (e.g., PDCCH, DCI) via the second coreset group can include that the second TRP can transmit the downlink signals / channels via a coreset within the second coreset group. The second TRP can not transmit downlink signals / channels (e.g., PDCCH, DCI) via the first coreset group. Not transmitting downlink signals / channels (e.g., PDCCH, DCI) via the first coreset group can include that the second TRP can not transmit the downlink signals / channels via a coreset within the first coreset group.

[0346] In an example, the one or more configuration parameters can indicate a TRP index of the plurality of TRPs. In an example, each TRP of the plurality of TRPs can be identified by a respective TRP index of the TRP index. In an example, a first TRP of the plurality of TRPs (e.g., TRP 1 in FIG. 1) can be identified by a first TRP index of the TRP index. In an example, a second TRP of the plurality of TRPs (e.g., TRP 2 in FIG. 1) can be identified by a second TRP index of the TRP index. Figure 22 In an example, the one or more configuration parameters can indicate a TRP index of the plurality of TRPs. In an example, each TRP of the plurality of TRPs can be identified by a respective TRP index of the TRP index. In an example, a first TRP of the plurality of TRPs (e.g., TRP 1 in FIG. 1) can be identified by a first TRP index of the TRP index. In an example, a second TRP of the plurality of TRPs (e.g., TRP 2 in FIG. 1) can be identified by a second TRP index of the TRP index. Figure 22 In an example, the one or more configuration parameters can indicate a TRP index of the plurality of TRPs. In an example, each TRP of the plurality of TRPs can be identified by a respective TRP index of the TRP index. In an example, a first TRP of the plurality of TRPs (e.g., TRP 1 in FIG. 1) can be identified by a first TRP index of the TRP index. In an example, a second TRP of the plurality of TRPs (e.g., TRP 2 in FIG. 1) can be identified by a second TRP index of the TRP index.

[0347] In an example, the one or more configuration parameters can indicate a coreset index of the plurality of coresets (e.g., provided by a higher layer parameter ControlResourceSetld). In an example, each coreset of the plurality of coresets can be identified by a respective coreset index of the coreset index. In an example, a first coreset can be identified by a first coreset index of the coreset index. In an example, a second coreset can be identified by a second coreset index of the coreset index. In an example, a third coreset can be identified by a third coreset index of the coreset index. In an example, a fourth coreset can be identified by a fourth coreset index of the coreset index.

[0348] In an example, the one or more configuration parameters can indicate a core set group index of the plurality of core sets. In an example, each core set of the plurality of core sets can be identified by a respective one of the core set group indexes. In an example, a first core set of the first core set group can be identified by a first one of the core set group indexes. In an example, a third core set of the first core set group can be identified by a third one of the core set group indexes. In an example, a second core set of the second core set group can be identified by a second one of the core set group indexes. In an example, a fourth core set of the second core set group can be identified by a fourth one of the core set group indexes.

[0349] In an example, the wireless device can group one or more core sets of the plurality of core sets having a same core set group index in a (same) core set group of the plurality of core set groups. In an example, the wireless device can group core sets of the plurality of core sets having different core set group indexes in different core set groups. In an example, one or more core sets of the plurality of core sets in a core set group of the plurality of core set groups can have / share a same core set group index. In an example, the one or more configuration parameters can indicate a same core set group index for the one or more core sets in a core set group. The one or more core set group indexes of the one or more core sets in a core set group can be the same / equal. In an example, a respective core set group index of each core set of the one or more core sets in a core set group can be the same / equal.

[0350] In an example, the one or more first core sets of the first core set group can have / share a same core set group index (e.g., zero, one, two, etc.). In an example, the one or more configuration parameters can indicate the same core set group index of the one or more first core sets of the first core set group. In an example, the one or more configuration parameters can indicate the same core set group index of each core set of the one or more first core set group of the first core set group. In an example, the first core set group index and the third core set group index can be the same / equal. The wireless device can group the first core set and the third core set in the first core set group based on the first core set group index and the third core set group index being the same / equal. The first core set and the third core set can be in a same core set group (e.g., the first core set group) based on the first core set group index and the third core set group index being the same / equal.

[0351] In an example, the one or more second cores in the second core cluster group can have / share a same core cluster group index (e.g., zero, one, two, etc.). In an example, the one or more configuration parameters can indicate the same core cluster group index for the one or more second cores in the second core cluster group. In an example, the one or more configuration parameters can indicate the same core cluster group index for each core of the one or more second cores in the second core cluster group. In an example, the second core cluster group index and the fourth core cluster group index can be same / equal. The wireless device can group the second core and the fourth core in the second core cluster group based on the second core cluster group index and the fourth core cluster group index being same / equal. The second core and the fourth core can be in a same core cluster group (e.g., the second core cluster group) based on the second core cluster group index and the fourth core cluster group index being same / equal.

[0352] In an example, the first core cluster group index and the second core cluster group index can be different. The wireless device can group the first core and the second core in different core cluster groups based on the first core cluster group index and the second core cluster group index being different. In an example, the wireless device can group the first core in a first core cluster group. The wireless device can group the second core in a second core cluster group different from the first core cluster group based on the first core cluster group index and the second core cluster group index being different.

[0353] In an example, the plurality of core cluster groups can be identified by (or associated with) a group index. In an example, each of the plurality of core cluster groups can be identified by a respective one of the group index. In an example, the one or more configuration parameters can indicate the group index of the plurality of core cluster groups. In an example, a first core cluster group can be identified by (or associated with) a first one of the group index. The first core cluster group identified by (or associated with) the first one of the group index can include a respective core cluster group index of each core set in the first core cluster group being equal to the first one of the group index. The first core cluster group being identified by (or associated with) the first one of the group index can include a respective core cluster group index of each of the one or more first core sets in the first core cluster group being equal to the first one of the group index. In an example, a first core set in the first core cluster group has a first core cluster group index equal to the first one of the group index. In an example, a third core set in the first core cluster group has a third core cluster group index equal to the first one of the group index. A second core cluster group can be identified by (or associated with) a second one of the group index. The second core cluster group identified by (or associated with) the second one of the group index can include a respective core cluster group index of each core set in the second core cluster group being equal to the second one of the group index. The second core cluster group identified by (or associated with) the second one of the group index can include a respective core cluster group index of each of the one or more second core sets in the second core cluster group being equal to the second one of the group index. In an example, a second core set in the second core cluster group has a second core cluster group index equal to the second one of the group index. In an example, a fourth core set in the second core cluster group has a fourth core cluster group index equal to the second one of the group index.

[0354] In an example, the wireless device can monitor PDCCH for DCI via the plurality of core sets based on the one or more antenna port quasi-co-location properties (e.g., Figure 22 In an example, the wireless device can monitor PDCCH for DCI via the plurality of core sets based on the one or more antenna port quasi-co-location properties (e.g.,

[0355] In the example, receiving / detecting a PDCCH containing DCI via the core set of the multiple core sets based on the antenna port quasi-co-addressability properties of one or more antenna ports may include at least one DM-RS port of the PDCCH containing DCI quasi-co-addressability with a reference signal quasi-co-addressable (QCL-ed) indicated by the antenna port quasi-co-addressability properties (in the antenna port quasi-co-addressability properties). The antenna port quasi-co-addressability properties may include / indicate a reference signal (e.g., Figure 22 The antenna port quasi-co-addressability includes RS1 for core set 1, RS2 for core set 2, RS3 for core set 2, and RS4 for core set 4. The quasi-co-addressability of the antenna ports may include / indicate a reference signal index (e.g., SSB-index, CSI-RS-index, etc.). The at least one DM-RS port of the PDCCH may be quasi-co-addressable with the reference signal (QCL-ed) with respect to the quasi-co-addressability type (e.g., QCL-TypeA, QCL-TypeB, QCL-TypeC, QCL-TypeD). The antenna port quasi-co-addressability may include / indicate the quasi-co-addressability type. The antenna port quasi-co-addressability may include / indicate the quasi-co-addressability type of the reference signal.

[0356] In the example, the wireless device can be based on the first antenna port quasi-co-location property in one or more antenna port quasi-co-location properties (e.g., Figure 22 Antenna port QCL property 1) Monitoring the first PDCCH for the first DCI in the first core set / via the first core set. In the example, the wireless device can receive / detect the first PDCCH containing the first DCI via the first core set based on the first antenna port quasi-co-address property.

[0357] In the example, the wireless device can be based on the second antenna port quasi-co-location property in the one or more antenna port quasi-co-location properties (e.g., Figure 22 Antenna port QCL property 2) Monitoring the second PDCCH for the second DCI via the second core set. In the example, the wireless device can receive / detect the second PDCCH containing the second DCI via the second core set based on the second antenna port quasi-co-address property.

[0358] In the example, the wireless device can be based on the third antenna port quasi-co-location property in the one or more antenna port quasi-co-location properties (e.g., Figure 22 Antenna port QCL property 3) Monitoring the third PDCCH for the third DCI in / via the third core set. In the example, the wireless device can receive / detect the third PDCCH containing the third DCI via the third core set based on the quasi-co-location property of the third antenna port.

[0359] In an example, the wireless device can monitor a fourth PDCCH for a fourth DCI based on a fourth antenna port quasi-co-location property (e.g., Antenna Port QCL Property 4 in Figure 22 In an example, the wireless device can receive / detect the fourth PDCCH including the fourth DCI via the fourth coreset based on the fourth antenna port quasi-co-location property.

[0360] In an example, the first antenna port quasi-co-location property and the second antenna port quasi-co-location property can be the same. In an example, the first antenna port quasi-co-location property and the second antenna port quasi-co-location property can be different. In an example, the first antenna port quasi-co-location property and the third antenna port quasi-co-location property can be the same. In an example, the first antenna port quasi-co-location property and the third antenna port quasi-co-location property can be different. In an example, the first antenna port quasi-co-location property and the fourth antenna port quasi-co-location property can be the same. In an example, the first antenna port quasi-co-location property and the fourth antenna port quasi-co-location property can be different. In an example, the third antenna port quasi-co-location property and the second antenna port quasi-co-location property can be the same. In an example, the third antenna port quasi-co-location property and the second antenna port quasi-co-location property can be different. In an example, the fourth antenna port quasi-co-location property and the second antenna port quasi-co-location property can be the same. In an example, the fourth antenna port quasi-co-location property and the second antenna port quasi-co-location property can be different. In an example, the third antenna port quasi-co-location property and the fourth antenna port quasi-co-location property can be the same. In an example, the third antenna port quasi-co-location property and the fourth antenna port quasi-co-location property can be different.

[0361] In an example, the wireless device can group one or more core sets of the plurality of core sets that have a same antenna port quasi-co-location property in a (same) core set group of the plurality of core set groups. In an example, grouping the one or more core sets that have a same antenna port quasi-co-location property can include the wireless device grouping the one or more core sets, each core set having a respective antenna port quasi-co-location property that indicates a same reference signal. In an example, grouping the one or more core sets that have a same antenna port quasi-co-location property can include the wireless device grouping the one or more core sets, each core set having a respective antenna port quasi-co-location property that indicates a same reference signal having a same quasi-co-location type (e.g., QCL TypeD). In an example, the wireless device can group core sets of the plurality of core sets that have different antenna port quasi-co-location properties in different core set groups. In an example, one or more core sets of the plurality of core sets in a core set group of the plurality of core set groups can have / share a same antenna port quasi-co-location property. In an example, the one or more configuration parameters can indicate a same antenna port quasi-co-location property for the one or more core sets in a core set group. The one or more antenna port quasi-co-location properties of the one or more core sets in a core set group can be the same. In an example, the respective antenna port quasi-co-location property of each core set of the one or more core sets in a core set group can be the same.

[0362] In an example, the one or more first core sets in the first core set group can have / share a same antenna port quasi-co-location property. In an example, the first antenna port quasi-co-location property and the third antenna port quasi-co-location property can be the same. In an example, the first antenna port quasi-co-location property and the third antenna port quasi-co-location property being the same can include a first reference signal (e.g., RS 1) in (or indicated by) the first antenna port quasi-co-location property and a third reference signal (e.g., Figure 22 in the third antenna port quasi-co-location property being the same. In an example, the first antenna port quasi-co-location property and the third antenna port quasi-co-location property being the same can include a first reference signal (e.g., RS 1) in (or indicated by) the first antenna port quasi-co-location property and a third reference signal (e.g., Figure 22RS 3) in the first antenna port quasi-co-location property (or indicated by the first antenna port quasi-co-location property) and a fourth reference signal (e.g., RS 4) in the fourth antenna port quasi-co-location property (or indicated by the fourth antenna port quasi-co-location property) can be QCL-ed with respect to a quasi-co-location type (e.g., QCL-typeD). The wireless device can group the second core set and the fourth core set in the second core set group based on the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same. Based on the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same, the second core set and the fourth core set can be in the same core set group (e.g., the second core set group).

[0363] In an example, the one or more second core sets in the second core set group can have / share the same antenna port quasi-co-location property. In an example, a second antenna port quasi-co-location property and a fourth antenna port quasi-co-location property can be the same. In an example, the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same can include a second reference signal (e.g., RS 2) in the second antenna port quasi-co-location property (or indicated by the second antenna port quasi-co-location property) and a fourth reference signal (e.g., RS 4) in the fourth antenna port quasi-co-location property (or indicated by the fourth antenna port quasi-co-location property) can be QCL-ed with respect to a quasi-co-location type (e.g., QCL-typeD). The wireless device can group the second core set and the fourth core set in the second core set group based on the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same. Based on the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same, the second core set and the fourth core set can be in the same core set group (e.g., the second core set group). Figure 22 Figure 22 In an example, the one or more second core sets in the second core set group can have / share the same antenna port quasi-co-location property. In an example, a second antenna port quasi-co-location property and a fourth antenna port quasi-co-location property can be the same. In an example, the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same can include a second reference signal (e.g., RS 2) in the second antenna port quasi-co-location property (or indicated by the second antenna port quasi-co-location property) and a fourth reference signal (e.g., RS 4) in the fourth antenna port quasi-co-location property (or indicated by the fourth antenna port quasi-co-location property) can be QCL-ed with respect to a quasi-co-location type (e.g., QCL-typeD). The wireless device can group the second core set and the fourth core set in the second core set group based on the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same. Based on the second antenna port quasi-co-location property and the fourth antenna port quasi-co-location property being the same, the second core set and the fourth core set can be in the same core set group (e.g., the second core set group).

[0364] In an example, the wireless device can group different core sets in different core set groups based on respective antenna port quasi-co-location properties of the two core sets being different. In an example, a first antenna port quasi-co-location property and a second antenna port quasi-co-location property can be different. In an example, the first antenna port quasi-co-location property and the second antenna port quasi-co-location property being different can include a first reference signal (e.g., RS 1) in the first antenna port quasi-co-location property (or indicated by the first antenna port quasi-co-location property) and a second reference signal (e.g., RS 2) in the second antenna port quasi-co-location property (or indicated by the second antenna port quasi-co-location property) can be QCL-ed with respect to a quasi-co-location type (e.g., QCL-typeD). The wireless device can group the first core set and the second core set in different core set groups based on the first antenna port quasi-co-location property and the second antenna port quasi-co-location property being different. Based on the first antenna port quasi-co-location property and the second antenna port quasi-co-location property being different, the first core set and the second core set can be in different core set groups (e.g., the first core set group and the second core set group). Figure 22 ​RS 1) and the second reference signal in the quasi-co-location property of the second antenna port (or indicated by the quasi-co-location property of the second antenna port) (e.g., Figure 22 RS 2) in the first antenna port can be different. In the example, the difference between the first antenna port quasi-co-location nature and the second antenna port quasi-co-location nature may include a first reference signal in the first antenna port quasi-co-location nature (or indicated by the first antenna port quasi-co-location nature) and a second reference signal in the second antenna port quasi-co-location nature (or indicated by the second antenna port quasi-co-location nature) that are not related to the quasi-co-location type (e.g., QCL-typeD) QCL-ed. The wireless device may group the first core set and the second core set into different core cluster groups based on the difference between the first antenna port quasi-co-location nature and the second antenna port quasi-co-location nature. The first core set and the second core set may be in different core cluster groups based on the difference between the first antenna port quasi-co-location nature and the second antenna port quasi-co-location nature. In the example, the wireless device may group the first core set into the first core cluster group. The wireless device may group the second core set into a second core cluster group different from the first core cluster group based on the difference between the first antenna port quasi-co-location nature and the second antenna port quasi-co-location nature.

[0365] In the example, a cell may include multiple BWPs. These multiple BWPs may include one or more uplink BWPs, which include the cell's uplink BWPs. These multiple BWPs may also include one or more downlink BWPs, which include the cell's downlink BWPs.

[0366] In the example, one or more configuration parameters can indicate the multiple core sets on the cell's downlink BWP / for the cell's downlink BWP.

[0367] In the example, one or more configuration parameters can indicate the PRACH transmission parameters (e.g., time-frequency resources, PRACH timing, etc.) on the cell's uplink BWP or for the cell's uplink BWP.

[0368] In the example, the radio device can activate one or more downlink BWPs of the cell as the active downlink BWP of the cell. In the example, the radio device can activate one or more uplink BWPs of the cell as the active uplink BWP.

[0369] In the example, the wireless device can receive a Physical Downlink Control Channel (PDCCH) command that initiates a random access procedure (e.g., Figure 22 The PDCCH command in the first core group). The wireless device can be transmitted via the first core set in the first core cluster group (e.g., Figure 22The first core 1 in the core set group 1 in the cell receives the PDCCH order. The random access procedure can be a contention-free random access procedure (e.g., a contention-free based random access procedure). The wireless device can initiate the random access procedure of the cell. The PDCCH order can initiate / trigger the random access procedure of the cell. The wireless device can initiate the random access procedure based on receiving the PDCCH order.

[0370] In an example, the wireless device can monitor the first PDCCH for the first DCI in the first core set / via the first core set receiving the PDCCH order based on the first antenna port quasi-co-location property (e.g., Figure 22 In an example, the wireless device can monitor the first PDCCH for the first DCI in the first core set / via the first core set receiving the PDCCH order based on the first antenna port quasi-co-location property (e.g., Figure 22 In an example, the wireless device can receive / detect the first PDCCH containing the first DCI while monitoring the first PDCCH for the first DCI in the first core set / via the first core set. In an example, the wireless device can receive / detect the first PDCCH containing the first DCI via the first core set based on the first antenna port quasi-co-location property. In an example, the first DCI can indicate the PDCCH order initiating / triggering the random access procedure. In an example, the wireless device can receive / detect the first PDCCH containing the first DCI indicating the PDCCH order via the first core set based on the first antenna port quasi-co-location property. The wireless device can receive the PDCCH order in the first core set / via the first core set based on the first antenna port quasi-co-location property. Receiving / detecting the first PDCCH in the first core set / via the first core set based on the first antenna port quasi-co-location property can include (the wireless device determining) that the at least one first DM-RS port of the first PDCCH is quasi co-located (QCL-ed) with a first reference signal (e.g.,

[0371] In an example, the wireless device can monitor the first PDCCH for the first DCI in the first core set / via the first core set receiving the PDCCH order based on the first antenna port quasi-co-location property (e.g., Figure 22RS 1) quasi co-located (QCL-ed). The at least one first DM-RS port of the first PDCCH can be QCL-ed with the first reference signal with respect to a first quasi co-location type (e.g., QCL TypeD, QCL TypeA, etc.).

[0372] In an example, based on receiving the PDCCH order, the wireless device can transmit a random access preamble of a random access procedure. The wireless device can transmit the random access preamble via at least one random access resource (e.g., PRACH occasion) of the active uplink BWP of the cell.

[0373] In an example, based on transmitting the random access preamble, the wireless device can monitor (or start monitoring) for a second DCI (e.g., DCI format 1_0 in Figure 22 In an example, based on transmitting the random access preamble, the wireless device can monitor (or start monitoring) for a second DCI (e.g., DCI format 1_0 in Figure 22 In an example, based on transmitting the random access preamble, the wireless device can monitor (or start monitoring) for a second DCI (e.g., DCI format 1_0 in

[0374] In an example, the monitoring for the second DCI can include that the wireless device can monitor a second coreset of a second coreset group for the second DCI (e.g., the second coreset of the second coreset group can be indicated by a search space set of the second DCI). Figure 22In an example, monitoring the second PDCCH in the second core set in the second core set group based on the second antenna port quasi co-location property for the second DCI can include monitoring the second PDCCH for the second DCI in a PDCCH monitoring occasion of / for a search space set associated with (or linked to) the second core set in the second core set group. The one or more configuration parameters can indicate the PDCCH monitoring occasion of / for the search space set. In an example, the wireless device can monitor the second PDCCH for the second DCI in the second core set based on a second antenna port quasi co-location property of the second core set associated with (or linked to) the search space set. In an example, the wireless device can determine that the first core set group including the first core set that the PDCCH order is received from can be different from the second core set group including the second core set that the second DCI is monitored for. In an example, based on the determination, the wireless device can monitor the second PDCCH for the second DCI in the second core set based on a second antenna port quasi co-location property of the second core set associated with (or linked to) the search space set. In an example, the search space set can be a Type1-PDCCH CSS set. In an example, the search space set can be a common search space set. In an example, the search space set can be associated with (or linked to) the second core set. In an example, the one or more configuration parameters can indicate a ra-search space of the search space set.

[0375] In an example, monitoring the second PDCCH in the second core set in the second core set group based on the second antenna port quasi co-location property for the second DCI can include at least one second DM-RS port of the second PDCCH being quasi co-located (QCL-ed) with a second reference signal (e.g., RS 2) indicated by the second antenna port quasi co-location property (in the second antenna port quasi co-location property). Figure 22 In an example, monitoring the second PDCCH in the second core set in the second core set group based on the second antenna port quasi co-location property for the second DCI can include at least one second DM-RS port of the second PDCCH being quasi co-located (QCL-ed) with a second reference signal (e.g., RS 2) indicated by the second antenna port quasi co-location property (in the second antenna port quasi co-location property).

[0376] In an example, the first core set group including the first core set that the PDCCH order is received from and the second core set group including the second core set that the second DCI is monitored for can be different. In an example, the wireless device can determine that the first core set group and the second core set group are different. The first core set group and the second core set group being different can include a first group index of the first core set group and a second group index of the second core set group being different.

[0377] In the example, the wireless device can receive / detect a second PDCCH of the second DCI that includes / includes a search space set (e.g., a Type 1-PDCCH CSS set) in the second core set. In the example, the wireless device can receive the second PDCCH based on (or simultaneously) monitoring the second PDCCH of the search space set for the second DCI in the second core set. In the example, the wireless device can receive the second PDCCH of the second DCI that includes / includes the search space set (e.g., a Type 1-PDCCH CSS set) in the second core set based on the quasi-co-addressable nature of the second antenna port of the second core set associated with (or linked to) the search space set. The wireless device can complete a random access procedure based on receiving the second PDCCH. The second DCI can schedule a random access response (e.g., containing a random access preamble) corresponding to the random access preamble. Figure 22 The PDSCH (Personalized Access Response) is used in the random access response. In the example, the wireless device can complete the random access procedure based on receiving a random access response corresponding to the random access preamble. The random access response corresponding to the random access preamble may include an indication of the random access preamble (or a random access preamble index of the random access preamble).

[0378] In the example, monitoring of the second DCI may include the wireless device being located in a second core set within the first core cluster group (e.g., Figure 22monitor a second PDCCH for a second DCI in a second core set in a second core set group (e.g., a second core set in a second core set group 1 or a second core set in a second core set group 3 in FIG. 13B). Monitoring the second PDCCH for the second DCI in the second core set in the first core set group can include that the wireless device can monitor the second PDCCH for the second DCI in a PDCCH monitoring occasion of / for a search space set associated with (or linked to) the second core set of the first core set group. The one or more configuration parameters can indicate the PDCCH monitoring occasion of / for the search space set. In an example, the wireless device can monitor the second PDCCH for the second DCI in the second core set based on the first antenna port quasi-co-location property of the first core set in which the PDCCH order is received. In an example, based on monitoring the second PDCCH for the second DCI in the second core set, the wireless device can update (replace / assume) a second antenna port quasi-co-location property of the second core set to be the first antenna port quasi-co-location property of the first core set in which the PDCCH order is received. In an example, based on monitoring the second PDCCH for the second DCI in the second core set, the second antenna port quasi-co-location property of the second core set can be the same as the first antenna port quasi-co-location property of the first core set in which the PDCCH order is received. In an example, the wireless device can determine that the first core set group contains the first core set in which the PDCCH order is received and the second core set in which the second PDCCH is monitored for the second DCI. In an example, the wireless device can determine that the first core set in which the PDCCH order is received and the second core set in which the second PDCCH is monitored for the second DCI belong to the first core set group (e.g., a same core set group). In an example, based on the determination, the wireless device can monitor the second PDCCH for the second DCI in the second core set based on the first antenna port quasi-co-location property of the first core set in which the PDCCH order is received. In an example, the search space set can be a Type1-PDCCH CSS set. In an example, the search space set can be a common search space set. In an example, the search space set can be associated with (or linked to) the second core set. In an example, the one or more configuration parameters can indicate a ra-search space of / for the search space set.

[0379] In an example, monitoring the second PDCCH for the second DCI in the second core set based on the first antenna port quasi-co-location property can include that at least one second DM-RS port of the second PDCCH is quasi co-located (QCL-ed) with a first reference signal (e.g., RS 1 in FIG. 13B) indicated by (in) the first antenna port quasi-co-location property. The at least one second DM-RS port of the second PDCCH can be QCL-ed with the first reference signal with respect to a first quasi co-location type (e.g., QCL TypeD, QCL TypeA, etc.). Figure 22

[0380] ​In an example, based on monitoring the second PDCCH for the second DCI in the second coreset, the wireless device can determine that the first antenna port quasi-co-location property of the first PDCCH indicating / containing the PDCCH order is the same as the second antenna port quasi-co-location property of the second PDCCH containing the second DCI. Based on the determination, the wireless device can set the second antenna port quasi-co-location property to be the same as the first antenna port quasi-co-location property. Based on the setting, the second antenna port quasi-co-location property can include a first reference signal in the first antenna port quasi-co-location property. Based on the setting, a second reference signal can be updated with the first reference signal in the first antenna port quasi-co-location property. Based on the setting, the second antenna port quasi-co-location property can include a first quasi-co-location type in the first antenna port quasi-co-location property. Based on the setting, a second quasi-co-location type can be updated with the first quasi-co-location type in the first antenna port quasi-co-location property.

[0381] In an example, the wireless device can receive the second PDCCH containing / including the second DCI of a search space set (e.g., Type1-PDCCH CSS set) in the second coreset. In an example, the wireless device can receive the second PDCCH based on (or concurrently with) monitoring the second PDCCH for the second DCI of the search space set in the second coreset. In an example, the wireless device can receive the second PDCCH containing / including the second DCI of a search space set (e.g., Type1-PDCCH CSS set) in the second coreset based on the first antenna ...

Claims

1. A method of communication, comprising: receiving, by a wireless device and via a first control resource set (coreset) having a first coreset group index, a physical downlink control channel (PDCCH) order initiating a random access procedure; transmitting a random access preamble of the random access procedure; and receiving, via a second coreset having a second coreset group index, downlink control information (DCI) scheduling a random access response corresponding to the random access preamble, wherein receiving the DCI is based on: a first transmission configuration indicator (TCI) state of the first coreset in response to the first coreset group index being the same as the second coreset group index; and a second TCI state of the second coreset in response to the first coreset group index being different from the second coreset group index.

2. The method of claim 1, further comprising receiving one or more messages containing one or more configuration parameters of a cell.

3. The method of claim 1, further comprising: monitoring a PDCCH in the first coreset based on the first TCI state.

4. The method of claim 1, wherein receiving the DCI based on the second TCI state comprises: at least one demodulation reference signal (DM-RS) port of a PDCCH carrying the DCI received in the second coreset is quasi co-located with a second reference signal indicated by the second TCI state.

5. The method of any one of claims 1-4, further comprising receiving the random access response, wherein receiving the random access response is based on: the first TCI state of the first coreset in response to the first coreset group index being the same as the second coreset group index; and the second TCI state of the second coreset in response to the first coreset group index being different from the second coreset group index.

6. A 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 perform the method of any one of claims 1-5.

7. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1-5.

8. A method of communication, comprising: transmitting, by a base station and via a first control resource set (coreset) having a first coreset group index, a physical downlink control channel (PDCCH) order initiating a random access procedure; receiving a random access preamble of the random access procedure; and transmitting, via a second coreset having a second coreset group index, downlink control information (DCI) corresponding to the random access preamble for scheduling a random access response, wherein transmitting the DCI is based on: a first transmission configuration indicator (TCI) state of the first coreset in response to the first coreset group index being the same as the second coreset group index; and a second TCI state of the second coreset in response to the first coreset group index being different from the second coreset group index. a first transmission configuration indicator, TCI, state of the first coreset in response to the first coreset group index being the same as the second coreset group index; and a second TCI state of the second coreset in response to the first coreset group index being different from the second coreset group index.

9. The method of claim 8, further comprising: transmitting one or more messages comprising one or more configuration parameters of a cell.

10. The method of claim 9, wherein the one or more configuration parameters indicate the first coreset and the second coreset of an active downlink bandwidth part, BWP, of the cell.

11. The method of claim 8, wherein transmitting the DCI based on the second TCI state comprises: at least one demodulation reference signal, DM-RS, port of a PDCCH carrying the DCI transmitted in the second coreset is quasi co-located with a second reference signal indicated by the second TCI state.

12. The method of any one of claims 8-11, further comprising transmitting the random access response, wherein transmitting the random access response is based on: a first TCI state of the first coreset in response to the first coreset group index being the same as the second coreset group index; and a second TCI state of the second coreset in response to the first coreset group index being different from the second coreset group index.

13. A base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to perform the method of any one of claims 8-12.

14. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 8-12.

15. A communication system 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: initiate a physical downlink control channel, PDCCH, order of a random access procedure via a first coreset transmission having a first coreset group index; receive a random access preamble of the random access procedure; and transmit, via a second coreset transmission having a second coreset group index, downlink control information, DCI, corresponding to the random access preamble for scheduling a random access response, wherein transmitting the DCI is based on: a first transmission configuration indicator, TCI, state of the first coreset in response to the first coreset group index being the same as the second coreset group index; and a second TCI state of the second coreset in response to the first coreset group index being different from the second coreset group index; 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 first processors, cause the wireless device to: receive a physical downlink control channel, PDCCH, order to initiate a random access procedure; transmit a random access preamble for the random access procedure; and receive DCI scheduling a random access response corresponding to the random access preamble.

Images