Channel state information reporting for mobility enhancement

Abstract

A wireless device receives, via a first cell, a command indicating uplink transmissions of channel state information (CSI) reports in a first time slot for one or more candidate cells of a layer 1 / 2 triggered mobility (LTM) procedure. The wireless device, for receiving a reference signal (RS) for the CSI reporting, determines a symbol prior to the first time slot based on beam reporting timing. The wireless device transmits, in the first time slot and via the first cell, the CSI report measured on a first RS of the one or more candidate cells, wherein the first RS is received not later than the symbol and within a measurement window.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 440,155, filed on January 20, 2023, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] Figure 1A and Figure 1B An example mobile communications network is presented in which embodiments of the present disclosure may be implemented.

[0005] Figure 2A and Figure 2B The New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0006] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Shows the flow Figure 2A Figure 2 shows an example downlink data flow of the NR user plane protocol stack.

[0008] Figure 4B Shows an example format of the MAC subheader in a MAC PDU.

[0009] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels for downlink and uplink respectively is shown.

[0010] Figure 6 is an example diagram showing RRC state transition of a UE.

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

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

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

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

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

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

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

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

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

[0020] Figure 14A An example of CORESET configuration showing the bandwidth portion.

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

[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 Example structures for uplink and downlink transmissions are shown.

[0024] Figure 17A 、 Figure 17B and Figure 17C An example of a MAC subheader is shown.

[0025] Figure 18A An example of a DL MAC PDU is shown.

[0026] Figure 18B An example of a UL MAC PDU is shown.

[0027] Figure 19 An example of multiple LCIDs for the downlink is shown.

[0028] Figure 20 An example of multiple LCIDs for the uplink is shown.

[0029] Figure 21A and Figure 21BAn example of the SCell activation / deactivation MAC CE format is shown.

[0030] Figure 22 An example of BWP activation / deactivation on a cell is shown.

[0031] Figure 23 Examples of various DCI formats are shown.

[0032] Figure 24A An example of a MIB message is shown.

[0033] Figure 24B An example of the configuration of CORESET 0 is shown.

[0034] Figure 24C An example of the configuration of search space 0 is shown.

[0035] Figure 25 An example of a SIB1 message is shown.

[0036] Figure 26 An example of RRC configuration of BWP, PDCCH and CORESET is shown.

[0037] Figure 27 An example of RRC configuration of the search space is shown.

[0038] Figure 28 An example of an SSB configuration is shown.

[0039] Figure 29 An example of SSB transmission by a base station is shown.

[0040] Figure 30 An example of SSB transmission by a base station is shown.

[0041] Figure 31A and Figure 31B An example embodiment of a multi-TRP configuration is shown.

[0042] Figure 32 An example embodiment of a layer 3 based handover procedure is shown.

[0043] Figure 33 An example embodiment of RRC messages for layer 3 based handover is shown.

[0044] Figure 34 An example embodiment of RRC messages for layer 3 based handover is shown.

[0045] Figure 35 An example embodiment of a layer 3 based conditional handover procedure is shown.

[0046] Figure 36An example embodiment of RRC messages for a layer 3 based conditional handover procedure is shown.

[0047] Figure 37 An example embodiment of layer 1 / 2 triggered mobility is shown.

[0048] Figure 38 An example embodiment of inter-cell beam management is shown.

[0049] Figure 39 An example embodiment of layer 1 / 2 triggered mobility with early CSI reporting is shown.

[0050] Figure 40 Example embodiments of RRC messages for CSI reporting are shown.

[0051] Figure 41 Example embodiments of RRC messages for CSI reporting are shown.

[0052] Figure 42 Example embodiments of RRC messages for CSI reporting are shown.

[0053] Figure 43 An example embodiment of layer 1 CSI reporting is shown.

[0054] Figure 44A and Figure 44B An example embodiment of CSI calculation delay requirements is shown.

[0055] Figure 45 An example embodiment of layer 1 measurement gaps for layer 1 / 2 triggered mobility is shown.

[0056] Figure 46 An example embodiment of layer 1 / 2 CSI reporting for layer 1 / 2 triggered mobility is shown.

[0057] Figure 47 An example embodiment of layer 1 / 2 CSI reporting for layer 1 / 2 triggered mobility is shown.

[0058] Figure 48 An example flow diagram of layer 1 / 2 CSI reporting for layer 1 / 2 triggered mobility is shown. DETAILED DESCRIPTION

[0059] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited by any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features and / or elements from the disclosed example embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figures that highlight functionality and advantages are provided for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0060] Embodiments can be configured to operate as desired. For example, the disclosed mechanisms can be implemented when certain criteria are met in a wireless device, base station, radio environment, network, combinations thereof, and the like. Example criteria can be based, at least in part, on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, combinations thereof, and the like. When one or more criteria are met, various example embodiments can be applied. Thus, example embodiments that selectively implement the disclosed protocols can be implemented.

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

[0062] In this disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will 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 the phrase following the term "may" is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms "including" and "consisting of" list one or more components of the element being described. The terms "including" and "comprising" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of" provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed elements. 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.

[0063] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently, "based at least on") indicates that the phrase following the term "based on" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments. The phrase "in response to" (or equivalently, "in response to at least") indicates that the phrase following the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments. The phrase "depending on" (or equivalently, "depending on at least") indicates that the phrase following the phrase "depending on" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments. The phrase "using / adopting" (or equivalently, "at least adopting / adopting") indicates that the phrase following the phrase "adopting / adopting" is an example of one of multiple suitable possibilities that may or may not be used in one or more different embodiments.

[0064] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings in a device that affect the operational characteristics of the device, whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. can be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Terms such as "a control message induced in a device" can mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0065] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may 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 an example embodiment, when one or more messages include multiple parameters, it means that the parameters of the multiple parameters are in at least one of the one or more messages, but not necessarily in every one of the one or more messages.

[0066] Many of the features set forth are described as optional, either by the use of "may" or by the use of parentheses. For the sake of 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 as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely, having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0067] Many elements described in the disclosed embodiments can be implemented as modules. Modules are defined here as elements that perform defined functions and have defined interfaces to other elements. The modules described in this disclosure can be implemented with hardware, software, firmware, wetware (e.g., hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior. For example, a module can be implemented as a software routine written in a computer language that is configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, MATLAB, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement a module using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between the smaller internal hardware blocks on the programmable device. The aforementioned techniques are often used in combination to achieve the desired functional blocks.

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

[0069] The CN 102 may provide an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-carrier DNs, for the wireless device 106. As part of the interface functionality, the CN 102 may establish an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

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

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

[0072] The RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to refer to and encompass: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a forwarder node or relay node used to extend the coverage area of ​​a donor node; a next-generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

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

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

[0075] The RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high-level transmit power. The RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas that overlap with the relatively larger coverage area provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0077] Figure 1BAnother example mobile communication network 150 is shown in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG, 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). Figure 1A Corresponding components are described as being implemented and operating in the same or similar manner.

[0078] 5G-CN 152 provides an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN, to the UE 156. As part of the interface functionality, the 5G-CN 152 can establish an end-to-end connection between the UE 156 and the one or more DNs, authenticate the UE 156, and provide charging functionality. Compared to the CN of the 3GPP 4G network, the basis of the 5G-CN 152 can be a service-based architecture. This means that the architecture of the nodes that make up the 5G-CN 152 can be defined as network functions that provide services to other network functions via interfaces. The network functions of the 5G-CN 152 can be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0079] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are shown in FIG. Figure 1B In the figure, they are shown as one component AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification to support routing of service flows to the one or more DNs, user plane quality of service (QoS) handling (e.g., packet filtering, gating, uplink / downlink rate enforcement and uplink service verification), 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 fulcrum to support multi-homed PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

[0080] The AMF 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policy), network slicing support and / or session management function (SMF) selection. NAS may refer to a function operating between the CN and the UE, and AS may refer to a function operating between the UE and the RAN.

[0081] 5G-CN 152 may include for clarity Figure 1B One or more additional network functions not shown in the figure. For example, the 5G-CN 152 may 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).

[0082] The NG-RAN 154 can connect the 5G-CN 152 to the UE 156 via radio communications over the air interface. The NG-RAN 154 can include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively, gNB 160), and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively, ng-eNB 162). The gNBs 160 and ng-eNB 162 can be more generally referred to as base stations. The gNBs 160 and ng-eNB 162 can include one or more antennas for communicating with the UE 156 over the air interface. For example, one or more gNBs in gNB 160 and / or one or more ng-eNBs in ng-eNB 162 can include three antennas to control three cells (or sectors), respectively. The cells of gNB 160 and ng-eNB 162 may together provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

[0083] like Figure 1BAs shown in FIG, gNB 160 and / or ng-eNB 162 can be connected to 5G-CN 152 via an NG interface and connected to other base stations via an Xn interface. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections through an underlying transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can be connected to UE 156 via a Uu interface. For example, Figure 1B As shown in FIG, gNB 160A can be connected to UE 156A via a Uu interface. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stack associated with the interface can be composed of Figure 1B Network elements in a network exchange data and signaling messages and may include two planes: the user plane and the control plane. The user plane handles data of interest to users, while the control plane handles signaling messages of interest to network elements.

[0084] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, via one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide for delivery of user plane PDUs (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A via an NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, delivery of NAS messages, paging, PDU session management, and configuration delivery and / or warning message transmission.

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

[0086] The 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 4G core network in a mode known as "non-standalone operation." In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B Only one AMF / UPF 158 is shown in the figure, 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.

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

[0088] Figure 2A and Figure 2B Examples of the NR user plane and NR control plane protocol stacks for the Uu interface between the UE 210 and the gNB 220 are shown, respectively. Figure 2A and Figure 2B The protocol stack shown in the can be used with e.g. Figure 1B The protocol stacks of the Uu interface between UE 156A and gNB 160A shown in FIG are the same or similar.

[0089] Figure 2A The NR user plane protocol stack is shown, including five layers implemented in the UE 210 and gNB 220. At the bottom of the protocol stack, the physical layers (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and can correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include the medium access control layer (MAC) 212 and 222, the radio link control layer (RLC) 213 and 223, the packet data convergence protocol layer (PDCP) 214 and 224, and the service data application protocol layer (SDAP) 215 and 225. Together, these four protocols can constitute layer 2, or the data link layer, of the OSI model.

[0090] Figure 3 Shows examples of services provided between protocol layers of the NR user plane protocol stack. Figure 2A and Figure 3Starting from the top, SDAPs 215 and 225 can perform QoS flow handling. UE 210 can receive services via 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. The CN's UPF (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping 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, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0091] PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection to ensure that control messages originate from the intended source. PDCPs 214 and 224 can also perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate packets received due to, for example, intra-gNB handovers. PDCPs 214 and 224 can also perform packet duplication to increase the likelihood of packet reception and remove any duplicate packets at the receiver. Packet duplication can be suitable for services requiring high reliability.

[0092] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in dual connectivity scenarios. Dual connectivity is a technology that allows a UE to be connected to two cells or more generally to two cell groups: a master cell group (MCG) and a secondary cell group (SCG). Split bearers are split bearers when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapped split radio bearers between RLC channels belonging to a cell group.

[0093] RLC 213 and 223 can perform segmentation, retransmission via automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be on a per-logical channel basis, independent of parameter sets and / or transmission time interval (TTI) durations. Figure 3 As shown in FIG, RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0094] MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs using dynamic scheduling. Scheduling may be performed in gNB 220 (at MAC 222) for both downlink and uplink. MACs 212 and 222 may be configured to perform error correction using hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of UE 210 using logical channel prioritization, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timing. In an example, mapping restrictions in logical channel prioritization can control which parameter sets and / or transmission timings a logical channel can use. Figure 3 As shown in FIG, MAC 212 and 222 may provide logical channels as a service to RLC 213 and 223.

[0095] PHY 211 and 221 can perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions can include, for example, encoding / decoding and modulation / demodulation. PHY 211 and 221 can perform multi-antenna mapping. Figure 3 As shown in , PHYs 211 and 221 may provide one or more transport channels as a service to MACs 212 and 222 .

[0096] Figure 4A Shows an example downlink data flow through the NR user plane protocol stack. Figure 4AThe figure shows the downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two TBs at the gNB 220. The uplink data flow through the NR user plane protocol stack can be the same as Figure 4A The downlink data flow is similar to that depicted in .

[0097] Figure 4A The downlink data flow of starts when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. Figure 4A In the SDAP header (in Figure 4A The data unit from / to the higher protocol layer is called the service data unit (SDU) of the lower protocol layer, and the data unit to / from the lower protocol layer is called the protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data units from SDAP 225 are SDUs of the lower protocol layer PDCP 224 and are PDUs of SDAP 225 .

[0098] Figure 4A The remaining protocol layers in the Figure 3 ), add the corresponding headers and forward their corresponding output to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 2) and forwards its output to the MAC 222. The MAC 222 may multiplex many RLC PDUs and may append MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDUs, as shown in FIG. Figure 4A In LTE, the MAC subheader can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU subheader can be calculated before assembling the complete MAC PDU.

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

[0100] Figure 4B Further shown is a MAC Control Element (CE) inserted into a MAC PDU by a MAC (e.g., MAC 223 or MAC 222). For example, Figure 4B The two MAC CEs inserted into the MAC PDU are shown. Figure 4B ) and a MAC CE is inserted at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reporting and power headroom reporting; activation / deactivation MAC CEs, such as those used for PDCP duplicate 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. The MAC CE may be preceded by a MAC subheader having a format similar to that described for the MAC SDU, and may be identified with a reserved value in the LCID field that indicates the type of control information contained in the MAC CE.

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

[0102] Figure 5A and Figure 5BThe mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively. Information is passed 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 as control channels that carry control and configuration information in the NR control plane, or as traffic channels that carry data in the NR user plane. Logical channels can be classified as dedicated logical channels dedicated to a specific UE, or as common logical channels that 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:

[0103] --Paging Control Channel (PCCH), which is used to carry paging messages used to page UEs whose locations are unknown to the network at the cell level;

[0104] - 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), which can be used by UEs to obtain information about how a cell is configured and how it operates within the cell;

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

[0106] - a dedicated control channel (DCCH), which is used to carry control messages to / from a specific UE to configure the UE; and

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

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

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

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

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

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

[0113] -- Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

[0114] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have a set of associated time-frequency resources for carrying information for one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide control information to the lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

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

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

[0117] Physical Downlink Control Channel (PDCCH), which carries Downlink Control Information (DCI), including downlink scheduling commands, uplink scheduling grants, and uplink power control commands.

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

[0119] -- Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and scheduling request (SR); and

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

[0121] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. Figure 5A and Figure 5B As shown in [1], the physical layer signals defined by NR include: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Sounding Reference Signal (SRS), and Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0122] Figure 2BAn example NR control plane protocol stack is shown. Figure 2B As shown in , the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0123] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., AMF 158A), or more generally between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages known as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which NAS messages may be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

[0124] RRCs 216 and 226 may provide control plane functionality between UE 210 and gNB 220, or more generally, between UE 210 and the RAN. RRCs 216 and 226 may provide control plane functionality between UE 210 and gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transported between UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC may multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to the 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 such reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS messaging. As part of establishing an RRC connection, the RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0125] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG or any other wireless device described in this disclosure is the same or similar. Figure 6 As shown in , the UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, RRC_INACTIVE).

[0126] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in the RAN 104 depicted in FIG; Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG; Figure 2A and Figure 2B ; or any other base station described in the present disclosure. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may include parameters used for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to 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. While in RRC connection 602, the UE's mobility may be managed by a RAN (e.g., RAN 104 or NG-RAN 154). The UE may 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 may request handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

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

[0128] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows for a quick 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 may be in a sleep state, and the UE's mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 via a Connection Resumption Procedure 614, or to RRC Idle 604 via a Connection Release Procedure 616, which may be the same as or similar to the Connection Release Procedure 608.

[0129] The RRC state 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 notify the UE of events via paging messages without having to broadcast paging messages across the entire mobile communications network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 can allow the network to track the UE at a cell group level, so that paging messages can be broadcast to cells in the cell group in which the UE is currently residing, rather than across the entire mobile communications network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 track the UE at a cell group level. These mobility management mechanisms can do so using groupings of different granularities. For example, there can be three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas, known as tracking areas and identified by a Tracking Area Identifier (TAI).

[0130] Tracking areas can be used to track UEs 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 that is not included in the list of TAIs associated with the UE's registration area through cell reselection, the UE can perform a registration update on the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0131] RAN areas can be used to track UEs at the RAN level. For a UE in the RRC Inactive 606 state, a RAN notification area can be assigned to the UE. The RAN notification area can include one or more cell identifiers, a list of RAIs, or a list of TAIs. In an example, a base station can belong to one or more RAN notification areas. In an example, a cell can belong to one or more RAN notification areas. If a UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE can perform a notification area update on the RAN to update the UE's RAN notification area.

[0132] The base station that stores the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least for the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or for the period of time that the UE remains in RRC inactivity 606.

[0133] gNB, such as Figure 1B The gNB 160 in the LTE network can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DUs). The gNB-CU can be coupled to one or more gNB-DUs using the F1 interface. The gNB-CU can include RRC, PDCP, and SDAP. The gNB-DU can include RLC, MAC, and PHY.

[0134] In NR, physical signals and physical channels (about Figure 5A and Figure 5BDiscussed) 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). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be treated as if they were in the frequency domain and used as input 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 source symbol from each of the F parallel symbol streams) and use each source symbol to modulate the amplitude and phase of one of the 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 symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. This operation produces discrete Fourier transform (DFT) precoded OFDM symbols that can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbols at the receiver to recover the data mapped to the source symbols.

[0135] Figure 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As shown, an NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes of 1 ms duration. A subframe may be divided into slots, each containing, for example, 14 OFDM symbols.

[0136] The duration of a timeslot may depend on the parameter set used for the OFDM symbol of the timeslot. 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 may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 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.

[0137] A slot may have a fixed number of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 The transmission structure of the slot duration and slot per subframe associated with the parameter set is shown (for ease of illustration, Figure 7 (The numerology with 240kHz subcarrier spacing is not shown in the figure). The subframe in NR can be used as a time reference independent of the numerology, while the slot can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration and start at any OFDM symbol and continue to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

[0138] Figure 8 An example configuration of time slots in the time and frequency domains of an NR carrier is shown. The time slots contain resource elements (REs) and resource blocks (RBs). REs are the smallest physical resources in NR. REs span one OFDM symbol in the time domain through one subcarrier in the frequency domain, as shown in Figure 2. Figure 8 As shown in . RB spans twelve consecutive REs in the frequency domain, as Figure 8 As shown in . The NR carrier can be limited to a width of 275 RBs or 275×12=3300 subcarriers. If this restriction is used, the NR carrier can be limited to 50MHz, 100MHz, 200MHz and 400MHz for subcarrier spacing of 15kHz, 30kHz, 60kHz and 120kHz, respectively, where the 400MHz bandwidth can be set based on the 400MHz bandwidth limit per carrier.

[0139] Figure 8A single numerology set is shown for use across the entire bandwidth of an NR carrier. In other example configurations, multiple numerology sets may be supported on the same carrier.

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

[0141] NR defines bandwidth parts (BWPs) to support UEs that cannot 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. The UE can be configured (e.g., via the 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.

[0142] For unpaired spectrum, a downlink BWP from the set of configured downlink BWPs may be linked with an uplink BWP from the 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, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0143] For a downlink BWP in the set of configured downlink BWPs on a primary cell (PCell), the base station can configure the 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 search for control information. A search space can be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, the base station can configure a common search space for a UE on a PCell or a primary supplementary cell (PSCell) in an active downlink BWP.

[0144] For an uplink BWP in the set of configured uplink BWPs, the BS may configure one or more resource sets for the UE for one or more PUCCH transmissions. The UE may receive downlink transmissions (e.g., PDCCH or PDSCH) in the downlink BWP based on the configured parameter set for the downlink BWP (e.g., subcarrier spacing and cyclic prefix duration). The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP based on the configured parameter set (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

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

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

[0147] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in the following circumstances: (a) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., incrementing the BWP inactivity timer value from zero to, or decrementing the BWP inactivity timer value from zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

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

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

[0150] 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 at a switching point. Figure 9 In the example shown, the BWPs include: BWP 902, which has a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904, which has a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906, which has a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between BWPs at a switching point. Figure 9 In the example shown in FIG. 1 , the UE may switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 may occur for any suitable reason, such as in response to expiration of a BWP inactivity timer (indicating a switch to a default BWP) and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE may switch from active BWP 904 to BWP 906 at switch point 910 in response to receiving a DCI indicating that BWP 906 is the active BWP. The UE may switch from active BWP 906 to BWP 904 at switch point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is the active BWP. The UE may switch from active BWP 904 to BWP 902 at switch point 914 in response to receiving a DCI indicating that BWP 902 is the active BWP.

[0151] If the UE is configured for a secondary cell with a default downlink BWP and timer values ​​from the set of configured downlink BWPs, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell. For example, the UE may use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values ​​for the primary cell.

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

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

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

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

[0156] The configured SCell 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. Figure 4B The configured SCells may be activated and deactivated using a MAC CE. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0157] The downlink control information of a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, which is called self-scheduling. The DCI of a cell can be transmitted on another cell, which is called cross-carrier scheduling. The uplink control information for the aggregated cell (for example, HARQ confirmation 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 may become overloaded. The cell can be divided into multiple PUCCH groups.

[0158] Figure 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 can each contain one or more downlink CCs. Figure 10BIn the example shown in FIG1 , PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050, in this example, includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may 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) may 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) may be transmitted in the uplink of PSCell 1061. In this example, if Figure 10B If the aggregated cell depicted in FIG is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell transmits UCI associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

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

[0160] In carrier aggregation, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, the HARQ entity can operate on the serving cell. Transport blocks can be generated based on the assignment / grant of each serving cell. Transport blocks and potential HARQ retransmissions of the transport blocks can be mapped to the serving cell.

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

[0162] Figure 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks may contain one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, e.g., Figure 11A ). The burst may be transmitted periodically (e.g., every 2 frames or 20 ms). The burst may be limited to half a frame (e.g., the first half frame having a duration of 5 ms). It will be understood that Figure 11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst position within a frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the parameter set or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factors. In an example, the UE may assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored unless the radio network configures the UE to assume a different subcarrier spacing.

[0163] SS / PBCH blocks may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, e.g., Figure 11A ) and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and may span 240 subcarriers.

[0164] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). In order to find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If no PSS is found after a certain duration (for example, 20ms), the UE may search for the PSS at different frequency positions within the carrier, as indicated by the synchronization raster. If the PSS is found at a certain position in the time and frequency domains, the UE may determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In an example, the primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

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

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

[0167] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH blocks transmitted with different SS / PBCH block indices.

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

[0169] In an example, a base station may transmit multiple SS / PBCH blocks within a frequency range of a carrier. In an example, a first PCI of a first SS / PBCH block in the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block in the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations may be different or the same.

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

[0171] The base station can semi-statically configure the UE with one or more CSI-RS resource sets. CSI-RS resources can be associated with positions and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can indicate to the UE that CSI-RS resources in a CSI-RS resource set are activated and / or deactivated.

[0172] The base station can configure the UE to report CSI measurement values. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with the timing and / or period of multiple CSI reports. For aperiodic CSI reporting, the base station can request a CSI report. For example, the base station can command the UE to measure the configured CSI-RS resources and provide a CSI report related to the measurement value. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station can configure the UE with a CSI-RS resource set and CSI reporting using RRC signaling.

[0173] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and control resource set (CORESET) when the downlink CSI-RS and 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. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH blocks.

[0174] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, the downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The 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 frontload DMRS pattern. The frontload DMRS can be mapped on the one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where the DMRS position, DMRS pattern and / or scrambling sequence can be the same or different. The base station may use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE may use the one or more downlink DMRSs to perform consistent demodulation / channel estimation on the PDSCH.

[0175] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0176] The PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. Higher layers may configure up to three DMRS for the PDSCH.

[0177] The downlink PT-RS may be transmitted by the base station and used by the UE for phase noise compensation. The presence or absence of the downlink PT-RS may depend on the RRC configuration. The presence and / or type of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters that may be indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters including at least the MCS. NR networks may support multiple PT-RS densities defined in the time and / or frequency domain. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use the same precoding for both DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be restricted to the scheduled time / frequency duration of the UE. The downlink PT-RS may be transmitted on a symbol to facilitate phase tracking at the receiver.

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

[0179] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on a layer in the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0180] Depending on the RRC configuration of the UE, the uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or type of the uplink PT-RS can be configured based on the UE specific configuration through a combination of RRC signaling and / or one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least the MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be restricted to the scheduled time / frequency duration of the UE.

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

[0182] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or aperiodic SRS resources; the number of OFDM symbols in the SRS resources; the starting OFDM symbol of the SRS resources; the SRS bandwidth; the frequency hopping bandwidth; the cyclic shift; and / or the SRS sequence ID.

[0183] Antenna ports are defined such that the channel over which one symbol on the antenna port is communicated can be inferred from the channel over which another symbol on the same antenna port is communicated. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. If one or more large-scale properties of the channel over which the first symbol on the first antenna port is communicated can be inferred from the channel over which the second symbol on the second antenna port is communicated, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCLed). The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0184] 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 beamforming reference signals. The UE can perform downlink beam measurements and generate beam measurement reports based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)). After establishing an RRC connection with a base station, the UE can perform a downlink beam measurement procedure.

[0185] Figure 11B An example of channel state information reference signal (CSI-RS) mapping in time and frequency domain is shown. Figure 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may 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 may be configured for the CSI-RS resource configuration via 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) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, 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.

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

[0187] CSI-RS, such as Figure 11BThose shown in (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurement values. For example, the UE can measure the reference signal received power (RSRP) of the configured CSI-RS resource. The base station can configure the UE with a reporting configuration, and the UE can report the RSRP measurement value to the network (e.g., via one or more base stations) based on the reporting configuration. In an example, the base station can determine one or more transmission configuration indication (TCI) states including multiple reference signals based on the reported measurement results. In an example, the base station can indicate one or more TCI states to the 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, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter of the transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-matching capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured for the UE by the base station. The base station may select and instruct the UE on an uplink beam based on measurements of one or more SRS resources transmitted by the UE.

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

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

[0190] Figure 12B Three examples of uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements on a UE's Tx beam, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, Tx beam sweeping from a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

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

[0192] The UE may measure the quality of a beam-pair link using one or more reference signals (RS), the one or more reference signals including one or more SS / PBCH blocks, one or more CSI-RS resources and / or one or more demodulation reference signals (DMRS). The quality of a beam-pair link may be based on one or more of the following: 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 an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). When the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from the transmission to the UE via the RS resource are similar or identical to the channel characteristics from the transmission to the UE via the channel, the RS resource and the one or more DMRSs of the channel may be QCLed.

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

[0194] Figure 13A A four-step contention-based random access procedure is shown. Before initiating the procedure, the base station may transmit a configuration message 1310 to the 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 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0195] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0196] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that may be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities, and (b) one or more reference signals. The one or more RACH parameters may indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

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

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

[0199] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., Group A and Group B). The base station may use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE may determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) to select a preamble and to determine a PRACH opportunity. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

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

[0201] Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 was received by the base station. Msg 2 1312 may include a time alignment command that the UE may use to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., a RA-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTI may be as follows:

[0202] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0≤t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for the NUL carrier and 1 for the SUL carrier).

[0203] The UE may 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 may be used, for example, Figure 13A 1314 ). Contention resolution in the contention-based random access procedure presented in . In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide RARs corresponding to the UEs. If the multiple UEs interpret the RARs as corresponding to themselves, a collision may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 and / or any other suitable identifier if a C-RNTI is assigned).

[0204] Msg 4 1314 may 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 use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in the RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was successfully completed.

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

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

[0207] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Figure 13B For example, the base station may indicate or assign to the UE a preamble to be used for Msg 1 1321. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

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

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

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

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

[0212] The UE may determine the radio resources and / or uplink transmission power of 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 may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or transport block 1342. The time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel used for monitoring and / or receiving Msg B 1332.

[0213] Transport block 1342 may 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 may transmit Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or TC-RNTI). The UE may 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 UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0214] The UE and the base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2). The control signaling may 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.

[0215] Downlink control signaling may include: downlink scheduling assignments; uplink scheduling grants indicating uplink radio resources and / or transport formats; time slot format information; preemption indications; power control commands; and / or any other suitable signaling. The UE may receive downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group-common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0216] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier for the UE (or an identifier for the group of UEs). Scrambling the CRC parity bits with the identifier may include a Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of a Radio Network Temporary Identifier (RNTI).

[0217] DCI can be used for different purposes. The purpose can be indicated by the 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 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 the triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Figure 13AThe displayed Msg 3 1313 is Msg 3). Other RNTIs configured by the base station to the UE may include: the configured scheduling RNTI (CS-RNTI), transmit power control PUCCH RNTI (TPC-PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit 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), etc.

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

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

[0220] Figure 14A An example of a CORESET configuration for a bandwidth portion is shown. The base station may transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources in which the UE attempts to decode the DCI using one or more search spaces. The base station may configure the CORESET in the time-frequency domain. Figure 14A In the example shown in FIG1 , first CORESET 1401 and second CORESET 1402 appear at the first symbol in a time slot. First CORESET 1401 overlaps with second CORESET 1402 in the frequency domain. Third CORESET 1403 appears at the third symbol in a time slot. Fourth CORESET 1404 appears at the seventh symbol in a time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

[0221] Figure 14B An example of CCE to REG mapping for DCI transmission on a CORESET and PDCCH processing is shown. The CCE to REG mapping can be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a 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 the CCE to REG mapping through RRC configuration. A CORESET can be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter can indicate the QCL information of the demodulation reference signal (DMRS) used for PDCCH reception in the CORESET.

[0222] The base station may transmit an RRC message including configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate the association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: the number of PDCCH candidates to be monitored per aggregation level; the PDCCH monitoring periodicity and the PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the identity of the UE (e.g., C-RNTI).

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

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

[0225] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for the UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may contain two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE may use PUCCH format 0 to transmit UCI in the PUCCH resources. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may contain two or fewer bits. If the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two, the UE may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. If the transmission is more than one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can contain more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not contain orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can contain more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources contain orthogonal cover codes, the UE may use PUCCH format 4.

[0226] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. The multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. The PUCCH resource set may be configured with: a PUCCH resource set index; multiple PUCCH resources having PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid); and / or a certain number (e.g., a maximum number) of UCI information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, the UE may select one PUCCH resource set (e.g., HARQ-ACK, SR, and / or CSI) from the multiple PUCCH resource sets based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE may select the 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 the first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of 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 may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

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

[0228] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as Figure 1A The mobile communication network 100 is shown. Figure 1B The mobile communication network 150 shown or any other communication network. Figure 15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , 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 Figure 15 The same or similar configurations as those shown.

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

[0230] In the downlink, data to be transmitted from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may 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 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A Layer 3 may include the following: Figure 2B RRC layer.

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

[0232] At base station 1504, receive processing system 1512 may receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 may receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and the like.

[0233] like Figure 15 As shown in FIG, wireless device 1502 and base station 1504 may include multiple antennas. The multiple antennas may be used to implement 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.

[0234] Processing system 1508 and processing system 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 may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Figure 15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive 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 may be executed to perform one or more of their respective functions.

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

[0236] 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 the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to the GPS chipset 1517 and the 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.

[0237] Figure 16AAn example structure for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. The one or more functions may include at least one of the following: scrambling; modulating the scrambled bits to generate complex-valued symbols; mapping the complex-valued modulated symbols to 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 complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports, etc. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, the SC-FDMA signal can be generated by Figure 16A Generates a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0238] Figure 16B An example structure is shown for modulating and upconverting a baseband signal to a carrier frequency. The baseband signal can be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0239] Figure 16C An example structure for downlink transmission is presented. A baseband signal representing a physical downlink channel can perform one or more functions. These one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transmission layers; precoding the complex-valued modulation symbols on layers for transmission on antenna ports; mapping the complex-valued modulation symbols for the antenna ports to resource elements; generating a complex-valued time-domain OFDM signal for the antenna ports, and the like. These functions are presented as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0240] Figure 16D Another example structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

[0241] A wireless device may receive one or more messages (e.g., RRC messages) from a base station including configuration parameters for multiple cells (e.g., a primary cell, a secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device at the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, or RRC layer. For example, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, the configuration parameters may include parameters indicating values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

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

[0243] The base station may transmit one or more MAC PDUs to the wireless device. In an example, the MAC PDU may be a bit string that is length-byte aligned (e.g., aligned to a multiple of eight bits). In an example, the bit string may be represented by a table, where the most significant bit is the leftmost bit of the first row of the table and the least significant bit is the rightmost bit of the last row of the table. More generally, the bit string may be read from left to right and then in the order in which the line is read. In an example, the bit order of the parameter fields within the MAC PDU is represented with the first and most significant bit being the leftmost bit and the last and least significant bit being the rightmost bit.

[0244] In an example, a MAC SDU may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). In an example, the MAC SDU may be included in the MAC PDU starting from the first bit. A MAC CE may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). A MAC subheader may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). In an example, the MAC subheader may be placed directly in front of the corresponding MAC SDU, MAC CE, or padding. The MAC entity may ignore the value of reserved bits in the DL MAC PDU.

[0245] In an example, a MAC PDU may include one or more MAC subPDUs. A MAC subPDU in the one or more MAC subPDUs may include: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. A MAC SDU may have a variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0246] In an example, when the MAC subheader corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC subheader may include: an R field having a one-bit length; an F field having a one-bit length; an LCID field having a multi-bit length; an L field having a multi-bit length, or a combination thereof.

[0247] Figure 17A An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Figure 17A In the example MAC subheader of , the LCID field may be six bits in length and the L field may be eight bits in length. Figure 17B An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Figure 17B In the example MAC subheader shown in FIG, the LCID field may be six bits long, and the L field may be sixteen bits long. When the MAC subheader corresponds to a fixed-size MAC CE or padding, the MAC subheader may include an R field having a two-bit length and an LCID field having a multi-bit length. Figure 17C An example of a MAC subheader having an R field and an LCID field is shown. Figure 17C In the example MAC subheader shown in , the LCID field may be six bits in length and the R field may be two bits in length.

[0248] Figure 18AAn example of a DL MAC PDU is shown. Multiple MAC CEs (such as MAC CEs 1 and 2) can be placed together. A MAC subPDU including a MAC CE can be placed before a MAC subPDU including a MAC SDU or a MAC subPDU including padding. Figure 18B An example of a UL MAC PDU is shown. Multiple MAC CEs (such as MAC CEs 1 and 2) can be placed together. In an embodiment, a MAC subPDU including a MAC CE can be placed after all MAC subPDUs including a MAC SDU. In addition, a MAC subPDU can be placed before a MAC subPDU including padding.

[0249] In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device. Figure 19 An example of multiple LCIDs that may be associated with one or more MAC CEs is shown. The one or more MAC CEs include at least one of the following: SP ZP CSI-RS resource set activation / deactivation MAC CE; PUCCH spatial relation activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI reporting on PUCCH activation / deactivation MAC CE; TCI status indication for UE-specific PDCCH MAC CE; TCI status indication for UE-specific PDSCH MAC CE; Aperiodic CSI triggering status subselection MAC CE; SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; Radio device contention resolution identity MAC CE; Timing Advance Command MAC CE; DRX Command MAC CE; Long DRX Command MAC CE; SCell activation / deactivation MAC CE (1 octet); SCell activation / deactivation MAC CE (4 octets); and / or duplicate activation / deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID of 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0250] In an example, a MAC entity of a wireless device may transmit one or more MAC CEs to a MAC entity of a base station. Figure 20An example of one or more MAC CEs is shown. The one or more MAC CEs may include at least one of the following: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grant confirmation MAC CE; a single-entry PHR MAC CE; a multi-entry PHR MAC CE; a short truncated BSR; and / or a long truncated BSR. In the example, the MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short truncated command MAC CE.

[0251] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may receive or transmit simultaneously on one or more CCs using CA techniques depending on the capabilities of the wireless device. In an embodiment, the wireless device may support CA for contiguous CCs and / or for non-contiguous CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, the wireless device may have one RRC connection with the network. During RRC connection establishment / reestablishment / handover, the cell that provides NAS mobility information may be a serving cell. During the RRC connection reestablishment / handover procedure, the cell that provides security input may be a serving cell. In an example, the serving cell may represent a PCell. In an example, the base station may transmit one or more messages including configuration parameters of multiple one or more SCells to the wireless device depending on the capabilities of the wireless device.

[0252] When configured with Carrier Access Control (CA), the base station and / or wireless device can employ SCell activation / deactivation mechanisms to improve battery and power consumption of the wireless device. When a wireless device is configured with one or more SCells, the base station can activate or deactivate at least one of the one or more SCells. Following SCell configuration, the SCell can be deactivated immediately unless the SCell state associated with the SCell is set to "activated" or "dormant."

[0253] The wireless device may activate / deactivate the SCell in response to receiving the SCell activation / deactivation MAC CE. In an example, the base station may transmit one or more messages including an SCell timer (e.g., sCellDeactivationTimer) to the wireless device. In an example, the wireless device may deactivate the SCell in response to expiration of the SCell timer.

[0254] When the wireless device receives an SCell activation / deactivation MAC CE to activate the SCell, the wireless device may activate the SCell. In response to activating the SCell, the wireless device may perform operations including: SRS transmission on the SCell; CQI / PMI / RI / CRI reporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and / or PUCCH transmission on the SCell. In response to activating the SCell, the wireless device may start or restart a first SCell timer associated with the SCell (e.g., sCellDeactivationTimer). When an SCell activation / deactivation MAC CE to activate the SCell has been received, the wireless device may start or restart the first SCell timer in a time slot. In an example, in response to activating the SCell, the wireless device may (re)initialize one or more suspended configured uplink grants of a configured grant type 1 associated with the SCell according to a stored configuration. In an example, in response to activating the SCell, the wireless device may trigger a PHR.

[0255] When the wireless device receives an SCell activation / deactivation MAC CE to deactivate the activated SCell, the wireless device may deactivate the activated SCell. In an example, when the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may deactivate the activated SCell. In response to deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink grants of the configured uplink grant type 2 associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device may: suspend one or more configured uplink grants of the configured uplink grant type 1 associated with the activated SCell; and / or clear the HARQ buffer associated with the activated SCell.

[0256] When an SCell is deactivated, the wireless device may not perform operations including: transmitting an SRS on the SCell; reporting CQI / PMI / RI / CRI for the SCell; transmitting on the UL-SCH on the SCell; transmitting on the RACH on the SCell; monitoring at least one first PDCCH on the SCell; monitoring at least one second PDCCH for the SCell; and / or transmitting a PUCCH on the SCell. When at least one first PDCCH on the activated SCell indicates an uplink grant or downlink assignment, the wireless device may restart a first SCell timer associated with the activated SCell (e.g., sCellDeactivationTimer). In an example, when at least one second PDCCH on the serving cell (e.g., a PCell or SCell configured with PUCCH, i.e., a PUCCH SCell) scheduling the activated SCell indicates an uplink grant or downlink assignment for the activated SCell, the wireless device may restart the first SCell timer associated with the activated SCell (e.g., sCellDeactivationTimer). In an example, when the SCell is deactivated, if there is an ongoing random access procedure on the SCell, the wireless device may abort the ongoing random access procedure on the SCell.

[0257] Figure 21A An example of a one-octet SCell activation / deactivation MAC CE is shown. Figure 19 The first MAC PDU subheader (shown as '111010' in FIG) may identify a one-octet SCell activation / deactivation MAC CE. The one-octet SCell activation / deactivation MAC CE may have a fixed size. The one-octet SCell activation / deactivation MAC CE may include a single octet. The single octet may include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one).

[0258] Figure 21B An example of a four-octet SCell activation / deactivation MAC CE is shown. Figure 19 The second MAC PDU subheader (shown as '111001' in FIG) may identify a four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE may have a fixed size. The four-octet SCell activation / deactivation MAC CE may include four octets. The four octets may include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0259] exist Figure 21A and / or Figure 21B In the example, if the SCell with SCell index i has been configured, then C i The field may indicate the activation / deactivation status of the SCell with SCell index i. In the example, when C i When the field is set to one, the SCell with SCell index i can be activated. In the example, when C i When the field is set to zero, the SCell with SCell index i may be deactivated. In an example, if there is no SCell configured with SCell index i, the wireless device may ignore C i field. Figure 21A and Figure 21B In the , R field can indicate a reserved bit. The R field can be set to zero.

[0260] The base station may configure the wireless device with an uplink (UL) bandwidth part (BWP) and a downlink (DL) BWP to enable bandwidth adaptation (BA) on the PCell. If carrier aggregation is configured, the base station may further configure the wireless device with at least a DL BWP (i.e., there may be no UL BWP in the UL) to enable BA on the SCell. For the PCell, the initial active BWP may be the first BWP used for initial access. For the SCell, the first active BWP may be the second BWP configured for the wireless device to operate on the SCell when the SCell is activated. In paired spectrum (e.g., FDD), the base station and / or wireless device may independently switch the DL BWP and UL BWP. In unpaired spectrum (e.g., TDD), the base station and / or wireless device may simultaneously switch the DL BWP and UL BWP.

[0261] In an example, a base station and / or wireless device can switch between configured BWPs via DCI or a BWP inactivity timer. When a BWP inactivity timer is configured for a serving cell, the base station and / or wireless device can switch the active BWP to a default BWP in response to the expiration of the BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network. In an example, for an FDD system, when BA is configured, one UL BWP and one DL BWP per uplink carrier can be active at any time in the active serving cell. In an example, for a TDD system, one DL / UL BWP pair can be active at any time in the active serving cell. Operating on this one UL BWP and this one DL BWP (or this one DL / UL pair) can improve wireless device battery consumption. BWPs other than the one active UL BWP and the one active DL BWP on which the wireless device can operate can be deactivated. On a deactivated BWP, the wireless device may: not monitor the PDCCH; and / or not transmit on the PUCCH, PRACH, and UL-SCH.

[0262] In an example, a serving cell may be configured with up to a first number (e.g., four) of BWPs. In an example, for an activated serving cell, there may be one active BWP at any point in time. In an example, BWP switching for a serving cell may be used to simultaneously activate an inactive BWP and deactivate an active BWP. In an example, BWP switching may be controlled by a PDCCH indicating a downlink assignment or uplink grant. In an example, BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). In an example, BWP switching may be controlled by a MAC entity in response to initiating a random access procedure. When adding a SpCell or activating an SCell, a BWP may initially be active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP for a serving cell may be indicated by RRC and / or PDCCH. In an example, for unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common for both UL and DL.

[0263] Figure 22An example of performing a BWP switching on a cell (e.g., a PCell or SCell) is shown. In this example, a wireless device may receive at least one RRC message from a base station, the at least one RRC message including parameters of the cell and one or more BWPs associated with the cell. The RRC message may include: an RRC connection reconfiguration message (e.g., RRCReconfiguration); an RRC connection reestablishment message (e.g., RRCReestablishment); and / or an RRC connection setup message (e.g., RRCSetup). Of the one or more BWPs, at least one BWP may be configured as a first active BWP (e.g., BWP 1) and one BWP may be configured as a default BWP (e.g., BWP 0). The wireless device may receive a command (e.g., an RRC message, a MAC CE, or a DCI) to activate the cell in the nth time slot. If the cell is a PCell, the wireless device may not receive a command to activate the cell. For example, upon receiving an RRC message including configuration parameters for the PCell, the wireless device may activate the PCell. In response to the cell activation, the wireless device may begin monitoring the PDCCH on BWP 1.

[0264] In an example, in response to receiving a DCI indicating a DL assignment on BWP 1, the wireless device may start (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) at the mth time slot. When the BWP inactivity timer expires, the wireless device may switch back to the default BWP (e.g., BWP 0) as the active BWP at the sth time slot. When the sCellDeactivationTimer expires (e.g., if the cell is an SCell), the wireless device may deactivate the cell and / or stop the BWP inactivity timer. In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer to the PCell.

[0265] In an example, the MAC entity may apply normal operations to the active BWP of an activated serving cell configured with a BWP, including: transmitting on UL-SCH; transmitting on RACH; monitoring PDCCH; transmitting PUCCH; receiving DL-SCH; and / or (re)initializing any suspended configured uplink grants of configured grant type 1 according to the stored configuration (if any).

[0266] In an example, on an inactive BWP for each activated serving cell configured with a BWP, the MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor PDCCH; not transmit PUCCH; not transmit SRS and not receive DL-SCH; clear any configured downlink assignments and configured uplink grants of configured grant type 2; and / or suspend any configured uplink grants of configured type 1.

[0267] In an example, if the MAC entity receives a PDCCH for a BWP switch of a serving cell while a random access procedure associated with the serving cell is not in progress, the wireless device may perform a BWP switch to the BWP indicated by the PDCCH. In an example, if the bandwidth part indicator field is configured in DCI format 1_1, the bandwidth part indicator field value may indicate an active DL BWP for DL ​​reception from the configured DL BWP set. In an example, if the bandwidth part indicator field is configured in DCI format 0_1, the bandwidth part indicator field value may indicate an active UL BWP for UL transmission from the configured UL BWP set.

[0268] In an example, for a primary cell, a default DL BWP among the configured DL BWPs may be provided to the wireless device via the higher layer parameter Default-DL-BWP. If no default DL BWP is provided to the wireless device via the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a timer value for the primary cell may be provided to the wireless device via the higher layer parameter bwp-InactivityTimer. If configured, the wireless device may increment the timer (if running) at intervals of 1 millisecond for frequency range 1 or 0.5 milliseconds for frequency range 2 if, during the interval, the wireless device fails to detect DCI format 1_1 for paired spectrum operation, or fails to detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation.

[0269] In an example, if the wireless device is configured for a secondary cell with a higher layer parameter Default-DL-BWP indicating a default DL BWP among the configured DL BWPs, and the wireless device is configured with a higher layer parameter bwp-InactivityTimer indicating a timer value, then the wireless device procedure on the secondary cell can be the same as the wireless device procedure on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0270] In an example, if the wireless device is configured with a first active DL BWP on a secondary cell or carrier via a higher layer parameter Active-BWP-DL-SCell and a first active UL BWP via a higher layer parameter Active-BWP-UL-SCell, the wireless device may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the corresponding first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0271] In an example, a set of PDCCH candidates to be monitored by a wireless device may be defined in terms of a PDCCH search space set.The search space set includes a CSS set or a USS set. The wireless device monitors PDCCH candidates in one or more of the following search space sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the SI-RNTI on the primary cell of the MCG; a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the SI-RNTI on the primary cell of the MCG; a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the RA-RNTI, MsgB-RNTI or TC-RNTI on the primary cell; a Type2-PDCCH configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the P-RNTI on the primary cell of the MCG CSS set; Type3-PDCCH CSS set configured by SearchSpace with searchSpaceType=common in PDCCH-Config for DCI format with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI or PS-RNTI and only for primary cell, C-RNTI, MCS-C-RNTI or CS-RNTI; and USS set configured by SearchSpace with searchSpaceType=ue-Specific in PDCCH-Config for DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI or SL-L-CS-RNTI.

[0272] In an example, the wireless device configures the PDCCH based on one or more PDCCH configuration parameters (e.g., based on Figure 27Example embodiment) to determine the PDCCH monitoring opportunity on the active DL BWP, the one or more PDCCH configuration parameters including: PDCCH monitoring periodicity, PDCCH monitoring offset and PDCCH monitoring mode within the time slot. For search space set (SS s), if The wireless device determines that the number is n f The frame number is There is a PDCCH monitoring opportunity in the time slot. is the number of time slots in the time frame of the configuration parameter set μ. s is a PDCCH configuration parameter (e.g., based on Figure 27 k s is a PDCCH configuration parameter (e.g., based on Figure 27 The wireless device monitors the PDCCH periodicity indicated in the example embodiment of FIG. Start monitoring PDCCH candidates for the search space set for T s consecutive time slots, and in the next k s -T s No PDCCH candidates are monitored for the search space set s during consecutive time slots.In an example, the USSs at CCE aggregation level L∈{1,2,4,8,16} are defined by the set of PDCCH candidates for CCE aggregation level L.

[0273] In an example, the wireless device decides for a search space set s associated with CORESETp that for a carrier indicator field value n CI For the active DL BWP of the corresponding serving cell, in the time slot In the search space set, the PDCCH candidates The corresponding CCE index of aggregation level L is For any CSS, For USS, Y p,-1 =n RNTI ≠0, for p mod 3=0, A p =39827, for pmod 3=1, A p =39839, for p mod 3 = 2, A p =39839, and D = 65537; i = 0, ..., L-1; in CORESETp, N CCE,p is the number of CCEs, numbered from 0 to N CCE,p -1; if the wireless device is configured with the carrier indicator field CrossCarrierSchedulingConfig for the serving cell on which to monitor the PDCCH, then nCI Is the Carrier Indicator field value; otherwise, contains the value of n for any CSS. CI =0; in The wireless device is configured to CI The number of PDCCH candidates monitored for the aggregation level L of the search space set s for the corresponding serving cell; for any CSS, For USS, is n over all configurations of CCE aggregation level L for search space set s Ck value The maximum value of n RNTI The RNTI value is C-RNTI.

[0274] In an example, the wireless device may monitor a set of PDCCH candidates based on configuration parameters of a search space set including a plurality of search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Figure 26 The CORESET may be configured according to an example embodiment of the present invention. Monitoring may include decoding one or more PDCCH candidates in a set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. Possible DCI formats may be based on Figure 23 Example embodiments of the present invention.

[0275] Figure 23 An example of a DCI format is shown, which can be used by a base station to transmit control information to a wireless device, or by a wireless device for PDCCH monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In the example, DCI format 0_0 can be used to schedule PUSCH in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCHs in a cell, or to indicate CG-DFI (configured grant downlink feedback information) of a configured grant PUSCH, etc. The DCI formats that a wireless device can monitor in an SS can be configured.

[0276] Figure 24AAn example of configuration parameters of a master information block (MIB) for a cell (e.g., PCell) is shown. In the example, based on receiving a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS), a wireless device can receive the MIB via the PBCH. The configuration parameters of the MIB may include six bits of the system frame number (SFN) (systemFrameNumber), a subcarrier spacing indicator (subCarrierSpacingCommon), a frequency domain offset in terms of the number of subcarriers between the SSB and the entire resource block grid (ssb-SubcarrierOffset), an indication indicating whether the cell is barred (cellBarred), a DMRS position indication indicating the position of the DMRS (dmrs-TypeA-Position), parameters of the PDCCH including the CORESET and SS of the common CORESET (pdcch-ConfigSIB1), a common search space and necessary PDCCH parameters, etc.

[0277] In an example, pdcch-ConfigSIB1 may include a first parameter (e.g., controlResourceSetZero) indicating a common ControlResourceSet (CORESET) with ID #0 (e.g., CORESET#0) of the initial BWP of the cell. controlResourceSetZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify a configuration of CORESET#0.

[0278] Figure 24B An example of the configuration of CORESET#0 is shown. Figure 24B As shown, based on the value of the integer of controlResourceSetZero, the wireless device can determine the SSB and CORESET#0 multiplexing pattern, the number of RBs of CORESET#0, the number of symbols of CORESET#0, and the RB offset of CORESET#0.

[0279] In an example, pdcch-ConfigSIB1 may include a second parameter (e.g., searchSpaceZero) indicating a common search space with ID #0 (e.g., SS #0) of the initial BWP of the cell. searchSpaceZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify the configuration of SS #0.

[0280] Figure 24C An example of the configuration of SS#0 is shown. Figure 24CAs shown, based on the integer value of searchSpaceZero, the wireless device can determine one or more parameters (e.g., O, M) for time slot determination for PDCCH monitoring, the first symbol index for PDCCH monitoring, and / or the number of search spaces per time slot.

[0281] In an example, based on receiving the MIB, the wireless device may monitor the PDCCH via SS#0 of CORESET#0 for receiving DCI scheduling system information block 1 (SIB1). The SIB1 message may be based on Figure 25 The wireless device may receive a DCI having a CRC scrambled with a system information radio network temporary identifier (SI-RNTI) dedicated for receiving SIB1.

[0282] Figure 25 An example of RRC configuration parameters of a system information block (SIB) is shown. The SIB (e.g., SIB1) can be transmitted to all wireless devices in a broadcast manner. The SIB can contain information related to evaluating whether to allow a wireless device to access a cell, paging configuration, and / or configuration information for scheduling other system information. The SIB can contain radio resource configuration information common to all wireless devices and prohibition information applied to unified access control. In the example, the base station can transmit one or more SIB information to a wireless device (or multiple wireless devices). Figure 25 As shown, the parameters of the one or more SIB information may include: one or more parameters for cell selection related to the serving cell (e.g., cellSelectionInfo), one or more configuration parameters of the serving cell (e.g., represented by the ServingCellConfigCommonSIB IE), and one or more other parameters. The ServingCellConfigCommonSIB IE may include at least one of the following: common downlink parameters of the serving cell (e.g., represented by the DownlinkConfigCommonSIB IE), common uplink parameters of the serving cell (e.g., represented by the UplinkConfigCommonSIB IE), and other parameters.

[0283] In an example, the DownlinkConfigCommonSIB IE may include parameters of the initial downlink BWP of the serving cell (eg, SpCell) (initialDownlinkBWP IE). The parameters of the initial downlink BWP may be included in the BWP-DownlinkCommon IE (eg, Figure 26(As shown in Figure 2-1). The BWP-DownlinkCommon IE can be used to configure the common parameters of the downlink BWP of the serving cell. The base station can configure locationAndBandwidth so that the initial downlink BWP includes the entire CORESET#0 of the serving cell in the frequency domain. The wireless device can apply locationAndBandwidth upon receiving this field (e.g., determine the frequency location of the signal described by locationAndBandwidth), but it remains in CORESET#0 until after receiving RRCSetup / RRCResume / RRCReestablishment.

[0284] In an example, the DownlinkConfigCommonSIB IE may include parameters for paging channel configuration. These parameters may include a paging cycle value (T, represented by the defaultPagingCycle IE), a parameter (nAndPagingFrameOffset IE) indicating the total number (N) of paging frames (PF) and paging frame offsets (PF_offset) in the paging DRX cycle, the number (N) of total paging occasions (PO) for each PF, and a first PDCCH monitoring occasion indication parameter (firstPDCCH-MonitoringOccasionofPOIE) indicating the first PDCCH monitoring occasion for paging of each PO of the PF. Based on the parameters configured by the PCCH, the wireless device may monitor the PDCCH to receive a paging message.

[0285] In an example, the parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in SIB1 for paging in the initial DL BWP.For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in the corresponding BWP configuration.

[0286] Figure 26 An example of RRC configuration parameters (e.g., BWP-DownlinkCommon IE) in the downlink BWP of the serving cell is shown. The base station may transmit one or more configuration parameters of the downlink BWP (e.g., initial downlink BWP) of the serving cell to the wireless device (or multiple wireless devices). Figure 26As shown, the one or more configuration parameters for the downlink BWP may include: one or more common BWP parameters for the downlink BWP, one or more cell-specific parameters for the PDCCH of the downlink BWP (e.g., represented by the pdcch-ConfigCommon IE), one or more cell-specific parameters for the PDSCH of the BWP (e.g., represented by the pdsch-ConfigCommon IE), and one or more other parameters. The pdcch-ConfigCommon field may include parameters for COESET#0 (e.g., controlResourceSetZero), which may be used in any common or UE-specific search space. The value of controlResourceSetZero may be interpreted like the corresponding bit in the MIB pdcch-ConfigSIB1. The pdcch-ConfigCommon IE may include parameters for an additional common control resource set (e.g., represented by commonControlResourceSet), which may be configured and used in any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is included in the bandwidth of CORESET#0. The pdcch-ConfigCommon IE may include parameters for the list of additional common search spaces (e.g., represented by commonSearchSpaceList). The search space parameters may be based on Figure 27 The pdcch-ConfigCommon IE may indicate, from the list of search spaces, a search space for paging (e.g., pagingSearchSpace), a search space for random access procedure (e.g., ra-SearchSpace), a search space for SIB1 message (e.g., searchSpaceSIB1), common search space #0 (e.g., searchSpaceZero), and one or more other search spaces.

[0287] like Figure 26 As shown, a control resource set (CORESET) can be associated with a CORESET index (e.g., ControlResourceSetId). Figure 14A and / or Figure 14BThe example embodiments described implement a CORESET. A CORESET index with a value of 0 may identify a common CORESET configured in the MIB and in ServingCellConfigCommon (controlResourceSetZero) and may not be used in a ControlResourceSet IE. A CORESET index with other values ​​may identify a CORESET configured by dedicated signaling or in SIB1. The controlResourceSetId is unique among the BWPs of the serving cell. A CORESET may be associated with a coresetPoolIndex indicating an index of a CORESET pool of the CORESET. A CORESET may be associated with a duration parameter (e.g., duration) indicating a continuous duration of the CORESET in a number of symbols. In the example, Figure 26 As shown, the configuration parameters of the CORESET may include at least one of the following: a frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), multiple TCI states, an indicator indicating whether TCI is present in the DCI, and the like. A frequency resource indication comprising a certain number of bits (e.g., 45 bits) may indicate frequency domain resources, each bit of the indication corresponding to a group of 6 RBs, where the grouping starts from the first RB group in the BWP of the cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit may correspond to the first RB group in the BWP, and so on. A bit set to 1 may indicate that the RB group corresponding to the bit belongs to the frequency domain resources of the CORESET. A bit corresponding to a group of RBs that is not completely contained in the BWP in which the CORESET is configured may be set to zero.

[0288] Figure 27An example of a configuration of a search space (e.g., SearchSpace IE) is shown. In the example, one or more search space configuration parameters of the search space may include at least one of the following: a search space ID (searchSpaceId), a control resource set ID (controlResourceSetId), a monitoring slot periodicity and offset parameter (monitoringSlotPeriodicityAndOffset), a search space duration value (Duration), a monitoring symbol indication (monitoringSymbolsWithinSlot), the number of candidates for the aggregation level (nrofCandidates), and / or an SS type (searchSpaceType) indicating a common SS type or a UE-specific SS type. The monitoring slot periodicity and offset parameter may indicate a time slot (e.g., in a radio frame) and a time slot offset (e.g., relative to the start of a radio frame) for PDCCH monitoring. The monitoring symbol indication may indicate on which symbol(s) of a time slot a wireless device may monitor for PDCCH on an SS. The control resource set ID may identify a control resource set on which an SS may be located.

[0289] In an example, a wireless device in an RRC_IDLE or RRC_INACTIVE state may periodically monitor a paging occasion (PO) to receive a paging message for the wireless device. Prior to monitoring the PO, the wireless device in the RRC_IDLE or RRC_INACTIVE state may wake up at a time before each PO to prepare and / or turn on all components to prepare for data reception (preheating). The interval between wake-up and PO may be long enough to accommodate all processing requirements. After preheating, the wireless device may perform timing acquisition and coarse synchronization from the SSB, frequency and time tracking, time and frequency offset compensation, and / or calibration of the local oscillator. Thereafter, the wireless device may monitor the PDCCH for paging DCI in one or more PDCCH monitoring occasions based on the configuration parameters of the PCCH configuration configured in SIB1. The configuration parameters of the PCCH configuration may be based on the above-mentioned Figure 25 The example embodiments described are implemented.

[0290] In an example, a base station may periodically transmit one or more SSBs to a wireless device or multiple wireless devices. A wireless device (in an RRC_idle state, an RRC_inactive state, or an RRC_connected state) may use one or more SSBs to synchronize time and frequency with a cell of a base station. The SSBs including the primary synchronization signal (PSS), the secondary synchronization signal (SSS), the physical broadcast channel (PBCH), and the PBCH DM-RS may be based on the above information. Figure 11A The example embodiments described are used to transmit. Figure 11A As shown, an SSB may occupy multiple (e.g., 4) OFDM symbols. The base station may transmit one or more SSBs in an SSB burst, for example, to implement beam scanning for PSS / SSS and PBCH. An SSB burst includes a group of SSBs, each SSB potentially transmitted on a different beam. The SSBs in an SSB burst may be transmitted in a time division multiplexed manner. In an example, an SSB burst may always be limited to a 5 ms window and located in the first half or the second half of a 10 ms radio frame. In this specification, an SSB burst may be equivalently referred to as a transmission window (e.g., 5 ms) in which the group of SSBs is transmitted.

[0291] In an example, the base station may indicate the transmission periodicity of the SSB via an RRC message (e.g., ssb-PeriodicityServingCell in ServingCellConfigCommonSIB of SIB1 message, such as Figure 25 The candidate values ​​of transmission periodicity can be in the range of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}. The maximum number of candidate SSBs in an SSB burst (L max ) depends on the carrier frequency / band of the cell. In the example, if f c <=3GHz, then L max =4, where f c Is the cell's carrier frequency. If 3GHz <f c <=6GHz, then L max =8. If f c >=6GHz, then L max =64, etc.

[0292] In an example, the starting OFDM symbol index of candidate SSBs (occupying 4 OFDM symbols) within an SSB burst (5 ms) can depend on the subcarrier spacing (SCS) of the cell and the carrier frequency band.

[0293] Figure 28 An example embodiment of determining the starting OFDM symbol index is shown.

[0294] As Figure 28 shown, for a cell configured with 15 kHz and a carrier frequency fc < 3 GHz (L max = 4), the starting OFDM symbol indices of the SSBs in the SSB burst are 2, 8, 16, and 22. The OFDM symbols in a half-frame are indexed, where the first symbol of the first slot is indexed as 0. For a cell configured with 15 kHz and a carrier frequency 3 GHz < fc < 6 GHz (L max = 8), the starting OFDM symbol indices of the SSBs in the SSB burst are 2, 8, 16, 22, 30, 36, 44, and 50, etc. In an example, when the base station does not transmit the SSB using beamforming, the base station can transmit only one SSB by using the first SSB starting position.

[0295] Figure 29 An example embodiment of SSB transmission of a cell by the base station is shown. In Figure 29 the example, the SCS of the cell is 15 kHz, and the cell is configured with 3 GHz < fc <= 6 GHz. Based on Figure 28 the example embodiment, the maximum number of candidate SSBs in the SSB burst is 8 (Lmax = 8). As Figure 29 shown, SSB#1 starts at symbol #2 among 70 symbols within 5 ms, SSB#2 starts at symbol #8, SSB#3 starts at symbol #16, SSB#4 starts at symbol #22, SSB#5 starts at symbol #30, SSB#6 starts at symbol #36, SSB#7 starts at symbol #44, and SSB#8 starts at symbol 50. The SSB burst is transmitted in the first half (not the second half as Figure 29 shown) of a radio frame having 10 ms.

[0296] In an example, the SSB burst (also for each SSB of the SSB burst) can be transmitted with a certain periodicity. In Figure 29In the example of FIG, the default periodicity of the SSB burst is 20 ms, for example, before the wireless device receives the SIB1 message for initial access to the cell. A base station with a 20 ms transmission periodicity of SSB (or SSB burst) may transmit the SSB burst in the first 5 ms of every 20 ms. The base station does not transmit the SSB burst in the remaining 15 ms of every 20 ms.

[0297] In an example embodiment, the base station may transmit an RRC message (e.g., SIB1) indicating cell-specific configuration parameters for SSB transmission. The cell-specific configuration parameters may include a value for the transmission periodicity of the SSB burst (ssb-PeriodicityServingCell), positions of multiple SSBs (e.g., active SSBs) among multiple candidate SSBs included in the SSB burst. The multiple candidate SSBs may be based on the above description of the Figure 28 The cell-specific configuration parameter may include a position indication of an SSB in an SSB burst (e.g., ssb-PositionsInBurst). The position indication may include a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup) indicating positions of multiple SSBs included in the SSB burst.

[0298] Figure 30 An example embodiment of an SSB position indication in an SSB burst is shown. Figure 30 In the example of , the maximum number of candidate SSBs in an SSB burst is 64. The candidate SSBs may include SSBs indexed from 0 to 63. The first bitmap (groupPresence) (configured by the SIB1 message) may include a certain number of bits (e.g., 8), each bit corresponding to a corresponding group in the SSB groups of a plurality of SSBs in the SSB burst (which may be the maximum number of candidate SSBs). Figure 30In an example, the first bit (e.g., the leftmost bit of the first bitmap) may correspond to a first SSB group including the 1st SSB (SSB index 0), the 2nd SSB (SSB index 1) ... and the 8th SSB (SSB index 7). The second bit (e.g., the second bit of the first bitmap) may correspond to a second SSB group including the 9th SSB (SSB index 8), the 10th SSB (SSB index 9) ... and the 16th SSB (SSB index 15). The last bit (e.g., the rightmost bit of the first bitmap) may correspond to the 8th SSB group including the 57th SSB (SSB index 56), the 58th SSB (SSB index 57) ... and the 64th SSB (SSB index 63), etc. In an example embodiment, an SSB may belong to at most one SSB group in the first SSB group. A bit of the first bitmap may indicate whether the base station transmits the SSB group corresponding to the bit in an SSB burst. In an example, a bit set to a first value (e.g., 1) may indicate that the corresponding SSB group is transmitted by the base station in an SSB burst. In an example, a bit set to a second value (eg, 0) may indicate that the corresponding SSB group is not transmitted by the base station in an SSB burst, and vice versa.

[0299] like Figure 30 As shown, the second bitmap (inOneGroup) (configured by the SIB1 message) may include a certain number of bits (e.g., 8), each bit corresponding to a corresponding group in the SSB groups of the plurality of SSBs in the SSB burst. Figure 30 In an example, the first bit (e.g., the leftmost bit of the second bitmap) may correspond to a first SSB group including the 1st SSB (SSB index is 0), the 2nd SSB (SSB index is 8) ... and the 8th SSB (SSB index is 56). The second bit (e.g., the second bit of the second bitmap) may correspond to a second SSB group including the 1st SSB (SSB index is 1), the 2nd SSB (SSB index is 9) ... and the 8th SSB (SSB index is 57). The last bit (e.g., the rightmost bit of the second bitmap) may correspond to the 8th SSB group including the 1st SSB (SSB index is 7), the 2nd SSB (SSB index is 15) ... and the 8th SSB (SSB index is 63), etc. In the example, an SSB may belong to at most one SSB group in the second SSB group. A bit of the second bitmap may indicate whether the base station transmits the SSB group corresponding to the bit in an SSB burst. In the example, a bit set to a first value (e.g., 1) may indicate that the corresponding SSB group is transmitted by the base station in an SSB burst. In an example, a bit set to a second value (eg, 0) may indicate that the corresponding SSB group is not transmitted by the base station in an SSB burst, and vice versa.

[0300] exist Figure 30In the example of , for the first bitmap, multiple SSBs (e.g., SSB indices are 0 to 63) can be grouped into a first SSB group, each SSB including SSBs with consecutive SSB indices. The first SSB group in the first SSB group includes SSBs with SSB indices from 0 to 7, the second SSB group includes SSB indices from 8 to 15, and so on. For the second bitmap, multiple SSBs can also be grouped into a second SSB group, each SSB including SSBs with discontinuous SSB indices. The first SSB group in the second SSB group includes SSBs with SSB indices of {0, 8, 16, ...56}, and the SSB index gap between two adjacent SSB indices is 8. The second SSB group in the second SSB group includes SSBs with SSB indices of {1, 9, 17, ...57}, and so on.

[0301] In an example embodiment, when fc≤3 GHz, the maximum number of SSBs within an SS burst is equal to four, and the wireless device may determine that the four leftmost bits of a bitmap (e.g., the first bitmap and / or the second bitmap) are valid. The wireless device may ignore the four rightmost bits of the first bitmap and / or the second bitmap.

[0302] exist Figure 30 In the example of , the first bitmap may be indicated by the base station as {1 0 1 0 0 0 0 0}, and the second bitmap may be indicated as {1 1 0 0 0 0 0 0}. Based on the grouping configuration of the first SSB group and the second SSB group, the base station may transmit SSBs with indices of {0 1 16 17} in the SSB burst.

[0303] In an example, the base station may transmit a master information block (MIB) on the PBCH to indicate configuration parameters for wireless devices that monitor the PDCCH to schedule SIB1 messages (for CORESET#0). The base station may transmit the MIB message with a transmission periodicity of 80 milliseconds (ms). The same MIB message may be repeated within 80 ms (according to the SSB periodicity). The content of the MIB message is the same within the 80 ms period. The same MIB is transmitted on all SSBs within an SS burst. In an example, the PBCH may indicate that there is no associated SIB1, in which case the wireless device may be directed to another frequency from which to search for the SSB associated with SIB1 and the frequency range in which the wireless device may assume that there is no SSB associated with SIB1. The indicated frequency range may be limited to within a continuous spectrum allocation of the same operator where the SSB was detected.

[0304] In an example, the base station may transmit a SIB1 message with a periodicity of 160 ms. The base station may transmit the same SIB1 message with a variable transmission repetition periodicity within 160 ms. The default transmission repetition periodicity of SIB1 is 20 ms. The base station may determine the actual transmission repetition periodicity based on the network implementation. In an example, for SSB and CORESET reuse mode 1, the SIB1 repetition transmission periodicity is 20 ms. For SSB and CORESET reuse modes 2 / 3, the SIB1 transmission repetition periodicity is the same as the SSB periodicity. SIB1 may include information about the availability and scheduling of other SIBs (e.g., SIB to SI message mapping, periodicity, SI window size), an indication of whether one or more SIBs are provided only on demand, and configuration parameters required for the wireless device to perform the SI request in this case.

[0305] In an example, a base station may be equipped with multiple transmission reception points (TRPs) to improve spectrum efficiency or transmission robustness. The base station may transmit DL signals / channels via multiple TRPs within a cell (e.g., Figure 31A ) and / or via multiple TRPs between cells (e.g., Figure 31B ).

[0306] In an example, a base station may be equipped with more than one TRP. A first TRP may be physically located at a different location than a second TRP. The first TRP may be connected to the second TRP via a backhaul link (e.g., a wired link or a wireless link), where the backhaul link is an ideal backhaul link with zero or negligible transmission delay, or the backhaul link is a non-ideal backhaul link. The first TRP may be implemented with antenna elements, RF chains, and / or baseband processors that are configured / managed independently of the second TRP.

[0307] Figure 31A An example of intra-cell TRP-based communication between a base station (equipped with multiple TRPs) and a wireless device (equipped with a single panel or multiple panels) is shown. Utilizing transmission and reception of multiple TRPs can improve system throughput and / or transmission robustness for wireless communications at high frequencies (e.g., above 6 GHz). In the example, multiple TRPs are associated with the same physical cell identifier (PCI). Multiple TRPs on which the PDCCH / PDSCH / PUCCH / PUSCH resources of a cell are shared can be referred to as intra-cell TRPs (or intra-PCI TRPs).

[0308] In an example, a TRP among a plurality of TRPs of a base station may be identified by at least one of the following: a TRP identifier (ID), a virtual cell index, or a reference signal index (e.g., a group index). In an example, in a cell, a TRP may be indexed by a control resource set (coreset) group (or pool) of a coreset group (e.g., Figure 26 In an example, the TRP ID of the TRP may include a TRP index indicated in the DCI. In an example, the TRP ID of the TRP may include a TCI state group index of a TCI state group. The TCI state group may include at least one TCI state in which the wireless device receives a downlink TB or the base station transmits a downlink TB.

[0309] In an example, a base station may transmit one or more RRC messages to a wireless device including configuration parameters for a plurality of CORESETs on a cell (or a BWP of a cell). Each CORESET in the plurality of CORESETs may be identified by a CORESET index and may be associated with (or configured with) a CORESET pool (or group) index. One or more CORESETs in the plurality of CORESETs having the same CORESET pool index may indicate that DCI received on the one or more CORESETs is transmitted from the same TRP in a plurality of TRPs of the base station. The wireless device may determine a receive beam (or spatial domain filter) for PDCCH / PDSCH based on a TCI indication (e.g., DCI) and a CORESET pool index associated with the CORESET for the DCI.

[0310] In an example, when the wireless device receives one or more RRC messages (e.g., PDCCH-Config IE) including a first CORESET pool index (e.g., CORESETPoolIndex) value and a second CORESET pool index in a ControlResourceSet IE, the wireless device may receive multiple PDCCHs scheduling PDSCHs that completely overlap / partially overlap / non-overlap in the time and frequency domains. When the PDCCHs scheduling two PDSCHs are associated with different ControlResourceSets with different values ​​of CORESETPoolIndex, the wireless device may determine to receive only the PDSCHs that completely / partially overlap in the time domain.

[0311] In an example, the wireless device may assume (or determine) that for a ControlResourceSet without a CORESETPoolIndex, the ControlResourceSet is assigned a CORESETPoolIndex of 0. When a wireless device is scheduled using PDSCHs that fully overlap, partially overlap, or do not overlap in time and frequency, scheduling information for receiving the PDSCH is indicated and carried only by the corresponding PDCCH. It is expected that wireless devices will be scheduled using the same active BWP and the same SCS. In an example, when a wireless device is scheduled using PDSCHs that fully overlap, partially overlap, or do not overlap in time and frequency, the wireless device can be scheduled using up to two codewords simultaneously.

[0312] In an example, when a PDCCH scheduling two PDSCHs is associated with different ControlResourceSets having different values ​​of CORESETPoolIndex, the wireless device is allowed to perform the following operations: for any two HARQ process IDs in a given scheduled cell, if the wireless device is scheduled to start receiving a first PDSCH starting at symbol j via a PDCCH associated with a value of CORESETpoolIndex that ends at symbol i, the wireless device can be scheduled to receive a PDSCH that starts earlier than the end of the first PDSCH using a PDCCH associated with a different value of CORESETpoolIndex that ends later than symbol i; in the given scheduled cell, the wireless device can receive the first PDSCH and the second PDSCH in time slot i, the first PDSCH having a corresponding HARQ-ACK assigned to be transmitted in time slot j, the second PDSCH associated with a different value of CORESETpoolIndex, the second PDSCH starting later than the first PDSCH, and having its corresponding HARQ-ACK assigned to be transmitted in a time slot prior to time slot j.

[0313] In an example, if the wireless device is configured with a higher layer parameter PDCCH-Config containing two different values ​​of CORESETPoolIndex in ControlResourceSet, then for both cases, when tci-PresentInDCI is set to 'enabled' and tci-PresentInDCI is not configured in RRC connected mode, if DL If the offset between the reception of the DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the wireless device may assume that in the latest time slot (in which one or more CORESETs associated with the same value of CORESETPoolIndex as the PDCCH scheduling the PDSCH within the active BWP of the serving cell are monitored by the wireless device), the DM-RS port of the PDSCH associated with the value of CORESETPoolIndex of the serving cell is quasi-co-located with the RS with respect to the QCL parameter, which is used for the quasi-co-location indication of the PDCCH of the CORESET associated with the monitored search space with the lowest CORESET-ID among the CORESETs (which are configured with the same value of CORESETPoolIndex as the PDCCH scheduling the PDSCH). If the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state of the serving cell on which the PDSCH is scheduled includes 'QCL-TypeD', and at least one TCI code point indicates two TCI states, the wireless device may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest code point among the TCI code points including the two different TCI states.

[0314] Figure 31B An example of inter-cell TRP (or inter-PCI TRP) based communication between a base station (equipped with multiple TRPs) and a wireless device (equipped with a single panel or multiple panels) is shown. Figure 31A , multiple TRPs are associated with different PCIs. In the example, different Figure 31A, multiple TRPs are associated with (or belong to) different physical cells (cell 1 with PCI 1 and cell 2 with PCI 2), which may be referred to as inter-cell TRPs (or inter-PCI TRPs). A cell may be a serving cell or a non-serving (neighboring) cell for a wireless device. When operating an inter-cell TRP for a wireless device, the base station may configure cell 2 with PCI 2 as a portion of cell 1 with PCI 1 (e.g., a second TRP with a second PCI that is different from the first PCI of the first TRP), in which case the wireless device may receive a 1st SSB from cell 1 with PCI 1 and a 2nd SSB from cell 2 with PCI 2. The 1st SSB and the 2nd SSB may have different configuration parameters, wherein the configuration parameters may be based on the above description of Figure 28 、 Figure 29 and / or Figure 30 With inter-cell TRP, a wireless device may receive PDCCH / PDSCH and / or transmit PUCCH / PUSCH in different TCI states on cell 1 with PCI 1 and cell 2 with PCI 2 (e.g., one TCI state is associated with one of the 1st SSBs, another TCI state is associated with one of the 2nd SSBs, and so on).

[0315] In an example, a serving cell may be a cell (e.g., PCell, SCell, PSCell, etc.) on which a wireless device receives SSB / CSI-RS / PDCCH / PDSCH and / or transmits PUCCH / PUSCH / SRS, etc. A serving cell is identified by a serving cell index (e.g., ServCellIndex or SCellIndex configured in an RRC message). For wireless devices that are not configured with CA / DC in RRC_CONNECTED, there is only one serving cell including a primary cell. For wireless devices that are configured with CA / DC in RRC_CONNECTED, the term 'serving cell' is used to refer to a set of cells including a special cell and all secondary cells. For wireless devices configured with CA, a cell that provides additional radio resources on top of a special cell is called a secondary cell.

[0316] In an example, a non-serving (or neighboring) cell may be a cell on which a wireless device does not receive MIB / SIB / PDCCH / PDSCH and / or does not transmit PUCCH / PUSCH / SRS, etc. The non-serving cell has a physical cell identifier (PCI) that is different from the serving cell's PCI. The non-serving cell may not be identified by (or associated with) a serving cell index (e.g., ServCellIndex or SCellIndex). If the TCI state of the serving cell is associated with the SSB of the non-serving cell (e.g., in the TCI-State IE of TS 38.331), the wireless device may rely on the SSB of the non-serving cell for Tx / Rx beam (or spatial domain filter) determination (for PDCCH / PDSCH / PUCCH / PUSCH / CSI-RS / SRS, etc. for the serving cell). The base station does not transmit an RRC message to configure the resources of the PDCCH / PDSCH / PUCCH / PUSCH / SRS of the non-serving cell of the wireless device.

[0317] exist Figure 31BIn the example of , for a particular wireless device, cell 1 is a serving cell and is associated with a first TRP (TRP 1). Cell 2 is a non-serving (or neighboring) cell and is associated with a second TRP. The base station may transmit one or more RRC messages including configuration parameters of cell 1 to the wireless device. The configuration parameters of cell 1 may indicate multiple additional PCI configurations (e.g., SSB-MTC-AdditionalPCI IE) for multiple (non-serving or neighboring) cells of cell 1, each additional PCI configuration corresponding to a (non-serving or neighboring) cell having a PCI value different from that of the serving cell, and including: an additional PCI index (AdditionalPCIIndex) identifying the additional PCI configuration, the PCI of the non-serving cell, an SSB periodicity indication, an indication of the position of the (candidate) SSB in the SSB burst, an indication of the transmission power of the SSB, etc. The configuration parameters of cell 1 may further indicate multiple TCI states. Each TCI state in a plurality of TCI states may be associated with one or more TCI parameters including a TCI state identifier identifying the TCI state, one or more QCL information parameters including an SSB index identifying the SSB, and a QCL type indicator indicating one QCL type in a plurality of QCL types, for example, if the SSB is transmitted via cell 1 (or in another serving cell). If the SSB in the TCI state is transmitted via a non-serving (neighboring) cell, the TCI state may be further associated with an additional PCI index (AdditionalPCIIndex) indicating the (non-serving or neighboring) cell configured in the SSB-MTC-AdditionalPCI IE. Similar to multiple TRPs within a cell, a wireless device may receive downlink signals and / or transmit uplink signals based on the (activated / indicated) TCI state associated with the TRP. The difference between multiple TRPs within a cell and multiple TRPs between cells is that, for the latter case, the reference RS for the TCI state of the serving cell may come from the (non-serving or neighboring) cell (or transmitted via the cell). The SSB may be based on the above description of Figure 28 、 Figure 29 and / or Figure 30 The example embodiments described may be implemented.

[0318] exist Figure 31B In the example shown in FIG1 , cell 1 is the serving cell of the wireless device. Cell 2 is a (non-serving or neighboring) cell associated with cell 1 of the wireless device. Cell 2 may be the serving cell of a second wireless device. Cell 1 may be the (non-serving or neighboring) cell of the second wireless device. Different wireless devices may have different serving cells and non-serving / neighboring cells.

[0319] In an example, a base station may use two TRPs to transmit to a wireless device via cell 1. In an example, the base station may indicate (via a DCI / MAC CE) a first TCI state associated with an SSB / CSI-RS transmitted via cell 1 (or another serving cell) for a first transmission to the wireless device (via the PDCCH / PDSCH / PUSCH / PUCCH / SRS resources of cell 1). Additionally, the base station may indicate (via the same DCI / MAC CE or another DCI / MAC CE) a second TCI state associated with a second SSB transmitted via cell 2 (which is non-serving / neighboring) (a cell indicated by AdditionalPCIIndex in the TCI configuration parameter) for a second transmission to the wireless device (via the PDCCH / PDSCH / PUSCH / PUCCH / SRS resources of cell 1). The second SSB transmitted via cell 2 is different from the first SSB transmitted via cell 1. Using two TCI states from two TRPs (one TRP from the serving cell and the other TRP from the non-serving / neighboring cell) can avoid time-consuming handover (HO) between cell 1 and cell 2, and improve coverage when the wireless device moves at the edge of cell 1 and cell 2.

[0320] exist Figure 31A and Figure 31B In an example, two TCI states may be provided to a wireless device, each TCI state corresponding to one TRP in a plurality of TRPs. When a TCI state is used for a specific channel (e.g., PDSCH / PDCCH / PUCCH / PUSCH), the TCI state may be referred to as a channel-specific TCI state, where different channels may be associated with different channel-specific TCI states. When a TCI state is used for multiple channels (e.g., PDSCH / PDCCH / PUCCH / PUSCH), the TCI state may be referred to as a unified TCI state, where different channels may be associated with the same unified TCI state. The base station may transmit an RRC message indicating whether the TCI state is a unified TCI state for the wireless device.

[0321] based on Figure 31A and Figure 31BFor example, when the wireless device is close to the center of the cell, has more data to deliver and / or requires high reliability (for example, for URLLC service), the base station can perform data / signaling transmission based on multiple intra-cell TRPs for the wireless device (for example, which can be referred to as intra-cell M-TRP or intra-PCI M-TRP). For example, when the wireless device is at the edge of the cell and in the coverage of another cell (which may or may not be the serving cell of the wireless device) (moving or positioning), the base station can perform data / signaling transmission based on multiple inter-cell TRPs for the wireless device (for example, which can be referred to as inter-cell M-TRP or inter-PCI M-TRP).

[0322] In the prior art, a base station may enable power saving operation of a wireless device due to limited battery capability of the wireless device, for example, based on BWP management, SCell dormancy mechanism, wakeup / enter sleep indication, SSSG switching on active BWP, and / or PDCCH skipping.

[0323] However, when instructing a wireless device to perform power saving operations, the base station may not be able to save energy from the perspective of the base station. For example, when the base station needs to periodically transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) during a certain period of time, even if there are no active wireless devices transmitting to / receiving from the base station during the period of time. When the base station transitions a cell to a dormant state by switching the cell's active BWP to a dormant BWP, the base station may need to periodically transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.).

[0324] In an example, if the base station needs to reduce the periodicity of always-on downlink signal transmission for network energy saving, the base station may transmit an RRC message (eg, SIB1) indicating a longer periodicity of always-on downlink signal transmission.

[0325] In an example, before determining to power down (e.g., both RF modules and baseband units (BBUs)) for network energy saving, the base station may transmit an RRC reconfiguration message to each wireless device in the source cell to indicate handover to the neighboring cell. The handover (HO) procedure may be based on Figure 32 The present invention is implemented in accordance with an exemplary embodiment of the present invention.

[0326] Figure 32 An example of performing a HO procedure for a wireless device from a source gNB to a target gNB is shown.

[0327] In an example, for network controlled mobility in RRC_CONNECTED, the PCell may be changed using an RRC connection reconfiguration message (e.g., RRCReconfiguration) containing reconfigurationWithSync (in the NR specification) or MobilityControlInfo (handover) in the LTE specification. The SCell may be changed using an RRC connection reconfiguration message with or without reconfigurationWithSync or MobilityControlInfo. The network may trigger the HO procedure, for example, based on radio conditions, load, QoS, UE category, etc. The RRC connection reconfiguration message may be based on the UE's Figure 33 and Figure 34 The example embodiments described in the accompanying drawings may be implemented.

[0328] like Figure 32 As shown, the network may configure the wireless device to perform measurement reporting (possibly including configuration of measurement gaps). Measurement reports are Layer 3 reports, distinct from Layer 1 CSI reports. The wireless device may transmit one or more measurement reports to the source gNB (or source PCell). In this example, the network may blindly initiate a HO, for example, without receiving measurement reports from the wireless device. Before sending the HO message to the wireless device, the source gNB may prepare one or more target cells. The source gNB may select candidate target PCells.

[0329] like Figure 32 As shown, based on one or more measurement reports from the wireless device, the source gNB may provide the target gNB with a list of the best cells for each frequency for which measurement information is available, for example, in order of decreasing RSRP value. The source gNB may also include available measurement information for the cells provided in the list. The target gNB may decide which cells to configure for use after HO, which may include cells other than the cells indicated by the source gNB. In the example, Figure 32 As shown, the source gNB may transmit a HO request to the target gNB. The target gNB may respond with a HO message. In this example, in the HO message, the target gNB may indicate the access stratum configuration to be used in the target cell of the wireless device.

[0330] In this example, the source gNB may transparently (e.g., without changing the value / content) forward the HO message / information received from the target gNB to the wireless device. In the HO message, the RACH resource configuration may be configured to enable the wireless device to access a cell in the target gNB. Where appropriate, the source gNB may initiate data forwarding on (a subset of) dedicated radio bearers.

[0331] like Figure 32As shown, after receiving the HO message, the wireless device may start the HO timer (e.g., T304) with the initial timer value. The HO timer may be configured in the HO message. Based on the HO message, the wireless device may apply the RRC parameters of the target PCell of the target gNB and / or the cell group (MCG / SCG) associated with the target PCell and perform downlink synchronization with the target gNB. After performing downlink synchronization with the target gNB (e.g., based on Figure 29 and / or Figure 30 After or in response to searching for a suitable / detectable SSB from candidate SSBs configured on the target gNB, the wireless device may initiate a random access (e.g., based on Figure 13A 、 Figure 13B and / or Figure 13C In an example, a contention-free or contention-based) procedure is used to attempt to access the target gNB at an available RACH opportunity according to RACH resource selection, where the available RACH opportunity may be configured in the RACH resource configuration (e.g., based on the RACH resource configuration described later). Figure 34 When a dedicated preamble is allocated for random access in the target gNB, the RAN may ensure that the preamble is available from the first RACH opportunity that the wireless device can use.

[0332] In an example, the wireless device may activate an uplink BWP configured with firstActiveUplinkBWP-id and a downlink BWP configured with firstActiveDownlinkBWP-id on the target PCell after performing HO to the target PCell.

[0333] In an example, after applying the RRC parameters of the target PCell and / or completing downlink synchronization with the target PCell, the wireless device may, for example, Figure 13A 、 Figure 13B and / or Figure 13C The described example embodiments perform RACH procedures to perform UL synchronization. Performing UL synchronization may include: activating an uplink BWP (eg, a BWP configured as firstActiveUplinkBWP-id) of an uplink BWP of a target PCell. Figure 33 ) transmits a preamble; in the active downlink BWP (eg, the BWP configured as firstActiveDownlinkBWP-id, as shown Figure 33The wireless device monitors the PDCCH on the target PCell (as shown) to receive an RAR including a TA for PUSCH / PUCCH transmission via the target PCell; receives the RAR and / or obtains the TA. After completing UL synchronization, the wireless device obtains the TA for PUSCH / PUCCH transmission via the target PCell. The wireless device transmits PUSCH / PUCCH via the target PCell by using the TA to adjust the uplink transmission timing. Adjusting the uplink transmission timing may include advancing or delaying the transmission by an amount indicated by the value of the TA, for example, to ensure that the uplink signal received at the target PCell is aligned (in the time domain) with the uplink signal transmitted from other wireless devices.

[0334] In an example, the wireless device may release RRC configuration parameters of the source PCell and the MCG / SCG associated with the source PCell.

[0335] In this specification, HO triggered by receiving an RRC reconfiguration message (e.g., RRCReconfiguration) including a HO command / message (e.g., by including reconfigurationWithSync (in NR specifications) or mobilityControlInfo (handover) included in LTE specifications) is referred to as normal HO, unconditional HO, and is different from HO that will be triggered in Figure 35 This is in contrast to the conditions described later in HO (CHO).

[0336] In the example, Figure 32 As shown, the wireless device may transmit the preamble to the target gNB via a RACH resource. The RACH resource may be selected from multiple RACH resources (e.g., configured in the rach-ConfigDedicated IE, as shown in FIG. 1 ) based on the SSB / CSI-RS measurement of the target gNB. Figure 33 and Figure 34 The wireless device may select a (best) SSB / CSI-RS from the configured SSB / CSI-RS of the target gNB. The wireless device may select an SSB / CSI-RS with an RSRP value greater than the RSRP threshold configured for the RA procedure from the configured SSB / CSI-RS of the target gNB. The wireless device then determines a RACH opportunity (e.g., time domain resource, etc.) associated with the selected SSB / CSI-RS and determines a preamble associated with the selected SSB / CSI-RS.

[0337] In an example, the target gNB may receive a preamble transmitted from the wireless device. The target gNB may transmit a random access response (RAR) to the wireless device, where the RAR includes the preamble transmitted by the wireless device. The RAR may also include a TAC for uplink transmissions via the target PCell. In response to receiving the RAR including the preamble, the wireless device may complete the random access procedure. In response to completing the random access procedure, the wireless device may stop the HO timer (T304). The wireless device may transmit an RRC reconfiguration complete message to the target gNB after completing the random access procedure or before completing the random access procedure. After completing the random access procedure to the target gNB, the wireless device may apply the CQI reporting configuration, SRS configuration, and the first part of the SRS configuration, which does not require the wireless device to know the system frame number (SFN) of the target gNB. After completing the random access procedure to the target PCell, the wireless device may apply the second part of the measurement and radio resource configuration after obtaining the SFN of the target gNB, which requires the wireless device to know the SFN of the target gNB (e.g., measurement gaps, periodic CQI reporting, SR configuration, SRS configuration).

[0338] In an example, based on a HO procedure (e.g., Figure 32 As shown in Figure 2, for network energy conservation, the base station can instruct each wireless device in the source cell to perform a 4-step or 2-step RACH-based (contention-free) HO to a neighboring cell. After the wireless device completes the HO procedure to the neighboring cell, the base station can shut down (RF part and BBU, etc.) to save energy.

[0339] Figure 33 An example embodiment of RRC messages for HO is shown. Figure 33In an example, the base station may transmit and / or the wireless device may receive an RRC reconfiguration message (e.g., RRCReconfiguration-IE) indicating an RRC connection modification. The RRC reconfiguration message may convey information for measurement configuration, mobility control, radio resource configuration (including RB, MAC main configuration, and physical channel configuration), and AS security configuration. The RRC reconfiguration message may include the configuration of a master cell group (masterCellGroup). The master cell group may be associated with a SpCell (SpCellConfig). When SpCellConfig includes reconfiguration with synchronization (reconfigurationWithSync), the wireless device determines that the SpCell is a target PCell for HO. Reconfiguration with synchronization (reconfigurationWithSync) may include cell-common parameters (spCellConfigCommon) of the target PCell, an RNTI (newUE-Identity) identifying the wireless device in the target PCell, a value of T304, dedicated RACH resources (rach-ConfigDedicated), etc. In the example, the dedicated RACH resources may include one or more RACH opportunities, one or more SSBs, one or more CSI-RSs, one or more RA preamble indexes, etc.

[0340] Figure 34 Shown based on the above Figure 33 The exemplary embodiment of the described exemplary embodiment is an exemplary embodiment of an RRC message for RACH resource configuration for a HO procedure. Figure 33 As shown, the reconfigurationWithSync IE includes the dedicated RACH resources indicated by the rach-ConfigDedicated IE.

[0341] like Figure 34As shown, the rach-ConfigDedicated IE includes the contention-free RA resources indicated by the cfra IE. The cfra IE includes multiple opportunities indicated by the rach-ConfigGeneric IE, the ssb-perRACH-Occasion IE, and multiple resources associated with SSBs (indicated by the ssb IE) or CSI-RS (indicated by the csirs IE). The ssb-perRACH-Occasion IE indicates the number of SSBs per RACH opportunity. The rach-ConfigGeneric IE indicates the configuration of CFRA opportunities. The wireless device ignores the preambleReceivedTargetPower, preambleTransMax, powerRampingStep, and ra-ResponseWindow signaled in this field and uses the corresponding values ​​provided in RACH-ConfigCommon.

[0342] like Figure 34 As shown, when multiple resources for CFRA configured in the reconfigurationWithSync IE are associated with SSBs, the resources IE includes an ssb IE. The ssb IE includes a CFRA SSB resource list (ssb-ResourceList) and an indication of a PRACH opportunity mask index (ra-ssb-OccasionMaskIndex). Each CFRA SSB resource in the CFRA SSB resource list includes an SSB index, an RA preamble index, and the like. ra-ssb-OccasionMaskIndex indicates the PRACH mask index selected for the RA resource. The mask is valid for all SSB resources signaled in the ssb-ResourceList.

[0343] like Figure 34 As shown in FIG, when multiple resources for CFRA configured in the reconfigurationWithSync IE are associated with CSI-RS, the resources IE includes a csir IE. The csir IE includes a CFRA CSI-RS resource list (csirs-ResourceList) and an RSRP threshold (rsrp-ThresholdCSI-RS). Each CFRA CSI-RS resource in the CFRA CSI-RS resource list includes a CSI-RS index, an RA opportunity list (ra-OccasionList), an RA preamble index, and the like.

[0344] In an example, when a wireless device moves in a network where multiple small cells (e.g., cells with a cell coverage of hundreds of meters) are deployed, HO execution triggered by receiving an RRC reconfiguration message including a reconfigurationWithSync IE may introduce HO delay (e.g., too late HO). An improved HO mechanism based on measurement event triggering is proposed to reduce HO delay, such as Figure 35 shown.

[0345] Figure 35 An example embodiment of a Conditional Handover (CHO) procedure is shown. In the example, Figure 35 As shown, the network (e.g., base station, source gNB) can configure the wireless device to perform measurement reporting (possibly including configuration of measurement gaps) for multiple neighboring cells (e.g., cells from candidate target gNB 1, candidate target gNB 2, etc.). The measurement reports are Layer 3 reports, different from Layer 1 CSI reports. The wireless device can transmit one or more measurement reports to the source gNB (or source PCell).

[0346] like Figure 35 As shown, based on one or more measurement reports from the wireless device, the source gNB may provide the target gNB with a list of the best cells for each frequency for which measurement information is available, for example, in order of decreasing RSRP. The source gNB may also include available measurement information for the cells provided in the list. The target gNB may decide which cells to configure for use after CHO, which may include cells other than the cells indicated by the source gNB. In the example, Figure 35 As shown, the source gNB may transmit a HO request to the target gNB. The target gNB may respond with a HO message. In an example, in the HO message, the target gNB may indicate the access stratum configuration (e.g., the RRC configuration of the target cell) to be used for the wireless device.

[0347] In an example, the source gNB may transparently (e.g., without changing the value / content) forward the handover message / information received from the target gNB (e.g., contained in the RRC reconfiguration message of the target gNB) to the wireless device.

[0348] In an example, the source gNB may include a conditional reconfiguration message (e.g., a conditionalReconfiguration IE in an RRC reconfiguration message) Figure 36 to configure a different HO procedure than the normal one (e.g. Figure 32 、 Figure 33 and / or Figure 34In the case of performing CHO to a candidate target PCell, the conditional reconfiguration message may include a list of candidate target PCells, each candidate target PCell being associated with a dedicated RACH resource for the RA procedure. CHO execution conditions (or RRC reconfiguration conditions) are also configured for each candidate target PCell, etc. In the example, the CHO execution conditions may include a measurement event A3 in which the candidate target PCell becomes offset better than the current PCell (e.g., the PCell of the source gNB), a measurement event A4 in which the candidate target PCell becomes better than an absolute threshold configured in the RRC reconfiguration message, a measurement event A5 in which the current PCell becomes worse than a first absolute threshold and the candidate target PCell becomes better than a second absolute threshold, and so on.

[0349] exist Figure 35 In the example of , based on the received RRC reconfiguration message including the parameters of the CHO procedure, the wireless device can evaluate the (RRC) reconfiguration conditions of the candidate target PCell list and / or the current / source PCell. The wireless device can measure the RSRP / RSRQ of the SSB / CSI-RS of each candidate target PCell in the candidate target PCell list. Figure 32 In the normal HO procedure described in

[15] , the wireless device does not perform HO to the target PCell in response to receiving an RRC reconfiguration message including parameters for the CHO procedure. The wireless device may perform HO to the target PCell for CHO only if the (RRC) reconfiguration conditions for the target PCell are met. Otherwise, the wireless device may continue evaluating the reconfiguration conditions for the list of candidate target PCells, for example, until the HO timer expires or an RRC reconfiguration message is received indicating abort of the CHO procedure.

[0350] exist Figure 35 In the example, in response to a reconfiguration condition of a first candidate target PCell (e.g., PCell 1) being met or satisfied, the wireless device may perform a CHO procedure toward the first candidate target PCell. When multiple candidate target PCells meet or satisfy the reconfiguration condition, the wireless device may select one of the multiple candidate target PCells through its implementation.

[0351] In this example, executing the CHO procedure to the first candidate target PCell is the same as executing Figure 32By performing the CHO procedure, the wireless device may release the RRC configuration parameters of the source PCell and the MCG associated with the source PCell, apply the RRC configuration parameters of PCell 1, reset the MAC, perform cell group configuration for the received MCG included in the RRC reconfiguration message for PCell 1, and / or perform an RA procedure to PCell 1, etc.

[0352] In the example, the MCG of the RRC reconfiguration message of PCell 1 can be associated with the SpCell (SpCellConfig) on ​​the target gNB 1. When sPCellConfig includes reconfiguration with synchronization (reconfigurationWithSync), the wireless device determines that the SpCell is the target PCell (PCell 1) of the HO. The reconfiguration with synchronization (reconfigurationWithSync) can include the cell common parameters (spCellConfigCommon) of the target PCell, the RNTI (newUE-Identity) that identifies the wireless device in the target PCell, the value of T304, the dedicated RACH resources (rach-ConfigDedicated), etc. In the example, the dedicated RACH resources can include one or more RACH opportunities, one or more SSBs, one or more CSI-RSs, one or more RA preamble code indices, etc. In the example, the wireless device can determine that the HO is the target PCell (PCell 1) of the HO according to the above description. Figure 32 The described example embodiment performs cell group configuration for the received primary cell group included in the RRC reconfiguration message for PCell 1 on target gNB 1.

[0353] Figure 36 An example of RRC messages for CHO is shown. Figure 36 In an example, the base station may transmit and / or the wireless device may receive an RRC reconfiguration message (e.g., RRCReconfiguration-V1610-IE) indicating the RRC connection modification. The RRC reconfiguration message may be included in a (parent) RRC reconfiguration message (e.g., RRCReconfiguration-IE), such as Figure 33 As shown, the (parent) RRC reconfiguration message may include a (L3 beam / cell) measurement configuration (e.g., measConfig IE).

[0354] exist Figure 36In the example of , the RRC reconfiguration message (e.g., RRCReconfiguration-V1610-IE) may include a conditional reconfiguration IE (conditionalReconfiguration IE). The conditional reconfiguration IE may include a conditional reconfiguration list (condReconfigToAddModList). Each conditional reconfiguration corresponds to a corresponding candidate target cell (PCell) in the candidate target cell list. For each conditional reconfiguration in the conditional reconfiguration list, the base station may indicate one or more measurement events (condExecutionCond) for triggering CHO on the candidate target PCell, an RRC reconfiguration message (condRRCReconfig) of the candidate target cell (PCell) received by the source gNB from the target gNB via the X2 / Xn interface. The RRC reconfiguration message of the candidate target cell may be based on the above description of Figure 33 and / or Figure 34 The example embodiments described herein may be implemented. In the example, the RRC reconfiguration message may include the configuration of the master cell group (masterCellGroup) of the target gNB. The master cell group may be associated with the SpCell (SpCellConfig). When sPCellConfig includes reconfiguration with synchronization (reconfigurationWithSync), the SpCell is the target PCell for performing CHO. The reconfiguration with synchronization (reconfigurationWithSync) may include the cell common parameters (spCellConfigCommon) of the target PCell, the RNTI (newUE-Identity) that identifies the wireless device in the target PCell, the value of T304, dedicated RACH resources (rach-ConfigDedicated), etc. In the example, the dedicated RACH resources may include one or more RACH opportunities, one or more SSBs, one or more CSI-RSs, one or more RA preamble indexes, etc.

[0355] exist Figure 36In the example, the measurement event (condExecutionCond) for triggering CHO on the candidate target PCell is an execution condition that needs to be met (at the wireless device) in order to trigger the execution of the conditional reconfiguration of CHO. The indication of the measurement event can point to a measurement ID (MeasId), which identifies a measurement configuration from multiple measurement configurations configured by the source gNB (e.g., included in the measConfig IE). The measurement configuration can be associated with multiple measurement events (or conditional events). The conditional events can include conditional event A3, conditional event A4, and / or conditional event A5, etc. Conditional event A3 is that the candidate target PCell becomes better than the current PCell (e.g., the source gNB's PCell) by an offset. Conditional event A4 is that the candidate target PCell becomes better than an absolute threshold configured in the RRC reconfiguration message. Conditional event A5 is that the current PCell becomes worse than a first absolute threshold and the candidate target PCell becomes better than a second absolute threshold, etc.

[0356] In an example, performing CHO by a decision of a wireless device based on evaluating reconfiguration conditions on multiple candidate target cells (long-term and / or layer 3 beam / cell measurements relative to one or more configured thresholds) may result in load imbalance on the cells and / or CHO failure if the target cell changes its configuration during the CHO condition evaluation (e.g., for network energy saving), etc. Figure 37 An improved handover triggered by layer 1 / 2 signaling is proposed in [1]. In an example, layer 1 signaling may include DCI transmitted via PDCCH. Layer 2 signaling may include MAC CE scheduled by the DCI. For HO / CHO, layer 1 / 2 signaling is different from layer 3 signaling, which includes RRC reconfiguration messages.

[0357] Figure 37 An example embodiment of a layer 1 / 2 triggered HO procedure is shown. In the example, Figure 37 As shown, the network (e.g., base station, source gNB) can configure the wireless device to perform measurement reporting (possibly including configuration of measurement gaps) for multiple neighboring cells (e.g., cells from candidate target gNB 1, candidate target gNB 2, etc.). The measurement report is a layer 3 report, different from the layer 1 CSI report. The wireless device can transmit one or more measurement reports to the source gNB (or source PCell, i.e., Figure 37 Cell 0 in ).

[0358] like Figure 37As shown, based on one or more measurement reports from the wireless device, the source gNB may provide the target gNB with a list of the best cells for each frequency for which measurement information is available, for example, in order of decreasing RSRP. The source gNB may also include available measurement information for the cells provided in the list. The target gNB may decide which cells to configure for use after HO (as target PCell and / or one or more SCells), which may include cells other than the cells indicated by the source gNB. In the example, Figure 37 As shown, the source gNB may transmit a HO request to the target gNB. The target gNB may respond with a HO message. In an example, in the HO message, the target gNB may indicate the access stratum configuration (e.g., the RRC configuration of the target cell) to be used for the wireless device.

[0359] In an example, the source gNB may transparently (e.g., without changing the value / content) forward the HO message / information received from the target gNB (e.g., contained in the RRC reconfiguration message of the target gNB, the cell group configuration IE of the target gNB, and / or the SpCell configuration IE of the target PCell / SCell of the target gNB) to the wireless device.

[0360] In an example, the source gNB may configure a different HO procedure (e.g., as in the normal HO procedure) by including a Layer 1 / 2 candidate PCell configuration message (e.g., the newly defined candidates-L1L2-Config IE) in the RRC reconfiguration message of the source gNB. Figure 32 、 Figure 33 and / or Figure 34 ) and / or CHO procedures (e.g., as Figure 35 and / or Figure 36 HO (PCell handover / change, mobility, etc.) procedures based on layer 1 / 2 signaling (as shown). In the case where the HO based on layer 1 / 2 signaling is triggered by layer 1 / 2 signaling and performs handover to a candidate target PCell, etc., the layer 1 / 2 candidate PCell configuration message may include a list of candidate target PCells, each of which is associated with a dedicated RACH resource for the RA procedure. The parameter configuration of the candidate target PCell may have multiple options.

[0361] In the example, as a first option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message of the source gNB may include the (encapsulated) RRC reconfiguration message of the candidate target gNB (e.g., RRCReconfiguration) received by the source gNB from the candidate target gNB via the X2 / Xn interface. The (encapsulated) RRC reconfiguration message of the candidate target gNB may reuse the same signaling structure of the RRC reconfiguration message of the source gNB, such as Figure 33 and / or Figure 34 shown.

[0362] In an example, as a second option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message of the source gNB may include the (encapsulated) cell group configuration message (e.g., CellGroupConfig) of the candidate target gNB received by the source gNB from the candidate target gNB via the X2 / Xn interface. The (encapsulated) cell group configuration message of the candidate target gNB may reuse the same signaling structure of the cell group configuration message of the source gNB, such as Figure 33 and / or Figure 34 Compared with the first option, the second option can reduce the signaling overhead of parameter configuration of the candidate target PCell.

[0363] In an example, as a third option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message of the source gNB may include the (encapsulated) SpCell configuration message (e.g., SpCellConfig) of the candidate target gNB received by the source gNB from the candidate target gNB via the X2 / Xn interface. The (encapsulated) SpCell configuration message of the candidate target gNB may reuse the same signaling structure of the SpCell configuration message of the source gNB, such as Figure 33 and / or Figure 34 Compared with the second option, the third option can reduce the signaling overhead of parameter configuration of the candidate target PCell.

[0364] In an example, for each candidate target PCell, the source gNB may indicate cell-common and / or UE-specific parameters (e.g., SSB / CSI-RS, BWP, RACH resources, PDCCH / PDSCH / PUCCH / PUSCH resources, etc.).

[0365] exist Figure 37 In an example, according to a received RRC reconfiguration message including parameters for a HO procedure based on layer 1 / 2 signaling, the wireless device may perform layer 1 / 2 measurement reporting (CSI / beam) for a candidate target PCell list and / or a current PCell. The layer 1 / 2 measurement report may include layer 1 RSRP, layer 1 RSRQ, PMI, RI, layer 1 SINR, CQI, etc.

[0366] In an example, layer 1 / 2 measurement reports may be transmitted with a periodicity configured by the source gNB.

[0367] In an example, a layer 1 / 2 measurement report may be triggered when the CSI / beam measurement of the candidate target PCell is greater than a threshold or (offset) greater than the current PCell, etc.

[0368] exist Figure 37 In an example, the base station may perform an inter-cell beam management (ICBM) procedure before transmitting layer 1 / 2 signaling that triggers a HO procedure including handing over a PCell from a source gNB to a target gNB. The ICBM procedure may allow the base station and the wireless device to use the resources (time / frequency / space) of the target gNB (or the PCell / SCell of the target gNB) without performing a HO procedure to the target gNB, thereby reducing the frequency of performing the HO procedure. The ICBM procedure may allow the base station and the wireless device to synchronize the time / frequency / beam to the target PCell of the target gNB before performing the HO, which may reduce the HO latency. ICBM may be based on the HO procedure described later. Figure 38 The present invention is implemented in accordance with an exemplary embodiment of the present invention.

[0369] exist Figure 37 In an example, in response to a configured ICBM procedure, the source gNB may transmit a first DCI / MAC CE to the wireless device, wherein the first DCI / MAC CE configures / indicates a first candidate target cell (e.g., cell 1) among candidate target cells (PCell / SCell) as a neighbor or non-serving cell other than the current PCell (e.g., cell 0) of the wireless device. The base station may select the first candidate target cell from the candidate target cells based on a Layer 1 / 2 measurement report from the wireless device.

[0370] In an example, a first DCI / MAC CE (e.g., activating a TCI state) may indicate that a reference RS (e.g., SSB / CSI-RS) associated with the first TCI state is from the first candidate target cell (cell 1) (e.g., by associating the reference RS with an additional PCI of cell 1 that is different from the PCI of cell 0), as a supplement to the reference RS associated with the second TCI state being from the current PCell (cell 0). The association between reference signals and TCI states may be based on the above description of Figure 31B Activating the TCI state by using the RS of a neighboring (non-serving) cell as a reference RS by a DCI / MAC CE may allow a base station to use the beam of the neighboring cell to transmit downlink signals / channels or receive uplink signals / channels, and / or use the beam of the current cell for transmission / reception without performing a HO to the neighboring cell for transmission / reception.

[0371] exist Figure 37 In the example of FIG, in response to receiving the first DCI / MAC CE, the wireless device may apply the first TCI state and the second TCI state to downlink reception and / or uplink transmission.

[0372] In the example, applying the first TCI state and the second TCI state to downlink reception may include: receiving PDCCH / PDSCH / CSI-RS (from cell 1) according to the first TCI state (or associated with it) using the same receive beam / filter as used to receive the reference signal transmitted from cell 1, and receiving PDCCH / PDSCH / CSI-RS (from cell 0) according to the second TCI state (or associated with it) using the same receive beam / filter as used to receive the reference signal transmitted from cell 0.

[0373] In an example, applying the first TCI state and the second TCI state to uplink transmission may include: transmitting PUCCH / PUSCH / SRS according to the first TCI state (or associated with it) (via cell 1) using the same transmission beam / filter as used to receive the reference signal transmitted from cell 1, and transmitting PUCCH / PUSCH / SRS according to the second TCI state (or associated with it) using the same transmission beam / filter as used to receive the reference signal transmitted from cell 0 (via cell 0).

[0374] exist Figure 37 In an example, the base station may skip performing the ICBM procedure before transmitting the layer 1 / 2 signaling that triggers the HO procedure. For example, the base station may skip performing the ICBM procedure when beamforming is not used in the target PCell, or if there are no good SSBs from the target PCell, or if there are no available radio resources from the target PCell to accommodate the wireless device, or when the wireless device does not support ICBM and / or when the base station does not support ICBM.

[0375] exist Figure 37 In the example shown in Figure 2, the source base station may determine to hand over the wireless device from the source gNB (Cell 0) to the target gNB (Cell 1). The source base station may determine the handover based on load / traffic conditions, CSI / beam reports from the target gNB, the location / trajectory of the wireless device, network power saving policies (e.g., the source base station determines to transition Cell 0 and / or one or more SCells to save power), etc.

[0376] exist Figure 37 In the example of , the source base station may transmit a second DCI / MAC CE indicating a PCell change from the current PCell (cell 0) to a new cell (eg, cell 1).

[0377] In an example, the new cell may be one of the neighboring (non-serving) cells used in the ICBM procedure (e.g., indicated by the first DCI / MAC CE). Figure 37In the example of , the new cell may be cell 1. When the ICBM procedure is supported and / or configured, the wireless device is synchronized with the target gNB regarding which beam should be used for transmission / reception via the target gNB before performing the HO procedure instructed by the source base station, which is different from the (C)HO based on layer 3 signaling (e.g. Figure 32 and / or Figure 35 as shown), where the wireless device needs to synchronize to the target gNB after performing HO / CHO and then obtain an indication of the new beam to be used for the target gNB.

[0378] In an example, when the ICBM procedure is not configured / supported / indicated / activated for the new cell, the new cell can be one of the multiple neighboring (non-serving) cells included in the L1 beam / CSI report, for example, the one with the best measurement report, the one with the closest distance to the wireless device, etc.

[0379] exist Figure 37 In the example of FIG, in response to receiving the second DCI / MAC CE, the wireless device may change PCell from cell 0 to cell 1. The wireless device may apply the (stored / received) RRC parameters (included in RRCReconfiguration, CellGroupConfig, and / or SpCellConfig IE) of the target PCell (cell 1) as the current PCell.

[0380] In an example, in a case where the wireless device is already synchronized with the target PCell based on the ICBM procedure, the wireless device may skip downlink (time / frequency / beam) synchronization (e.g., monitoring MIB / SSB / SIB and / or selecting SSB as a reference for downlink reception and / or uplink transmission) when ICBM is configured / supported / indicated / activated before receiving the 2nd DCI / MAC CE.

[0381] In an example, for example, when the target PCell is close to the source PCell, or the uplink TA is the same or similar for the source PCell and the target PCell, or dedicated RACH resources are not configured in the RRC reconfiguration message of the target PCell, the wireless device can skip performing the RA procedure to the target PCell before transmitting to and / or receiving from the target PCell.

[0382] In an example, the wireless device may be based on the above description of Figure 32 、 Figure 33 、 Figure 34 、 Figure 35 and / or Figure 36Example embodiments are described to perform downlink synchronization (SSB / PBCH / SIB monitoring) and / or uplink synchronization (RA procedure) for HO based on layer 1 / 2 signaling (e.g., when ICBM is not configured / supported / indicated / activated), just as is done for HO / CHO based on layer 3 signaling.

[0383] Figure 38 An example embodiment of the ICBM procedure is shown. Figure 38 In the example shown in FIG2 , a first wireless device (UE1) may be within the coverage of cell 0, which is deployed under a first node (e.g., gNB A or TRP A). UE1 is not within the coverage of cell 1, which is deployed under a second node (e.g., gNB B or TRP B). Cell 0 and cell 1 have different PCIs. UE1 may use an RS (e.g., RS1) transmitted from cell 0 as a reference RS for a TCI state used for beam / spatial domain filter determination (Tx / Rx-based TCI state 0 associated with RS1) for downlink reception and / or uplink transmission. UE1 does not use RSs (e.g., RS2 and / or RS3) transmitted from cell 1 as reference RSs for the TCI state. UE1 configured with a TCI state associated with an RS of a serving cell having a first PCI and not associated with an RS of another cell having a second PCI different from the first PCI may be referred to in this specification as a wireless device without (configured / activated) ICBM.

[0384] exist Figure 38 In the example shown in FIG2 , a second wireless device (UE2) may be within the coverage of cell 0, which is deployed under a first node (e.g., gNB A or TRPA). UE2 is also within the coverage of cell 1, which is deployed under a second node (e.g., gNB B or TRPA B). Cell 0 and cell 1 have different PCIs. UE2 may use an RS transmitted from cell 0 (e.g., RS2) as a reference RS for a first TCI state (used for beam / spatial domain filter determination for downlink reception and / or uplink transmission via cell 0 (Tx / Rx-based TCI state 1 associated with RS2). UE2 may also use an RS transmitted from cell 1 (e.g., RS3) as a reference RS for a second TCI state (used for beam / spatial domain filter determination for downlink reception and / or uplink transmission via cell 1 (Tx / Rx-based TCI state 2 associated with RS3). A UE2 configured with a first TCI state associated with an RS of a serving cell having a first PCI and configured with a second TCI state associated with an RS of another cell having a second PCI different from the first PCI may be referred to in this specification as a wireless device with (configured / activated) ICBM.

[0385] In the example, when gNB B or TRP B receives an uplink signal / channel with a second TCI state, the gNB B or TRP B may forward the uplink signal / channel to gNB A or TRPA for processing.

[0386] In an example, gNB A or TRP A may forward the downlink signal / channel to gNB B or TRP B for transmission to the wireless device along with the second TCI state.

[0387] exist Figure 38 In the ICBM procedure of UE2, cell 1 having a second PCI different from the first PCI of cell 0 can be regarded as / configured as part of cell 0 of UE2 (e.g., a second TRP having a second PCI different from the first PCI of the first TRP), for example, based on the above description of Figure 31B When cell 1 is configured as part of cell 0, cell 0 and cell 1 may belong to the same DU (or gNB-DU). The gNB-DU may be configured based on the above description of Figure 1A and / or Figure 1B The example embodiments described herein are implemented. PDCCH / PDSCH / PUCCH / PUSCH resources are shared between cell 1 and cell 0 in a manner transparent to UE 2. However, the SSB / CSI-RS of cell 0 does not share the same resources as the SSB / CSI-RS of cell 1. The SSB / CSI-RS of cell 0 may have different configuration parameters (e.g., number of beams, periodicity, transmit power, etc.) than those of the SSB / CSI-RS of cell 1.

[0388] In the example, for example, when cell 1 is based on the above Figure 33 and / or Figure 36 When the described example embodiment is configured as a candidate target cell, cell 1 having a second PCI different from the first PCI of cell 0 may be considered / configured as a separate cell from cell 0 of UE 2. When cell 1 is configured as a separate cell from cell 0, cell 0 and cell 1 may belong to different DUs (or gNB-DUs) associated with the same CU (or gNB-CU) or different CUs. The gNB-DU and / or gNB-CU may be based on the above description of the Figure 1A and / or Figure 1B Cell resources (SSB / CSI-RS / PDCCH / PDSCH / PUCCH / PUSCH) are not shared between cell 1 and cell 0. Cell 1 has configuration parameters for cell resources that are different from (or independent of) the configuration parameters for cell resources of cell 0.

[0389] In the prior art, a base station configures the RRC configuration parameters (SSB, RACH resources, MAC parameters, PHY cell common and / or UE specific parameters, such as Figure 33 、 Figure 34 and / or Figure 36 ) for performing a (C)HO from the source PCell to the target PCell. When performing a (C)HO to the target PCell, the wireless device applies the received / stored RRC configuration parameters. The wireless device begins performing downlink synchronization to the target PCell (e.g., by monitoring the time / frequency alignment of the SSBs configured on the target PCell, e.g., according to 3GPP TS 38.213 Section 4 - Synchronization Procedure). After downlink synchronization is completed, the wireless device begins performing uplink synchronization, e.g., by initiating a (CF)RA procedure based on the RACH resources configured on the target PCell. The wireless device receives a time alignment (TA) command in the RAR corresponding to the preamble transmitted by the wireless device.

[0390] In the prior art, in order to transmit a preamble for a CFRA procedure, when multiple beams are used by a base station for SSB transmission (e.g., based on the above description of Figure 29 and / or Figure 30 The wireless device may select a RACH resource on the target PCell (e.g., based on the example embodiment described above) based on the RSRP value of the first SSB being greater than the RSRP threshold. Figure 34 The wireless device selects a first SSB from a plurality of candidate SSBs configured in the example embodiment described in the embodiment described in the preceding text. The wireless device determines a preamble having a preamble index associated with the selected first SSB based on the RACH resource configuration parameters. After selecting the first SSB, the wireless device determines the next available PRACH opportunity corresponding to the selected first SSB from the PRACH opportunities that is permitted by the restrictions given by the ra-ssb-OccasionMaskIndex configured in the rach-ConfigDedicated IE, such as Figure 34 As shown. The wireless device transmits the preamble to the target PCell via the determined PRACH opportunity. The wireless device monitors the PDCCH of the target PCell to receive the RAR corresponding to the preamble. The wireless device receives the RAR including the preamble index and / or the TA command. The wireless device completes the CFRA procedure. The CFRA procedure can be based on the above description of Figure 13BAfter completing the CFRA procedure, the wireless device may receive a beam indication (or TCI state indication) from the target PCell for PDCCH / PDSCH / CSI-RS reception and / or PUCCH / PUSCH / SRS transmission for the target PCell. The wireless device may apply the beam (or TCI state) to PDCCH / PDSCH / CSI-RS reception and / or PUCCH / PUSCH / SRS transmission for the target PCell.

[0391] In the prior art, after receiving a HO command (e.g., an RRC reconfiguration with a ReconfigurationWithSync IE), the wireless device performs downlink synchronization and uplink synchronization, and beam alignment / management via the target PCell. Performing downlink synchronization, uplink synchronization, and / or beam alignment can be time-consuming.

[0392] In order to reduce the HO delay, especially the delay introduced by uplink synchronization, an early TA acquisition scheme is proposed.

[0393] Figure 39 An example of a HO procedure based on early TA acquisition (or ETA) is shown.

[0394] In the example, Figure 39 As shown, the network (e.g., base station, source gNB) may configure the wireless device to perform (layer 3) measurement reports (possibly including configuration of measurement gaps) for multiple neighboring cells (e.g., cell 1 from candidate target gNB 1, cell 2 from candidate target gNB 2, etc.). The measurement reports are layer 3 reports, distinct from layer 1 CSI reports. The wireless device may transmit (in an RRC message) one or more layer 3 measurement reports to the source gNB (or source PCell, i.e., Figure 39 Cell 0 in ).

[0395] like Figure 39 As shown, based on one or more measurement reports from the wireless device, the source gNB may provide the target gNB with a list of best cells for each frequency for which measurement information is available, for example, in order of decreasing RSRP. The source gNB may also include available measurement information for the cells provided in the list. The target gNB may decide which cells to configure for use after the HO (as target PCell and / or one or more SCells), which may include cells other than the cells indicated by the source gNB.

[0396] In an example, the source gNB may transmit a HO request to the target gNB ( Figure 39(not shown). The target gNB may respond with a HO message. In an example, in the HO message, the target gNB may indicate the access stratum configuration in the target cell to be used for the wireless device (e.g., the RRC configuration of the target cell).

[0397] In an example, the source gNB may configure the candidate PCell (cell 1, cell 2, etc.) by sending an RRC reconfiguration message to the source gNB (e.g., configuration of the candidate PCell (cell 1, cell 2, etc.), such as Figure 39 ) includes a layer 1 / 2 candidate PCell configuration message (eg, a newly defined candidates-L1L2-ConfigIE) to configure a HO procedure different from the normal layer 3-based HO procedure (eg, Figure 32 、 Figure 33 and / or Figure 34 ) and / or CHO procedures (e.g., as Figure 35 and / or Figure 36 HO (PCell handover / change, mobility, Layer 1 / 2 triggered mobility, LTM, etc.) procedures based on Layer 1 / 2 signaling (as shown). In the case where the HO based on Layer 1 / 2 signaling is triggered by Layer 1 / 2 signaling and performs a handover to a candidate target PCell, the Layer 1 / 2 candidate PCell configuration message may include a list of candidate target PCells, each of which is associated with a dedicated RACH resource for the RA procedure. There are multiple options for parameter configuration of the candidate target PCell.

[0398] In an example, as a first option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message transmitted from the source gNB may include the (encapsulated) RRC reconfiguration message of the candidate target gNB (e.g., RRCReconfiguration) received by the source gNB from the candidate target gNB via the X2 / Xn interface. The (encapsulated) RRC reconfiguration message of the candidate target gNB may reuse the same signaling structure of the RRC reconfiguration message of the source gNB, such as Figure 33 and / or Figure 34 shown.

[0399] In the example, as a second option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message transmitted from the source gNB may include the (encapsulated) cell group configuration message (e.g., CellGroupConfig) of the candidate target gNB received by the source gNB from the candidate target gNB via the X2 / Xn interface. The (encapsulated) cell group configuration message of the candidate target gNB may reuse the same signaling structure of the cell group configuration message of the source gNB, such as Figure 33 and / or Figure 34Compared with the first option, the second option can reduce the signaling overhead of parameter configuration of the candidate target PCell.

[0400] In an example, as a third option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message transmitted from the source gNB may include the (encapsulated) SpCell configuration message (e.g., SpCellConfig) of the candidate target gNB received by the source gNB from the candidate target gNB via the X2 / Xn interface. The (encapsulated) SpCell configuration message of the candidate target gNB may reuse the same signaling structure of the SpCell configuration message of the source gNB, such as Figure 33 and / or Figure 34 Compared with the second option, the third option can reduce the signaling overhead of parameter configuration of the candidate target PCell.

[0401] In an example, for each candidate target PCell, the source gNB may indicate cell-common and / or UE-specific parameters (e.g., SSB / CSI-RS, BWP, RACH resources, PDCCH / PDSCH / PUCCH / PUSCH resources, etc.) in the RRC reconfiguration message.

[0402] In an example, cell 0, cell 1, and / or cell 2 may belong to the same gNB-DU, in which case cell 1 and / or cell 2 may be configured as part of cell 0 serving as a cell. The radio resources (PDCCH, PDSCH, etc.) of cell 0 are shared with cell 1 and / or cell 2. Cell 1 and / or cell 2 may be configured based on, for example, Figure 38 The gNB-DU may transmit an SSB different from the SSB transmitted via Cell 0 based on the above Figure 1A and / or Figure 1B The example embodiments described may be implemented.

[0403] In an example, cell 0, cell 1, and / or cell 2 may belong to different gNB-DUs (which are associated with the same gNB-CU or associated with different gNB-CUs), in which case cell 1 and / or cell 2 may be configured as cells separate from cell 0 (non-serving cells). The radio resources (PDCCH, PDSCH, etc.) of cell 0 are not shared with cell 1 and / or cell 2. Cell 1 and / or cell 2 may, for example, be based on Figure 38 The gNB-DU and / or gNB-CU may transmit an SSB different from the SSB transmitted via Cell 0 based on the above Figure 1A and / or Figure 1B The example embodiments described may be implemented.

[0404] exist Figure 39In an example, the wireless device may perform layer 1 / 2 measurement reporting (CSI / beam) for the candidate target PCell list and / or the current PCell. The layer 1 / 2 measurement report may include layer 1 RSRP, layer 1 RSRQ, PMI, RI, layer 1 SINR, CQI, etc., which is different from the L3 measurement shown above. To facilitate the wireless device to perform L1 / 2 measurements, the base station may transmit an RRC configuration message that includes configuration parameters for L1 / 2 measurements of one or more candidate cells. The one or more candidate cells may be a subset of the multiple candidate cells for which the wireless device reports L3 measurements to the base station.

[0405] In an example, the RRC configuration message including the configuration parameters for L1 / 2 measurement of one or more candidate cells may be the same as the RRC message for L3 measurement configuration, or the same as the RRC configuration message for candidate PCell configuration as shown above.

[0406] In an example, the RRC configuration message including the configuration parameters for L1 / 2 measurement of one or more candidate cells may be separate and / or independent from the RRC configuration message for the candidate PCell configuration as shown above.

[0407] In an example, the RRC configuration message including the configuration parameters for L1 / 2 measurement may be sent to the configured serving cell (eg, Figure 39 The RRC message is the same as the RRC message of the cell 0 shown, and the RRC message includes the L1 / 2 measurement configuration of the serving cell.

[0408] In an example, the L1 / 2 measurement configuration of the serving cell may be based on Figure 40 、 Figure 41 and / or Figure 42The example embodiments are implemented in accordance with the embodiment of the present invention, which will be described later in the specification. In the example, the L1 / 2 measurement configuration of the serving cell may include multiple SSB resource sets (CSI-SSB-ResourceSet) for CSI (CQI / PMI / RI / L1-RSRP / L1-SINR, etc.) measurement. The CSI-SSB-ResourceSet is identified by a CSI-SSB-Resource set identifier (ID) and includes a list of SSB indexes, each SSB index is associated with a ServingAdditionalPCIIndex, and the ServingAdditionalPCIIndex indicates the physical cell ID of the SSB associated with the ServingAdditionalPCIInex in multiple SSBs. If the value of ServingAdditionalPCIIndex is zero, the PCI of the SSB index is the PCI of the serving cell (e.g., cell 0). If the value of ServingAdditionalPCIIndex is not zero, ServingAdditionalPCIIndex indicates the additionalPCIIndex of the SSB-MTC-AdditionalPCI configured using additionalPCI-ToAddModList in ServingCellConfig, and the PCI is the additionalPCI in SSB-MTC-AdditionalPCI (e.g., PCI of cell 1, PCI of cell 2, etc.). The PCI of a cell is a cell identifier that uniquely identifies a cell in a wireless communication system. In an example, the CSI-SSB-Resourceset of cell 0 may indicate SSB 0 from cell 0, SSB 1 from cell 1, SSB 2 from cell 2, and so on.

[0409] In an example, based on the L1 / 2 measurement configuration of the serving cell (cell 0), the wireless device may measure the CSI (e.g., CQI / PMI / L1-RSRP / L1-RSRQ / L1-SINR) of each of the SSBs configured in the CSI-SSB-ResourceSet of cell 0, where each SSB may be from a different cell (or a different PCI). In an example, if the CSI-SSB-Resourceset of cell 0 indicates SSB 0 from cell 0, SSB 1 from cell 1, SSB 2 from cell 2, etc., the wireless device may measure SSB 0 from cell 0, SSB 1 from cell 1, and SSB 2 from cell 2 for the L1 / 2 CSI / beam measurement of the LTM procedure. The wireless device may measure the CSI (e.g., CQI / PMI / L1-RSRP / L1-RSRQ / L1-SINR) of each of the SSBs configured in the CSI-SSB-ResourceSet of cell 0, where each SSB may be from a different cell (or a different PCI). In an example, if the CSI-SSB-Resourceset of cell 0 indicates SSB 0 from cell 0, SSB 1 from cell 1, SSB 2 from cell 2, etc., the wireless device may measure SSB 0 from cell 0, SSB 1 from cell 1, and SSB 2 from cell 2 for the L1 / 2 CSI / beam measurement of the LTM procedure. Figure 43 、 Figure 44A and / or Figure 44B An example embodiment of the present invention is used to measure CSI.

[0410] In an example, the wireless device may trigger a layer 1 / 2 measurement report based on the measured CSI of each of the SSBs configured in the CSI-SSB-ResourceSet of cell 0. Triggering the layer 1 / 2 measurement report may be based on a trigger indication from the base station and / or a trigger event occurring at the wireless device.

[0411] In an example, a layer 1 / 2 measurement report may be triggered by a measurement event, for example, when the measurement of the CSI of a candidate target PCell (e.g., cell 1, cell 2, etc.) is greater than a threshold or (offset) greater than the current PCell (cell 0), etc.

[0412] In an example, a layer 1 / 2 measurement report may be triggered by receiving a trigger indication (e.g., DCI or MAC CE) indicating reporting layer 1 / 2 measurements of one or more candidate target PCells (e.g., cell 1, cell 2, etc.). In response to receiving the trigger indication, the wireless device may (after performing L1 / 2 measurements) transmit a layer 1 / 2 measurement report indicating whether at least one candidate target PCell has a better CSI measurement than the current PCell. In response to no candidate target PCell having a better CSI measurement than the current PCell after receiving the trigger indication, the wireless device may skip transmitting the layer 1 / 2 measurements of the candidate target PCells (cell 1, cell 2, etc.), or may only transmit the layer 1 / 2 CSI measurement of the serving cell (cell 0).

[0413] In an example, layer 1 / 2 measurement reports may be transmitted with a periodicity configured by the source gNB.

[0414] In an example, layer 1 / 2 measurement reports may be included in the UCI via PUCCH / PUSCH or MAC CE (eg, event triggered, associated with a configured SR for MAC CE transmission).

[0415] In this specification, layer 1 / 2 measurement and / or reporting of a candidate target PCell before actually switching to the candidate target PCell as the serving PCell may be referred to as early CSI reporting of the candidate target PCell, which is different from CSI reporting of the serving PCell. Early CSI reporting of the candidate target PCell before the wireless device performs a layer 1 / 2 triggered mobility procedure to switch to the candidate target PCell as the serving PCell may enable the base station to obtain correct beam information, for example, where when the wireless device later switches to the candidate target PCell as the serving PCell, the SSB may be used as a beam reference for downlink transmission for the candidate target PCell without waiting for beam management after the switch, thereby improving the (handover) latency of the PCell switch.

[0416] exist Figure 39 In the example of , the wireless device may determine that cell 1 has better channel quality (L1-RSRP / L1-SINR / L1-RSRQ, etc.) than cell 0. The wireless device may transmit a layer 1 / 2 measurement report indicating that cell 1 has better channel quality than cell 0.

[0417] In an example, the source base station and / or the target base station may determine which cell to use as the target PCell. Upon receiving the layer 1 / 2 measurement report, the source base station may coordinate with the candidate target base station as to whether cell 1 may be used as a candidate target PCell for future HO.

[0418] exist Figure 39 In the example of FIG, when determining that cell 1 is used as the target PCell for future HO, the source base station (e.g., upon request of the target base station if time alignment has not been previously obtained for cell 1) may transmit from cell 0 (or an activated SCell of the wireless device) a first layer 1 / 2 (first L1 / 2) command (e.g., a DCI / MACCE / RRC message including a PDCCH command, such as FIG) triggering a preamble transmission (RACH, or other uplink signals such as SRS) to cell 1. Figure 39 In the prior art, DCI may be based on a PDCCH command.

[0419] exist Figure 39 In the example of FIG. 1 , the wireless device may send the preamble (or Figure 39 The target base station may monitor the PRACH opportunity for receiving the preamble after the wireless device switches the PCell from cell 0 to cell 1 to estimate the TA for future uplink transmissions from the wireless device.

[0420] exist Figure 39In the example of , the target base station may forward the estimated TA of cell 1 to the source base station.

[0421] exist Figure 39 In the example of , the source base station may transmit the forwarded TA to the wireless device, for example, via a RAR message or via a TAC MA CE. In this case, the wireless device may transmit the forwarded TA to the wireless device based on existing technology (e.g., based on the above description of Figure 13A 、 Figure 13B and / or Figure 13C The wireless device may monitor the PDCCH (on cell 0) for receiving the RAR message (e.g., the example embodiment described). The wireless device may maintain the TAT of the TAG associated with cell 1. The wireless device may maintain cell 1 as a non-serving cell. The TAC MAC CE may indicate (e.g., one or more bit fields of the MAC CE) whether the TAC is for the serving cell (or a TAG associated with the serving cell) or for the non-serving cell (e.g., cell 1).

[0422] In this example, the source base station may skip transmitting the forwarded TA to the wireless device. Alternatively, the source base station may indicate the TA and a Layer 2 1 / 2 command indicating / triggering a PCell handover from cell 0 to cell 1. In this case, the wireless device may skip monitoring the PDCCH (on cell 0) for receiving RAR messages.

[0423] exist Figure 39 In the example of the present invention, the transmission of a preamble to a candidate target PCell before receiving a (P)Cell handover command (including or excluding a TA estimated by the target base station for the target PCell) indicating handover of the PCell to the target PCell is referred to as an early TA acquisition (ETA) procedure / process / feature / scheme in this specification. By implementing ETA, before the wireless device performs HO, the target base station can obtain the TA to be used by the wireless device after performing HO to the target PCell. The TA of the target PCell can be transmitted in the RAR or combined with the L1 / 2 (or L1 / L2) command indicating the PCell handover. The ETA procedure can reduce the delay in uplink synchronization with the target PCell after performing the HO procedure (or PCell handover procedure).

[0424] exist Figure 39 In the example of FIG. 1 , the wireless device may receive a second L1 / 2 command (eg, MAC CE, such as FIG. 2 ) indicating a PCell handover from cell 0 to cell 1. Figure 39As shown). For example, if the TA is not received before receiving the second L1 / 2 command, the second L1 / 2 command may further indicate the TA (forwarded from the target base station to the source base station and used for the target PCell in the future). The second L1 / 2 command may further indicate beam information (TCI state and / or SSB index, which can be obtained in the early CSI report as described above) to be used for downlink reception and / or uplink transmission on cell 1. In response to receiving the second L1 / 2 command, the wireless device may switch the PCell from cell 0 to cell 1 and transmit PUSCH / PUCCH via cell 1 based on the TA. The wireless device may receive downlink signals and transmit uplink signals based on the indicated beam information. Switching the PCell from cell 0 to cell 1 may include at least one of: applying the RRC configuration parameters of cell 1, stopping applying the RRC configuration parameters of cell 0, resetting / reconfiguring the MAC entity, receiving RRC messages / MIB / SSB / SIB / PDCCH / PDSCH from cell 1, and stopping receiving RRC messages / MIB / SSB / SIB / PDCCH / PDSCH from cell 0.

[0425] In the example, based on the above Figure 39 In the described example embodiments, the PCell switching procedure based on L1 / 2 commands (eg, combined with early CSI reporting and / or ETA procedures) may be referred to as an L1 / 2 triggered mobility (LTM) procedure.

[0426] Figure 40 、 Figure 41 and Figure 42 An example of an RRC message for layer 1 / 2 CSI measurement and / or reporting configuration is shown. In the example, the base station may transmit an RRC message of the serving cell to the wireless device (e.g., Figure 40The RRC message includes configuration parameters for layer 1 / 2 measurements (e.g., csi-MeasConfig IE) and configuration parameters for layer 3 measurements (e.g., serviceCellMO IE). The csi-MeasConfig IE may indicate a non-zero power CSI-RS resource list (e.g., nzp-CSI-RS-ResourceToAddModList), a non-zero power CSI-RS resource set list (e.g., nzp-CSI-RS-ResourceSetToAddModList), an SSB resource set list (e.g., csi-SSB-ResourceSetToAddList), a CSI resource configuration list (e.g., csi-ResourceConfigToAddList), a CSI report configuration list (e.g., csi-ReportConfigToAddList), etc. The non-zero power CSI resource (e.g., NZP-CSI-RS-Resource) is identified by NZP-CSI-RS-ResourceId and is configured with periodicity and offset parameters (CSI-ResourcePeriodicityAndOffset) and QCL configuration (e.g., TCI-stateId). The CSI-RS resource can be based on the above Figure 11B The non-zero power CSI resource set is identified by NZP-CSI-RS-ResourceSetId and includes a list of non-zero power CSI-RS resources.

[0427] like Figure 41As shown, the csi-SSB-ResourceSet is identified by CSI-SSB-ResourceSetId and includes a list of SSB indices, each SSB index being associated with a corresponding ServingAdditionalPCIIndex of an additional PCI list (servingAdditionalPCIList). The serviceAdditionalPCIList indicates the physical cell ID (PCI) of the SSB in the csi-SSB-ResourceList. If the serviceAdditionalPCIList exists in the csi-SSB-ResourceSet, the list has the same number of entries as the csi-SSB-ResourceList. The first entry in the list indicates the value of the PCI of the first entry of the csi-SSB-ResourceList, the second entry in this list indicates the value of the PCI of the second entry of the csi-SSB-ResourceList, and so on. In the example, for each entry of serviceAdditionalPCIList, if the value is zero, the PCI is the PCI of the serving cell in which this CSI-SSB-ResourceSet is defined, otherwise, the value is the value of additionalPCIIndex-r17 of SSB-MTC-AdditionalPCI-r17 configured using additionalPCI-ToAddModList-r17 in ServingCellConfig, and the PCI is the additionalPCI-r17 in this SSB-MTC-AdditionalPCI-r17.

[0428] like Figure 41As shown, based on the NZP-CSI-RS-ResourceSet list and the csi-SSB-ResourceSet list, the base station can configure a CSI-RS resource set list (csi-RS-ResourceSetList) for each CSI resource configuration (CSI-ResourceConfigId) identified by CSI-ResourceConfigId, which includes a non-zero power CSI-RS resource set list (nzp-CS-RS-ResourceSetList) and / or a csi-SSB-ResourceSet list (csi-SSB-ResourceSetList) for CSI measurement, or includes a csi-IM-Resource set list (csi-IM-ResourceSetList) for interference measurement. Each CSI resource of the CSI resource configuration is located in the DL BWP identified by the higher layer parameter BWP-id of the CSI resource configuration, and all CSI resource lists linked to the CSI report setting have the same DL BWP.

[0429] like Figure 42 As shown, based on the above Figure 40 and / or Figure 41 For the CSI resource configuration described in the specification, the base station may configure, for each CSI reporting configuration (CSI-ReportConfig) identified by a CSI reporting configuration identifier (e.g., CSI-ReportConfigId), the following: a serving cell index indicating in which serving cell the CSI-ResourceConfig will be found (if the field does not exist, the resources are on the same serving cell as this reporting configuration); a CSI-ResourceConfigId indicating the CSI resources used for channel measurement; a report type indication indicating whether the CSI report is periodic, semi-persistent CSI reporting on the PUCCH, semi-persistent CSI reporting on the PUSCH, or aperiodic; a report quantity indication indicating the number of reports (e.g., CRI-RSRP, SSB-index-RSRP, etc.) (where SSB-index-RSRP is referred to as Layer 1 RSRP (L1-RSRP) in this specification); a time domain restriction indication for channel measurement (timeRestrictionForChannelMeasurements), etc. Semi-persistent CSI reporting on the PUCCH may be triggered by an SP CSI activation / deactivation MAC CE. Semi-persistent CSI reporting on PUSCH may be triggered by a DCI whose CRC is scrambled by SP-CSI-RNTI. Aperiodic CSI reporting may be indicated by a DCI that schedules PUSCH transmission and includes an aperiodic CSI request field.

[0430] Based on Figure 40 、 Figure 41 and / or Figure 42 If the wireless device configures CSI measurement and reporting through RRC messages, the wireless device can measure and transmit CSI reports. For beam measurements, the wireless device can transmit L1-RSRP reports.

[0431] In an example, when resource-wise quasi-co-located with 'Type C' and 'Type D' (if applicable), the wireless device may (eg, based on the above description of Figure 40 、 Figure 41 and / or Figure 42 In the example embodiments described herein, the wireless device may be configured with CSI-RS resources, SS / PBCH block resources, or both CSI-RS and SS / PBCH block resources. In this example, the wireless device may be configured with a CSI-RS resource configuration of up to 16 CSI-RS resource sets, each with up to 64 resources. The total number of different CSI-RS resources across all resource sets does not exceed 128.

[0432] In an example, for L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with a step size of 1 dB. If the higher layer parameter nrofReportedRS is configured to be greater than one, or if the higher layer parameter groupBasedBeamReporting is configured to 'enabled', or if the higher layer parameter groupBasedBeamReporting-r17 is configured, the wireless device uses differential L1-RSRP based reporting, where the maximum measured L1-RSRP value is quantized to a 7-bit value in the range [-140, -44] dBm with a step size of 1 dB, and the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is calculated with a 2 dB step size with reference to the maximum measured L1-RSRP value as part of the same L1-RSRP reporting instance.

[0433] In an example, when the higher layer parameter groupBasedBeamReporting-r17 in CSI-ReportConfig is configured, the wireless device indicates the CSI resource set associated with the maximum measured value of L1-RSRP, and for each group, the CRI or SSBRI of the indicated CSI resource set is present first.

[0434] In an example, if the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "not configured", the wireless device can derive channel measurements for calculating the L1-RSRP value reported in uplink time slot n based only on the SS / PBCH or NZP CSI-RS associated with the CSI resource configuration that is not later than the CSI reference resource. Figure 43 The example embodiments of the present invention are used to define and implement CSI reference resources.

[0435] In an example, if the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the wireless device may derive channel measurements for calculating the L1-RSRP reported in uplink time slot n based only on the latest timing of the SS / PBCH or NZP CSI-RS associated with the CSI resource setting that is no later than the latest timing of the CSI reference resource.

[0436] In an example, when the wireless device is configured with SSB-MTC-AdditionalPCI, the CSI-SSB-ResourceSet configured for L1-RSRP reporting contains a set of SSB indices and a set of PCI indices, where each SSB index is associated with a PCI index, as described above with respect to Figure 41 shown.

[0437] In an example, when the wireless device is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RSRP-Capability[Set]Index' or 'ssb-Index-RSRP-Capability[Set]Index', a wireless device capability value set index indicating the maximum supported number of SRS antenna ports is reported together with a pair of SSBRI / CRI and L1-RSRP.

[0438] Figure 43 An example of a CSI report (eg, L1-RSRP report) of a serving cell is shown. In the example, the base station may transmit (eg, at T0) a DCI to the wireless device indicating / triggering the L1-RSRP report of the serving cell.

[0439] In an example, the DCI may indicate aperiodic CSI reporting including L1-RSRP reporting via PUSCH resources.

[0440] In an example, DCI may trigger a semi-persistent CSI report (SP CSI report) including a L1-RSRP report of a serving cell via a PUSCH resource. The SP CSI report may be periodically transmitted by the wireless device based on the periodicity of the SP CSI report configuration.

[0441] In an example, the DCI may include a trigger indication of an aperiodic CSI-RS (AP-CSI-RS) for L1-RSRP reporting. In response to receiving the trigger indication of the AP-CSI-RS, the wireless device may measure the AP-CSI-RS for L1-RSRP reporting.

[0442] In an example, L1-RSRP reporting may be measured based on periodic CSI-RS or SSB.

[0443] In the example, based on the above Figure 40 、 Figure 41 and / or Figure 42 Example embodiments are described to configure L1-RSRP reporting.

[0444] like Figure 43 As shown, the base station may transmit CSI-RS and / or SSB for CSI reporting, for example, transmitting the 1st CSI-RS / SSB at T1, ..., transmitting the kth CSI-RS / SSB at T2, transmitting the (k+1)th CSI-RS / SSB at T4, and so on. In this example, the wireless device may determine the CSI reference resource (n) of the serving cell for the L1-RSRP report to be transmitted at T5. CSI_ref , which is T3, such as Figure 43 shown).

[0445] In an example, if the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to “notConfigured”, the wireless device only reports the measurement results based on the CSI reference resource (n) associated with the CSI resource setting. CSI_ref , which is T3, such as Figure 43 ) SS / PBCH or NZP CSI-RS (e.g., the 1st CSI-RS / SSB at T1, ..., the Kth CSI-RS / SSB at T2, as shown) Figure 43 ) to derive the channel measurements used to calculate the L1-RSRP value reported in uplink time slot n (e.g., at T5).

[0446] In an example, if the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the wireless device only reports the measurement results based on the SS / PBCH or NZP CSI-RS associated with the CSI resource setting no later than the CSI reference resource (n CSI_ref , which is T3, such as Figure 43 The latest (e.g., the Kth CSI-RS / SSB at T2, as shown) Figure 43 The channel measurement used to calculate the L1-RSRP reported in uplink time slot n (e.g., at T5) is derived at the timing shown in FIG.

[0447] In this example, the CSI reference resource (n CSI_ref , which is T3, such as Figure 43 ) is defined in the frequency domain by a group of downlink physical resource blocks (PRBs) corresponding to the frequency band to which the derived CSI is related.

[0448] In an example, in the time domain, for uplink time slot n' (eg, Figure 43 CSI reference resource (n) for CSI report in T5) CSI_ref , which is T3, such as Figure 43 shown) consists of a single downlink time slot Definition, where K offset is a parameter configured by higher layers (e.g., as specified in clause 4.2 of 3GPP TS 38.213), and where is K with a value of 0 in frequency range 1 offset subcarrier spacing configuration.

[0449] In the example, And μ DL and μ UL are the subcarrier spacing configurations for DL ​​and UL, respectively, and and μ offset Determined by the configured ca-SlotOffset of the higher layers of the cell transmitting uplink and downlink.

[0450] In an example, for periodic and semi-persistent CSI reporting, if a single CSI-RS / SSB resource is configured for channel measurement, then n CSI_ref is greater than or equal to The minimum value of n such that it corresponds to a valid downlink time slot, or if multiple CSI-RS / SSB resources are configured for channel measurement, then n CSI_ref is greater than or equal to The minimum value of , so that it corresponds to a valid downlink time slot.

[0451] In an example, for aperiodic CSI reporting, if the DCI instructs the wireless device to report CSI in the same time slot as the CSI request, then n CSI_ref Make the reference resource and the corresponding CSI request in the same valid downlink time slot, otherwise, n CSI_ref is greater than or equal to The minimum value of time slot nn CSI_ref corresponds to the valid downlink time slot, where Z' corresponds to the time slot that will be Figure 44A and Figure 44B The latency requirements are described later in .

[0452] In an example, when periodic or semi-persistent CSI-RS / CSI-IM or SSB is used for channel / interference measurement, the wireless device is not expected to measure the channel / interference on the CSI-RS / CSI-IM / SSB whose last OFDM symbol is not received until Z' symbols before the transmission time of the first OFDM symbol of the aperiodic CSI report.

[0453] In an example, a timeslot in a serving cell should be considered a valid downlink timeslot if the timeslot includes at least one higher layer configured downlink or flexible symbol and does not fall within a configured measurement gap for the wireless device.

[0454] In an example, if there is no valid downlink timeslot for CSI reference resources corresponding to the CSI reporting setting in the serving cell, CSI reporting is omitted for the serving cell in uplink timeslot n'.

[0455] In the example, after CSI reporting (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the wireless device reports a CSI report only after receiving at least one CSI-RS transmission opportunity for channel measurement and CSI-RS and / or CSI-IM opportunity for interference measurement no later than the CSI reference resource, otherwise the report is discarded.

[0456] In an example, when DRX is configured, the wireless device reports a CSI report only upon receiving at least one CSI-RS transmission opportunity for channel measurement and a CSI-RS and / or CSI-IM opportunity for interference measurement not later than a CSI reference resource in a DRX active time, and otherwise discards the report.

[0457] In an example, the wireless device may spend a non-zero amount of time performing CSI calculation to obtain / transmit a CSI report in response to receiving a DCI indicating / triggering a CSI report. The amount of time used for CSI calculation may be referred to as a CSI calculation time. The wireless device determines the CSI calculation time as follows: for example, when a CSI request field on a DCI triggers a CSI report on a PUSCH, if the first uplink symbol used to carry the corresponding CSI report including the timing advance effect is not earlier than the first uplink symbol at symbol Z. ref If the first uplink symbol used to carry the nth CSI report including the timing advance effect is not earlier than symbol Z' ref (n) starts, the wireless device provides a valid CSI report for the nth triggered report.

[0458] In the example, Z ref is defined as the next uplink symbol whose CP starts T after the end of the last symbol of the PDCCH that triggers the CSI report proc,CSI =(Z)(2048+144)·κ2 -μ ·T C +T switch .

[0459] In the example, when the aperiodic CSI-RS is used for channel measurement of the nth triggered CSI report, and at T switch is the receive antenna switching delay based on the wireless device capabilities (e.g., based on existing standardization in clause 6.4 of TS 38.214) and is calculated only at Z1CSI with delay requirement 1 (which will be Figure 44A When Z' ref (n) is defined as the next uplink symbol whose CP starts T′ after the end of the last symbol of the latest time of proc,CSI =(Z′)(2048+144)·κ2 -μ ·T C : Aperiodic CSI-RS resources for channel measurement, aperiodic CSI-IM for interference measurement, and aperiodic NZP CSI-RS for interference measurement.

[0460] In an example, if the PUSCH indicated by the DCI overlaps with another PUCCH or PUSCH, the CSI report (e.g., based on the procedures specified in clause 9.2.5 of TS 38.213 and clause 5.2.5 of TS 38.214) is multiplexed when applicable, otherwise the CSI report is transmitted on the PUSCH indicated by the DCI.

[0461] In the example, when the CSI request field on the DCI triggers a CSI report on the PUSCH, if the first uplink symbol used to carry the corresponding CSI report including the timing advance effect is earlier than the first uplink symbol at symbol Z ref Initially, the wireless device may ignore the scheduling DCI if no HARQ-ACK or transport blocks are multiplexed on the PUSCH.

[0462] In the example, when the CSI request field on the DCI triggers a CSI report on the PUSCH, if the first uplink symbol used to carry the nth CSI report including the timing advance effect is earlier than the first uplink symbol Z′ ref (n), then if the number of triggered reports is one and no HARQ-ACK or transport block is multiplexed on PUSCH, the wireless device may ignore the scheduling DCI, otherwise the wireless device does not need to update the CSI for the nth triggered CSI report.

[0463] In an example, when PDCCH reception contains two PDCCH candidates from two corresponding search space sets (eg, as described in clause 10.1 of TS 38.213), to determine the last symbol of the PDCCH triggering CSI reporting, the PDCCH candidate ending at the later time is used.

[0464] In the example, Z, Z' and μ are defined as: Z = max m＝0,…,M-1 (Z(m)) and Z′=max m＝0,…,M-1 (Z′(m)), where M is the number of updated CSI reports (e.g., according to clause 5.2.1.6 of TS 38.214), (Z(m), Z′(m)) corresponds to the mth updated CSI report and is defined as

[0465] - Figure 44A (Z1, Z1′), the condition is max{μ PDCCH ,μ CSI-RS ,μ UL}≤3, and the condition is that when L=0 CPUs are occupied (e.g., according to clause 5.2.1.6 of TS 38.214) and the CSI to be transmitted is a single CSI and corresponds to a wideband frequency granularity, the CSI is triggered with a transport block or HARQ-ACK or both without a CRI report, wherein the CSI corresponds to at most 4 CSI-RS ports in a single resource without a CRI report, and wherein CodebookType is set to 'typeI-SinglePanel', or wherein reportQuantity is set to 'cri-RI-CQI', or

[0466] - Figure 44B(Z1, Z1′), provided that the CSI to be transmitted corresponds to a wideband frequency granularity, wherein the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI reporting, and wherein CodebookType is set to 'typeI-SinglePanel', or wherein reportQuantity is set to 'cri-RI-CQI', or

[0467] - Figure 44B (Z1,Z1′), provided that the CSI to be transmitted corresponds to wideband frequency granularity, where reportQuantity is set to 'ssb-Index-SINR', 'cri-SINR', 'ssb-Index-SINR-Capability[Set]Index', or 'cri-SINR-Capability[Set]Index', or

[0468] - Figure 44B (Z3, Z3′), provided that reportQuantity is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP-Capability[Set]Index', or 'ssb-Index-RSRP-Capability[Set]Index', where Xμ is beamReportTiming according to the capabilities reported by the wireless device, and KB l According to the beamSwitchTiming capability reported by the wireless device (e.g., as defined in TS 38.306 and / or as described later), or

[0469] -otherwise, Figure 44B (Z2, Z2′).

[0470] - Figure 44A and Figure 44B μ corresponds to min(μ PDCCH ,μ CSI-RS ,μ UL ), where μ PDCCH corresponds to the subcarrier spacing of the PDCCH transmitting DCI, and μ UL corresponds to the subcarrier spacing of the PUSCH transmitting the CSI report, and μ CSI-RS Corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by DCI.

[0471] Figure 44A and Figure 44B Example latency requirements for CSI calculations are shown. Figure 44A The CSI calculation delay requirement 1 is shown. Figure 44BThe CSI calculation delay requirement 2 is shown. The wireless device can determine Figure 44A and Figure 44B Which one of them is used to calculate the delay based on the CSI of the embodiment described above.

[0472] In an example, Xμ (where μ is the SCS defined above) is reported according to the capability beamReportTiming reported by the wireless device. The reported beamReportingTiming indicates the number of OFDM symbols between the end of the last symbol of the SSB / CSI-RS and the start of the first symbol of the transport channel containing the beam report. The wireless device can report the value of beamReportingTiming for each SCS. In an example, in 3GPP Rel.17 standardization, the value of beamReportingTiming for a 15kHz SCS can be one of 2, 4, and 8. The value of beamReportingTiming for a 30kHz SCS can be one of 4, 8, 14, and 28. The value of beamReportingTiming for a 60kHz SCS can be one of 8, 14, and 28. The value of beamReportingTiming for a 120kHz SCS can be one of 14, 28, and 56. The wireless device provides the capability to provide a report on the frequency band number in which the measurement was performed. The wireless device includes this field for each supported subcarrier spacing.

[0473] In the example, KB l According to the beamSwitchTiming capability reported by the wireless device. The beamSwitchTiming capability reported by the wireless device indicates the minimum number of OFDM symbols between the DCI trigger for aperiodic CSI-RS and the aperiodic CSI-RS transmission. The number of OFDM symbols is measured from the end of the last symbol containing the indication to the beginning of the first symbol for CSI-RS. The wireless device includes this field for each supported subcarrier spacing. The value of beamSwitchTiming (sym224 or sym336 for 60kHz and 120kHz SCS with l=1, sym896 or sym1344 for 480kHz SCS with l=3, and sym1792 or sym2688 for 960kHz SCS with l=4) can be used to determine the wireless device expectations / behavior for aperiodic CSI-RS for tracking and the latency requirement for L1-RSRP reporting, while the wireless device behavior / assumptions before or after beam switch timing are not specified for measuring AP CSI-RS for CSI acquisition (without trs-Info and without repetition) and for beam management (with repetition 'off').

[0474] In an example, in 3GPP NR Release 17 (Rel. 17 or R17), L1 CSI reporting of inter-cell multiple TRPs is supported and specified by configuring SSB / CSI-RS with an additional PCI different from the PCI of the serving cell and configuring the CSI reporting associated with the SSB / CSI-RS of the serving cell (e.g., as Figure 31B and / or Figure 41 As shown). The L1 CSI reporting for inter-cell multi-TRP specified in 3GPP NR Rel.17 has restrictions, including: the SSBs of the (non-serving) cell with a different PCI from the serving cell are completely contained in the active BWP or are associated with the initial downlink BWP of the wireless device; the SSBs of the (non-serving) cell with a different PCI from the serving cell have the same SCS and center frequency in the frequency domain as the SSBs of the serving cell; and in the time domain: the SSBs of the (non-serving) cell with a different PCI from the serving cell have the same sfn-SSB-Offset in the time domain; the timing difference between the SSBs of the serving cell and the (non-serving) cell with a different PCI arriving at the wireless device is less than the CP length of the corresponding SCS; and the wireless device has sent a valid L3 measurement report within the past 5 seconds. Otherwise, in 3GPP NR Rel.17, the wireless device and / or base station does not support L1-RSRP measurement of the (non-serving) cell with a different PCI from the serving cell.

[0475] In the example, the features of L3 beam / cell measurement, inter-frequency measurement and intra-frequency measurement supported in 3GPP NR Rel.15-17 are as follows: wherein the intra-frequency measurement needs to indicate the center frequency of the SSB of the serving cell used for measurement, and the center frequency of the SSB of the non-serving cell is the same, and the subcarrier spacing of the two SSBs is also the same, otherwise, the measurement is classified as inter-frequency measurement (for example, as specified in TS38.133 Section 9.3). Intra-frequency and inter-frequency measurements based on CSI-RS are defined in Sections 9.10.2 and 9.10.3 of TS38.133, similar to SSB-based measurements.

[0476] In an example, for inter-frequency L3 measurements, the wireless device may be configured with measurement gaps for measuring non-serving cells or candidate target cells.

[0477] In an example, the wireless device may transmit a wireless device capability parameter (e.g., interFrequencyMeas-NoGap-r16) to the base station, indicating whether the wireless device can perform frequency SSB-based measurements without measurement gaps if the SSB is fully contained within the wireless device's active BWP (e.g., as specified in TS 38.133). If this parameter is indicated differently for FR1 and FR2, each indication corresponds to a frequency range of the cell to be measured.

[0478] In an example, for intra-frequency L3 measurement, the wireless device may measure a non-serving cell or a target cell without applying a measurement gap.

[0479] In the example, for 3GPP Rel.18 LTM, the early CSI report of the candidate cell and the serving cell can be regarded as an inter-frequency measurement, which is different from the measurement based on the inter-cell multi-TRP of 3GPP Rel.17. The serving cell and the non-serving cell defined for the inter-cell multi-TRP of 3GPP Rel.17 can belong to the same DU (as described above for Figure 31B (as illustrated in FIG5 ), which is referred to as intra-DU inter-cell deployment. However, the serving cell and non-serving cell defined for 3GPP Rel. 18 LTM may belong to the same DU (which may be considered as intra-frequency deployment), or may not belong to the same DU, which is referred to as inter-DU inter-cell deployment (which may be considered as inter-frequency deployment). In the example, scenarios not included in the intra-frequency of 3GPP Rel. 18 LTM ar...

Claims

1. A method comprising: A configuration parameter for triggering a Layer 1 / 2 mobility LTM procedure is received by a wireless device, wherein the configuration parameter indicates: Synchronization symbol block SSB of the candidate cell; and A measurement window for measuring the channel state information (CSI) report of the candidate cell; receiving, via a serving cell, downlink control information (DCI), the DCI indicating uplink transmission of a CSI report of the candidate cell in a first time slot; determining, based on beam reporting timing associated with the LTM procedure, a symbol preceding the first time slot for the CSI report of the candidate cell; as well as The CSI report of a first one of the SSBs of the candidate cell is transmitted via the serving cell in the first time slot, wherein the first SSB measured for the CSI report is received under the following circumstances: not later than the said symbol; and within the measurement window.

2. A method comprising: receiving, by the wireless device via the first cell, a command indicating uplink transmission in a first time slot of channel state information (CSI) reports of one or more candidate cells for a layer 1 / 2 triggered mobility (LTM) procedure; For receiving a reference signal RS for the CSI report, determining a symbol before the first time slot based on beam reporting timing; as well as The CSI report measured on a first RS of the one or more candidate cells is transmitted in the first time slot and via the first cell, wherein the first RS is received no later than the symbol and within a measurement window. 3 . The method according to claim 2 , wherein the measurement window is a layer 1 measurement gap indicating a minimum number of Orthogonal Frequency Division Multiplexing (OFDM) symbols for performing the CSI reporting.

4. The method according to any one of claims 2 to 3, wherein the command comprises at least one of the following: Downlink Control Information DCI; and Media Access Control Element MAC CE.

5. The method according to any one of claims 2 to 4, wherein the RS comprises at least one of the following: Synchronization Signal Block SSB; and Channel State Information Reference Signal CSI-RS.

6. The method according to any one of claims 2 to 5, wherein the CSI report comprises at least one of the following: Layer 1 reference signal received power L1-RSRP; an indication of a first one of the RSs; and An indication of a second cell among the one or more candidate cells, wherein the L1-RSRP is measured on the first RS of the second cell.

7. The method according to any one of claims 2 to 6, wherein the CSI reports of the one or more candidate cells are inter-frequency measurements compared to the first cell.

8. The method according to any one of claims 2 to 7, wherein: Frequency resources of the RS of the one or more candidate cells: is not covered by any active bandwidth portion (BWP) of a primary cell (PCell) and a secondary cell (SCell) configured for the wireless device, and is covered by at least one configured BWP of the PCell and the SCell configured for the wireless device; or is not covered by any configured BWP of the PCell and the SCell; and The first cell is one of the PCell and the SCell.

9. The method according to any one of claims 2 to 8, further comprising receiving one or more radio resource control (RRC) messages including configuration parameters of the first cell and the one or more candidate cells, wherein the first cell is different from any of the one or more candidate cells.

10. The method according to claim 9, wherein: The configuration parameter of the first cell indicates a plurality of CSI resources for the CSI report; and The plurality of CSI resources include at least one of the following: a first CSI resource associated with a first physical cell identifier (PCI) index indicating the first cell; as well as A second CSI resource is associated with a second PCI index different from the first PCI index and indicating one of the one or more candidate cells.

11. The method according to claim 10, wherein: For each CSI resource in the multiple CSI resources, the configuration parameter of the first cell indicates: frequency resources; Periodicity in the time domain; as well as Transmit power; and Each of the multiple CSI resources includes at least one SSB or CSI-RS.

12. The method according to any one of claims 2 to 11, further comprising receiving the first RS of the one or more candidate cells for the CSI report via the one or more candidate cells, wherein the first RS is received in the following circumstances: not later than the said symbol; and within the measurement window.

13. The method according to any one of claims 2 to 12, further comprising not receiving a second RS in the one or more candidate cells for the CSI report via the one or more candidate cells, wherein a time resource of the second RS occurs in the following circumstances: after the symbol; or Outside the measurement window.

14. The method according to any one of claims 2 to 13, wherein in response to receiving a second RS of the one or more candidate cells in the following case, the CSI report of the one or more candidate cells is not based on the second RS: After the symbol; and Outside the measurement window.

15. The method according to any one of claims 2 to 14, further comprising transmitting, by the wireless device, one or more radio resource control (RRC) messages including a wireless device capability parameter indicating the beam reporting timing.

16. A method according to claim 15, wherein the beam reporting timing indicates the number of orthogonal frequency division multiplexing (OFDM) symbols between the end of the symbol of the first RS of the one or more candidate cells and the start of the first symbol of the first time slot in which the CSI report is transmitted via the first cell.

17. The method according to any one of claims 15 to 16, wherein the one or more RRC messages further include a second beam reporting timing different from the beam reporting timing.

18. The method according to any one of claims 17, wherein the second beam reporting timing indicates the number of OFDM symbols between the end of the symbol of the RS of the first cell and the start of the first symbol of the first time slot in which the CSI report is transmitted via the first cell.

19. The method of any one of claims 2 to 18, further comprising transmitting, by the wireless device, one or more RRC messages including a wireless device capability parameter indicating the measurement window.

20. The method of claim 19, wherein the measurement window indicates a number of time slots or symbols during which the wireless device: performing measurements on the one or more candidate cells for the CSI report; and Receiving downlink signals and transmitting uplink signals via the first cell are stopped.

21. The method according to any one of claims 2 to 20, further comprising receiving an indication of the measurement window from a base station, wherein the indication indicates at least one of the following: a time offset of a starting position of the measurement window; the periodicity of the measurement window; and The length of the measurement window.

22. The method of claim 21, wherein the time offset indicates the number of symbols or slots between a starting slot of a radio frame and the starting position of the measurement window.

23. The method according to any one of claims 21 to 22, wherein the time offset indicates the number of symbols or time slots between: a symbol of the second time slot on which the command is received; and The starting position of the measurement window.

24. The method according to any one of claims 21 to 23, wherein the indication is comprised in at least one of: one or more RRC messages comprising configuration parameters of the first cell and the one or more candidate cells; and The command.

25. The method according to any one of claims 2 to 24, further comprising receiving, by the wireless device, one or more RRC messages to periodically configure the measurement window.

26. The method of any one of claims 2 to 25, wherein the command indicates that the measurement window is aperiodic.

27. The method according to any one of claims 2 to 26, further comprising receiving, by the wireless device, one or more RRC messages to periodically configure the measurement window, wherein the measurement window is semi-persistent and is activated by the command.

28. The method according to any one of claims 2 to 27, wherein: In response to at least one of the one or more candidate cells having better channel quality than the first cell, the CSI report includes an indication of at least one of the first RSs of the one or more candidate cells; or In response to none of the one or more candidate cells having a better channel quality than the first cell, the CSI report includes an indication of at least one of the second RSs of the first cell.

29. The method according to any one of claims 2 to 28, wherein the LTM procedure comprises at least one of the following: receiving downlink control information (DCI) indicating that a preamble is transmitted via a first candidate cell among the one or more candidate cells; transmitting the preamble to the first candidate cell; receiving a media access control element (MAC CE) indicating a handover from the first cell to the first candidate cell as a serving cell; as well as Switch to the first candidate cell as the serving cell.

30. The method of claim 29, wherein before receiving the MAC CE indicating handover from the first cell to the first candidate cell, when the first cell is the serving cell, the one or more candidate cells are not activated.

31. The method according to any one of claims 2 to 30, wherein the first cell is a primary cell (PCell).

32. The method according to any one of claims 2 to 31, wherein the uplink transmission of the CSI report is via at least one of: Physical Uplink Shared Channel PUSCH; and Physical Uplink Control Channel PUCCH.

33. The method according to any one of claims 2 to 32, wherein the uplink transmission of the CSI report comprises an aperiodic CSI report.

34. The method according to any one of claims 2 to 33, wherein the uplink transmission of the CSI report comprises a semi-persistent CSI report via a Physical Uplink Shared Channel (PUSCH) or a Physical Uplink Control Channel (PUCCH).

35. The method of any one of claims 2 to 34, wherein the uplink transmission of the CSI report comprises a periodic CSI report.

36. A method comprising: Receiving, by the wireless device via the first cell, a command indicating uplink transmission of channel state information (CSI) reports of one or more candidate cells for a layer 1 / 2 triggered mobility (LTM) procedure in a first time slot; and The CSI report measured on a first RS of the one or more candidate cells is transmitted in the first time slot and via the first cell, wherein the first RS is received via the one or more candidate cells no later than a symbol before the first time slot based on beam reporting timing.

37. The method of claim 36, wherein the beam reporting timing is based on a time gap between an end of measurement of the first RS on the one or more candidate cells and a start of transmission of the CSI report via the first cell.

38. The method according to any one of claims 36 to 37, wherein the CSI report comprises at least one of the following: Layer 1 reference signal received power L1-RSRP; an indication of a first one of the RSs; and An indication of a second cell among the one or more candidate cells, wherein the L1-RSRP is measured on the first RS of the second cell.

39. The method according to any one of claims 36 to 38, wherein in response to receiving a second RS of the one or more candidate cells after the symbol, the CSI report of the one or more candidate cells is not based on the second RS.

40. The method according to any one of claims 36 to 39, further comprising transmitting, by the wireless device, one or more RRC messages comprising a wireless device capability parameter indicating the beam reporting timing.

41. A method according to claim 40, wherein the beam reporting timing indicates the number of orthogonal frequency division multiplexing (OFDM) symbols between the end of the symbol of the first RS of the one or more candidate cells and the start of the first symbol of the first time slot in which the CSI report is transmitted via the first cell.

42. The method according to any one of claims 40 to 41, wherein the one or more RRC messages further include a second beam reporting timing different from the beam reporting timing.

43. The method of claim 42, wherein the second beam reporting timing indicates the number of OFDM symbols between an end of a symbol of the RS of the first cell and a start of a first symbol of the first time slot in which the CSI report is transmitted via the first cell.

44. A method according to any one of claims 36 to 43, wherein: In response to at least one of the one or more candidate cells having better channel quality than the first cell, the CSI report includes an indication of at least one of the first RSs of the one or more candidate cells; or In response to none of the one or more candidate cells having a better channel quality than the first cell, the CSI report includes an indication of at least one of the second RSs of the first cell.

45. A method comprising: Receiving, by the wireless device via the first cell, a command indicating uplink transmission of channel state information (CSI) reports of one or more candidate cells for a layer 1 / 2 triggered mobility (LTM) procedure in a first time slot; and The CSI report measured on a first RS of the one or more candidate cells is transmitted in the first time slot and via the first cell, wherein the first RS is received via the one or more candidate cells within a measurement window.

46. ​​The method of claim 45, wherein the measurement window is a layer 1 measurement gap indicating a minimum number of Orthogonal Frequency Division Multiplexing (OFDM) symbols used to perform measurements for the CSI report.

47. The method according to any one of claims 45 to 46, wherein the CSI report comprises at least one of the following: Layer 1 reference signal received power L1-RSRP; an indication of a first one of the RSs; and An indication of a second cell among the one or more candidate cells, wherein the L1-RSRP is measured on the first RS of the second cell.

48. The method according to any one of claims 45 to 47, wherein in response to receiving a second RS of the one or more candidate cells outside the measurement window, the CSI report of the one or more candidate cells is not based on the second RS.

49. The method of any one of claims 45 to 48, further comprising transmitting, by the wireless device, one or more RRC messages including a wireless device capability parameter indicating the measurement window.

50. The method of any one of claims 45 to 49, wherein the measurement window indicates a number of time slots or symbols during which the wireless device: performing measurements on the one or more candidate cells for the CSI report; and Receiving downlink signals and transmitting uplink signals via the first cell are stopped.

51. The method of any one of claims 45 to 50, further comprising receiving, by the wireless device, one or more RRC messages to periodically configure the measurement window, wherein the measurement window is semi-persistent and is activated by the command.

52. A method according to any one of claims 45 to 51, wherein: In response to at least one of the one or more candidate cells having better channel quality than the first cell, the CSI report includes an indication of at least one of the first RSs of the one or more candidate cells; or In response to none of the one or more candidate cells having a better channel quality than the first cell, the CSI report includes an indication of at least one of the second RSs of the first cell.

53. The method according to any one of claims 45 to 52, wherein the first RS is received via the one or more candidate cells no later than a symbol before the first time slot based on beam reporting timing.

54. A method comprising: A configuration parameter for triggering a Layer 1 / 2 mobility LTM procedure is received by a wireless device, wherein the configuration parameter indicates: Reference signal RS of the candidate cell; and A measurement window for measuring the layer 1 reference signal received power L1-RSRP of the candidate cell; Receiving downlink control information (DCI) via a serving cell, the DCI indicating uplink transmission of a channel state information (CSI) report of the candidate cell in a first time slot; and The CSI report of a first RS among the RSs of the candidate cell is transmitted in the first time slot, wherein the first RS is received within the measurement window.

55. The method of claim 54, wherein the measurement window is a layer 1 measurement gap indicating a minimum number of Orthogonal Frequency Division Multiplexing (OFDM) symbols used to perform measurements for the CSI report.

56. The method according to any one of claims 54 to 55, wherein the CSI report comprises at least one of the following: Layer 1 reference signal received power L1-RSRP; an indication of a first one of the RSs; and An indication of a second cell of the candidate cell, wherein the L1-RSRP is measured on the first RS of the second cell.

57. The method according to any one of claims 54 to 56, wherein in response to receiving a second RS of the candidate cell outside the measurement window, the measurement of the CSI report of the candidate cell is not based on the second RS.

58. The method of any one of claims 54 to 57, further comprising transmitting, by the wireless device, one or more RRC messages including a wireless device capability parameter indicating the measurement window.

59. The method of claim 58, wherein the measurement window indicates a number of time slots or symbols during which the wireless device: performing measurements on the candidate cells for the CSI report; and Receiving downlink signals and transmitting uplink signals via the serving cell are stopped.

60. The method of any one of claims 54 to 59, further comprising receiving, by the wireless device, one or more RRC messages to periodically configure the measurement window, wherein the measurement window is semi-persistent and activated by the DCI. 61 . The method according to claim 54 , wherein the first RS is received via the candidate cell no later than a symbol before the first time slot based on beam report timing.

62. A wireless device comprising: one or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform a method according to any one of claims 2 to 61.

63. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to perform the method of any one of claims 2 to 61.

Images