Uplink transmission in power saving mode

Abstract

A wireless device receives configuration parameters of a configured acknowledgment type 2 associated with a given cell. The wireless device receives first downlink control information indicating the activation of the configured acknowledgment type 2. The wireless device transmits transmission blocks based on the configured acknowledgment type 2. The wireless device receives second downlink control information indicating the transition of the cell to a sleep state. The wireless device transitions the cell to a sleep state based on the second downlink control information. In response to transitioning the cell to a sleep state, the wireless device clears the configured acknowledgment type 2 associated with the cell and retains the configuration parameters of the configured acknowledgment type 2.

Description

Technology Field

[0001] 관련 출원의 교차 참조

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 805,182 filed on February 13, 2019 and U.S. Provisional Application No. 62 / 805,703 filed on February 14, 2019, all of which are incorporated herein by reference in their entirety. Brief explanation of the drawing

[0003] Some examples of the various embodiments of the present disclosure are described herein with reference to the drawings. FIG. 1 is a diagram of an exemplary RAN architecture according to one aspect of one embodiment of the present disclosure. FIG. 2a is a diagram of an exemplary user plane protocol stack according to one aspect of one embodiment of the present disclosure. FIG. 2b is a diagram of an exemplary control plane protocol stack according to one aspect of one embodiment of the present disclosure. FIG. 3 is a diagram of an exemplary wireless device and two base stations according to one aspect of one embodiment of the present disclosure. FIGS. 4a, FIGS. 4b, FIGS. 4c and FIGS. 4d are exemplary diagrams for uplink and downlink signal transmission according to one aspect of one embodiment of the present disclosure. FIG. 5a is a diagram of exemplary uplink channel mapping and exemplary uplink physical signals according to one aspect of one embodiment of the present disclosure. FIG. 5b is a diagram of exemplary downlink channel mapping and exemplary downlink physical signals according to one aspect of one embodiment of the present disclosure. FIG. 6 is a graph illustrating an exemplary transmission time or reception time for a carrier wave according to one aspect of one embodiment of the present disclosure. FIGS. 7a and 7b are diagrams illustrating exemplary OFDM subcarrier sets according to one aspect of one embodiment of the present disclosure. FIG. 8 is a diagram illustrating exemplary OFDM radio resources according to one aspect of one embodiment of the present disclosure. FIG. 9a is a diagram illustrating exemplary CSI-RS and / or SS block transmission in a multi-beam system. FIG. 9b is a diagram illustrating an exemplary downlink beam management procedure according to one aspect of one embodiment of the present disclosure. FIG. 10 is an exemplary diagram of a BWP configured according to one aspect of one embodiment of the present disclosure. FIGS. 11a and FIGS. 11b are diagrams of exemplary multi-connectivity according to one aspect of one embodiment of the present disclosure. FIG. 12 is a diagram of an exemplary random access procedure according to one aspect of one embodiment of the present disclosure. FIG. 13 is a structure of exemplary MAC entities according to one aspect of one embodiment of the present disclosure. FIG. 14 is a diagram of an exemplary RAN architecture according to one aspect of one embodiment of the present disclosure. FIG. 15 is a diagram of an exemplary RRC state according to one aspect of one embodiment of the present disclosure. FIGS. 16a, FIGS. 16b, and FIGS. 16c are examples of MAC subheaders according to one aspect of one embodiment of the present disclosure. FIGS. 17a and FIGS. 17b are examples of a MAC PDU according to one aspect of one embodiment of the present disclosure. FIG. 18 is an example of an LCID for DL-SCH according to one aspect of one embodiment of the present disclosure. FIG. 19 is an example of an LCID for UL-SCH according to one aspect of one embodiment of the present disclosure. FIG. 20a is an example of a 1-octet SCell-activated / deactivated MAC CE according to one aspect of one embodiment of the present disclosure. FIG. 20b is an example of a 4-octet SCell-activated / deactivated MAC CE according to one aspect of one embodiment of the present disclosure. FIG. 21a is an example of a 1-octet SCell hibernation MAC CE according to one aspect of one embodiment of the present disclosure. FIG. 21b is an example of a 4-octet SCell hibernation MAC CE according to one aspect of one embodiment of the present disclosure. FIG. 21c is an example of MAC control elements for SCell state transition according to one aspect of one embodiment of the present disclosure. FIG. 22 is an example of a DCI format according to one aspect of one embodiment of the present disclosure. FIG. 23 is an example of BWP management in SCell according to one aspect of one embodiment of the present disclosure. FIG. 24 is an example of a discontinuous reception (DRX) operation according to one aspect of one embodiment of the present disclosure. FIG. 25 is an example of DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 26a is an example of a wake-up signal / channel-based power saving operation according to one aspect of one embodiment of the present disclosure. FIG. 26b is an example of a go-to-sleep signal / channel-based power saving operation according to one aspect of one embodiment of the present disclosure. FIG. 27 illustrates an exemplary embodiment of power saving enable / disable according to one aspect of one embodiment of the present disclosure. FIG. 28 illustrates an exemplary embodiment of DCI for power saving enable (or activation) according to one aspect of one embodiment of the present disclosure. FIG. 29 illustrates an exemplary embodiment of a DCI for power saving disablement (or deactivation) according to one aspect of one embodiment of the present disclosure. FIG. 30 illustrates an example of one or more CSI reporting configurations according to one aspect of one embodiment of the present disclosure. FIG. 31 illustrates an exemplary embodiment of a semi-continuous CSI reporting mechanism according to one aspect of one embodiment of the present disclosure. FIG. 32 illustrates an exemplary embodiment of a semi-continuous CSI reporting mechanism equipped with BWP switching according to one aspect of one embodiment of the present disclosure. FIG. 33 illustrates an exemplary embodiment of a semi-continuous CSI reporting mechanism equipped with BWP switching according to one aspect of one embodiment of the present disclosure. FIG. 34 illustrates an exemplary embodiment of a semi-continuous CSI report in a power-saving state according to one aspect of one embodiment of the present disclosure. FIG. 35 illustrates an exemplary embodiment of a semi-continuous CSI report in a power-saving state according to one aspect of one embodiment of the present disclosure. FIG. 36 illustrates an exemplary embodiment of semi-continuous CSI-RS measurement in a power-saving state according to one aspect of one embodiment of the present disclosure. FIGS. 37a, FIGS. 37b, and FIGS. 37c illustrate exemplary embodiments of SRS transmission according to one aspect of one embodiment of the present disclosure. FIG. 38 illustrates an exemplary embodiment of SRS transmission in a power-saving state according to one aspect of one embodiment of the present disclosure. FIG. 39 illustrates an exemplary embodiment of uplink transmission based on uplink acknowledgment type 1 configured in a power-saving state, according to one aspect of one embodiment of the present disclosure. FIG. 40 illustrates an exemplary embodiment of uplink transmission based on uplink acknowledgment type 2 configured in a power-saving state, according to one aspect of one embodiment of the present disclosure. FIG. 41 illustrates an exemplary embodiment of a TCI based on PDCCH monitoring in a power-saving state, according to one aspect of one embodiment of the present disclosure. FIG. 42 illustrates an exemplary embodiment of PUCCH transmission based on spatial relationship information in a power-saving state, according to one aspect of one embodiment of the present disclosure. FIG. 43 illustrates an exemplary flowchart of an uplink transmission of a configured acknowledgment type 2 in a power-saving operation according to one aspect of one embodiment of the present disclosure. FIG. 44 illustrates an exemplary flowchart of an uplink transmission of a configured acknowledgment type 2 in a power-saving operation according to one aspect of one embodiment of the present disclosure. FIG. 45 illustrates an exemplary flowchart of an uplink transmission of configured approval type 1 in a power-saving operation according to one aspect of one embodiment of the present disclosure. FIG. 46 illustrates an exemplary flowchart of an uplink transmission of configured approval type 1 in a power saving operation according to one aspect of one embodiment of the present disclosure. FIG. 47 is an exemplary CSI reporting procedure according to one aspect of one embodiment of the present disclosure. FIG. 48 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 49 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 50 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 51 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 52 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 53 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 54 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 55 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. FIG. 56 is an exemplary CSI reporting procedure in DRX operation according to one aspect of one embodiment of the present disclosure. Specific details for implementing the invention

[0004] Exemplary embodiments of the present disclosure enable power-saving operations of wireless devices and / or base stations. Embodiments of the technology disclosed herein may be used in the field of multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein may be associated with wireless devices and / or base stations of multi-carrier communication systems.

[0005] The following acronyms are used throughout the present disclosure.

[0006]

[0007]

[0008]

[0009]

[0010]

[0011] Exemplary embodiments of the present disclosure may be implemented using various physical layer modulation and transmission mechanisms. Exemplary 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 technology, and / or similar. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be used. Various modulation techniques may be applied to signal transmission at the physical layer. Examples of modulation techniques include, but are not limited to, phase, amplitude, code, combinations thereof, and / or similar. An exemplary wireless transmission method 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, and / or similar. Physical wireless transmission can be enhanced by dynamically or reactively changing modulation and encoding methods according to transmission requirements and wireless conditions.

[0012] FIG. 1 is an exemplary Radio Access Network (RAN) architecture according to one aspect of an embodiment of the present disclosure. As illustrated in this example, a RAN node may be a next-generation node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol endpoints toward a first radio device (e.g., 110A). In one example, a RAN node may be a next-generation evolution node B (ng-eNB) (e.g., 120C, 120D) providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol endpoints toward a second radio device (e.g., 110B). The first radio device may communicate with the gNB via a Uu interface. The second radio device may communicate with the ng-eNB via a Uu interface.

[0013] A gNB or ng-eNB can host functions such as wireless resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at 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)), measurement and measurement reporting configuration, transport-level packet marking within the uplink, session management, support for network slicing, Quality of Service (QoS) flow management and mapping for data wireless bearers, support for UE in RRC_INACTIVE state, distribution function for Non-Access Layer (NAS) messages, RAN sharing, and dual connection or strict interworking between NR and E-UTRA.

[0014] In one example, one or more gNBs and / or one or more ng-eNBs may be interconnected via an Xn interface. A gNB or ng-eNB may be connected to a 5G core network (5GC) via an NG interface. In one example, the 5GC may include one or more AMF / UPF (User Plan Function) functions (e.g., 130A or 130B). A gNB or ng-eNB may be connected to a UPF via an NG-U (NG-User plane) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of User Plane Protocol Data Units (PDUs) between a RAN node and a UPF. A gNB or ng-eNB may be connected to an AMF via an NG-Control plane (NG-C) interface. The NG-C interface can provide functions such as NG interface management, UE context management, UE movement management, NAS message transmission, paging, PDU session management, configuration transmission, or alert message transmission.

[0015] In one example, the UPF may host functions such as an anchor point for intra- / inter-RAT (Radio Access Technology) movement (where applicable), an external PDU session point for interconnection to a data network, packet routing and forwarding, packet inspection and user plane portions for policy rule enforcement, traffic usage reporting, an uplink classifier to support routing traffic flow to a data network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane, e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement, uplink traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and / or downlink data notification triggering.

[0016] In one example, the AMF can host various functions, such as NAS signaling termination, NAS signaling security, access layer (AS) security control, inter-core network (CN) node signaling for movement between 3GPP access networks, idle mode UE accessibility (e.g., control and execution of paging retransmission), registration area management, support for intra-system and inter-system movement, access authentication, including checking roaming rights, movement management control (subscription and policy), and support for network slicing and / or session management function (SMF) selection.

[0017] FIG. 2a is an exemplary user plane protocol stack, wherein the Service Data Adaptation Protocol (SDAP) (e.g., 211, 221), Packet Data Convergence Protocol (PDCP) (e.g., 212, 222), Radio Link Control (RLC) (e.g., 213, 223), Media Access Control (MAC) (e.g., 214 and 224), sublayers, and the Physical Layer (PHY) (e.g., 215 and 225) may be terminated at a network-side radio device (e.g., 110) and a gNB (e.g., 120). In one example, the PHY layer provides transport services to the upper layers (e.g., MAC, RRC, etc.). In one example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC service data units (SDUs) belonging to one or different logical channels in / from transport blocks (TBs) transmitted to / from the PHY layer, reporting scheduling information, error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)), priority handling between UEs using dynamic scheduling, priority handling between logical channels of a single UE using logical channel prioritization, and / or padding. A MAC entity may support one or more numerologies and / or transport timings. In one example, a mapping restriction in logical channel prioritization may control the numerologies and / or transport timings available to the logical channel. In one example, the RLC partial layer can support transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM) transmission modes.RLC configuration can be performed per logical channel without relying on numerology and / or Transmission Time Interval (TTI) durations. In one example, an Automatic Repeat Request (ARQ) may operate based on any of the numerology and / or TTI durations for which the logical channel is configured. In one example, services and functions of the PDCP layer for the user plane may include sequence numbering, header compression and decompression, transmission of user data, reordering and duplicate detection, PDCP PDU routing (e.g., for split bearers), retransmission of PDCP SDUs, encryption, deciphering, integrity protection, discarding of PDCP SDUs, PDCP re-establishment and data recovery for RLC AM, and / or duplication of PDCP PDUs. In one example, services and functions of the SDAP may include mapping between QoS flows and data radio bearers. In one example, SDAP services and functions may include mapping Quality of Service Indicators (QFIs) in DL and UL packets. In one example, SDAP protocol entities may be configured for individual PDU sessions.

[0018] FIG. 2b is a control plane protocol stack, wherein PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), MAC (e.g., 235 and 244) partial layers and PHY layers (e.g., 236, 245) can be terminated at a network-side wireless device (e.g., 110) and a gNB (e.g., 120) and can perform the services and functions described above. In one example, RRC (e.g., 232 and 241) can be terminated at a network-side wireless device and a gNB. In one example, the services and functions of the RRC may include broadcasting system information related to the AS and NAS, paging initiated by the 5GC or RAN, establishing, maintaining, and releasing an RRC connection between the UE and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing a signaling radio bearer (SRB) and a data radio bearer (DRB), mobility functions, QoS management functions, control of UE measurement reporting and reporting, detection of radio link failures and recovery from failures, and / or transmission of NAS messages to / from the NAS, from / to the UE. In one example, the NAS control protocol (e.g., 231 and 251) may be terminated at the network side at the radio device and AMF (e.g., 130) and may perform functions such as session management between the UE and the SMF for 3GPP access and non-3GPP access, and authentication and mobility management between the UE and the AMF for 3GPP access and non-3GPP access.

[0019] In one example, a base station may configure multiple logical channels for a wireless device. A logical channel within the multiple logical channels may correspond to a radio bearer, and the radio bearer may be associated with QoS requirements. In one example, a base station may configure a logical channel to be mapped to one or more TTI / numericals from a plurality of TTI / numericals. The wireless device may receive Downlink Control Information (DCI) through a Physical Downlink Control Channel (PDCCH) indicating an uplink grant. In one example, the uplink grant may be for a first TTI / numerical and may indicate uplink resources for the transmission of a transmission block. The base station may configure each logical channel within the multiple logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. One or more parameters may include priority, a prioritized bit rate, etc. A logical channel of the multiple logical channels may correspond to one or more buffers containing data associated with the logical channel. A logical channel prioritization procedure may allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) within a plurality of logical channels. One or more first logical channels may be mapped to a first TTI / numericology. In a wireless device, the MAC layer may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) within a MAC PDU (e.g., a transmission block). In one example, the MAC PDU may include a MAC header containing a plurality of MAC subheaders. A MAC subheader within the plurality of MAC subheaders may correspond to a MAC CE or MAC SUD (logical channel) within one or more MAC CEs and / or one or more MAC SDUs.In one example, a Logical Channel IDentifier (LCID) may be configured on a MAC CE or a logical channel. In one example, the LCID for the logical channel or MAC CE may be fixed or pre-configured. In one example, the LCID for the logical channel or MAC CE may be configured for a wireless device by a base station. A MAC subheader corresponding to a MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0020] In one example, a base station may enable and / or disable and / or affect one or more processes in a wireless device by employing one or more MAC commands (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). One or more MAC commands may include one or more MAC control elements. In one example, one or more processes may include enabling and / or disabling PDCP packet replication for one or more wireless bearers. The base station may transmit a MAC CE containing one or more fields, the values ​​of which indicate the enabling and / or disabling of PDCP replication for one or more wireless bearers. In one example, one or more processes may include transmitting Channel State Information (CSI) for one or more cells. The base station may transmit one or more MAC CEs indicating the enabling and / or disabling of CSI transmission on one or more cells. In one example, one or more processes may include enabling or disabling one or more secondary cells. In one example, the base station may transmit a MAC CE indicating the activation or deactivation of one or more secondary cells. In one example, the base station may transmit one or more MAC CEs indicating the start and / or stop of one or more Discontinuous Reception (DRX) timers in a wireless device. In one 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).

[0021] FIG. 3 is a block diagram of base stations (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 an NB, eNB, gNB, and / or ng-eNB. In one example, the wireless device and / or base station may operate 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, and / or others), at least one processor (321A), and at least one set of program code instructions (323A) executable by at least one processor (321A) and stored in non-transient memory (322A). 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) executable by at least one processor (321B) and stored in non-transient memory (322B).

[0022] A base station may include many sectors, such as, for example, 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 or more. Cells may be classified, for example, as primary cells or secondary cells. In Radio Resource Control (RRC) connection establishment / re-establishment / handover, one serving cell may provide NAS (Non-Access Layer) mobility information (e.g., TAI (Tracking Area Identifier)). In RRC connection re-establishment / handover, one serving cell may provide a security input. This 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 an UL PCC. Depending on the wireless device performance, the 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.

[0023] A cell containing a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to a single cell. A cell ID or a cell index may also identify the downlink carrier or uplink carrier of a cell (depending on the context in which it is used). In this disclosure, a cell ID may likewise be referred to as a carrier ID, 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 cell ID may be determined using a synchronization signal transmitted from a downlink carrier. A cell index may be determined using an RRC message. For example, when this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell containing the first downlink carrier. The same concept may apply, for example, to carrier activation. Where the present disclosure indicates that the first carrier is activated, the specification may likewise mean that the cell containing the first carrier is activated.

[0024] A base station may transmit one or more messages (e.g., RRC messages) containing multiple configuration parameters for one or more cells to a wireless device. One or more cells may include at least one primary cell and at least one secondary cell. In one example, the RRC message may be broadcast or unicast to the wireless device. In one example, the configuration parameters may include common parameters and dedicated parameters.

[0025] Services and / or functions of the RRC sublayer may include: broadcasting of system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishment, maintenance, and / or release of RRC connections between a radio device and NG-RAN, which may include the addition, modification, and release of carrier aggregation; or at least one of the addition, modification, and / or release of duplex connections in NR or between E-UTRA and NR. Services and / or functions of the RRC sublayer may further include: security functions including key management; establishment, configuration, maintenance, and / or release of signaling radio bearers (SRB) and / or data radio bearers (DRB); handover (e.g., intra-NR movement or inter-RAT movement) and context transmission; or at least one of mobility functions which may include at least one of radio device cell selection and reselection and control of cell selection and reselection. Services and / or functions of the RRC sublayer may include QoS management functions; radio device measurement configuration / reporting; Detection of wireless link failure and / or recovery from failure; or transmission of NAS messages to / from a wireless device to / from a core network entity (e.g., AMF, Mobility Management Entity (MME)), at least one of which may be further included.

[0026] The RRC sublayer may support an RRC_Idle state, an RRC_Inactive state, and / or an RRC_Connected state for a wireless device. In the RRC_Idle state, the wireless device may perform at least one of Public Land Mobile Network (PLMN) selection; reception of broadcasted system information; cell selection / reselection; monitoring / reception of paging for mobile end-of-the-world data initiated by 5GC; paging for mobile end-of-the-world data regions 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 receiving broadcasted system information; cell selection / reselection; monitoring / reception of RAN / CN paging initiated by NG-RAN / 5GC; RAN-based notification regions (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) to the wireless device and / or save the 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 establishing a 5GC-NG-RAN connection (both C / U-planes) to the wireless device; saving the UE AS context for the wireless device; transmitting / receiving unicast data to / from the wireless device; or performing network control movements 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.

[0027] System information (SI) can be divided into a minimum SI and other SIs. The minimum SI may be broadcast periodically. The minimum SI may include basic information required for initial access and information provided in an order, i.e., scheduling information, intended for periodically obtaining any other SI broadcasts. Other SIs may be broadcast or provided in a dedicated manner, triggered by the network or upon a request from a wireless device. The minimum SI contains different messages (e.g., MasterInformationBlock and SystemInformationBlockType1 It can be transmitted through two different downlink channels using ). The other SI is SystemInformationBlockType2 It can be transmitted via. For a wireless device in the RRC_connected state, dedicated RRC signaling may be used for requests and delivery of other SIs. For a wireless device in the RRC_Idle state and / or RRC_Inactive state, a request may trigger a random access procedure.

[0028] A wireless device may report wireless access capability information, which may be static. A base station may request certain capabilities for a wireless device to report based on band information. If permitted by the network, a request for a temporary capability limitation may be transmitted by the wireless device 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 acknowledge or deny the request. Temporary capability limitations may be transparent to the 5GC (e.g., static capabilities may be stored in the 5GC).

[0029] When CA is configured, the wireless device can establish an RRC connection with the network. During the RRC connection establishment / reconfiguration / handover procedure, one serving cell can provide NAS mobility information, and during the RRC connection re-establishment / handover, one serving cell can provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, the SCell may be configured to form a set of serving cells together with the PCell. The configured set of serving cells for the wireless device may include one PCell and one or more SCells.

[0030] The reconfiguration, addition, and removal of SCells can be performed by the RRC. During intra-NR handover, the RRC can also add, remove, or reconfigure SCells for use with the target PCell. When adding a new SCell, dedicated RRC signaling can be used to transmit all required system information for the SCell. That is, while in connection mode, the wireless device may not need to obtain system information broadcast directly from the SCell.

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

[0032] The RRC connection establishment (or re-establish, resume) procedure may establish (or re-establish, resume) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure may be used to transmit initial NAS-specific information / messages from a wireless device to the E-UTRAN. RRCConnectionReestablishment The message can be used to re-establish SRB1.

[0033] The measurement reporting procedure may involve transmitting measurement results from a wireless device to the NG-RAN. The wireless device may initiate the measurement reporting procedure after successful security activation. A measurement report message may be used to transmit the measurement results.

[0034] The wireless device (110) may include at least one communication interface (310) (e.g., a wireless modem, an antenna, and / or the like), at least one processor (314), and at least one set of program code instructions (316) executable by the at least one processor (314) and stored in non-transient memory (315). The wireless device (110) may further include 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).

[0035] The processor (314) of the wireless device (110), the processor (321A) of base station 1 (120A), and / or the processor (321B) of base station 2 (120B) may include at least one of a general-purpose processor, a digital signal processor (DSP), a controller, 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) of base station 1 (120A), and / or the processor (321B) of base station 2 (120B) may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other function that enables the wireless device (110), base station 1 (120A), and / or base station 2 (120B) to operate in a wireless environment.

[0036] The processor (314) of the wireless device (110) may be connected to a speaker / microphone (311), a keypad (312), and / or a 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) within the wireless device (110) may receive power from a power source (317) and / or be configured to distribute power to other components of the wireless device (110). The power source (317) may include at least one of one or more batteries, solar cells, fuel cells, etc. The processor (314) may be connected to a GPS chipset (318). The GPS chipset (318) may be configured to provide geographic location information of the wireless device (110).

[0037] The processor (314) of the wireless device (110) may be additionally connected to other peripheral devices (319) that may include one or more software and / or hardware modules providing additional features and / or functions. For example, the peripheral device (319) may include at least one of an accelerometer, a satellite transceiver, a digital camera, a USB port, a hands-free headset, a frequency modulation (FM) radio device, a media player, an internet browser, etc.

[0038] 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 individually with the communication interface (310) of the wireless device (110) via the wireless link (330A) and / or the wireless link (330B). In one 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.

[0039] 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 base station 1 (120A) and / or the communication interface (320B) of base station 2 (120B). Base station 1 (120A) and the wireless device (110) and / or base station 2 (120B) and the wireless device (110) may each be configured to transmit and receive transmission blocks through the wireless link (330A) and / or the wireless link (330B). The wireless link (330A) and / or the wireless link (330B) may use at least one frequency carrier. According to some of the various aspects of the embodiment, transceiver(s) may be used. The transceiver may be a device comprising both a transmitter and a receiver. The transceiver may be used in devices such as wireless devices, base stations, relay nodes, and / or others. Exemplary embodiments of wireless technology implemented in communication interfaces (310, 320A, 320B) and wireless links (330A, 330B) are illustrated in FIG. 4a, 4b, 4c, 4d, 6, 7a, 7b, 8 and the accompanying text.

[0040] In one example, other nodes of the wireless network (e.g., AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and memory for storing instructions.

[0041] A node (e.g., a wireless device, a base station, an AMF, an SMF, a UPF, servers, switches, antennas, and / or others) may include one or more processors, and memory that stores instructions that cause the node to perform specific processes and / or functions when executed by one or more processors. Exemplary embodiments may enable operation of single-carrier and / or multi-carrier communication. Other exemplary embodiments may include a non-transient type computer-readable medium containing instructions executable by one or more processors to induce operation of single-carrier and / or multi-carrier communication. Yet another exemplary embodiment may include a non-transient type computer-readable machine-accessible medium having encoded instructions to enable programmable hardware to enable the node to operate of single-carrier and / or multi-carrier communication. The node may include a processor, memory, an interface, and / or others.

[0042] 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 electronic devices such as connectors, wires, drivers, amplifiers, and / or others. The software interface may include code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and / or others. The firmware interface may include a combination of embedded hardware and code stored in a memory device and / or communicating with the memory device to implement connections, electronic device operation, protocol(s), protocol layers, communication drivers, device drivers, hardware operation, combinations thereof, and / or others.

[0043] FIGS. 4a, 4b, 4c, and 4d are exemplary diagrams for uplink and downlink signal transmission according to one aspect of one embodiment of the present disclosure. FIG. 4a illustrates an exemplary uplink transmitter for at least one physical channel. A baseband signal representing a physical uplink shared channel may perform one or more functions. One or more functions include scrambling; modulation of scrambed bits to generate complex-valued symbols; mapping of complex-valued modulation symbols to one or more transport layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of a complex-valued time-domain single carrier-frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; It may include at least one of and / or others. In one example, when conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, when conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 4a. These functions are illustrated as examples, and it is expected that various mechanisms may be implemented in various embodiments.

[0044] An exemplary structure for modulation and up-conversion of complex value SC-FDMA or CP-OFDM baseband signals to carrier frequencies for antenna port and / or physical random access channel (PRACH) baseband signals of complex values ​​is illustrated in FIG. 4b. Filtering may be used before transmission.

[0045] An exemplary structure for downlink transmission is illustrated in FIG. 4c. A baseband signal representing a downlink physical channel may perform one or more functions. One or more functions may include: scrambling of bits coded within a codeword to be transmitted over the physical channel; modulation of the scrambled bits to generate modulation symbols of complex values; mapping of modulation symbols of complex values ​​over one or several transport layers; precoding of modulation symbols of complex values ​​over a layer for transmission over an antenna port; mapping of modulation symbols of complex values ​​to resource elements for the antenna port; generation of a time-domain OFDM signal of complex values ​​for the antenna port; and / or other such functions. These functions are illustrated by example, and it is expected that various mechanisms may be implemented in various embodiments.

[0046] In one example, a gNB can transmit a first symbol and a second symbol on an antenna port to a wireless device. The wireless device can estimate a channel for transmitting a second symbol on an antenna port (e.g., fading gain, multipath delay, etc.) from a channel for transmitting a first symbol on an antenna port. In one example, if one or more large-scale characteristics of the channel for transmitting a first symbol on a first antenna port can be inferred from the channel for transmitting a second symbol on a second antenna port, the first antenna port and the second antenna port may be quasi-colocated. One or more large-scale characteristics may include at least one of delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0047] Exemplary modulation and upconversion of a complex OFDM baseband signal for an antenna port with respect to the carrier frequency are illustrated in FIG. 4d. Filtering may be used before transmission.

[0048] FIG. 5a is a diagram of an exemplary uplink channel mapping and exemplary uplink physical signals. FIG. 5b is a diagram of an exemplary downlink channel mapping and exemplary downlink physical signals. In one example, the physical layer may provide one or more information transmission services to the MAC and / or one or more upper layers. For example, the physical layer may provide one or more information transmission services to the MAC through one or more transmission channels. An information transmission service may indicate how and with what characteristics data is transmitted through a wireless interface.

[0049] In an exemplary embodiment, the wireless network may include one or more downlink and / or uplink transmission channels. For example, the diagram in FIG. 5a illustrates an exemplary uplink transmission channel including an uplink shared channel (UL-SCH) (501) and a random access channel (RACH) (502). The diagram in FIG. 5b illustrates an exemplary downlink transmission channel including a downlink shared channel (DL-SCH) (511), a paging channel (PCH) (512), and a broadcast channel (BCH) (513). The transmission 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) can be mapped to a physical broadcast channel (PBCH) (516).

[0050] There may be one or more physical channels that do not have a corresponding transmission channel. 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 the UCI (509) from the UE to the base station. For example, a physical downlink control channel (PDCCH) (515) may carry the DCI (517) from the base station to the UE. NR may support multiplexing of the UCI (509) in PUSCH (503) if the transmission of the UCI (509) and PUSCH (503) can match at least partially in a slot. The UCI (509) may include at least one of a CSI, an ACK (acknowledgment) / NACK (negative acknowledgment), and / or a scheduling request. The DCI (517) on the PDCCH (515) may indicate at least one of one or more downlink allocations and / or one or more uplink scheduling grants.

[0051] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, 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 one or more RSs to the UE (e.g., unicast, multicast, and / or broadcast). For example, 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).

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

[0053] In one example, whether an uplink PT-RS (507) exists may depend on the RRC configuration. For example, the presence of an uplink PT-RS may be configured specifically for the UE. For example, the presence and / or pattern of an uplink PT-RS (507) within a scheduled resource may be configured specifically for the UE by a combination of associations with one or more parameters used for RRC signaling and / or other purposes that may be represented by DCI (e.g., Modulation and Coding Scheme (MCS)). If configured, the dynamic presence of an uplink PT-RS (507) may be associated with at least one DCI parameter including an MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain densities may be associated with at least one configuration of the scheduled bandwidth, if present. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be fewer than the number of DM-RS ports of the scheduled resources. For example, the uplink PT-RS (507) may be limited to the scheduled time / frequency duration for the UE.

[0054] In one example, the UE may transmit an SRS (508) to the 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 uplink channel states at one or more different frequencies. The base station scheduler may use the uplink channel state to allocate one or more blocks of good quality resources for uplink PUSCH transmissions from the UE. The base station may semi-statistically configure one or more sets of SRS resources for the UE. For an SRS resource set, the base station may configure one or more SRS resources for the UE. The applicability of an SRS resource set may be configured by upper-layer (e.g., RRC) parameters. For example, if the upper-layer parameter indicates beam management, the SRS resources within each set of one or more SRS resource sets may be transmitted at once. The UE may transmit one or more SRS resources within different SRS resource sets simultaneously. A new wireless access technology network may support non-periodic, periodic, and / or semi-continuous SRS transmission. A UE may transmit SRS resources based on one or more trigger types, wherein one or more trigger types may include upper layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format may be used by the UE to select at least one of one or more configured sets of SRS resources). SRS trigger type 0 may represent an SRS triggered based on upper layer signaling. SRS trigger type 1 may represent an SRS triggered based on one or more DCI formats. In one example, when PUSCH (503) and SRS (508) are transmitted in the same slot, the UE may be configured to transmit SRS (508) after the transmission of PUSCH (503) and the corresponding uplink DM-RS (506).

[0055] In one example, the base station may semi-statistically configure one or more SRS configuration parameters representing at least one of the following to the UE: an SRS resource configuration identifier, a plurality of SRS ports, time domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-continuous, or non-periodic SRS), slot (mini-slot, and / or subframe) level periodicity and / or offset for periodic and / or non-periodic SRS resources, a plurality of OFDM symbols within the SRS resource, the start OFDM symbol of the SRS resource, SRS bandwidth, frequency hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0056] In one example, in the time domain, the SS / PBCH block may contain one or more OFDM symbols within the SS / PBCH block (e.g., four OFDM symbols numbered in ascending order from 0 to 3). The SS / PBCH block may contain a PSS / SSS (521) and a PBCH (516). In one example, in the frequency domain, the SS / PBCH block may contain one or more contiguous subcarriers within the SS / PBCH block (e.g., 240 contiguous subcarriers having subcarriers numbered in ascending order from 0 to 239). For example, the PSS / SSS (521) may occupy one OFDM symbol and 127 subcarriers. For example, the PBCH (516) may span three OFDM symbols and 240 subcarriers. A UE may assume that one or more SS / PBCH blocks transmitted with the same block index may be quasi-colocated with respect to, for example, Doppler spread, Doppler shift, mean gain, mean delay, and spatial Rx parameters. A UE may not assume quasi-colocation for the transmission of other SS / PBCH blocks. The periodicity of the SS / PBCH blocks may be configured by a wireless network (e.g., by RRC signaling), and one or more time positions in which the SS / PBCH blocks may be transmitted may be determined by subcarrier intervals. In one example, unless the wireless network configures the UE to take different subcarrier intervals, the UE may take a band-specific subcarrier interval for the SS / PBCH blocks.

[0057] In one example, the downlink CSI-RS (522) may be used by the UE to obtain channel state information. The wireless network may support periodic, non-periodic, and / or semi-continuous transmission of the downlink CSI-RS (522). For example, a base station may semi-statistically configure and / or reconfigure the periodic transmission of the downlink CSI-RS (522) to the UE. The configured CSI-RS resources may be enabled and / or disabled. For semi-continuous transmission, the activation and / or deactivation of the CSI-RS resources may be dynamically triggered. In one example, the CSI-RS configuration may include one or more parameters representing at least a number of antenna ports. For example, the base station may configure 32 ports for the UE. The base station may semi-statistically configure one or more sets of CSI-RS resources for the UE. One or more CSI-RS resources may be assigned to one or more UEs from one or more sets of CSI-RS resources. For example, a base station may semi-statistically configure one or more parameters representing CSI-RS resource mapping, such as the time-domain location of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In one example, the UE may be configured to use the same OFDM symbols for the downlink CSI-RS (522) and the control resource set (core set) when the downlink CSI-RS (522) and the core set are spatially quasi-collocated and the resource element associated with the downlink CSI-RS (522) is outside the PRB configured for the core set. In one example, the UE may be configured to use the same OFDM symbols for the downlink CSI-RS (522) and the SS / PBCH block when the downlink CSI-RS (522) and the SS / PBCH block are spatially quasi-collocated and the resource element associated with the downlink CSI-RS (522) is outside the PRB configured for the SS / PBCH block.

[0058] In one example, the UE may transmit one or more downlink DM-RS (523) to the base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH (514)). For example, the wireless 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-loaded DM-RS pattern. A front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statistically configure up to a maximum number of front-loaded DM-RS symbols for the PDSCH (514) to the UE. For example, a DM-RS configuration may support one or more DM-RS ports. For example, for single-user MIMO, a DM-RS configuration may support at least eight orthogonal downlink DM-RS ports. For example, in the case of multi-user MIMO, the DM-RS configuration may support 12 orthogonal downlink DM-RS ports. The wireless network may support a common DM-RS structure for DL ​​and UL, for example, at least for CP-OFDM, where the DM-RS location, DM-RS pattern and / or scrambling sequence may be the same or different.

[0059] In one example, whether a downlink PT-RS (524) exists may depend on the RRC configuration. For example, the presence of the downlink PT-RS (524) may be configured specifically for the UE. For example, the presence and / or pattern of the downlink PT-RS (524) within a scheduled resource may be configured specifically for the UE by a combination of associations with one or more parameters used for RRC signaling and / or other purposes (e.g., MCS) that may be represented by DCI. If configured, the dynamic presence of the downlink PT-RS (524) may be associated with at least one DCI parameter including MCS. The wireless network may support multiple PT-RS densities defined in the time / frequency domain. The frequency domain density may be associated with at least one configuration of the scheduled bandwidth, if present. The UE may assume the same precoding for the DMRS ports and PT-RS ports. Multiple PT-RS ports may be fewer than the number of DM-RS ports in the scheduled resource. For example, the downlink PT-RS (524) may be limited to a scheduled time / frequency duration for the UE.

[0060] FIG. 6 is a diagram illustrating exemplary transmission and reception times for a carrier according to one aspect of one embodiment of the present disclosure. A multi-carrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 in the case of carrier aggregation, or from 1 to 64 in the case of duplex connection. Different radio frame structures may be supported (e.g., FDD and TDD duplex mechanisms). FIG. 6 illustrates exemplary frame timing. Downlink and uplink transmissions may be structured into radio frames (601). In this example, the radio frame duration is 10 ms. In this example, the 10 ms radio frame (601) may be divided into 10 subframes (602) of equal size having a duration of 1 ms. The subframe(s) may include one or more slots (e.g., slots (603 and 605)) according to the subcarrier interval and / or CP length. For example, subframes having subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz may each contain 1, 2, 4, 8, 16, and 32 slots, respectively. In FIG. 6, a subframe may be divided into two slots (603) of the same size having a duration of 0.5 ms. For example, 10 subframes may be available for downlink transmission, and 10 subframes may be available for uplink transmission at 10 ms intervals. Uplink and downlink transmissions may be separated in the frequency domain. The slot(s) may contain a plurality of OFDM symbols (604). The number of OFDM symbols (604) within a slot (605) may depend on the cyclic prefix length. For example, the slot can be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP.A slot may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with an extended CP. A slot may include a downlink, an uplink, or a downlink portion and an uplink portion and / or other.

[0061] FIG. 7a is a diagram illustrating sets of exemplary OFDM subcarriers according to one aspect of one embodiment of the present disclosure. In this example, a gNB may communicate with a wireless device with a carrier having an exemplary channel bandwidth (700). In this diagram, arrow(s) may illustrate subcarriers in a multi-carrier OFDM system. The OFDM system may use technologies such as OFDM technology, SC-FDMA technology, and / or others. In one example, an arrow (701) indicates a subcarrier transmitting information symbols. In one example, the subcarrier spacing (702) between two adjacent subcarriers within a carrier may be any one of 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, etc. In one example, different subcarrier spacings may correspond to different transmission numerologies. In one example, the transmission numerology may include, at least, a numerology index; a value of a subcarrier interval; and a periodic prefix (CP) of a certain type. In one example, the gNB may transmit to / receive from the UE on a plurality of subcarriers (703) within the carrier. In one example, the bandwidth occupied by the plurality of subcarriers (703) (transmission bandwidth) may be smaller than the channel bandwidth (700) of the carrier due to guard bands (704 and 705). In one example, the guard bands (704 and 705) may be used to reduce interference to and from one or more adjacent carriers. The plurality of subcarriers (transmission bandwidth) within the carrier may depend on the channel bandwidth and subcarrier interval of the carrier. For example, the transmission bandwidth for a carrier having a 20 MHz channel bandwidth and a 15 kHz subcarrier spacing can have 1024 subcarriers.

[0062] In one example, the gNB and the wireless device may communicate with multiple CCs if CA is configured therein. In one example, if CA is supported, different component carriers may have different bandwidths and / or subcarrier spacings. In one example, the gNB may transmit a first type of service to the UE via the first component carrier. The gNB may transmit a second type of service to the UE via the second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability) suitable for transmission via different component carriers having different subcarrier spacings and / or bandwidths. FIG. 7b illustrates an exemplary embodiment. 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 interval (711). The carriers of the multi-carrier OFDM communication system may be adjacent carriers, non-adjacent carriers, or a combination of both adjacent and non-adjacent carriers.

[0063] FIG. 8 is a diagram illustrating OFDM radio resources according to one aspect of one embodiment of the present disclosure. In one example, the carrier may have a transmission bandwidth (801). In one example, the resource grid may have a structure in the frequency domain (802) and the time domain (803). In one example, the resource grid may include a second number of resource blocks starting from a common resource block represented by a first number of OFDM symbols and transmission numerology in a subframe and upper-level signaling for the carrier (e.g., RRC signaling). In one example, in the resource grid, the resource unit identified by the subcarrier index and the symbol index may be a resource element (805). In one example, the subframe may include a first number of OFDM symbols (807) according to the numerology associated with the carrier. For example, if the subcarrier spacing of the carrier's numerology is 15 kHz, the subframe may have 14 OFDM symbols for the carrier. If the subcarrier spacing of the numerology is 30 kHz, the subframe may have 28 OFDM symbols. If the subcarrier spacing of the numerology is 60 kHz, the subframe may have 56 OFDM symbols. In one example, the second number of resource blocks included in the carrier's resource grid may depend on the carrier's bandwidth and numerology.

[0064] As illustrated in FIG. 8, a resource block (806) may include 12 subcarriers. In one example, a plurality of resource blocks may be grouped into a Resource Block Group (RBG) (804). In one example, the size of the RBG may depend on at least one of an RRC message indicating the RBG size configuration; the size of the carrier bandwidth; or the size of a portion of the carrier bandwidth. In one example, the carrier may include a plurality of bandwidth portions. A first bandwidth portion of the carrier may have a frequency position and / or bandwidth different from a second bandwidth portion of the carrier.

[0065] In one example, the gNB may transmit downlink control information, including downlink or uplink resource block allocation, to a wireless device. The base station may transmit to or receive from the wireless device data packets (e.g., transmission blocks) scheduled and transmitted through one or more resource blocks and one or more slots according to the parameters of the downlink control information and / or RRC message(s). In one example, a start symbol for the first slot of one or more slots may be indicated to the wireless device. In one example, the gNB may transmit to or receive from the wireless device data packets scheduled in one or more RBGs and one or more slots.

[0066] In one example, the gNB may transmit downlink control information, including downlink allocation, to a wireless device via one or more PDCCHs. The downlink allocation may include parameters representing at least modulation and coding formats; resource allocation; and / or HARQ information related to DL-SCH. In one example, the resource allocation may include parameters for resource block allocation; and / or slot allocation. In one example, the gNB may dynamically allocate resources to a wireless device via a Cell-to-Wireless Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor one or more PDCCH(s) to discover available allocations when its downlink reception is enabled. When the wireless device successfully detects one or more PDCCHs, it may receive one or more downlink data packages on one or more PDSCHs scheduled by the one or more PDCCHs.

[0067] In one example, the gNB may allocate a scheduling (CS) resource configured for downlink transmission to a wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS acknowledgment. The gNB may transmit a DCI via a PDCCH addressed to a configured scheduling-RNTI (CS-RNTI) that enables the CS resource. The DCI may include a parameter indicating whether the downlink acknowledgment is a CS acknowledgment. The CS acknowledgment may be implicitly reused according to the periodicity defined by one or more RRC messages until it is disabled.

[0068] In one example, the gNB may transmit downlink control information, including uplink acknowledgments, to a wireless device via one or more PDCCHs. The uplink acknowledgments may include parameters representing at least modulation and coding formats; resource allocation; and / or HARQ information related to UL-SCHs. In one example, resource allocation may include parameters for resource block allocation; and / or slot allocation. In one example, the gNB may dynamically allocate resources to a wireless device via C-RNTIs on one or more PDCCHs. The wireless device may monitor one or more PDCCHs to discover available resource allocations. When the wireless device successfully detects one or more PDCCHs, it may transmit one or more uplink data packages via one or more PUSCHs scheduled by the one or more PDCCHs.

[0069] In one example, the gNB may allocate a CS resource to a wireless device for uplink data transmission. The gNB may transmit one or more RRC messages indicating the periodicity of the CS acknowledgment. The gNB may transmit a DCI via a PDCCH addressed to a CS-RNTI that enables the CS resource. The DCI may include a parameter indicating that the uplink acknowledgment is a CS acknowledgment. The CS acknowledgment may be implicitly reused according to the periodicity defined by one or more RRC messages until it is disabled.

[0070] In one example, the base station may transmit DCI / control signaling via PDCCH. The DCI may take a format in multiple formats. The DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ-related parameters, MCS), CSI requests (e.g., non-periodic CQI reports), SRS requests, uplink power control commands for one or more cells, and one or more timing information (e.g., TB transmit / receive timing, HARQ feedback timing, etc.). In one example, the DCI may indicate an uplink acknowledgment containing transmission parameters for one or more transmit blocks. In one example, the DCI may indicate a downlink allocation indicating parameters for receiving one or more transmit blocks. In one example, the DCI may be used by the base station to initiate contention-free random access from a wireless device. In one example, the base station may transmit a DCI including a Slot Format Indicator (SFI) that notifies a slot format. In one example, the base station may transmit a DCI containing a pre-emption indication that notifies PRB(s) and / or OFDM symbol(s) when the UE does not take any transmission intended for that UE. In one example, the base station may transmit a DCI for group power control of PUCCH, PUSCH, or SRS. In one example, the DCI may correspond to an RNTI. In one example, the radio device may acquire an RNTI in response to completing an initial access (e.g., C-RNTI). In one example, the base station may configure an RNTI for the radio (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI).In one example, the radio device can calculate an RNTI (e.g., the radio device can calculate an RA-RNTI based on the resources used for transmitting the preamble). In one example, the RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In one example, the radio device can monitor a group common search space that may be used by a base station to transmit DCIs intended for a group of UEs. In one example, the group common DCI may correspond to an RNTI commonly configured for a group of UEs. In one example, the radio device can monitor a UE-specific search space. In one example, the UE-specific DCI may correspond to an RNTI configured for the radio device.

[0071] 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 blocks, which may include at least a PSS, SSS, and / or PBCH. A radio device may measure the quality of a beam-pair link using one or more RSs. 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 a PBCH may be used as RSs to measure the quality of a beam-pair link. The quality of a beam-pair link may be defined by a Reference Signal Received Output (RSRP) value, or a Reference Signal Received Quality (RSRQ) value and / or a CSI value measured on the RS resources. The base station may indicate whether the RS resources used to measure the quality of the beam-pair link are quasi-co-located (QCLed) with the DM-RS of the control channel. The RS resources and DM-RS of the control channel may be referred to as quasi-collocated (QCLed) when the channel characteristics from the transmission to the wireless device on the RS and the channel characteristics from the transmission to the wireless device on the control channel are similar or identical under configured criteria. In multi-beam operation, the wireless device may perform uplink beam sweeping to access the cell.

[0072] In one example, a wireless device may be configured to simultaneously monitor PDCCHs 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 the wireless device to monitor PDCCHs on one or more beam pair links at different PDCCH OFDM symbols. For example, the base station may transmit upper-layer signaling (e.g., RRC signaling) or MAC CE containing parameters related to the wireless device's Rx beam settings to monitor PDCCHs on one or more beam pair links. The base station may transmit an indication of the spatial QCL assumption between the DL RS antenna port(s) (e.g., cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DM-RS) and the DL RS antenna port(s) of the PBCH for demodulation of the DL control channel. Signaling for beam indication to PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification-transparent and / or implicit methods, and combinations of these signaling methods.

[0073] For reception of a unicast DL data channel, a base station may indicate spatial QCL parameters between the DL RS antenna port(s) and the DM-RS antenna port(s) of the DL data channel. The base station may transmit a DCI (e.g., downlink acknowledgment) containing information indicating the RS antenna port(s). The information may indicate the RS antenna port(s) that can be QCLed with the DM-RS antenna port(s). Different sets of DM-RS antenna port(s) for the DL data channel may be indicated as QCLs together with different sets of RS antenna port(s).

[0074] FIG. 9a is an example of beam sweeping in a DL channel. In the RRC_INACTIVE or 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 the SS beam to multiple beams along with forming the SS burst (940). One or more SS blocks may be transmitted on a single beam. When multiple SS bursts (940) are transmitted to multiple beams, the SS bursts may together form an SS burst set (950).

[0075] A 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 CSI-RS. For example, based on RSRP measurements for CSI-RS, the wireless device may report a beam index associated with the RSRP value of the beam, as indicated in the CRI, for downlink beam selection. CSI-RS may be transmitted over a CSI-RS resource comprising at least one antenna port and at least one time or frequency radio resource. The CSI-RS resource 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 the cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell may measure the wireless device-specific CSI-RS resource.

[0076] CSI-RS resources can be transmitted periodically using non-periodic transmission or multi-shot or semi-continuous transmission. For example, in the periodic transmission of FIG. 9a, the base station (120) can periodically transmit the configured CSI-RS resources (940) using periodicity configured in the time domain. In non-periodic transmission, the configured CSI-RS resources can be transmitted in a dedicated time slot. In multi-shot or semi-continuous transmission, the configured CSI-RS resources can be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beam width than the beam used for SS-block transmission.

[0077] FIG. 9b is an example of a beam management procedure in an exemplary new wireless access technology network. A base station (120) and / or a 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 the wireless device (110) and one or more base stations (120). In one example, the P-1 procedure (910) may be used to enable the wireless device (110) to measure one or more transmission (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). For beam forming at the base station (120), the base station (120) may sweep a set of different TX beams. For beamforming in the wireless device (110), the wireless device (110) may sweep a set of different Rx beams. In one 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) in order to enable the wireless device (110) to change a first set of Tx beams associated with the base station (120). The P-2 procedure (920) may be performed on a beam set for smaller beam refinement than in the P-1 procedure (910). The P-2 procedure (920) may be a special case of the P-1 procedure (910). In one 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) in order to change a first set of Rx beams associated with the wireless device (110).

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

[0079] In an exemplary embodiment, the new wireless access technology network may support Bandwidth Adaptation (BA). In one example, the receiving and / or transmitting bandwidth configured by a UE using BA may not be large. For example, the receiving and / or transmitting bandwidth may not be as large as the cell bandwidth. The receiving and / or transmitting bandwidth may be adjustable. For example, the UE may change the receiving and / or transmitting bandwidth to contract, for example, during periods of low activity, to save power. For example, the UE may change the position of the receiving and / or transmitting bandwidth in the frequency domain, for example, to increase scheduling flexibility. For example, the UE may change the subcarrier spacing to allow for different services.

[0080] In an exemplary embodiment, a subset of the cell's total cell bandwidth may be referred to as a Bandwidth Part (BWP). A base station may configure one or more BWPs to achieve BA for a UE. For example, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0081] FIG. 10 is an exemplary diagram of three BWPs configured, namely BWP1 (1010 and 1050) with a width of 40 MHz and a subcarrier spacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz and a subcarrier spacing of 15 kHz; and BWP3 (1030) with a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0082] In one example, a UE configured to operate on one or more BWPs of a cell may be configured by one or more upper layers (e.g., RRC layers) for a cell, such as a set of one or more BWPs (e.g., up to 4 BWPs) for transmission by the UE (set of UL BWPs) in the UL bandwidth by at least one parameter UL-BWP for the cell, and a set of one or more BWPs (e.g., set of DL BWPs) for reception by the UE (e.g., set of 4 BWPs) in the DL bandwidth by at least one parameter DL-BWP.

[0083] To enable BA on a PCell, the base station may configure one or more UL and DL BWP pairs on the UE. To enable BA on a SCell (e.g., for CA), the base station may configure at least one DL BWP on the UE (e.g., there may be nothing in the UL).

[0084] In one example, the initial active DL BWP may be defined by at least one of the location and number of adjacent PRBs for a set of control resources for at least one common search space, subcarrier spacing, or periodic prefix code. For operation on a PCell, one or more upper-level parameters may represent at least one initial UL BWP for a random access procedure. When a secondary carrier on a primary cell is configured on a UE, an initial BWP for a random access procedure on the secondary carrier may be configured on that UE.

[0085] In one example, for unpaired spectrum operation, the UE can expect the center frequency for the DL BWP to be the same as the center frequency for the UL BWP.

[0086] For example, for each DL BWP or UL BWP within a set of one or more DL BWPs or one or more UL BWPs, the base station may semi-statistically configure one or more parameters representing at least one of the following to a given UE for a given cell: subcarrier spacing; periodic prefix code; a plurality of adjacent PRBs; an index within a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and a UL BWP in the configured set of DL BWPs and UL BWPs; DCI sensing for PDSCH reception timing; PDSCH reception for HARQ-ACK transmission timing value; DCI sensing for PUSCH transmission timing value; an offset of the first PRB of each of the DL bandwidth or UL bandwidth for the first PRB of the bandwidth.

[0087] In one example, for a DL BWP within a set of one or more DL BWPs on a PCell, the base station may configure at least one type of common search space and / or one or more sets of control resources for a UE-specific search space. For example, the base station may not configure the UE so that there is no common search space on the PCell or PSCell in the active DL BWP.

[0088] For a UL BWP within one or more UL BWP sets, the base station may configure one or more resource sets for one or more PUCCH transmissions to the UE.

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

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

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

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

[0093] In one example, if the UE is configured to have a default DL BWP and a timer value among the configured DL BWPs for the secondary cell, the UE procedure for the secondary cell may be the same as that for the primary cell using the default DL BWP and the timer value for the secondary cell.

[0094] In one example, when a base station configures a first active DL BWP and a first active UL BWP on a secondary cell or carrier for a UE, the UE may use the indicated DL BWP and indicated UL BWP on the secondary cell as individual first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0095] FIGS. 11a and 11b illustrate packet flow using multiple connections (e.g., dual connection, multiple connection, strict interoperability, and / or others). FIG. 11a is an exemplary diagram of the protocol structure of a wireless device (110) (e.g., UE) having CA and / or multiple connections according to one aspect of an embodiment. FIG. 11b is an exemplary diagram of the protocol structure of a plurality of base stations having CA and / or multiple connections according to one aspect of an embodiment. The plurality of base stations may include a master node, MN (1130) (e.g., master node, master base station, master gNB, master eNB, similar) and secondary nodes, SN (1150) (e.g., secondary base station, secondary gNB, secondary eNB, and / or others). The master node (1130) and the secondary nodes (1150) may cooperate to communicate with the wireless device (110).

[0096] When multiple connections are configured for a wireless device (110), the wireless device (110), capable of supporting multiple receive / transmit functions in an RRC connection state, may be configured to utilize wireless resources provided by multiple schedulers of multiple base stations. Multiple base stations may be interconnected via non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and / or etc.). A base station associated with multiple connections for a specific wireless device may perform at least one of two different roles: the base station may operate as a master base station or a secondary base station. In multiple connections, the wireless device may be connected to one master base station and one or more secondary base stations. In one example, the master base station (e.g., MN (1130)) may provide a master cell group (MCG) comprising a primary cell and / or one or more secondary cells for the wireless device (e.g., wireless device (110)). A secondary base station (e.g., SN (1150)) may provide a secondary cell group (SCG) comprising a first secondary cell (PSCell) and / or one or more secondary cells for a wireless device (e.g., wireless device (110)).

[0097] In a multiple connection, the wireless protocol architecture used by the bearer depends on how the bearer is configured. In one example, three different types of bearer setup options may be supported: an MCG bearer, an SCG bearer, and / or a split bearer. A wireless device may receive / transmit packets from an MCG bearer through one or more cells of an MCG and / or receive / transmit packets from an SCG bearer through one or more cells of an SCG. A multiple connection may also be described as having at least one bearer configured to use wireless resources provided by a secondary base station. A multiple connection may not be configured or implemented in some of the exemplary embodiments.

[0098] In one example, a wireless device (e.g., wireless device (110)) can transmit and / or receive packets of an MCG bearer through 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)); Packets of a split bearer can be transmitted and / or received through an SDAP layer (e.g., SDAP (1110)), a PDCP layer (e.g., NR PDCP (1112)), one of a master or secondary RLC layer (e.g., MN RLC (1115, SN RLC (1116)), and one of a master or secondary MAC layer (e.g., MN MAC (1118, SN MAC (1119))); and / or packets of an SCG bearer can be transmitted and / or received through 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 (1119)).

[0099] In one example, a master base station (e.g., MN (1130)) and / or a secondary base station (e.g., SN (1150)) may transmit / receive packets of an MCG bearer through a master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), a master or secondary node PDCP layer (e.g., NR PDCP (1121), NR PDCP (1142)), a master node RLC layer (e.g., MN RLC (1124), MN RLC (1125)), and a master node MAC layer (e.g., MN MAC (1128)); and a master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), a master or secondary node PDCP layer (e.g., NR PDCP (1122), NR PDCP (1143)), a secondary node RLC layer (e.g., SN Packets of the SCG bearer can be transmitted / received through the RLC (1146), SN RLC (1147)), and secondary node MAC layer (e.g., SN MAC (1148)); packets of the split bearer can be transmitted / received through the master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), master or secondary node PDCP layer (e.g., NR PDCP (1123), NR PDCP (1141)), master or secondary node RLC layer (e.g., MN RLC (1126), SN RLC (1144), SN RLC (1145), MN RLC (1127)), and master or secondary node MAC layer (e.g., MN MAC (1128), SN MAC (1148)).

[0100] In a multiple connection, the wireless device may be configured with multiple MAC entities: one MAC entity for the master base station (e.g., MN MAC (1118)) and another MAC entity for the secondary base station (e.g., SN MAC 1119). In a multiple connection, the configured set of serving cells for the wireless device may include two subsets: an MCG comprising the serving cells of the master base station and an SCG comprising the serving cells of the secondary base station. For the SCG, one or more of the following configurations may apply: at least one cell of the SCG has a configured UL CC, and PUCCH resources are configured in at least one cell of the SCG designated as a primary secondary cell (PSCcell, PCell of the SCG, or sometimes so-called PCell); when the SCG is configured, there may be at least one SCG bearer or one split bearer; When a physical layer problem or random access problem is detected on the PSCell, or when multiple NR RLC retransmissions associated with the SCG arrive, or when an access problem is detected on the PSCell during an SCG addition or SCG change: the RRC connection re-establishment procedure may not be triggered, UL transmissions toward the cells of the SCG may be stopped, the master base station may be notified by the radio device of the type of SCG failure for the split bearer, and DL data transmission through the master base station may be maintained; an NR RLC acknowledged mode (AM) bearer may be configured for the split bearer; the PCell and / or PSCell may not be disabled; the PSCell may be changed by an SCG change procedure (e.g., by a security key change and RACH procedure); and / or a change in bearer type between the split bearer and the SCG bearer or simultaneous configuration of the SCG and the split bearer may be supported or not supported.

[0101] Regarding the interaction between a master base station and secondary base stations for multiple connections, one or more of the following may apply: the master base station and / or secondary base stations may maintain Radio Resource Management (RRM) measurement configurations of the radio device; the master base station may determine whether to request the secondary base station to provide additional resources (e.g., serving cells) for the radio device (based, e.g., received measurement reports, traffic states, and / or bearer types); upon receiving a request from the master base station, the secondary base station may create / modify a container that results in the configuration of additional serving cells for the radio device (or determine that the secondary base station does not have any resources available to do so); for UE performance tuning, the master base station may provide AS configurations and UE performances (parts thereof) to the secondary base station; the master base station and secondary base stations may exchange information regarding UE configurations by using RRC containers (inter-node messages) returned via Xn messages; The secondary base station may initiate the reconfiguration of the secondary base station present in the serving cells (e.g., PUCCH toward the secondary base station); the secondary base station may determine which cell is the PSCell within the SCG; the master base station may change or not change the contents of the RRC configurations provided by the secondary base station; in the case of SCG addition and / or SCG SCell addition, the master base station may provide the most recent (or most up-to-date) measurement results for the SCG cell(s); the master base station and the secondary base station may receive information of each other's SFN and / or subframe offsets from the OAM and / or through the Xn interface (e.g., for the purpose of DRX alignment and / or identification of measurement gaps).In one example, when adding a new SCG SCell, dedicated RRC signaling can be used to transmit necessary system information of the cell, such as CA, excluding the SFN obtained from the MIB of the SCG's PSCell.

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

[0103] In an exemplary 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 Msg1 (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 Msg1 (1220) transmissions and one or more Msg2 (1230) transmissions.

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

[0105] In one example, Msg1 (1220) may be one or more transmissions of random access preambles. In a contention-based random access procedure, the UE may select an SS block having an RSRP higher than the RSRP threshold. If a random access preamble group B exists, the UE may select one or more random access preambles from group A or group B according to the potential Msg3 (1240) size. If a random access preamble group B does not exist, the UE may select one or more random access preambles from group A. The UE may randomly select a random access preamble index from one or more random access preambles associated with the selected group (e.g., with equal probability or a normal distribution). If the base station constructs the association between the random access preambles and the SS blocks for the UE semi-statistically, 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.

[0106] 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 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-RSs for the UE. If at least one of the associated SS blocks having an RSRP higher than a first RSRP threshold, or at least one of the associated CSI-RSs having an RSRP higher than a second RSRP threshold, 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 a beam failure recovery request.

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

[0108] The UE can 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 to have an association between one or more PRACH occasions and one or more SS blocks, the UE can determine a PRACH occasion from one or more PRACH occasions corresponding to the selected SS block. For example, if the UE selects a CSI-RS and is configured to have an association between one or more PRACH occasions and one or more CSI-RSs, the UE can determine a PRACH occasion from one or more PRACH occasions corresponding to the selected CSI-RSs. The UE can transmit the selected random access preamble to the base station through the selected PRACH occasions. The UE can determine the transmission power for the transmission of the selected random access preamble based on at least an initial preamble power and a power-ramping factor. The UE can determine the RA-RNTI associated with the selected PRACH occasion in which the selected random access preamble is transmitted. For example, the UE cannot determine the RA-RNTI for a beam failure recovery request. The UE can determine the RA-RNTI based on at least the index of the first OFDM symbol and the index of the first slot of the selected PRACH time and / or the uplink carrier index for the transmission of Msg1 (1220).

[0109] In one example, the UE may receive a random access response, Msg2 (1230), from a base station. To monitor the random access response, the UE may use a predetermined time window (e.g., ra-ResponseWindow ) can be initiated. For a beam failover request, the base station can provide the UE with different time windows (e.g.,) to monitor the response to the beam failover request. bfr-ResponseWindow ...can be configured. For example, the UE may start a time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at the beginning of the first PDCCH period 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 a time window at the beginning of the first PDCCH period after a fixed duration of one or more symbols from the end of the first preamble transmission. The UE may monitor the cell's PDCCH for at least one random access response identified by RA-RNTI or at least one response to a beam failure recovery request identified by C-RNTI while a timer runs for a predetermined time window.

[0110] In one example, if at least one random access response contains a random access preamble identifier corresponding to a random access preamble transmitted by the UE, the UE may consider the reception of the random access response successful. If the reception of the random access response is successful, the UE may consider it a successfully completed contentless random access procedure. If a contentless random access procedure is triggered for a beam failure recovery request, the UE may consider the contentless random access procedure to be successfully completed if the PDCCH transmission is addressed to C-RNTI. In one example, if at least one random access response contains a random access preamble identifier, the UE may consider the random access procedure to be successfully completed and may indicate the reception of an acknowledgment for a system information request to a higher layer. If the UE has signaled multiple preamble transmissions, the UE may stop the transmission of any remaining preambles (if any) in response to the successful reception of the corresponding random access response.

[0111] In one example, the UE may perform one or more Msg3 (1240) transmissions in response to the successful reception of a random access response (e.g., for a contention-based random access procedure). The UE may adjust uplink transmission timing based on a timing advanced command indicated by the random access response and transmit one or more transmission blocks based on an uplink acknowledgment indicated by the random access response. The subcarrier interval for the PUSCH transmission of Msg3 (1240) may be provided by at least one upper layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and Msg3 (1240) through the PUSCH of the same cell. The base station may indicate the UL BWP for the PUSCH transmission of Msg3 (1240) through a system information block. The UE may use HARQ for the retransmission of Msg3 (1240).

[0112] In one example, multiple UEs can perform Msg1 (1220) by transmitting the same preamble to a base station and receiving the same random access response from the base station containing an identity (e.g., TC-RNTI). Contention resolution (1250) can ensure that a UE does not incorrectly use another UE's identity. For example, contention resolution (1250) can be based on a C-RNTI on the PDCCH or a UE contention resolution identity on the DL-SCH. For example, if the base station assigns a C-RNTI to a UE, the UE can perform contention resolution (1250) based on the reception of a PDCCH transmission addressed to the C-RNTI. In response to the detection of the C-RNTI on the PDCCH, the UE can consider the contention resolution (1250) successful and the random access procedure to be successfully completed. If the UE does not have a valid C-RNTI, contention resolution can be handled by using a TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU contains a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 (1250), the UE can be considered to have successfully resolved the contention (1250) and the random access procedure can be considered to have been successfully completed.

[0113] FIG. 13 is an exemplary structure for MAC entities according to one aspect of one embodiment. In one example, a wireless device may be configured to operate in a multiple connection mode. A wireless device in an RRC_CONNECTED state having multiple RX / TX may be configured to use wireless resources provided by multiple schedulers located at multiple base stations. Multiple base stations may be connected via an Xn interface through a non-ideal or ideal backhaul. In one example, a base station within the multiple base stations may operate as a master base station or a secondary base station. The wireless device may be connected to one master base station and one or more secondary base stations. Multiple MAC entities may be configured on the wireless device, for example, one MAC entity for the master base station and one or more other MAC entities for the secondary base station(s). In one example, a configured set of serving cells for the wireless device may include two subsets: an MCG comprising serving cells of the master base station and one or more SCGs comprising serving cells of the secondary base station(s). FIG. 13 illustrates an exemplary structure for a MAC entity when the MCG and SCG are configured for a wireless device.

[0114] In one example, at least one cell within the SCG may have a configured UL CC, wherein the cell of at least one cell may be referred to as the PSCell or PCell of the SCG, or sometimes simply as the PCell. PUCCH resources may be configured in the PSCell. In one example, when the SCG is configured, there may be at least one SCG bearer or one split bearer. In one example, upon detection of a physical layer problem or random access problem on the PSCell, or upon reaching multiple RLC retransmissions associated with the SCG, or upon detection of an access problem on the PSCell during SCG addition or SCG change: the RRC connection re-establishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the master base station may be notified of the SCG failure type by the UE, and DL data transmission through the master base station may be maintained.

[0115] In one example, the MAC sublayer may provide services such as data transmission and wireless resource allocation to upper layers (e.g., 1310 or 1320). The MAC sublayer may include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer may provide data transmission services over a logical channel. Multiple types of logical channels may be defined to accommodate different types of data transmission services. A logical channel may support the transmission of a specific type of information. Logical channel types may be defined according to what type of information (e.g., control or data) is transmitted. For example, BCCH, PCCH, CCCH, and DCCH may be control channels, and DTCH may be a traffic channel. In one example, the first MAC entity (e.g., 1310) may provide services to PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In one example, a second MAC entity (e.g., 1320) can provide services to BCCH, DCCH, DTCH, and MAC control elements.

[0116] The MAC sublayer may anticipate physical layer services (e.g., 1330 or 1340), such as data transmission services, HARQ feedback signaling, scheduling requests, or measurement (e.g., CQI) signaling. In one example, in a duplex connection, two MAC entities may be configured for a wireless device, one for the MCG and one for the SCG. The MAC entities of the wireless device may handle multiple transmission channels. In one example, the first MAC entity may handle a first transmission channel comprising the PCCH of the MCG, the 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 one example, the second MAC entity can handle a second transmission channel comprising 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.

[0117] In one example, if one or more SCells are configured in a MAC entity, multiple DL-SCHs may exist, and multiple RACHs as well as multiple UL-SCHs may exist for each MAC entity. In one example, one DL-SCH and one UL-SCH may exist on an SpCell. In one example, for a SCell, one DL-SCH, or zero or one UL-SCH, and zero or one RACH may exist. A DL-SCH may support reception using different numerologies and / or TTI durations within a MAC entity. Additionally, a UL-SCH may support transmission using different numerologies and / or TTI durations within a MAC entity.

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

[0119] FIG. 14 is an exemplary diagram of a RAN architecture including one or more base stations. In one example, protocol stacks (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at the nodes. A base station (e.g., gNB(120A or 120B)) may 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, 1430D)) when a functional split is configured. The upper protocol layers of the base station may be located in the base station CU, and the lower layers of the base station may be located within the base station DU. An F1 interface connecting the base station CU and the base station DU (e.g., a CU-DU interface) may be an ideal or ideal backhaul. F1-C can provide control plane connectivity through the F1 interface, and F1-U can provide user plane connectivity through the F1 interface. In one example, the Xn interface can be configured between base station CUs.

[0120] In one example, the base station CU may include RRC functions, SDAP layers, and PDCP layers, and the base station DU may include RLC layers, MAC layers, and PHY layers. In one example, various functional partitioning options between the base station CU and the base station DU may be possible by locating different combinations of upper protocol layers (RAN functions) within the base station CU and lower protocol layers (RAN functions) within the base station DU. Functional partitioning can support the flexibility to move protocol layers between the base station CU and the base station DU depending on service requirements and / or network environments.

[0121] In one example, the functional splitting options may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or at other granularities. In each base station CU split, the base station CU may have a fixed splitting option, and the base station DU may be configured to match the splitting option of the base station CU. In each base station DU split, different splitting options may be configured in the base station DU, and the base station CU may provide different splitting options for different base station DUs. In each UE split, the base station (base station CU and at least one base station DU) may provide different splitting options for different radio devices. In each bearer split, different splitting options may be available for different bearers. In each slice splice, different splitting options may be applied to different slices.

[0122] FIG. 15 is an example diagram illustrating an RRC state transition of a wireless device. In one example, the wireless device may be in at least one RRC state among 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 one 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) that can have UE status information of the wireless device. UE context information (e.g., wireless device context information) may include at least one of access layer context information, one or more wireless link configuration parameters, bearer configuration information (e.g., data wireless bearer (DRB), signaling wireless bearer (SRB), logical channel, QoS flow, PDU session, and / or others), security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In one example, in an RRC idle state, the wireless device may not have an RRC connection with the base station, and the UE context information of the wireless device may not be stored at the base station. In one example, in an RRC inactive state, the wireless device may not have an RRC connection with the base station. The UE context information of the wireless device may be stored at a base station that may be called an anchor base station (e.g., end serving base station).

[0123] In one example, the wireless device may switch the UE RRC state in two ways between the RRC idle state and the RRC connected state (e.g., disconnect (1540) or establish connection (1550) or re-establish connection) and / or in two ways between the RRC inactive state and the RRC connected state (e.g., disable connection (1570) or resume connection (1580)). In one example, the wireless device may switch its RRC state from the RRC inactive state to the RRC idle state (e.g., disconnect (1560)).

[0124] In one example, the anchor base station may be a base station capable of maintaining the wireless device's UE status information (wireless device status information) during the time period when the wireless device remains in the anchor base station's RAN notification area (RNA) and / or when the wireless device remains in an RRC inactive state. In one example, the anchor base station may be the base station where the wireless device in an RRC inactive state was last connected in the latest RRC connection state or where the wireless device last performed the RNA update procedure. In one example, the RNA may include one or more cells operated by one or more base stations. In one example, a base station may belong to one or more RNAs. In one example, a cell may belong to one or more RNAs.

[0125] In one example, the wireless device can switch the UE RRC state at the base station from an RRC connected state to an RRC inactive state. The wireless device can 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, the IP address of the base station, an AS status information identifier of the wireless device, a resumption identifier, and / or other such identifiers.

[0126] In one example, an anchor base station may broadcast a message (e.g., a RAN paging message) to base stations of RNA to reach radio devices in an RRC-inactive state, and / or base stations capable of receiving a message from the anchor base station may broadcast and / or multicast other messages (e.g., paging messages) to radio devices within their coverage area, cell coverage area, and / or beam coverage area associated with RNA via an air interface.

[0127] In one example, when a radio device in an RRC-inactive state moves to a new RNA, the radio device may perform an RNA update (RNAU) procedure that may include a random access procedure and / or a UE situation information retrieval procedure by the radio device. UE situation information retrieval may include receiving a random access preamble from the radio device by the base station; and fetching the radio device's UE situation information from the old anchor base station by the base station. Fetching may include transmitting a retrieval UE situation information request message containing a resumption identifier to the old anchor base station, and receiving a retrieval UE situation information response message containing the radio device's UE situation information from the old anchor base station.

[0128] In an exemplary embodiment, a wireless device in an RRC-inactive state may select a cell to camp on based on at least one measurement result for one or more cells, i.e., a cell where the wireless device can monitor RNA paging messages and / or core network paging messages from a base station. In one example, the wireless device in an RRC-inactive state may select a cell to perform a random access procedure to resume an RRC connection and / or transmit one or more packets to a base station (e.g., a network). In one example, if the selected cell belongs to an RNA different from the RNA for the wireless device in an RRC-inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In one example, if the wireless device in an RRC-inactive state transmits one or more packets to a network in a buffer, the wireless device may initiate a random access procedure to transmit one or more packets to the base station of the cell selected by the wireless device. The random access procedure can be performed with two messages (e.g., two-stage random access) and / or four messages (e.g., four-stage random access) between the wireless device and the base station.

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

[0130] A gNB can communicate with a wireless device through a wireless network utilizing one or more novel wireless access technologies. The one or more wireless technologies may include at least one of a number of technologies related to the physical layer, a number of technologies related to the media access control layer, and / or a number of technologies related to the wireless resource control layer. Exemplary embodiments that enhance one or more wireless technologies can improve the performance of the wireless network. Exemplary embodiments can increase system throughput or data transmission speed. Exemplary embodiments can reduce battery consumption of the wireless device. Exemplary embodiments can improve the latency of data transmission between the gNB and the wireless device. Exemplary embodiments can improve the network coverage of the wireless network. Exemplary embodiments can improve the transmission efficiency of the wireless network.

[0131] A gNB can transmit one or more MAC PDUs to a wireless device. In one example, the MAC PDU may be a bit sequence whose length is aligned in bytes (e.g., a multiple of 8 bits). In one example, the bit sequence may be represented by tables where the leftmost bit of the first line of the table is the most significant bit and the rightmost bit of the last line of the table is the least significant bit. More generally, the bit sequence may be read from left to right, followed by the reading order of the rows. In one example, the bit order of the parameter fields within the MAC PDU is represented by the first most significant bit of the leftmost bit and the last least significant bit of the rightmost bit.

[0132] In one example, the MAC SDU may be a bit sequence of byte-aligned length (e.g., a multiple of 8 bits). In one example, the MAC SDU may be included in the MAC PDU starting from the first bit.

[0133] In one example, MAC CE can be a bit sequence of length aligned in bytes (e.g., a multiple of 8 bits).

[0134] In one example, the MAC subheader may be a bit sequence of byte-aligned length (e.g., a multiple of 8 bits). In one example, the MAC subheader may be placed immediately before the corresponding MAC SDU, MAC CE, or padding.

[0135] In one example, the MAC entity can ignore the value of the reserved bit in the DL MAC PDU.

[0136] In one example, a MAC PDU may include one or more MAC sub-PDUs. The MAC sub-PDUs of one or more MAC sub-PDUs may include only a MAC sub-header (including padding); a MAC sub-header and a MAC SDU; a MAC sub-header and a MAC CE; and / or a MAC sub-header and padding. In one example, a MAC SDU may be of variable size. In one example, a MAC sub-header may correspond to a MAC SDU, a MAC CE, or padding.

[0137] In one example, where the MAC subheader corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC subheader may include an R field of 1 bit length; an F field of 1 bit length; an LCID field of multiple bit length; and / or an L field of multiple bit length.

[0138] FIG. 16a illustrates an example of a MAC subheader having an R field, an F field, an LCID field, and an L field. In the exemplary MAC subheader of FIG. 16a, the LCID field may have a length of 6 bits, and the L field may have a length of 8 bits. FIG. 16b illustrates an example of a MAC subheader having an R field, an F field, an LCID field, and an L field. In the exemplary MAC subheader of FIG. 16b, the LCID field may have a length of 6 bits, and the L field may have a length of 16 bits.

[0139] In one example, where the MAC subheader corresponds to a fixed-size MAC CE or padding, the MAC subheader may include an R field of 2 bits in length and an LCID field of multiple bits in length. FIG. 16c illustrates an example of a MAC subheader having an R field and an LCID field. In the exemplary MAC subheader of FIG. 16c, the LCID field may be 6 bits in length and the R field may be 2 bits in length.

[0140] FIG. 17a illustrates an example of a DL MAC PDU. In the example of FIG. 17a, multiple MAC CEs, such as MAC CE 1 and MAC CE 2, may be placed together. A MAC sub-PDU containing MAC CEs may be placed before any MAC sub-PDU containing a MAC SDU or a MAC sub-PDU containing padding.

[0141] FIG. 17b illustrates an example of a UL MAC PDU. In the example of FIG. 17b, multiple MAC CEs, such as MAC CE 1 and MAC CE 2, may be placed together. A MAC sub-PDU containing MAC CEs may be placed after any MAC sub-PDU containing a MAC SDU. Additionally, a MAC sub-PDU may be placed before a MAC sub-PDU containing padding.

[0142] In one example, the MAC entity of the gNB may transmit one or more MAC CEs to the MAC entity of the wireless device. FIG. 18 illustrates an example of multiple LCIDs that may be associated with one or more MAC CEs. In the example of FIG. 18, one or more MAC CEs include at least one of the following: SP ZP CSI-RS resource set enable / disable MAC CE; PUCCH spatial relationship enable / disable MAC CE; SP SRS enable / disable MAC CE; SP CSI report for PUCCH enable / disable MAC CE; TCI status indication for UE-specific PDCCH MAC CE; TCI status indication for UE-specific PDSCH MAC CE; non-periodic CSI trigger status subselect MAC CE; SP CSI-RS / CSI-IM resource set enable / disable MAC CE; UE contention resolution identity MAC CE; timing advance command MAC CE; DRX command MAC CE; long DRX command MAC CE; SCell enable / disable MAC CE (1 octet); A MAC CE that enables / disables SCell (4 octets); and / or enables / disables replication MAC CE. In one example, a MAC CE such as the MAC CE that the gNB's MAC entity transmits to the wireless device's MAC entity may have an LCID in the MAC subheader corresponding to the MAC CE. Another MAC CE may have a different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given as 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0143] In one example, the MAC entity of the wireless device may transmit one or more MAC CEs to the MAC entity of the gNB. FIG. 19 illustrates an example of one or more MAC CEs. 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 acknowledgment MAC CE; a single-entry PHR MAC CE; a multi-entry PHR MAC CE; a short frustum BSR; and / or a long frustum BSR. In one example, a MAC CE may have an LCID in the MAC subheader corresponding to this MAC CE. Another MAC CE may have a different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given as 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short frustum command MAC CE.

[0144] In Carrier Aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may use the CA technique to receive or transmit one or more CCs simultaneously, depending on the capabilities of the wireless device. In one example, the wireless device may support CA for adjacent CCs and / or non-adjacent CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCell).

[0145] When CA is configured, the wireless device may establish a single RRC connection with the network. During RRC connection establishment / re-establishment / handover, the cell providing NAS mobility information may be the serving cell. During the RRC connection re-establishment / handover procedure, the cell providing security input may be the serving cell. In one example, the serving cell may represent a PCell. In one example, the gNB may transmit one or more messages to the wireless device, including configuration parameters of one or more SCells, depending on the capabilities of the wireless device.

[0146] When CA is configured, the base station and / or wireless device may utilize the SCell enable / disable mechanism to improve the battery or power consumption of the wireless device. When one or more SCells are configured in the wireless device, the gNB may enable or disable at least one of the one or more SCells. When configuring a SCell, the SCell may be disabled unless the SCell state associated with the SCell is set to "enabled" or "dormant".

[0147] In one example, a wireless device can enable / disable SCell in response to receiving a SCell enable / disable MAC CE.

[0148] In one example, the gNB is a SCell timer (e.g.,) to the wireless device. sCellDeactivationTimer One or more messages including ) can be transmitted. In one example, the wireless device can disable SCell in response to the expiration of the SCell timer.

[0149] When a wireless device receives a SCell enable / disable MAC CE, the wireless device may enable the SCell. In response to SCell enable, the wireless device may perform operations including SRS transmission on the SCell; CQI / PMI / RI / CRI reporting to the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and / or PUCCH transmission on the SCell.

[0150] In one example, the wireless device responds to SCell activation by providing a first SCell timer associated with the SCell (e.g., sCellDeactivationTimer The wireless device may start or restart the SCell timer in the corresponding slot when a SCell enable / disable MAC CE that enables the SCell is received. In one example, the wireless device may (re)initialize one or more suspended configured uplink acknowledgments of configured acknowledgment type 1 associated with the SCell according to the stored configuration in response to the SCell enable. In one example, the wireless device may trigger a PHR in response to the SCell enable.

[0151] When a wireless device receives a SCell enable / disable MAC CE that disables an enabled SCell, the wireless device may disable the enabled SCell. In one example, a first SCell timer associated with the enabled SCell (e.g., sCellDeactivationTimer When ) expires, the wireless device may disable the active SCell. In response to the disablement of the active SCell, the wireless device may stop the first SCell timer associated with the active SCell. In one example, in response to the disablement of the active SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink acknowledgments of configured uplink acknowledgment type 2 associated with the active SCell. In one example, in response to the disablement of the active SCell, the wireless device may suspend one or more configured uplink acknowledgments of configured uplink acknowledgment type 1 associated with the active SCell; and / or empty the HARQ buffers associated with the active SCell.

[0152] In one example, when the SCell is disabled, the wireless device may not perform operations including SRS transmission on the SCell; CQI / PMI / RI / CRI reporting to the SCell; transmission on the UL-SCH on the SCell; transmission on the RACH on the SCell; monitoring of at least one first PDCCH on the SCell; monitoring of at least one second PDCCH on the SCell; and / or PUCCH transmission on the SCell.

[0153] In one example, when at least one first PDCCH on an active SCell indicates an uplink acknowledgment or a downlink assignment, the wireless device has a first SCell timer associated with the active SCell (e.g., sCellDeactivationTimer ) can be restarted. In one example, if at least one second PDCCH on a serving cell scheduling an active SCell (e.g., a PCell or SCell configured with PUCCH, i.e., a PUCCH Scell) indicates an uplink acknowledgment or downlink assignment for the active SCell, the wireless device may use a first SCell timer associated with the active SCell (e.g., sCellDeactivationTimer You can restart ).

[0154] In one example, when SCell is disabled, if there is a random access procedure in progress on SCell, the wireless device can stop the random access procedure in progress on SCell.

[0155] FIG. 20a illustrates an example of a single octet SCell enable / disable MAC CE. A first MAC PDU subheader having a first LCID (e.g., '111010' as shown in FIG. 18) can identify the single octet SCell enable / disable MAC CE. The single octet SCell enable / disable MAC CE may have a fixed size. The single octet SCell enable / disable MAC CE may contain a single octet. The single octet may contain a first number (e.g., 7) of C-fields and a second number (e.g., 1) of R-fields.

[0156] FIG. 20b illustrates an example of a SCell-enabled / disabled MAC CE of four octets. A second MAC PDU subheader having a second LCID (e.g., '111001' as shown in FIG. 18) can identify the SCell-enabled / disabled MAC CE of four octets. The SCell-enabled / disabled MAC CE of four octets may have a fixed size. The SCell-enabled / disabled MAC CE of four octets may contain four octets. The four octets may contain a third number (e.g., 31) of C-fields and a fourth number (e.g., 1) of R-fields.

[0157] In FIG. 20a and / or FIG. 20b, when a SCell having SCell index i is configured, C i The field can indicate the enabled / disabled status of the SCell with SCell index i. In one example, C i When the field is set to 1, the SCell with SCell index i can be enabled. In one example, C i When the field is set to 0, the SCell with SCell index i may be disabled. In one example, if there is no SCell configured to have SCell index i, the wireless device C i The field can be ignored. In FIG. 20a and FIG. 20b, the R field may represent a reserved bit. The R field may be set to 0.

[0158] When CA is configured, the base station and / or radio device may utilize a hibernation mechanism for the SCell to improve the battery or power consumption of the radio device and / or improve the latency of SCell activation / deactivation. When the radio device hibernates the SCell, the SCell may enter a sleep state. In response to the SCell entering a sleep state, the radio device may stop SRS transmission on the SCell; while in the sleep state, may report CQI / PMI / RI / PTI / CRI to the SCell according to the periodicity configured for the SCell; may not transmit on the UL-SCH on the SCell; may not transmit on the RACH on the SCell; may not monitor the PDCCH on the SCell; may not monitor the PDCCH for the SCell; and / or may not transmit the PUCCH on the SCell. In one example, when the SCell is in a sleep state, reporting a CSI for the SCell without monitoring the PDCCH on or toward the SCell can provide the base station with a CSI that is always updated for the SCell. According to the always-updated CSI, the base station can use fast / fast or accurate channel adaptive scheduling on the SCell once the SCell is switched back to an active state, thereby accelerating the SCell activation process. In one example, when the SCell is in a sleep state, reporting a CSI for the SCell without monitoring the PDCCH on or toward the SCell can improve the battery or power consumption of the wireless device while providing timely and / or accurate channel information feedback to the base station. In one example, the PCell / PSCell and / or PUCCH secondary cell may not be configured or may be switched to a sleep state.

[0159] When one or more SCells are configured, the gNB can activate, hibernate, or deactivate at least one of the one or more SCells. In one example, the gNB can transmit one or more RRC messages to a wireless device that include parameters indicating at least one SCell set to an active, hibernating, or inactive state.

[0160] In one example, when the SCell is active, the wireless device can perform the following: transmit SRS on the SCell; report CQI / PMI / RI / CRI to the SCell; monitor PDCCH on the SCell; monitor PDCCH for the SCell; and / or transmit PUCCH / SPUCCH on the SCell.

[0161] In one example, when the SCell is inactive, the wireless device may not transmit SRS to the SCell; may not report CQI / PMI / RI / CRI to the SCell; may not transmit from the UL-SCH on the SCell; may not transmit from the RACH on the SCell; may not monitor the PDCCH on the SCell; may not monitor the PDCCH for the SCell; and / or may not transmit PUCCH / SPUCCH to the SCell.

[0162] In one example, when the SCell is in a sleep state, the wireless device may not transmit SRS to the SCell; may report CQI / PMI / RI / CRI to the SCell; may not transmit from the UL-SCH on the SCell; may not transmit from the RACH on the SCell; may not monitor the PDCCH on the SCell; may not monitor the PDCCH for the SCell; and / or may not transmit PUCCH / SPUCCH to the SCell.

[0163] When one or more SCells are configured, the gNB can enable, hibernate, or disable at least one of the one or more SCells. In one example, the gNB can transmit one or more MAC control elements to a wireless device, the MAC control elements including parameters indicating the enable, disable, or hibernation of at least one SCell.

[0164] In one example, the gNB may transmit a first MAC CE (e.g., an enable / disable MAC CE such as shown in FIG. 20a or FIG. 20b) indicating the enable or disablement of at least one SCell to a wireless device. In FIG. 20a and / or FIG. 20b, if a SCell having SCell index i is configured, C i The field can indicate the enabled / disabled status of the SCell with SCell index i. In one example, C i When the field is set to 1, the SCell with SCell index i can be enabled. In one example, C i When the field is set to 0, the SCell with SCell index i may be disabled. In one example, if there is no SCell configured to have SCell index i, the wireless device C i The field can be ignored. In FIG. 20a and FIG. 20b, the R field may represent a reserved bit. In one example, the R field may be set to 0.

[0165] In one example, the gNB may transmit a second MAC CE (e.g., hibernation MAC CE) to a wireless device indicating the activation or hibernation of at least one SCell. In one example, the second MAC CE may be associated with a second LCID different from the first LCID of the first MAC CE (e.g., activation / deactivation MAC CE). In one example, the second MAC CE may have a fixed size. In one example, the second MAC CE may consist of a single octet comprising seven C fields and one R field. FIG. 21a illustrates an example of a second MAC CE having a single octet. In another example, the second MAC CE may consist of four octets comprising thirty-one C fields and one R field. FIG. 21b illustrates an example of a second MAC CE having four octets. In one example, a second MAC CE having four octets may be associated with a third LCID different from the second LCID of a second MAC CE having a single octet and / or the first LCID of an enabled / disabled MAC CE. In one example, if there is no SCell with a serving cell index greater than 7, a second MAC CE having one octet may be applied, otherwise a second MAC CE having four octets may be applied.

[0166] In one example, when the second MAC CE is received and the first MAC CE is not received, C i is SCell index i If there is a SCell configured, the SCell index i It can indicate the dormant / active state of SCell having, otherwise the MAC entity is C i The field can be ignored. In one example, C i If set to "1", the wireless device is the SCell index i You can put the associated SCell into a dormant state. In one example, C i If set to "0", the wireless device is the SCell index i You can activate the SCell associated with it. In one example, C i is set to "0" and SCell index i If a SCell with is in a sleep state, the wireless device is the SCell index i You can enable SCell having. In one example, C i is set to "0" and SCell index i If the SCell having is not in a sleep state, the wireless device is C i You can ignore the field.

[0167] In one example, when both the first MAC CE (enable / disable MAC CE) and the second MAC CE (hibernation MAC CE) are received, the two Cs of the two MAC CEs i The field is a SCell index i If there is a SCell composed of, the SCell index i It can represent possible state transitions of SCell having, and otherwise the MAC entity is C i The field can be ignored. In one example, the C of 2 MAC CEs i The field can be interpreted according to Fig. 21c.

[0168] When one or more SCells are configured, the gNB may enable, hibernate, or disable at least one of the one or more SCells. In one example, the MAC entity of the gNB and / or wireless device may set a SCell disable timer for each configured SCell (excluding cases where PUCH / SPUCCH is configured in the SCell) (e.g., sCellDeactivationTimer It maintains ) and can disable the associated SCell upon the timer's expiration.

[0169] In one example, the MAC entity of the gNB and / or wireless device uses a SCell hibernation timer for each configured SCell (excluding cases where PUCH / SPUCCH is configured in the SCell) (e.g., sCellHibernationTimer ) is maintained, and if the SCell is in a disabled state, the associated SCell can be hibernated upon the expiration of the SCell hibernation timer. In one example, if both the SCell disable timer and the SCell hibernation timer are configured, the SCell hibernation timer may take precedence over the SCell disable timer. In one example, if both the SCell disable timer and the SCell hibernation timer are configured, the gNB and / or wireless device may ignore the SCell disable timer regardless of the SCell disable timer expiration.

[0170] In one example, the MAC entity of the gNB and / or wireless device has a sleep SCell disable timer for each configured SCell (excluding cases where PUCH / SPUCCH is configured in the SCell) (e.g., dormantSCellDeactivationTimer ) is maintained, and if SCell is in a sleep state, the associated SCell can be disabled upon the expiration of the sleep SCell disable timer.

[0171] In one example, when a SCell is configured to be enabled upon SCell configuration, the MAC entity of the wireless device can enable the SCell. In one example, when the MAC entity of the wireless device receives MAC CE(s) that enable the SCell, the MAC entity can enable the SCell. In one example, the MAC entity can start or restart the SCell disable timer associated with the SCell in response to SCell activation. In one example, the MAC entity can start or restart the SCell hibernation timer associated with the SCell (if configured) in response to SCell activation. In one example, the MAC entity can trigger a PHR procedure in response to SCell activation.

[0172] In one example, when the MAC entity of a wireless device receives MAC CE(s) indicating the disablement of SCell, the MAC entity may disable SCell. In one example, in response to receiving MAC CE(s), the MAC entity may disable SCell; stop the SCell disable timer associated with SCell; and / or empty all HARQ buffers associated with SCell.

[0173] In one example, if the SCell disable timer associated with an active SCell expires and the SCell hibernation timer is not configured, the MAC entity can disable the SCell; stop the SCell disable timer associated with the SCell, and / or empty all HARQ buffers associated with the SCell.

[0174] In one example, when a first PDCCH on an active SCell indicates an uplink acknowledgment or a downlink assignment, or a second PDCCH on a serving cell scheduling the active SCell indicates an uplink acknowledgment or a downlink assignment for the active SCell, or when a MAC PDU is transmitted from a configured uplink acknowledgment or received from a configured downlink assignment, the MAC entity restarts the SCell deactivation timer associated with the SCell; and / or restarts the SCell hibernation timer associated with the SCell if the SCell is configured. In one example, when the SCell is deactivated, a random access procedure in progress on the SCell may be interrupted.

[0175] In one example, when a SCell associated with a SCell state set to sleep state during SCell configuration is configured in a MAC entity, or when the MAC entity receives MAC CE(s) indicating that the SCell is being put to sleep state, the MAC entity may put the SCell to sleep state and send one or more CSI reports for the SCell; stop the SCell disable timer associated with the SCell; stop the SCell hibernation timer associated with the SCell if the SCell is configured; start or restart the sleep SCell disable timer associated with the SCell; and / or flush all HARQ buffers associated with the SCell. In one example, when the SCell hibernation timer associated with an active SCell expires, the MAC entity may hibernate the SCell; stop the SCell disable timer associated with the SCell; stop the SCell hibernation timer associated with the SCell; and / or flush all HARQ buffers associated with the SCell. In one example, when the dormant SCell disable timer associated with the dormant SCell expires, the MAC entity disables the SCell; and / or stops the dormant SCell disable timer associated with the SCell. In one example, when the SCell is in a dormant state, a random access procedure in progress on the SCell may be interrupted.

[0176] FIG. 22 illustrates DCI formats for an example of 20 MHz FDD operation in an LTE system where the base station has two Tx antennas and there is no carrier aggregation. In an NR system, the DCI format may include at least one of the following: DCI format 0_0 / 0_1 indicating the scheduling of PUSCH on the cell; DCI format 1_0 / 1_1 indicating the scheduling of PDSCH on the cell; DCI format 2_0 notifying a group of UEs of a slot format; DCI format 2_1 notifying a group of UEs of PRB(s) and OFDM symbol(s), wherein the UE may assume that the transmission is not intended for that UE; DCI format 2_2 indicating the transmission of TPC commands for PUCCH and PUSCH; and / or DCI format 2_3 indicating the transmission of a group of TPC commands for SRS transmission by one or more UEs. In one example, the gNB may transmit a DCI via the PDCCH for scheduling decisions and power control commands. More specifically, the DCI may include at least one of downlink scheduling assignments, uplink scheduling acknowledgments, and power control commands. Downlink scheduling assignments may include at least one of a PDSCH resource indication, a transmission format, HARQ information, and control information related to a number of antenna modes, and a command for power control of the PUCCH used for transmitting ACK / NACK in response to the downlink scheduling assignments. Uplink scheduling acknowledgments may include at least one of a PUSCH resource indication, a transmission format, and HARQ-related information, and a power control command of the PUSCH.

[0177] In one example, different types of control information may correspond to different DCI message sizes. For example, in supporting spatial multiplexing with non-contiguous allocation of RBs in the frequency domain, larger scheduling messages may be required compared to uplink acknowledgments that allow only contiguous allocation of frequencies. DCI can be classified into different DCI formats, one format corresponding to a specific message size and usage.

[0178] In one example, a UE may monitor one or more PDCCH candidates to detect one or more DCIs in one or more DCI formats. One or more PDCCHs may be transmitted in a common search space or a UE-specific search space. To conserve power consumption, the UE may monitor PDCCHs with only a limited set of DCI formats. For example, a normal UE may not need to detect DCIs having DCI format 6, which is used by eMTC UEs. To detect more DCI formats, more power may be consumed by the UE.

[0179] In one example, one or more PDCCH candidates monitored by a UE can be defined in terms of PDCCH UE-specific search spaces. CCE aggregation level In PDCCH UE, the specific search space is at the CCE aggregation level It can be defined by a set of PDCCH candidates for. In one example, for the DCI format, the UE has a CCE aggregation level per serving cell by one or more higher-level parameters. A number of PDCCH candidates can be formed.

[0180] In one example, in non-DRX mode operation, the UE controls resource sets Can be configured by one or more higher-level parameters for Control resource set based on the periodicity of symbols One or more PDCCH candidates within can be monitored.

[0181] In one example, information within DCI formats used for downlink scheduling may be organized into different groups comprising at least one of: a carrier indicator (0 or 3 bits), resource information consisting of RB allocation; HARQ process number; MCS, NDI, and RV (for the first TB); MCS, NDI, and RV (for the second TB); MIMO-related information; PDSCH resource-element mapping and QCI; downlink allocation index (DAI); TPC for PUCCH; SRS request (1 bit) triggering one-shot SRS transmission; ACK / NACK offset; DCI format 0 / 1A indication used to distinguish between DCI format 1A and 0; and padding (if necessary), wherein the corresponding fields exist as they vary between DCI formats. MIMO-related information may include at least one of PMI, pre-coding information, transmission block swap flag, power offset between PDSCH and reference signal, reference signal scrambling sequence, number of layers, and / or antenna ports for transmission.

[0182] In one example, the information within the DCI formats used for uplink scheduling may be organized into different groups comprising at least one of the following: resource information consisting of a carrier indicator, resource allocation type, and RB allocation; MCS, NDI (for the first TB); MCS, NDI (for the second TB); phase rotation of the uplink DMRS; pre-coding information; a CSI request requesting a non-periodic CSI report; an SRS request (2 bits) used to trigger a non-periodic SRS transmission using one of up to three pre-configured settings; uplink index / DAI; TPC for PUSCH; DCI format 0 / 1A indication; and padding (if necessary), wherein the corresponding fields exist as they vary between the DCI formats.

[0183] In one example, the gNB may perform Cyclic Redundancy Check (CRC) scrambling for the DCI before transmitting the DCI via PDCCH. The gNB may perform CRC scrambling using the CRC bits of the DCI by bitwise sum (or modulo-2 addition or exclusive OR (XOR) operation) of multiple bits of at least one radio device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI, SI-RNTI, RA-RNTI, and / or MCS-C-RNTI). When the radio device detects the DCI, it may examine the CRC bits of the DCI. The radio device may receive the DCI when the CRC is scrambled by a sequence of bits identical to at least one radio device identifier.

[0184] In an NR system, to support wide bandwidth operation, a gNB can transmit one or more PDCCHs in different sets of control resources. The gNB can transmit one or more RRC messages containing configuration parameters of one or more sets of control resources. At least one of the one or more sets of control resources may include at least one of a first OFDM symbol, a number of consecutive OFDM symbols, a set of resource blocks, a CCE-to-REG mapping, and a REG bundle size in the case of interleaved CCE-to-REG mapping.

[0185] A base station (gNB) may enable bandwidth adaptation (BA) in a PCell by configuring an uplink (UL) bandwidth portion (BWP) and a downlink (DL) BWP in a wireless device (UE). Once carrier aggregation is configured, the gNB may enable BA in a SCell by additionally configuring at least DL BWP(s) in the UE (i.e., there may be no UL BWP in the UL). In the case of a PCell, the initial active BWP may be a first BWP used for initial access. In the case of a SCell, the first active BWP may be a second BWP configured for the UE to operate in the SCell when the SCell is activated.

[0186] In paired spectrum (e.g., FDD), the gNB and / or UE can switch the DL BWP and UL BWP independently. In unpaired spectrum (e.g., TDD), the gNB and / or UE can switch the DL BWP and UL BWP simultaneously.

[0187] In one example, the gNB and / or UE can switch BWPs between configured BWPs using a DCI or BWP inactivity timer. If a BWP inactivity timer is configured for a serving cell, the gNB and / or UE can switch the active BWP to the default BWP in response to the expiration of the BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network.

[0188] In one example, for an FDD system, if a BA is configured, one UL BWP and one DL BWP for each uplink carrier can be activated at once in an active serving cell. In one example, for a TDD system, one DL / UL BWP pair can be activated at once in an active serving cell. Operation of one UL BWP and one DL BWP (or one DL / UL pair) can improve UE battery consumption. BWPs other than the one active DL BWP and one active UL BWP that the UE can operate on may be disabled. In disabled BWPs, the UE may not monitor the PDCCH and / or transmit on the PUCCH, PRACH, and UL-SCH.

[0189] In one example, a serving cell may be configured with a maximum first number (e.g., 4) of BWPs. In one example, in an active serving cell, there may be one active BWP at any given time.

[0190] In one example, BWP switching for a serving cell may be used to enable an inactive BWP and disable an active BWP at a time. In one example, BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink acknowledgment. In one example, BWP switching is controlled by a BWP inactive timer (e.g., bwp-InactivityTimer It can be controlled by ). In one example, BWP switching may be controlled by a MAC entity in response to the initiation of a random access procedure. Upon addition of SpCell or activation of SCell, one BWP may be initially activated without receiving a PDCCH indicating downlink assignment or uplink acknowledgment. The active BWP for the serving cell may be indicated by RRC and / or PDCCH. In one example, for unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common to both UL and DL.

[0191] FIG. 23 illustrates an example of BWP switching in a SCell. In one example, a UE may receive an RRC message containing the parameters of the SCell and one or more BWP configurations associated with the SCell. The RRC message is an RRC connection reconfiguration message (e.g., RRCReconfiguration ); RRC connection re-establishment message (e.g., RRCRestablishment ); and / or RRC connection setup messages (e.g., RRCSetup It may include ). Among one or more BWPs, at least one BWP may be configured as a first active BWP (e.g., BWP 1 in FIG. 23), and one BWP may be configured as a default BWP (e.g., BWP 0 in FIG. 23). The UE may receive a MAC CE that activates the SCell in the nth slot. The UE may use a SCell disable timer (e.g., sCellDeactivationTimer ) can be initiated, CSI-related operations for SCell can be initiated, and / or CSI-related operations for the first active BWP of SCell can be initiated. In response to SCell activation, the UE can start PDCCH monitoring on BWP 1.

[0192] In one example, in response to receiving a DCI indicating a DL allocation from BWP 1, the UE mIn the nth slot, the BWP inactive timer (e.g., bwp-InactivityTimer ) can be restarted. The UE is s When the BWP inactive timer expires in the i-th slot, it can switch back to the default BWP (e.g., BWP 0) as the active BWP. The UE sCellDeactivationTimer You can disable SCell and / or stop the BWP inactivity timer when it expires.

[0193] When multiple cells with wide bandwidths (e.g., 1 GHz) are configured in the UE, the power consumption of the UE can be further reduced by using a BWP inactive timer. When there is no activity in the active BWP, the UE can transmit or receive only at a narrow bandwidth BWP (e.g., 5 MHz) in the PCell or SCell.

[0194] In one example, a MAC entity may apply normal operations in an active BWP to an active serving cell in which a BWP is configured, including the following: sending in UL-SCH; sending in RACH; PDCCH monitoring; PUCCH sending; DL-SCH receiving; and / or, if a stored configuration exists, an operation to (re)initialize any suspended configured uplink acknowledgment of configured acknowledgment type 1 according to that stored configuration.

[0195] In one example, in an inactive BWP for each active serving cell configured with a BWP, the MAC entity may not transmit on UL-SCH; may not transmit on RACH; may not monitor PDCCH; may not transmit PUCCH; may not transmit SRS; may not receive DL-SCH; may clear any configured downlink assignment and configured uplink acknowledgment of configured acknowledgment type 2; and / or may suspend configured uplink acknowledgment of configured type 1.

[0196] In one example, if a MAC entity receives a PDCCH for BWP switching of a serving cell while a random access procedure associated with the serving cell is not in progress, the UE can perform BWP switching to the BWP indicated by the PDCCH.

[0197] In one example, if the bandwidth sub-indicator field is configured in DCI format 1_1, the bandwidth sub-indicator field value may represent an active DL BWP from a configured DL BWP set for DL ​​reception. In one example, if the bandwidth sub-indicator field is configured in DCI format 0_1, the bandwidth sub-indicator field value may represent an active UL BWP from a configured UL BWP set for UL transmission.

[0198] In one example, for a primary cell, the UE may be provided with a default DL BWP among the configured DL BWPs as the upper-level parameter Default-DL-BWP. If the UE is not provided with a default DL BWP as the upper-level parameter Default-DL-BWP, the default DL BWP may be the initial active DL BWP.

[0199] In one example, the timer value for the primary cell in the UE is a higher-level parameter bwp-InactivityTimer It may be provided as. If a UE is configured, the UE may increase the timer at intervals of 1 millisecond in the case of frequency range 1 if the timer is running, or at intervals of 0.5 milliseconds in the case of frequency range 2 if the UE may not detect DCI format 1_1 for paired spectrum operation or if the UE may not detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation during the interval.

[0200] In one example, for a secondary cell in the UE, a higher-level parameter Default-DL-BWP is configured to represent the default DL BWP among the configured DL BWPs, and a higher-level parameter representing a timer value in the UE bwp-InactivityTimer If configured, the UE procedure in the secondary cell may be the same as in the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0201] In one example, for a secondary cell or carrier, if a first active DL BWP is configured with the upper layer parameter Active-BWP-DL-SCell and a first active UL BWP is configured with the upper layer parameter Active-BWP-UL-SCell, the UE may use the indicated DL BWP and the indicated UL BWP in the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0202] In one example, a wireless device may transmit one or more uplink control information (UCI) to a base station via one or more PUCCH resources. One or more UCIs may include at least one of HARQ-ACK information; a scheduling request (SR); and / or a CSI report. In one example, a PUCCH resource may be identified by a PUCCH format associated with at least a frequency position (e.g., start PRB) and / or an initial cyclic shift of the base sequence and time domain position (e.g., start symbol index). In one example, the PUCCH format may be PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, or PUCCH format 4. PUCCH format 0 may have a length of one or two OFDM symbols and may be 2 bits or less. PUCCH format 1 may occupy 4 to 14 OFDM symbols and may be 2 bits or less. PUCCH format 2 can occupy one or two OFDM symbols and can be larger than 2 bits. PUCCH format 3 can occupy four to fourteen OFDM symbols and can be larger than 2 bits. PUCCH format 4 can occupy four to fourteen OFDM symbols and can be larger than 2 bits. PUCCH resources can be configured on a PCell or a PUCCH secondary cell.

[0203] In one example, if a base station is configured with a plurality of uplink BWPs, it may transmit one or more RRC messages to a wireless device containing configuration parameters of one or more sets of PUCCH resources (e.g., up to four sets) on one of the uplink BWPs. Each set of PUCCH resources includes a PUCCH resource set index, and each PUCCH resource includes a PUCCH resource identifier (e.g., pucch-Resourceid A list of PUCCH resources identified by ) and / or a maximum number of UCI information bits that a wireless device can transmit using one of a plurality of PUCCH resources within a set of PUCCH resources may be configured.

[0204] In one example, if one or more PUCCH resource sets are configured therein, the wireless device may select one of the one or more PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ARQ bits, SR, and / or CSI) to be transmitted by the wireless device. In one example, if the total bit length of the UCI information bits is 2 or less, the wireless device may select a first PUCCH resource set having a PUCCH resource set index equal to "0". In one example, if the total bit length of the UCI information bits is greater than 2 and less than or equal to a first configured value, the wireless device may select a second PUCCH resource set having a PUCCH resource set index equal to "1". In one example, if the total bit length of the UCI information bits is greater than a first configured value and less than or equal to a second configured value, the wireless device may select a third PUCCH resource set having a PUCCH resource set index equal to "2". In one example, if the total bit length of the UCI information bits is greater than the second configured value and less than or equal to the third value (e.g., 1706), the wireless device may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

[0205] In one example, a wireless device may determine one PUCCH format from a plurality of PUCCH formats, including PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, and / or PUCCH format 4, based on a plurality of uplink symbols and a plurality of UCI bits of a UCI transmission. In one example, the wireless device may transmit a UCI in a PUCCH using PUCCH format 0 when the transmission spans one or two symbols and the number of HARQ-ACK information bits having positive or negative SR (HARQ-ACK / SR bits) is one or two. In one example, the wireless device may transmit a UCI in a PUCCH using PUCCH format 1 when the transmission spans four or more symbols and the number of HARQ-ACK / SR bits is one or two. In one example, if the transmission spans one or two symbols and the number of UCI bits is greater than 2, the wireless device may transmit the UCI on the PUCCH using PUCCH format 2. In one example, if the transmission spans four or more symbols and the number of UCI bits is greater than 2, and the PUCCH resource does not contain an orthogonal cover code, the wireless device may transmit the UCI on the PUCCH using PUCCH format 3. In one example, if the transmission spans four or more symbols and the number of UCI bits is greater than 2, and the PUCCH resource contains an orthogonal cover code, the wireless device may transmit the UCI on the PUCCH using PUCCH format 4.

[0206] In one example, to transmit HARQ-ACK information on a PUCCH resource, a wireless device may determine a PUCCH resource from a set of PUCCH resources. The set of PUCCH resources may be determined as described above. The wireless device may determine a PUCCH resource based on a PUCCH resource indicator field within a DCI received on a PDCCH (e.g., having DCI format 1_0 or DCI format 1_1). A 3-bit PUCCH resource indicator field within the DCI may indicate one of eight PUCCH resources within the set of PUCCH resources. The wireless device may transmit HARQ-ACK information on the PUCCH resource indicated by the 3-bit PUCCH resource indicator field within the DCI.

[0207] In one example, the wireless device can transmit one or more UCI bits through the PUCCH resource of the active uplink BWP of the PCell or PUCCH secondary cell. Since at most one active uplink BWP in the cell is supported for the wireless device, the PUCCH resource indicated in the DCI is naturally the PUCCH resource on the cell's active uplink BWP.

[0208] In one example, DRX operation may be used by a wireless device (UE) to improve UE battery life. In one example, in DRX, the UE may discontinuously monitor downlink control channels, such as PDCCH or EPDCCH. In one example, the base station may configure a set of DRX parameters for DRX operation, for example, using RRC configuration. The set of DRX parameters may be selected based on the application type so that the wireless device can reduce power and resource consumption. In one example, because the UE may be in a DRX sleep / off state when data arrives at the UE and the base station may wait until the UE switches to a DRX ON state, the UE may receive data packets with increased delay in response to the DRX being configured / activated.

[0209] In one example, during DRX mode, the UE can turn off power to most of its circuitry when there are no packets to be received. The UE can monitor the PDCCH discontinuously in DRX mode. The UE can monitor the PDCCH continuously when DRX operation is not set. During this time, the UE listens to the downlink (DL) (or monitors the PDCCH), which is called the DRX active state. In DRX mode, the time when the UE does not listen to or monitor the PDCCH is called the DRX sleep state.

[0210] FIG. 24 illustrates an example of an embodiment. The gNB may transmit an RRC message containing one or more DRX parameters of a DRX cycle. One or more parameters may include a first parameter and / or a second parameter. The first parameter may represent a first time value of the DRX active state of the DRX cycle (e.g., DRX on duration). The second parameter may represent a second time value of the DRX sleep state of the DRX cycle (e.g., DRX off duration). One or more parameters may further include a predetermined duration of the DRX cycle. During the DRX active state, the UE may monitor the PDCCH to detect one or more DCIs in the serving cell. During the DRX sleep state, the UE may stop monitoring the PDCCH on the serving cell. When multiple cells are in an active state, the UE may monitor all PDCCHs on (or toward) those multiple cells during the DRX active state. During the DRX off duration, the UE may stop monitoring all PDCCHs on (or toward) multiple cells. The UE may repeat the DRX operation according to one or more DRX parameters.

[0211] In one example, DRX can be beneficial to the base station. In one example, if DRX is not configured, the wireless device may frequently transmit periodic CSI and / or SRS (e.g., based on configuration). If DRX is configured, during the DRX off period, the UE may not transmit periodic CSI and / or SRS. The base station can allocate these resources to other UEs to improve resource utilization efficiency.

[0212] In one example, the MAC entity may be configured by an RRC having a DRX function that controls a UE’s downlink control channel (e.g., PDCCH) monitoring activities for a plurality of RNTIs for the MAC entity. The plurality of RNTIs may include at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-permanent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. In one example, the MAC entity may monitor the PDCCH discontinuously using the DRX operation in response to being in RRC_CONNECTED if the DRX is configured; otherwise, the MAC entity may monitor the PDCCH continuously.

[0213] In one example, RRC can control DRX operations by setting multiple timers. The multiple timers may include: a DRX on duration timer (e.g., drx-onDurationTimer ); DRX inactive timer(e.g., drx-InactivityTimer ); Downlink DRX HARQ RTT Timer(e.g., drx-HARQ-RTT-TimerDL ); Uplink DRX HARQ RTT Timer(e.g., drx-HARQ-RTT-TimerUL ); Downlink retransmission timer(e.g., drx-RetransmissionTimerDL ); Uplink retransmission timer(e.g., drx-RetransmissionTimerUL ); short DRX configuration (e.g., drx-ShortCycle and / or drx-ShortCycleTimer One or more parameters of ); and long DRX configuration (e.g., drx-LongCycle One or more parameters of ). In one example, the time granularity for the DRX timer can be expressed in PDCCH subframes (e.g., indicated as psf in the DRX configuration) or milliseconds.

[0214] In one example, in response to the setting of a DRX cycle, the active time may include the time during which at least one timer is running. At least one timer drx-onDurationTimer , drx-InactivityTimer , drx-RetransmissionTimerDL , drx-RetransmissionTimerUL , or mac-ContentionResolutionTimer It may include.

[0215] In one example, drx-Inactivity-Timer It can specify the duration for which the UE can be activated after successfully decoding a PDCCH representing a new transmission (UL or DL ​​or SL). In one example, this timer may be restarted when receiving a PDCCH for a new transmission (UL or DL ​​or SL). In one example, the UE may be switched to DRX mode in response to the expiration of this timer (e.g., using a short DRX cycle or a long DRX cycle).

[0216] In one example, drx-ShortCycle may be a first type of DRX cycle that the UE must follow when entering DRX mode (e.g., if configured). In one example, DRX-Config IE indicates a short cycle length.

[0217] In one example, drx-ShortCycleTimer can be expressed as a multiple of shortDRX-Cycle. The timer can indicate the number of initial DRX cycles that follow a short DRX cycle before entering a long DRX cycle.

[0218] In one example, drx-onDurationTimer It can specify the duration at the start of the DRX cycle (e.g., DRX ON). In one example, drx-onDurationTimer can indicate the duration before entering sleep mode (DRX off).

[0219] In one example, drx-HARQ-RTT-TimerDLIt can specify the minimum duration from the time a new transmission is received until the UE can expect a retransmission of the same packet. In one example, this timer can be fixed and may not be configured by RRC.

[0220] In one example, drx-RetransmissionTimerDL can represent the maximum duration for which the UE can monitor PDCCH when a retransmission from eNodeB is expected by the UE.

[0221] In one example, in response to the configuration of the DRX cycle, the active time may include the time when a scheduling request is sent from PUCCH and is pending.

[0222] In one example, in response to the configuration of the DRX cycle, the active time may include the time when an uplink acknowledgment for a pending HARQ retransmission occurs and there is data in the corresponding HARQ buffer for the synchronous HARQ process.

[0223] In one example, in response to the configuration of the DRX cycle, the active time may include a time when a PDCCH representing a new transmission addressed to the C-RNTI of the MAC entity is not received after the successful reception of a random access response to a preamble not selected by the MAC entity.

[0224] In one example, DRX can be configured for a wireless device. The DL HARQ RTT timer may expire in a subframe, and the data of the corresponding HARQ process may not be successfully decoded. The MAC entity for the corresponding HARQ process drx-RetransmissionTimerDL Can start.

[0225] In one example, DRX can be configured for a wireless device. The UL HARQ RTT timer can expire in a subframe. The MAC entity for the corresponding HARQ process drx-RetransmissionTimerDL Can start.

[0226] In one example, DRX can be configured for a wireless device. A DRX command MAC control element or a long DRX command MAC control element may be received. The MAC entity is drx-onDurationTimer Stop and drx-InactivityTimer It can stop.

[0227] In one example, DRX can be configured for a wireless device. In one example, drx-InactivityTimer It may expire, or a DRX command MAC control element may be received in a subframe. In one example, in response to a short DRX cycle being configured, the MAC entity drx-ShortCycleTimer It can be started or restarted, and a short DRX cycle can be used. Otherwise, the MAC entity can use a long DRX cycle.

[0228] In one example, DRX can be configured for a wireless device. In one example, drx-ShortCycleTimer It can expire in a subframe. MAC entities can use long DRX cycles.

[0229] In one example, DRX can be configured for a wireless device. In one example, a long DRX command MAC control element can be received. The MAC entity is drx-ShortCycleTimer You can stop and use a long DRX cycle.

[0230] In one example, DRX can be configured for a wireless device. In one example, a short DRX cycle is used and [(SFN * 10) + number of subframes] mod ( drx-ShortCycle ) = ( drxStartOffset ) mod ( drx-ShortCycle In the case of ) (mod is modular), the wireless device is drx-onDurationTimer You can start.

[0231] In one example, DRX can be configured for a wireless device. In one example, a long DRX cycle is used and [(SFN * 10) + number of subframes] mod ( drx-longCycle ) = drxStartOffset In this case, the wireless device is drx-onDurationTimer You can start.

[0232] FIG. 25 illustrates an example of DRX operation in a legacy system. The base station can transmit an RRC message containing configuration parameters for the DRX operation. The base station can transmit a DCI for downlink resource allocation to the UE via the PDCCH. The UE drx-InactivityTimer It can start, and during that time, the UE can monitor the PDCCH. The UE drx-InactivityTimer When it is running, after receiving a transmission block (TB), the HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL ) can be started, and during this time, the UE can stop PDCCH monitoring. The UE can send a NACK to the base station when TB reception fails. When the HARQ RTT timer expires, the UE monitors the PDCCH and the HARQ retransmission timer (e.g., drx-RetransmissionTimerDL ) can be started. When the HARQ retransmission timer is running, the UE can receive a second DCI indicating a DL acknowledgment for the retransmission of the TB. If the UE does not receive the second DCI before the HARQ retransmission timer expires, the UE can stop PDCCH monitoring.

[0233] In LTE / LTE-A or 5G systems, when DRX operation is configured, the UE may monitor the PDCCH to detect one or more DCIs during the DRX active time of the DRX cycle. To reduce power consumption, the UE may stop monitoring the PDCCH during the DRX sleep / off time of the DRX cycle. In some cases, because one or more DCIs are not addressed to the UE, the UE may not detect one or more DCIs during the DRX active time. For example, the UE may be a URLLC UE, an NB-IoT UE, or an MTC UE. The UE may not always have data received from the gNB, and in this case, waking up to monitor the PDCCH during the DRX active time may cause unnecessary power consumption. Power consumption can be further reduced, particularly during the DRX active time, by using a wake-up mechanism combined with the DRX operation. FIGS. 26a and 26b illustrate examples of wake-up mechanisms.

[0234] As illustrated in FIG. 26a, the gNB may transmit one or more messages to the UE containing parameters of the wake-up duration (or sleep duration). The wake-up duration may be located a number of slots (or symbols) prior to the DRX-on duration of the DRX cycle. The number of slots (or symbols), or the gap between the wake-up duration and the DRX-on duration, may be configured in one or more RRC messages or determined as a predetermined fixed value. The gap may be used for at least one of synchronization with the gNB; reference signal measurement; and / or RF parameter readjustment. The gap may be determined based on the performance of the UE and / or the gNB. In one example, the wake-up mechanism may be based on a wake-up signal. The parameters of the wake-up duration may include at least one of the wake-up signal format (e.g., numerology, sequence length, sequence code, etc.); periodicity of the wake-up signal; duration value of the wake-up duration; and frequency position of the wake-up signal. In the LTE Re.15 specification, a wake-up signal for paging may include a signal sequence (e.g., Zadoff-Chu sequence) generated based on the following cell identification (e.g., cell ID): . In this example, And, am.

[0235] In one example, , here . can be the cell ID of the serving cell. M can be the number of subframes that can be transmitted by WUS, and and, here is the maximum number of subframes that can be transmitted by WUS. It can be a scrambling sequence (e.g., a 31-character gold sequence), which at the start of transmission of the WUS It can be initialized to, and here is the first frame of the first paging opportunity associated with WUS, and is the first slot of the first paging opportunity associated with WUS.

[0236] In one example, the wake-up duration parameter may be predetermined without RRC configuration. In one example, the wake-up mechanism may be based on a wake-up channel (e.g., PDCCH or DCI). The wake-up duration parameter may include at least one of the wake-up channel format (e.g., numerology, DCI format, PDCCH format); the periodicity of the wake-up channel; and the set of control resources and / or search space of the wake-up channel. If the wake-up duration parameter is configured therein, the UE may monitor the wake-up signal or wake-up channel during the wake-up duration. In response to receiving the wake-up signal / channel, the UE may initiate to monitor the PDCCH as expected according to the DRX configuration. In one example, in response to receiving the wake-up signal / channel, the UE during the DRX active time (e.g., drx-onDurationTimer (When running) the UE can monitor the PDCCH. If the UE does not receive the PDCCH during the DRX active time, it can return to a sleep state. The UE can remain in a sleep state during the DRX off duration of the DRX cycle. In one example, if the UE does not receive a wake-up signal / channel during the wake-up duration, the UE can skip PDCCH monitoring during the DRX active time. This mechanism can reduce power consumption for PDCCH monitoring during the DRX active time. In this example, during the wake-up duration, the UE can monitor only the wake-up signal / channel. During the DRX off duration, the UE can stop monitoring the PDCCH and the wake-up signal / channel. During the DRX active duration, if the UE receives the wake-up signal / channel within the wake-up duration, it can monitor the PDCCH excluding the wake-up signal / channel. In one example, the gNB and / or UE may apply a wake-up mechanism to the paging operation when the UE is in the RRC_idle state or RRC_inactive state, or to the connected DRX operation (C-DRX) when the UE is in the RRC_CONNECTED state.

[0237] In one example, the wake-up mechanism may be based on a go-to-sleep signal. FIG. 26b illustrates one example. The gNB may transmit one or more messages to the UE containing parameters of the wake-up duration (or sleep duration). One or more messages may include at least one RRC message. At least one RRC message includes one or more cell-specific or cell-common RRC messages (e.g., ServingCellConfig IE, ServingCellConfigCommon IE, MAC-CellGroupConfig It may include IE). The wake-up duration may be located in a number of slots (or symbols) prior to the DRX-on duration of the DRX cycle. The number of slots (or symbols) may be configured in one or more RRC messages or determined by a fixed value in advance. In one example, the wake-up mechanism may be based on a go-to-sleep signal. The parameters of the wake-up duration may include at least one of the go-to-sleep signal format (e.g., numerology, sequence length, sequence code, etc.); periodicity of the go-to-sleep signal; duration value of the wake-up duration; and frequency position of the go-to-sleep signal. In one example, the wake-up mechanism may be based on a go-to-sleep channel (e.g., PDCCH or DCI). The parameters of the wake-up duration may include at least one of the go-to-sleep channel format (e.g., numerology, DCI format, PDCCH format); periodicity of the go-to-sleep channel; and a set of control resources and / or a search space of the go-to-sleep channel. If the wake-up duration parameter is configured, the UE can monitor the go-to-sleep signal or go-to-sleep channel during the wake-up duration. In response to receiving the go-to-sleep signal / channel, the UE can return to sleep during the DRX active time and skip PDCCH monitoring. In one example, if the UE does not receive the go-to-sleep signal / channel during the wake-up duration, the UE can monitor the PDCCH during the DRX active time. This mechanism can reduce power consumption for PDCCH monitoring during the DRX active time.

[0238] In one example, a power saving operation associated with a DRX operation and based on a wake-up or go-to-sleep indication may be extended to cases independent of the DRX operation. In one example, the base station and / or wireless device may dynamically enable or disable the power saving operation regardless of the DRX configuration.

[0239] FIG. 27 illustrates an exemplary embodiment of dynamic activation / deactivation of a power saving mode. A base station (e.g., gNB in ​​FIG. 27) may transmit one or more RRC messages containing configuration parameters of a power saving mode (PS in FIG. 27) to a wireless device (e.g., UE in FIG. 27). The one or more RRC messages may include one or more cell-specific or cell-common RRC messages (e.g., ServingCellConfig IE, ServingCellConfigCommon IE, MAC-CellGroupConfig It may include IE). One or more RRC messages are RRC connection reconfiguration messages (e.g., RRCReconfiguration ); RRC connection re-establishment message (e.g., RRCRestablishment ); and / or RRC connection setup messages (e.g., RRCSetup It may include ). In one example, the cell may be a primary cell (e.g., PCell), a PUCCH secondary cell if a secondary PUCCH group is configured, or a primary secondary cell (e.g., PSCell) if a dual linkage is configured. The cell may be identified by a cell-specific identity (e.g., cell ID) (or may be associated with that identity).

[0240] In one example, the configuration parameters may include parameters of at least one power saving mode configuration on the cell. Each of the at least one power saving mode configuration may be identified by a power saving configuration identifier (index, indicator, or ID).

[0241] In one example, the power saving mode of the power saving mode configuration may be based on a power saving signal (e.g., a wake-up signal as shown in FIG. 26a and / or a go-to-sleep signal as shown in FIG. 26b). The parameters of the power saving signal-based power saving mode configuration may include at least one of the following: a window size of a time window indicating the duration for which the power saving signal may be transmitted; a transmission period value of the power saving signal; a time resource for which the power saving signal may be transmitted; a frequency resource for which the power saving signal may be transmitted; a BWP for which the wireless device may monitor the power saving signal; and / or a cell for which the wireless device may monitor the power saving signal.

[0242] In one example, the sleep mode may be based on a sleep channel (e.g., a wake-up channel (WUCH)). The sleep channel may include a downlink control channel (e.g., PDCCH) dedicated to the sleep mode. The parameters of the sleep channel-based sleep mode configuration may include at least one of the following: a time window indicating the duration during which a base station can transmit sleep information (e.g., wake-up information, or go-to-sleep information) through the sleep channel; parameters of a set of control resources (e.g., time, frequency resources, and / or TCI status indication of the sleep channel); the transmission period of the sleep channel; the DCI format of the sleep information; a BWP that allows a wireless device to monitor the sleep channel; and / or a cell that allows a wireless device to monitor the sleep channel.

[0243] In one example, a radio device in an RRC connection state can communicate with a base station in full-function mode (or normal-function mode). In full-function mode, the radio device can continuously monitor the PDCCH if no DRX operation is configured on the radio device. In full-function mode, if a DRX operation is configured (e.g., as shown in FIG. 24 or FIG. 25), the radio device can discontinuously monitor the PDCCH by applying one or more DRX parameters of the DRX operation. In full-function mode, the radio device can monitor the PDCCH; transmit SRS; transmit on the RACH; transmit on the UL-SCH; and / or receive the DL-SCH. In one example, the full-function mode in a given cell may be similar to or equivalent to the active state of the given cell.

[0244] As illustrated in FIG. 27, a wireless device may communicate with a base station in full-function mode. The base station may transmit a first command (e.g., the first command in FIG. 27) to the wireless device indicating the enabling of a power saving mode (PS as shown in FIG. 27) when, for example, data services are suitable for PS mode, or when the wireless device operates in PS mode due to reduced available processing power in the wireless device. The first command may be a DCI having a first DCI format (e.g., one of the DCI formats 0-0 / 0-1, 1-0 / 1-1, or 2-0 / 2-1 / 2-2 / 2-3 already defined in the 3GPP NR specification) or a second DCI format (e.g., a new DCI format to be defined in the future). The first command may be a MAC CE or an RRC message. In response to receiving the first command, the wireless device may enable (or activate) the PS mode and / or switch from full-function mode to PS mode. In one example, in PS mode, the wireless device may perform at least one of the following: monitoring the PS signal / channel; stopping the transmission of PUCCH / PUSCH / SRS / PRACH; stopping the reception of PDSCH; and / or not monitoring PDCCH. The PS mode may be referred to as the PS operation or PS state.

[0245] As illustrated in FIG. 27, a base station may transmit a second command (e.g., the second command in FIG. 27) to a wireless device indicating the disabling (or deactivation) of the PS mode. The base station may transmit the second command during a wake-up window (e.g., which may occur periodically in the time domain according to one or more configuration parameters of the PS mode). The wireless device may receive the second command while monitoring the PS signal / channel during the wake-up window. The second command may be a DCI having a first DCI format (e.g., one of the DCI formats 0-0 / 0-1, 1-0 / 1-1, or 2-0 / 2-1 / 2-2 / 2-3 already defined in the 3GPP NR specification) or a second DCI format (e.g., a new DCI format to be defined in the future). The second command may be a MAC CE or an RRC message. In response to receiving the second command, the wireless device may disable (or deactivate) the PS mode and / or switch from the PS mode to the full-function mode. In response to switching to the full-function mode as illustrated in FIG. 27, the wireless device may monitor the configured PDCCH. In response to switching to the full-function mode, the wireless device may monitor the PDCCH to detect a DCI having a CRC bit scrambled by at least one of the following: C-RNTI; P-RNTI; SI-RNTI; CS-RNTI; RA-RNTI; TC-RNTI; MCS-C-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; TPC-SRS-RNTI; INT-RNTI; SFI-RNTI; and / or SP-CSI-RNTI. In response to switching to the full-function mode, the wireless device transmits the SRS; transmits on the RACH; transmits on the UL-SCH; And / or DL-SCH can be received.

[0246] FIG. 28 illustrates an exemplary embodiment of a power saving mechanism. A base station (e.g., gNB in ​​FIG. 28) may transmit one or more RRC messages containing first configuration parameters of a power saving mode (PS in FIG. 28) to a wireless device (e.g., UE in FIG. 28).

[0247] In one example, the first configuration parameter may represent one or more PS parameters of a plurality of power saving modes. One or more PS parameters of the first power saving mode (PS mode 1 as shown in FIG. 28) may represent at least one of the following: one or more first search spaces and / or one or more first control resource sets (SS1 / CORESET1 in FIG. 28); one or more first DCI formats (DCI format 0-0, 1-0, or other DCI formats); and / or one or more first PS signal parameters (e.g., PS signal format; periodicity; time / frequency position). One or more PS parameters of the second power saving mode (PS mode 2 as shown in FIG. 28) may represent at least one of the following: one or more second search spaces and / or one or more second control resource sets (SS1 / CORESET1 and SS2 / CORESET2 as shown in FIG. 28); one or more second DCI formats; and / or one or more second PS signal parameters. In one example, one or more PS parameters of the power saving mode may indicate that the search space and / or control resource set is not configured in a given cell.

[0248] In one example, one or more RRC messages may further include one or more third search spaces and / or one or more third control resource sets (e.g., SS1 / CORESET1, SS2 / CORESET2, ..., SSn / CORESETn as shown in FIG. 28); and second configuration parameters representing one or more third DCI formats.

[0249] In one example, a radio device in an RRC connection state can communicate with a base station in full-function mode. In full-function mode, the radio device can monitor a PDCCH for one or more third DCI formats in one or more third search spaces of one or more third control resource sets. In full-function mode, the radio device can monitor the PDCCH discontinuously by applying one or more DRX parameters of a DRX operation when the DRX operation is configured (e.g., as illustrated in FIG. 24 and / or FIG. 25). In full-function mode, the radio device can monitor the PDCCH; transmit an SRS; transmit on a RACH; transmit on a UL-SCH; and / or receive a DL-SCH. In one example, when the radio device monitors a PDCCH in / for a cell; when transmitting an SRS in a cell; when transmitting on a RACH in a cell; when transmitting on a UL-SCH in a cell; When transmitting uplink control signals (e.g., CSI / SR / PUCCH) to a cell; and / or when receiving DL-SCH through the cell, the full functional mode of the cell may be similar (or equivalent) to the active state of the cell.

[0250] As illustrated in FIG. 28, a wireless device may communicate with a base station in full-function mode. The base station may transmit a first DCI (e.g., the first DCI in FIG. 28) to the wireless device indicating the enabling of a first power saving mode (PS mode 1 as shown in FIG. 28), for example, when a data service is suitable for the first PS mode or when the wireless device is operating in the first PS mode. The first DCI may be transmitted in a first DCI format (e.g., one of the DCI formats 0-0 / 0-1, 1-0 / 1-1, or 2-0 / 2-1 / 2-2 / 2-3 already defined in the 3GPP NR specification) or a second DCI format (e.g., a new DCI format to be defined in the future). In response to receiving the first DCI, the wireless device may enable (or activate) the first PS mode and / or switch from full-function mode to the first PS mode. In one example, as illustrated in FIG. 28, in a first PS mode, the wireless device may monitor a first PDCCH for at least one DCI having one or more first DCI formats in one or more first search spaces of one or more first control resource sets (e.g., SS1 / CORESET1 as shown in FIG. 28). In the first PS mode, the wireless device may monitor a PS signal according to one or more first PS signal parameters. In the first PS mode, the wireless device may not monitor a PDCCH in one or more second search spaces of one or more second control resource sets. In the first PS mode, the wireless device may not monitor a PDCCH in one or more third search spaces of one or more third control resource sets.

[0251] Likewise, as illustrated in FIG. 28, a base station may transmit a second DCI (e.g., the second DCI in FIG. 28) to a wireless device indicating the enabling (or activation) of a second PS mode (PS mode 2 as illustrated in FIG. 28). In response to receiving the second DCI, the wireless device may enable (or activate) the second PS mode and / or switch from the first PS mode to the second PS mode. In one example, as illustrated in FIG. 28, in the second PS mode, the wireless device may monitor a second PDCCH for at least one DCI having one or more second DCI formats in one or more second search spaces of one or more second control resource sets (e.g., SS1 / CORESET1, SS2 / CORESET2 as illustrated in FIG. 28). In the second PS mode, the wireless device may monitor the PS signal according to one or more second PS signal parameters. In the second PS mode, the wireless device may not monitor a PDCCH on one or more first search spaces of one or more first control resource sets. In the second PS mode, the wireless device may not monitor a PDCCH on one or more third search spaces of one or more third control resource sets.

[0252] Likewise, as illustrated in FIG. 28, the base station may transmit a third DCI (e.g., the third DCI in FIG. 28) to the wireless device indicating the enabling (or activation) of the full function mode. In response to receiving the third DCI, the wireless device may disable (or deactivate) the first PS mode and the second PS mode. In one example, as illustrated in FIG. 28, in the full function mode, the wireless device may monitor a third PDCCH for at least one DCI having one or more third DCI formats in one or more third search spaces of one or more third control resource sets (e.g., SS1 / CORESET1, SS2 / CORESET2, ..., SSn / CORESETn as shown in FIG. 28). In the full function mode, the wireless device may not monitor a PDCCH in one or more first search spaces of one or more first control resource sets. In full function mode, the wireless device may not monitor PDCCHs on one or more second search spaces of one or more second control resource sets.

[0253] FIG. 29 illustrates an exemplary embodiment of a power saving mechanism when, for example, a DRX is configured. A base station (e.g., gNB in ​​FIG. 29) may transmit one or more RRC messages containing first configuration parameters of a plurality of DRX configurations to a wireless device (e.g., UE in FIG. 29). In one example, the first configuration parameters of a first DRX configuration (e.g., a first DRX configuration as illustrated in FIG. 29) may represent the following: one or more first search spaces (e.g., a first SS as illustrated in FIG. 29) and / or one or more first control resource sets (e.g., a first CORESET as illustrated in FIG. 29); one or more first RNTIs of PDCCH candidate monitoring (e.g., a first RNTI as illustrated in FIG. 29); one or more first DCI formats (e.g., a first DCI format as illustrated in FIG. 29); one or more first DRX timers; and / or one or more first PS signal parameters. In one example, the first configuration parameter of the second DRX configuration (e.g., the second DRX configuration as illustrated in FIG. 29) may represent the following: one or more second search spaces (e.g., the second SS as illustrated in FIG. 29) and / or one or more second control resource sets (e.g., the second CORESET as illustrated in FIG. 29); one or more second RNTIs of PDCCH candidate monitoring (e.g., the second RNTI as illustrated in FIG. 29); one or more second DCI formats (e.g., the second DCI format as illustrated in FIG. 29); one or more second DRX timers; and / or one or more second PS signal parameters.

[0254] In one example, one or more RRC messages may further include second configuration parameters representing one or more third search spaces (third SS as shown in FIG. 29) and one or more third control resource sets (third CORESET as shown in FIG. 29); one or more third DCI formats (third DCI as shown in FIG. 29); and one or more third RNTIs of PDCCH candidate monitoring (e.g., third RNTI as shown in FIG. 29).

[0255] As illustrated in FIG. 29, a wireless device may communicate with a base station in full-function mode. The base station may transmit to the wireless device a first DCI (e.g., the first DCI in FIG. 29) indicating the enabling of a first DRX configuration (e.g., the first DRX configuration as illustrated in FIG. 29). In response to receiving the first DCI, the wireless device may enable (or activate) the first DRX configuration. In one example, as illustrated in FIG. 29, in the first DRX configuration state, the wireless device may monitor a first PDCCH for at least one DCI having one or more first DCI formats based on one or more first RNTIs, based on one or more parameters of the first DRX configuration, in one or more first search spaces of one or more first control resource sets. Likewise, as illustrated in FIG. 29, a base station may transmit a second DCI (e.g., the second DCI in FIG. 29) to a wireless device indicating the enabling of a second DRX configuration (the second DRX configuration as illustrated in FIG. 29). The wireless device may enable (or activate) the second DRX configuration in response to receiving the second DCI. In one example, as illustrated in FIG. 29, in the second DRX configuration state, the wireless device may monitor a second PDCCH for at least one DCI having one or more second DCI formats based on one or more second RNTIs in one or more second search spaces of one or more second control resource sets based on one or more parameters of the second DRX configuration.

[0256] Likewise, as illustrated in FIG. 29, the base station may transmit a third DCI (e.g., the third DCI in FIG. 29) to the wireless device indicating the enabling (or activation) of the full function mode. In response to receiving the third DCI, the wireless device may disable (or deactivate) the first DRX configuration and the second DRX configuration. In one example, as illustrated in FIG. 29, in the full function mode, the wireless device may monitor a third PDCCH for at least one DCI having one or more third DCI formats based on one or more RNTIs in one or more third search spaces of one or more third control resource sets.

[0257] In one example, as illustrated in FIG. 28 and / or FIG. 29, the search space, control resource set, RNTI, and / or DCI format that a wireless device can use to monitor a PDCCH in sleep mode may be different (or configured independently / separately) from the search space, control resource set, RNTI, and / or DCI format that a wireless device can use to monitor a PDCCH in full-function mode (or non-sleep mode). In one example, as illustrated in FIG. 28 and / or FIG. 29, the first number of search spaces, control resource sets, RNTI, and / or DCI format that a wireless device can use to monitor a PDCCH in sleep mode may be fewer than the second number of search spaces, control resource sets, RNTI, and / or DCI format that a wireless device can use to monitor a PDCCH in full-function mode (or non-sleep mode). By this embodiment, the base station and / or wireless device can appropriately control power consumption depending on whether the wireless device is operating in power-saving mode or in full-function mode.

[0258] In one example, a base station may transmit one or more RRC messages including one or more channel state information (CSI) configuration parameters, including at least one CSI-RS resource setting; one or more CSI reporting setting; and one CSI measurement setting.

[0259] In one example, a CSI-RS resource configuration may include one or more CSI-RS resource sets. In one example, there may be one CSI-RS resource set for periodic CSI-RS or semi-persistent (SP) CSI-RS. In one example, a CSI-RS resource set may include at least one of the following: one CSI-RS type (e.g., periodic, non-periodic, or semi-persistent); a CSI-RS resource configuration identity (or index), the number of CSI-RS ports, a CSI-RS configuration (symbol and RE position in a subframe), a CSI-RS subframe configuration (subframe position in a radio frame, offset, and / or periodicity), a CSI-RS power parameter; one or more CSI-RS resources including at least one of CSI-RS sequence parameter; a CDM type parameter; frequency density; a transmission comb; and / or QCL parameter.

[0260] In one example, one or more CSI-RS resources may be transmitted periodically using non-periodic transmission, multishot transmission, and / or SP transmission. In periodic transmission, the configured CSI-RS resources may be transmitted using configured periodicity in the time domain. In non-periodic transmission, the configured CSI-RS resources may be transmitted in a dedicated time slot or subframe. In multishot or semi-continuous transmission, the configured CSI-RS resources may be transmitted within a configured period. In one example, the gNB may transmit one or more SP CSI-RS while maintaining a specified periodicity. The gNB may stop the transmission of one or more SP CSI-RS when a transmission duration is configured for the CSI-RS. The gNB may stop the transmission of one or more SP CSI-RS in response to transmitting a MAC CE or DCI to disable (or stop transmission of) one or more SP CSI-RS.

[0261] In one example, a CSI report configuration may include at least one of the following: one report configuration identifier; one report type; one or more reported CSI parameter(s); one or more CSI types (e.g., Type I or Type II); one or more codebook configuration parameters; one or more parameters indicating time domain behavior; frequency granularity for CQI and PMI; and / or measurement limit configuration. The report type may indicate the time domain behavior of the report (non-periodical, SP, or periodic). A CSI report configuration may further include at least one of the following: one periodicity parameter; one duration parameter; and / or one offset (e.g., in slots) if the report type is a periodic or SP report. The periodicity parameter may indicate the periodicity of the CSI report. The duration parameter may indicate the duration of the CSI report transmission. The offset parameter may indicate the timing offset value of the CSI report.

[0262] In one example, a CSI measurement setting may include one or more links, each containing one or more link parameters. The link parameters may include at least one of a CSI reporting setting indicator, a CSI-RS resource setting indicator, and one or more measurement parameters.

[0263] FIG. 30 illustrates examples of various CSI reporting trigger mechanisms. In one example, a gNB may trigger a CSI report by transmitting an RRC message, or a MAC CE, or a DCI, as illustrated in FIG. 30. In one example, a UE may perform a periodic CSI report (e.g., P-CSI report in FIG. 30) based on an RRC message and one or more periodic CSI-RSs. In one example, a UE may not be permitted (or required) to perform a periodic CSI report based on one or more non-periodic CSI-RSs and / or one or more SP CSI-RSs. In one example, a UE may perform an SP CSI report (e.g., SP-CSI report in FIG. 30) based on a MAC CE and / or DCI and based on one or more periodic or SP CSI-RSs. In one example, a UE may not be permitted (or required) to perform an SP CSI report based on one or more non-periodic CSI-RSs. In one example, the UE may perform aperiodic CSI reporting (e.g., AP-CSI reporting in FIG. 30) based on DCI and one or more periodic or SP or aperiodic CSI-RS. In one example, the wireless device may perform SP CSI reporting on the PUCCH in response to SP CSI reporting being enabled (or triggered) by MAC CE. The wireless device may perform SP CSI reporting on the PUSCH in response to SP CSI reporting being enabled (or triggered). In one example, the base station may instruct the wireless device to perform SP CSI reporting on the PUCCH (e.g., by transmitting MAC CE) when compact CSI (e.g., small amount of reporting content) is required by the base station, or when DCI transmission is not convenient for the base station, and / or when CSI is not urgently required by the base station.In one example, the base station may instruct the radio device to perform SP CSI reporting in PUSCH (e.g., by transmitting DCI) when a large CSI (e.g., a large amount of report content) is required by the base station, or when DCI transmission is not convenient for the base station, and / or when CSI is not urgently required by the base station.

[0264] FIG. 31 illustrates an example of SP CSI reporting in a given cell. In one example, a base station (e.g., gNB in ​​FIG. 31) may transmit one or more RRC messages containing configuration parameters of one or more SP CSI reporting configurations to a wireless device (e.g., UE in FIG. 31). The base station n In the nth slot (or subframe), a first MAC CE or DCI indicating the activation of one or more SP CSI reporting configurations can be transmitted to a wireless device. The base station n + k One or more SP CSI-RS transmissions can be initiated in the nth slot (or subframe). In one example, k can be 0 or an integer greater than 0, can be configured by an RRC message, or can be predefined as a fixed value.

[0265] As illustrated in FIG. 31, the wireless device may perform CSI measurements for one or more CSI-RS according to an activated SP CSI reporting configuration after receiving or in response to a first MAC CE or a first DCI. In one example, the wireless device, after receiving or in response to a first MAC CE or a first DCI, n + k + m first, n + k + m + l first, n + k + m+ 2 * l In the slot / subframe of the th, etc. l One or more SP CSI reports may be transmitted while maintaining periodicity of several subframes (or slots) (e.g., based on CSI measurements). Such periodicity may be set within an RRC message. In one example, the UE may receive a second MAC / DCI indicating the deactivation of the SP CSI report configuration. The UE may stop transmitting one or more SP CSI reports after receiving the second MAC / DCI or in response to the second MAC / DCI. In one example, k can be 0 (can consist of 0 or be predefined). In one example, m (for example, k (where =0) may be a time offset between when the wireless device receives the first MAC CE / DCI for activating the SP CSI report and when the wireless device transmits the first SP CSI report of one or more SP CSI reports. In one example, m It can be configured by an RRC message or predefined as a fixed value. m The value of may vary depending on the capabilities of the UE and / or network.

[0266] As illustrated in FIG. 31, a wireless device can estimate a CSI-RS transmission period (e.g., a CSI-RS transmission window in FIG. 30) in response to a first MAC CE / DCI for activating an SP CSI reporting configuration and based on one or more configuration parameters of the activated SP CSI reporting configuration. The base station can transmit one or more CSI-RS in at least one CSI-RS transmission period based on the activated SP CSI reporting configuration. In one example, the wireless device can perform CSI measurements for one or more CSI-RS transmitted in the CSI-RS transmission period.

[0267] FIG. 32 illustrates an exemplary embodiment of the SP CSI reporting mechanism when SP CSI reporting is triggered by MAC CE. In one example, a base station (e.g., gNB in ​​FIG. 32) may transmit one or more RRC messages to a radio device (e.g., UE in FIG. 32) containing one or more BWP configuration parameters of one or more BWPs of a given cell. One or more RRC messages may further indicate the BWP timer value of a BWP inactive timer. One or more BWPs may include a default BWP. The cell may be a PCell or a SCell. One or more BWP configuration parameters of one of the one or more BWPs may include at least one of the following: a BWP index; one or more RS (e.g., SSB / CSI-RS) resource settings; one or more CSI reporting settings; and one CSI measurement setting.

[0268] In one example, the first BWP (e.g., BWP 1 in FIG. 32) may be an active BWP with which the gNB can communicate with the UE. The first BWP may be either a DL BWP or a UL BWP. In one example, as illustrated in FIG. 32, the UE may receive a MAC CE indicating the activation of SP CSI reported on the PUCCH. After or in response to the MAC CE, the UE may transmit one or more SP CSI reports through the PUCCH resources of the active UL BWP (e.g., the first BWP if the first BWP is a UL BWP), according to the SP CSI reporting configuration indicated by the MAC CE. The UE may transmit one or more SP CSI reports through the PUCCH resources of the active UL BWP at a predetermined reporting cycle. One or more SP CSI reports may be measured based on one or more RS (e.g., SSB / CSI-RS) on the active DL BWP. In one example, the UE may transmit one or more SP CSI reports for the first BWP when the first BWP is a DL BWP, after or in response to MAC CE. The UE may start (or restart) the BWP inactive timer after or in response to receiving a downlink assignment or uplink acknowledgment through the DL BWP.

[0269] In one example, as illustrated in FIG. 32, a base station may transmit a first DCI to a UE indicating an active BWP switching from a first BWP (e.g., BWP 1 in FIG. 32) to a second BWP (e.g., BWP 2 in FIG. 32). The UE may suspend the transmission of an SP CSI report after or in response to the first DCI. The UE may suspend the transmission of an SP CSI report after or in response to the expiration of a BWP inactivity timer. In one example, the UE may resume the transmission of an SP CSI report after receiving a second DCI indicating an active BWP switching from the second BWP to the first BWP, or in response to the same. In one example, the UE may stop the transmission of an SP CSI report after or in response to the expiration of a BWP inactivity timer.

[0270] FIG. 33 illustrates an exemplary embodiment of an SP CSI reporting mechanism when SP CSI reporting is triggered by a DCI. In one example, a base station (e.g., gNB in ​​FIG. 33) may transmit one or more RRC messages to a radio device (e.g., UE in FIG. 33) containing one or more BWP configuration parameters of one or more BWPs of a given cell. One or more RRC messages may further indicate the BWP timer value of a BWP inactive timer. One or more BWPs may include a default BWP. The cell may be a PCell or a SCell. One or more BWP configuration parameters of one of the one or more BWPs may include at least one of the following: a BWP index; one or more RS (e.g., SSB / CSI-RS) resource settings; one or more CSI reporting settings; and one CSI measurement setting.

[0271] In one example, the first BWP (e.g., BWP 1 in FIG. 33) may be an active BWP with which the gNB can communicate with the UE. The first BWP may be a DL BWP or a UL BWP. In one example, as illustrated in FIG. 33, the UE may receive a DCI indicating the activation of SP CSI reported on the PUSCH. After or in response to the DCI, the UE may transmit one or more SP CSI reports through the PUSCH resources of the active UL BWP (e.g., the first BWP if the first BWP is a UL BWP), according to the SP CSI reporting configuration indicated by the DCI. The UE may transmit one or more SP CSI reports through the PUSCH resources of the active UL BWP at a predetermined reporting cycle. One or more SP CSI reports may be measured based on one or more RSs (e.g., SSB / CSI-RS) on the DL BWP. The UE may start (or restart) the BWP inactive timer after receiving a downlink assignment or uplink acknowledgment through the DL BWP or in response thereto.

[0272] In one example, as illustrated in FIG. 33, a base station may transmit a first DCI to a UE indicating an active BWP switching from a first BWP (e.g., BWP 1 in FIG. 33) to a second BWP (e.g., BWP 2 in FIG. 33). The second BWP may be a DL BWP or a UL BWP. In one example, the UE may suspend the transmission of an SP CSI report for the first BWP after or in response to the first DCI (e.g., when the first DCI indicates an active UL BWP switching). In one example, the UE may suspend the transmission of an SP CSI report from the first BWP after or in response to the expiration of a BWP inactivity timer. In one example, the UE may suspend the transmission of an SP CSI report for the first BWP after or in response to the first DCI (e.g., when the first DCI indicates an active DL BWP switching). In one example, the UE may suspend the transmission of the SP CSI report for the first BWP after the expiration of the BWP inactive timer or in response to such expiration.

[0273] In one example, the UE may receive a second DCI indicating an active BWP switching from the second BWP to the first BWP. In one example, the UE may resume the transmission of the SP CSI report after receiving the second DCI or in response thereto. In one example, the UE may resume the transmission of the SP CSI report after receiving the second DCI and the third DCI indicating the activation of the SP CSI report or in response thereto. In one example, the second DCI and the third DCI may be transmitted in a DCI format comprising a first field(s) indicating an active BWP switching from the second BWP to the first BWP and a second field(s) indicating the reactivation of the SP CSI report. In one example, the second DCI and the third DCI may be transmitted in two formats, namely, a first DCI format including fields indicating active BWP switching from the second BWP to the first BWP, and a second DCI format including field(s) indicating (re)activation of the SP CSI report.

[0274] In the prior art, a wireless device may transmit one or more SP CSI reports for an SP CSI reporting configuration on the PUCCH of the first BWP in response to the SP CSI reporting configuration being activated by a MAC CE and the first BWP being active. The wireless device may suspend the transmission of one or more SP CSI reports in response to switching from the first BWP to a second BWP as the active BWP. In one example, the wireless device may resume the transmission of one or more SP CSI reports before receiving a MAC CE that disables the SP CSI reporting configuration in response to switching the first BWP as the active BWP.

[0275] In the prior art, a wireless device may transmit one or more SP CSI reports for an SP CSI reporting configuration on the PUSCH of the first BWP in response to the SP CSI reporting configuration being enabled by a DCI and the first BWP being active. The wireless device may disable the SP CSI configuration in response to switching from the first BWP to a second BWP as the active BWP. The wireless device may stop transmitting one or more SP CSI reports in response to disabling the SP CSI reporting configuration. In one example, the wireless device may not resume transmitting one or more SP CSI reports before receiving a DCI that enables the SP CSI reporting configuration in response to switching the first BWP as the active BWP.

[0276] In one example, while a wireless device is transmitting one or more SP CSI reports in a first BWP (active BWP), it may receive a command instructing it to switch to a power-saving mode (e.g., by implementing the example of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29). The wireless device may switch to a power-saving mode in response to the command. After switching to a power-saving mode, the wireless device may keep the first BWP active. By implementing existing technology, the wireless device may continue to transmit one or more SP CSI reports in a power-saving mode, for example, because the first BWP is active. Transmitting CSI reports in a power-saving mode enables the base station to obtain the latest channel quality. Transmitting CSI reports in a power-saving mode can improve data transmission delay by using the latest channel quality when the wireless device switches back to a non-power-saving mode.

[0277] In one example, the power saving mode when the wireless device transmits a CSI report may be similar to or equivalent to the sleep state of a certain cell as exemplified above in this specification. The power saving mode may include a period during which the wireless device performs at least one of not monitoring a downlink control channel for the certain cell, not receiving downlink data, not transmitting uplink data, and transmitting a CSI report for the certain cell. The sleep state of the cell may include a period during which the wireless device performs at least one of not monitoring a downlink control channel for the cell, not receiving downlink data from the cell, not transmitting uplink data from the cell, and transmitting a CSI report for the cell. In one example, in this specification, the power saving mode may be referred to as a power saving state, a sleep state of a cell, a sleep state of a cell, etc.

[0278] In one example, a wireless device may transmit CSI reports in sleep mode. The wireless device may transmit one or more SP CSI reports enabled in full-function mode while in sleep mode. Transmission may increase the power consumption of the wireless device and / or uplink interference to other wireless devices. In one example, the wireless device may disable the SP CSI report configuration for one or more SP CSI reports in sleep mode. After disabling the SP CSI report configuration, the wireless device may receive a second command instructing it to switch from sleep mode to full-function mode. According to the prior art, the wireless device may have difficulty determining whether to automatically resume the transmission of one or more SP CSI reports or wait for another SP CSI report enable command. The prior art may result in misalignment between the base station and the wireless device regarding SP CSI reports after the wireless device switches from sleep mode to full-function mode. Misalignment between the base station and the wireless device may cause uplink interference to other wireless devices, delays in uplink transmission, increase the power consumption of the wireless device and / or decrease uplink spectrum efficiency. There is a need to improve the existing SP CSI reporting mechanism in power saving mode. An exemplary embodiment can reduce uplink interference to other wireless devices, delay in uplink transmission, and power consumption of wireless devices, or increase uplink spectrum efficiency by improving the existing SP CSI reporting mechanism.

[0279] In one example, a wireless device may transmit a CSI report for a cell when the cell is in a sleep state. The wireless device may transmit one or more SP CSI reports that are enabled in the active state for the cell in the sleep state. Transmission may increase the power consumption of the wireless device and / or uplink interference to other wireless devices. In one example, the wireless device may disable the SP CSI report configuration for one or more SP CSI reports for the cell in response to the cell being in a sleep state. After disabling the SP CSI report configuration, the wireless device may receive a second command instructing a switch from the sleep state to the active state. According to the prior art, the wireless device may have difficulty determining whether to automatically resume the transmission of one or more SP CSI reports or to wait for another SP CSI report enable command. The prior art may result in misalignment between the base station and the wireless device regarding SP CSI reports after the wireless device switches the cell from the sleep state to the active mode. Misalignment between a base station and a wireless device can cause uplink interference to other wireless devices, delays in uplink transmission, and increase / and / or increase power consumption of the wireless device, or decrease uplink spectrum efficiency. There is a need to improve the existing SP CSI reporting mechanism in the sleep state. An exemplary embodiment can reduce uplink interference to other wireless devices, delays in uplink transmission, and power consumption of the wireless device, or increase uplink spectrum efficiency by improving the existing SP CSI reporting mechanism.

[0280] FIG. 34 illustrates an exemplary embodiment of an improved SP CSI reporting mechanism in power saving (PS) mode (or a cell in a sleep state). In one example, a base station (e.g., gNB in ​​FIG. 34) may transmit one or more RRC messages to a radio device (e.g., UE in FIG. 34) comprising first configuration parameters of PS mode and second configuration parameters of CSI reporting. In one example, the first configuration parameter may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be a period during which the cell is in a sleep state. In one example, the second configuration parameter may be configured by implementing one or more embodiments of FIG. 31, FIG. 32, and / or FIG. 33. In one example, a wireless device may receive a Media Access Control Element (MAC CE) that enables SP CSI reporting on a PUCCH for an SP CSI reporting configuration. In response to receiving the MAC CE, the wireless device may transmit one or more SP CSI reports on a PUCCH resource of an active BWP according to one or more parameters of the enabled SP CSI reporting configuration.

[0281] In one example, the wireless device may receive a first command to enable PS mode in the active BWP during the period in which it transmits one or more SP CSI reports on the active BWP's PUCCH resource. The first command may indicate that the cell is transitioning from an active state to a sleep state. As illustrated in FIG. 34, the wireless device may switch to PS mode or transition the cell to a sleep state in response to receiving the first command. The wireless device may maintain the active BWP (e.g., an uplink BWP) without changing it in response to switching to PS mode. In one example, the wireless device may suspend the transmission of one or more SP CSI reports for the cell in response to switching to PS mode. The wireless device may maintain the SP CSI report configuration in an active state. In one example, maintaining an SP CSI report configuration in an active state may include maintaining configuration parameters of the SP CSI report configuration, including first parameters of one or more CSI-RS resource settings, second parameters of one or more CSI report settings, and third parameters of one CSI measurement setting. In one example, the wireless device may, in PS mode, stop the transmission of one or more SP CSI reports, stop the transmission of non-periodic CSI reports, and / or continue the transmission of one or more periodic CSI reports. In one example, the wireless device may, in PS mode, stop the transmission of one or more SP CSI reports, the transmission of non-periodic CSI reports, and / or the transmission of one or more periodic CSI reports. In one example, if the PS mode includes a cell in a dormant state, the wireless device may stop transmitting one or more SP CSI reports for that cell, stop transmitting non-periodic CSI reports for that cell, and / or continue transmitting one or more periodic CSI reports for that cell.According to the present embodiment, a wireless device may suspend SP CSI reporting (e.g., enabled by an SP CSI-enabled MAC CE) and maintain the configuration parameters of SP CSI reporting in response to the cell being in a sleep state. Suspending SP CSI reporting in a sleep state can improve the power consumption of the wireless device and / or reduce interference with other wireless devices. Suspending SP CSI reporting in a sleep state allows the base station to reallocate the uplink radio resources of SP CSI reporting to other wireless devices, thereby improving uplink throughput. Maintaining the configuration parameters of SP CSI reporting in a sleep state can reduce the signaling overhead for reactivating SP CSI reporting when the cell switches from a sleep state to an active state.

[0282] In one example, as illustrated in FIG. 34, the wireless device may receive a second command to disable the PS mode in the active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to the switch to the full-function mode, the wireless device may resume the transmission of one or more SP CSI reports on the PUCCH resources of the active BWP, for example, without waiting for a new MAC CE to enable SP CSI reporting.

[0283] According to an exemplary embodiment of FIG. 34, a wireless device may suspend SP CSI reporting on the PUCCH in PS mode and resume SP CSI reporting on the PUCCH when switching from PS mode to full-function mode. The exemplary embodiment may reduce power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may reduce signaling overhead for reactivating SP CSI reporting on the PUCCH when switching from PS mode to full-function mode.

[0284] FIG. 35 illustrates an exemplary embodiment of an improved SP CSI reporting mechanism in power saving (PS) mode. In one example, a base station (e.g., gNB in ​​FIG. 35) may transmit one or more RRC messages to a wireless device (e.g., UE in FIG. 35) comprising first configuration parameters of PS mode and second configuration parameters of CSI reporting. In one example, the first configuration parameters may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the second configuration parameters may be configured by implementing one or more embodiments of FIG. 31, FIG. 32, and / or FIG. 33. In one example, a wireless device may receive downlink control information (DCI) that enables SP CSI reporting on PUSCH for an SP CSI reporting configuration. In response to receiving the DCI, the wireless device may transmit one or more SP CSI reports on the PUSCH resources of an active BWP according to one or more parameters of the enabled SP CSI reporting configuration.

[0285] In one example, the wireless device may receive a first command to enable the PS mode in the active BWP during the period in which it transmits one or more SP CSI reports over the PUSCH resource of the active BWP. As illustrated in FIG. 35, the wireless device may switch to the PS mode in response to receiving the first command. The wireless device may maintain the active BWP without changing it in response to the switch to the PS mode. In one example, the wireless device may disable the SP CSI report configuration for transmitting one or more SP CSI reports over the PUSCH resource of the active BWP in response to the switch to the PS mode. In one example, after disabling the SP CSI report configuration, the wireless device may stop transmitting one or more SP CSI reports over the PUSCH of the active BWP in the PS mode. In one example, if the PS mode includes a cell that is in a sleep state, the wireless device may stop transmitting one or more SP CSI reports to that cell in response to the disabling of the SP CSI report configuration. The wireless device may clear the configuration parameters of the SP CSI report configuration. The wireless device may not automatically resume the transmission of the SP CSI report based on the deactivation of the SP CSI report configuration. The wireless device may transmit (or resume) the SP CSI report in response to receiving another DCI indicating the activation of the SP CSI report configuration. According to the present embodiment, the wireless device may (automatically) deactivate the SP CSI report (e.g., activated by an SP CSI activation DCI) and clear the configuration parameters of the SP CSI report in response to the cell being in a sleep state. Deactivating the SP CSI report in a sleep state may improve the power consumption of the wireless device and / or reduce interference with other wireless devices.Disabling SP CSI reporting in a power-saving state allows the base station to reallocate the uplink radio resources of SP CSI reporting to other radio devices, thereby improving uplink throughput. By not automatically resuming SP CSI reporting, the base station can flexibly enable SP CSI reporting by transmitting an SP CSI enable DCI when necessary when the cell transitions from a sleep state to an active state.

[0286] In one example, as illustrated in FIG. 35, the wireless device may receive a second command to disable the PS mode in the active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to switching to the full-function mode, the wireless device may not resume the transmission of one or more SP CSI reports on the PUSCH resource of the active BWP until it receives a (re)enable command for the transmission of one or more SP CSI reports. In one example, as illustrated in FIG. 35, the wireless device may transmit one or more SP CSI reports on the PUSCH resource of the active BWP in response to receiving a second DCI that enables the SP CSI reports on the PUSCH.

[0287] According to an exemplary embodiment of FIG. 35, a wireless device may disable SP CSI reporting on PUSCH in PS mode. The wireless device may not resume SP CSI reporting on PUSCH when switching from PS mode to full-function mode until it receives an enable command for SP CSI reporting on PUSCH. The exemplary embodiment may reduce power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may allow the base station to flexibly control SP CSI reporting on PUSCH when switching the wireless device from PS mode to full-function mode.

[0288] FIG. 36 illustrates an example of an improved CSI-RS selection / decision mechanism in PS mode. In one example, a base station (e.g., gNB in ​​FIG. 36) may transmit one or more RRC messages to a wireless device (e.g., UE in FIG. 36) that include first configuration parameters of PS mode and second configuration parameters of CSI-RS. In one example, the first configuration parameters may be implemented by one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. The second configuration parameters may be implemented by one or more embodiments of FIG. 30 and / or FIG. 31. In one example, the wireless device may receive a MAC CE that activates one or more sets of CSI-RS resources from the CSI-RS on an active BWP. One or more sets of CSI-RS resources may include one or more SP CSI-RS resources, or one or more SP CSI-IM (Interference Measurement) resources. One or more sets of CSI-RS resources may include one or more SP Zero-Power (ZP) CSI-RS resources. In response to receiving a MAC CE, the radio device may assume that the base station transmits one or more sets of CSI-RS resources after receiving the MAC CE. The radio device may calculate (or measure) one or more CSI / IM based on one or more active sets of CSI-RS resources. Based on the measurement of one or more CSI / IM, the radio device may transmit one or more CSI / IM reports via the PUCCH / PUSCH resources of the active BWP.

[0289] In one example, as illustrated in FIG. 36, a wireless device may receive a first command to enable PS mode in an active BWP during the period when the wireless device measures CSI / IM based on one or more CSI-RS resource sets. The wireless device may switch to PS mode in response to receiving the first command. The wireless device may assume that when it switches to PS mode, the base station does not transmit one or more CSI-RS resource sets. The wireless device may stop measuring for one or more CSI-RS resource sets in PS mode. In one example, the wireless device may receive a second command to disable PS mode in an active BWP. The wireless device may switch from PS mode to full-function mode in response to receiving the second command. The wireless device may assume that after switching from PS mode to full-function mode in response to receiving the second command, the base station transmits one or more CSI-RS resource sets. The wireless device may resume CSI / IM measurements based on one or more CSI-RS resource sets.

[0290] According to an exemplary embodiment of FIG. 36, in PS mode, the wireless device may stop CSI / IM measurements for a set of CSI-RS resources enabled by MAC CE in full-function mode. The wireless device may resume CSI / IM measurements based on the set of CSI-RS resources when switching from PS mode to full-function mode. The exemplary embodiment may reduce the power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may reduce signaling overhead when switching from PS mode to full-function mode.

[0291] In one example, a base station may instruct a radio device to transmit one or more SRSs for channel quality estimation (e.g., CSI acquisition, or uplink beam management) to enable frequency-selective scheduling on the uplink. Transmission of SRSs may be used for other purposes, such as to enhance power control or to support various start functions for radio devices that have not been recently scheduled. Some embodiments in which SRS transmission is useful include initial Modulation and Coding Scheme (MCS) selection, initial power control for data transmission, timing advance, and frequency-semi-selective scheduling.

[0292] In one example, a base station may instruct a wireless device to transmit at least one of three types of SRS: periodic SRS transmission (Type 0); non-periodic SRS transmission (Type 1); and semi-continuous SRS transmission. In the case of periodic SRS transmission, the subframe in which the SRS may be transmitted may be indicated by cell-specific broadcast signaling and / or UE-specific signaling.

[0293] FIG. 37a illustrates an example of periodic SRS transmission. The periodicity of the periodic SRS transmission may range from a value that occurs as often as once every 2 ms to a value that does not occur as often as once every 160 ms. A wireless device may transmit SRS in SC-FDMA or OFDM symbols (e.g., the last 1 to 3 symbols of a subframe) in a configured subframe.

[0294] FIG. 37b illustrates an example of aperiodic SRS transmission. A wireless device may transmit an SRS aperiodically in response to a DCI reception indicating aperiodic SRS transmission.

[0295] FIG. 37c illustrates an embodiment of SP SRS transmission. In one example, a wireless device may receive configuration parameters of SP SRS transmission. The configuration parameters may include at least one of the periodicity of the SP SRS transmission; time / frequency radio resources; cyclic shift parameters; and / or other radio parameters (e.g., bandwidth, frequency hopping, transmission bit and offset, frequency domain position). The wireless device may transmit SP SRS in response to receiving a first MAC CE that enables SP SRS. The wireless device may periodically repeat SP SRS transmission until it receives a second MAC CE that disables SP SRS. The wireless device may disable SP SRS and stop SP SRS transmission in response to receiving a second MAC CE that disables SP SRS.

[0296] In the prior art, a wireless device may transmit one or more SP SRSs on a first BWP in response to one or more SP SRSs being activated by a MAC CE and a first BWP being active, for example, as illustrated in FIG. 37c. The wireless device may suspend the transmission of one or more SP SRSs in response to switching from the first BWP to a second BWP as an active BWP. In one example, the wireless device may resume the transmission of one or more SP SRSs before receiving a MAC CE that disables the SP SRSs in response to switching the first BWP to an active BWP. In one example, while transmitting one or more SP SRSs on the first BWP (active BWP), the wireless device may receive a command instructing a switch to a power-saving mode (e.g., by implementing the examples of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29). The wireless device may switch to a power-saving mode in response to the command. A wireless device may keep a first BWP active after switching to a power-saving mode. By implementing existing technology, the wireless device may, for example, continue to transmit one or more SP SRSs even in power-saving mode because the first BWP is active. When transmitting in power-saving mode, one or more SP SRSs enabled in full-function mode may increase the power consumption of the wireless device and / or uplink interference to other wireless devices. In one example, the wireless device may disable one or more SP SRSs in power-saving mode. After disabling one or more SP SRSs, the wireless device may receive a second command instructing it to switch from power-saving mode to full-function mode. According to existing technology, the wireless device may have difficulty determining whether to automatically resume transmission of one or more SP SRSs or to wait for another SP SRS enable command.Existing technologies can cause misalignment between the base station and the wireless device regarding SP SRS transmission after the wireless device switches from sleep mode to full-function mode. Misalignment between the base station and the wireless device can lead to uplink interference to other wireless devices, delays in uplink transmission, increased power consumption of the wireless device, and / or decreased uplink spectrum efficiency. There is a need to improve the existing SP SRS transmission mechanism in sleep mode. An exemplary embodiment can reduce uplink interference to other wireless devices, delays in uplink transmission, and power consumption of the wireless device, or increase uplink spectrum efficiency by improving the existing SP SRS transmission mechanism.

[0297] FIG. 38 illustrates an exemplary embodiment of an improved SP SRS transmission mechanism in PS mode. In one example, a base station (e.g., gNB in ​​FIG. 38) may transmit one or more RRC messages to a wireless device (e.g., UE in FIG. 38) comprising first configuration parameters of PS mode and second configuration parameters of SRS. In one example, the first configuration parameters may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the second configuration parameters may be configured by implementing one or more embodiments of FIG. 37a, FIG. 37b, and / or FIG. 37c. In one example, the wireless device may receive a MAC CE that enables SP SRS transmission. The wireless device can transmit SP SRS on the active BWP in response to receiving MAC CE.

[0298] In one example, the wireless device may receive a first command to enable PS mode on the active BWP while transmitting one or more SP SRS on the active BWP. As illustrated in FIG. 38, the wireless device may switch to PS mode in response to receiving the first command. The wireless device may maintain the active BWP without changing it in response to switching to PS mode. In one example, the wireless device may suspend SP SRS transmission on the active BWP in response to switching to PS mode. The wireless device may keep the SP SRS active. In one example, the wireless device may stop SP SRS transmission and stop the transmission of non-periodic SRS and / or continue the transmission of one or more periodic SRS in PS mode. In one example, the wireless device may stop SP SRS transmission, the transmission of non-periodic SRS, and / or the transmission of one or more periodic SRS in PS mode.

[0299] In one example, as illustrated in FIG. 38, the wireless device may receive a second command to disable the PS mode in the active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to the switch to the full-function mode, the wireless device may resume SP SRS transmission on the active BWP.

[0300] According to an exemplary embodiment of FIG. 38, a wireless device may suspend SP SRS transmission in PS mode and resume SP SRS transmission when switching from PS mode to full function mode. The exemplary embodiment may reduce power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may reduce signaling overhead for reactivating SP SRS transmission when switching from PS mode to full function mode.

[0301] In one example, a wireless device may transmit one or more uplink transmission blocks (TBs) over the cell's wireless resources based on configured acknowledgments. The configured acknowledgments may include a first type of configured acknowledgment (e.g., Type 1), a second type of configured acknowledgment (e.g., Type 2), and / or the like. When the wireless device receives RRC messages containing configuration parameters of configured acknowledgment Type 1, it may transmit one or more TBs over the cell's wireless resources based on the configuration parameters of the configured acknowledgment Type 1. The configuration parameters may include at least one of the following: frequency hopping indication, one or more DMRS configuration parameters, MCS table indication parameters, resource allocation type indication, one or more power control parameters (e.g., P0, alpha, and / or power control loop indicator), number of transmission repetitions, transmission periodicity indicator, time domain offset value, time domain resource allocation parameter, frequency domain resource allocation parameter, number of antenna ports, SRS resource indicator, etc. Based on the configuration parameters of configured acknowledgment type 1, the wireless device can periodically transmit one or more TBs through the cell's wireless resources without waiting for a transmission request (e.g., DCI or MAC CE) from a base station.

[0302] In one example, when the configured acknowledgment is a type 2 configured acknowledgment, the radio device may receive first configuration parameters of the configured acknowledgment within an RRC message and second configuration parameters of the configured acknowledgment within a DCI indicating the activation of the configured acknowledgment. In one example, when the configured acknowledgment is a type 2 configured acknowledgment, the radio device may receive an RRC message containing first configuration parameters of the configured acknowledgment type 2, wherein the first configuration parameters include at least one of a frequency hopping indicator, one or more DMRS configuration parameters, an MCS table indicator parameter, a resource allocation type indicator, one or more power control parameters (e.g., P0, alpha, and / or power control loop indicator), a number of iterations, and / or a transmission periodicity indicator. The radio device may receive a DCI indicating the activation of the configured acknowledgment (e.g., a CRC scrambled by CS-RNTI). The DCI may further indicate a second configuration parameter of the configured acknowledgment, wherein the second configuration parameter includes at least one of the following: a time domain offset value, a time domain resource allocation parameter, a frequency domain resource allocation parameter, a number for antenna ports, an SRS resource indicator, etc. In one example, the wireless device may transmit one or more TBs through the cell's wireless resources based on the first configuration parameters of the configured acknowledgment type 2 and the second configuration parameters of the configured acknowledgment type 2. In response to receiving a DCI that enables the configured acknowledgment, the wireless device may periodically transmit one or more TBs through the cell's wireless resources based on the configuration parameters of the configured acknowledgment type 2. The wireless device may stop transmission in response to receiving a second DCI indicating the deactivation of the configured acknowledgment type 2.

[0303] In one example, the wireless device may suspend the configured uplink type 1 on the cell's first BWP in response to an active BWP switching from the cell's first BWP to the second BWP. The wireless device may clear the configured uplink type 2 on the cell's first BWP in response to an active BWP switching from the cell's first BWP to the second BWP. In one example, the wireless device may deactivate the cell in response to the expiration of a SCell deactivation timer associated with the cell and / or in response to receiving a MAC CE indicating deactivation of the cell. In response to deactivation of the cell, the wireless device may clear the configured uplink type 2 and / or suspend the configured uplink type 1.

[0304] In one example, a power-saving mode based on the exemplary embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29, which includes the transmission of a CSI report, may be similar to or equivalent to a sleep state of a certain cell as exemplified above in this specification. The power-saving mode may include a period during which the wireless device performs at least one of not monitoring a downlink control channel for the certain cell, not receiving downlink data, not transmitting uplink data, and transmitting a CSI report for the certain cell. A sleep state of a cell may include a period during which the wireless device performs at least one of not monitoring a downlink control channel for the cell, not receiving downlink data from the cell, not transmitting uplink data from the cell, and transmitting a CSI report for the cell. In one example, in this specification, the power-saving mode may be referred to as a power-saving state, a sleep state of a cell, a sleep state of a cell, etc.

[0305] In one example, the wireless device may receive a DCI indicating a power saving operation via the PDCCH. The power saving operation may be based on at least one of the following: a wake-up / go-to-sleep indication (e.g., a wake-up or go-to-sleep indication as shown in FIG. 26a or FIG. 26b), a power saving enable / disable indication (e.g., FIG. 27), a PDCCH monitoring adaptation based on the DCI (e.g., FIG. 28), a dynamic DRX configured based on the DCI (e.g., FIG. 29), etc. The power saving operation may not include active downlink BWP switching or active uplink BWP switching. The power saving operation may include a sleep state for the cell. The sleep state of the cell is different from the inactive state of the cell as exemplified above in this specification. In one example, the wireless device continues to run the SCell inactive timer for the cell in the sleep state. However, the wireless device does not continue to run the SCell inactive timer for the cell in the inactive state. In one example, the wireless device transmits a CSI report for a cell in a dormant state. However, the wireless device does not transmit a CSI report for a cell in an inactive state.

[0306] In existing technology, a wireless device may receive one or more MAC CEs (e.g., FIG. 20a, FIG. 20b, FIG. 21a, FIG. 21b, and / or FIG. 21c) indicating the deactivation of a SCell or the transition of a SCell to a sleep state. The implementation of existing technology using MAC CE(s) to transition a SCell to a sleep state may result in increased signaling overhead for the base station and / or increased processing complexity for the wireless device. A wireless device processing MAC CE(s) for sleep indication may incur additional processing time and may result in increased power consumption. In some cases, since the deactivation of a SCell is not urgent, using MAC CE(s) for SCell deactivation may be sufficient. However, existing technology may fail to meet the requirements for dynamic power adaptation in the SCell by switching the SCell to a sleep state based on MAC CE(s). In one example, channel quality and / or traffic patterns may change frequently in cells deployed at high frequencies (e.g., 6 GHz, 30 GHz, etc.). Wireless devices may consume more power at high frequencies than at low frequencies for communication with base stations. Power adaptation considering frequently changing channel quality and traffic patterns may require wireless devices to process sleep indications quickly and respond immediately upon receiving them. Conventional MAC CE-based sleep indications may not enable wireless devices to rapidly adapt to power consumption in the cell. Conventional MAC CE-based sleep indications may not enable wireless devices to quickly transition the cell to a sleep state to reduce power consumption and maintain CSI reporting. Conventional MAC CE-based sleep indications may not enable wireless devices to quickly transition the cell from a sleep state to an active state to resume transmission.An exemplary embodiment implements an enhanced method for transitioning a SCell to a sleep state. By implementing the exemplary embodiment, a base station may transmit a DCI indicating that the SCell is transitioning to a sleep state. The exemplary embodiment implements an enhanced process for a configured acknowledgment type 1 when a wireless device receives a DCI indicating that the SCell is transitioning to a sleep state. The exemplary embodiment enables a rapid process for a configured acknowledgment type 1 when a DCI indicating the SCell sleep state is implemented by a base station and / or a wireless device.

[0307] In one example, when a wireless device receives a DCI indicating a power-saving operation (or SCell sleep), it may be transmitting an uplink via a configured acknowledgment (e.g., configured uplink acknowledgment type 1). In response to receiving the DCI, the wireless device may stop transmitting an uplink via the configured acknowledgment. In response to receiving the DCI, the wireless device may maintain the cell's active BWP (e.g., downlink BWP and / or uplink BWP) unchanged. In response to receiving the DCI, the wireless device may maintain the SCell's active state and continue running the SCell disable timer associated with the SCell. Based on the running SCell disable timer, the wireless device may consider the SCell to be active (or not in a disabled state). In response to receiving a DCI indicating transitioning an active cell to a sleep state, the wireless device may transition the active cell to a sleep state—which may be referred to as the active cell in a sleep state. The wireless device may transmit a CSI report for the active cell in a sleep state. A wireless device may determine that a cell is active (or not inactive) based on transmitting a CSI report regarding a cell in a sleep state. By implementing existing technology, the base station and / or the wireless device may retain radio resources of configured acceptance type 1 for the wireless device. By implementing existing technology, the wireless device and / or the base station may retain / reserve radio resources after the wireless device receives a DCI indicating a switch to a sleep state. Retaining / reserving radio resources may prevent other wireless devices from transmitting TBs through those radio resources. This may result in a reduction in spectrum efficiency and throughput in the wireless network.

[0308] In one example, the configured acknowledgment may be configured acknowledgment type 1. A base station may transmit one or more RRC messages to a radio device that include configuration parameters of configured acknowledgment type 1. The configuration parameters may include at least one of the following: frequency hopping indication, one or more DMRS configuration parameters, MCS table indication parameters, resource allocation type indication, one or more power control parameters (e.g., P0, alpha, and / or power control loop indicator), number of transmission iterations, transmission periodicity indicator, time domain offset value, time domain resource allocation parameter, frequency domain resource allocation parameter, number of antenna ports, SRS resource indicator, etc. The radio device may retain / reserve radio resources indicated by the configuration parameters of configured acknowledgment type 1 after ceasing uplink transmission based on switching to a power-saving state. The radio device and / or base station retaining / reserving radio resources may prevent other radio devices from utilizing those radio resources by implementing existing techniques. This may result in a reduction in system throughput. In some existing technologies, a wireless device may release configuration parameters of a configured acknowledgment type 1 in response to the SCell transitioning to a sleep or disabled state. This may increase the need for downlink signaling overhead to reconfigure the configured acknowledgment type 1 and increase processing delays when reactivating the configured acknowledgment type 1. In one example, a base station may reserve wireless resources for a wireless device. A wireless device unaware of whether the base station has reserved wireless resources may release configuration parameters of the configured acknowledgment type 1, and vice versa. In this case, misalignment may occur between the base station and the wireless device.Misalignment between the base station and the wireless device in relation to configured acceptance type 1 in power saving state may increase the power consumption of the wireless device, increase the signaling overhead of the base station, and / or decrease system throughput.

[0309] It is necessary to improve the signaling for switching SCell to sleep state, and to improve the configured acknowledgment processing to reduce signaling overhead during power saving operation and improve system throughput. Exemplary embodiments can improve the power consumption of the wireless device, reduce the signaling overhead of the base station, reduce uplink interference to other wireless devices, and / or improve uplink throughput.

[0310] In one example, one of the exemplary embodiments may include receiving a DCI indicating a transition to a sleep state (e.g., transition of a cell to a sleep state) and suspending a configured acknowledgment type 1 in response to the transition to a sleep state based on the DCI. Suspending a configured acknowledgment type 1 may include maintaining the configuration parameters of the configured acknowledgment type 1 indicated by one or more RRC messages that configure the configured acknowledgment type 1. Maintaining the configuration parameters of the configured acknowledgment type 1 enables the wireless device to quickly re-initialize the configured acknowledgment type 1 and / or resume uplink transmission through the configured acknowledgment type 1 when the wireless device receives another DCI indicating a transition from a sleep state to a non-sleep state (e.g., transitioning a cell from a sleep state to an active state). Maintaining the configuration parameters of the configured acknowledgment type 1 can reduce signaling overhead (e.g., RRC messages) for reconfiguring the configured acknowledgment type 1. Maintaining the configuration parameters of the configured approval type 1 and stopping transmission through the configured approval type 1 wireless resources from the wireless device allows the base station to reallocate the wireless resources to other wireless devices, thereby improving the system throughput for the wireless network.

[0311] In one example, one of the exemplary embodiments may include receiving a DCI indicating a switching from a sleep state to a non-sleep state (e.g., switching a SCell from a sleep state to an active state), (re)initializing a configured acknowledgment type 1, and automatically resuming transmission over the configured acknowledgment type 1 in response to the switching to a non-sleep state based on the DCI (e.g., switching a SCell to an active state). By automatically resuming the configured acknowledgment type 1, the wireless device may transmit uplink TBs over the configured acknowledgment type 1 when the wireless device switches from a sleep state to a non-sleep state. The exemplary embodiment may improve downlink signaling overhead for activating the configured acknowledgment type 1 in a sleep state. The exemplary embodiment may improve spectrum efficiency and throughput in a wireless network.

[0312] FIG. 39 illustrates an exemplary embodiment of a PUSCH transmission on a configured grant in PS mode. In one example, a base station (e.g., gNB in ​​FIG. 39) may transmit one or more RRC messages to a radio device (e.g., UE in FIG. 39) comprising first configuration parameters of the PS mode and second configuration parameters of a configured grant (CG). The CG may be CG type 1. In one example, the first configuration parameters may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. The PS mode may include a cell in a sleep state. In one example, the second configuration parameters of CG type 1 include a frequency hopping indicator; DMRS configuration; MCS table; resource allocation type indicator; RGB size; It may include one or more power control parameters; a number of repetitions; an RV pattern sequence; one or more time domain allocation parameters; and / or one or more frequency domain allocation parameters. In one example, a wireless device may receive a SCell enable / disable MAC CE indicating the activation of a cell (e.g., one or more embodiments of FIG. 20a and / or FIG. 20b). The wireless device may enable the cell based on the SCell enable / disable MAC CE. Based on the second configuration parameter, the wireless device may transmit an uplink transmission block (TB) via CG type 1 on the cell's active BWP when the cell is in an active state (active state, or non-idle state, or non-idle).

[0313] In one example, the wireless device may receive a first command that enables the PS mode in the active BWP (e.g., puts the cell to sleep or puts it to sleep) during the period when it transmits an uplink TB via CG type 1 on the active BWP of the active cell. The first command may be a DCI indicating a power saving mode that may be addressed to the wireless device or to a group of wireless devices including the wireless device. The first command may be a DCI indicating putting the cell to sleep. As illustrated in FIG. 39, the wireless device may switch to PS mode in response to receiving the first command. The wireless device may put the cell to sleep in response to receiving the first command. The wireless device may maintain the active BWP (e.g., the active uplink BWP) without changing it in response to switching to PS mode. In one example, the wireless device may suspend CG type 1 on the active BWP in response to switching to PS mode. In one example, suspending CG type 1 on the active BWP of a cell may include maintaining (or not releasing) second configuration parameters of CG type 1 configured by one or more RRC messages. In one example, the wireless device may stop transmission of uplink TB through CG type 1 of the active BWP. According to embodiments, by suspending the configured acknowledgment type 1 in sleep mode (or on an active cell in sleep state) and by maintaining the configuration parameters of the configured acknowledgment type 1, the wireless device may promptly re-initialize the configured acknowledgment type 1 and / or resume uplink transmission through the configured acknowledgment type 1 when it receives another DCI indicating a switching from sleep mode to non-sleep mode (e.g., switching the cell to an active state).Maintaining the configuration parameters of the configured acknowledgment type 1 can reduce the signaling overhead (e.g., RRC messages) required to reconfigure the configured acknowledgment type 1.

[0314] In one example, as illustrated in FIG. 39, the wireless device may receive a second command (e.g., DCI) that disables the PS mode in the active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to receiving the second command, the wireless device may switch the cell from a sleep state to a non-sleep state (e.g., active state). In response to switching the cell to a non-sleep state, the wireless device may re-initialize CG type 1 on the cell's active BWP. In response to switching the cell to a non-sleep state, the wireless device may resume transmission of the uplink TB through CG type 1 in the active BWP based on the re-initialization of CG type 1 in the cell's active BWP.

[0315] According to an exemplary embodiment of FIG. 39, the wireless device may suspend UL transmission on the CG (e.g., Type 1) in PS mode and resume UL transmission on the CG when switching from PS mode to full function mode. The exemplary embodiment may reduce power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may reduce signaling overhead for reconfiguring the CG when switching from PS mode to full function mode.

[0316] In existing technology, a wireless device may receive one or more MAC CEs (e.g., FIG. 20a, FIG. 20b, FIG. 21a, FIG. 21b, and / or FIG. 21c) indicating the deactivation of a SCell or the transition of a SCell to a sleep state. The implementation of existing technology using MAC CE(s) to transition a SCell to a sleep state may result in increased signaling overhead for the base station and / or increased processing complexity for the wireless device. A wireless device processing MAC CE(s) for sleep indication may incur additional processing time and may result in increased power consumption. When the deactivation of a SCell is not urgent, using MAC CE(s) for SCell deactivation may be sufficient. However, existing technology may fail to meet the requirements for dynamic power adaptation in the SCell by switching the SCell to a sleep state based on MAC CE(s). In one example, channel quality and / or traffic patterns may change frequently in cells deployed at high frequencies (e.g., 6 GHz, 30 GHz, etc.). Power adaptation considering frequently changing channel quality and traffic patterns may require wireless devices to rapidly process sleep indications and respond immediately upon receiving them. Conventional MAC CE-based sleep indications may not enable wireless devices to rapidly adapt to power consumption in the cell. Conventional MAC CE-based sleep indications may not enable wireless devices to rapidly transition the cell to a sleep state to reduce power consumption and maintain CSI reporting. Conventional MAC CE-based sleep indications may not enable wireless devices to rapidly transition the cell from a sleep state to an active state to resume transmission. An exemplary embodiment implements an enhanced method for transitioning a SCell to a sleep state.A base station may transmit a DCI indicating that the SCell is being put into sleep by implementing an exemplary embodiment. The exemplary embodiment implements an enhanced process for configured acknowledgment type 2 when a wireless device receives a DCI indicating that the SCell is being put into sleep. The exemplary embodiment enables a rapid process for configured acknowledgment type 2 when the DCI indicating the SCell sleep state is implemented by the base station and / or the wireless device.

[0317] In one example, when a wireless device receives a DCI indicating a power-saving operation (or SCell sleep), it may be transmitting an uplink via a configured acknowledgment (e.g., configured uplink acknowledgment type 2). In response to receiving the DCI, the wireless device may stop transmitting an uplink via the configured acknowledgment. In response to receiving the DCI, the wireless device may maintain the cell's active BWP (e.g., downlink BWP and / or uplink BWP) unchanged. In response to receiving the DCI, the wireless device may maintain the SCell's active state and continue running the SCell disable timer associated with the SCell. Based on the running SCell disable timer, the wireless device may consider the SCell to be active (or not in a disabled state). In response to receiving a DCI indicating transitioning an active cell to a sleep state, the wireless device may transition the active cell to a sleep state—which may be referred to as the active cell in a sleep state. The wireless device may transmit a CSI report for the active cell in a sleep state. A wireless device may determine that a cell is active (or not inactive) based on transmitting a CSI report regarding a cell in a sleep state. By implementing existing technology, the base station and / or the wireless device may retain radio resources of configured acceptance type 2 for the wireless device. By implementing existing technology, the wireless device and / or the base station may retain / reserve radio resources after the wireless device receives a DCI indicating a switch to a sleep state. Retaining / reserving radio resources may prevent other wireless devices from transmitting TBs through those radio resources. This may result in a reduction in spectrum efficiency and throughput in the wireless network.

[0318] In one example, the configured acknowledgment may be a configured acknowledgment type 2. The configured acknowledgment type 2 may be associated with a first configuration parameter indicated by an RRC message and a second configuration parameter indicated by a configured acknowledgment enable DCI. The first configuration parameter includes at least one of a frequency hopping indicator, one or more DMRS configuration parameters, an MCS table indicator parameter, a resource allocation type indicator, one or more power control parameters (e.g., P0, alpha, and / or power control loop indicator), a number of iterations, and / or a transmission periodicity indicator. The second configuration parameter may include at least one of a time domain offset value, a time domain resource allocation parameter, a frequency domain resource allocation parameter, a number for antenna ports, an SRS resource indicator, etc. After stopping uplink transmission based on switching to a power-saving state, the wireless device may retain / reserve the wireless resources indicated by the first configuration parameters (e.g., in an RRC message) and / or the second configuration parameters of the configured acknowledgment type 2 (e.g., in a DCI). Wireless devices and / or base stations that retain / reserve wireless resources may prevent other wireless devices from utilizing those wireless resources by implementing existing technology. This may result in a reduction in system throughput. In some existing technology, a wireless device may release a first configuration parameter of a configured admit type 2 in response to the SCell transitioning to a sleep or disabled state. This may increase the need for downlink signaling overhead to reconfigure the configured admit type 2 and increase processing delays upon reactivating the configured admit type 2. In one example, a base station may reserve wireless resources for a wireless device. A wireless device that does not know whether the base station has reserved wireless resources may release the configuration parameters of the configured admit type 2, and vice versa.In this case, misalignment between the base station and the wireless device may occur. Misalignment between the base station and the wireless device in relation to configured acknowledgment type 2 in power-saving state may increase the power consumption of the wireless device, increase the signaling overhead of the base station, and / or decrease system throughput.

[0319] It is necessary to improve the signaling for switching SCell to sleep state, and to improve the configured acknowledgment processing to reduce signaling overhead during power saving operation and improve system throughput. Exemplary embodiments can improve the power consumption of the wireless device, reduce the signaling overhead of the base station, reduce uplink interference to other wireless devices, and / or improve uplink throughput.

[0320] In one example, one of the exemplary embodiments may include receiving a DCI indicating a transition to a power-saving state (e.g., switching a cell to a sleep state); and in response to the transition to a power-saving state based on the DCI (e.g., switching a cell to a sleep state), maintaining first configuration parameters of the configured acknowledgment type 2 and clearing second configuration parameters of the configured acknowledgment type 2. The first configuration parameters may be indicated in one or more RRC messages configuring the configured acknowledgment type 2. The second configuration parameters may be indicated in the configured acknowledgment-enabled DCI. Clearing the second configuration parameters of the configured acknowledgment type 2 in a power-saving state may improve uplink throughput, for example, by enabling the base station to reallocate uplink radio resources of the configured acknowledgment type 2 to other radio devices. In a power-saving state, maintaining the first configuration parameters of the configured acknowledgment type 2 can improve downlink signaling overhead by, for example, preventing one or more RRC messages from the base station from being transmitted to reconfigure the first configuration parameters of the configured acknowledgment type 2. Maintaining the first configuration parameters and erasing the second configuration parameters can enable the base station and the wireless device to achieve a trade-off between downlink signaling overhead and uplink throughput.

[0321] In one example, one of the exemplary embodiments may include receiving a DCI indicating a switching from a power-saving state to a non-power-saving state (e.g., switching a cell from a sleep state to an active or non-sleep state); and automatically resuming transmission via a configured acknowledgment type 2 in response to the switching to a non-power-saving state based on the DCI (e.g., switching a cell to a non-sleep state). The wireless device may not automatically resume the configured acknowledgment type 2, thereby enabling the configured acknowledgment type 2 in response to receiving another DCI indicating the activation of the configured acknowledgment type 2 when the wireless device switches from a power-saving state to a non-power-saving state. An exemplary embodiment may not enable the wireless device to automatically resume the configured acknowledgment type 2 for power saving and / or interference reduction. An exemplary embodiment may enable a base station to conveniently activate the configured acknowledgment type 2 by transmitting a DCI indicating the activation of the configured acknowledgment type 2. DCI transmission can be convenient for activating configured acknowledgment type 2 compared to one or more RRC message transmissions.

[0322] FIG. 40 illustrates an exemplary embodiment of a PUSCH transmission on an acknowledgment configured in PS mode. In one example, a base station (e.g., gNB in ​​FIG. 40) may transmit one or more RRC messages to a radio device (e.g., UE in FIG. 40) comprising first configuration parameters of the PS mode and second configuration parameters of the configured acknowledgment (CG). The CG may be CG type 2. In one example, the first configuration parameters may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the second configuration parameters of CG type 2 include a frequency hopping indicator; DM-RS configuration; MCS table; resource allocation type indicator; RBG size; one or more power control parameters; and the number of repetitions. It may include an and / or RV pattern sequence. In one example, the wireless device may receive a SCell enable / disable MAC CE indicating the activation of the cell (e.g., one or more embodiments of FIG. 20a and / or FIG. 20b). The wireless device may activate the cell based on the SCell enable / disable MAC CE. In one example, the wireless device may receive a first DCI that enables CG Type 2 on an active BWP. The first DCI may be addressed as an RNTI dedicated to uplink transmission via configured acknowledgment (e.g., CS-RNTI). The first DCI may further include third configuration parameters of CG Type 2, comprising at least one of one or more time domain radio resource allocation parameters; one or more frequency domain radio resource allocation parameters; and / or one or more MIMO parameters.A wireless device can transmit an uplink TB via CG type 2 on an active BWP of a cell based on the second configuration parameters and the third configuration parameters of CG type 2.

[0323] In one example, a wireless device may receive a first command to enable PS mode on the active BWP of a cell during the period of transmitting an uplink TB via CG type 2 on the active BWP of a given cell. The first command may be a DCI indicating a power saving mode that may be addressed to the wireless device or to a group of wireless devices including the wireless device. The first command may be a DCI indicating switching the cell to a sleep state. As illustrated in FIG. 40, the wireless device may switch to PS mode in response to receiving the first command. The wireless device may switch the cell to a sleep state in response to receiving the first command. The wireless device may maintain the active BWP without changing it in response to switching to PS mode. In one example, the wireless device may clear CG type 2 on the active BWP (e.g., one or more configuration parameters of CG type 2) in response to switching to PS mode. In one example, the wireless device may stop the transmission of an uplink TB through the CG of an active BWP. Clearing CG type 2 may include clearing third configuration parameters of CG type 2 indicated by the DCI for the activation of CG type 2. Clearing CG type 2 may include retaining (or not releasing) second configuration parameters of CG type 2 indicated by one or more RRC messages.

[0324] In one example, as illustrated in FIG. 40, the wireless device may receive a second command (e.g., DCI) that disables the PS mode in the active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to switching to the full-function mode, the wireless device may not automatically resume transmission of the uplink TB through the CG on the active BWP until it receives a second DCI that enables the CG on the active BWP.

[0325] According to an exemplary embodiment of FIG. 40, the wireless device can clear the CG (e.g., Type 2) in PS mode and resume UL transmission over the CG when switching from PS mode to full function mode. The exemplary embodiment can reduce power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment can enable flexible control of uplink transmission through the CG when the base station switches from PS mode to full function mode.

[0326] In one example, one or more embodiments of FIG. 34 may be applied to improve PDCCH beam determination in PS mode. FIG. 41 illustrates an exemplary embodiment of improved PDCCH beam determination in PS mode. In one example, a base station (e.g., gNB in ​​FIG. 41) may transmit one or more RRC messages to a radio device (e.g., UE in FIG. 41) including first configuration parameters of PS mode and second configuration parameters of a transmission configuration indicator (TCI). In one example, the first configuration parameters may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the second configuration parameters of the TCI state may include one or more QCL parameters of one or more QCL types for each TCI state. Each TCI state can be identified by a TCI ID. One or more QCL types may include QCL type 1 and QCL type 2. One or more QCL parameters of a QCL type may include a cell ID; a BWP ID; a CSI-RS resource index or an SSB index; and / or a QCL type indicator representing one of type A, type B, type C, and type D.

[0327] In one example, a wireless device may receive a MAC CE from TCI states that activates a TCI state. In response to receiving the MAC CE, the wireless device may monitor the PDCCH according to the activated TCI state. In one example, the wireless device may attempt to decode the DCI on the PDCCH based on the assumption that the DM-RS antenna port for receiving the PDCCH is QCLed to the CSI-RS or SSB indicated in the TCI state.

[0328] In one example, as illustrated in FIG. 41, the wireless device may receive a first command to enable PS mode on the active BWP during the period when the wireless device monitors the PDCCH according to the active TCI state on the active BWP. As illustrated in FIG. 41, the wireless device may switch to PS mode in response to receiving the first command. The wireless device may maintain the active BWP without changing it in response to the switch to PS mode. In one example, the wireless device may stop monitoring the PDCCH according to the active TCI state on the active BWP in response to the switch to PS mode. In one example, the wireless device may stop monitoring the PDCCH according to a new TCI state on the active BWP (e.g., a state different from the TCI state enabled by MAC CE) in response to the switch to PS mode. In one example, the wireless device may receive a higher-level message (e.g., MIB One or more configuration parameters within ) (e.g., pdcch-ConfigSIB1 A new TCI state identical to the TCI state for PDCCH reception can be determined in the CORESET configured by ). In one example, the UE determines a new TCI state so that the radio device can assume that the DM-RS antenna port associated with PDCCH reception in PS mode is QCLed to the most recent of the SS / PBCH that blocks the radio device identified during the initial access procedure or the SS / PBCH that blocks the radio device identified during the non-contention random access procedure. In one example, the radio device can determine the new TCI state as a TCI state exclusively configured by an RRC message to monitor PDCCH in PS mode.

[0329] In one example, as illustrated in FIG. 41, the wireless device may receive a second command to disable the PS mode in the active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to the switch to the full-function mode, the wireless device may resume PDCCH monitoring according to the activated TCI state on the active BWP, for example, before receiving a new MAC CE to activate a new TCI state.

[0330] According to an exemplary embodiment of FIG. 41, in PS mode, the wireless device may stop monitoring the PDCCH in which the TCI state is enabled in full-function mode, and may resume monitoring the PDCCH in which the TCI state is enabled when switched from PS mode to full-function mode. The exemplary embodiment may reduce the power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may improve PDCCH monitoring and / or reduce the signaling overhead for reactivating the TCI state for PDCCH monitoring when switched from PS mode to full-function mode.

[0331] Similarly, the exemplary embodiment of FIG. 34 can be applied to improve PUCCH beam determination in PS mode. FIG. 42 illustrates an exemplary embodiment of improved PUCCH beam determination in PS mode. In one example, a base station (e.g., gNB in ​​FIG. 42) may transmit one or more RRC messages to a wireless device (e.g., UE in FIG. 42) comprising first configuration parameters of PS mode and second parameters of PUCCH spatial relationship information configuration. In one example, the first configuration parameters may be configured by implementing one or more embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, the PS mode may be implemented by embodiments of FIG. 26a, FIG. 26b, FIG. 27, FIG. 28, and / or FIG. 29. In one example, each PUCCH spatial relationship information configuration of the PUCCH spatial relationship information configurations may be identified by a PUCCH spatial relationship information configuration ID. The second configuration parameter of each PUCCH spatial relationship information configuration may include a cell ID; one of the CSI-RS resource index, SSB index, and SRS resource index; and / or one or more power control parameters.

[0332] In one example, a wireless device may receive a MAC CE that activates a first PUCCH spatial relationship information configuration from PUCCH spatial relationship information configurations. Based on the MAC CE, the wireless device may transmit one or more uplink control information (e.g., HARQ ACK / NACK, SR, and / or CSI report) over the PUCCH according to the activated first PUCCH spatial relationship information configuration. In one example, the wireless device may transmit one or more uplink control information over the PUCCH using the same spatial domain filter used for receiving an SSB identified by an SSB index within the activated first PUCCH spatial relationship information configuration. In one example, the wireless device may transmit one or more uplink control information over the PUCCH using the same spatial domain filter used for receiving a CSI-RS identified by a CSI-RS resource index within the activated first PUCCH spatial relationship information configuration. In one example, the wireless device may transmit one or more uplink control information through the PUCCH using the same spatial domain filter for transmitting the SRS identified by the SRS resource index within the activated first PUCCH spatial relationship information configuration.

[0333] In one example, as illustrated in FIG. 42, a wireless device may receive a first command to enable PS mode in an active BWP during the period in which the wireless device transmits a PUCCH according to the first PUCCH spatial relationship information configuration in which the wireless device is active. As illustrated in FIG. 42, the wireless device may switch to PS mode in response to receiving the first command. In response to switching to PS mode, the wireless device may maintain the active BWP without changing it. In one example, in response to switching to PS mode, the wireless device may stop transmitting a PUCCH according to the first PUCCH spatial relationship information configuration in which the wireless device is active.

[0334] In one example, as illustrated in FIG. 42, the wireless device may receive a second command to disable the PS mode in an active BWP. In response to receiving the second command, the wireless device may switch from the PS mode to the full-function mode. In response to switching to the full-function mode, the wireless device may resume the transmission of the PUCCH according to the second PUCCH spatial relationship information configuration before receiving a new MAC CE to enable the new PUCCH spatial relationship information configuration. In one example, the wireless device may determine the second PUCCH spatial relationship information configuration based on one or more RSs for monitoring the PDCCH in the PS mode.

[0335] In one example, the wireless device may resume transmission of the PUCCH according to the first PUCCH spatial relationship information configuration before receiving a new MAC CE to activate the new PUCCH spatial relationship information configuration in response to switching to full function mode.

[0336] According to an exemplary embodiment of FIG. 42, in PS mode, the wireless device may stop PUCCH transmission based on the spatial relationship information configuration activated in full-function mode, and resume PUCCH transmission based on the spatial relationship information configuration when switching from PS mode to full-function mode. The exemplary embodiment may reduce power consumption of the wireless device in PS mode, reduce uplink interference to other wireless devices, and / or increase uplink spectrum efficiency. The exemplary embodiment may reduce signaling overhead for reactivating the PUCCH spatial relationship information configuration to transmit PUCCH when switching from PS mode to full-function mode.

[0337] In one example, a wireless device may receive a Media Access Control element that enables semi-persistent Channel State Information (SP CSI) on a PUCCH. In response to receiving the Media Access Control element, the wireless device may transmit an SP CSI report via a PUCCH resource for SP CSI reporting. The wireless device may receive a first command indicating a switch to a sleep mode. In response to receiving the first command, the wireless device may suspend the transmission of the SP CSI report via the PUCCH resource. In one example, the wireless device may receive a second command indicating a switch from a sleep mode. In response to receiving the second command, the wireless device may resume the transmission of the SP CSI report via the PUCCH resource.

[0338] In one example, a wireless device may receive a first downlink control information (DCI) that enables SP CSI reporting on PUSCH. In response to receiving the first DCI, the wireless device may transmit SP CSI reporting via a PUSCH resource for SP CSI reporting. The wireless device may receive a second DCI indicating a switch to a power-saving mode. In response to receiving the second DCI, the wireless device may disable SP CSI reporting on PUSCH. In one example, the wireless device may receive a third DCI indicating a switch from a power-saving mode and enabling SP CSI reporting on PUSCH. In response to receiving the third DCI, the wireless device may transmit SP CSI reporting via a PUSCH resource.

[0339] In one example, a wireless device may receive a MAC CE that enables SP SRS transmission. The wireless device may transmit SP SRS in response to the MAC CE. The wireless device may receive a first DCI indicating a switch to a power-saving mode. In response to receiving the first DCI, the wireless device may suspend SP SRS transmission. In one example, the wireless device may receive a second DCI indicating a switch from a power-saving mode. In response to receiving the second DCI, the wireless device may resume SP SRS transmission.

[0340] FIG. 43 illustrates an exemplary flowchart of transmission via CG type 2 in a power-saving state according to one aspect of one embodiment of the present disclosure. In 4310, a wireless device (e.g., UE) receives configuration parameters of CG type 2 associated with a given cell. The configuration parameters consist of one or more RRC messages. In 4320, the wireless device receives a first DCI indicating the activation of CG type 2. In 4330, the wireless device transmits an uplink TB based on the configuration parameters of CG type 2. In 4340, the wireless device switches the cell to a sleep state in response to receiving a second DCI. The second DCI indicates that the cell has switched to a sleep state. In 4350, in response to switching the cell to a sleep state, the wireless device clears the CG type 2 associated with the cell and retains the configuration parameters of CG type 2.

[0341] According to an exemplary embodiment, the wireless device stops transmitting TB through the wireless resources of the cell's CG type 2 in response to erasing CG type 2.

[0342] According to an exemplary embodiment, the second DCI does not indicate the deactivation of CG type 2.

[0343] According to an exemplary embodiment, the configuration parameters of CG type 2 include at least one of a frequency hopping indicator, one or more demodulation reference signal configuration parameters, a transmission periodicity indicator, and / or one or more power control parameters.

[0344] According to an exemplary embodiment, the dormancy of a cell includes the period during which a cell deactivation timer associated with the cell is running.

[0345] According to an exemplary embodiment, the cell's dormancy includes a period during which the wireless device performs at least one of stopping monitoring one or more downlink control channels in the active downlink bandwidth portion of the cell, stopping one or more uplink channel transmissions in the active uplink bandwidth portion of the cell, and / or transmitting channel status information reports for the cell.

[0346] According to an exemplary embodiment, a first DCI is received with the cyclic redundancy check bits of the first DCI scrambled by a configured scheduling wireless network temporary identifier (CS-RNTI).

[0347] According to an exemplary embodiment, a second DCI is received with the cyclic redundancy check bits of the second DCI scrambled by a power-saving wireless network temporary identifier (PS-RNTI).

[0348] According to an exemplary embodiment, a second DCI is received with the cyclic redundancy check bits of the second DCI scrambled by a cell radio network temporary identifier (C-RNTI) that identifies a wireless device.

[0349] According to an exemplary embodiment, the second DCI includes a group common DCI addressed to a group of wireless devices including a wireless device.

[0350] According to an exemplary embodiment, a wireless device activates a first downlink bandwidth portion (BWP) among a plurality of downlink BWPs of a cell as an active downlink BWP of the cell.

[0351] According to an exemplary embodiment, a wireless device receives a third DCI indicating that the cell is switched to a non-dormant state and a fourth DCI indicating the activation of CG type 2. The wireless device activates CG type 2 based on the third DCI and the fourth DCI. Based on the activation of CG type 2, the wireless device transmits an uplink TB through the wireless resources of CG type 2.

[0352] According to an exemplary embodiment, the non-dormant state of the cell includes a period during which the wireless device performs at least one of monitoring one or more downlink control channels in the active downlink bandwidth portion of the cell, transmitting one or more uplink channels in the active uplink bandwidth portion of the cell, and / or transmitting a channel status information report for the cell.

[0353] According to an exemplary embodiment, a wireless device receives a Media Access Control element, namely a MAC CE, indicating the activation of a cell. Based on the MAC CE indicating the activation of the cell, the wireless device switches the cell to an active state.

[0354] According to an exemplary embodiment, the wireless device does not switch from the first uplink BWP to the second uplink BWP as the active uplink BWP of the cell in response to switching the cell to a sleep state, wherein the cell comprises at least the first uplink BWP and the second uplink BWP. A configuration parameter indicates that CG type 2 is configured in the first uplink bandwidth portion of the cell.

[0355] According to an exemplary embodiment, the first DCI further indicates uplink accept parameters of a configured uplink accept type 2, comprising a time domain offset for CG type 2, a start symbol for CG type 2, a length indicator indicating the number of symbols for CG type 2, and / or one or more resource blocks for CG type 2. Clearing a configured uplink accept type 2 includes clearing the uplink accept parameters of a configured uplink accept type 2.

[0356] FIG. 44 illustrates an exemplary flowchart of transmission via CG type 2 in a power-saving state according to one aspect of one embodiment of the present disclosure. In 4410, a base station transmits configuration parameters of CG type 2 associated with a given cell to a wireless device. The configuration parameters consist of one or more RRC messages. In 4420, the base station transmits a first DCI indicating the activation of CG type 2 for the wireless device. In 4430, the base station receives an uplink TB from the wireless device based on the configuration parameters of CG type 2. In 4440, the base station transmits a second DCI indicating the transition of the cell to a sleep state for the wireless device. The base station transitions the cell to a sleep state based on the second DCI for the wireless device. In 4450, the base station, in response to the cell’s transition to a sleep state for a wireless device, erases the CG type 2 associated with the cell for the wireless device and retains the configuration parameters of the CG type 2 for the wireless device.

[0357] FIG. 45 illustrates an exemplary flowchart of uplink transmission through CG type 1 in a power-saving state according to one aspect of one embodiment of the present disclosure. In 4510, a wireless device (e.g., UE) receives one or more RRC messages containing configuration parameters of CG type 1 associated with a given cell. In 4520, the wireless device transmits an uplink TB based on the configuration parameters of CG type 1. In 4530, the wireless device receives a first DCI indicating a transition of the cell to a sleep state. The wireless device transitions the cell to a sleep state based on the first DCI. In 4540, the wireless device suspends the CG type 1 associated with the cell in response to the first DCI indicating a transition of the cell to a sleep state. The wireless device stops uplink transmission through the wireless resources of CG type 1 based on the suspension of CG type 1.

[0358] According to an exemplary embodiment, the wireless device maintains the configuration parameters of CG type 1 in response to switching the cell to a sleep state.

[0359] According to an exemplary embodiment, the wireless device reactivates a suspended CG type 1 associated with the cell in response to receiving a second DCI indicating that the cell is transitioning from a sleep state to an active state. Based on the reactivation of the suspended CG type 1, the wireless device transmits one or more uplink TBs over the wireless resources of the CG type 1.

[0360] FIG. 46 illustrates an exemplary flowchart of transmission via CG type 1 in a power-saving state according to one aspect of one embodiment of the present disclosure. In 4610, the base station transmits one or more RRC messages to the wireless device, including configuration parameters of CG type 1 associated with a given cell. In 4620, the base station receives an uplink TB from the wireless device based on the configuration parameters of CG type 1. In 4630, the base station transmits a first DCI indicating the transition of the cell for the wireless device to a sleep state. The base station transitions the cell for the wireless device to a sleep state. In 4640, the base station suspends the CG type 1 associated with the cell for the wireless device in response to the transition of the cell to a sleep state.

[0361] In NR (New Radio) Release 15, methods for enhanced reliability as well as TTI structures for low latency were introduced to provide basic support for URLLC. More stringent URLLC requirements necessitate improvements to the capabilities of NR Release 15. Exemplary use cases for enhanced URLLC include AR / VR (entertainment industry), factory automation, the transportation industry (including remote operation use cases), and power distribution. Examples of more stringent URLLC requirements, depending on the use case (factory automation, transportation industry, and power distribution), include higher reliability (up to level 1E-6), higher availability, and short latency of approximately 0.5 to 1 ms. Examples of features requiring enhancement for enhanced URLLC include PDCCH enhancements (e.g., compact DCI, PDCCH repetition, increased PDCCH monitoring capability), UCI enhancements (enhanced HARQ feedback method (increased number of HARQ transmission possibilities within a given slot), CSI feedback enhancements, PUSCH enhancements (e.g., mini-slot level hopping and retransmission / repetition enhancements), scheduling / HARQ / CSI processing timelines (wireless device and base station), enhanced multiplexing considering various latency and reliability requirements (e.g., Tx prioritization / multiplexing between UL UEs), and enhanced UL configuration acknowledgment (acknowledgment-free) transmission, accompanied by research focused on enhanced configuration acknowledgment behavior (e.g., explicit HARQ-ACK, ensuring K-repetition and mini-slot repetition within a given slot), PDCCH enhancements (e.g., mini-slot level hopping and retransmission / repetition enhancements), scheduling / HARQ / CSI processing timelines (wireless device and base station), enhanced multiplexing considering various latency and reliability requirements (e.g., Tx prioritization / multiplexing between UL UEs), and enhanced UL configuration acknowledgment (acknowledgment-free) transmission.

[0362] Legacy CSI reporting mechanisms depend on DRX procedures. Due to legacy processes, situations may arise where a wireless device does not transmit a periodic CSI report even if the base station triggers the wireless device to transmit a periodic CSI via PUCCH. This leads to inefficient scheduling and network performance degradation. There is a need to improve legacy processes for CSI reporting and DRX. Exemplary embodiments improve legacy CSI reporting and DRX processes.

[0363] In an exemplary embodiment as illustrated in FIG. 47, a wireless device may receive one or more messages containing configuration parameters. One or more messages may include one or more RRC messages. One or more messages may include configuration parameters of one or more cells. In one example, one or more cells may include a primary cell. In one example, one or more cells may include a primary cell and one or more secondary cells. In one example, one or more uplink control channels may be configured in the primary cell. In one example, one or more uplink control channels may be configured in one or more first secondary cells among the one or more cells. In one example, one or more uplink control channels may include one or more first short uplink control channels. In one example, the short uplink control channel may have a shorter duration than the long uplink control channel. In one example, the duration of the short uplink control channel may be one or more symbols. In one example, the duration of the short uplink control channel may be one or more symbols and may be shorter than the slot duration. In one example, a short uplink control channel may be used to transmit CSI reports of one or more types of CSI among multiple CSI types (e.g., periodic, non-periodic, semi-continuous, etc.).

[0364] The configuration parameters may include Channel State Information (CSI) configuration parameters. In ...

Claims

Claim 1 A method comprising: receiving, by a wireless device, first downlink control information (DCI) indicating the activation of a configured uplink acknowledgment type 2 of a cell; transmitting a transmission block based on the configured uplink acknowledgment type 2; switching the cell to a sleep state in response to receiving a second DCI; and clearing the configured uplink acknowledgment type 2 associated with the cell in response to switching the cell to a sleep state. Claim 2 A method according to claim 1, wherein the step of converting the cell to a dormant state includes the step of converting the cell to a dormant state while maintaining the activation of the cell. Claim 3 A method according to claim 1, further comprising the step of transmitting a channel state information timer for the cell during the dormant state. Claim 4 A method according to claim 1, wherein the dormant state of the cell includes a period when a cell deactivation timer associated with the cell is running. Claim 5 A method according to claim 1, further comprising: receiving a media access control element (MAC CE) indicating the activation of the cell; and activating the cell based on the MAC CE indicating the activation of the cell—the step of switching the cell to a sleep state is after the activation. Claim 6 The method of claim 1 further comprises a step of deactivating the cell after the step of switching the cell to a dormant state, wherein the deactivating step is based on: receiving a MAC CE indicating the deactivation of the cell; or the expiration of a cell deactivation timer. Claim 7 A method according to claim 1, wherein the second DCI includes a group common DCI addressed to a wireless device group including the wireless device, and the group common DCI is associated with a group common wireless network temporary identifier including a power-saving wireless network temporary identifier. Claim 8 The method of claim 1, wherein the dormant state of the cell comprises a period during which the wireless device performs at least one of the following: stopping monitoring of one or more downlink control channels in the active downlink bandwidth portion of the cell; or stopping transmission of one or more uplink channels in the active uplink bandwidth portion of the cell; or transmitting channel status information for the active uplink bandwidth portion of the cell. Claim 9 A wireless device comprising one or more processors and memory, wherein the memory comprises instructions that cause the wireless device to perform the method of any one of claims 1 to 8 when executed by the one or more processors. Claim 10 A method comprising: transmitting a first downlink control information (DCI) to a wireless device by a base station indicating the activation of a configured uplink acknowledgment type 2 of a cell of the wireless device; receiving a transmission block based on the configured uplink acknowledgment type 2; switching the cell of the wireless device to a sleep state in response to transmitting a second DCI; and clearing the configured uplink acknowledgment type 2 associated with the cell in response to switching the cell to a sleep state. Claim 11 A method according to claim 10, wherein the step of converting the cell to a dormant state includes the step of converting the cell to a dormant state while maintaining the activation of the cell. Claim 12 A method according to claim 10, further comprising the step of receiving a channel status report for the cell from the wireless device during the above-mentioned dormant state. Claim 13 In claim 10, the dormant state of the cell includes the period when the cell deactivation timer associated with the cell is running. Claim 14 In claim 10, the method further comprises: transmitting a media access control element (MAC CE) indicating the activation of the cell; activating the cell based on the MAC CE indicating the activation of the cell - the step of switching the cell to a sleep state is after the activation -; and further comprising a step of deactivating the cell after the step of switching the cell to a sleep state, wherein the deactivating step is based on: transmitting a MAC CE indicating the deactivation of the cell; or the expiration of a cell deactivation timer. Claim 15 A method according to claim 10, wherein the second DCI comprises a group common DCI addressed to a wireless device group including the wireless device, and the group common DCI is associated with a group common wireless network temporary identifier including a power-saving wireless network temporary identifier. Claim 16 A base station comprising one or more processors and memory, wherein the memory comprises instructions that cause the wireless device to perform the method of any one of claims 10 to 15 when executed by the one or more processors. Claim 17 A system comprising a wireless device according to paragraph 10 and a base station according to paragraph 16. Claim 18 A computer-readable non-transient storage medium comprising instructions that cause the processor to perform the method of any one of claims 1 through 8 and claims 10 through 15 when executed by the processor. Claim 19 delete Claim 20 delete Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete Claim 33 delete Claim 34 delete Claim 35 delete Claim 36 delete Claim 37 delete Claim 38 delete Claim 39 delete Claim 40 delete Claim 41 delete Claim 42 delete Claim 43 delete Claim 44 delete Claim 45 delete Claim 46 delete Claim 47 delete Claim 48 delete Claim 49 delete Claim 50 delete Claim 51 delete Claim 52 delete Claim 53 delete Claim 54 delete Claim 55 delete Claim 56 delete Claim 57 delete Claim 58 delete Claim 59 delete Claim 60 delete Claim 61 delete Claim 62 delete Claim 63 delete Claim 64 delete Claim 65 delete Claim 66 delete Claim 67 delete Claim 68 delete Claim 69 delete Claim 70 delete Claim 71 delete Claim 72 delete Claim 73 delete Claim 74 delete Claim 75 delete Claim 76 delete

Images