Power Saving Operations for Multicast and Broadcast Services

Abstract

A wireless device receives parameters indicating the following: a first discontinuous reception (DRX) configuration associated with a unicast transmission, and a second DRX configuration associated with a multicast transmission. The wireless device receives a power saving (PS) indication of a PS operation indicating a DRX on duration. In response to the PS indication indicating the PS operation, the wireless device skips monitoring a first physical downlink control channel (PDCCH) associated with the unicast transmission during a first DRX on duration of the first DRX configuration. Regardless of the PS indication, the wireless device monitors a second PDCCH associated with the multicast transmission during a second DRX on duration of the second DRX configuration.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 122,111, filed December 7, 2020, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] Figure 1A and Figure 1B show an exemplary mobile communication network in which embodiments of the present disclosure can be implemented.

[0005] Figure 2A and Figure 2B show the New Radio (NR) user plane and control plane protocol stacks, respectively.

[0006] Figure 3 show an example of a service provided between protocol layers of the NR user plane protocol stack in Figure 2A .

[0007] Figure 4A show an exemplary downlink data flow that flows through Figure 2A of the NR user plane protocol stack.

[0008] Figure 4B show an exemplary format of the MAC sub - header in the MAC PDU.

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

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

[0011] Figure 7 show an exemplary configuration of an NR frame into which OFDM symbols are grouped.

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

[0013] Figure 9 show an example of bandwidth adaptation using three configured BWPs of an NR carrier.

[0014] Figure 10A show three carrier aggregation configurations with two component carriers.

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

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

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

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

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

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

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

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

[0023] Figure 16A 、 Figure 16B 、 Figure 16C and Figure 16D Exemplary structures for uplink and downlink transmissions are shown.

[0024] Figure 17A 、 Figure 17B and Figure 17C Examples of the MAC sub-header are shown.

[0025] Figure 18A Examples of DL MAC PDUs are shown.

[0026] Figure 18B Examples of UL MAC PDUs are shown.

[0027] Figure 19 Examples of multiple LCIDs for the downlink are shown.

[0028] Figure 20 Examples of multiple LCIDs for the uplink are shown.

[0029] Figure 21A andFigure 21B Shows an example of the SCell activation / deactivation MAC CE format.

[0030] Figure 22 Shows an example of the BWP activation / deactivation on the SCell.

[0031] Figure 23A 、 Figure 23B and Figure 23C Shows an example of the configuration parameters of the MIB.

[0032] Figure 24 Shows an example of the RRC configuration of the SIB1 message.

[0033] Figure 25 Shows an example of the RRC configuration of the downlink BWP.

[0034] Figure 26 Shows an example of the RRC configuration of the search space.

[0035] Figure 27A and Figure 27B Shows examples of unicast, multicast, and broadcast transmissions.

[0036] Figure 28A and Figure 28B Shows an example of the MBS resource allocation mode.

[0037] Figure 29 Shows an exemplary implementation of DRX operation.

[0038] Figure 30 Shows an exemplary implementation of DRX operation.

[0039] Figure 31 Shows an exemplary implementation of power saving for MBS transmission.

[0040] Figure 32 Shows an exemplary implementation of power saving for MBS transmission.

[0041] Figure 33 Shows an exemplary implementation of power saving for MBS transmission.

[0042] Figure 34 Shows an exemplary flowchart of a method for power saving in MBS transmission.

[0043] Figure 35 Shows an exemplary implementation of power saving for MBS transmission.

[0044] Figure 36 Shows an exemplary implementation of power saving for MBS transmission.

[0045] Figure 37Shows an exemplary implementation for power saving in MBS transmission. Detailed implementation

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

[0047] Implementations can be configured to operate as needed. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanisms can be executed. Exemplary criteria can be at least partially based on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary implementations can be applied. Thus, exemplary implementations of selectively implementing the disclosed protocol can be implemented.

[0048] A base station can communicate with a mixture of wireless devices. The wireless devices and / or the base station can support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may mean a subset of the total wireless devices in the coverage area. For example, this disclosure may mean multiple wireless devices with a given capability and a given LTE or 5G version in a given sector of the base station. The multiple wireless devices in this disclosure can refer to a selected multiple of wireless devices, and / or a subset of the total wireless devices in the coverage area that execute according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not conform to the disclosed method. For example, these wireless devices or base stations may execute based on an older version of LTE or 5G technology.

[0049] In the present disclosure, "a", "an", and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of one of the various suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms "comprising" and "consisting of" enumerate one or more components of the element being described. The term "comprising" is interchangeable with "including" and does not exclude components not enumerated from being included in the element being described. In contrast, "consisting of" provides a complete enumeration of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "at least partially based on" rather than, for example, "only based on". As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" can represent A; B; C; A and B; A and C; B and C; or A, B, and C.

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

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

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

[0053] Many of the features presented are described as optional by using "may" or by using parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by making selections from the group of optional features. The present disclosure should be construed as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0054] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure can be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological elements), or combinations thereof, all of which can be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement a module using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages such as assembly, C, C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages (HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between the less-functional internal hardware modules on the programmable device. The technologies mentioned are often used in combination to achieve the result of a functional module.

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

[0056] The CN 102 can provide an interface to one or more data networks (DNs) (such as a public DN (e.g., the Internet), a private DN, and / or an operator-internal DN) to the wireless devices 106. As part of the interface function, the CN 102 can set up end-to-end connections between the wireless devices 106 and one or more DNs, authenticate the wireless devices 106, and provide a charging function.

[0057] The RAN 104 can connect the CN 102 to the wireless device 106 via radio communication over the air interface. As part of the radio communication, the RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is referred to as the downlink, while the communication direction from the wireless device 106 to the RAN 104 over the air interface is referred to as the uplink. Frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques can be used to separate downlink transmissions from uplink transmissions.

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

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

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

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

[0062] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna patterns and similar high-level transmission powers. RAN 104 can be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas that overlap with the relatively large coverage areas provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas with weak macrocell coverage. Examples of small cell base stations, in decreasing order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0063] The 3rd Generation Partnership Project (3GPP) was established in 1998 to provide global specification standardization for mobile communication networks similar to the mobile communication network 100 in Figure 1A So far, 3GPP has developed specifications for three generations of mobile networks: the 3rd generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the 4th generation (4G) network known as Long-Term Evolution (LTE), and the 5th generation (5G) network known as the 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network known as the Next Generation RAN (NG-RAN). These embodiments can be applicable to the RANs of other mobile communication networks, such as Figure 1A the RAN 104 in

[0064] Figure 1BFIG. 150 shows another exemplary mobile communication network in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. As Figure 1B shown, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UEs 156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A FIGs. 151-152.

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

[0066] As Figure 1B shown, the 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are shown as one component AMF / UPF 158 for ease of illustration in Figure 1B FIG. 152. The UPF 158B may act as a gateway between the NG-RAN 154 and the one or more DNs. Functions that the UPF 158B may perform include, for example: packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, support for uplink classification for routing traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may act as an anchor for mobility within / across radio access technologies (RATs), an external protocol (or packet) data unit (PDU) session point for interconnecting with the one or more DNs, and / or a pivot for supporting multi-homed PDU sessions. The UEs 156 may be configured to receive services via PDU sessions, which are logical connections between the UEs and the DNs.

[0067] The functions that the AMF 158A can perform include, for example: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, in-system and inter-system mobility support, access authentication, access authorization including roaming right verification, mobility management control (subscription and policy), network slice support, and / or session management function (SMF) selection. NAS can refer to the functions operating between the CN and the UE, and AS can refer to the functions operating between the UE and the RAN.

[0068] The 5G-CN 152 may include one or more additional network functions not shown for clarity in Figure 1B For example, the 5G-CN 152 may include one or more of the following: session management function (SMF), NR repository function (NRF), policy control function (PCF), network exposure function (NEF), unified data management (UDM), application function (AF), and / or authentication server function (AUSF).

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

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

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

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

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

[0074] As discussed, Figure 1B the interfaces between the network elements in

[0075] Figure 2A and Figure 2B can be associated with the protocol stacks used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. The user plane can handle data of interest to the user, while the control plane can handle signaling messages of interest to the network elements. Figure 2A and Figure 2B show examples of the NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220, respectively. Figure 2A and Figure 2B The protocol stacks shown in Figure 1B can be the same as or similar to those for the Uu interface between UE156A and gNB 160A shown in Figure 1B

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

[0077] Figure 3 shows an example of the services provided between the protocol layers of the NR user plane protocol stack. From Figure 2A and Figure 3Starting from the top, the SDAPs 215 and 225 can perform QoS flow processing. The UE 210 can receive services through a PDU session, which can be a logical connection between the UE 210 and the DN. The PDU session can have one or more QoS flows. The UPF in the CN (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). The SDAPs 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between the QoS flow and the data radio bearer can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flow and the data radio bearer through reflected mapping or control signaling received from the gNB 220. For reflected mapping, the SDAP 225 at the gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between the QoS flow and the data radio bearer.

[0078] The PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from the expected source. The PDCPs 214 and 224 can perform retransmission of undelivered packets, in-order delivery and reordering of packets, and removal of packets that are repeatedly received due to, for example, handover within the gNB. The PDCPs 214 and 224 can perform packet duplication to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0079] Although Figure 3 not shown in, the PDCPs 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual-connectivity scenario. Dual connectivity is a technique that allows the UE to be connected to two cells or more generally to two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225) is handled by the cell groups in the dual connectivity. The PDCPs 214 and 224 can map / demap split radio bearers between RLC channels belonging to the cell groups.

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

[0081] MAC 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing can include: multiplexing data units belonging to the one or more logical channels into / demultiplexing the data units from the transport blocks delivered to / from PHY 211 and 221. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling can be performed for the downlink and uplink at gNB 220 (at MAC 222). MAC 212 and 222 can be configured to perform 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 logical channels of UE 210 by means of logical channel prioritization, and / or padding. MAC 212 and 222 can support one or more parameter sets and / or transmission timings. In an example, the mapping restrictions in logical channel prioritization can control which parameter set and / or transmission timing a logical channel can use. As Figure 3 shown, MAC 212 and 222 can provide logical channels as services to RLC 213 and 223.

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

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

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

[0085] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., regarding Figure 3 ), add corresponding headers, and forward their respective outputs to the next lower layer. For example, PDCP 224 can perform IP header compression and encryption and forward its output to RLC 223. RLC 223 can optionally perform segmentation (e.g., as shown for IP packet m in Figure 4A ) and forward its output to MAC 222. MAC 222 can multiplex a number of RLC PDUs and can attach a MAC sub-header to the RLC PDUs to form a transport block. In NR, the MAC sub-header can be distributed throughout the MAC PDU, as shown in Figure 4A . In LTE, the MAC sub-header can be entirely at the start of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be calculated before the complete MAC PDU is assembled.

[0086] Figure 4BIllustrates an exemplary format of a MAC sub-header in a MAC PDU. The MAC sub-header includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU corresponding to the MAC sub-header; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0087] Figure 4B Further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B Illustrates two MAC CEs inserted into the MAC PDU. The MAC CEs can be inserted at the start of a downlink transmission of the MAC PDU (as Figure 4B shown) and at the end of an uplink transmission of the MAC PDU. The MAC CEs can be used for in-band control signaling. Exemplary MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC sub-header having a format similar to the format described for the MAC SDU can exist before the MAC CE, and the MAC CE can be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

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

[0090] - Paging Control Channel (PCCH), which is used to carry paging messages for paging UEs whose location is unknown to the network at the cell level;

[0091] - Broadcast Control Channel (BCCH), which is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), where the system information messages can be used by the UE to obtain information on how the cell is configured and how to operate within the cell;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0106] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, and the UCI can include HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

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

[0109] Figure 2B shows an exemplary NR control plane protocol stack. As shown in Figure 2BAs shown, the NR control plane protocol stack can use the same / similar first four protocol layers as the exemplary NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack has Radio Resource Control (RRC) 216 and 226 and NAS protocol 217 and 237 at the top of this NR control plane protocol stack.

[0110] NAS protocol 217 and 237 can provide control plane functions between UE 210 and AMF 230 (e.g., AMF 158A), or more generally between UE 210 and the CN. NAS protocol 217 and 237 can provide control plane functions between UE 210 and AMF 230 via signaling messages called NAS messages. There is no direct path through which NAS messages can be transmitted between UE 210 and AMF 230. The AS of the Uu and NG interfaces can be used to transmit NAS messages. NAS protocol 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0111] RRC 216 and 226 can provide control plane functions between UE 210 and gNB 220, or more generally between UE 210 and the RAN. RRC 216 and 226 can provide control plane functions between UE 210 and gNB 220 via signaling messages called RRC messages. Signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers can be used to transmit RRC messages between UE 210 and the RAN. The MAC can multiplex control plane and user plane data into the same transport block (TB). The control plane functions that RRC 216 and 226 can provide include, for example: broadcasting of system information related to the AS and NAS; paging initiated by the CN or RAN; establishment, maintenance, and release of the RRC connection between UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of the report; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS message passing. As part of establishing the RRC connection, RRC 216 and 226 can establish an RRC context, which can involve configuring parameters for communication between UE 210 and the RAN.

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

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

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

[0115] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC Connected 602 with reduced signaling overhead compared to the transition from RRC Idle 604 to RRC Connected 602. While in RRC Inactive 606, the UE may be in a sleep state, and the mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 through a Connection Resumption Procedure 614, or to RRC Idle 604 through a Connection Release Procedure 616, which may be the same or similar to the Connection Release Procedure 608.

[0116] The RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to notify the UE of an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at a cell group level, so that the paging message may be broadcast over a cell in the cell group in which the UE currently resides instead of over the entire mobile communication network. The mobility management mechanism used for RRC idle 604 and RRC inactive 606 tracks the UE at a cell group level. These mobility management mechanisms may do so using groups of different granularities. For example, there may be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

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

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

[0119] The base station storing the RRC context for the UE or the last serving base station of the UE can be referred to as the anchor base station. The anchor base station can maintain the RRC context for the UE at least during the period when the UE remains in the RAN notification area of the anchor base station and / or during the period when the UE remains in the RRC inactive 606 state.

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

[0121] In NR, physical signals and physical channels (regarding Figure 5A and Figure 5BThe one discussed) can be mapped onto an Orthogonal Frequency Division Multiplexing (OFDM) symbol. OFDM is a multi-carrier communication scheme that transmits data over F orthogonal sub-carriers (or tones). Before transmission, the data can be mapped onto a series of complex symbols called source symbols (e.g., M-ary Quadrature Amplitude Modulation (M-QAM) symbols or M-ary Phase Shift Keying (M-PSK) symbols), and divided into F parallel symbol streams. The F parallel symbol streams can be considered as if they were in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal sub-carriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal sub-carriers. The F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be scrambled using an FFT block before being processed by the IFFT block. This operation produces a Discrete Fourier Transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the Peak-to-Average Power Ratio (PAPR). The inverse processing of the OFDM symbol can be performed at the receiver using an FFT block to recover the data mapped onto the source symbols.

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

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

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

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

[0126] Figure 8Shows a single parameter set used across the entire bandwidth of an NR carrier. In other exemplary configurations, multiple parameter sets can be supported on the same carrier.

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

[0128] NR defines a bandwidth part (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of consecutive RBs on a carrier. A UE can be configured (e.g., via the RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell can be active. The one or more BWPs can be referred to as the active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

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

[0130] For a downlink BWP in the set of configured downlink BWPs on a primary cell (PCell), the base station can configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domain where a UE can look for control information. The search space can be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, the base station can configure a common search space for a UE on the PCell or a primary-secondary cell (PSCell) in the active downlink BWP.

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

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

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

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

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

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

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

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

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

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

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

[0142] When using CA, one of the aggregated cells in the aggregated cells for a UE can be called a primary cell (PCell). The PCell can be the serving cell to which the UE is initially connected at RRC connection establishment, re - establishment, and / or handover. The PCell can provide the UE with NAS mobility information and security inputs. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be called the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be called the uplink primary CC (UL PCC). Other aggregated cells for the UE can be called secondary cells (SCells). In an example, the SCell can be configured after the PCell is configured for the UE. For example, the SCell can be configured through the RRC connection re - configuration procedure. In the downlink, the carrier corresponding to the SCell can be called the downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell can be called the uplink secondary CC (UL SCC).

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

[0144] The downlink control information of a cell (such as scheduling assignment and scheduling grant) can be transmitted on the cell corresponding to the assignment and grant, which is called self - scheduling. The DCI of a cell can be transmitted on another cell, which is called cross - carrier scheduling. The uplink control information for the aggregated cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PUCCH of the PCell. For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. The cells can be divided into multiple PUCCH groups.

[0145] Figure 10B An example showing how the aggregated cells can be configured into one or more PUCCH groups is presented. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In Figure 10BIn the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs in this example: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as a primary Scell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted on the uplink of PSCell 1061. In the example, if Figure 10B the aggregated cells depicted in Figure 10B are not partitioned into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell transmits UCI related to the downlink CCs, and the PCell may become overloaded. By partitioning the transmission of UCI between PCell 1021 and PSCell 1061, overload can be prevented.

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

[0147] In CA, the multi-carrier nature of the PHY may be exposed to the MAC. In the example, the HARQ entity may operate on the serving cell. The transport block may be generated according to the assignment / grant of each serving cell. The transport block and the potential HARQ retransmission of the transport block may be mapped to the serving cell.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] In an example, the transmitter (e.g., the base station) can use a precoding matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoding matrix for a first bandwidth and a second precoding matrix for a second bandwidth. The first precoding matrix and the second precoding matrix can be different based on the difference between the first bandwidth and the second bandwidth. The UE can assume the same precoding matrix is used throughout the set of PRBs. The set of PRBs can be represented as a precoding resource block group (PRG).

[0163] The PDSCH can include one or more layers. The UE can assume that at least one symbol with DMRS exists on a layer among the one or more layers of the PDSCH. The higher layer can configure up to 3 DMRSs for the PDSCH.

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

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

[0166] The PUSCH can include one or more layers, and the UE can transmit at least one symbol with DMRS on the layer(s) present in one or more layers of the PUSCH. In an example, the higher layer can configure up to three DMRS for the PUSCH.

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

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

[0169] The base station may semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; time domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and / or sub-frame level period; slot of the periodic and / or aperiodic SRS resource; number of OFDM symbols in the SRS resource; start OFDM symbol of the SRS resource; SRS bandwidth; hopping bandwidth; cyclic shift; and / or SRS sequence ID.

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

[0171] Channels using beamforming require beam management. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on a downlink reference signal (e.g., channel state information reference signal (CSI-RS)) and generate a beam measurement report. After the RRC connection is set up by the base station, the UE may perform a downlink beam measurement procedure.

[0172] Figure 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown in [Figure] can represent resource blocks (RBs) within the bandwidth of a cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured for a CSI-RS resource configuration by higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scrambling identity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

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

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

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

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

[0179] The UE may measure the quality of the beam pair link using one or more reference signals (RSs), the one or more reference signals including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam pair link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, reference signal received quality (RSRQ) value, and / or CSI value measured on an RS resource. The base station may indicate that an RS resource is quasi-co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). The one or more DMRSs of the RS resource and the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) of the transmission from the RS resource to the UE are similar to or the same as the channel characteristics of the transmission from the channel to the UE.

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

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

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

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

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

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

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

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

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

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

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

[0191] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If the C-RNTI is included in Msg 31313, the base station will address the UE on the PDCCH using the C-RNTI. If the unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure has been successfully completed. If the TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in the RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU transmitted (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution is successful and / or the UE may determine that the random access procedure has been successfully completed.

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

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

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

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

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

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

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

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

[0200] The transport block 1342 can include data (e.g., delay-sensitive data), the identifier of the UE, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station can transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 can include at least one of the following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., C-RNTI or TC-RNTI). The UE can determine that the two-step random access procedure is successfully completed if any of the following conditions are met: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., the transport block 1342).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0215] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 in accordance with an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as Figure 1A the mobile communication network 100 shown,Figure 1B The mobile communication network 150 or any other communication network shown. Figure 15 Only one wireless device 1502 and one base station 1504 are shown, but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same or similar configurations as those shown. Figure 15 shown.

[0216] The base station 1504 can connect the wireless device 1502 to a core network (not shown) through radio communication via an air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 through the air interface 1506 is called the downlink, while the communication direction from the wireless device 1502 to the base station 1504 through the air interface is called the uplink. Frequency-division duplexing (FDD), time-division duplexing (TDD), and / or some combination of the two duplexing techniques can be used to separate downlink transmissions from uplink transmissions.

[0217] In the downlink, the data to be sent from the base station 1504 to the wireless device 1502 can be provided to the processing system 1508 of the base station 1504. This data can be provided to the processing system 1508 through, for example, the core network. In the uplink, the data to be sent from the wireless device 1502 to the base station 1504 can be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 can implement layer 3 and layer 2 OSI functions to process the data for transmission. Layer 2 can include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer regarding Figure 2A , Figure 2B , Figure 3 and Figure 4A . The RLC layer and the MAC layer. Layer 3 can include the RRC layer regarding Figure 2B .

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

[0219] At base station 1504, the receive processing system 1512 can receive an uplink transmission from wireless device 1502. At wireless device 1502, the receive processing system 1522 can receive a downlink transmission from base station 1504. The receive processing system 1512 and the receive processing system 1522 can implement layer 1 OSI functions. Layer 1 can include regarding Figure 2A , Figure 2B , Figure 3 and Figure 4A of the PHY layer. For receive processing, the PHY layer can perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, etc.

[0220] As Figure 15 shown, wireless device 1502 and base station 1504 can include multiple antennas. The multiple antennas can be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, wireless device 1502 and / or base station 1504 can have a single antenna.

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

[0222] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0223] The processing system 1508 and / or the processing system 1518 may be respectively connected to one or more peripheral devices 1516 and one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functions, such as speakers, microphones, keyboards, displays, touch pads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, Internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). The processing system 1508 and / or the processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the above-mentioned one or more peripheral devices. The processing system 1518 in the wireless device 1502 may receive power from a power supply and / or may be configured to distribute power to other components in the wireless device 1502. The power supply may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be respectively connected to a GPS chipset 1517 and a GPS chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide the geographical location information of the wireless device 1502 and the base station 1504, respectively.

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

[0225] Figure 16B An exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal of an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed before transmission.

[0226] Figure 16C An exemplary structure for downlink transmission is shown. The baseband signal representing the Physical Downlink Channel may perform one or more functions. The one or more functions may include: scrambling the coded bits in the codeword to be transmitted on the physical channel; modulating the scrambled bits to generate complex-valued modulated symbols; mapping the complex-valued modulated symbols to one or more transport layers; precoding of the complex-valued modulated symbols on the layer for transmission on an antenna port; mapping the complex-valued modulated symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for an antenna port; and so on. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0227] Figure 16D Another exemplary structure for modulating and upconverting a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued OFDM baseband signal of an antenna port. Filtering may be employed before transmission.

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

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

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

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

[0232] In an example, the MAC PDU can include one or more MAC sub-PDUs. The MAC sub-PDUs in one or more MAC sub-PDUs can include: only the MAC sub-header (including padding); the MAC sub-header and the MAC SDU; the MAC sub-header and the MAC CE; the MAC sub-header and the padding, or a combination thereof. The MAC SDU can have a variable size. The MAC sub-header can correspond to the MAC SDU, MAC CE, or padding.

[0233] In an example, when the MAC sub-header corresponds to the MAC SDU, variable-size MAC CE, or padding, the MAC sub-header can include: an R field with a length of one bit; an F field with a length of one bit; an LCID field with a length of multiple bits; an L field with a length of multiple bits, or a combination thereof.

[0234] Figure 17A An example of a MAC sub-header with an R field, an F field, an LCID field, and an L field is shown. In Figure 17A the exemplary MAC sub-header, the length of the LCID field can be six bits, and the length of the L field can be eight bits. Figure 17B An example of a MAC sub-header with an R field, an F field, an LCID field, and an L field is shown. In Figure 17B the exemplary MAC sub-header shown, the length of the LCID field can be six bits, and the length of the L field can be sixteen bits. When the MAC sub-header corresponds to a fixed-size MAC CE or padding, the MAC sub-header can include: an R field with a length of two bits and an LCID field with a length of multiple bits. Figure 17C An example of a MAC sub-header with an R field and an LCID field is shown. In Figure 17C the exemplary MAC sub-header shown, the length of the LCID field can be six bits, and the length of the R field can be two bits.

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

[0236] In an example, the MAC entity of a base station can transmit one or more MAC CEs to the MAC entity of a wireless device. Figure 19 An example of multiple LCIDs that can be associated with one or more MAC CEs is shown. The one or more MAC CEs can include at least one of the following: SP ZP CSI-RS resource set activation / deactivation MAC CE; PUCCH spatial relation activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI reporting on PUCCH activation / deactivation MAC CE; TCI state indication for UE-specific PDCCH MAC CE; TCI state indication for UE-specific PDSCH MAC CE; aperiodic CSI trigger state sub-selection MAC CE; SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; UE contention resolution identity MAC CE; timing advance command MAC CE; DRX command MAC CE; long DRX command MAC CE; SCell activation / deactivation MAC CE (1 octet); SCell activation / deactivation MAC CE (4 octets); and / or copy activation / deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by the MAC entity of a base station to the MAC entity of a wireless device, can have an LCID in the MAC sub-header corresponding to the MAC CE. Different MAC CEs can have different LCIDs in the MAC sub-header corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC sub-header can indicate that the MAC CE associated with the MAC sub-header is a long DRX command MAC CE.

[0237] In an example, the MAC entity of a wireless device can transmit one or more MAC CEs to the MAC entity of a base station. Figure 20An example of one or more MAC CEs is shown. The one or more MAC CEs may include at least one of the following: Short Buffer Status Report (BSR) MAC CE; Long BSR MAC CE; C-RNTI MAC CE; Configured Grant Acknowledgment MAC CE; Single Entry PHR MAC CE; Multiple Entry PHR MAC CE; Short Truncated BSR; and / or Long Truncated BSR. In an example, a MAC CE may have an LCID in a MAC sub-header corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC sub-header corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC sub-header may indicate that the MAC CE associated with the MAC sub-header is a Short Truncated Command MAC CE.

[0238] In Carrier Aggregation (CA), two or more Component Carriers (CCs) may be aggregated. The wireless device may use the technology of CA to receive or transmit simultaneously on one or more CCs depending on the capabilities of the wireless device. In an embodiment, the wireless device may support CA for contiguous CCs and / or for non-contiguous CCs. The CCs may be organized into cells. For example, the CCs may be organized into one Primary Cell (PCell) and one or more Secondary Cells (SCells). When configured with CA, the wireless device may have one RRC connection with the network. During RRC connection establishment / 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 the security input may be the serving cell. In an example, the serving cell may represent the PCell. In an example, the base station may transmit one or more messages including configuration parameters of a plurality of one or more SCells to the wireless device depending on the capabilities of the wireless device.

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

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

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

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

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

[0244] Figure 21A An example of an octet SCell activation / deactivation MAC CE is shown. The first MAC PDU subheader with a first LCID (e.g., '111010' as shown in Figure 19 may identify an octet SCell activation / deactivation MAC CE. The octet SCell activation / deactivation MAC CE may have a fixed size. The octet SCell activation / deactivation MAC CE may include a single octet. The single octet may include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one). Figure 21B An example of a four-octet SCell activation / deactivation MAC CE is shown. The second MAC PDU subheader with a second LCID (e.g., '111001' as shown in Figure 19 may identify a four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE may have a fixed size. The four-octet SCell activation / deactivation MAC CE may include four octets. The four octets may include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., one).

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

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

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

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

[0249] Figure 22An example of BWP switching on a cell (e.g., PCell or SCell) is shown. In the example, the wireless device may receive at least one RRC message from the base station, and the at least one RRC message includes parameters of the cell and one or more BWPs associated with the cell. The RRC message may include: an RRC connection reconfiguration message (e.g., RRCReconfiguration); an RRC connection reestablishment message (e.g., RRCRestablishment); and / or an RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), and one BWP is configured as the default BWP (e.g., BWP 0). The wireless device may receive a command (e.g., an RRC message, a MAC CE, or DCI) to activate the cell at the nth time slot. The wireless device may start a cell deactivation timer (e.g., sCellDeactivationTimer), and start CSI-related actions for the cell, and / or start CSI-related actions for the first active BWP of the cell. The wireless device may start monitoring the PDCCH on BWP 1 in response to activating the cell.

[0250] In the example, in response to receiving DCI indicating a DL assignment on BWP 1, the wireless device may start restarting the BWP inactivity timer (e.g., BWP-InactivityTimer) at the mth time slot. When the BWP inactivity timer expires, the wireless device may switch back to the default BWP (e.g., BWP 0) as the active BWP at the sth time slot. When the sCellDeactivationTimer expires, the wireless device may deactivate the cell and / or stop the BWP inactivity timer.

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

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

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

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

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

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

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

[0258] In an example, a wireless device determines PDCCH monitoring occasions on an active DL BWP based on one or more PDCCH configuration parameters, the one or more PDCCH configuration parameters including: a PDCCH monitoring period, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a time slot. For a search space set (SS s), if then the wireless device determines that the PDCCH monitoring occasions exist in a number of f frames and a number of time slots. is the number of time slots in a frame when the configuration parameter set is μ. o s is the time slot offset indicated in the PDCCH configuration parameter. k s is the PDCCH monitoring period indicated in the PDCCH configuration parameter. The wireless device monitors PDCCH candidates for the search space set starting from a time slot for a duration of T s consecutive time slots, and does not monitor PDCCH candidates for the search space set s during the next k s -T s consecutive time slots. In the example, the USS at a CCE aggregation level L ∈ {1, 2, 4, 8, 16} is defined by a set of PDCCH candidates for the CCE aggregation level L.

[0259] In the example, the wireless device decides for a search space set s associated with CORESETp that, for the active DL BWP of a serving cell corresponding to a carrier indicator field value n CI in a time slot the CCE index of the aggregation level L corresponding to the PDCCH candidate of the search space set is where for any for for p mod 3 = 0 A p = 39827, for p mod 3 = 1 A p = 39829, for p mod 3 = 2 A p = 39839, and D = 65537; i = 0,..., L - 1; in CORESETp, N CCE，p- is the number of CCEs, numbered from 0 to N CCE,p -1; if the wireless device is configured with a carrier indicator field CrossCarrierSchedulingConfig for the serving cell on which it monitors the PDCCH, then n CI is the carrier indicator field value; otherwise, including for any CSS, n CI = 0; where is the number of PDCCH candidates that a wireless device is configured to monitor for an aggregation level L of a search space set s for a serving cell corresponding to n CI ; for any CSS, for USS, is the maximum value over all configured n CI values for an aggregation level L of CCEs for the search space set s; and the RNTI value for n RNTI is C-RNTI.

[0260] In an example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set including multiple search spaces (SS). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the DCI format being monitored. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in a common SS, and / or number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding.

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

[0262] In an example, pdcch-ConfigSIB1 may include a first parameter (e.g., controlResourceSetZero), which indicates a common ControlResourceSet (CORESET) having an ID #0 (e.g., CORESET #0) of the initial BWP of the cell. controlResourceSetZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify the configuration of CORESET #0. Figure 23B An example showing the configuration of CORESET #0. As Figure 23B shown, based on the integer value of controlResourceSetZero, the wireless device may determine the SSB and CORESET #0 multiplexing mode, the number of RBs of CORESET #0, the number of symbols of CORESET #0, and the RB offset of CORESET #0.

[0263] In an example, pdcch-ConfigSIB1 may include a common search space of a second parameter (e.g., searchSpaceZero) having an ID #0 (e.g., SS #0) of the initial BWP of the cell. searchSpaceZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify the configuration of SS #0. Figure 23C An example showing the configuration of SS #0. As Figure 23C shown, based on the integer value of searchSpaceZero, the wireless device may determine one or more parameters (e.g., O, M) for slot determination for PDCCH monitoring, the first symbol index for PDCCH monitoring, and / or the number of search spaces per slot.

[0264] In an example, based on receiving the MIB, the wireless device may monitor the PDCCH via SS #0 of CORESET #0 for receiving the DCI that schedules the System Information Block 1 (SIB1). The wireless device may receive a DCI having a CRC scrambled with a System Information Radio Network Temporary Identifier (SI-RNTI) dedicated to receiving SIB1.

[0265] Figure 24 An example showing the RRC configuration parameters of the System Information Block (SIB). The SIB (e.g., SIB1) may contain information relevant when evaluating whether to allow a wireless device to access the cell and may define the scheduling of other system information. The SIB may contain radio resource configuration information common to all wireless devices and prohibition information applied to unified access control. In an example, the base station may transmit one or more SIB information to the wireless device (or wireless devices). As Figure 24As shown, the parameters of one or more SIB information may include: one or more parameters related to cell selection of the serving cell (e.g., cellSelectionInfo), one or more configuration parameters of the serving cell (e.g., represented by the ServingCellConfigCommonSIB IE), and one or more other parameters. The ServingCellConfigCommonSIB IE may include at least one of the following: common downlink parameters of the serving cell (e.g., represented by the DownlinkConfigCommonSIB IE), common uplink parameters of the serving cell (e.g., represented by the UplinkConfigCommonSIB IE), and other parameters.

[0266] In an example, the DownlinkConfigCommonSIB IE may include parameters of the initial downlink BWP of the serving cell (e.g., SpCell). The parameters of the initial downlink BWP may be included in the BWP-DownlinkCommon IE (as Figure 25 shown). The BWP-DownlinkCommon IE can be used to configure the common parameters of the downlink BWP of the serving cell. The base station can configure the locationAndBandwidth such that the initial downlink BWP includes the entire CORESET#0 of the serving cell in the frequency domain. The wireless device can apply the locationAndBandwidth when receiving this field (e.g., determine the frequency position of the signal described by the locationAndBandwidth), but it retains the CORESET#0 until after receiving RRCSetup / RRCResume / RRCReestablishment.

[0267] In an example, the UplinkConfigCommonSIB IE may include parameters of the initial uplink BWP of the serving cell (e.g., SpCell). The parameters of the initial uplink BWP may be included in the BWP-UplinkCommon IE. The BWP-UplinkCommon IE can be used to configure the common parameters of the uplink BWP. The common parameters of the uplink BWP are "cell-specific". The base station can ensure the necessary alignment with the corresponding parameters of other wireless devices. The common parameters of the initial bandwidth part of the PCell can be provided via the system information. For all other serving cells, the base station can provide the common parameters via dedicated signaling.

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

[0269] As Figure 25As shown, a control resource set (CORESET) can be associated with a CORESET index (e.g., ControlResourceSetId). A CORESET index with a value of 0 can identify a common CORESET configured in the MIB and in ServingCellConfigCommon (controlResourceSetZero), and cannot be used in the ControlResourceSet IE. CORESET indexes with other values can identify CORESETs configured by dedicated signaling or in SIB1. The controlResourceSetId is unique among the BWPs of a serving cell. A CORESET can be associated with a coresetPoolIndex that indicates the index of the CORESET pool that indicates the CORESET. A CORESET can be associated with a duration parameter (e.g., duration), which indicates the continuous duration of the CORESET in terms of the number of symbols. In the example, as Figure 25 shown, the configuration parameters of a CORESET can include at least one of the following: frequency resource indication (e.g., frequencyDomainResources), CCE-REG mapping type indicator (e.g., cce-REG-MappingType), multiple TCI states, an indicator indicating whether there is a TCI in the DCI, etc. The frequency resource indication, which contains a number of bits (e.g., 45 bits), indicates the frequency domain resources, with each bit of the indication corresponding to a group of 6 RBs, where the grouping starts from the first RB group in the BWP of a cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit corresponds to the first RB group in the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to the bit belongs to the frequency domain resources of the CORESET. Bits corresponding to a group of RBs that are not fully contained in the BWP in which the CORESET is configured are set to zero.

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

[0271] In an exemplary embodiment, the base station may transmit or the wireless device may receive a transport block (TB) scheduled in a unicast transmission, a broadcast transmission, a multicast transmission, or a combination thereof. Figure 27A and Figure 27B Examples of unicast transmission, broadcast transmission, and multicast transmission are shown.

[0272] As Figure 27A shown, a first wireless device (e.g., WD1) may receive from the base station a transport block (TB) dedicated to the first wireless device and / or scheduled by a DCI with a first UE-specific RNTI (e.g., C-RNTI, CS-RNTI, MCS-C-RNTI, etc.). In Figure 27A the example shown, a second wireless device (e.g., WD2, WD3, WD4, etc.) may not receive the TB dedicated to the first wireless device because the second wireless device is not configured with the first UE-specific RNTI. In the example, the TB dedicated to a wireless device may be referred to as a unicast TB. The PDSCH carrying the TB dedicated to a wireless device may be referred to as a unicast PDSCH. The PDCCH (or DCI) scheduling the dedicated TB may be referred to as a unicast PDCCH (or unicast DCI). In the example, transmitting a TB to a wireless device and scheduling it with a unicast DCI may improve the security and flexibility of scheduling.

[0273] As Figure 27AAs shown, a wireless device can receive a multicast transport block (or groupcast transport block) of a multicast service (e.g., MBS) from a base station, and the multicast transport block can be received by a group of wireless devices (e.g., WD2, WD3, WD4, etc.) within the coverage of the base station. To receive the multicast transport block, the group of wireless devices can be allocated / configured with a group-specific radio network temporary identifier (e.g., G-RNTI or SC-RNTI, or MBS-RNTI). Based on the configured group-specific radio network temporary identifier, the group of wireless devices can monitor the physical downlink control channel (PDCCH) to receive a downlink control information (DCI) with a cyclic redundancy check (CRC) scrambled by the group-specific radio network temporary identifier, and the DCI schedules the multicast transport block. In an example, a wireless device (e.g., WD1) not configured with a group-specific radio network temporary identifier may not receive the multicast transport block. In an example, the MBS can carry application messages, including at least one of the following: V2X, public safety, live video (e.g., concert or sports), IoT software update, industrial applications, etc. An MBS carrying a type of application data can be defined as an MBS session. Different MBS sessions can be used for different applications. A wireless device interested in the MBS provided by the base station can indicate to the base station that the wireless device is interested in the MBS service. The base station can accordingly transmit MBS configuration parameters to the wireless device, and the parameters include a radio network temporary identifier dedicated to receiving the DCI scheduling the MBS transport block. By allocating a dedicated radio network temporary identifier to the wireless device receiving the MBS, the base station can know which wireless device or how many wireless devices have subscribed to the MBS. The MBS is different from a broadcast message, in which the base station does not know which wireless device or how many wireless devices are receiving the broadcast message. In an example, a network operator can determine an MBS transmission strategy or a price strategy based on the number of subscribers of the MBS by using multicast / groupcast scheduling.

[0274] As Figure 27B shown, a wireless device can receive a broadcast transport block from a base station, and the broadcast transport block can be received by any wireless device within the coverage of the base station. The broadcast transport block can include a system information message, a paging information message, etc. In an example, when receiving broadcast system information or paging information, any wireless device in the cell can monitor the PDCCH to receive a DCI with a CRC scrambled by a predefined radio network temporary identifier (e.g., SI-RNTI with a predefined value of "FFFF" in hexadecimal, or P-RNTI with a predefined value of "FFFE" in hexadecimal, etc.). Since the radio network temporary identifier for receiving the DCI scheduling the broadcast message is known to any wireless device in the cell (e.g., by being set to a predefined value), any wireless device can receive the broadcast message. In an example, by transmitting system information or paging messages scheduled by a broadcast scheduling DCI to a group of wireless devices, the base station can improve the signaling efficiency of the base station.

[0275] In an exemplary embodiment, the base station may transmit an MBS TB and control signaling (e.g., DCI) associated with the MBS TB to a group of wireless devices via the group common frequency resources of multiple BWPs of a cell. The group common frequency resources may be configured as dedicated BWPs among the multiple BWPs of the cell. The group common frequency resources may be configured as multiple resource blocks within a BWP among the multiple BWPs of the cell. Figure 28A and Figure 28B illustrates an example of MBS configuration when multiple BWPs are configured in a cell.

[0276] As Figure 28A shown, the BWP for transmitting the MBS TB (e.g., which may be referred to as the MBS BWP in the present disclosure) may be configured separately and / or independently from the BWP for transmitting unicast TBs and / or broadcast TBs (e.g., which may be referred to as the unicast BWP in the present disclosure). The MBS BWP in this specification may be defined as the BWP of a cell on which the MBS PDCCH / PDSCH can be transmitted. The unicast BWP in the present disclosure may be defined as the BWP of a cell on which the unicast PDCCH / PDSCH (and / or broadcast PDCCH / PDSCH) can be transmitted. The MBS BWP may be associated with the unicast BWP. The association between the MBS BWP and the unicast BWP may be indicated by the base station and / or RRC message as the MBS BWP having the same parameter set as the unicast BWP.

[0277] In an exemplary embodiment, the base station may transmit one or more RRC messages including the configuration parameters of a cell to a wireless device, where the cell includes multiple BWPs. The one or more RRC messages may indicate that a first set of the multiple BWPs is dedicated for unicast BWPs (e.g., BWP n, BWP m, etc., for unicast PDCCH / PDSCH transmission, or broadcast system information transmission, or broadcast paging message transmission). In an example, the one or more RRC messages may indicate that a second set of the multiple BWPs is dedicated for MBS BWPs (e.g., BWP x, BWP y, etc., for MBS PDCCH / PDSCH transmission). In an embodiment, different MBSS (e.g., V2X, public safety, live video, IOT software update, industrial applications, etc.) targeted at different groups of wireless devices may be configured on different BWPs. The MBS BWP may be used to transmit different MBS TBs associated with different MBS configurations (e.g., V2X, public safety, live video, IOT software update, industrial applications, etc.). In an example, configuring a separate BWP for MBS from the unicast BWP may improve system throughput and reduce the scheduling limitations / impacts on unicast PDSCH scheduling. In an embodiment, to support configuring a separate BWP for MBS, it may be necessary for the wireless device to support multiple active BWPs in the cell.

[0278] As Figure 28B shown, the frequency resources for transmitting MBS TBs can be configured within the BWP for transmitting unicast TBs and / or broadcast TBs. The frequency resources configured for MBS configuration / session in the BWP can be resource blocks that are common to a set of wireless devices configured with the MBS configuration / session. The BWP can be the initial BWP of the cell or the first active BWP configured on the cell. The BWP can be any BWP except the dormant BWP of the cell. In an embodiment, multiple resource blocks within the unicast BWP can be dedicated to transmitting MBS PDCCH / PDSCH to a set of wireless devices. In an example, the number of resource blocks (or a set of resource blocks) and the position of that number of resource blocks within the BWP can be configured by the base station in one or more RRC messages. One or more RRC messages can further indicate the configuration parameters of the PDCCH for MBS (e.g., referred to as MBS PDCCH), where the MBS PDCCH can carry DCI with a CRC scrambled by an MBS-specific RNTI (e.g., MBS-RNTI, SC-RNTI, G-RNTI, etc.). The configuration parameters can indicate the frequency resource allocation and time domain allocation of the search space and / or CORESET for receiving the MBS PDCCH within the bandwidth of the unicast BWP. In an example, the frequency resource allocation and time domain allocation of the search space and / or CORESET can be implemented based on Figure 25 and / or Figure 26 the examples of

[0279] In an exemplary embodiment, different MBSs targeted at different groups of wireless devices can be configured on different sets of resource blocks within the unicast BWP. As Figure 28B shown, the resource blocks of the MBS can be allocated on different unicast BWPs. In an example, configuring the frequency resources for the MBS within the unicast BWP can simplify the implementation of the wireless device and reduce the power consumption of the wireless device. In an example, by supporting the configuration of the frequency resources for the MBS within the unicast BWP, it can be required that the wireless device supports a single active BWP in the cell.

[0280] In an exemplary embodiment, DRX operation can be used by a wireless device to improve the battery life of the wireless device. In the case where DRX is configured, the wireless device can discontinuously monitor the downlink control channel, e.g., PDCCH or enhanced PDCCH (EPDCCH). The base station can configure the DRX operation with a set of DRX parameters (e.g., using RRC configuration). The DRX parameter set can be selected based on the application type so that the wireless device can reduce power and resource consumption. In response to DRX being configured / activated, the wireless device can receive data packets with extended latency since the wireless device can be in the DRX sleep / off state when the data arrives at the wireless device, and the base station can wait until the wireless device transitions to the DRX on state.

[0281] In an exemplary embodiment, during the DRX mode, when there are no packets to receive, the wireless device can turn off most of its circuitry. The wireless device can discontinuously monitor the PDCCH in the DRX mode. When DRX operation is not configured, the wireless device can continuously monitor the PDCCH. During this period, the wireless device listens for the downlink (DL) (or monitors the PDCCH) which is referred to as the DRX active state. In the DRX mode, the time when the wireless device does not listen / monitor the PDCCH is referred to as the DRX sleep state.

[0282] Figure 29 An example of an embodiment is shown. The base station can transmit an RRC message including one or more DRX parameters including a DRX cycle. The one or more parameters can include a first parameter and / or a second parameter. The first parameter can indicate a first time / window value (e.g., DRX on duration timer) of the DRX active state of the DRX cycle (e.g., DRX on duration). The second parameter can indicate a second time (e.g., DRX off duration) of the DRX sleep state of the DRX cycle. The one or more parameters can additionally include the duration of the DRX cycle. During the DRX active state, the wireless device can monitor the PDCCH to detect one or more DCIs on the serving cell. During the DRX sleep state, the wireless device can stop monitoring the PDCCH on the serving cell. When multiple cells are active, the wireless device can monitor all PDCCHs on (or for) the multiple cells during the DRX active state. During the DRX off duration, the wireless device can stop monitoring all PDCCHs on (or for) the multiple cells. The wireless device can repeat the DRX operation according to the one or more DRX parameters.

[0283] In an exemplary embodiment, DRX may be beneficial to the base station. In an example, if DRX is not configured, the wireless device may transmit periodic CSI and / or SRS frequently (e.g., based on configuration). With DRX, during the DRX off period, the wireless device may not transmit periodic CSI and / or SRS. The base station may assign these resources to other UEs to improve resource utilization efficiency.

[0284] In an exemplary embodiment, the MAC entity may be configured by the RRC with DRX functionality that controls the activity of the wireless device's downlink control channel (e.g., PDCCH) monitoring for multiple RNTIs for the MAC entity. The multiple 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-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. In an example, in response to being in RRC_CONNECTED, if DRX is configured, the MAC entity may use DRX operation to discontinuously monitor the PDCCH; otherwise, the MAC entity may continuously monitor the PDCCH.

[0285] In an exemplary embodiment, the RRC may control DRX operation by configuring multiple timers. The multiple timers may include: DRX on-duration timer (e.g., drx-onDurationTimer); DRX inactivity timer (e.g., drx-InactivityTimer); downlink DRX HARQ round-trip time (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); one or more parameters of the short DRX configuration (e.g., drx-ShortCycle and / or drx-ShortCycleTimer) and one or more parameters of the long DRX configuration (e.g., drx-LongCycle). In an example, the time granularity of the DRX timers may be in PDCCH subframes (e.g., indicated as psf in the DRX configuration) or in milliseconds.

[0286] In an exemplary embodiment, in response to the DRX cycle being configured, the active time of the DRX operation may include the time when at least one timer is running. The at least one timer may include drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or mac-ContentionResolutionTimer. During the active timer of the DRX operation, the wireless device may monitor the PDCCH with an RNTI affected by the DRX operation. The RNTI may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and / or AI-RNTI.

[0287] In an exemplary embodiment, the drx-Inactivity-Timer may specify the duration for which the wireless device may be active after successfully decoding a PDCCH indicating a new transmission (UL or DL or SL). This timer may be restarted when a PDCCH for a new transmission (UL or DL or SL) is received. The wireless device may transition to the DRX mode (e.g., using a short DRX cycle or a long DRX cycle) in response to the expiration of this timer. In an example, drx-ShortCycle may be the first type of DRX cycle that the wireless device needs to follow when entering the DRX mode (e.g., if configured). In an example, the DRX-Config IE indicates the length of the short cycle. The drx-ShortCycleTimer may be expressed as a number of shortDRX-Cycles. The timer may indicate the number of initial DRX cycles to follow the short DRX cycle before entering the long DRX cycle. The drx-onDurationTimer may specify the duration at the start of the DRX cycle (e.g., DRX on). The drx-onDurationTimer may indicate the duration before entering the sleep mode (DRX off). The drx-HARQ-RTT-TimerDL may specify the minimum duration from when a new transmission is received and before the wireless device may expect a retransmission of the same packet. This timer may be fixed and may not be configured by RRC. The drx-RetransmissionTimerDL may indicate the maximum duration for which the wireless device may monitor the PDCCH when the wireless device expects a retransmission from the eNodeB.

[0288] In response to a DRX cycle being configured, the active time may include the time during which a scheduling request is sent on the PUCCH and is pending. In an example, in response to a DRX cycle being configured, the active time may include the time during which an uplink grant for a pending HARQ retransmission may occur and there is data in the corresponding HARQ buffer for synchronizing the HARQ process. In response to a DRX cycle being configured, the active time may include the time after receiving a random access response for a preamble not selected by the MAC entity successfully and before receiving a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity.

[0289] In an exemplary embodiment, the DL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) may expire in a subframe and the data of the corresponding HARQ process may not be decoded successfully. The MAC entity may start drx-RetransmissionTimerDL for the corresponding HARQ process. The UL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL) may expire in a subframe. The MAC entity may start drx-RetransmissionTimerUL for the corresponding HARQ process. A DRX command MAC control element or a long DRX command MAC control element may be received. The MAC entity may stop drx-onDurationTimer and stop drx-InactivityTimer. In an example, drx-InactivityTimer may expire, or a DRX command MAC control element may be received in a subframe. In an example, in response to a short DRX cycle being configured, the MAC entity may start or restart drx-ShortCycleTimer and may use the short DRX cycle. Otherwise, the MAC entity may use the long DRX cycle.

[0290] In an exemplary embodiment, drx-ShortCycleTimer may expire in a subframe. The MAC entity may use the long DRX cycle. In an example, a long DRX command MAC control element may be received. The MAC entity may stop drx-ShortCycleTimer and may use the long DRX cycle.

[0291] In an exemplary embodiment, if a short DRX cycle is used and [(SFN * 10) + subframe number] modulo (drx-ShortCycle) = (drxStartOffset) modulo (drx-ShortCycle), the wireless device may start the drx-onDurationTimer. In an example, if a long DRX cycle is used and [(SFN * 10) + subframe number] modulo (drx-longCycle) = drxStartOffset, the wireless device may start the drx-onDurationTimer.

[0292] Figure 30 An example of DRX operation is shown. The base station may transmit an RRC message including configuration parameters for DRX operation. The configuration parameters may include a first timer value for the DRX inactivity timer (e.g., drx-InactivityTimer), a second timer value for the HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL), and a third timer value for the HARQ retransmission timer (e.g., drx-RetransmissionTimerDL or drx-RetransmissionTimerUL).

[0293] As Figure 30 shown, the base station may transmit DCI (e.g., first DCI) including a downlink assignment of a TB to the wireless device via PDCCH. In response to receiving the DCI, the wireless device may start the drx-InactivityTimer. When the drx-InactivityTimer is running (e.g., during the period when the drx-InactivityTimer is running), the wireless device may monitor the PDCCH. The wireless device may receive the TB based on the received DCI. The wireless device may transmit a NACK to the base station when the TB is not successfully decoded. In the first symbol after the end of the NACK transmission, the wireless device may start the HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL). The wireless device may stop the drx-RetransmissionTimerDL for the HARQ process corresponding to the TB ( Figure 30(not shown). When the HARQ RTT timer is running, the wireless device may stop (or skip) monitoring the PDCCH for one or more RNTIs affected by DRX operation. The one or more RNTIs may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and / or AI-RNTI.

[0294] As Figure 30 shown, when the HARQ RTT timer expires, the wireless device may monitor the PDCCH and start the HARQ retransmission timer (e.g., drx-RetransmissionTimerDL). When the HARQ retransmission timer is running, the wireless device may receive a second DCI (e.g., Figure 30 the second DCI in ) that schedules a retransmission of the TB during PDCCH monitoring. If the second DCI is not received before the HARQ retransmission timer expires, the wireless device may stop monitoring the PDCCH.

[0295] Figure 31 shows an exemplary embodiment of the DRX configuration in a cell. In the example, the base station may configure the wireless device in the cell with two DRX configurations ( Figure 31 the unicast DRX and MBSDRX in ). These two DRX configurations may include a first DRX configuration that controls PDCCH monitoring for one or more first RNTIs associated with the unicast DRX, and a second DRX configuration that controls PDCCH monitoring for one or more second RNTIs associated with the MBSDRX.

[0296] In an exemplary embodiment, the base station may transmit the configuration parameters of the first DRX configuration to the wireless device ( Figure 31unicast DRX). The configuration parameter may include one or more of the following timer values: a first timer value of a DRX on-duration timer indicating a duration at the start of a DRX cycle (e.g., drx-onDurationTimer); a value of a DRX slot offset indicating a delay before starting the drx-onDurationTimer (e.g., drx-SlotOffset); a second timer value of a DRX inactivity timer indicating a duration after a PDCCH occasion in which the PDCCH indicates a new UL or DL transmission of a MAC entity of a wireless device; a third timer value of a DRX retransmission timer for DL transmissions indicating a (maximum) duration until a DL retransmission is received (e.g., drx-RetransmissionTimerDL) (in accordance with a DL HARQ process); a fourth timer value of a DRX retransmission timer for UL transmissions indicating a (maximum) duration until an authorization for a UL retransmission is received (e.g., drx-RetransmissionTimerUL) (in accordance with a UL HARQ process); a DRX long cycle and DRX start offset (e.g., drx-LongCycleStartOffset) indicating a long DRX cycle and a drx-StartOffset defining a subframe at which long and short DRX cycles start; a length of a short DRX cycle (e.g., drx-ShortCycle); a fifth timer value of a DRX short cycle timer indicating a duration during which a wireless device may follow a short DRX cycle (e.g., drx-ShortCycleTimer); a sixth timer value of a DRX HARQ RTT timer for DL transmissions indicating a (minimum) duration before a DL assignment for which a MAC entity expects a HARQ retransmission (e.g., drx-HARQ-RTT-TimerDL) (in accordance with a DL HARQ process); or a seventh timer value of a DRX HARQ RTT timer for UL transmissions indicating a (minimum) duration before a UL HARQ retransmission authorization for which a MAC entity expects (e.g., drx-HARQ-RTT-TimerUL) (in accordance with a UL HARQ process).

[0297] In an exemplary embodiment, one or more first RNTIs may include a C-RNTI, a CS-RNTI, and / or an SP-CSI-RNTI, which may be used to scramble unicast DCI that schedules a unicast PDSCH. The unicast DCI is addressed specifically to a wireless device. The unicast PDSCH is transmitted specifically to the wireless device. One or more first RNTIs may include a CI-RNTI, an INT-RNTI, an SFI-RNTI, a TPC-PUCCH-RNTI, a TPC-PUSCH-RNTI, a TPC-SRS-RNTI, and / or an AI-RNTI, for scrambling group common DCI that indicates group common control information. The group common DCI that indicates group common control information may not include a downlink assignment for downlink data packet transmission or an uplink grant for uplink data packet transmission. In an example, a group common DCI having a CRC scrambled by a CI-RNTI may indicate an uplink cancellation indication for a group of wireless devices. A group common DCI having a CRC scrambled by an INT-RNTI may indicate a downlink preemption indication for a group of wireless devices. A group common DCI having a CRC scrambled by an SFI-RNTI may indicate a slot format indication for a group of wireless devices. A group common DCI having a CRC scrambled by a TPC-PUCCH-RNTI, a TPC-PUSCH-RNTI, or a TPC-SRS-RNTI may indicate a power control command for PUCCH, PUSCH, or SRS transmission, respectively. A group common DCI having a CRC scrambled by an AI-RNTI may indicate an availability indication on a cell, etc. In an example, in the present disclosure, a first DRX configuration that controls PDCCH monitoring for one or more first RNTIs may be referred to as a DRX configuration for unicast transmission (or unicast DRX configuration). A wireless device may perform PDCCH monitoring according to the unicast DRX configuration based on the exemplary embodiments described above with respect to Figure 29 and / or Figure 30 The wireless device may monitor the PDCCH when a first DRX on-duration timer associated with the unicast DRX is running (or during the unicast DRX on-duration in Figure 31 ). When the first DRX on-duration timer expires (or during the unicast DRX off-duration in Figure 31 ), the wireless device may stop monitoring the PDCCH.

[0298] In an exemplary embodiment, a base station may transmit configuration parameters of a second DRX configuration to a wireless device (e.g., Figure 31in MBSDRX). The configuration parameters may include the timer value of the MBSDRX on-duration timer indicating the duration at the start of the DRX cycle (e.g., drx-onDurationTimer, onDurationTimerSCPTM, onDurationTimerMBS, etc.); the timer value of the MBSDRX inactivity timer indicating the duration after the PDCCH occasion, in which the PDCCH indicates a new UL or DL transmission of the MAC entity of the wireless device (e.g., drx-InactivityTimer, drx-InactivityTimerSCPTM, drx-InactivityTimerMBS, etc.); the MBSDRX long cycle and MBSDRX start offset (e.g., drx-LongCycleStartOffset) indicating the long MBS DRX cycle and the subframe defining the start of the long and short MBSDRX cycles; the length of the short MBSDRX cycle (e.g., drx-ShortCycle); the MBSDRX short cycle timer indicating the duration for which the wireless device can follow the short MBSDRX cycle (e.g., drx-ShortCycleTimer), etc. In an example, for MBSDRX configuration, the active time of MBSDRX may include the time during which the MBSDRX on-duration timer or the MBSDRX inactivity timer configured for MBSDRX is running. The wireless device may start the MBSDRX on-duration timer at the start of the DRX cycle configured for MBD DRX. The wireless device may monitor the PDCCH for the MBS dedicated RNTI during the active time of MBSDRX (or during the Figure 31 MBSDRX on-duration). In response to receiving DCI with the MBS dedicated RNTI, the wireless device may start or restart the MBSDRX inactivity timer configured for MBSDRX. When the MBSDRX on-duration timer of MBSDRX expires (or when in the Figure 31 MBSDRX off-duration), the wireless device may stop monitoring the PDCCH.

[0299] In an exemplary embodiment, one or more second RNTIs may include one or more RNTIs dedicated to MBS sessions (e.g., G-RNTI, SC-RNTI, MBS-RNTI, or generally MBS-dedicated RNTIs, which may be equivalently referred to in this disclosure). One or more second RNTIs may be configured separately and / or independently from one or more first RNTIs. The MBS-dedicated RNTI may be used for scrambling of multicast (or group common) DCI for scheduling MBS TB via multicast (or group common) PDSCH resources (e.g., based on the exemplary embodiments described above with respect to Figure 28A and / or Figure 28B . The multicast DCI is addressed to a group of wireless devices configured with the MBS-dedicated RNTI. The MBS TB is transmitted to a group of wireless devices configured with the MBS-dedicated RNTI. In an example, in this disclosure, the second DRX configuration that controls the PDCCH monitoring for one or more second RNTIs may be referred to as the DRX configuration for MBS transmission (or MBS DRX configuration).

[0300] In an exemplary embodiment, a wireless device may perform unicast DRX operations and MBS DRX operations individually (and / or independently) or jointly.

[0301] In an exemplary embodiment, performing unicast DRX operations and MBS DRX operations individually may include starting a DRX timer (e.g., DRX on-duration timer, DRX inactivity timer, DRX retransmission timer) of the MBS DRX operation based on reception of DCI via an MBS PDCCH associated with an MBS of a group of wireless devices, rather than based on reception of DCI via a unicast PDCCH associated with the wireless device. Performing unicast DRX operations and MBS DRX operations individually may include starting a DRX timer (e.g., DRX on-duration timer, DRX inactivity timer, DRX retransmission timer) of the unicast DRX operation based on reception of DCI via a unicast PDCCH associated with the wireless device, rather than based on reception of DCI via an MBS PDCCH associated with the MBS of the group of wireless devices.

[0302] In an exemplary embodiment, jointly performing unicast DRX operations and MBS DRX operations may include starting a DRX timer (e.g., a DRX on-duration timer, a DRX inactivity timer, a DRX retransmission timer) of the MBS DRX operation based on receiving DCI via an MBS PDCCH associated with an MBS of a group of wireless devices, and / or based on receiving DCI via a unicast PDCCH associated with the wireless device. Jointly performing unicast DRX operations and MBS DRX operations may include starting a DRX timer (e.g., a DRX on-duration timer, a DRX inactivity timer, a DRX retransmission timer) of the unicast DRX operation based on receiving DCI via a unicast PDCCH associated with the wireless device, and / or based on receiving DCI via an MBS PDCCH associated with the MBS of the group of wireless devices.

[0303] In an exemplary embodiment, a base station and / or a wireless device may perform a PS operation based on a power saving (PS) indication (e.g., wake up, enter sleep, hibernate, search space switching, PDCCH skipping, etc.). The PS indication may be a signal sequence (e.g., a pseudo-random sequence or an SSB / CSI-RS / DMRS) or included in DCI (e.g., having a specific DCI format dedicated to the PS operation). The base station may transmit configuration parameters of the PS indication to the wireless device, and the configuration parameters include at least one of the following: a PS duration, at which time the PS indication may be received via a PS signal / channel; a PS signal / channel format (e.g., a sequence identifier / index, a parameter set, a DCI format, a PDCCH format); a periodicity of the PS signal / channel; a control resource set; and / or a search space of the PS channel. When configured with a parameter of the PS duration, the wireless device may monitor the PS signal / channel during the PS duration. In response to receiving the PS signal / channel during the PS duration, the wireless device may determine whether to wake up to monitor the PDCCH according to the DRX configuration.

[0304] In an example, in response to receiving a PS signal / channel including a wake-up indication (or a DRX on-duration timer start indication) of the wireless device, the wireless device may start a DRX on-duration timer (e.g., drx-onDurationTimer) configured by the DRX, and / or monitor the PDCCH while the DRX on-duration timer is running.

[0305] In an example, in response to receiving a PS signal / channel indicating an enter-sleep indication (or a DRX on-duration timer not-start indication), when the DRX on-duration timer is not running within a DRX cycle, the wireless device may not start a DRX on-duration timer of the DRX cycle configured according to the DRX and / or may skip monitoring the PDCCH.

[0306] In an example, in response to not receiving a PS signal / channel during a PS duration, a wireless device may determine whether to wake up or enter sleep during a DRX on-duration based on an indication from a base station. When the base station (via an RRC message) indicates that the wireless device wakes up during the DRX on-duration in response to not receiving a PS signal / channel, the wireless device may wake up during the DRX on-duration to perform PDCCH monitoring in response to not receiving a PS signal / channel during the PS duration. When the base station (via an RRC message) indicates that the wireless device skips the DRX on-duration (or does not wake up during the DRX on-duration) in response to not receiving a PS signal / channel, the wireless device may skip PDCCH monitoring during the DRX on-duration in response to not receiving a PS signal / channel during the PS duration.

[0307] In an example, a wireless device may perform a power saving (PS) operation on one or more cells based on receiving a power saving indication (e.g., a wake-up indication, a sleep indication, a hibernation indication, a search space switching indication, a stop indicator for PDCCH monitoring, etc.). The PS operation may include skipping / stopping PDCCH monitoring during a DRX on-duration, and / or at a monitoring skip period, on an active BWP of the cell. The PS operation may include switching from a first BWP of the cell to a second BWP of the cell as the active BWP of the cell. The second BWP may be a hibernation BWP or a non-hibernation BWP configured by the base station. The PS operation may include switching from a first search space to a second search space on an active BWP of the cell. The PS operation may include transitioning the cell to a hibernation state.

[0308] In an example, when a wireless device subscribes to an MBS session / configuration, in addition to receiving a unicast TB dedicated to the wireless device, the wireless device may also receive an MBS TB transmitted to a group of wireless devices including the wireless device. The MBS TB may be scheduled by a group common DCI addressed to the group of wireless devices configured with MBS. To save power consumption for PDCCH monitoring, the wireless device may be configured with two or more DRX configurations in a cell (or in an active BWP of the cell), including a first DRX configuration dedicated to unicast transmission and a second DRX configuration dedicated to the MBS session / configuration.

[0309] Based on the prior art, when MBSDRX and unicast DRX are configured in a cell, a wireless device may have difficulty determining a power saving operation on the cell when receiving a power saving indication. Based on the prior art, a base station may not know whether a wireless device is monitoring an MBS PDCCH to receive an MBS TB when a power saving operation is applied in the cell based on the received power saving indication. Existing power saving techniques may reduce the system throughput of MBS transmissions. Existing power saving techniques may increase the power consumption of receiving an MBS TB for an MBS configuration / session. Therefore, there is a need to improve the power saving operation for MBS transmissions.

[0310] In an exemplary embodiment, a wireless device may perform unicast DRX operations based on a power saving (PS) signal and MBSDRX operations based on the PS signal independently and / or separately on a cell (or an active BWP of the cell). The exemplary embodiment may reduce the implementation complexity of the wireless device. The exemplary embodiment may reduce the power consumption of the wireless device. The exemplary embodiment may improve the system throughput of MBS transmissions for a group of wireless devices.

[0311] In an exemplary embodiment, a base station may transmit a group common PS signal indicating the wake-up of a first group of wireless devices to monitor an MBS PDCCH to receive a group common DCI scheduling an MBS TB. The base station may transmit a second DCI including a plurality of PS signals to a second group of wireless devices to monitor a PDCCH to receive a DCI scheduling a unicast TB, each of the plurality of PS signals indicating the wake-up of a corresponding wireless device in the second group of wireless devices. The exemplary embodiment may improve the signaling overhead of PS signal transmission for an MBS configuration / session. The exemplary embodiment may improve the power consumption of the wireless device. The exemplary embodiment may improve the system throughput of MBS in a cell.

[0312] In an exemplary embodiment, a wireless device may perform a power saving operation for a unicast DRX operation in a cell and skip performing a power saving operation for an MBSDRX operation. The power saving operation for the unicast DRX operation may not affect the MBSDRX operation. When the wireless device has no unicast TB to receive, this embodiment may allow the wireless device to skip monitoring the unicast PDCCH during the DRX-on duration of the unicast DRX configuration to save power. When the wireless device is in a power saving mode associated with the power saving operation of the unicast DRX configuration, this embodiment may allow the wireless device to continue monitoring the MBS PDCCH during the DRX-on duration of the MBSDRX configuration. The exemplary embodiment may improve the system throughput of MBS transmissions.

[0313] In an exemplary embodiment, based on receiving a single PS signal, a wireless device may perform power saving operations for unicast DRX operation and for MBSDRX operation in a cell. The exemplary embodiment may improve the signaling overhead of PS signal transmission.

[0314] In an exemplary embodiment, based on the reception of a PS signal, a wireless device may monitor an MBS dedicated PDCCH and a unicast dedicated PDCCH according to the same DRX configuration. The base station may skip configuring MBS dedicated DRX for MBS transmission. The exemplary embodiment may improve the signaling overhead of the wireless device and / or reduce its implementation complexity. The exemplary embodiment may improve the power consumption of the wireless device.

[0315] In an exemplary embodiment, based on the reception of a signal sequence or RS, a wireless device may determine whether to wake up during the DRX-on duration of a PDCCH for monitoring a group common DCI dedicated to scheduling an MBS TB addressed to a group of wireless devices. The exemplary embodiment may improve the power consumption of the power saving signal for receiving MBS transmission.

[0316] Figure 32 An exemplary embodiment of DRX operation based on a PS signal for MBS transmission is shown. In the example, the base station may transmit one or more RRC messages to the wireless device, the RRC message including a first configuration parameter (e.g., MBSDRX) of an MBS DRX configuration associated with a first PS signal and a second configuration parameter (e.g., unicast DRX) of a unicast DRX configuration associated with a second PS signal. The MBSDRX configuration and the unicast DRX configuration may be in the same cell or in different cells. The MBSDRX configuration and the unicast DRX configuration may be in the same BWP of the cell or in different BWPs of the same cell. The MBSDRX configuration and the unicast DRX configuration may be implemented based on the exemplary embodiments described above with respect to Figure 31 are described.

[0317] In an exemplary embodiment, a first configuration parameter may be configured independently and separately from a second configuration parameter. The first configuration parameter may include: a first DRX on-duration timer indicating a duration at the start of a DRX cycle indicating MBS DRX configuration; a first DRX inactivity timer indicating a duration after a multicast PDCCH occasion in which the multicast PDCCH indicates a new DL transmission for a group of wireless devices (e.g., a multicast TB having a CRC scrambled with an MBS dedicated RNTI), etc. The first configuration parameter may further include a first DRX HARQ RTT timer (per DL MBS HARQ process) indicating a (minimum) duration before a DCI (e.g., via a multicast PDCCH and having a CRC scrambled with an MBS dedicated RNTI) that indicates a DL assignment for which the group of wireless devices expects a HARQ retransmission. The first configuration parameter may further include a first DRX retransmission timer (per DL MBS HARQ process) indicating a (maximum) duration until a DL retransmission of a multicast TB is received. The first configuration parameter may include a first DRX slot offset (e.g., drx-SlotOffset) of the MBS DRX configuration indicating a delay before starting the DRX on-duration timer, a first DRX long cycle parameter (e.g., drx-LongCycleStartOffset), a first DRX short cycle parameter (e.g., drx-ShortCycle, drx-ShortCycleTimer).

[0318] In an exemplary embodiment, a second configuration parameter (for unicast DRX configuration) may include a second DRX on-duration timer indicating a duration at the start of a DRX cycle indicating unicast DRX configuration, a second DRX inactivity timer indicating a duration after a unicast PDCCH occasion in which the unicast PDCCH indicates a new DL transmission for a wireless device (e.g., a unicast TB having a CRC scrambled with a C-RNTI, CS-RNTI, or MCS-C-RNTI). The second configuration parameter may further include a second DRX HARQ RTT timer (per DL unicast HARQ process) indicating a (minimum) duration before a DCI (e.g., via a unicast PDCCH and having a CRC scrambled with a C-RNTI, CS-RNTI, or MCS-C-RNTI) that indicates a DL assignment for which the wireless device expects a HARQ retransmission. The second configuration parameter may further include a second DRX retransmission timer (per DL unicast HARQ process) indicating a (maximum) duration until a DL retransmission of a unicast TB is received.

[0319] In an exemplary embodiment, a first DRX HARQ RTT timer (for MBS DRX configuration) may be configured with the same timer value or a different timer value as a second DRX HARQ RTT timer (for unicast DRX configuration). The second configuration parameter may include a second DRX slot offset (e.g., drx-SlotOffset) of the unicast DRX configuration indicating a delay before starting a second DRX on-duration timer, a second DRX long cycle parameter (e.g., drx-LongCycleStartOffset), and a second DRX short cycle parameter (e.g., drx-ShortCycle, drx-ShortCycleTimer).

[0320] In an exemplary embodiment, a first configuration parameter may include a configuration parameter of a first PS signal associated with an MBS DRX configuration. A second configuration parameter may include a configuration parameter of a second PS signal associated with a unicast DRX configuration. The configuration parameter of the first PS signal may be configured separately and / or independently from the configuration parameter of the second PS signal. The configuration parameter of the first PS signal and the configuration parameter of the second PS signal may be implemented based on Figure 33 the exemplary embodiment of

[0321] In an exemplary embodiment, a wireless device may perform PS operations for MBS DRX and unicast DRX separately and / or independently.

[0322] In an exemplary embodiment, a wireless device may monitor a first PDCCH (e.g., a group common PDCCH in an MBS dedicated common frequency resource) to receive a first PS signal. The first PS signal may be a DCI specifically indicating a PS operation. The first PS signal may be a DCI having a CRC scrambled with an RNTI dedicated to PS operations (e.g., MBS-PS-RNTI). The DCI specifically indicating a PS operation may be transmitted to a group of wireless devices configured with an MBS session / configuration.

[0323] As Figure 32As shown, in response to receiving a first PS signal indicating wake-up during a DRX on-duration (e.g., included in DCI) (e.g., when the first PS signal is set to a first value), a wireless device may start a first DRX on-duration timer associated with MBSDRX. Based on starting the first DRX on-duration timer, when the first DRX on-duration timer is running, the wireless device may determine that the wireless device is in the active time of MBSDRX. During the active time of MBSDRX, the wireless device may monitor the MBS PDCCH specifically configured for MBS. During the active time of MBSDRX, the wireless device may monitor the MBS PDCCH associated with a plurality of RNTIs, the plurality of RNTIs including at least one of the following: MBS-RNTI for DCI for receiving MBS TB; MBS CS-RNTI for DCI for activating / deactivating MBS SPS, etc. The wireless device may start or restart a first DRX inactive timer in response to receiving a DCI indicating a downlink assignment of a multicast PDSCH resource for transmission of MBS TB. When the first DRX on-duration timer expires (or when in the MBSDRX off-duration of an MBSDRX cycle), the wireless device may stop monitoring the MBS PDCCH.

[0324] As Figure 32 As shown, in response to receiving a first PS signal indicating sleep during a DRX on-duration (e.g., when the first PS signal is set to a second value), the wireless device may not start a first DRX on-duration timer associated with MBSDRX. Based on not starting the first DRX on-duration timer, the wireless device may determine that the wireless device is not in the active time of MBSDRX. Based on not starting the first DRX on-duration timer, the wireless device may skip monitoring the MBS PDCCH specifically configured for MBS during the DRX on-duration period (MBSDRX on-duration) of a DRX cycle associated with MBS.

[0325] In an exemplary embodiment, the RNTI of a PS indication (e.g., MBS-PS-RNTI) dedicated to MBSDRX configuration may be different from the MBS-RNTI dedicated to scheduling MBS TB. The base station may configure in an RRC message the RNTI of the PS indication dedicated to MBSDRX configuration and the RNTI dedicated to or scheduling MBS TB.

[0326] In an exemplary embodiment, the first configuration parameter may further include an indication indicating that the wireless device may wake up in response to not receiving the first PS signal (e.g., Figure 33(the first wake-up indication in ). In response to not receiving the first PS signal during monitoring of the first PDCCH and based on the first configuration parameter, the wireless device may start a first DRX on-duration timer associated with MBSDRX. Based on starting the first DRX on-duration timer, the wireless device may monitor the MBS dedicated PDCCH for DCI with an MBS dedicated RNTI for receiving the MBS TB during the DRX on-duration period (MBSDRX on-duration) of the DRX cycle associated with MBS.

[0327] In an exemplary embodiment, the first configuration parameter may further include an indication (e.g., Figure 33 (the first wake-up indication in ) indicating that the wireless device may enter sleep in response to not receiving the first PS signal. In response to not receiving the first PS signal during monitoring of the first PDCCH and based on the first configuration parameter, the wireless device may not start the first DRX on-duration timer associated with MBSDRX. Based on not starting the first DRX on-duration timer, the wireless device may skip monitoring the MBS dedicated PDCCH for DCI with an MBS dedicated RNTI for receiving the MBS TB during the DRX on-duration period (MBSDRX on-duration) of the DRX cycle associated with MBS.

[0328] In an exemplary embodiment, the first configuration parameter may not include an indication (e.g., Figure 33 (the first wake-up indication in ) indicating whether the wireless device may wake up or enter sleep in response to not receiving the first PS signal. By default, the wireless device may not wake up in response to not receiving the first PS signal during monitoring of the first PDCCH. By default, the wireless device may wake up in response to not receiving the first PS signal during monitoring of the first PDCCH. For the case where the wireless device does not receive the first PS signal during monitoring of the first PDCCH, a default behavior (e.g., wake up or enter sleep) may be predefined.

[0329] As Figure 32 shown, the wireless device may perform the PS operations of MBSDRX and unicast DRX separately and / or independently. In an exemplary embodiment, the wireless device may monitor a second PDCCH (e.g., the PDCCH in the unicast BWP) to receive a second PS signal. The second PS signal may be a DCI specifically indicating the PS operation. The second PS signal may be a DCI with a CRC scrambled by an RNTI (e.g., PS-RNTI) dedicated to the PS operation of the unicast BWP. The DCI specifically indicating the PS operation may be transmitted to a group of wireless devices configured with the PS operation.

[0330] In an exemplary embodiment, an RNTI (e.g., PS-RNTI) specifically configured for PS operation of a unicast BWP can be separate and independent from an RNTI (e.g., MBS-PS-RNTI) configured for PS operation of common frequency resources associated with MBS. The base station can indicate in an RRC message the RNTI for PS operation of the unicast DRX configuration dedicated to the unicast BWP and the RNTI for PS operation of the MBS DRX configuration dedicated to the common frequency resources.

[0331] As Figure 32 shown, in response to receiving a second PS signal (e.g., included in DCI) including a wake-up indication of a DRX-on duration (e.g., when the second PS signal is set to a first value), the wireless device can start a second DRX-on duration timer associated with the unicast DRX. Based on starting the second DRX-on duration timer, when the second DRX-on duration timer is running, the wireless device can determine that the wireless device is in the active time of the unicast DRX. During the active time of the unicast DRX, the wireless device can monitor the PDCCH according to the unicast DRX configuration. During the active time of the unicast DRX, the wireless device can monitor the PDCCH associated with multiple RNTIs, which includes at least one of the following: C-RNTI; CS-RNTI; MCS-C-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. The wireless device can start or restart a second DRX-inactive timer in response to receiving DCI indicating a downlink assignment of a unicast PDSCH resource for transmitting a unicast TB. When the second DRX-on duration timer expires (or when in the DRX-off duration of the unicast DRX cycle), the wireless device can stop monitoring the PDCCH.

[0332] As Figure 32 shown, in response to receiving a second PS signal (e.g., when the second PS signal is set to a second value) including a sleep indication of a DRX-on duration, the wireless device can not start a second DRX-on duration timer associated with the unicast DRX. Based on not starting the second DRX-on duration timer, the wireless device can determine that the wireless device is not in the active time of the unicast DRX. Based on not starting the second DRX-on duration timer, the wireless device can skip monitoring the PDCCH during the DRX-on duration period of the unicast DRX cycle.

[0333] In an exemplary embodiment, the second configuration parameter may further include an indication that the wireless device may wake up in response to not receiving a second PS signal during monitoring of the second PDCCH (e.g., ​ the second wake-up indication in ). In response to not receiving the second PS signal during monitoring of the first PDCCH and based on the second configuration parameter, the wireless device may start a second DRX-on duration timer associated with unicast DRX. Based on starting the second DRX-on duration timer, the wireless device may monitor the PDCCH during a DRX-on duration period (unicast DRX-on duration) of a DRX cycle associated with unicast DRX. The wireless device may monitor the PDCCH associated with a plurality of RNTIs, the plurality of RNTIs including at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. Monitoring the PDCCH associated with an RNTI may include attempting to decode (or receive) DCI having a CRC scrambled by the RNTI in a PDCCH monitoring occasion.

[0334] In an exemplary embodiment, the second configuration parameter may further include an indication that the wireless device may not wake up (or may enter a sleep state) in response to not receiving a second PS signal during monitoring of the second PDCCH (e.g., ​ the second wake-up indication in ). In response to not receiving the second PS signal during monitoring of the first PDCCH and based on the second configuration parameter, the wireless device may not start a second DRX-on duration timer associated with unicast DRX. Based on not starting the second DRX-on duration timer, the wireless device may skip monitoring the PDCCH during a DRX-on duration period (unicast DRX-on duration) of a DRX cycle associated with unicast DRX. The wireless device may skip monitoring the PDCCH associated with a plurality of RNTIs, the plurality of RNTIs including at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI.

[0335] In an exemplary embodiment, the second configuration parameter may not include an indication of whether the wireless device can wake up or go to sleep in response to not receiving the second PS signal (e.g., ​ the second wake-up indication in

[0336] ). By default, the wireless device may not wake up in response to not receiving the second PS signal during monitoring of the second PDCCH. By default, the wireless device may wake up in response to not receiving the second PS signal during monitoring of the second PDCCH. For the case where the wireless device does not receive the second PS signal during monitoring of the second PDCCH, a default behavior (e.g., wake up or go to sleep) may be predefined. ​ Exemplary embodiments based on this can reduce the implementation complexity of the wireless device. Exemplary embodiments can reduce the power consumption of the wireless device. Exemplary embodiments can improve the system throughput of MBS transmissions for a group of wireless devices.

[0337] ​ Exemplary embodiments showing power-saving indications for PDCCH monitoring of a cell (or the active BWP of a cell). The PDCCH may include a (unicast) PDCCH associated with a unicast BWP configured for a specific wireless device, and the (unicast) PDCCH may be associated with a first plurality of RNTIs including: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. The PDCCH may include an MBS PDCCH associated with a common frequency resource of an MBS configuration / session of a group of wireless devices, and the MBS PDCCH may be associated with a second plurality of RNTIs including at least one of the following: MBS-RNTI for DCI for receiving an MBS TB; MBS CS-RNTI for DCI for activating / deactivating MBSSPS. The first plurality of RNTIs may be configured separately and independently from the second plurality of RNTIs.

[0338] In an exemplary embodiment, the base station may transmit an RRC message to the wireless device, and the RRC message includes a first PS signal associated with MBS transmission ( ​Configuration parameters of the first PS signal in [ ]. The configuration parameters of the first PS signal may include at least one of the following: the first RNTI for receiving the first DCI including the first PS signal; the first time offset of the starting symbol / slot relative to the MBSDRX on-duration period for receiving the first DCI; the PS indication indicating whether to wake up if the first DCI is received; the first wake-up indication indicating whether to wake up if the first DCI is not detected; the time period for skipping MBS PDCCH monitoring (e.g., within the DRX on-duration of MBSDRX); the first reporting indication indicating whether to transmit a CSI report when the first DRX on-duration timer of MBSDRX is not started, etc. The configuration parameters of the first PS signal may not include the position parameter indicating the position of the PS signal associated with a specific wireless device in the first DCI. The configuration parameters of the first PS signal may not include the DCI size indication of the first DCI. The wireless device may monitor the group common PDCCH for receiving the first DCI including the first PS signal based on the configuration of the first PS signal, e.g., based on the exemplary embodiments described above with respect to ​ the described exemplary embodiments, to monitor the group common PDCCH for receiving the first DCI including the first PS signal.

[0339] In an exemplary embodiment, the first DCI may be associated with a DCI format that includes at least one of the following: the PS indication indicating whether to wake up within the group common (e.g., MBS) DRX on-duration and / or the value of the PDCCH skip period. The DCI format of the first DCI may be different from that of the second DCI. The DCI format associated with the second DCI may include multiple power saving blocks. The blocks in the multiple power saving blocks in the second DCI associated with the respective wireless devices in a group of wireless devices may include at least one of the following: the wake-up indication of the wireless device; and the sub-block including the SCell sleep indication of the wireless device. The wireless device-specific wake-up indication may not be configured (or may not exist) in the first DCI. The wireless device-specific SCell sleep indication may not be configured (or may not exist) in the first DCI.

[0340] In an exemplary embodiment, for each wireless device in a group of wireless devices configured with an MBS configuration / session, in response to receiving a PS signal indicating to wake up within the DRX on-duration configured by MBSDRX, the wireless device may wake up to monitor the MBS PDCCH to receive the group common DCI scheduling the MBS TB. Based on the group common PS signal addressed to a group of wireless devices, the base station may indicate to the group of wireless devices whether to wake up within the DRX on-duration or skip the DRX on-duration.

[0341] In an exemplary embodiment, a base station may transmit an RRC message to a wireless device, the RRC message including configuration parameters of a second PS signal ( ​ the second PS signal in ​ ) associated with unicast transmission. The configuration parameters of the second PS signal may include at least one of the following: a second RNTI for receiving a second DCI including the second PS signal dedicated to the wireless device; a second time offset from the start symbol / slot of the unicast DRX on-duration period for receiving the second DCI; a DCI size indication of the second DCI including the second PS signal; a position parameter indicating the position of the second PS signal associated with the wireless device in the second DCI; a second wake-up indication indicating whether to wake up if the second DCI is not detected; a second reporting indication indicating whether to transmit a CSI report when the second DRX on-duration timer of the unicast DRX is not started, etc.

[0342] In an exemplary embodiment, the second DCI may include a plurality of PS signals, each PS signal associated with a specific wireless device and indicating whether the specific wireless device wakes up or goes to sleep. The configuration parameters of the second PS signal may include a position parameter indicating the position of the second PS signal associated with the specific wireless device in the second DCI. The wireless device may monitor a group common PDCCH for receiving the second DCI including the second PS signal based on the configuration of the second PS signal. The wireless device may receive the second DCI. In response to the second PS signal associated with the wireless device in the second DCI indicating wake-up, the wireless device may wake up to monitor the PDCCH during the DRX on-duration of the unicast DRX. In response to receiving the second DCI, different wireless devices associated with different PS signals in the second DCI may respectively determine whether to wake up or go to sleep.

[0343] In an exemplary embodiment, for an MBSDRX configuration, in response to receiving a group common PS signal in a first group common DCI, a group of wireless devices may wake up or sleep during the DRX on-duration of the MBSDRX configuration. For a unicast DRX configuration, in response to receiving a wireless device-specific PS signal in a second group common DCI including a plurality of PS signals, the wireless device may wake up or sleep during the DRX on-duration of the unicast DRX configuration.

[0344] In an example, the first group common DCI may be transmitted in an SS / CORESET different from the second group common DCI. The first group common DCI may be associated with a DCI format different from the second group common DCI. The first group common DCI may include a single PS signal applicable to the group of wireless devices. The second group common DCI may include a plurality of PS signals, each PS signal corresponding to a respective wireless device in a group of wireless devices.

[0345] In an example, the first set of common DCI may be transmitted in the same SS / CORESET as the second set of common DCI. The first set of common DCI may be associated with the same DCI format as the second set of common DCI.

[0346] Based on ​ and / or ​ the exemplary embodiments, the base station may transmit a group common PS signal (e.g., via the first DC) indicating the wake-up of the first set of wireless devices to monitor the MBS PDCCH to receive the group common DCI scheduling the MBSTB to the first set of wireless devices. The base station may transmit a second DCI including a plurality of PS signals to the second set of wireless devices to monitor the PDCCH to receive the DCI scheduling the unicast TB, and each of the plurality of PS signals indicates the wake-up of the corresponding wireless device in the second set of wireless devices. The exemplary embodiments may improve the signaling overhead of the PS signal transmission for the MBS configuration / session. The exemplary embodiments may improve the power consumption of the wireless devices. The exemplary embodiments may increase the system throughput of the MBS in the cell.

[0347] ​ is an exemplary flowchart of a method for performing PS signal-based DRX operations for MBS transmission according to some embodiments. In an example, the base station may transmit one or more RRC messages to the wireless device, and the RRC messages include the first configuration parameter of the first PS signal for the group common transmission (e.g., MBS transmission) and the second configuration parameter of the second PS signal for the unicast transmission. The first PS signal may be associated with the MBSDRX configuration (e.g., MBSDRX). The second PS signal may be associated with the unicast DRX configuration (e.g., unicast DRX). The MBSDRX configuration and the unicast DRX configuration may be in the same cell or in different cells.

[0348] In an exemplary embodiment, the first configuration parameter of the first PS signal may be configured independently and separately from the second configuration parameter of the second PS signal. The MBSDRX configuration and the unicast DRX configuration may be implemented based on the exemplary embodiments described above with respect to ​ description.

[0349] In an exemplary embodiment, the first configuration parameter may include the configuration parameter of the first PS signal associated with the MBSDRX configuration. The second configuration parameter may include the configuration parameter of the second PS signal associated with the unicast DRX configuration. The configuration parameter of the first PS signal may be configured separately and / or independently from the configuration parameter of the second PS signal. The configuration parameter of the first PS signal and the configuration parameter of the second PS signal may be based on ​It can be implemented by the exemplary embodiments. The first configuration parameter of the first PS signal may include the first SS / CORESET in the cell for receiving the first PS signal. The second configuration parameter of the second PS signal may include the second SS / CORESET in the cell for receiving the second PS signal.

[0350] In an exemplary embodiment, the wireless device may perform PS operations for MBSDRX and unicast DRX separately and / or independently. The wireless device may monitor the PDCCH to receive the first PS signal and / or the second PS signal.

[0351] In an exemplary embodiment, the wireless device may monitor a first PDCCH (e.g., a group common PDCCH in the MBS dedicated common frequency resource) via the first SS / CORESET to receive the first PS signal. The first PS signal may be a DCI that specifically indicates a PS operation. The first PS signal may be a DCI having a CRC scrambled by an RNTI dedicated to the PS operation (e.g., MBS-PS-RNTI). The DCI that specifically indicates a PS operation may be transmitted to a group of wireless devices configured with an MBS session / configuration.

[0352] As ​ shown, in response to receiving a first PS signal indicating a power saving indication (e.g., a sleep indication, a DRX on-duration timer not started indication, a dormant indication, a search space switching indication, a PDCCH monitoring skip indication, etc.), the wireless device may perform a first power saving operation configured for MBSDRX. The first power saving operation may include at least one of the following: skipping MBS PDCCH monitoring (for a first plurality of RNTIs according to the MBS DRX configuration) during the DRX on-duration configured for MBSDRX; not starting the first DRX on-duration timer configured for MBSDRX; switching the active BWP to the dormant BWP of the cell; deactivating the Scell; switching from the first search space to the second search space for PDCCH monitoring. In response to receiving a first PS signal that does not indicate a power saving indication (e.g., including a wake-up indication, a DRX on-duration timer start indication, a non-dormant indication, etc.), the wireless device may switch from the first power saving operation to a non-PS operation configured for MBSDRX. The non-PS operation may include at least one of the following: monitoring the MBS PDCCH (for a first plurality of RNTIs according to the MBSDRX configuration) during the DRX on-duration configured for MBSDRX; starting the first DRX on-duration timer configured for MBSDRX; switching from the dormant BWP of the cell to a non-dormant BWP, etc.

[0353] In an exemplary embodiment, a wireless device may monitor a second PDCCH (e.g., a PDCCH in a wireless device-specific BWP) via a second SS / CORESET to receive a second PS signal. The second PS signal may be DCI that specifically indicates PS operation. The second PS signal may be DCI having a CRC scrambled with an RNTI dedicated to PS operation (e.g., PS-RNTI). The DCI that specifically indicates PS operation may be transmitted to a group of wireless devices configured with PS operation.

[0354] As ​ shown, in response to receiving a second PS signal indicating a power saving indication (e.g., a sleep indication, a DRX-on duration timer not started indication, a hibernation indication, a search space switching indication, a PDCCH monitoring skip indication, etc.), the wireless device may perform a second power saving operation for unicast DRX configuration. The second power saving operation may include at least one of the following: skipping PDCCH monitoring (for a second plurality of RNTIs according to the unicast DRX configuration) during the DRX-on duration of the unicast DRX configuration; not starting the second DRX-on duration timer of the unicast DRX configuration; switching the active BWP to the hibernation BWP of the cell; deactivating the Scell; switching from a first search space to a second search space for PDCCH monitoring. In response to receiving a second PS signal that does not indicate a power saving indication (e.g., including a wake-up indication, a DRX-on duration timer start indication, a non-hibernation indication, etc.), the wireless device may switch from the second power saving operation to a non-PS operation of the unicast DRX configuration. The non-PS operation may include at least one of the following: monitoring the PDCCH (for a second plurality of RNTIs according to the unicast DRX configuration) during the DRX-on duration of the MBSDRX configuration; starting the second DRX-on duration timer of the unicast DRX configuration; switching from the hibernation BWP of the cell to a non-hibernation BWP, etc.

[0355] Based on the exemplary embodiment, the wireless device may perform a first PS operation of the MBSDRX configuration and a second PS operation of the unicast DRX operation independently and / or separately on a cell (or the active BWP of the cell). ​ The exemplary embodiment may reduce the implementation complexity of the wireless device. The exemplary embodiment may reduce the power consumption of the wireless device. The exemplary embodiment may improve the system throughput of MBS transmission for a group of wireless devices.

[0356] In an example, separate PS signals for configuring MBSDRX and unicast DRX may increase the signaling overhead of the base station.

[0357] ​An exemplary implementation of PS signal-based DRX operation for MBS transmission is shown. In the example, the base station may transmit one or more RRC messages to the wireless device, and the RRC message includes a first configuration parameter (e.g., MBSDRX) of the MBSDRX configuration associated with the PS signal and a second configuration parameter (e.g., unicast DRX) of the unicast DRX configuration. The MBSDRX configuration and the unicast DRX configuration may be in the same cell or in different cells. The PS signal associated with the unicast DRX configuration may not be applied to the MBSDRX configuration.

[0358] In an exemplary implementation, the first configuration parameter may be configured independently and separately from the second configuration parameter. The first configuration parameter (for the MBSDRX configuration) and the second configuration parameter (for the unicast DRX configuration) may be implemented based on the exemplary implementation described above with respect to ​ and / or ​ described exemplary implementation.

[0359] In an exemplary implementation, the first configuration parameter may not include the configuration parameter of the PS signal associated with the MBSDRX configuration. The second configuration parameter may include the configuration parameter of the PS signal associated with the unicast DRX configuration. The configuration parameter of the PS signal may be implemented based on the exemplary implementation described above with respect to ​ described.

[0360] In an exemplary implementation, the wireless device may not apply the PS operation based on the PS signal to the MBSDRX configuration, regardless of whether a PS signal indicating the PS operation is received.

[0361] In the example, based on the non-existence of the configuration parameter of the PS signal associated with the MBSDRX configuration in the RRC message of the MBSDRX configuration, the wireless device may not apply the PS operation based on the PS signal to the MBSDRX configuration. Based on the existence of the configuration parameter of the PS signal associated with the unicast DRX configuration in the RRC message of the unicast DRX configuration, the wireless device may apply the PS operation based on the PS signal to the unicast DRX configuration, and / or may not apply the PS operation based on the PS signal to the MBSDRX configuration.

[0362] As ​ shown, the wireless device may start a first DRX-on duration timer associated with MBSDRX based on the configuration parameter of the MBSDRX configuration. Based on the above with respect to ​In the described exemplary embodiment, the wireless device may start a first DRX on-duration timer associated with MBS DRX. Based on starting the first DRX on-duration timer, when the first DRX on-duration timer is running, the wireless device may determine that the wireless device is in the active time of MBS DRX. During the active time of MBS DRX, the wireless device may monitor the MBS PDCCH specifically configured for MBS. During the active time of MBS DRX, the wireless device may monitor the MBS PDCCH associated with multiple RNTIs, where the multiple RNTIs include at least one of the following: MBS-RNTI for DCI for receiving MBS TB; MBS CS-RNTI for DCI for activating / deactivating MBS SPS, etc. The wireless device may start or restart a first DRX inactivity timer in response to receiving a DCI indicating a downlink assignment of a multicast PDSCH resource for the transmission of MBS TB. In response to the expiration of the first DRX on-duration timer, the wireless device may stop monitoring the MBS PDCCH. The wireless device performs DRX operations for each DRX cycle of the MBS DRX configuration.

[0363] As ​ shown, the wireless device may perform PS operations for unicast DRX based on the configuration parameters of the PS signal. The wireless device may perform PS operations for unicast DRX based on the exemplary embodiment described above with respect to ​ The PS operations for unicast DRX may not affect the operations on the MBS DRX configuration.

[0364] Based on ​ the exemplary embodiment, the wireless device may perform power saving operations for unicast DRX operations in the cell and skip performing power saving operations for MBS DRX operations. The power saving operations for unicast DRX operations may not affect the MBS DRX operations. When the wireless device has no unicast TB to receive, this embodiment may allow the wireless device to skip monitoring the unicast PDCCH during the DRX on-duration of the unicast DRX configuration to save power. When the wireless device is in a power saving mode associated with the power saving operations of the unicast DRX configuration, this embodiment may allow the wireless device to continue monitoring the MBS PDCCH during the DRX on-duration of the MBS DRX configuration. The exemplary embodiment may improve the system throughput of MBS transmissions.

[0365] Based on ​In an exemplary embodiment, the base station may transmit to the wireless device parameters indicating a first DRX configuration associated with unicast transmission on the cell and a second DRX configuration associated with multicast transmission. The base station may transmit to the wireless device a PS indication (e.g., in group common DCI or in UE-specific DCI) indicating the PS operation of the wireless device (e.g., entering sleep, skipping PDCCH monitoring, etc.). In response to transmitting the PS indication, the base station may skip transmitting the first PDCCH associated with unicast transmission to the wireless device during the first DRX on-duration of the first DRX configuration. For multicast transmission and regardless of the PS indication, the base station may transmit group common DCI to the wireless device via a second PDCCH associated with the multicast transmission during the second DRX on-duration of the second DRX configuration. Based on this exemplary embodiment, after transmitting the PS indication, skipping the transmission of the first PDCCH for unicast transmission may allow the base station to save downlink signaling and / or resources for downlink transmission to other wireless devices. Transmitting the group common DCI for multicast transmission by the base station to the wireless device may allow the base station to transmit the group common TB of the MBS session without interruption even when the wireless device is in a power saving mode (where the wireless device stops receiving unicast transmission). When the wireless device supports both unicast transmission and multicast transmission, the exemplary embodiment may improve the MBS throughput of the base station and / or the power consumption of the wireless device.

[0366] ​ An exemplary embodiment of PS-based DRX operation for MBS transmission is shown. In the example, the base station may transmit one or more RRC messages to the wireless device, the RRC message including a first configuration parameter (e.g., MBSDRX) of the MBSDRX configuration associated with the PS signal and a second configuration parameter (e.g., unicast DRX) of the unicast DRX configuration. The MBS DRX configuration and the unicast DRX configuration may be in the same cell or in different cells. The PS signal associated with the unicast DRX configuration may be applied to the MBSDRX configuration.

[0367] In an exemplary embodiment, the first configuration parameter may be configured independently and separately from the second configuration parameter. The first configuration parameter (for the MBSDRX configuration) and the second configuration parameter (for the unicast DRX configuration) may be implemented based on the exemplary embodiments described above with respect to ​ and / or ​ described exemplary embodiments.

[0368] In an exemplary embodiment, the first configuration parameter may not include a configuration parameter of the PS signal associated with the MBSDRX configuration. The second configuration parameter may include a configuration parameter of the PS signal associated with the unicast DRX configuration. The configuration parameter of the PS signal may be implemented based on the exemplary embodiments described above with respect to ​ described above.

[0369] In an exemplary embodiment, configuration parameters based on the PS signal associated with the unicast DRX configuration are present in the RRC message of the unicast DRX configuration, and the wireless device may apply the PS operation based on the PS signal to the unicast DRX configuration and / or may apply the PS operation based on the PS signal to the MBSDRX configuration.

[0370] In an exemplary embodiment, the wireless device may perform the PS operation of unicast DRX based on the configuration parameters of the PS signal. The wireless device may perform the PS operation of unicast DRX based on the exemplary embodiment described above with respect to ​ Upon performing the PS operation of unicast DRX, the wireless device may perform the PS operation of MBSDRX.

[0371] As ​ shown, in response to receiving a PS signal indicating wake-up, the wireless device may start a first DRX-on duration timer for MBSDRX and a second DRX-on duration timer for unicast DRX. Based on starting the first DRX-on duration timer, the wireless device may monitor the MBS dedicated PDCCH to receive the group common DCI scheduling the MBS TB. Based on starting the second DRX-on duration timer, the wireless device may monitor the unicast PDCCH to receive the unicast DCI scheduling the wireless device-specific TB and / or the group common DCI of control information. When the first DRX-on duration timer expires (or when in the MBSDRX-off duration of the MBSDRX cycle), the wireless device may stop monitoring the MBS dedicated PDCCH. When the second DRX-on duration timer expires (or when in the unicast DRX-off duration of the MBSDRX cycle), the wireless device may stop monitoring the unicast PDCCH.

[0372] As Figure 36 shown, in response to receiving a PS signal indicating sleep, the wireless device may not start the first DRX-on duration timer for MBSDRX and may not start the second DRX-on duration timer for unicast DRX. Based on not starting the first DRX-on duration timer, the wireless device may skip monitoring the MBS dedicated PDCCH during the DRX-on duration of the MBSDRX cycle. Based on not starting the second DRX-on duration timer, the wireless device may skip monitoring the unicast PDCCH during the DRX-on duration of the unicast DRX cycle.

[0373] Based on Figure 36In an exemplary embodiment, based on receiving a single PS signal, a wireless device can perform power saving operations for unicast DRX operation and for MBSDRX operation in a cell. The exemplary embodiment can improve the signaling overhead of PS signal transmission.

[0374] In an exemplary embodiment, a base station can transmit an RRC message to a wireless device, the RRC message including a configuration parameter indicating whether power saving operation based on a PS signal is applicable to MBS. In response to the configuration parameter indicating that the power saving operation based on the PS signal is not applicable to MBS, the wireless device can skip performing the power saving operation for MBS based on the exemplary embodiment described above with respect to Figure 35 In response to the configuration parameter indicating that the power saving operation based on the PS signal is applicable to MBS, the wireless device can perform the power saving operation based on the exemplary embodiment described above with respect to Figure 36 described exemplary embodiments.

[0375] In an exemplary embodiment, a wireless device can determine whether a power saving operation based on a PS signal is applicable to MBS (e.g., based on a predefined rule).

[0376] In an exemplary embodiment, a wireless device can defaultly (e.g., without configuration from the base station) determine that the power saving operation based on the PS signal is not applicable to MBS. In response to determining that the power saving operation based on the PS signal is not applicable to MBS, the wireless device can skip performing the power saving operation for MBS based on the exemplary embodiment described above with respect to Figure 35 described exemplary embodiments.

[0377] In an exemplary embodiment, a wireless device can defaultly (without configuration from the base station) determine that the power saving operation based on the PS signal is applicable to MBS. In response to determining that the power saving operation based on the PS signal is applicable to MBS, the wireless device can perform the power saving operation based on the exemplary embodiment described above with respect to Figure 36 described exemplary embodiments.

[0378] Figure 37 An exemplary embodiment of PS-based DRX operation for MBS transmission is shown. In the example, a base station can transmit one or more RRC messages to a wireless device, the RRC message being configuration parameters of a DRX configuration associated with a PS signal. The wireless device can monitor the MBS PDCCH of the MBS transmission according to the same DRX configuration of the unicast transmission.

[0379] In an exemplary embodiment, configuration parameters (for DRX configuration) may include a DRX on-duration timer indicating a duration at the start of a DRX cycle applicable to MBS transmissions and unicast transmissions, a DRX inactivity timer indicating a duration after a PDCCH occasion in which the PDCCH indicates a new DL transmission for the wireless device. The configuration parameters may further include a DRX HARQ RTT timer (per DL HARQ process) indicating a (minimum) duration before a DCI that indicates a DL assignment for which the wireless device expects a HARQ retransmission. The configuration parameters may also include a DRX retransmission timer (per DL HARQ process) indicating a (maximum) duration until a DL retransmission of a TB is received. The configuration parameters may include a DRX slot offset (e.g., drx-SlotOffset) of a DRX configuration indicating a delay before starting the DRX on-duration timer, DRX long cycle parameters (e.g., drx-LongCycleStartOffset), DRX short cycle parameters (e.g., drx-ShortCycle, drx-ShortCycleTimer).

[0380] In an exemplary embodiment, a wireless device may monitor a PDCCH (e.g., a group common PDCCH in an active BWP) to receive a PS signal. The PS signal may be a DCI specifically indicating PS operation. The PS signal may be a DCI having a CRC scrambled with an RNTI dedicated to PS operation (e.g., PS-RNTI). The DCI specifically indicating PS operation may be transmitted to a group of wireless devices configured with the PS-RNTI.

[0381] As Figure 37 shown, in response to receiving a PS signal (e.g., included in a DCI) indicating wake-up during the DRX on-duration (e.g., when a first PS signal is set to a first value), the wireless device may start a DRX on-duration timer associated with DRX. Based on starting the DRX on-duration timer, when the DRX on-duration timer is running, the wireless device may determine that the wireless device is in the active time of DRX. During the active time of DRX, the wireless device may monitor a first PDCCH and a second PDCCH. During the active time of DRX, the wireless device may monitor a first PDCCH associated with a first plurality of RNTIs (e.g., Figure 37in the unicast PDCCH), the first plurality of RNTIs includes at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. During the active time of DRX, the wireless device may monitor a second PDCCH associated with a second plurality of RNTIs (e.g., Figure 37 the MBS PDCCH in), the second plurality of RNTIs includes at least one of the following: MBS-RNTI for receiving DCI of the MBS TB; MBS CS-RNTI for DCI for activating / deactivating MBS SPS, etc. The wireless device may start or restart the DRX inactivity timer in response to receiving a DCI that indicates a downlink assignment of a PDSCH resource (e.g., a unicast PDSCH resource or an MBS PDSCH resource) that transmits a TB (e.g., a unicast TB or an MBS TB). When the DRX on-duration timer expires (or when in the DRX off-duration of the DRX cycle), the wireless device may stop monitoring the MBS PDCCH and the unicast PDCCH.

[0382] As Figure 37 shown, in response to receiving a PS signal indicating to enter sleep during the DRX on-duration (e.g., when the PS signal is set to a second value), the wireless device may not start the DRX on-duration timer associated with DRX. Based on not starting the DRX on-duration timer, the wireless device may determine that the wireless device is not in the active time of DRX. Based on not starting the DRX on-duration timer, the wireless device may skip monitoring the unicast PDCCH and the MBS PDCCH during the DRX on-duration of the DRX cycle.

[0383] Based on Figure 37 the exemplary embodiment of, based on the reception of the PS signal, the wireless device may monitor the MBS dedicated PDCCH and the unicast dedicated PDCCH according to the same DRX configuration. The base station may skip configuring MBS dedicated DRX for MBS transmission. The exemplary embodiment may improve the signaling overhead of the wireless device and / or reduce its implementation complexity. The exemplary embodiment may improve the power consumption of the wireless device.

[0384] Figure 32 and / or Figure 34It can be enhanced to improve the power consumption of the PS signal for receiving MBS transmissions. The PS signal can be transmitted by the base station via the PDCCH with a signal sequence or reference signal different from the DCI.

[0385] In an exemplary embodiment, the base station can transmit a signal sequence to a group of wireless devices, and the signal sequence indicates to wake up during the DRX-on duration of the MBS DRX configuration. The signal sequence (e.g., Zadoff-Chu sequence) can be generated based on the MBS identifier (e.g., cell ID, MBS session ID, MBS-RNTI, etc.). The signal sequence can include one or more RSs, which include at least one of: CSI-RS, SSB, and / or DMRS. One or more RSs can be generated based on the MBS identifier. The signal sequence of the PS operation of the MBS DRX configuration associated with the wireless device in the RRC_CONNECTED state can be configured separately and independently from the signal sequence of the PS operation for paging the wireless device in the RRC idle state.

[0386] In an exemplary embodiment, the wake-up indication can be the CSI-RS configured by the base station for the PS operation associated with the MBS DRX. The base station can transmit an RRC message to the wireless device, and the RRC message includes the configuration parameters of the CSI-RS for the PS operation associated with the MBS DRX. The configuration parameters of the CSI-RS can include at least one of the following: periodicity and offset parameters; power offset value of the PDSCH RE to the CSI-RS RE; QCL-information of the CSI-RS; resource mapping indication; and / or scrambling ID indicating the MBS identifier.

[0387] In an exemplary embodiment, for the wake-up indication associated with the MBS DRX configuration, the wireless device can determine the RS sequence r(m) of the RS as where c(i) can be a pseudo-random sequence. The pseudo-random sequence generator can be initialized with at the start of each symbol, where is the slot number within the radio frame, l is the symbol number within the slot, and n ID is equal to the MBS identifier configured by the base station.

[0388] In an exemplary embodiment, a wireless device may detect a reference signal (RS) based on configuration parameters of the RS for packet switched (PS) operation. In response to detecting the RS, the wireless device may wake up within a DRX-on duration configured for MBSDRX. Based on waking up, the wireless device may start a DRX-on duration timer configured for MBSDRX. Based on waking up, the wireless device may monitor the MBS PDCCH to receive group common DCI for scheduling the transmission of an MBS transport block (TB) to a group of wireless devices. In response to not detecting the RS, the wireless device may go to sleep (or may not wake up) within the DRX-on duration configured for MBSDRX. Based on going to sleep, the wireless device may not start a DRX-on duration timer configured for MBSDRX. Based on going to sleep, the wireless device may skip monitoring the MBS PDCCH within the DRX-on duration configured for MBSDRX.

[0389] Based on an exemplary embodiment, based on the reception of a signal sequence or RS, a wireless device may determine whether to wake up within a DRX-on duration for monitoring a physical downlink control channel (PDCCH) for group common DCI dedicated to scheduling an MBS TB addressed to a group of wireless devices. The exemplary embodiment may improve the power consumption of a power saving signal for receiving MBS transmissions.

[0390] In an exemplary embodiment, a wireless device receives a plurality of DCI via a cell, including: a first DCI including a first wake-up indication associated with a first DRX configuration for an MBS transmission; and a second DCI including a second wake-up indication associated with a second DRX configuration for a unicast transmission. Based on the first wake-up indication, the wireless device performs a first power saving operation associated with the first DRX configuration on the cell to receive the MBS transmission. Based on the second wake-up indication, the wireless device performs a second power saving operation associated with the second DRX configuration on the cell to receive the unicast transmission.

[0391] In an exemplary embodiment, the first DCI is received together with a first radio network temporary identifier of the first wake-up indication. The wireless device receives the first DCI via a first downlink control channel in a first radio resource associated with the MBS transmission.

[0392] In an exemplary embodiment, the second DCI is received together with a second radio network temporary identifier of the second wake-up indication. The wireless device receives the second DCI via a second downlink control channel in a second radio resource associated with the unicast transmission.

[0393] In an exemplary embodiment, the first power saving operation includes, for MBS transmissions on a cell, prohibiting the start of the first DRX on-duration timer of the first DRX. The first power saving operation includes skipping the monitoring of the first downlink control channel for MBS transmissions on the cell during the first DRX on-duration of the second DRX, wherein the first downlink control channel is associated with a first plurality of radio network temporary identifiers.

[0394] In an exemplary embodiment, the second power saving operation includes, for unicast transmissions on a cell, prohibiting the start of the second DRX on-duration timer of the second DRX. The second power saving operation includes skipping the monitoring of the second downlink control channel for unicast transmissions on the cell during the second DRX on-duration of the second DRX, wherein the second downlink control channel is associated with a second plurality of radio network temporary identifiers.

[0395] In an exemplary embodiment, MBS transmissions include transport blocks scheduled by group common DCI and addressed to a group of wireless devices. Unicast transmissions include transport blocks scheduled by wireless device-specific DCI and addressed to a wireless device.

[0396] In an exemplary embodiment, a first wake-up indication is applied to a group of wireless devices configured for MBS transmissions. A second wake-up indication is applied specifically to a wireless device for unicast transmissions.

[0397] In an exemplary embodiment, a first DCI is associated with a first DCI format. A second DCI is associated with a second DCI format.

[0398] In an exemplary embodiment, a wireless device receives one or more RRC messages including a first configuration parameter of a first wake-up indication and a second configuration parameter of a second wake-up indication.

[0399] In an exemplary embodiment, one or more RRC messages indicate a plurality of group common resources associated with MBS transmissions of a group of wireless devices including the wireless device and a plurality of wireless device-specific resources associated with the wireless device.

[0400] In an exemplary embodiment, a group common resource among the plurality of group common resources is associated with: a plurality of frequency resource blocks, a plurality of time slots, a plurality of demodulation reference signal antenna ports, and a TCI state indication.

[0401] In an exemplary embodiment, a wireless device-specific resource among the plurality of wireless device-specific resources is associated with: the number of frequency resource blocks, a plurality of time slots, a plurality of demodulation reference signal antenna ports, and a TCI state indication.

[0402] In an exemplary embodiment, a wireless device receives a first DCI via one or more group common resources associated with MBS transmissions. The wireless device receives a second DCI via one or more wireless device-specific resources among a plurality of wireless device-specific resources.

[0403] In an exemplary embodiment, in response to a first wake-up indication being set to a first value, the wireless device performs a first power-saving operation. In response to a second wake-up indication being set to the first value, the wireless device performs a second power-saving operation.

Claims

1. A wireless device, the wireless device comprising: One or more processors; And A memory storing instructions which, when executed by the one or more processors, cause the wireless device to: Receive parameters, the parameters including: A first discontinuous reception (DRX) configuration, the first DRX configuration indicating a first DRX on-duration timer value associated with unicast transmissions in a cell; and A second DRX configuration, the second DRX configuration indicating a second DRX on-duration timer value associated with multicast and broadcast services (MBS) in the cell; and Receive a power saving (PS) indication; After receiving the PS indication, based on receiving the PS indication, skip monitoring a first physical downlink control channel (PDCCH) for the unicast transmission during a first DRX on-duration of the first DRX configuration; and During a second DRX on-duration of the second DRX configuration and while skipping monitoring the first PDCCH during the first DRX on-duration, monitor a second PDCCH for the MBS.

2. The wireless device according to claim 1, wherein the first DRX configuration of the unicast transmission and the second DRX configuration of the MBS are in the same bandwidth part in a cell including a plurality of bandwidth parts.

3. The wireless device according to claim 1, wherein receiving the parameters includes receiving one or more radio resource control (RRC) messages including the parameters.

4. The wireless device according to claim 1, wherein the parameters further include a first radio network temporary identifier (RNTI) for unicast transmission, wherein the first RNTI is different from a second RNTI associated with the MBS.

5. The wireless device according to claim 1, wherein the first DRX configuration associated with the unicast transmission is independent of the second DRX configuration associated with the MBS.

6. The wireless device according to claim 1, wherein the parameters further indicate one or more parameters of the PS indication, wherein the one or more parameters include at least one of the following: A power saving RNTI (PS-RNTI) for receiving downlink control information (DCI) including the PS indication; A starting point of a search window for receiving DCI scrambled by the PS-RNTI with cyclic redundancy check (CRC) bits.

7. The wireless device according to claim 1, wherein the multicast transmission includes at least one of the following: Transmission of group common downlink control information (DCI) addressed to a group of wireless devices configured with the MBS, including the wireless device; or Transmission of a group common transport block (TB) addressed to the group of wireless devices.

8. The wireless device according to claim 1, wherein the unicast transmission includes at least one of the following: Transmission of unicast DCI specifically addressed to the wireless device; or Transmission of a unicast TB addressed to the wireless device.

9. A base station, the base station comprising: One or more processors; And A memory storing instructions that, when executed by the one or more processors, cause the base station to: Transmit parameters to a wireless device, the parameters including: A first discontinuous reception (DRX) configuration indicating a first DRX on-duration timer value associated with unicast transmissions in a cell; and A second DRX configuration indicating a second DRX on-duration timer value associated with multicast and broadcast services (MBS) in the cell; A transmission power saving (PS) indication; After the wireless device receives the PS indication, skip transmitting a first physical downlink control channel (PDCCH) for the unicast transmission to the wireless device during a first DRX on-duration of the first DRX configuration; and Transmit a second PDCCH for the MBS to the wireless device.

10. The base station according to claim 9, wherein the first DRX configuration for the unicast transmission and the second DRX configuration for the MBS are in the same bandwidth part in a cell including a plurality of bandwidth parts.

11. The base station according to claim 9, wherein transmitting the parameters includes transmitting one or more radio resource control (RRC) messages including the parameters.

12. The base station according to claim 9, wherein the parameters further include a first radio network temporary identifier (RNTI) for unicast transmission, wherein the first RNTI is different from a second RNTI associated with the MBS.

13. The base station according to claim 9, wherein the first DRX configuration associated with the unicast transmission is independent of the second DRX configuration associated with the MBS.

14. The base station according to claim 9, wherein the parameters further indicate one or more parameters of the PS indication, wherein the one or more parameters include at least one of the following: A power saving RNTI (PS-RNTI) for receiving downlink control information (DCI) including the PS indication; A starting point of a search window for receiving DCI scrambled by the PS-RNTI and having cyclic redundancy check (CRC) bits.

15. The base station according to claim 9, wherein the multicast transmission includes at least one of the following: Transmission of group common downlink control information (DCI) addressed to a group of wireless devices configured with the MBS, including the wireless device; or Transmission of a group common transport block (TB) addressed to the group of wireless devices.

16. A non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to: Receive parameters, the parameters including: A first discontinuous reception (DRX) configuration indicating a first DRX on-duration timer value associated with unicast transmissions in a cell; And A second DRX configuration, the second DRX configuration indicating a second DRX on-duration timer value associated with multicast and broadcast services (MBS) in the cell; And Receiving a power saving (PS) indication; After receiving the PS indication, based on receiving the PS indication, skipping monitoring of a first physical downlink control channel (PDCCH) for the unicast transmission during a first DRX on-duration of the first DRX configuration; And During a second DRX on-duration of the second DRX configuration and while skipping monitoring of the first PDCCH during the first DRX on-duration of the first DRX configuration, monitoring a second PDCCH for the MBS.

17. The non-transitory computer-readable medium of claim 16, wherein the first DRX configuration for the unicast transmission and the second DRX configuration for the MBS are in the same bandwidth part in a cell including a plurality of bandwidth parts.

18. The non-transitory computer-readable medium of claim 16, wherein receiving the parameter includes receiving one or more radio resource control (RRC) messages including the parameter.

19. The non-transitory computer-readable medium of claim 16, wherein the parameter further includes a first radio network temporary identifier (RNTI) for the unicast transmission, wherein the first RNTI is different from a second RNTI associated with the MBS.

20. The non-transitory computer-readable medium of claim 16, wherein the first DRX configuration associated with the unicast transmission is independent of the second DRX configuration associated with the MBS.

Images