Beam failure recovery procedure in dormant state

Abstract

A wireless device receives one or more messages including one or more configuration parameters of a cell. A beam failure recovery procedure for the cell is initiated based on beam failure detection of the cell. The cell is transitioned to a dormant state during the beam failure recovery procedure. Channel state information of the cell is reported in the dormant state. The beam failure recovery procedure is terminated based on the transition of the cell to the dormant state during the beam failure recovery procedure.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 714,207, filed on August 3, 2018, which is incorporated herein 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 drawings.

[0004] Figure 1 is a diagram of an example RAN architecture in accordance with aspects of an embodiment of the present disclosure.

[0005] Figure 2A is a diagram of an example user plane protocol stack according to aspects of an embodiment of the present disclosure.

[0006] Figure 2B is a diagram of an example control plane protocol stack in accordance with aspects of an embodiment of the present disclosure.

[0007] Figure 3 is a diagram of an example wireless device and two base stations in accordance with aspects of an embodiment of the present disclosure.

[0008] Figure 4A , Figure 4B , Figure 4C and Figure 4D is an example diagram of uplink and downlink signal transmission according to aspects of an embodiment of the present disclosure.

[0009] Figure 5A is a diagram of an example uplink channel map and example uplink physical signals according to aspects of an embodiment of the present disclosure.

[0010] Figure 5B is a diagram of an example downlink channel map and example downlink physical signals according to aspects of an embodiment of the present disclosure.

[0011] Figure 6 is a diagram depicting example transmission times or reception times of carriers according to aspects of embodiments of the present disclosure.

[0012] Fig. 7A and Figure 7B is a diagram depicting an example set of OFDM subcarriers in accordance with aspects of an embodiment of the present disclosure.

[0013] Figure 8 is a diagram depicting example OFDM radio resources in accordance with aspects of an embodiment of the present disclosure.

[0014] Fig. 9Ais a diagram depicting example CSI-RS and / or SS block transmissions in a multi-beam system.

[0015] Fig. 9B is a diagram depicting an example downlink beam management procedure in accordance with aspects of an embodiment of the present disclosure.

[0016] Fig.10 is an example diagram of a configured BWP in accordance with aspects of an embodiment of the present disclosure.

[0017] Fig.11A and Fig. 11B is a diagram of example multiple connectivity according to aspects of an embodiment of the present disclosure.

[0018] Fig.12 is a diagram of an example random access procedure according to aspects of an embodiment of the present disclosure.

[0019] Fig.13 is the structure of an example MAC entity according to aspects of an embodiment of the present disclosure.

[0020] Fig.14 is an example RAN architecture diagram according to aspects of an embodiment of the present disclosure.

[0021] Fig.15 is a diagram of example RRC states in accordance with aspects of an embodiment of the present disclosure.

[0022] Fig.16A , Fig. 16B and Fig. 16C is an example of a MAC subheader according to aspects of an embodiment of the present disclosure.

[0023] Fig.17A and Fig. 17B is an example of a MAC PDU according to aspects of an embodiment of the present disclosure.

[0024] Fig.18 is an example of an LCID for DL-SCH according to aspects of an embodiment of the present disclosure.

[0025] Fig.19 is an example of an LCID for UL-SCH according to aspects of an embodiment of the present disclosure.

[0026] Fig. 20A is an example of a one-octet SCell activation / deactivation MAC CE according to aspects of embodiments of the present disclosure.

[0027] Fig. 20B is an example of a four-octet SCell activation / deactivation MAC CE according to aspects of embodiments of the present disclosure.

[0028] Fig.21A is an example of a one-octet SCell sleep MAC CE according to aspects of embodiments of the present disclosure.

[0029] Fig. 21B is an example of a four-octet SCell sleep MAC CE according to aspects of embodiments of the present disclosure.

[0030] Fig. 21C is an example of a MAC control element for SCell state transition according to aspects of an embodiment of the present disclosure.

[0031] Fig. 22 is an example of a signaling-based SCell state transition mechanism according to aspects of an embodiment of the present disclosure.

[0032] Fig.23 is an example of a timer-based SCell state transition mechanism according to aspects of an embodiment of the present disclosure.

[0033] Fig.24A and Fig. 24B is an example of a downlink beam failure according to aspects of an embodiment of the present disclosure.

[0034] Fig.25 is an example flow chart of a downlink beam failure recovery procedure in accordance with aspects of an embodiment of the present disclosure.

[0035] Fig.26 is an example of a downlink beam failure example indication according to aspects of an embodiment of the present disclosure.

[0036] Fig. 27 is an example of a downlink beam failure example indication according to aspects of an embodiment of the present disclosure.

[0037] Fig.28 is an example of a downlink beam failure recovery procedure in a dormant state according to aspects of an embodiment of the present disclosure.

[0038] Fig.29A and Fig.29B is an example of a downlink beam failure recovery procedure according to aspects of an embodiment of the present disclosure.

[0039] Fig.30 According to aspects of embodiments of the present disclosure Fig.28 Example flow chart of .

[0040] Fig.31 is a flow chart according to aspects of example embodiments of the present disclosure. DETAILED DESCRIPTION

[0041] Example embodiments of the present disclosure implement the operation of a beam failure recovery procedure. Embodiments of the technology disclosed herein may be employed in the technical field of multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein may relate to a beam failure recovery procedure in a multi-carrier communication system.

[0042] The following abbreviations are used throughout this disclosure:

[0043] 3GPP 3rd Generation Partnership Project

[0044] 5GC 5G Core Network

[0045] ACK

[0046] AMF Access and Mobility Management Function

[0047] ARQ Automatic Repeat Request

[0048] AS access layer

[0049] ASIC Application-Specific Integrated Circuit

[0050] BA Bandwidth Adaptation

[0051] BCCH Broadcast Control Channel

[0052] BCH Broadcast Channel

[0053] BPSK Binary Phase Shift Keying

[0054] BWP Bandwidth Part

[0055] CA Carrier Aggregation

[0056] CC Component Carrier

[0057] CCCH Common Control Channel

[0058] CDMA Code Division Multiple Access

[0059] CN Core Network

[0060] CP Cyclic Prefix

[0061] CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0062] C-RNTI Cell-Radio Network Temporary Identifier

[0063] CS Configured Scheduling

[0064] CSI Channel State Information

[0065] CSI-RS Channel State Information-Reference Signal

[0066] CQI Channel Quality Indicator

[0067] CSS Common Search Space

[0068] CU Central Unit

[0069] DAI Downlink Assignment Index

[0070] DC Dual Connectivity

[0071] DCCH Dedicated Control Channel

[0072] DCI Downlink Control Information

[0073] DL Downlink

[0074] DL-SCH Downlink Shared Channel

[0075] DM-RS Demodulation Reference Signal

[0076] DRB Data Radio Bearer

[0077] DRX Discontinuous Reception

[0078] DTCH Dedicated Traffic Channel

[0079] DU Distributed Unit

[0080] EPC Evolved Packet Core

[0081] E-UTRA Evolved UMTS Terrestrial Radio Access

[0082] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0083] FDD Frequency Division Duplex

[0084] FPGA Field Programmable Gate Array

[0085] F1-C F1-Control Plane

[0086] F1-U F1-User Plane

[0087] gNB Next Generation Node B

[0088] HARQ Hybrid Automatic Repeat Request

[0089] HDL Hardware Description Language

[0090] IE Information Elements

[0091] IP Internet Protocol

[0092] LCID Logical Channel Identifier

[0093] LTE Long Term Evolution

[0094] MAC Media Access Control

[0095] MCG Master Cell Group

[0096] MCS modulation and coding scheme

[0097] MeNB Leading Node B

[0098] MIB Master Information Block

[0099] MME Mobility Management Entity

[0100] MN Master Node

[0101] NACK Negative Acknowledgement

[0102] NAS Non-Access Layer

[0103] NG CP Next Generation Control Plane

[0104] NGC Next Generation Core

[0105] NG-C NG-Control Plane

[0106] ng-eNB Next Generation Evolved Node B

[0107] NG-U NG-User Plane

[0108] NR New Radio

[0109] NR MAC New Radio MAC

[0110] NR PDCP New Radio PDCP

[0111] NR PHY New Radio Physics

[0112] NR RLC New Radio RLC

[0113] NR RRC New Radio RRC

[0114] NSSAI Network Slice Selection Assistant Information

[0115] O&M Operation and Maintenance

[0116] OFDM Orthogonal Frequency Division Multiplexing

[0117] PBCH Physical Broadcast Channel

[0118] PCC Primary Component Carrier

[0119] PCCH Paging Control Channel

[0120] PCell Primary Community

[0121] PCH Paging Channel

[0122] PDCCH Physical Downlink Control Channel

[0123] PDCP Packet Data Convergence Protocol

[0124] PDSCH Physical Downlink Shared Channel

[0125] PDU Protocol Data Unit

[0126] PHICH Physical HARQ Indicator Channel

[0127] PHY

[0128] PLMN Public Land Mobile Network

[0129] PMI Precoding Matrix Indicator

[0130] PRACH Physical Random Access Channel

[0131] PRB Physical Resource Block

[0132] PSCell Primary Secondary Cell

[0133] PSS Primary Synchronization Signal

[0134] pTAG Primary Timing Advance Group

[0135] PT-RS Phase Tracking Reference Signal

[0136] PUCCH Physical Uplink Control Channel

[0137] PUSCH Physical Uplink Shared Channel

[0138] QAM Quadrature Amplitude Modulation

[0139] QFI Quality of Service Indicator

[0140] QoS Quality of Service

[0141] QPSK Quadrature Phase Shift Keying

[0142] RA Random Access

[0143] RACH Random Access Channel

[0144] RAN Radio Access Network

[0145] RAT Radio Access Technology

[0146] RA-RNTI Random Access-Radio Network Temporary Identifier

[0147] RB Resource Block

[0148] RBG Resource Block Group

[0149] RI Rank Indicator

[0150] RLC Radio Link Control

[0151] RLM Radio Link Monitoring

[0152] RRC Radio Resource Control

[0153] RS reference signal

[0154] RSRP Reference Signal Received Power

[0155] SCC Secondary Component Carrier

[0156] SCell Secondary Cell

[0157] SCG Secondary Cell Group

[0158] SC-FDMA Single Carrier Frequency Division Multiple Access

[0159] SDAP Service Data Adaptation Protocol

[0160] SDU Service Data Unit

[0161] SeNB Secondary Evolved Node B

[0162] SFN System Frame Number

[0163] S-GW Service Gateway

[0164] SI System Information

[0165] SIB System Information Block

[0166] SMF session management functions

[0167] SN Secondary Node

[0168] SpCell Special Cell

[0169] SRB Signalling Radio Bearer

[0170] SRS Sounding Reference Signal

[0171] SS Sync Signal

[0172] SSS Secondary synchronization signal

[0173] sTAG Secondary Timing Advance Group

[0174] TA Timing Advance

[0175] TAG Timing Advance Group

[0176] TAI Tracking Area Identifier

[0177] TAT Time Alignment Timer

[0178] TB Transfer Block

[0179] TCI Transmit Configuration Indicator

[0180] TC-RNTI Temporary Cell-Radio Network Temporary Identifier

[0181] TDD Time Division Duplex

[0182] TDMA Time Division Multiple Access

[0183] TTI Transmit Time Interval

[0184] UCI Uplink Control Information

[0185] UE User Equipment

[0186] UL Uplink

[0187] UL-SCH Uplink Shared Channel

[0188] UPF User Plane Function

[0189] UPGW User Plane Gateway

[0190] VHDL VHSIC Hardware Description Language

[0191] Xn-C Xn-Control Plane

[0192] Xn-U Xn-User Plane

[0193] Various physical layer modulation and transmission mechanisms may be used to implement example embodiments of the present disclosure. Example transmission mechanisms may include, but are not limited to: code division multiple access (CDMA), orthogonal frequency division multiple access (OFDMA), time division multiple access (TDMA), wavelet techniques, etc. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be employed. Various modulation schemes may be applied to signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, combinations of these, etc. Example radio transmission methods may implement quadrature amplitude modulation (QAM) using binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding schemes according to transmission requirements and radio conditions.

[0194] Figure 1 is an example radio access network (RAN) architecture in accordance with aspects of an embodiment of the present disclosure. As shown in the example, the RAN node may be a next generation node B (gNB) (e.g., 120A, 120B) that provides a new radio (NR) user plane and control plane protocol termination to a first wireless device (e.g., 110A). In an example, the RAN node may be a next generation evolved node B (ng-eNB) (e.g., 120C, 120D) that provides an evolved UMTS terrestrial radio access (E-UTRA) user plane and control plane protocol termination to a second wireless device (e.g., 110B). The first wireless device may communicate with the gNB via a Uu interface. The second wireless device may communicate with the ng-eNB via a Uu interface.

[0195] The gNB or ng-eNB can host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of access and mobility management function (AMF) at the user equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or operation and maintenance (O&M)), measurements and measurement report configuration, transport layer packet marking in uplink, session management, network slice support, Quality of Service (QoS) flow management and mapping to data radio bearer, support for UE in RRC_INACTIVE state, distribution function of non-access stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

[0196] In an instance, one or more gNBs and / or one or more ng-eNBs may be interconnected to each other via an Xn interface. A gNB or ng-eNB may be connected to a 5G core network (5GC) via an NG interface. In an instance, a 5GC may include one or more AMF / User Planning Function (UPF) functions (e.g., 130A or 130B). A gNB or ng-eNB may be connected to the UPF via an NG user plane (NG-U) interface. The NG-U interface may provide delivery of user plane protocol data units (PDUs) (e.g., non-guaranteed delivery) between the RAN node and the UPF. A gNB or ng-eNB may be connected to the AMF via an NG control plane (NG-C) interface. The NG-C interface may provide functions such as NG interface management, UE context management, UE mobility management, transmission of NAS messages, paging, PDU session management, configuration delivery, or warning message transmission.

[0197] In an instance, the UPF may host functions such as an anchor point for intra / inter-radio access technology (RAT) mobility (when applicable), an external PDU session point for interconnection to a data network, packet routing and forwarding, user plane portion of packet inspection and policy rule enforcement, service usage reporting, an uplink classifier to support routing of service flows to the data network, a branch point to support multi-host PDU sessions, QoS processing for the user plane (e.g., packet filtering, gating), uplink (UL) / downlink (DL) rate enforcement, uplink service verification (e.g., service data flow (SDF) to QoS flow mapping), downlink packet buffering and / or downlink data notification triggering.

[0198] In an instance, the AMF may host functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, core network (CN) inter-node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming rights check, mobility management control (subscription and policy), support for network slice and / or session management function (SMF) selection, etc.

[0199] Figure 2Ais an example user plane protocol stack, in which service data adaptation protocol (SDAP) (e.g., 211 and 221), packet data convergence protocol (PDCP) (e.g., 212 and 222), radio link control (RLC) (e.g., 213 and 223), and medium access control (MAC) (e.g., 214 and 224) sublayers and physical (PHY) (e.g., 215 and 225) layers may be terminated in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side. In an example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In an example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) belonging to one or different logical channels into / demultiplexing of transport blocks (TBs) delivered to / from the PHY layer, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between UEs through dynamic scheduling, priority handling between logical channels of a UE through logical channel prioritization and / or padding. The MAC entity may support one or more parameter sets and / or transmission timings. In an example, mapping restrictions in logical channel prioritization may control which parameter set and / or transmission timing a logical channel may use. In an example, the RLC sublayer may support transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM) transmission modes. The RLC configuration may be based on each logical channel, independent of the parameter set and / or transmission time interval (TTI) duration. In an instance, the automatic repeat request (ARQ) can operate on any parameter set and / or TTI duration configured for the logical channel. In an instance, the services and functions of the PDCP layer for the user plane may include sequence numbering, header compression and decompression, delivery, reordering and duplication detection of user data, PDCP PDU routing (e.g., in the case of separate bearers), retransmission, encryption, decryption and integrity protection of PDCP SDUs, PDCP SDU discard, PDCP reconstruction and data recovery of RLC AM, and / or duplication of PDCP PDUs. In an instance, the services and functions of SDAP may include mapping between QoS flows and data radio bearers. In an instance, the services and functions of SDAP may include mapping quality of service indicators (QFIs) in DL and UL packets. In an instance, the protocol entities of SDAP may be configured for individual PDU sessions.

[0200] Figure 2Bis an example control plane protocol stack, wherein PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243) and MAC (e.g., 235 and 244) sublayers and PHY (e.g., 236 and 245) layers may be terminated in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side and perform the above services and functions. In an example, RRC (e.g., 232 and 241) may be terminated in a wireless device and a gNB on the network side. In an example, the services and functions of RRC may include: broadcasting system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between a UE and a RAN, security functions including key management, establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of reporting, detection of radio link failure and recovery of radio link failure, and / or delivery of NAS messages from UE to NAS / from NAS to UE. In an example, the NAS control protocol (e.g., 231 and 251) may be terminated in the wireless device and AMF (e.g., 130) on the network side, and may perform functions such as authentication, mobility management between UE and AMF for 3GPP access and non-3GPP access, and session management between UE and SMF for 3GPP access and non-3GPP access.

[0201] In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer, and the radio bearer may be associated with a QoS requirement. In an example, the base station may configure a logical channel to be mapped to one or more TTIs / parameter sets in a plurality of TTIs / parameter sets. The wireless device may receive downlink control information (DCI) indicating an uplink grant via a physical downlink control channel (PDCCH). In an example, the uplink grant may be for a first TTI / parameter set and may indicate an uplink resource for transmission of a transport block. The base station may configure each of the plurality of logical channels, wherein one or more parameters will be used by a logical channel prioritization procedure at a MAC layer of the wireless device. The one or more parameters may include a priority, a prioritized bit rate, and the like. A logical channel in the plurality of logical channels may correspond to one or more buffers including data associated with the logical channel. The logical channel prioritization procedure may allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) in the plurality of logical channels. One or more first logical channels may be mapped to a first TTI / parameter set. The MAC layer at the wireless device may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) in a MAC PDU (e.g., a transport block). In an example, the MAC PDU may include a MAC header including a plurality of MAC subheaders. A MAC subheader in a plurality of MAC subheaders may correspond to a MAC CE or MAC SUD (logical channel) in one or more MAC CEs and / or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a logical channel identifier (LCID). In an example, the LCID for a logical channel or MAC CE may be fixed / preconfigured. In an example, the LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC subheader corresponding to the MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0202] In an example, a base station may activate and / or deactivate and / or affect one or more processes (e.g., setting the value of one or more parameters of one or more processes or starting and / or stopping one or more timers of one or more processes) at a wireless device by using one or more MAC commands. The one or more MAC commands may include one or more MAC control elements. In an example, one or more processes may include activation and / or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE including one or more fields, the value of the field indicating activation and / or deactivation of PDCP duplication for one or more radio bearers. In an example, one or more processes may include channel state information (CSI) transmission on one or more cells. The base station may transmit one or more MAC CEs indicating activation and / or deactivation of CSI transmission on one or more cells. In an example, one or more processes may include activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MAC CE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and / or stopping one or more discontinuous reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values ​​for one or more timing advance groups (TAGs).

[0203] Figure 3 1 is a block diagram of a base station (base station 1, 120A and base station 2, 120B) and a wireless device 110. The wireless device may be referred to as a UE. The base station may be referred to as a NB, an eNB, a gNB, and / or an ng-eNB. In an example, the wireless device and / or the base station may act as a relay node. Base station 1, 120A may include at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, etc.), at least one processor 321A, and at least one set of program code instructions 323A, which are stored in a non-transitory memory 322A and can be executed by at least one processor 321A. Base station 2, 120B may include at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B, which are stored in a non-transitory memory 322B and can be executed by at least one processor 321B.

[0204] A base station may include many sectors, for example: 1, 2, 3, 4 or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. Cells may be classified as, for example, primary cells or secondary cells. During radio resource control (RRC) connection establishment / reconstruction / switching, a serving cell may provide NAS (non-access layer) mobility information (e.g., tracking area identifier (TAI)). During RRC connection reconstruction / switching, a serving cell may provide security input. The cell may be referred to as a primary cell (PCell). In the downlink, the carrier corresponding to the PCell may be a DL primary component carrier (PCC), and in the uplink, the carrier may be a UL PCC. Depending on the wireless device capabilities, a secondary cell (SCell) may be configured to form a serving cell set together with the PCell. In the downlink, the carrier corresponding to the SCell may be a downlink secondary component carrier (DL SCC), and in the uplink, the carrier may be an uplink secondary component carrier (UL SCC). The SCell may or may not have an uplink carrier.

[0205] A physical cell ID and a cell index may be assigned to a cell including a downlink carrier and an optional uplink carrier. A carrier (downlink or uplink) may belong to a cell. A cell ID or a cell index may also identify a downlink carrier or an uplink carrier of a cell (depending on the context in which it is used). In the present disclosure, a cell ID may refer to a carrier ID equivalently, and a cell index may be referred to as a carrier index. In an embodiment, a physical cell ID or a cell index may be assigned to a cell. A synchronization signal transmitted on a downlink carrier may be used to determine the cell ID. An RRC message may be used to determine the cell 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 including a first downlink carrier. The same concept may be applied, for example, to carrier activation. When the present disclosure indicates that a first carrier is activated, the designation may also mean activating a cell including the first carrier.

[0206] The base station may transmit one or more messages (e.g., RRC messages) including multiple configuration parameters of one or more cells to the wireless device. The one or more cells may include at least one primary cell and at least one secondary cell. In an example, the RRC message may be broadcast or unicast to the wireless device. In an example, the configuration parameters may include common parameters and dedicated parameters.

[0207] The services and / or functions of the RRC sublayer may include at least one of the following: broadcasting system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishment, maintenance and / or release of an RRC connection between a wireless device and NG-RAN, which may include at least one of the addition, modification and release of carrier aggregation; or the addition, modification and / or release of dual connectivity in NR or between E-UTRA and NR. The services and / or functions of the RRC sublayer may further include at least one of the following security functions: key management; establishment, configuration, maintenance and / or release of signaling radio bearers (SRBs) and / or data radio bearers (DRBs); mobility functions, which may include at least one of handover (e.g., intra-NR mobility or inter-RAT mobility) and context transfer; or wireless device cell selection and reselection and control of cell selection and reselection. The services and / or functions of the RRC sub-device may further include at least one of the following: QoS management functions; wireless device measurement configuration / reporting; detection of radio link failure and / or recovery of radio link failure; or delivery of NAS messages from the wireless device to a core network entity (e.g., AMF, Mobility Management Entity (MME)) / from a core network entity to the wireless device.

[0208] The RRC sublayer may support the RRC_Idle state, RRC_Inactive state, and / or RRC_Connected state of the wireless device. In the RRC_Idle state, the wireless device may perform at least one of the following: public land mobile network (PLMN) selection; receiving broadcast system information; cell selection / reselection; monitoring / receiving paging of mobile terminated data initiated by 5GC; paging of mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In the RRC_Inactive state, the wireless device may perform at least one of the following: receiving broadcast system information; cell selection / reselection; monitoring / receiving RAN / CN paging initiated by NG-RAN / 5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN / CN paging configured by NG-RAN / NAS. In the RRC_Idle state of the wireless device, the base station (e.g., NG-RAN) may maintain a 5GC-NG-RAN connection (both C / U planes) for the wireless device; and / or store a UE AS context for the wireless device. In the RRC_Connected state of the wireless device, the base station (e.g., NG-RAN) may perform at least one of the following: establishing a 5GC-NG-RAN connection (both C / U planes) for the wireless device; storing a UE AS context for the wireless device; transmitting / receiving unicast data to / from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In the RRC_Connected state of the wireless device, the NG-RAN may know the cell to which the wireless device belongs.

[0209] System information (SI) can be divided into minimum SI and other SI. Minimum SI can be broadcast periodically. Minimum SI may include basic information required for initial access and information for obtaining any other SI that is broadcast periodically or provided on demand, i.e., scheduling information. Other SI may be broadcast, or provided in a dedicated manner, or triggered by the network, or upon request by a wireless device. Minimum SI may be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For wireless devices in the RRC_Connected state, dedicated RRC signaling may be used for requesting and delivering other SI. For wireless devices in the RRC_Idle state and / or the RRC_Inactive state, the request may trigger a random access procedure.

[0210] The wireless device may report radio access capability information which may be static. The base station may request what capabilities the wireless device reports based on the band information. When the network allows, the wireless device may send a temporary capability restriction request to signal the limited availability of certain capabilities to the base station (e.g., due to hardware sharing, interference, or overheating). The base station may confirm or deny the request. Temporary capability restrictions may be transparent to the 5GC (e.g., static capabilities may be stored in the 5GC).

[0211] When CA is configured, the wireless device may have an RRC connection with the network. During the RRC connection establishment / reestablishment / handover procedures, one serving cell may provide NAS mobility information, and upon RRC connection establishment / handover, one serving cell may provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, an SCell may be configured to form a serving cell set together with the PCell. The configured serving cell set for the wireless device may include one PCell and one or more SCells.

[0212] Reconfiguration, addition and removal of SCells may be performed by RRC. RRC may also add, remove or reconfigure SCells for use with the target PCell when switching within NR. When adding a new SCell, dedicated RRC signaling may be used to send all required system information for the SCell, i.e., when in connected mode, the wireless device may not need to obtain broadcast system information directly from the SCell.

[0213] The purpose of the RRC connection reconfiguration procedure may be to modify the RRC connection, (e.g., establish, modify and / or release RBs, perform handovers, set up, modify and / or release measurements, add, modify and / or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS-specific information may be delivered from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify the RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g., RBs, MAC primary configuration, and physical channel configuration), including any associated dedicated NAS information and security configuration. If the received RRC connection reconfiguration message contains sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC connection reconfiguration message contains sCellToAddModList, the wireless device may perform an SCell addition or modification.

[0214] The RRC connection establishment (or reestablishment, restoration) procedure may be to establish (or reestablish, restore) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure may be used to transfer initial NAS dedicated information / messages from the wireless device to the E-UTRAN. The RRCConnectionReestablishment message may be used to reestablish SRB1.

[0215] The measurement report procedure may be to transfer the measurement results from the wireless device to the NG-RAN. After successful security activation, the wireless device may initiate the measurement report procedure. The measurement results may be transmitted using a measurement report message.

[0216] The wireless device 110 may include at least one communication interface 310 (e.g., a wireless modem, an antenna, etc.), at least one processor 314, and at least one set of program code instructions 316 stored in a non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may additionally include at least one of at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, at least one global positioning system (GPS) chipset 318, and other peripherals 319.

[0217] The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and / or the processor 321B of the base station 2 120B may include at least one of a general purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, etc. The processor 314 of the wireless device 110, the processor 321A in the base station 1 120A, and / or the processor 321B in the base station 2 120B may perform at least one of signal decoding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 110, the base station 1 120A, and / or the base station 2 120B to operate in a wireless environment.

[0218] The processor 314 of the wireless device 110 may be connected to the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313. The processor 314 may receive user input data from the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313, and / or provide user output data to them. The processor 314 in the wireless device 110 may receive power from the power supply 317, and / or may be configured to distribute power to other components in the wireless device 110. The power supply 317 may include at least one of one or more dry cells, solar cells, fuel cells, etc. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.

[0219] The processor 314 of the wireless device 110 may be additionally connected to other peripherals 319, which may include one or more software and / or hardware modules that provide additional features and / or functionality. For example, the peripherals 319 may include at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, etc.

[0220] The communication interface 320A of base station 1, 120A and / or the communication interface 320B of base station 2, 120B may be configured to communicate with the communication interface 310 of the wireless device 110 via the wireless link 330A and / or the wireless link 330B, respectively. In an example, the communication interface 320A of base station 1, 120A may communicate with the communication interface 320B of base station 2 and other RAN and core network nodes.

[0221] The wireless link 330A and / or the wireless link 330B may include at least one of a bidirectional link and / or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1 120A and / or with the communication interface 320B of the base station 2 120B. The base station 1 120A and the wireless device 110 and / or the base station 2 120B and the wireless device 110 may be configured to send and receive transport blocks via the wireless link 330A and / or via the wireless link 330B, respectively. The wireless link 330A and / or the wireless link 330B may employ at least one frequency carrier. According to some different aspects of the embodiments, one or more transceivers may be employed. A transceiver may be a device that includes both a transmitter and a receiver. A transceiver may be used in devices such as wireless devices, base stations, relay nodes, etc. In Figure 4A , Figure 4B , Figure 4C , Figure 4D , Figure 6 , Fig. 7A , Figure 7B , Figure 8 Example embodiments of radio technologies implemented in the communication interfaces 310, 320A, 320B and wireless links 330A, 330B are shown in EMBODIMENTS and the associated text.

[0222] In an example, other nodes in the wireless network (eg, AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and a memory for storing instructions.

[0223] A node (e.g., a wireless device, a base station, an AMF, an SMF, an UPF, a server, a switch, an antenna, etc.) may include one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the node to perform certain processes and / or functions. Example embodiments may implement operations of single carrier and / or multi-carrier communications. Other example embodiments may include a non-transitory tangible computer-readable medium that includes instructions that can be executed by one or more processors to enable operations of single carrier and / or multi-carrier communications. Other example embodiments may include an article of manufacture that includes a non-transitory tangible computer-readable machine-accessible medium on which instructions are encoded for enabling programmable hardware to enable a node to implement operations of single carrier and / or multi-carrier communications. A node may include a processor, a memory, an interface, etc.

[0224] The interface may include at least one of a hardware interface, a firmware interface, a software interface, and / or a combination thereof. The hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, etc. The software interface may include code stored in a memory device to implement one or more protocols, protocol layers, communication devices, device drivers, combinations thereof, etc. The firmware interface may include a combination of embedded hardware and code stored in and / or in communication with a memory device to implement connections, electronic device operations, one or more protocols, protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, etc.

[0225] Figure 4A , Figure 4B , Figure 4C and Figure 4D is an example diagram of uplink and downlink signal transmission according to aspects of an embodiment of the present disclosure. Figure 4AAn example uplink transmitter for at least one physical channel is shown. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulation symbols to one or several transmission layers; transform pre-decoding to generate complex-valued symbols; pre-decoding of complex-valued symbols; mapping of pre-decoded complex-valued symbols to resource elements; generating a complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; etc. In an example, when transform pre-decoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In an example, when transform pre-decoding is not enabled, the uplink transmission may be performed by Figure 4A Generate 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.

[0226] An example structure for modulation and up-conversion of the carrier frequency of a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port is shown in Figure 4B In. Filtering can be applied before transmission.

[0227] Figure 4C An example structure for downlink transmission is shown in . The baseband signal representing the downlink physical channel can perform one or more functions. The one or more functions may include: scrambling the decoded bits in the codeword to be transmitted on the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols to one or several transmission layers; pre-decoding of complex-valued modulation symbols on the layer transmitted on the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; etc. These functions are shown as examples, and it is expected that other mechanisms can be implemented in various embodiments.

[0228] In an example, a gNB may transmit a first symbol and a second symbol to a wireless device on an antenna port. The wireless device may infer a 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. In an example, the first antenna port and the second antenna port may be quasi-co-located if one or more large-scale properties of a channel on which the first symbol on the first antenna port is communicated may be inferred from a channel on which the second symbol on the second antenna port is communicated. The one or more large-scale properties may include at least one of: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0229] Example modulation and up-conversion of the carrier frequency of a complex-valued OFDM baseband signal for an antenna port Figure 4D Filtering may be employed prior to transmission.

[0230] Figure 5A is a diagram of an example uplink channel map and an example uplink physical signal. Figure 5B is a diagram of an example downlink channel mapping and downlink physical signals. In an example, the physical layer may provide one or more information transfer services to the MAC and / or one or more higher layers. For example, the physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. The information transfer service may indicate the manner and characteristics of transferring data over the radio interface.

[0231] In an example embodiment, the radio network may include one or more downlink and / or uplink transport channels. Figure 5A The figure in shows an example uplink transport channel including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. Figure 5B 5 shows an example downlink transport channel including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. The transport channels may be mapped to one or more corresponding physical channels. For example, UL-SCH 501 may be mapped to a physical uplink shared channel (PUSCH) 503. RACH 502 may be mapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to a physical downlink shared channel (PDSCH) 514. BCH 513 may be mapped to a physical broadcast channel (PBCH) 516.

[0232] There may be one or more physical channels without corresponding transport channels. The one or more physical channels may be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, a physical uplink control channel (PUCCH) 504 may carry UCI 509 from a UE to a base station. For example, a physical downlink control channel (PDCCH) 515 may carry DCI 517 from a base station to a UE. When UCI 509 and PUSCH 503 transmissions may overlap at least partially in a time slot, NR may support UCI 509 multiplexing in PUSCH 503. UCI 509 may include at least one of CSI, acknowledgment (ACK) / negative acknowledgment (NACK), and / or a scheduling request. DCI 517 on PDCCH 515 may indicate at least one of: one or more downlink assignments and / or one or more uplink scheduling grants.

[0233] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, the one or more RSs may be at least one of a demodulation-RS (DM-RS) 506, a phase tracking-RS (PT-RS) 507, and / or a sounding RS (SRS) 508. In the downlink, the base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more RSs to the UE. For example, the one or more RSs may be at least one of a primary synchronization signal (PSS) / secondary synchronization signal (SSS) 521, a CSI-RS 522, a DM-RS 523, and / or a PT-RS 524.

[0234] In an example, the UE may transmit one or more uplink DM-RS 506 to the base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and / or PUCCH 504). For example, the UE may transmit at least one uplink DM-RS 506 to the base station using PUSCH 503 and / or PUCCH 504, wherein the at least one uplink DM-RS 506 may span the same frequency range as the corresponding physical channel. In an example, the base station may configure the UE using one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station may semi-statistically configure the UE using the maximum number of front-loaded DM-RS symbols for PUSCH and / or PUCCH. For example, the UE may schedule single-symbol DM-RS and / or double-symbol DM-RS based on the maximum number of front-loaded DM-RS symbols, wherein the base station may configure the UE with one or more additional uplink DM-RS for PUSCH and / or PUCCH. The new radio network may, for example, support a common DM-RS structure for DL ​​and UL at least for CP-OFDM, wherein the DM-RS position, DM-RS pattern and / or scrambling sequence may be the same or different.

[0235] In an example, whether the uplink PT-RS 507 is present may depend on the RRC configuration. For example, the presence of the uplink PT-RS may be UE-specifically configured. For example, the presence and / or pattern of the uplink PT-RS 507 in the scheduled resources may be UE-specifically configured by a combination of RRC signaling and / or an association with one or more parameters (e.g., modulation and coding scheme (MCS)) for other purposes that may be indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS 507 may be associated with one or more DCI parameters including at least the MCS. The radio network may support multiple uplink PT-RS densities defined in the time / 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 the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, the uplink PT-RS 507 may be limited to the scheduled time / frequency duration of the UE.

[0236] In an example, the UE may transmit SRS 508 to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. For example, the SRS 508 transmitted by the UE may allow the base station to estimate the uplink channel state at one or more different frequencies. The base station scheduler may use the uplink channel state to assign one or more resource blocks of high quality for uplink PUSCH transmission from the UE. The base station may semi-statistically configure the UE using one or more SRS resource sets. For the SRS resource set, the base station may configure the UE using one or more SRS resources. The SRS resource set applicability 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 each of the one or more SRS resource sets may be transmitted at a certain moment. The UE may transmit one or more SRS resources in different SRS resource sets at the same time. The new radio network may support non-periodic, periodic, and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format may be used for the UE to select at least one of 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 503 and SRS 508 are transmitted in the same time slot, the UE may be configured to transmit SRS 508 after transmission of PUSCH 503 and corresponding uplink DM-RS 506.

[0237] In an instance, the base station may semi-statistically configure the UE using one or more SRS configuration parameters indicating at least one of: an SRS resource configuration identifier, a number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), a slot (mini-slot and / or subframe) level periodicity and / or offset of periodic and / or aperiodic SRS resources, a number of OFDM symbols in an SRS resource, a starting OFDM symbol for an SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and / or an SRS sequence ID.

[0238] In an example, in the time domain, the SS / PBCH block may include one or more OFDM symbols within the SS / PBCH block (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3). The SS / PBCH block may include a PSS / SSS 521 and a PBCH 516. In an example, in the frequency domain, the SS / PBCH block may include one or more consecutive subcarriers within the SS / PBCH block (e.g., 240 consecutive subcarriers, the subcarriers are numbered in increasing order from 0 to 239). For example, the PSS / SSS 521 may occupy 1 OFDM symbol and 127 subcarriers. For example, the PBCH 516 may span 3 OFDM symbols and 240 subcarriers. The UE may assume that one or more SS / PBCH blocks transmitted using the same block index may be quasi-co-located, for example, with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The UE may not assume quasi-co-location of other SS / PBCH block transmissions. The periodicity of the SS / PBCH blocks may be configured by the radio network (e.g., via RRC signaling), and the subcarrier spacing may determine the one or more time locations at which the SS / PBCH blocks may be sent. In an example, the UE may assume a band-specific subcarrier spacing for the SS / PBCH blocks unless the radio network has configured the UE to assume a different subcarrier spacing.

[0239] In an example, a downlink CSI-RS 522 may be used for the UE to obtain channel state information. The radio network may support periodic, aperiodic and / or semi-persistent transmission of the downlink CSI-RS 522. For example, the base station may semi-statistically configure and / or reconfigure the UE using the periodic transmission of the downlink CSI-RS 522. The configured CSI-RS resources may be activated / deactivated. For semi-persistent transmission, the activation and / or deactivation of the CSI-RS resources may be dynamically triggered. In an example, the CSI-RS configuration may include one or more parameters indicating the number of at least antenna ports. For example, the base station may configure the UE using 32 ports. The base station may semi-statistically configure the UE using one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated to one or more UEs from one or more CSI-RS resource sets. For example, the base station may semi-statistically configure one or more parameters indicating CSI RS resource mapping, such as the time domain position of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In an example, the UE may be configured to employ the same OFDM symbol for the downlink CSI-RS 522 and the control resource set (core set) when the downlink CSI-RS 522 and the core set are quasi-co-located in space and the resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the core set. In an example, the UE may be configured to employ the same OFDM symbol for the downlink CSI-RS 522 and the SS / PBCH block when the downlink CSI-RS 522 and the SS / PBCH block are quasi-co-located in space and the resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the SS / PBCH block.

[0240] In an example, the UE may transmit one or more downlink DM-RS 523 to a base station for channel estimation, e.g., for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, the radio network may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-load DM-RS pattern. The front-load DM-RS may be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). The base station may semi-statistically configure the UE with a maximum number of front-load DM-RS symbols for PDSCH 514. For example, the DM-RS configuration may support one or more DM-RS ports. For example, for single-user-MIMO, the DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports. For example, for multi-user-MIMO, the DM-RS configuration may support 12 orthogonal downlink DM-RS ports. The radio network may support a common DM-RS structure for DL ​​and UL, for example, at least for CP-OFDM, where the DM-RS positions, DM-RS patterns and / or scrambling sequences may be the same or different.

[0241] In an example, whether a downlink PT-RS 524 exists may depend on an RRC configuration. For example, the presence of a downlink PT-RS 524 may be UE-specifically configured. For example, the presence and / or pattern of a downlink PT-RS 524 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and / or association with one or more parameters (e.g., MCS) for other purposes that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS 524 may be associated with one or more DCI parameters including at least an MCS. A radio network may support multiple PT-RS densities defined in a time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may use the same precoding for a DMRS port and a PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, a downlink PT-RS 524 may be limited to a scheduled time / frequency duration of the UE.

[0242] Figure 6 is a diagram depicting example transmit times and receive times for carriers in accordance with aspects of embodiments of the present disclosure. A multi-carrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers in the case of carrier aggregation, or ranging from 1 to 64 carriers in the case of dual connectivity. Different radio frame structures may be supported (e.g., for FDD and for TDD duplexing schemes). Figure 6 Example frame timing is shown. Downlink and uplink transmissions may be organized into radio frames 601. In this example, the radio frame duration is 10 milliseconds. In this example, the 10 millisecond radio frame 601 may be divided into ten equally sized subframes 602 having a duration of 1 millisecond. One or more subframes may include one or more time slots (e.g., time slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, subframes with 15kHz, 30kHz, 60kHz, 120kHz, 240kHz, and 480kHz subcarrier spacing may include one, two, four, eight, sixteen, and thirty-two time slots, respectively. Figure 6 In the embodiment of the present invention, a subframe can be divided into two equally sized time slots 603 with a duration of 0.5 milliseconds. For example, at an interval of 10 milliseconds, 10 subframes can be used for downlink transmission and 10 subframes can be used for uplink transmission. Uplink and downlink transmissions can be separated in the frequency domain. One or more time slots can contain multiple OFDM symbols 604. The number of OFDM symbols 604 in a time slot 605 can depend on the cyclic prefix length. For example, for the same subcarrier spacing of up to 480kHz with normal CP, a time slot can be 14 OFDM symbols. For the same subcarrier spacing of 60kHz with extended CP, a time slot can be 12 OFDM symbols. A time slot can contain a downlink, an uplink, or a downlink part and an uplink part, etc.

[0243] Fig. 7A700. The diagram depicts an example set of OFDM subcarriers according to aspects of an embodiment of the present disclosure. In the example, a gNB may communicate with a wireless device using a carrier having an example channel bandwidth 700. One or more arrows in the diagram may depict subcarriers in a multi-carrier OFDM system. The OFDM system may use technologies such as OFDM technology, SC-FDMA technology, etc. In the example, arrow 701 shows a subcarrier on which an information symbol is transmitted. In the example, a subcarrier spacing 702 between two consecutive subcarriers in a carrier may be any one of 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, etc. In the example, different subcarrier spacings may correspond to different transmission parameter sets. In the example, the transmission parameter set may include at least: a parameter set index; a value of the subcarrier spacing; a type of cyclic prefix (CP). In the example, the gNB may transmit to / receive from a UE on several subcarriers 703 in a carrier. In an example, due to the guard bands 704 and 705, the bandwidth occupied by several subcarriers 703 (transmit bandwidth) can be less than the channel bandwidth 700 of the carrier. In an example, the guard bands 704 and 705 can be used to reduce interference to and from one or more adjacent carriers. The number of subcarriers in a carrier (transmit bandwidth) can depend on the channel bandwidth and subcarrier spacing of the carrier. For example, for a carrier with a 20MHz channel bandwidth and a 15KHz subcarrier spacing, the transmit bandwidth can be the number of 1024 subcarriers.

[0244] In an example, when CA configuration is utilized, the gNB and wireless device may communicate with multiple CCs. In an example, if CA is supported, different component carriers may have different bandwidths and / or subcarrier spacings. In an example, the gNB may transmit a first type of service to the UE on a first component carrier. The gNB may transmit a second type of service to the UE on a second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carriers with different subcarrier spacings and / or bandwidths. Figure 7B An example embodiment is shown. The first component carrier may include a first number of subcarriers 706 having a first subcarrier spacing 709. The second component carrier may include a second number of subcarriers 707 having a second subcarrier spacing 710. The third component carrier may include a third number of subcarriers 708 having a third subcarrier spacing 711. The carriers in a multi-carrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of contiguous and non-contiguous carriers.

[0245] Figure 8801. In an example, a carrier may have a transmission bandwidth 801. In an example, a resource grid may be in a frequency domain 802 and a time domain 803 structure. In an example, a resource grid may include a first number of OFDM symbols and a second number of resource blocks in a subframe, starting from a common resource block for transmitting a parameter set and a carrier indicated by higher layer signaling (e.g., RRC signaling). In an example, in a resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element 805. In an example, depending on a parameter set associated with a carrier, a subframe may include a first number of OFDM symbols 807. For example, when the subcarrier spacing of the parameter set of the carrier is 15KHz, the subframe may have 14 OFDM symbols for the carrier. When the subcarrier spacing of the parameter set is 30KHz, the subframe may have 28 OFDM symbols. When the subcarrier spacing of the parameter set is 60Khz, the subframe may have 56 OFDM symbols, etc. In an example, the second number of resource blocks included in the resource grid of the carrier can depend on the bandwidth and the numerology of the carrier.

[0246] like Figure 8 As shown, resource block 806 may include 12 subcarriers. In an example, multiple resource blocks may be grouped into resource block groups (RBGs) 804. In an example, the size of the RBG may depend on at least one of: an RRC message indicating an RBG size configuration; the size of the carrier bandwidth; or the size of a bandwidth portion of the carrier. In an example, the carrier may include multiple bandwidth portions. A first bandwidth portion of the carrier may have a different frequency location and / or bandwidth than a second bandwidth portion of the carrier.

[0247] In an example, the gNB may transmit downlink control information including downlink or uplink resource block assignments to the wireless device. The base station may transmit to or receive from the wireless device a data packet (e.g., a transport block) scheduled and transmitted via one or more resource blocks and one or more time slots according to the downlink control information and / or parameters in one or more RRC messages. In an example, a start symbol of a first time slot relative to the one or more time slots may be indicated to the wireless device. In an example, the gNB may transmit to or receive from the wireless device a data packet scheduled on one or more RBGs and one or more time slots.

[0248] In an example, the gNB may transmit downlink control information including a downlink assignment to the wireless device via one or more PDCCHs. The downlink assignment may include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to the DL-SCH. In an example, the resource allocation may include parameters for a resource block allocation; and / or a time slot allocation. In an example, the gNB may dynamically allocate resources to the wireless device via a cell-radio network temporary identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs to find possible allocations when its downlink reception is enabled. When the one or more PDCCHs are successfully detected, the wireless device may receive one or more downlink data packets on one or more PDSCHs scheduled by the one or more PDCCHs.

[0249] In an example, the gNB may allocate configured scheduling (CS) resources for downlink transmission to the wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS grant. The gNB may transmit the DCI via a PDCCH addressed to the configured scheduling-RNTI (CS-RNTI) that activates the CS resources. The DCI may include a parameter indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivated.

[0250] In an example, the gNB may transmit downlink control information including an uplink grant to the wireless device via one or more PDCCHs. The uplink grant may include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to the UL-SCH. In an example, the resource allocation may include parameters for a resource block allocation; and / or a time slot allocation. In an example, the gNB may dynamically allocate resources to the wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs for possible resource allocations. Upon successful detection of the one or more PDCCHs, the wireless device may transmit one or more uplink data packets via one or more PUSCHs scheduled by the one or more PDCCHs.

[0251] In an example, the gNB may allocate CS resources for uplink data transmission to the wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to the CS-RNTI that activated the CS resources. The DCI may include a parameter indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivated.

[0252] In an example, a base station may transmit DCI / control signaling via PDCCH. DCI may adopt a format in a variety of formats. DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), a request for CSI (e.g., aperiodic CQI report), a request for SRS, an uplink power control command for one or more cells, one or more timing information (e.g., TB transmission / reception timing, HARQ feedback timing, etc.), etc. In an example, DCI may indicate an uplink grant including transmission parameters for one or more transport blocks. In an example, DCI may indicate a downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a base station may use DCI to initiate contention-free random access at a wireless device. In an example, a base station may transmit a DCI including a slot format indicator (SFI) that notifies a slot format. In an example, a base station may transmit a DCI including a preemptive indication notifying one or more PRBs and / or one or more OFDM symbols, wherein the UE may assume that there is no transmission intended for the UE. In an example, a base station may transmit a DCI for group power control of a PUCCH or PUSCH or SRS. In an example, the DCI may correspond to an RNTI. In an example, a wireless device may obtain an RNTI (e.g., C-RNTI) in response to completing initial access. In an example, a base station may configure an RNTI (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI) for wireless. In an example, a wireless device may calculate an RNTI (e.g., a wireless device may calculate an RA-RNTI based on resources used to transmit a preamble). In an example, the RNTI may have a preconfigured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space, which may be used by a base station to transmit a DCI intended for a group of UEs. In an example, the group common DCI may correspond to a RNTI configured commonly for a group of UEs. In an example, the wireless device may monitor a UE-specific search space. In an example, the UE-specific DCI may correspond to a RNTI configured for the wireless device.

[0253] The NR system may support single beam operation and / or multi-beam operation. In multi-beam operation, the base station may perform downlink beam sweeping to provide coverage for a common control channel and / or downlink SS block that may include at least PSS, SSS and / or PBCH. The wireless device may use one or more RSs to measure the quality of the beam to the link. One or more SS blocks, or one or more CSI-RS resources associated with a CSI-RS resource index (CRI), or one or more DM-RSs of the PBCH may be used as RSs for measuring the quality of the beam to the link. The quality of the beam to the link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. The base station may indicate whether the RS resource used to measure the quality of the beam to the link is quasi-co-located (QCL) with the DM-RS of the control channel. When the channel characteristics of the transmission from the RS to the wireless device and the transmission from the control channel to the wireless device are similar or identical under the configured criteria, the RS resources and DM-RS of the control channel may be referred to as QCL. In multi-beam operation, a wireless device may perform uplink beam sweeping to access a cell.

[0254] In an example, a wireless device may be configured to simultaneously monitor PDCCH on one or more beam pair links depending on the capabilities of the wireless device. This can increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure a wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, a base station may transmit higher layer signaling (e.g., RRC signaling) or MAC CE, which includes parameters for Rx beam settings of a wireless device for monitoring PDCCH on one or more beam pair links. A base station may transmit one or more DL RS antenna ports (e.g., cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS blocks, or PBCH with or without DM-RS of PBCH) and an indication of spatial QCL assumptions between one or more DL RS antenna ports for demodulating DL control channels. Signaling for beam indication for PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or standardized transparent and / or implicit methods, and combinations of these signaling methods.

[0255] For reception of a unicast DL data channel, the base station may indicate spatial QCL parameters between one or more DL RS antenna ports and one or more DM-RS antenna ports of the DL data channel. The base station may transmit a DCI (e.g., a downlink grant) including information indicating the one or more RS antenna ports. The information may indicate one or more RS antenna ports that may be QCLed with the one or more DM-RS antenna ports. Different sets of one or more DM-RS antenna ports for the DL data channel may be indicated as different sets of QCLed with the one or more RS antenna ports.

[0256] Fig. 9A is an example of beam sweeping in a DL channel. In the RRC_INACTIVE state or the RRC_IDLE state, the wireless device may assume that the SS blocks form an SS burst 940 and an SS burst set 950. The SS burst set 950 may have a given periodicity. For example, in multi-beam operation, the base station 120 may transmit SS blocks in multiple beams, thereby forming an SS burst 940 together. One or more SS blocks may be transmitted on one beam. If multiple SS bursts 940 are transmitted with multiple beams, then the SS bursts together may form an SS burst set 950.

[0257] The wireless device may additionally use CSI-RS in multi-beam operation to estimate the beam quality of the link between the wireless device and the base station. A beam may be associated with a CSI-RS. For example, the wireless device may report a beam index as indicated in the CRI for downlink beam selection and associated with the RSRP value of the beam based on an RSRP measurement report on the CSI-RS. The CSI-RS may be transmitted on a CSI-RS resource that includes at least one of one or more antenna ports, one or more time or frequency radio resources. The CSI-RS resources may be configured in a cell-specific manner by common RRC signaling or in a wireless device-specific manner by dedicated RRC signaling and / or L1 / L2 signaling. Multiple wireless devices covered by a cell may measure cell-specific CSI-RS resources. A dedicated subset of wireless devices covered by a cell may measure wireless device-specific CSI-RS resources.

[0258] The CSI-RS resources may be transmitted periodically or using aperiodic transmission or using multiple or semi-continuous transmission. Fig. 9A In periodic transmission in the time domain, the base station 120 may periodically transmit the configured CSI-RS resources 940 using the configured periodicity. In aperiodic transmission, the configured CSI-RS resources may be transmitted in a dedicated time slot. In multiple or semi-continuous transmission, the configured CSI-RS resources may be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beamwidth than the beam used for SS block transmission.

[0259] Fig. 9B is an example of a beam management procedure in an example new radio network. The base station 120 and / or the wireless device 110 may perform a downlink L1 / L2 beam management procedure. One or more of the following downlink L1 / L2 beam management procedures may be performed within one or more wireless devices 110 and one or more base stations 120. In an example, the P-1 procedure 910 may be used to enable the wireless device 110 to measure one or more transmit (Tx) beams associated with the base station 120 to support the selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beams associated with the wireless device 110. In order to perform beamforming at the base station 120, the base station 120 may sweep a set of different TX beams. In order to perform beamforming at the wireless device 110, the wireless device 110 may sweep a set of different Rx beams. In an example, the P-2 procedure 920 may be used to enable the wireless device 110 to measure one or more Tx beams associated with the base station 120 to possibly change the first set of Tx beams associated with the base station 120. The P-2 procedure 920 may be performed on a potentially smaller set of beams for beam optimization than in the P-1 procedure 910. The P-2 procedure 920 may be a special case of the P-1 procedure 910. In an example, the P-3 procedure 930 may be used to enable the wireless device 110 to measure at least one Tx beam associated with the base station 120 to change a first set of Rx beams associated with the wireless device 110.

[0260] The wireless device 110 may transmit one or more beam management reports to the base station 120. In the one or more beam management reports, the wireless device 110 may indicate some beam pair quality parameters, including at least: one or more beam identities of a subset of configured beams; RSRP; precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI). Based on the one or more beam management reports, the base station 120 may transmit a signal to the wireless device 110 indicating that the one or more beam pair links are one or more service beams. The base station 120 may transmit PDCCH and PDSCH for the wireless device 110 using one or more service beams.

[0261] In an example embodiment, the new radio network may support bandwidth adaptation (BA). In an example, the receive and / or transmit bandwidth configured by a UE employing BA may not be large. For example, the receive and / or transmit bandwidth may not be as large as the bandwidth of the cell. The receive and / or transmit bandwidth may be adjustable. For example, the UE may change the receive and / or transmit bandwidth, for example, shrink during low activity periods to save power. For example, the UE may change the location of the receive and / or transmit bandwidth in the frequency domain, for example, to increase scheduling flexibility. For example, the UE may change the subcarrier spacing, for example, to allow different services.

[0262] In an example embodiment, a subset of the total cell bandwidth of a cell may be referred to as a bandwidth part (BWP). The base station may configure the UE with one or more BWPs to implement BA. For example, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0263] Fig.10 This is an example diagram of 3 configured BWPs: BWP1 (1010 and 1050) with a width of 40MHz and a subcarrier spacing of 15kHz; BWP2 (1020 and 1040) with a width of 10MHz and a subcarrier spacing of 15kHz; BWP3 1030 with a width of 20MHz and a subcarrier spacing of 60kHz.

[0264] In an instance, a UE configured to operate in one or more BWPs of a cell may be configured by one or more higher layers (e.g., an RRC layer) of the cell with a set of one or more BWPs (e.g., up to four BWPs) for the UE (DL BWP set) to receive in a DL bandwidth via at least one parameter DL-BWP, and a set of one or more BWPs (e.g., up to four BWPs) for the UE (UL BWP set) to transmit in a UL bandwidth via at least one parameter UL-BWP for the cell.

[0265] To enable BA on PCell, the base station may configure the UE with one or more UL and DL BWP pairs. To enable BA on SCell (e.g., in case of CA), the base station may configure the UE with at least one or more DL BWPs (e.g., possibly none in UL).

[0266] In an example, the initial active DL BWP may be defined by at least one of the position and number of consecutive PRBs of a control resource set for at least one common search space, a subcarrier spacing, or a cyclic prefix. For operation on a PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If the UE is configured with a secondary carrier on a primary cell, the UE may be configured with an initial BWP for a random access procedure on the secondary carrier.

[0267] In an example, for unpaired spectrum operation, the UE may expect that the center frequency of the DL BWP may be the same as the center frequency of the UL BWP.

[0268] For example, for a DLBWP or UL BWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, the base station can semi-statistically configure the UE for the cell using one or more parameters, wherein the one or more parameters indicate at least one of the following: subcarrier spacing; cyclic prefix; the number of consecutive PRBs; an index in a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; DCI detection to PDSCH reception timing; PDSCH reception to HARQ-ACK transmission timing value; DCI detection to PUSCH transmission timing value; and an offset of the first PRB of the DL bandwidth or the UL bandwidth relative to the first PRB of the bandwidth, respectively.

[0269] In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, the base station may configure the UE with one or more control resource sets for at least one type of common search space and / or one UE-specific search space. For example, the base station may not configure the UE without a common search space on a PCell or on a PSCell in an active DL BWP.

[0270] For a UL BWP in a set of one or more UL BWPs, the base station may configure the UE with one or more resource sets for one or more PUCCH transmissions.

[0271] In an example, if the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active DL BWP from a configured DL BWP set for one or more DL receptions. If the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active UL BWP from a configured UL BWP set for one or more UL transmissions.

[0272] In an example, for PCell, the base station may semi-statistically configure the UE with a default DL BWP among the configured DL BWPs. If a default DL BWP is not provided to the UE, the default BWP may be the initial active DL BWP.

[0273] In an example, the base station may configure the UE with a timer value for the PCell. For example, when the UE detects a DCI indicating an active DL BWP other than the default DL BWP for paired spectrum operation or when the UE detects a DCI indicating an active DL BWP or UL BWP other than the default DL BWP for unpaired spectrum operation, the UE may start a timer called a BWP inactivity timer. If the UE does not detect a DCI during an interval for paired spectrum operation or for unpaired spectrum operation, the UE may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds). In an example, the timer may expire when the timer is equal to the timer value. When the timer expires, the UE may switch from the active DL BWP to the default DL BWP.

[0274] In an example, the base station may semi-statistically configure the UE with one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP (e.g., the second BWP may be the default 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. For example, Fig.10 1040, and BWP3 1030. BWP2 (1020 and 1040) may be the default BWP. BWP1 (1010) may be the initial active BWP. In an example, the UE may switch the active BWP from BWP1 1010 to BWP2 1020 in response to expiration of a BWP inactivity timer. For example, the UE may switch the active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as the active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040 and / or from BWP2 1040 to BWP1 1050 may be in response to receiving a DCI indicating an active BWP and / or in response to expiration of a BWP inactivity timer.

[0275] In an example, if the UE is configured with a default DL BWP and timer value among the configured DL BWPs for the secondary cell, the UE procedure on the secondary cell may be the same as the UE procedure on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0276] In an example, if the base station configures the UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, the UE may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0277] Fig.11A and Fig. 11B Packet flows employing multiple connectivity (eg, dual connectivity, multiple connectivity, tight interworking, etc.) are shown. Fig.11A is an example diagram of a protocol structure for a wireless device 110 (eg, UE) with CA and / or multiple connectivity according to aspects of the embodiments. Fig. 11B 1 is an example diagram of a protocol structure of multiple base stations with CA and / or multiple connectivity according to aspects of an embodiment. The multiple base stations may include a master node MN 1130 (e.g., a master node, a master base station, a master gNB, a master eNB, etc.) and a secondary node SN 1150 (e.g., a secondary node, a secondary base station, a secondary gNB, a secondary eNB, etc.). The master node 1130 and the secondary node 1150 may work together to communicate with the wireless device 110.

[0278] When multiple connections are configured for the wireless device 110, the wireless device 110 that can support multiple receive / transmit functions in the RRC connection state can be configured to utilize radio resources provided by multiple schedulers of multiple base stations. Multiple base stations can be interconnected through non-ideal or ideal backhauls (e.g., Xn interface, X2 interface, etc.). The base stations involved in the multiple connectivity for a certain wireless device can perform at least one of two different roles: the base station can act as a primary base station or a secondary base station. In multiple connectivity, the wireless device can be connected to a primary base station and one or more secondary base stations. In an example, a primary base station (e.g., MN 1130) can provide a wireless device (e.g., wireless device 110) with a primary cell group (MCG) including a primary cell and / or one or more secondary cells. A secondary base station (e.g., SN 1150) can provide a secondary cell group (SCG) including a primary secondary cell (PSCell) and / or one or more secondary cells for a wireless device (e.g., wireless device 110).

[0279] In multiple connectivity, the radio protocol architecture adopted by the bearer may depend on how the bearer is set up. In an example, three different types of bearer setting options can be supported: MCG bearer, SCG bearer and / or separate bearer. The wireless device can receive / transmit packets of the MCG bearer via one or more cells of the MCG, and / or can receive / transmit packets of the SCG bearer via one or more cells of the SCG. Multiple connectivity can also be described as having at least one bearer that is configured to use radio resources provided by a secondary base station. In some example embodiments, multiple connectivity may or may not be configured / implemented.

[0280] In an example, a wireless device (e.g., wireless device 110) may transmit and / or receive packets of an MCG bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC 1114), and a MAC layer (e.g., MN MAC 1118); transmit and / or receive packets of a separated bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of the primary or secondary RLC layers (e.g., MN RLC 1115, SN RLC 1116), and one of the primary or secondary MAC layers (e.g., MN MAC 1118, SN MAC 1119); and / or transmit and / or receive packets of a separated bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC 1117), and a MAC layer (e.g., MN MAC 1118). 1119) to transmit and / or receive packets carried by SCG.

[0281] In an example, a primary base station (e.g., MN 1130) and / or a secondary base station (e.g., SN 1150) may transmit / receive packets carried by the MCG via a primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a primary or secondary node PDCP layer (e.g., NR PDCP 1121, NR PDCP 1142), a primary node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and a primary node MAC layer (e.g., MN MAC 1128); and may transmit / receive packets carried by the MCG via a primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a primary or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g., SN MAC 1128). 1148) transmits / receives packets carried by the SCG; transmits / receives packets carried by the separated bearers via the primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), the primary or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), the primary or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127) and the primary or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

[0282] In multiple connectivity, the wireless device may configure multiple MAC entities: one MAC entity for the primary base station (e.g., MN MAC 1118), and other MAC entities for the secondary base stations (e.g., SN MAC 1119). In multiple connectivity, the configured service cell set for the wireless device may include two subsets: an MCG including service cells of the primary base station, and an SCG including service cells of the secondary base stations. For SCG, one or more of the following configurations may apply: at least one cell of the SCG has a configured UL CC, and at least one cell of the SCG, referred to as a primary secondary cell (PSCell, PCell of the SCG, or sometimes referred to as PCell) is configured with PUCCH resources; when the SCG is configured, there may be at least one SCG bearer or one split bearer; after a physical layer problem or a random access problem is detected on the PSCell, or after a number of NR RLC retransmissions associated with the SCG have been reached, or after an access problem is detected on the PSCell during SCG addition or SCG change: the RRC connection reestablishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the primary base station may be notified of the SCG failure type by the wireless device, and for a split bearer, DL data delivery on the primary base station may be maintained; NR may be configured for the split bearer RLC Acknowledged Mode (AM) bearer; PCell and / or PSCell cannot be deactivated; SCG change procedure can be used to change PSCell (for example, using security key change and RACH procedure); and / or bearer type change between split bearer and SCG bearer, or simultaneous configuration of SCG and split bearers may or may not be supported.

[0283] Regarding the interaction between the primary base station and the secondary base station for multiple connectivity, one or more of the following may be applied: the primary base station and / or the secondary base station may maintain the RRM measurement configuration of the wireless device; the primary base station may decide (for example, based on the received measurement report, traffic conditions and / or bearer type) to request the secondary base station to provide additional resources (for example, service cells) for the wireless device; upon receiving the request from the primary base station, the secondary base station may create / modify a container, which may result in the configuration of additional service cells for the wireless device (or determine that the secondary base station does not have available resources to do so); for UE capability coordination, the primary base station may provide (partial) AS configuration and UE capabilities to the secondary base station; the primary base station and the secondary base station may exchange information about UE configuration by adopting an RRC container (inter-node message) carried via an Xn message; the secondary base station may initiate reconfiguration of the secondary base station's existing service cell (for example, towards the PUCCH of the secondary base station); the secondary base station may decide which cell is the PSCell within the SCG; the primary base station may change or not change the content of the RRC configuration provided by the secondary base station; adding and / or re-adding a secondary base station to the SCG In the case of adding an SCell, the primary base station can provide the most recent (or latest) measurement results for one or more SCG cells; the primary base station and the secondary base station can receive information about SFN and / or each other's subframe offsets from OAM and / or via the Xn interface (for example, for the purpose of DRX alignment and / or identification of measurement gaps). In an example, when a new SCG SCell is added, dedicated RRC signaling can be used to send the required system information of the cell of the CA, except for the SFN obtained from the MIB of the PSCell of the SCG.

[0284] Fig.12 is an example diagram of a random access procedure. One or more events may trigger the random access procedure. For example, the one or more events may be at least one of: initial access from RRC_IDLE, an RRC connection reestablishment procedure, a handover, DL or UL data arrival during RRC_CONNECTED when the UL synchronization state is asynchronous, a transition from RRC_Inactive, and / or a request for other system information. For example, a PDCCH command, a MAC entity, and / or a beam failure indication may initiate the random access procedure.

[0285] In an example embodiment, the random access procedure may be at least one of a contention-based random access procedure and a contention-free random access procedure. For example, the contention-based random access procedure may include one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, the contention-free random access procedure may include one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

[0286] In an example, the base station may transmit (e.g., unicast, multicast, or broadcast) a RACH configuration 1210 to the UE via one or more beams. The RACH configuration 1210 may include one or more parameters indicating at least one of: a set of available PRACH resources for transmission of a random access preamble, an initial preamble power (e.g., a random access preamble initial reception target power), an RSRP threshold for selecting an SS block and a corresponding PRACH resource, a power ramp factor (e.g., a random access preamble power ramp step size), a random access preamble index, a maximum number of preamble transmissions, preamble groups A and B, a threshold (e.g., a message size) for determining a random access preamble group, a set of one or more random access preambles and corresponding PRACH resources (if any) for a system information request, a set of one or more random access preambles and corresponding PRACH resources (if any) for a beam failure recovery request, a time window for monitoring a RA response, a time window for monitoring a response to a beam failure recovery request, and / or a contention resolution timer.

[0287] In an example, Msg1 1220 may be one or more transmissions of a random access preamble. For a contention-based random access procedure, the UE may select an SS block with an RSRP above an RSRP threshold. If there is a random access preamble group B, the UE may select one or more random access preambles from group A or group B based on the potential Msg3 1240 size. If there is no random access preamble group B, the UE may select one or more random access preambles from group A. The UE may randomly (e.g., with equal probability or normal distribution) select a random access preamble index from one or more random access preambles associated with the selected group. If the base station semi-statistically configures the UE with an association between the random access preamble and the SS block, the UE may randomly select a random access preamble index from one or more random access preambles associated with the selected SS block and the selected group with equal probability.

[0288] For example, the UE may initiate a contention-free random access procedure based on a beam failure indication from a lower layer. For example, the base station may semi-statistically configure the UE with one or more contention-free PRACH resources for a beam failure recovery request associated with at least one of the SS blocks and / or CSI-RS. If at least one of the SS blocks having an RSRP higher than a first RSRP threshold among the associated SS blocks or at least one of the CSI-RS having an RSRP higher than a second RSRP threshold among the associated CSI-RS is available, the UE may select a random access preamble index corresponding to the selected SS block or CSI-RS from a set of one or more random access preambles for the beam failure recovery request.

[0289] For example, the UE may receive a random access preamble index from the base station via PDCCH or RRC for a contention-free random access procedure. If the base station does not configure the UE with at least one contention-free PRACH resource associated with an SS block or CSI-RS, the UE may select a random access preamble index. If the base station configures the UE with one or more contention-free PRACH resources associated with an SS block, and at least one SS block with an RSRP higher than a first RSRP threshold is available among the associated SS blocks, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If the base station configures the UE with one or more contention-free PRACH resources associated with a CSI-RS, and at least one CSI-RS with an RSRP higher than a second RSPR threshold is available among the associated CSI-RS, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

[0290] The UE may perform one or more Msg1 1220 transmissions by transmitting a selected random access preamble. For example, if the UE selects an SS block and is configured with an association between one or more PRACH opportunities and one or more SS blocks, the UE may determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected SS block. For example, if the UE selects a CSI-RS and is configured with an association between one or more PRACH opportunities and one or more CSI-RS, the UE may determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected CSI-RS. The UE may transmit the selected random access preamble to the base station via the selected PRACH opportunity. The UE may determine a transmit power for transmitting the selected random access preamble based at least on an initial preamble power and a power ramp factor. The UE may determine a RA-RNTI associated with the selected PRACH opportunity in which the selected random access preamble is transmitted. For example, the UE may not determine a RA-RNTI for a beam failure recovery request. The UE may determine the RA-RNTI based at least on an index of the first OFDM symbol and an index of a first slot of a selected PRACH opportunity and / or an uplink carrier index used for transmission of Msg1 1220 .

[0291] In an example, the UE may receive a random access response Msg 2 1230 from the base station. The UE may start a time window (e.g., ra-ResponseWindow) to monitor the random access response. For a beam failure recovery request, the base station may configure the UE with a different time window (e.g., bfr-ResponseWindow) to monitor the response to the beam failure recovery request. For example, the UE may start the time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at the start of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the preamble transmission. If the UE transmits multiple preambles, the UE may start the time window at the start of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the first preamble transmission. The UE may monitor the PDCCH of the cell for at least one random access response identified by the RA-RNTI or for at least one response to the beam failure recovery request identified by the C-RNTI while the timer of the time window is running.

[0292] In an example, if at least one random access response includes a random access preamble identifier corresponding to a random access preamble transmitted by the UE, the UE may consider that the reception of the random access response is successful. If the reception of the random access response is successful, the UE may consider that the contention-free random access procedure is successfully completed. If the contention-free random access procedure for a beam failure recovery request is triggered, the UE may consider that the contention-free random access procedure is successfully completed in the case where the PDCCH transmission is addressed to the C-RNTI. In an example, if at least one random access response includes a random access preamble identifier, the UE may consider that the random access procedure is successfully completed and may indicate receipt of an acknowledgment of a system information request for an upper layer. If the UE has signaled multiple preamble transmissions, the UE may stop transmitting the remaining preambles (if any) in response to successfully receiving the corresponding random access responses.

[0293] In an example, the UE may perform one or more Msg 3 1240 transmissions (e.g., for a contention-based random access procedure) in response to successful reception of a random access response. The UE may adjust the uplink transmission timing based on a timing advance command indicated by the random access response, and may transmit one or more transport blocks based on an uplink grant indicated by the random access response. The subcarrier spacing for PUSCH transmission of Msg3 1240 may be provided by at least one higher layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and transmit Msg3 1240 via PUSCH on the same cell. The base station may indicate the UL BWP for PUSCH transmission of Msg3 1240 via a system information block. The UE may retransmit Msg 3 1240 using HARQ.

[0294] In an example, multiple UEs may perform Msg 1 1220 by transmitting the same preamble to the base station and receiving the same random access response including an identity (e.g., TC-RNTI) from the base station. Contention resolution 1250 may ensure that the UE does not mistakenly use the identity of another UE. For example, contention resolution 1250 may be based on a C-RNTI on a PDCCH or a UE contention resolution identity on a DL-SCH. For example, if the base station assigns a C-RNTI to the UE, the UE may perform contention resolution 1250 based on the reception of a PDCCH transmission addressed to the C-RNTI. In response to detecting the C-RNTI on the PDCCH, the UE may deem contention resolution 1250 successful and may deem the random access procedure to have been successfully completed. If the UE does not have a valid C-RNTI, contention resolution may be addressed by adopting the TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, then the UE may consider contention resolution 1250 to be successful and the random access procedure to be successfully completed.

[0295] Fig.13 It is an example structure of a MAC entity according to aspects of an embodiment. In an example, a wireless device can be configured to operate in a multiple connectivity mode. A wireless device in RRC_CONNECTED with multiple RX / TX can be configured to utilize radio resources provided by multiple schedulers located in multiple base stations. Multiple base stations can be connected via non-ideal or ideal backhaul on an Xn interface. In an example, a base station among multiple base stations can act as a primary base station or a secondary base station. The wireless device can be connected to a primary base station and one or more secondary base stations. The wireless device can be configured with multiple MAC entities, for example, one MAC entity for a primary base station, and one or more other MAC entities for one or more secondary base stations. In an example, a configured service cell set for a wireless device can include two subsets: an MCG, which includes a service cell of a primary base station; and one or more SCGs, which include service cells of one or more secondary base stations. Fig.13 Shown is an example structure of a MAC entity when MCG and SCG are configured for a wireless device.

[0296] In an instance, at least one cell in an SCG may have a configured UL CC, where the cell of at least one cell may be referred to as a PSCell or a PCell of the SCG, or sometimes simply referred to as a PCell. The PSCell may be configured with PUCCH resources. In an instance, when an SCG is configured, there may be at least one SCG bearer or one separate bearer. In an instance, after a physical layer problem or a random access problem is detected on the PSCell, or after the number of RLC retransmissions associated with the SCG is reached, or after an access problem is detected on the PSCell during an SCG addition or SCG change: the RRC connection reestablishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the UE may notify the primary base station of the SCG failure type, and DL data delivery on the primary base station may be maintained.

[0297] In an example, the MAC sublayer may provide services such as data transfer and radio resource allocation to an upper layer (e.g., 1310 or 1320). The MAC sublayer may include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer may provide data transfer services on logical channels. In order to accommodate different types of data transfer services, multiple types of logical channels may be defined. Logical channels may support the transfer of specific types of information. The logical channel type may be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH, and DCCH may be control channels, and DTCH may be a traffic channel. In an example, a first MAC entity (e.g., 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In an example, a second MAC entity (e.g., 1320) may provide services on BCCH, DCCH, DTCH, and MAC control elements.

[0298] The MAC sublayer may anticipate services from the physical layer (e.g., 1330 or 1340), such as data transfer services, signaling of HARQ feedback, scheduling requests, or signaling of measurement values ​​(e.g., CQI). In an example, in dual connectivity, two MAC entities may be configured for the wireless device: one for the MCG and one for the SCG. The MAC entity of the wireless device may process multiple transport channels. In an example, a first MAC entity may process a first transport channel, including a PCCH of the MCG, a first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and one or more first RACHs of the MCG. In an example, a second MAC entity may process a second transport channel, including a second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more second RACHs of the SCG.

[0299] In an example, if a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs per MAC entity, and there may be multiple UL-SCHs as well as multiple RACHs. In an example, there may be one DL-SCH and UL-SCH on a SpCell. In an example, for a SCell, there may be one DL-SCH, zero or one UL-SCH, and zero or one RACH. The DL-SCH may support reception using different parameter sets and / or TTI durations within the MAC entity. The UL-SCH may also support transmission using different parameter sets and / or TTI durations within the MAC entity.

[0300] In an example, the MAC sublayer may support different functions and these functions may be controlled using control (e.g., 1355 or 1365) elements. Functions performed by the MAC entity may include mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g., 1352 or 1362) MAC SDUs from one or different logical channels to a transport block (TB) to be delivered to a physical layer on a transport channel (e.g., in uplink), demultiplexing (e.g., 1352 or 1362) MAC SDUs from a transport block (TB) delivered from a physical layer on a transport channel to one or different logical channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction by HARQ in uplink or downlink (e.g., 1363), and logical channel prioritization in uplink (e.g., 1351 or 1361). The MAC entity may handle a random access procedure (e.g., 1354 or 1364).

[0301] Fig.14 is an example diagram of a RAN architecture including one or more base stations. In an example, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) can be supported at a node. A base station (e.g., gNB 120A or 120B) can include a base station central unit (CU) (e.g., gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g., gNB-DU 1430A, 1430B, 1430C, or 1430D) (if functional separation is configured). The upper protocol layers of the base station can be located in the base station CU, and the lower layers of the base station can be located in the base station DU. The F1 interface (e.g., CU-DU interface) connecting the base station CU and the base station DU can be an ideal or non-ideal backhaul. F1-C can provide a control plane connection through the F1 interface, and F1-U can provide a user plane connection through the F1 interface. In an example, an Xn interface can be configured between the base station CUs.

[0302] In an example, the base station CU may include an RRC function, an SDAP layer, and a PDCP layer, and the base station DU may include an RLC layer, a MAC layer, and a PHY layer. In an example, various functional separation options between the base station CU and the base station DU are possible by locating different combinations of upper protocol layers (RAN functions) in the base station CU and different combinations of lower protocol layers (RAN functions) in the base station DU. The functional separation may support the flexibility of moving protocol layers between the base station CU and the base station DU according to service requirements and / or network environment.

[0303] In an instance, the functional separation options can be configured for each base station, each base station CU, each base station DU, each UE, each bearer, each slice layer, or at other granularity. In each base station CU separation, the base station CU can have a fixed separation option, and the base station DU can be configured to match the separation option of the base station CU. In each base station DU separation, the base station DU can be configured with different separation options, and the base station CU can provide different separation options for different base station DUs. In per-UE separation, the base station (base station CU and at least one base station DU) can provide different separation options for different wireless devices. In each bearer separation, different separation options can be used for different bearers. In each slice layer splicing, different separation options can be applied to different slice layers.

[0304] Fig.151 is an example diagram illustrating an RRC state transition of a wireless device. In an example, the wireless device may be in at least one of an RRC connected state (e.g., RRC connected 1530, RRC_Connected), an RRC idle state (e.g., RRC idle 1510, RRC_Idle), and / or an RRC inactive state (e.g., RRC inactive 1520, RRC_Inactive). In an example, in the RRC connected state, the wireless device may have at least one RRC connection with at least one base station (e.g., gNB and / or eNB), which may have a UE context of the wireless device. The UE context (e.g., wireless device context) may include at least one of an access layer context, one or more radio link configuration parameters, bearers (e.g., data radio bearers (DRBs), signaling radio bearers (SRBs), logical channels, QoS flows, PDU sessions, etc.), configuration information, security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In an example, in the RRC idle state, the wireless device may not have an RRC connection with the base station, and the UE context of the wireless device may not be stored in the base station. In an example, in the RRC inactive state, the wireless device may not have an RRC connection with the base station. The UE context of the wireless device may be stored in the base station, which may be referred to as an anchor base station (e.g., a last serving base station).

[0305] In an example, the wireless device may transition the UE RRC state between the RRC idle state and the RRC connected state in two ways (e.g., connection release 1540 or connection establishment 1550; or connection reestablishment) and / or between the RRC inactive state and the RRC connected state in two ways (e.g., connection deactivation 1570 or connection recovery 1580). In an example, the wireless device may transition its RRC state from the RRC inactive state to the RRC idle state (e.g., connection release 1560).

[0306] In an example, an anchor base station may be a base station that maintains a UE context (wireless device context) of a wireless device at least during a time period that the wireless device stays in a RAN notification area (RNA) of the anchor base station and / or the wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station to which a wireless device in an RRC inactive state was last connected in the latest RRC connected state, or a base station where the wireless device last performed an RNA update procedure. In an example, an RNA may include one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs.

[0307] In an example, the wireless device may transition the UE RRC state from the RRC connected state to the RRC inactive state in the base station. The wireless device may receive RNA information from the base station. The RNA information may include at least one of an RNA identifier, one or more cell identifiers of one or more cells of the RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a recovery identifier, etc.

[0308] In an instance, an anchor base station may broadcast a message (e.g., a RAN paging message) to a base station of the RNA to reach a wireless device in an RRC inactive state, and / or a base station receiving a message from the anchor base station may broadcast and / or multicast another message (e.g., a paging message) over an air interface to wireless devices in its coverage area, a cell coverage area, and / or a beam coverage area associated with the RNA.

[0309] In an example, when a wireless device in an RRC inactive state moves to a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may include a random access procedure and / or a UE context retrieval procedure for the wireless device. The UE context retrieval may include: a base station receiving a random access preamble from the wireless device; and the base station extracting a UE context of the wireless device from an old anchor base station. The extraction may include: sending a retrieve UE context request message including a recovery identifier to the old anchor base station, and receiving a retrieve UE context response message including the UE context of the wireless device from the old anchor base station.

[0310] In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on measurement results of at least one or more cells, cells that the wireless device may monitor RNA paging messages, and / or core network paging messages from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to restore an RRC connection and / or transmit one or more packets to a base station (e.g., to a network). In an example, if the selected cell belongs to an RNA different from the RNA of the wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if the wireless device in an RRC inactive state has one or more packets in a buffer to transmit to the network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell selected by the wireless device. The random access procedure may be performed using two messages (e.g., level 2 random access) and / or four messages (e.g., level 4 random access) between the wireless device and the base station.

[0311] In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may extract a UE context for the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a recovery identifier, and / or a cell identifier received from the wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device. In response to extracting the UE context, the base station may transmit a path switch request for the wireless device to a core network entity (e.g., AMF, MME, etc.). The core network entity may update a downlink tunnel endpoint identifier of one or more bearers established between a user plane core network entity (e.g., UPF, S-GW, etc.) and a RAN node (e.g., a base station) for the wireless device, for example, changing the downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.

[0312] The gNB may communicate with the wireless device via a wireless network that employs one or more new radio technologies. The one or more radio technologies may include at least one of: multiple technologies associated with a physical layer; multiple technologies associated with a media access control layer; and / or multiple technologies associated with a radio resource control layer. Example embodiments that enhance the one or more radio technologies may improve the performance of the wireless network. Example embodiments may increase system throughput or data transmission rate. Example embodiments may reduce battery consumption of the wireless device. Example embodiments may improve latency of data transmission between the gNB and the wireless device. Example embodiments may improve network coverage of the wireless network. Example embodiments may improve transmission efficiency of the wireless network.

[0313] Example downlink control information (DCI) will be discussed. In an example, the gNB may transmit DCI via PDCCH for at least one of: scheduling assignment / grant; slot format notification; preemption indication; and / or one or more power control commands. More specifically, the DCI may include at least one of: an identifier of a DCI format; one or more downlink scheduling assignments; one or more uplink scheduling grants; slot format indicator; preemption indication; power control for PUCCH / PUSCH; and / or power control for SRS.

[0314] In an example, the downlink scheduling assignment DCI may include parameters indicating at least one of: an identifier of a DCI format; a PDSCH resource indication; a transmission format; HARQ information; control information regarding a multiple antenna scheme; and / or a command for power control of a PUCCH.

[0315] In an example, the uplink scheduling grant DCI may include parameters indicating at least one of: an identifier of a DCI format; a PUSCH resource indication; a transport format; HARQ related information; and / or a power control command for the PUSCH.

[0316] In an example, different types of control information may correspond to different DCI message sizes. For example, supporting multiple beams and / or spatial multiplexing in the spatial domain and non-contiguous allocation of RBs in the frequency domain may require a larger scheduling message than an uplink grant that takes into account frequency-contiguous allocations. DCI may be categorized into different DCI formats, where a format corresponds to a certain message size and / or usage.

[0317] In an example, the wireless device may monitor one or more PDCCHs for detecting one or more DCIs having one or more DCI formats in a common search space or a wireless device-specific search space. In an example, the wireless device may monitor the PDCCH with a limited set of DCI formats to save power consumption. Typically, the wireless device consumes more power for each additional DCI format that the wireless device detects.

[0318] In an example, information in a DCI having a DCI format for downlink scheduling may include at least one of the following: an identifier of a DCI format; a carrier indicator; a frequency domain resource assignment; a time domain resource assignment; a bandwidth part indicator; a HARQ process number; one or more MCSs; one or more NDIs; one or more RVs; MIMO related information; a downlink assignment index (DAI); a PUCCH resource indicator; a PDSCH to HARQ_feedback timing indicator; a TPC for a PUCCH; an SRS request; and padding if necessary. In an example, the MIMO related information may include at least one of the following: a PMI; precoding information; a transport block swap flag; a power offset between a PDSCH and a reference signal; a reference signal scrambling sequence; a number of layers; and / or antenna ports for downlink transmission; and / or a transmit configuration indication (TCI).

[0319] In an instance, the information in a DCI having a DCI format for uplink scheduling may include at least one of: an identifier of the DCI format; a carrier indicator; a bandwidth part indication; a resource allocation type; a frequency domain resource assignment; a time domain resource assignment; an MCS; an NDI; a phase rotation of an uplink DMRS; precoding information; a CSI request; an SRS request; an uplink index / DAI; a TPC for a PUSCH; and / or padding if necessary.

[0320] In an example, the gNB may perform CRC scrambling for the DCI before transmitting the DCI via the PDCCH. The gNB may perform the CRC scrambling by adding a plurality of bits of at least one wireless device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, or TPC-SRS-RNTI) and CRC bits of the DCI in a binary manner. When detecting the DCI, the wireless device may check the CRC bits of the DCI. When the CRC is scrambled by the same bit sequence as the at least one wireless device identifier, the wireless device may receive the DCI.

[0321] In an example, to support wide bandwidth operation, the gNB may transmit one or more PDCCHs in different control resource sets ("core sets"). The gNB may transmit one or more RRC messages including configuration parameters for the one or more core sets. A core set may include at least one of: a first OFDM symbol; a number of consecutive OFDM symbols; a group of resource blocks; and / or a CCE to REG mapping. In an example, the gNB may transmit a PDCCH in a dedicated core set for a specific purpose, including, for example, for beam failure recovery confirmation.

[0322] In an example, a wireless device may monitor the PDCCH for detecting DCI in one or more configured core sets to reduce power consumption.

[0323] An example MAC PDU structure will now be discussed. The gNB may transmit one or more MAC PDUs to the wireless device. In an example, the MAC PDU may be a bit string whose length is byte aligned (e.g., 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 by the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0324] In an example, the MAC SDU may be a bit string whose length is byte-aligned (eg, a multiple of eight bits). In an example, the MAC SDU may be included in the MAC PDU starting from the first bit.

[0325] In an example, a MAC CE may be a bit string whose length is byte-aligned (eg, a multiple of eight bits).

[0326] In an example, the MAC subheader may be a bit string whose length is byte-aligned (eg, 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.

[0327] In an example, the MAC entity may ignore the value of the reserved bit in the DL MAC PDU.

[0328] 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; and / or a MAC subheader and padding. In an example, a MAC SDU may be of variable size. In an example, a MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0329] In an instance, 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 multiple-bit length; and / or an L field having a multiple-bit length.

[0330] Fig.16A An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Fig.16A 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. Fig. 16B An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Fig. 16B In an example MAC subheader, the LCID field may be six bits in length and the L field may be sixteen bits in length.

[0331] In an example, 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. Fig. 16C An example of a MAC subheader having an R field and an LCID field is shown. Fig. 16C In an example MAC subheader, the LCID field may be six bits in length and the R field may be two bits in length.

[0332] Fig.17A An example of a DL MAC PDU is shown. Fig.17AIn the example of , multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. A MAC subPDU including a MAC CE may be placed before any MAC subPDU including a MAC SDU or a MAC subPDU including padding.

[0333] Fig. 17B An example of a UL MAC PDU is shown. Fig. 17B In the example of , multiple MAC CEs, such as MAC CE 1 and 2, can be placed together. 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.

[0334] In an example, the MAC entity of the gNB may transmit one or more MAC CEs to the MAC entity of the wireless device. Fig.18 An example of multiple LCIDs that can be associated with one or more MAC CEs is shown. Fig.18 In an instance, 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 relationship activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI reported on PUCCH activation / deactivation MAC CE; TCI status indication of UE-specific PDCCH MAC CE; TCI status indication of UE-specific PDSCH MAC CE; non-periodic CSI triggering status sub-selection MAC CE; SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; UE 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 gNB 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 a MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0335] In an example, the MAC entity of the wireless device may transmit one or more MAC CEs to the MAC entity of the gNB. Fig.19 An 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 an example, a 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, the 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.

[0336] An example activation / deactivation mechanism for carrier aggregation will now be discussed. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may use the techniques of CA to simultaneously receive or transmit on one or more CCs, depending on the capabilities of the wireless device. In an example, a wireless device may support CA for adjacent CCs and / or for non-adjacent CCs. CCs may be organized into cells. For example, CCs may be organized into a primary cell (PCell) and one or more secondary cells (SCells).

[0337] When configured with CA, the wireless device may have one RRC connection with the network. During RRC connection establishment / reestablishment / handover, the cell providing NAS mobility information may be the serving cell. During the RRC connection establishment / handover procedure, the cell providing security input may be the serving cell. In an example, the serving cell may represent a PCell. In an example, the gNB 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.

[0338] When configured with CA, the base station and / or wireless device may employ an activation / deactivation mechanism of SCell to improve battery or power consumption of the wireless device. When the wireless device is configured with one or more SCells, the gNB may activate or deactivate at least one of the one or more SCells. After configuration of the SCell, the SCell may be deactivated immediately unless the SCell state associated with the SCell is set to "activated" or "dormant".

[0339] In an example, the wireless device may activate / deactivate the SCell in response to receiving the SCell activation / deactivation MAC CE.

[0340] In an example, the base station may transmit one or more messages including an SCell timer (eg, sCellDeactivationTimer) to the wireless device. In an example, the wireless device may deactivate the SCell in response to expiration of the SCell timer.

[0341] When the wireless device receives the SCell activation / deactivation MAC CE for activating 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.

[0342] In an example, in response to activating the SCell, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in a time slot when a SCell activation / deactivation MAC CE to activate the SCell has been received. 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.

[0343] When the wireless device receives the SCell activation / deactivation MAC CE to deactivate the activated SCell, the wireless device may deactivate the activated SCell.

[0344] In an example, when a first SCell timer (e.g., sCellDeactivationTimer) associated with an 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 a configured uplink grant type 2 associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device may additionally suspend one or more configured uplink grants of a configured uplink grant type 1 associated with the activated SCell. The wireless device may refresh a HARQ buffer associated with the activated SCell.

[0345] In an instance, when the SCell is deactivated, the wireless device may not perform operations including: transmitting SRS on the SCell; reporting CQI / PMI / RI / CRI for the SCell; transmitting on UL-SCH on the SCell; transmitting on 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 PUCCH on the SCell.

[0346] In an example, when at least one first PDCCH on the activated SCell indicates an uplink grant or a downlink assignment, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when at least one second PDCCH on a serving cell (e.g., a PCell or SCell configured with a PUCCH, i.e., a PUCCH SCell) that schedules the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell.

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

[0348] An example of SCell activation / deactivation MAC-CE will now be discussed. Fig. 20A An example of an octet SCell activation / deactivation MAC CE is shown. Fig.18 The first MAC PDU subheader ('111010' shown in '111010') may identify an octet SCell activation / deactivation MAC CE. An octet SCell activation / deactivation MAC CE may have a fixed size. An 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).

[0349] Fig. 20B An example of a four-octet SCell activation / deactivation MAC CE is shown. Fig.18The second MAC PDU subheader of the MAC PDU subheader ('111001' shown in '111001') can identify the 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).

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

[0351] An example of an SCell dormancy mechanism for carrier aggregation will now be discussed. When configured with CA, the base station and / or wireless device may employ a dormancy mechanism for the SCell to improve battery or power consumption of the wireless device and / or for fast SCell activation / addition. When the wireless device sleeps the SCell, the SCell may transition to a dormant state. In response to the SCell transitioning to a dormant state, the wireless device may: stop transmitting SRS on the SCell; report CQI / PMI / RI / PTI / CRI for the SCell according to the periodicity configured for the SCell in the dormant state; not transmit on the UL-SCH on the SCell; not transmit on the RACH on the SCell; not monitor the PDCCH on the SCell; not monitor the PDCCH for the SCell; and / or not transmit PUCCH on the SCell. In an example, when the SCell is in a dormant state, CSI for the SCell is reported and the PDCCH on / for the SCell is not monitored, and an "always updated" CSI for the SCell may be provided to the base station. With the always updated CSI, once the SCell transitions back to the active state, the base station can adopt fast and / or accurate channel adaptive scheduling on the SCell, thereby speeding up the activation procedure of the SCell. In an example, when the SCell is in a dormant state, reporting CSI for the SCell and not monitoring the PDCCH on / for the SCell can improve the battery or power consumption of the wireless device while still providing timely and / or accurate channel information feedback to the base station. In an example, the PCell / PSCell and / or PUCCH secondary cell may not be configured or transitioned to a dormant state.

[0352] When configured with one or more SCells, the gNB may activate, sleep, or deactivate at least one of the one or more SCells. In an example, the gNB may transmit one or more RRC messages including parameters indicating that at least one SCell is set to an active state, a dormant state, or an inactive state to the wireless device.

[0353] In an example, when the SCell is active, the wireless device may perform: 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 / SPUCCH transmission on the SCell.

[0354] In an example, when the SCell is in an inactive state, the wireless device may: not transmit SRS on the SCell; not report CQI / PMI / RI / CR for the SCell; not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell; not monitor PDCCH on the SCell; not monitor PDCCH for the SCell; and / or not transmit PUCCH on the SCell.

[0355] In an example, when the SCell is in a dormant state, the wireless device may: not transmit SRS on the SCell; report CQI / PMI / RI / CR for the SCell; not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell; not monitor PDCCH on the SCell; not monitor PDCCH for the SCell; and / or not transmit PUCCH on the SCell.

[0356] When configured with one or more SCells, the gNB may activate, sleep, or deactivate at least one of the one or more SCells. In an example, the gNB may transmit one or more MAC control elements including parameters indicating activation, deactivation, or sleep of at least one SCell to the wireless device.

[0357] In an example, the gNB may transmit a first MAC CE (e.g., an activation / deactivation MAC CE, such as a MAC CE) indicating activation or deactivation of at least one SCell to the wireless device. Fig. 20A or Fig. 20B ). Fig. 20A and / or Fig. 20B In the example, if the SCell with SCell index i has been configured, the Ci field can indicate the activation / deactivation status of the SCell with SCell index i. In an example, when the Ci field is set to one, the SCell with SCell index i can be activated. In an example, when the Ci field is set to zero, the SCell with SCell index i can be deactivated. In an example, if there is no SCell configured with SCell index i, the wireless device can ignore the Ci field. Fig. 20A and Fig. 20B In the example, the R field can indicate a reserved bit. In an example, the R field can be set to zero.

[0358] In an example, the gNB may transmit a second MAC CE (e.g., a dormancy MAC CE) to the wireless device indicating activation or dormancy of at least one SCell. In an example, the second MAC CE may be associated with a second LCID that is different from the first LCID of the first MAC CE (e.g., an activation / deactivation MAC CE). In an example, the second MAC CE may have a fixed size. In an example, the second MAC CE may consist of a single octet containing seven C fields and one R field. Fig.21A An example of a second MAC CE having a single octet is shown. In another example, the second MAC CE may consist of four octets containing 31 C fields and one R field. Fig. 21B An example of a second MAC CE with four octets is shown. In the example, the second MAC CE with four octets may be associated with a third LCID different from the second LCID of the second MAC CE with a single octet and / or the first LCID used to activate / deactivate the MAC CE. In the example, when there is no Scell ​​with a serving cell index greater than 7, a second MAC CE with one octet may be applied, otherwise a second MAC CE with four octets may be applied.

[0359] In an example, when the second MAC CE is received but the first MAC CE is not received, if there is an SCell configured with SCell index i, then Ci can indicate the sleep / activation state of the SCell with SCell index i, otherwise the MAC entity can ignore the Ci field. In an example, when Ci is set to "1", the wireless device can transition the SCell associated with SCell index i to a sleep state. In an example, when Ci is set to "0", the wireless device can activate the SCell associated with SCell index i. In an example, when Ci is set to "0" and the SCell with SCell index i is in a sleep state, the wireless device can activate the SCell with SCell index i. In an example, when Ci is set to "0" and the SCell with SCell index i is not in a sleep state, the wireless device can ignore the Ci field.

[0360] In an example, when both the first MAC CE (activation / deactivation MAC CE) and the second MAC CE (sleep MAC CE) are received, if there is an SCell configured with SCell index i, then the two Ci fields of the two MAC CEs can indicate the possible state transition of the SCell with SCell index i, otherwise the MAC entity can ignore the Ci field. Fig. 21C To explain the Ci fields of the two MAC CEs. Fig. 22An example of SCell state transition based on activation / deactivation of MAC CE and / or dormancy of MAC CE is shown.

[0361] When configured with one or more SCells, the gNB may activate, sleep, or deactivate at least one of the one or more SCells. In an example, the gNB and / or the MAC entity of the wireless device may maintain a SCell deactivation timer (e.g., sCellDeactivationTimer) for each configured SCell (except for the SCell configured with PUCCH / SPUCCH, if any) and deactivate the associated SCell upon its expiration.

[0362] In an example, the MAC entity of the gNB and / or the wireless device may maintain a SCell hibernation timer (e.g., sCellHibernationTimer) for each configured SCell (except for the SCell configured with PUCCH / SPUCCH, if any), and hibernate the associated SCell when the SCell hibernation timer expires if the SCell is active. In an example, when both the SCell deactivation timer and the SCell hibernation timer are configured, the SCell hibernation timer may take precedence over the SCell deactivation timer. In an example, when both the SCell deactivation timer and the SCell hibernation timer are configured, the gNB and / or the wireless device may ignore the SCell deactivation timer regardless of the expiration of the SCell deactivation timer.

[0363] In an example, the MAC entity of the gNB and / or the wireless device may maintain a dormant SCell deactivation timer (e.g., dormantSCellDeactivationTimer) for each configured SCell (except the SCell configured with PUCCH / SPUCCH, if any), and if the SCell is in a dormant state, deactivate the associated SCell when the dormant SCell deactivation timer expires.

[0364] Fig.23 An example of SCell state transition based on a first SCell timer (e.g., SCell deactivation timer or sCellDeactivationTimer), a second SCell timer (e.g., SCell hibernation timer or sCellHibernationTimer) and / or a third SCell timer (e.g., dormant SCell deactivation timer or dormantSCellDeactivationTimer) is shown.

[0365] In an example, when the activated SCell is configured to the MAC entity of the wireless device during SCell configuration, the MAC entity may activate the SCell. In an example, when the MAC entity of the wireless device receives one or more MAC CEs to activate the SCell, the MAC entity may activate the SCell. In an example, the MAC entity may start or restart the SCell deactivation timer associated with the SCell in response to activating the SCell. In an example, the MAC entity may start or restart the SCell sleep timer associated with the SCell (if configured) in response to activating the SCell. In an example, the MAC entity may trigger a PHR procedure in response to activating the SCell.

[0366] In an example, when the MAC entity of the wireless device receives one or more MAC CEs indicating deactivation of the SCell, the MAC entity may deactivate the SCell. In an example, in response to receiving one or more MAC CEs, the MAC entity may: deactivate the SCell; stop the SCell deactivation timer associated with the SCell; and / or refresh all HARQ buffers associated with the SCell.

[0367] In an example, when the SCell deactivation timer associated with the activated SCell expires and the SCell sleep timer is not configured, the MAC entity may: deactivate the SCell; stop the SCell deactivation timer associated with the SCell; and / or flush all HARQ buffers associated with the SCell.

[0368] In an example, when a first PDCCH on an activated SCell indicates an uplink grant or a downlink assignment, or a second PDCCH on a serving cell scheduling an activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, or a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment, the MAC entity may: restart an SCell deactivation timer associated with the SCell; and / or restart an SCell dormancy timer associated with the SCell (if configured). In an example, when the SCell is deactivated, a random access procedure in progress on the SCell may be aborted.

[0369] In an instance, for a configured SCell, when the MAC entity is configured with a SCell associated with a SCell state that is set to a dormant state when the SCell is configured, or when the MAC entity receives one or more MAC CEs for transitioning the SCell to a dormant state, the MAC entity may: transition the SCell to a dormant state; stop the SCell deactivation timer associated with the SCell; stop the SCell dormancy timer associated with the SCell (if configured); start or restart the dormant SCell deactivation timer associated with the SCell; and / or refresh all HARQ buffers associated with the SCell. In an instance, when the SCell dormancy timer associated with the activated SCell expires, the MAC entity may: sleep the SCell; stop the SCell deactivation timer associated with the SCell; stop the SCell dormancy timer associated with the SCell; and / or refresh all HARQ buffers associated with the SCell. In an instance, when the dormant SCell deactivation timer associated with the dormant SCell expires, the MAC entity may: deactivate the SCell; and / or stop the dormant SCell deactivation timer associated with the SCell. In an example, when the SCell is in a dormant state, a random access procedure in progress on the SCell may be terminated.

[0370] An example of QCL will be discussed. The base station may configure one or more TCI states for the wireless device through higher layer signaling. The number of one or more TCI states may depend on the capabilities of the wireless device. The wireless device may use one or more TCI states to decode the PDSCH based on the detected PDCCH. Each of the one or more TCI states may include an RS set TCI-RS-SetConfig. An RS set TCI-RS-SetConfig may contain one or more parameters. In an example, one or more parameters may be used to configure a quasi-co-location relationship between one or more reference signals in an RS set and a DM-RS port group of a PDSCH. An RS set may contain a reference to one or two DL RSs and an associated quasi-co-location type (QCL-Type) for each configured by a higher layer parameter QCL-Type. For the case of two DL RSs, the QCL type may be different. In an example, the references of the two DL RSs may be the same DL RS or different DL RSs. The quasi-co-location type indicated to the UE may be based on the higher layer parameter QCL-Type. The higher layer parameter QCL-Type can adopt one or a combination of the following types: QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}; QCL-TypeB': {Doppler shift, Doppler spread}; QCL-TypeC': {average delay, Doppler shift} and QCL-TypeD': {spatial Rx parameters}.

[0371] In an example, the wireless device may receive an activation command. The activation command may be used to map one or more TCI states to one or more code points of a DCI field transmission configuration indication (TCI). After the wireless device receives a higher layer configuration of the TCI state and before receiving the activation command, the wireless device may assume that one or more antenna ports in a DM-RS port group of a PDSCH of a serving cell are spatially quasi-co-located with the SSB. In an example, the SSB may be determined in an initial access procedure regarding Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, where applicable.

[0372] In an example, the wireless device may be configured with a higher layer parameter TCI-PresentInDCI by the base station. When the higher layer parameter TCI-PresentInDCI is set to 'enabled' for a CORESET scheduling PDSCH, the wireless device may assume that the TCI field is present in the DL DCI of the PDCCH transmitted on the CORESET. When the higher layer parameter TCI-PresentInDCI is set to 'disabled' for a CORESET scheduling PDSCH or a PDSCH scheduled by DCI format 1_0, for determining PDSCH antenna port quasi co-location, the wireless device may assume that the TCI state for PDSCH is the same as the TCI state applied to the CORESET for PDCCH transmission.

[0373] When the higher layer parameter TCI-PresentinDCI is set to 'enabled', the wireless device may use one or more TCI states to determine PDSCH antenna port quasi-co-location based on the value of the 'transmit configuration indication' field in the detected PDCCH with DCI. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold threshold-scheduling-offset, then the wireless device may assume that the antenna ports of one DM-RS port group of the PDSCH of the serving cell are quasi-co-located with one or more RSs in the RS set relative to one or more QCL type parameters given by the indicated TCI state. In an example, the threshold may be based on UE capabilities. When the higher layer parameter TCI-PresentInDCI = 'enabled' and the higher layer parameter TCI-PresentInDCI = 'disabled', if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold threshold-scheduling-offset, then the wireless device may assume that the antenna ports of one DM-RS port group of the PDSCH of the serving cell are quasi co-located based on the TCI state indicated by the PDCCH quasi co-location for the lowest CORESET-ID in the latest time slot configured for one or more CORESETs for the UE. If all configured TCI states do not contain QCL-TypeD', then the wireless device may derive other QCL assumptions for its scheduled PDSCH from the indicated TCI state regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0374] Examples of BFR procedures will be discussed. The gNB and / or wireless device may have multiple antennas to support high data rate transmission in the NR system. When configured with multiple antennas, the wireless device may perform one or more beam management procedures, such as Fig. 9B shown.

[0375] The wireless device may perform downlink beam management based on one or more CSI-RS and / or one or more SSBs. During the beam management procedure, the wireless device may measure the channel quality of a beam pair link. The beam pair link may include a transmit beam from the gNB and a receive beam at the wireless device. When multiple beams associated with multiple CSI-RS or SSBs are configured, the wireless device may measure multiple beam pair links between the gNB and the wireless device.

[0376] In an example, the wireless device may transmit one or more beam management reports to the gNB. In the beam management report, the wireless device may indicate one or more beam pair quality parameters, including at least: one or more beam identities; RSRP; PMI / CQI / RI of at least a subset of the configured multiple beams.

[0377] In an example, the gNB and / or wireless device may perform downlink beam management procedures on one or more transmit and receive points (TRPs), such as Fig. 9B Based on the beam management report of the wireless device, the gNB may transmit a signal to the wireless device indicating that the new beam pair link is the serving beam. The gNB may transmit the PDCCH and PDSCH to the wireless device using the serving beam.

[0378] In an example, the wireless device or the gNB may trigger a beam failure recovery mechanism. The wireless device may trigger a beam failure recovery (BFR) procedure, for example, when at least one beam failure occurs. In an example, a beam failure may occur when the quality of the beam pair link of at least one PDCCH falls below a threshold. The threshold may be an RSRP value (e.g., -140 dBm, -110 dBm) or an SINR value (e.g., -3 dB, -1 dB), which may be configured in an RRC message.

[0379] Fig.24A An example of a first beam failure scenario is shown. In the example, the gNB may transmit a PDCCH from a transmit (Tx) beam from a TRP to a receive (Rx) beam of a wireless device. When the PDCCH on a beam-pair link (between the gNB's Tx beam and the wireless device's Rx beam) has a value lower than a threshold RSRP / SINR value due to the beam-pair link being blocked (e.g., by a moving car or building), the gNB and the wireless device may initiate a beam failure recovery procedure on the TRP.

[0380] Fig. 24B An example of a second beam failure scenario is shown. In the example, the gNB may transmit the PDCCH from the beam from the first TRP to the wireless device. When the PDCCH on the beam is blocked, the gNB and the wireless device may initiate a beam failure recovery procedure on a new beam on the second TRP.

[0381] In an example, the wireless device may measure the quality of a beam-to-link using one or more RSs. The one or more RSs may be one or more SSBs, or one or more CSI-RS resources. The CSI-RS resources may be identified by a CSI-RS resource index (CRI). In an example, the quality of a beam-to-link may be defined as an RSRP value, or a reference signal received quality (e.g., RSRQ) value, and / or a CSI (e.g., SINR) value measured on an RS resource. In an example, the gNB may indicate whether the RS resource used to measure the quality of a beam-to-link is quasi co-located (QCL) with a DM-RS of a PDCCH. When the channel characteristics of a transmission from an RS to a wireless device and a transmission from a PDCCH to a wireless device are similar or identical under a configured standard, the RS resource and the DM-RS of the PDCCH may be referred to as a QCL. In an example, when the Doppler shift and / or Doppler shift of the channel of a transmission from an RS to a wireless device and a transmission from a PDCCH to a wireless device are the same, the RS resource and the DM-RS of the PDCCH may be referred to as a QCL.

[0382] In an example, the wireless device may monitor PDCCH on M beam pair links simultaneously, where M≥1 and the value of M may depend on at least the capability of the wireless device. In an example, monitoring PDCCH may include detecting DCI via PDCCH transmitted on a common search space and / or a wireless device-specific search space. In an example, monitoring multiple beam pair links may increase robustness against beam pair link blocking. In an example, the gNB may transmit one or more messages including parameters that instruct the wireless device to monitor PDCCH on different beam pair links in different OFDM symbols.

[0383] In an example, the gNB may transmit one or more RRC messages or MAC CEs including parameters indicating the Rx beam settings of the wireless device to monitor the PDCCH on multiple beam pair links. The gNB may transmit one or more DL RS antenna ports and an indication of the spatial QCL between one or more DL RS antenna ports for demodulating the DL control channel. In an example, the indication may be a parameter in a MAC CE or an RRC message or a DCI and / or a combination of these signalings.

[0384] In an example, to receive a data packet on the PDSCH, the gNB may indicate spatial QCL parameters between one or more DL RS antenna ports and one or more DM-RS antenna ports of a DL data channel. The gNB may transmit a DCI including parameters indicating the QCL between one or more RS antenna ports and one or more DM-RS antenna ports.

[0385] In an example, when the gNB transmits a signal indicating a QCL parameter between the CSI-RS and the DM-RS for the PDCCH, the wireless device may measure the beam pair link quality based on the CSI-RS and the DM-RS for the PDCCH QCL. In an example, when multiple adjacent beam failures occur, the wireless device may initiate a BFR procedure.

[0386] In an example, when the BFR procedure is initiated, the wireless device transmits a BFR signal to the gNB on an uplink physical channel. The gNB may transmit a DCI via the PDCCH in the core set in response to receiving the BFR signal on the uplink physical channel. When the DCI is received via the PDCCH in the core set, the wireless device may consider the BFR procedure to be successfully completed.

[0387] In an example, the gNB may transmit one or more messages including configuration parameters for an uplink physical channel or a signal for transmitting a beam failure recovery request. The uplink physical channel or signal may be based on one of the following: contention-free PRACH (BFR-PRACH), which may be a resource orthogonal to resources of other PRACH transmissions; PUCCH (BFR-PUCCH); and / or contention-based PRACH resources (CF-PRACH). The combination of these candidate signals / channels may be configured by the gNB. In an example, when multiple resources for BFR signals are configured, the wireless device may autonomously select a first resource for transmitting the BFR signal. In an example, when BFR-PRACH resources, BFR-PUCCH resources, and CF-PRACH resources are configured, the wireless device may select a BFR-PRACH resource for transmitting the BFR signal. In an example, when BFR-PRACH resources, BFR-PUCCH resources, and CF-PRACH resources are configured, a message indicating the resources for transmitting the BFR signal may be transmitted to the wireless device.

[0388] In an example, the gNB may transmit a response to the wireless device after receiving the one or more BFR signals. The response may include a CRI associated with the candidate beam indicated by the wireless device in the one or more BFR signals.

[0389] Examples of BFR procedures.

[0390] In NR systems, when multiple beams are configured, the gNB and / or the wireless device may perform one or more beam management procedures. For example, if one or more beam pair links between the gNB and the wireless device fail, the wireless device may perform a BFR procedure.

[0391] Fig.25An example flow chart of a BFR procedure is shown. A wireless device may receive one or more RRC messages including BFR parameters. The one or more RRC messages may include an RRC message (e.g., an RRC connection reconfiguration message, or an RRC connection reestablishment message, or an RRC connection setup message). The wireless device may detect at least one beam failure based on at least one of the BFR parameters. If configured in response to detecting at least one beam failure, the wireless device may start a first timer. The wireless device may select a selected beam in response to detecting at least one beam failure. The selected beam may be a beam with good channel quality (e.g., RSRP, SINR, or BLER) from a set of candidate beams. The candidate beams may be identified by a set of reference signals (e.g., SSB or CSI-RS). The wireless device may transmit at least a first BFR signal to the gNB in ​​response to selecting the selected beam. At least the first BFR signal may be associated with the selected beam. At least the first BFR signal may be a preamble transmitted on a PRACH resource, or a beam failure request (e.g., similar to a scheduling request) signal transmitted on a PUCCH resource, or a beam indication transmitted on a PUCCH / PUSCH resource. The wireless device may transmit at least the first BFR signal using a transmit beam corresponding to a receive beam associated with the selected beam. The wireless device may start a response window in response to transmitting at least the first BFR signal. In an example, the response window may be a timer having a value configured by the gNB. While the response window is running, the wireless device may monitor the PDCCH in the first core set. The first core set may be associated with a BFR procedure. In an example, the wireless device may monitor the PDCCH in the first core set under the condition that at least the first BFR signal is transmitted. The wireless device may receive a first DCI via the PDCCH in the first core set while the response window is running. The wireless device may consider the BFR procedure to be successfully completed when the first DCI is received via the PDCCH in the first core set before the response window expires. If configured in response to the BFR procedure being successfully completed, the wireless device may stop the first timer. The wireless device may stop the response window in response to the BFR procedure being successfully completed.

[0392] In an example, when the response window expires and the wireless device does not receive DCI, the wireless device may increment the number of transmissions, where the number of transmissions is initialized to a first number (e.g., 0) before the BFR procedure is triggered. If the number of transmissions indicates a number less than the configured maximum number of transmissions, the wireless device may repeat one or more actions including at least one of the following: BFR signal transmission; initiating a response window; monitoring the PDCCH; incrementing the number of transmissions if no response is received during the response window. If the number of transmissions indicates a number equal to or greater than the configured maximum number of transmissions, the wireless device may declare that the BFR procedure was not successfully completed.

[0393] The MAC entity of the wireless device may be configured by the RRC with a beam failure recovery procedure. The beam failure recovery procedure may be used to indicate a new (e.g., candidate) SSB or CSI-RS to a serving base station when a beam failure is detected. A beam failure may be detected on one or more serving SSBs / CSI-RS of a serving base station. In an example, a beam failure may be detected by counting beam failure instance indications from lower layers (e.g., a PHY layer) of the wireless device to the MAC entity.

[0394] In an example, RRC may configure one or more parameters for the wireless device in BeamFailureRecoveryConfig for beam failure detection and recovery procedures. The one or more parameters may include at least: beamFailureInstanceMaxCount for beam failure detection; beamFailureDetectionTimer for beam failure detection; beamFailureRecoveryTimer for beam failure recovery procedure; rsrp-ThresholdSSB: RSRP threshold for beam failure recovery; PowerRampingStep for beam failure recovery; preambleReceivedTargetPower for beam failure recovery; preambleTxMax for beam failure recovery; and ra-ResponseWindow. The ra-ResponseWindow may be a time window to monitor one or more responses for beam failure recovery using a contention-free random access preamble.

[0395] Fig.26 An example of a beam failure instance (BFI) indication is shown. In an example, the wireless device may use at least one UE variable for beam failure detection. BFI_COUNTER may be one of the at least one UE variable. BFI_COUNTER may be a counter for beam failure instance indication. BFI_COUNTER may be initially set to zero.

[0396] In an example, if the MAC entity of the wireless device receives a beam failure instance indication from a lower layer (e.g., PHY) of the wireless device, the wireless device may start or restart the beamFailureDetectionTimer (e.g., Fig.26 In addition to starting or restarting the beamFailureDetectionTimer, the wireless device may also increment the BFI_COUNTER by one (e.g., Fig.26 time T, 2T, 5T).

[0397] In an example, if configured with BeamFailureRecoveryConfig, the wireless device may initiate a random access procedure for beam failure recovery (e.g., on SpCell) in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount. In an example, if configured with BeamFailureRecoveryConfig, the wireless device may start beamFailureRecoveryTimer (if configured) in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount. In response to initiating the random access procedure, the wireless device may apply one or more parameters in BeamFailureRecoveryConfig (e.g., powerRampingStep, preambleReceivedTargetPower, and preambleTransMax). In an example, the random access procedure may be a contention-free random access procedure.

[0398] In an example, if BeamFailureRecoveryConfig is not configured, the wireless device may initiate a random access procedure for beam failure recovery (eg, on the SpCell) in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount. In an example, the random access procedure may be a contention-based random access procedure.

[0399] In the example, Fig.26 In the example, when a first number (eg, 3) is reached, the wireless device may initiate a random access procedure at time 6T.

[0400] In an example, if beamFailureDetectionTimer expires, the wireless device may set BFI_COUNTER to zero (e.g., Fig.26 The time is between 3T and 4T).

[0401] In an example, if a random access procedure (eg, contention-free random access or contention-based random access) is successfully completed, the wireless device may deem that the beam failure recovery procedure is successfully completed.

[0402] In an example, if the random access procedure (eg, contention-free random access) completes successfully, the wireless device may stop the beamFailureRecoveryTimer (if configured).

[0403] If the MAC entity of the wireless device transmits a contention-free random access preamble for a beam failure recovery request, the MAC entity may start the ra-ResponseWindow at the first PDCCH opportunity at the end of the transmission of the contention-free random access preamble. The ra-ResponseWindow may be configured in the BeamFailureRecoveryConfig. When the ra-ResponseWindow is running, the wireless device may monitor at least one PDCCH (e.g., the PDCCH of the SpCell) for a response to the beam failure recovery request. The beam failure recovery request may be identified by the C-RNTI.

[0404] In an instance, if a MAC entity of the wireless device receives notification of reception of at least one PDCCH transmission from a lower layer of the wireless device, and if at least one PDCCH transmission is addressed to the C-RNTI, and if the MAC entity transmits a contention-free random access preamble for a beam failure recovery request, then the wireless device can consider the random access procedure to be successfully completed.

[0405] In an example, the wireless device may initiate a contention-based random access preamble for a beam failure recovery request. When the wireless device transmits Msg3, the MAC entity of the wireless device may start a ra-ContentionResolutionTimer. The ra-ContentionResolutionTimer may be configured by RRC. In response to starting the ra-ContentionResolutionTimer, the wireless device may monitor at least one PDCCH while the ra-ContentionResolutionTimer is running. In an example, if the MAC entity receives a notification of reception of at least one PDCCH transmission from a lower layer of the wireless device; if a C-RNTI MAC-CE is included in Msg3; if a random access procedure for beam failure recovery is initiated and at least one PDCCH transmission is addressed to the C-RNTI of the wireless device, then the wireless device may consider that the random access procedure is successfully completed. In response to the successful completion of the random access procedure, the wireless device may stop the ra-ContentionResolutionTimer.

[0406] In an example, if the random access procedure of beam failure recovery is successfully completed, the wireless device may deem that the beam failure recovery is successfully completed.

[0407] An example of a BFR procedure will be discussed. The wireless device may configure a first set of periodic CSI-RS resource configuration indices for a serving cell via a higher layer parameter Beam-Failure-Detection-RS-ResourceConfig (e.g., failureDetectionResources). A second set of CSI-RS resource configuration indices and / or SS / PBCH block indices may be additionally configured for the wireless device via a higher layer parameter Candidate-Beam-RS-List (e.g., candidateBeamRSList). In an example, the first set and / or the second set may be used for radio link quality measurements on the serving cell. If the higher layer parameter Beam-Failure-Detection-RS-ResourceConfig is not provided to the wireless device, the wireless device may determine the first set to include SS / PBCH block indices and periodic CSI-RS resource configuration indices. In an example, the SS / PBCH block indices and the periodic CSI-RS resource configuration indices may have the same value as one or more RS indices in one or more RS sets. In an example, one or more RS indices in one or more RS sets may be indicated by one or more TCI states. In an example, one or more TCI states may be used for each set of control resources that the wireless device is configured to monitor the PDCCH.The wireless device may expect a single port RS in the first set.

[0408] In an example, the wireless device may expect the first periodic CSI-RS resource configuration set to include up to two RS indices. In an example, if the first periodic CSI-RS resource configuration set includes two RS indices, then the first periodic CSI-RS resource configuration set may include one or more RS indices with a QCL-TypeD configuration. In an example, the wireless device may expect a single port RS in the first periodic CSI-RS resource configuration set.

[0409] In an example, the first threshold (e.g., Qout, LR) may correspond to a first default value of a higher layer parameter RLM-IS-OOS-thresholdConfig (e.g., rlmInSyncOutOfSyncThreshold). In an example, the second threshold (e.g., Qin, LR) may correspond to a second default value of a higher layer parameter Beam-failure-candidate-beam-threshold (e.g., rsrp-ThresholdSSB).

[0410] In an example, a physical layer in the wireless device may evaluate a first radio link quality based on a first set of periodic CSI-RS resource configurations relative to a first threshold. For the first set, the wireless device may evaluate the first radio link quality based on a periodic CSI-RS resource configuration or SS / PBCH block. In an example, the periodic CSI-RS resource configuration or SS / PBCH block may be associated with at least one DM-RS received by a PDCCH monitored by the wireless device (e.g., quasi co-located).

[0411] In an example, the wireless device may apply the second threshold to a first L1-RSRP measurement obtained from one or more SS / PBCH blocks. In an example, the wireless device may apply the second threshold to a second L1-RSRP measurement obtained for one or more periodic CSI-RS resources after scaling the corresponding CSI-RS received power by a value provided by a higher layer parameter Pc_SS (e.g., powerControlOffsetSS).

[0412] In an example, the wireless device may evaluate a first radio link quality of a first set. When the first radio link quality of all corresponding resource configurations in the first set is worse than a first threshold (e.g., higher BLER, lower SINR, lower L1-RSRP, etc.), the physical layer in the wireless device may provide an indication to a higher layer (e.g., MAC). In an example, the wireless device may evaluate the first radio link quality using all corresponding resource configurations in the first set. When the first radio link quality is worse than a first threshold with a first periodicity, the physical layer may notify a higher layer (e.g., MAC, RRC). The first periodicity may be determined by the maximum value between the shortest periodicity of the periodic CSI-RS configuration or SS / PBCH block in the first set and X (e.g., 2 milliseconds). In an example, the wireless device may evaluate the periodic CSI-RS configuration or SS / PBCH block for the first radio link quality.

[0413] In an example, in response to a request from a higher layer (e.g., MAC), the wireless device may provide a periodic CSI-RS configuration index and / or SS / PBCH block index from a second set to the higher layer. The wireless device may additionally provide a corresponding L1-RSRP measurement greater than or equal to a second threshold to the higher layer.

[0414] A control resource set (core set) may be provided / configured for a wireless device via a link to a search space set. In an example, the search space set may be provided by a higher layer parameter recoverySearchSpaceId. The search space may be used to monitor a PDCCH in the control resource set. In an example, if the wireless device is provided by a higher layer parameter recoverySearchSpaceId, then the wireless device may not expect to be provided with a second search space set for monitoring the core set. In an example, the core set may be associated with a search space set provided by a higher layer parameter recoverySearchSpaceId.

[0415] The wireless device may receive a configuration for a PRACH transmission from a higher layer (e.g., MAC) via the parameter PRACH-ResourceDedicatedBFR. For a PRACH transmission in slot n, and based on the antenna port quasi-co-location parameters associated with a periodic CSI-RS configuration or an SS / PBCH block with a first RS index, the wireless device may monitor the PDCCH in a search space set (e.g., provided by a higher layer parameter recoverySearchSpaceId) for detecting a DCI format initiated from slot n+4 within a window. The window may be configured by a higher layer parameter BeamFailureRecoveryConfig. The DCI format may have a CRC scrambled by a C-RNTI. In an example, the first RS index may be provided by a higher layer.

[0416] In an example, for PDCCH monitoring and for corresponding PDSCH reception, the wireless device may assume the same antenna port quasi co-location parameters as the first RS index (e.g., as used for monitoring PDCCH) until the wireless device receives activation for TCI states or parameters TCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList through higher layers.

[0417] In an example, after the wireless device detects a DCI format with a CRC scrambled by a C-RNTI in a search space set (e.g., provided by a higher layer parameter recoverySearchSpaceId), the wireless device may monitor PDCCH candidates in the search space set until the wireless device receives a MAC-CE activation command for a TCI state or higher layer parameters TCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList.

[0418] In an example, if a core set for a search space set is not provided to the wireless device (e.g., provided by a higher layer parameter recoverySearchSpaceId), then the wireless device may not expect to receive a PDCCH command triggering a PRACH transmission. In an example, the wireless device may initiate a contention-based random access procedure for beam failure recovery in response to not being provided a core set.

[0419] In an example, if the higher layer parameter recoverySearchSpaceId is not provided for the wireless device, the wireless device may not expect to receive a PDCCH command triggering a PRACH transmission. In an example, the wireless device may initiate a contention-based random access procedure for beam failure recovery in response to not being provided with the higher layer parameter recoverySearchSpaceId.

[0420] In an example, the wireless device may provide a first set of reference signal (RS) resources (eg, SSB, CSI-RS) for a cell (eg, SCell, PCell, BWP) via a first higher layer parameter (eg, failureDetectionResources).

[0421] In an example, the wireless device may additionally provide the first threshold for the cell via a second higher layer parameter (eg, rlmInSyncOutOfSyncThreshold).

[0422] In an example, the wireless device may additionally provide one or more parameters for the cell via a third higher layer parameter (e.g., BeamFailureRecoveryConfig). The third higher layer parameter may be used for beam failure detection and / or beam failure recovery procedures for the cell. In an example, the one or more parameters may include at least: beamFailureInstanceMaxCount for beam failure detection, beamFailureDetectionTimer for beam failure detection, and beamFailureRecoveryTimer for beam failure recovery procedures.

[0423] In an example, a physical layer in the wireless device may evaluate a first radio link quality (e.g., BLER, L1-RSRP) based on a first RS resource set relative to a first threshold. When the first radio link quality is worse than the first threshold (e.g., higher BLER, lower SINR, lower L1-RSRP, etc.), the physical layer may provide a beam failure instance (BFI) indication to a medium access (MAC) entity of the wireless device.

[0424] In an example, the physical layer may provide the BFI indication to the MAC entity at a first periodicity. The first periodicity may be determined by a maximum value of a period of the RS in the first RS resource set and a second value (e.g., 2 milliseconds). In an example, in the first RS resource set, the RS may have the shortest periodicity. In an example, the second value may be configured by a higher layer (e.g., RRC). In an example, the second initial value may be predetermined / fixed. In an example, Fig. 27 In the example, the periodicity is T1.

[0425] In an example, in response to receiving a BFI indication from the physical layer, the MAC entity may set the BFI_COUNTER (e.g., Fig.26 The BFI_COUNTER in the wireless device may be incremented by one. The BFI_COUNTER may be a variable used by the wireless device. The BFI_COUNTER may be a counter indicated by the BFI. The BFI_COUNTER may be initially set to zero.

[0426] In an example, the MAC entity may start or restart the beamFailureDetectionTimer in response to receiving a BFI indication from the physical layer.

[0427] In an example, beamFailureDetectionTimer may expire. The wireless device may set BFI_COUNTER to zero in response to expiration of beamFailureDetectionTimer.

[0428] In an example, if configured with a third higher layer parameter, the wireless device may initiate a random access procedure for beam failure recovery of the cell in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount.

[0429] In an example, if configured with a third higher layer parameter, the wireless device may start beamFailureRecoveryTimer (if configured) in response to initiating a random access procedure (or in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount). In an example, the random access procedure may be a contention-free random access procedure.

[0430] In an example, if the third higher layer parameter is not configured, the wireless device may initiate a random access procedure for beam failure recovery in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount. In an example, the random access procedure may be a contention-based random access procedure.

[0431] In an example, a base station may configure a wireless device with one or more cells including a cell (eg, an SCell). In an example, a base station may activate, dormant, or deactivate a cell.

[0432] In an example, the base station may transmit one or more MAC CEs to the wireless device for transitioning the cell to a dormant state (eg, Fig. 22 ). In response to receiving one or more MAC CEs, the wireless device may transition the cell to a dormant state.

[0433] In an example, the base station may transmit one or more RRC messages including parameters. The parameters may indicate a scell state indicator (e.g., sCellState) associated with the cell. In an example, the scell state indicator may be set to a dormant state. In response to setting the scell state indicator to a dormant state, the wireless device may transition the cell to a dormant state.

[0434] In an example, an SCell dormancy timer (e.g., sCellHibernationTimer) associated with a cell may expire. In response to the SCell dormancy timer expiring, the wireless device may transition the cell to a dormant state (e.g., Fig.23 ).

[0435] In an example, when a cell is in a dormant state, the wireless device may not monitor the PDCCH on the cell. In an example, when a cell is in a dormant state, the wireless device may not monitor the PDCCH of the cell.

[0436] In an example, the wireless device may (re)start a dormant SCell deactivation timer (eg, dormantSCellDeactivationTimer) of the cell in response to transitioning the cell to a dormant state.

[0437] Fig. 27 An example embodiment is shown. In an example, at time Ta, the wireless device may transition the cell to a dormant state. In an example, the wireless device may not monitor the PDCCH in the dormant state (e.g., at Fig. 27 The wireless device is in a sleep state (e.g., between Ta and Tb). Fig. 27 In the dormant state (e.g., between Ta and Tb in FIG. 1 ), one or more downlink signals may not be received. Fig. 27 The wireless device may not evaluate the first radio link quality based on the first RS resource set relative to the first threshold.

[0438] In an example, the wireless device may not perform beam failure detection in the sleep state. The beam failure detection may include evaluating the first radio link quality based on the first RS resource set relative to the first threshold. In an example, the duration of the sleep state may be long (e.g., 50, 100, 500 milliseconds). In an example, not performing beam failure detection may enhance power saving of the wireless device.

[0439] In an example, in the dormant state, the wireless device may evaluate a second radio link quality of a subset of the first set of RS resources. In an example, a BFI indication based on the second radio link quality may be unreliable.

[0440] In an example, an instance of a BFI indication may be in a dormant state (e.g., Fig. 27 In an example, when the wireless device does not monitor the PDCCH, the physical layer may not send a BFI indication to the MAC entity (e.g., Fig. 27 In an example, when the wireless device is in a sleep state (e.g., in Fig. 27 The physical layer may not send a BFI indication for the cell to the MAC entity (e.g., between Ta and Tb in Fig. 27 3T1 in). In an example, not sending a BFI indication may be in response to not monitoring a PDCCH in a dormant state.

[0441] In an example, the physical layer may not be in a dormant state (e.g., Fig. 27 In the example, beamFailureDetectionTimer (e.g., in Fig. 27 The BFR timer in the example may be responsive to not receiving a BFI indication (e.g., Fig. 27 In an example, the wireless device may set the BFI COUNTER to zero in response to the beamFailureDetectionTimer expiring. Setting the BFI_COUNTER to zero may delay the initiation of the beam failure recovery procedure for the cell. For example, Fig. 27 In the example, beam failure recovery may be initiated at time (k+2)*T1 instead of at time k*T1.

[0442] In an example, the first RS resource set may have a first radio link quality worse than a first threshold in the dormant state (e.g., higher BLER, lower SINR, lower L1-RSRP, etc.). In that case, not providing a BFI indication in the dormant state may not reflect the actual radio link quality of one or more downlink control channels associated with the first RS resource set (QCL).

[0443] In an example, the physical layer may provide a BFI indication to a MAC entity in a dormant state. In an example, the BFI indication in the dormant state may be the same as the previous BFI indication. In an example, Fig. 27 In the example, there may be an instance of a BFI indication period in the sleep state (e.g., at time 3T1). In the example, if a second BFI indication is provided in a previous instance of the BFI indication period (e.g., at time 2T1), the physical layer may provide a BFI indication to the MAC entity in the sleep state (e.g., at time 3T1). In the example, if a second BFI indication is not provided in a previous instance of the BFI indication period (e.g., at time 2T1), the physical layer may not provide a BFI indication to the MAC entity in the sleep state (e.g., at time 3T1).

[0444] In an example, providing a BFI indication in a sleep state may enable the BFI_COUNTER to not be reset during the sleep state. In an example, not resetting the BFI_COUNTER in the sleep state may result in a faster BFR procedure. In an example, the BFI_COUNTER may reach beamFailureInstanceMaxCount faster. In an example, in response to the BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount, the wireless device may initiate a random access procedure for beam failure recovery. In an example, initiating a random access may avoid a radio link failure (RLF).

[0445] In an example, the physical layer of the wireless device may not provide a BFI indication to the MAC entity of the wireless device in the sleep state. In an example, the beamFailureDetectionTimer may expire in response to not providing the BFI indication. In an example, when the beamFailureDetectionTimer expires in the sleep state, in response to the wireless device being in the sleep state, the wireless device may not set the BFI_COUNTER to zero.

[0446] In an example, the physical layer of the wireless device may not send a BFI indication to the MAC layer of the wireless device in the sleep state. In an example, the beamFailureDetectionTimer may expire in response to not providing a BFI indication. The wireless device may reset the BFI_COUNTER to zero in response to the beamFailureDetectionTimer expiring.

[0447] In an example, the wireless device may stop / reset the beamFailureDetectionTimer in response to the wireless device being in a sleep state.

[0448] In an example, when the wireless device transitions to a sleep state (eg, Fig. 27 When the beamFailureDetectionTimer is set to Ta, the wireless device can stop / reset the beamFailureDetectionTimer.

[0449] In practice, beamFailureDetectionTimer can be run without sleeping. Stopping / resetting beamFailureDetectionTimer can avoid resetting BFI_COUNTER to zero.

[0450] In an example, the wireless device may transition a cell from a dormant state to an active state. In an example, the transition may be initiated by one or more MAC-CEs (e.g., Fig. 22 ) is triggered. In an example, in response to transitioning the cell to an active state, the wireless device may restart the beamFailureDetectionTimer.

[0451] In an example, the wireless device may transition a cell from a dormant state to an inactive state (e.g., deactivate). In an example, the transition may be initiated by one or more MAC-CEs (e.g., Fig. 22 ) or expiration of a dormant SCell deactivation timer (e.g., Fig.23 ). In an example, in response to the cell being transitioned to an inactive state, the wireless device may reset the beamFailureDetectionTimer. In an example, in response to the cell being transitioned to an inactive state, the wireless device may reset the BFI_COUNTER.

[0452] In an example, in response to transitioning to the sleep state, the wireless device may restart the beamFailureDetectionTimer. Restarting the beamFailureDetectionTimer may enable the BFI_COUNTER to not reset to zero in the sleep state.

[0453] In an example, the beamFailureDetectionTimer may expire in the sleep state. In an example, in response to the wireless device being in the sleep state, the wireless device may restart the beamFailureDetectionTimer. Restarting the beamFailureDetectionTimer may enable the BFI_COUNTER to not reset to zero in the sleep state.

[0454] In an example, in response to restarting the beamFailureDetectionTimer, the physical layer may not provide a BFI indication to the MAC entity in the sleep state.

[0455] In an example, the wireless device may indicate a BFI in a previous instance of the cycle (eg, Fig. 27 2T1 in) and the wireless device transitions to a sleep state (e.g., Fig. 27 Monitor a subset of the first RS resource set between times (e.g., time slots) of Ta).

[0456] In an example, the wireless device may indicate the next instance of the BFI indication period (eg, Fig. 27 k*T1 in the figure) and the wireless device transitions from a sleep state (e.g., Fig. 27 A subset of the first RS resource set is monitored between a second time (e.g., time slot) of (k+1)*T1).

[0457] In an example, if the wireless device evaluates a second radio link quality of a subset of one or more first RS resources to be worse than a first threshold (e.g., higher BLER, lower SINR, lower L1-RSRP, etc.), the physical layer may provide a BFI indication to the MAC entity in response to monitoring the subset.

[0458] In an example, if the wireless device evaluates that the second radio link quality of a subset of one or more first RS resources is better than a first threshold (e.g., lower BLER, higher SINR, higher L1-RSRP, etc.), the physical layer may not provide a BFI indication to the MAC entity in response to monitoring the subset.

[0459] In an example, in response to the wireless device being in a dormant state (e.g., Fig. 27 In 3T1), the physical layer can provide a BFI indication to the MAC entity. Providing a BFI indication can enable the BFI_COUNTER to not be reset to zero in the sleep state.

[0460] In an example, in response to the BFI indication, BFI_COUNTER may be equal to or greater than beamFailureInstanceMaxCount.The wireless device may defer / skip initiating a random access procedure for beam failure recovery in the sleep state until the wireless device transitions out of the sleep state (eg, active state).

[0461] In an example, the wireless device may transition the cell to a dormant state. The dormant state may be a power saving state. In the dormant state, the wireless device may not monitor the downlink control channel of the cell. In the dormant state, the wireless device may transmit a CSI report for the cell to a base station. In an example, the CSI report may be periodic. Based on not monitoring the downlink control channel in the dormant state, the wireless device may reduce power consumption during the dormant state. Based on transmitting the CSI report during the dormant state, the wireless device may reduce the activation waiting time of the cell (e.g., faster SCell activation). In an example, it may take longer (e.g., 5 milliseconds, 10 milliseconds) to transition the cell from a deactivated state to an active state than to transition the cell from a dormant state to an active state.

[0462] In a conventional system, a wireless device may initiate a beam failure recovery procedure in an activated state of a first cell. The wireless device may transmit an uplink signal (e.g., preamble, SR, MAC CE, etc.) for a beam failure recovery procedure via a second cell during a dormant state. In an example, the wireless device may monitor a downlink control channel (e.g., DCI, random access response, etc.) for a beam failure recovery procedure via a second cell during a dormant state. In an example, the second cell may be different from the first cell. In an example, the second cell and the first cell may be the same. During the beam failure recovery procedure, the wireless device may transition (from an active state) to a dormant state. In an existing system, when the first cell is in a dormant state, the wireless device may continue a beam failure recovery procedure for the first cell via a second cell. Implementing an existing beam failure recovery procedure based on transmitting an uplink signal for a beam failure recovery procedure and / or monitoring a downlink signal during a dormant state may increase power consumption of the wireless device and / or increase uplink interference to other cells and / or wireless devices.

[0463] In an example system, the duration of the sleep state may be long (e.g., in seconds). The duration of the beam failure recovery procedure may be short (e.g., in milliseconds). Executing the beam failure recovery procedure during the sleep state and identifying candidate beams for the beam failure recovery procedure may be inefficient. In an example, based on the duration of the sleep state being longer than the duration of the beam failure recovery procedure, the quality of the candidate beams during the sleep state may decrease (e.g., the quality is below a threshold). In an example, when the cell transitions to an active state (e.g., the quality of the candidate beams may be lower when transitioning to the active state), the base station may not serve (e.g., transmit and / or receive) a wireless device having a candidate beam identified during the sleep state. Identifying the candidate beams may result in increased power consumption (e.g., due to measuring the quality of a set of candidate beams). Serving a wireless device having a candidate beam of low quality may increase the error rate and / or reduce the data rate, resulting in reduced quality of service.

[0464] When the wireless device transitions a cell to a dormant state during a beam failure recovery procedure, an enhanced procedure for implementing the cause beam failure recovery procedure is required. An example embodiment implements an enhanced beam failure recovery procedure (e.g., when the wireless device transitions a cell to a dormant state during a beam failure recovery procedure). In an example, when the wireless device transitions to a dormant state during a beam failure recovery procedure, the wireless device may suspend the beam failure recovery procedure. In an example, the wireless device may stop transmitting an uplink signal for a beam failure recovery procedure for a cell via a second cell during a dormant state. In an example, the wireless device may stop monitoring a downlink control channel for a beam failure recovery procedure for a cell via a second cell during a dormant state. In an example, when the wireless device transitions to a dormant state during a beam failure recovery procedure, the wireless device may suspend the beam failure recovery procedure (e.g., stop a timer associated with the beam failure recovery procedure until transitioning to an active time). This enhanced process reduces uplink overhead, interference, and power consumption at the wireless device and / or base station.

[0465] Fig.28 In an example, a wireless device may be configured with first higher layer parameters, second layer parameters, and third layer parameters of a cell (e.g., Fig.28 time T0).

[0466] In an example, the wireless device may respond to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount (e.g., Fig.28 At time T1), the random access procedure for beam failure recovery of the cell is started.

[0467] In an example, if configured, the wireless device may start a beamFailureRecoveryTimer ( Fig.28 BFR timer in ).

[0468] In an example, the wireless device may transition the cell to a dormant state (e.g., Fig.28 In an example, the transition may be triggered in response to an SCell dormancy timer associated with the cell expiring (eg, Fig.23 In an example, the transition may be triggered in response to receiving one or more MAC CEs from a base station for transitioning a cell to a dormant state (eg, Fig. 22 ). In an example, the transition may be triggered in response to receiving one or more RRC messages including parameters from a base station. The parameters may indicate a scell state indicator set to a dormant state.

[0469] In an example, in response to transitioning the cell to a dormant state, the wireless device may abort a random access procedure for beam failure recovery of the cell. In an example, if configured, the wireless device may reset / stop beamFailureRecoveryTimer in response to aborting the random access procedure.

[0470] In an example, the wireless device may transmit at least a first BFR signal (e.g., a preamble) for a random access procedure. In response to transmitting at least the first BFR signal, the wireless device may start a response window (e.g., a ra-response-window). In an example, in response to transitioning the cell to a dormant state, the wireless device may stop the response window.

[0471] In an example, the wireless device may transmit at least a first BFR signal (e.g., a preamble) for a random access procedure. In response to transmitting at least the first BFR signal, the wireless device may increment a transmission number (e.g., a preamble transmission counter). In an example, the transmission number may be initialized to a first number (e.g., 0) in response to initiating the random access procedure. In an example, in response to transitioning the cell to a dormant state, the wireless device may reset the transmission number to the first number (e.g., zero).

[0472] Fig.29A and Fig.29B An example embodiment is shown. In an example, a base station may provide a first RS (e.g., SSB, CSI-RS) of a first RS resource set of a cell (e.g., PCell, SCell, BWP) to a wireless device. In an example, the first RS may have a first type QCL (e.g., QCL-TypeD).

[0473] In an example, the first RS may be used for radio link quality measurement of the cell. In an example, the wireless device may monitor the first RS for beam failure detection of the cell. In an example, the first RS may be associated with at least one DMRS of a PDCCH monitored by the wireless device on / for the cell (e.g., QCL).

[0474] In an example, the base station may configure a second RS of a second cell (eg, SCell, BWP). In an example, the second RS may have a second type QCL (eg, QCL-TypeA).

[0475] In an example, a first transmission of a first RS and a second transmission of a second RS may overlap (eg, Fig.29A and Fig.29B In at least one OFDM symbol, time slot, frame at time T1 in the example, the first RS (eg, the first transmission) may be considered more important than the second RS (eg, the second transmission). The first RS may have a higher priority than the second RS.

[0476] In the example, Fig.29A In the example, when the first type QCL and the second type QCL are not the same, the base station may override the second type QCL of the second cell. In the example, at time T1, in response to the override, the base station may apply the first type QCL of the first RS to the second transmission of the second RS. In the example, the base station may transmit the second RS with the first type QCL in response to the application. In the example, at time T1, the base station may apply the first type QCL of the first RS to the first transmission of the cell.

[0477] In an example, when the first type QCL and the second type QCL are not the same, in response to the first RS being used for beam failure detection, the base station may apply the first type QCL of the first RS to the second transmission of the second RS. In an example, the base station may transmit the second RS having the first type QCL in response to the application. In an example, the base station may apply the first type QCL of the first RS to the first transmission of the cell.

[0478] In an example, when the first type QCL and the second type QCL are not the same, in response to the first RS being used for beam failure detection, the wireless device may apply the first type QCL of the first RS to the second transmission of the second RS. In an example, the wireless device may receive the second RS having the first type QCL in response to the application.

[0479] In the example, Fig.29BIn the example, when the first type QCL and the second type QCL are not the same, the base station may discard the second transmission of the second RS. In the example, at time T1, the base station may perform the first transmission of the first RS with the first type QCL. In the example, at time T1, the base station may discard (or skip) the second transmission of the second RS.

[0480] In an example, when the first type QCL and the second type QCL are not the same, in response to the first RS being used for beam failure detection, the base station may discard / skip the second transmission of the second RS. In an example, the base station may perform the first transmission of the first RS in response to the discarding.

[0481] In an example, the wireless device may anticipate receiving a first transmission of the first RS in response to the discard.

[0482] In an example, a first transmission of a first RS of a cell and a second transmission of a second RS of a second cell may overlap (e.g., in at least one OFDM symbol, slot, frame, etc.). In an example, the first RS may have a first type QCL. In an example, the second RS may have a second type QCL.

[0483] In an example, the base station may drop / skip the first transmission of the first RS in response to the overlap. In an example, the base station may not perform the first transmission in response to the dropping / skipping.

[0484] In an example, the base station may overlay the first transmission with the second type QCL in response to the overlap.Overlaying the first transmission with the second type QCL may include performing the first transmission of the first RS with the second type QCL.

[0485] In an example, in response to dropping / skipping or overriding, a physical layer in the wireless device may evaluate that a first radio link quality of the first RS is worse than a first threshold (eg, higher BLER, lower SINR, lower L1-RSRP).

[0486] In an example, the physical layer may provide a BFI indication to a MAC entity of the wireless device in response to the evaluation. In an example, in response to receiving the BFI indication from the physical layer, the MAC entity may set the BFI_COUNTER (e.g., Fig.26 The BFI counter in is incremented by one.

[0487] In an example, in response to BFI_COUNTER being equal to or greater than beamFailureInstanceMaxCount, the wireless device may initiate a random access procedure for beam failure recovery of the cell.

[0488] In an example, discarding / skipping the first RS or covering the first transmission of the first RS with the second type QCL can result in starting the random access procedure for beam failure recovery of the cell earlier in time. Starting the random access procedure for beam failure recovery earlier in time can result in a waste of resources. In an example, the first RS may have good radio link quality. In response to discarding / skipping or covering, the wireless device may not evaluate the good radio link quality of the first RS. When the first radio link quality of the first RS is better than the first threshold (e.g., lower BLER, higher SINR, higher L1-RSRP), starting the random access procedure for beam failure recovery earlier in time can result in starting the random access procedure.

[0489] In an example, the cell may be a Pcell, an SCell, a first bandwidth part (BWP) of a carrier. In an example, the second cell may be a PCell, an SCell, a second bandwidth part (BWP) of a carrier. In an example, the first BWP and the second BWP may be active simultaneously.

[0490] In an example, the wireless device may receive one or more messages from a base station. The one or more messages may include one or more configuration parameters of a cell. In an example, the one or more configuration parameters may indicate one or more reference signals (RS) of the cell, a value of a beam failure instance counter, and a threshold.

[0491] In an example, the one or more RSs may be SSB and / or periodic CSI-RS.

[0492] In an example, the threshold may be based on BLER or L1-RSRP or SINR.

[0493] In an example, the physical layer of the wireless device can evaluate the radio link quality of one or more RSs. In an example, in response to evaluating one or more RSs whose radio link quality is worse than a threshold (e.g., higher BLER, lower L1-RSRP, etc.), the physical layer can provide a beam failure instance (BFI) indication.

[0494] In an example, the wireless device may initiate a random access procedure for beam failure recovery of the cell based on a plurality of BFI indications and the value. In an example, the number of BFI indications may be equal to or greater than the value.

[0495] In an example, the wireless device may start a beam failure recovery timer in response to initiating a random access procedure. In an example, the one or more configuration parameters may additionally indicate a beam failure recovery timer.

[0496] In an example, the wireless device may transition the cell to a dormant state. In an example, the transition may be triggered in response to one or more RRC messages including parameters from a base station received by the wireless device. The parameter may indicate an scell state indicator. In an example, the scell state indicator may be set to a dormant state. In an example, the transition may be triggered in response to expiration of an SCell dormancy timer associated with the cell. In an example, the transition may be triggered in response to receiving one or more MAC CEs from a base station for transitioning the cell to a dormant state.

[0497] In an example, the wireless device may abort a random access procedure for beam failure recovery in response to transitioning a cell to a dormant state.

[0498] In an example, the wireless device may stop the beam failure recovery timer in response to transitioning the cell to a dormant state.

[0499] Fig.31 is a flow chart in accordance with aspects of an example embodiment of the present disclosure. At 3110, a wireless device may transition a cell to a dormant state during a beam failure recovery procedure for the cell. At 3120, the beam failure recovery procedure may be aborted based on transitioning the cell to a dormant state during the beam failure recovery procedure.

[0500] According to an example embodiment, the wireless device may transition a bandwidth part (BWP) to a dormant state during a beam failure recovery procedure of the bandwidth part (BWP). Based on transitioning the BWP to a dormant state during the beam failure recovery procedure, the beam failure recovery procedure may be aborted.

[0501] According to an example embodiment, the wireless device may initiate a beam failure recovery procedure for a cell based on beam failure detection of the cell. During the beam failure recovery procedure, the cell may transition to a dormant state. Based on transitioning the cell to a dormant state during the beam failure recovery procedure, the beam failure recovery procedure may be aborted.

[0502] In an example, the wireless device may receive one or more messages. The one or more messages may include one or more configuration parameters of the cell. The wireless device may initiate a beam failure recovery procedure for the cell based on the beam failure detection of the cell. During the beam failure recovery procedure, the cell may transition to a dormant state. Channel state information of the cell may be reported in the dormant state. Based on transitioning the cell to the dormant state during the beam failure recovery procedure, the beam failure recovery procedure may be aborted.

[0503] According to an example embodiment, a cell may be transitioned to a dormant state based on expiration of a dormancy timer. According to an example embodiment, a cell may be transitioned to an inactive state based on expiration of a cell-deactivation timer. According to an example embodiment, one or more configuration parameters may indicate a dormancy timer for a cell. According to an example embodiment, a cell may be transitioned to an active state. Based on transitioning the cell to an active state, a cell-deactivation timer may be started. Based on transitioning the cell to an active state, a dormancy timer may be started. According to an example embodiment, a cell-deactivation timer may be stopped based on transitioning the cell to a dormant state. According to an example embodiment, a dormancy timer may be stopped based on transitioning the cell to a dormant state. According to an example embodiment, a dormancy cell deactivation timer may be started based on transitioning the cell to a dormant state. According to an example embodiment, a cell may be transitioned from a dormant state to an inactive state based on expiration of a dormancy cell deactivation timer. According to an example embodiment, when a dormancy timer is not configured, a cell may be transitioned to an inactive state based on expiration of a cell-deactivation timer. According to an example embodiment, a cell may be transitioned to a dormant state based on receiving one or more dormancy MAC-CE commands for the cell. According to an example embodiment, the cell may be transitioned to the dormant state based on receiving one or more radio resource control (RRC) commands instructing to set a scell state indicator to the dormant state of the cell.

[0504] According to an example embodiment, monitoring of a downlink control channel of a cell may be stopped in the dormant state.

[0505] According to an example embodiment, beam failure detection may be initiated. According to an example embodiment, beam failure detection may be stopped based on transitioning a cell to a dormant state. According to an example embodiment, beam failure detection may include evaluating a radio link quality of one or more reference signals of the cell having a quality below a threshold. According to an example embodiment, beam failure detection may include providing a beam failure instance indication to a medium access control layer of the wireless device via a physical layer of the wireless device. According to an example embodiment, the beam failure instance indication may include a radio link quality of one or more reference signals being below a threshold.

[0506] According to an example embodiment, the one or more configuration parameters may indicate a beam failure detection timer. According to an example embodiment, the beam failure detection timer may be stopped based on transitioning the cell to a dormant state. According to an example embodiment, the beam failure detection timer may be restarted based on transitioning the cell from a dormant state to an active state. According to an example embodiment, the beam failure detection timer may be restarted based on transitioning the cell from a dormant state to an active state. According to an example embodiment, the beam failure detection timer may be restarted based on transitioning the cell to a dormant state.

[0507] According to an example embodiment, one or more configuration parameters may indicate a beam failure recovery timer for the cell. According to an example embodiment, the beam failure recovery timer may be stopped based on terminating the beam failure recovery procedure. According to an example embodiment, the beam failure recovery timer may be started based on initiating the beam failure recovery procedure.

[0508] According to an example embodiment, the beam failure recovery procedure may include transmitting an uplink signal indicating the beam failure detection. According to an example embodiment, the counter may be incremented based on transmitting the uplink signal. According to an example embodiment, the counter may be reset based on aborting the beam failure recovery procedure.

[0509] According to an example embodiment, a cell may be deactivated. According to an example embodiment, deactivating a cell may include stopping reporting channel state information for the cell. According to an example embodiment, the deactivation may be in response to expiration of a cell-deactivation timer. According to an example embodiment, the deactivation may be in response to receiving a deactivation MAC CE.

[0510] According to an example embodiment, reporting channel state information may include at least one of: a channel quality indicator (CQI); a precoding matrix indicator (PMI); a rank indicator (RI); or a channel state information reference signal resource indicator (CRI).

[0511] According to an example embodiment, a wireless device may receive one or more messages including one or more configuration parameters of a cell. The one or more configuration parameters may indicate one or more reference signals (RS) of the cell. The one or more configuration parameters may indicate a beam failure detection timer. The one or more configuration parameters may indicate a threshold. Based on measuring one or more RSs with radio link quality below the threshold, a beam failure instance indication may be determined. Based on the beam failure instance indication, a beam failure detection timer may be started. The cell may be transitioned to a dormant state. Based on transitioning the cell to a dormant state, the beam failure detection timer may be stopped. The cell may be transitioned from the dormant state of the cell to an active state. Based on transitioning the cell from the dormant state of the cell to an active state, the beam failure detection timer may be restarted.

[0512] Embodiments may be configured to operate as desired. When certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms may be performed. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various example embodiments may be applied. Thus, it is possible to implement example embodiments that selectively implement the disclosed protocol.

[0513] A base station may communicate with a mixture of wireless devices. A wireless device and / or a 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 category and / or capabilities. A base station may include multiple sectors. 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 a given capability 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 method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that do not comply with the disclosed method because, for example, these wireless devices or base stations perform based on older versions of LTE or 5G technology.

[0514] In the present disclosure, "a" and "an" and similar phrases are interpreted as "at least one" and "one or more". Similarly, any plural terms are interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "for example, may". In other words, the term "may" indicates that the phrase following the term "may" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0515] If A and B are sets, and each 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={cell 1, cell 2} are: {cell 1}, {cell 2} and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopt / use" (or equivalently "at least adopt / use") indicates that the phrase after the phrase "adopt / use" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0516] The term configured may relate to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" may also mean a specific setting in a device that affects 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. may 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 caused in a device" may 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.

[0517] In the present disclosure, various embodiments are disclosed. Limitations, features and / or elements from the disclosed example embodiments may be combined to create additional embodiments within the scope of the present disclosure.

[0518] 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 a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0519] In addition, many of the features set forth above are described as optional through the use of "may" or the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. However, the present 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 all three of the three possible features.

[0520] 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 the present disclosure can be implemented with hardware, software, firmware, wetware (i.e., 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, which 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). In addition, it is possible to implement a module using physical hardware that incorporates 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, C++, etc. 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 internal hardware blocks with fewer functions on the programmable device. The above mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0521] The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, for the limited purpose of requiring by law, but otherwise reserves all copyright rights whatsoever.

[0522] Although various embodiments have been described above, it should be understood that they are presented by way of example and not limitation. It will be apparent to those skilled in the relevant art that various changes in form and detail may be made therein without departing from the scope of the present invention. Indeed, after reading the above description, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. Therefore, the present embodiments should not be limited by any of the above exemplary embodiments.

[0523] In addition, it should be understood that any diagrams highlighting functionality and advantages are provided for example purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in a manner other than that shown. For example, the actions listed in any flow chart may be reordered or only optionally used in certain embodiments.

[0524] In addition, the purpose of the Abstract of the Disclosure is to generally enable the U.S. Patent and Trademark Office and the public, especially scientists, engineers, and practitioners in the field who are not familiar with patent or legal terms or phraseology, to quickly determine the nature and substance of the technical disclosure of the application through a cursory review. The Abstract of the Disclosure is not intended to limit the scope in any way.

[0525] Finally, it is Applicant's intent that only claims containing the express language "means for" or "step for" be interpreted under 35 USC 112. Claims that do not expressly contain the phrase "means for" or "step for" should not be interpreted under 35 USC 112.

Claims

1. A method comprising: Determining, by a base station (120), a first reference signal configured for beam failure detection, the first reference signal overlapping with a second reference signal in at least one symbol; as well as Based on that the first reference signal is configured for beam failure detection, and the first reference signal and the second reference signal are not quasi co-located: transmitting a first reference signal; and The transmission of the second reference signal is discarded.

2. The method according to claim 1, wherein: The first reference signal has a first quasi co-site type, and the second reference signal has a second quasi co-site type different from the first quasi co-site type.

3. The method according to any of claims 1-2, further comprising transmitting one or more configuration parameters to a wireless device (110), the configuration parameters indicating a first set of reference signal resources including the first reference signal.

4. The method according to any one of claims 1 to 3, wherein: The first reference signal is for one or more of a primary cell, a secondary cell, and a first bandwidth portion of a cell; and The second reference signal is used for one or more of the primary cell, the secondary cell, or a second bandwidth portion of the cell.

5. The method according to any one of claims 1 to 4, wherein the first reference signal and the second reference signal include one or more of: Synchronization signal blocks; and Channel State Information Reference Signal.

6. A base station (120) comprising one or more processors and a memory storing instructions which, when executed by the one or more processors, cause the base station to perform the method according to any one of claims 1 to 5.

7. A non-transitory computer-readable storage medium comprising instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 5.

8. A method comprising: determining, by a wireless device (110), a first reference signal configured for beam failure detection, the first reference signal overlapping with a second reference signal in at least one symbol; as well as Based on the first reference signal being configured for beam failure detection, and the first reference signal and the second reference signal are not quasi co-located: measuring a first reference signal; as well as The measurement of the second reference signal is skipped.

9. The method according to claim 8, wherein: The first reference signal has a first quasi co-site type, and the second reference signal has a second quasi co-site type different from the first quasi co-site type.

10. The method according to any one of claims 8-9, further comprising receiving one or more configuration parameters from a base station (120), the configuration parameters indicating a first set of reference signal resources including the first reference signal.

11. The method according to any one of claims 8 to 10, wherein: The first reference signal is for one or more of a primary cell, a secondary cell, and a first bandwidth portion of a cell; and The second reference signal is used for one or more of the primary cell, the secondary cell, or a second bandwidth portion of the cell.

12. The method according to any one of claims 8 to 11, wherein the first reference signal and the second reference signal include one or more of: Synchronization signal blocks; and Channel State Information Reference Signal.

13. A wireless device (110) comprising one or more processors and a memory storing instructions which, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 8 to 12.

14. A non-transitory computer-readable storage medium comprising instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 8 to 12.

15. A system comprising: A base station (120) comprising one or more processors and a memory storing instructions which, when executed by the one or more processors, cause the base station to: Determining, by a base station, a first reference signal configured for beam failure detection, the first reference signal overlapping with a second reference signal in at least one symbol; as well as Based on the first reference signal being configured for beam failure detection, and the first reference signal and the second reference signal are not quasi co-located: transmitting a first reference signal configured for beam failure detection; as well as discarding transmission of the second reference signal; and a wireless device (110) comprising one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform: determining a first reference signal configured for beam failure detection, the first reference signal overlapping with a second reference signal in at least one symbol; as well as Based on the first reference signal being configured for beam failure detection, and the first reference signal and the second reference signal are not quasi co-located: measuring a first reference signal configured for beam fault detection; as well as The measurement of the second reference signal is skipped.

Images