Power saving for paging wireless devices

Abstract

A wireless device receives a parameter indicating a first location of a starting physical downlink control channel (PDCCH) monitoring occasion (MO) in a PDCCH MO of a paging early indication (PEI) occasion and a second location of a starting PDCCH MO in a PDCCH MO of a paging occasion. A first PDCCH is monitored starting from the first location and over a first number of PDCCH MOs of the PEI occasion. The PEI is received based on monitoring the first PDCCH. In response to the PEI, a second PDCCH is monitored starting from the second location and over a first number of PDCCH MOs of the paging occasion.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 186,486, filed May 10, 2021, the entire contents of which are incorporated herein by reference. Attached Figure Description

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

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

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

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

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

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

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

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

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

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

[0013] Figure 9 Three examples of bandwidth adaptation using NR carriers with configured BWPs are shown.

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

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

[0016] Figure 11A An example of the 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 Four-step contention-based random access procedures, two-step contention-free random access procedures, and another two-step random access procedure are shown respectively.

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

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

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

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

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

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

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

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

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

[0029] Figure 21A and Figure 21B An example of SCell activating / deactivating the MAC CE format is shown.

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

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

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

[0033] Figure 24B An exemplary configuration for CORESET 0 is shown.

[0034] Figure 24C An exemplary configuration for search space 0 is shown.

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

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

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

[0038] Figure 28A and Figure 28B Examples of paging based on some implementation schemes are shown.

[0039] Figure 29A and Figure 29B Examples of PEI-based paging according to some implementation schemes are shown.

[0040] Figure 30 An exemplary implementation scheme for PDCCH monitoring of PEI is shown.

[0041] Figure 31 An exemplary chart comparing the features and capabilities of RedCap wireless devices with those of non-RedCap wireless devices according to some implementation schemes is shown.

[0042] Figure 32 An example of PEI-based paging for RedCap wireless devices according to some implementation schemes is shown.

[0043] Figure 33A , Figure 33B , Figure 33C and Figure 33D An exemplary implementation of PEI and PO configuration is shown.

[0044] Figure 34Aand Figure 34B An exemplary implementation of PEI configuration is shown.

[0045] Figure 35 Examples of PEI-based paging according to some implementation schemes are shown.

[0046] Figure 36 An exemplary implementation of PEI-based paging according to some implementation schemes is shown. Detailed Implementation

[0047] In this disclosure, various embodiments are presented in the form of examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention. Indeed, after reading the specification, it will be apparent to those skilled in the art how to implement alternative embodiments. Embodiments of the invention should not be limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, actions listed in any flowchart may be reordered or optionally used only in certain embodiments.

[0048] The implementation scheme can be configured to operate as needed. For example, in wireless devices, base stations, radio environments, networks, combinations thereof, etc., the disclosed mechanisms can be executed when certain criteria are met. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, combinations thereof, etc. Various exemplary implementation schemes can be applied when one or more criteria are met. Therefore, exemplary implementation schemes that selectively implement the disclosed protocols can be implemented.

[0049] A base station can communicate with a hybrid of wireless devices. Wireless devices and / or base stations can support multiple technologies and / or multiple versions of the same technology. Wireless devices 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 refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices having a given capability and being in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure may refer to a selected set of wireless devices, and / or a subset of the total number of wireless devices in the coverage area performing according to the disclosed method, etc. Multiple base stations or multiple wireless devices may exist in the coverage area that may not conform to the disclosed method; for example, these wireless devices or base stations may be based on older versions of LTE or 5G technology.

[0050] In this disclosure, “a” (“a” and “an”) and similar phrases will be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” will be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” is interpreted as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that may or may not be used in one or more embodiments of various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components 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, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0051] 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, 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 a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations. The phrase “adopts / uses” (or equivalently “at least adopts / uses”) indicates that the phrase following the phrase “adopts / uses” is an example of one of a variety of suitable possibilities that may or may not be used for one or more different implementations.

[0052] The term "configurable" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configurable" can also mean specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

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

[0054] Many of the proposed features are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0055] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as software routines 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 modules 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++, etc. FPGAs, ASICs, and CPLDs are frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between limited internal hardware modules on a programmable device. The aforementioned techniques are often combined to achieve the desired functional module results.

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

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

[0058] RAN 104 can connect CN 102 to radio device 106 via radio communication through an air interface. As part of the radio communication, RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN 104 to radio device 106 via the air interface is referred to as the downlink, while the communication direction from radio device 106 to RAN 104 via the air interface is referred to as the uplink. Downlink transmissions can be separated from uplink transmissions using Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or some combination of these two duplex technologies.

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

[0060] RAN 104 may include one or more base stations (not shown). The term "base station" may 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 Header (RRH); Baseband Processing Unit coupled to one or more RRHs; Repeater Node or Relay Node for extending the coverage area of ​​the 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 may include at least one gNB Central Unit (gNB-CU) and at least one gNB Distributed Unit (gNB-DU).

[0061] The base stations included in RAN 104 may include one or more sets of antennas for communicating with wireless device 106 via an air interface. For example, one or more base stations in this RAN may include three sets of antennas to control three cells (or sectors) respectively. The size of a cell may 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 within the cell. The cells of the base stations may together provide radio coverage over a wide geographical area to wireless device 106 to support wireless device mobility.

[0062] Besides three-sector sites, other implementations of the base stations are also possible. For example, one or more base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units coupled to several remote radio heads (RRHs), and / or repeater or relay nodes for extending the coverage area of ​​the donor node. The baseband processing units coupled to the RRHs can be part of a centralized or cloud RAN architecture, where the baseband processing units can be centralized in a pool of baseband processing units or virtualized. Repeater nodes can amplify and replay radio signals received from the donor node. Relay nodes can perform the same / similar functions as repeater nodes, but can decode the radio signals received from the donor node to remove noise before amplifying and replaying the radio signals.

[0063] RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna configurations and similar high-level transmission power. RAN 104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas overlapping 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 "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations, in descending order of coverage area, include: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

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

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

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

[0068] The AMF 158A can perform functions such as: Non-Access Layer (NAS) signaling termination, NAS signaling security, Access Layer (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the UE, and AS can refer to functions operating between the UE and the RAN.

[0069] 5G-CN 152 may include, for clarity, not listed here. Figure 1B One or more additional network functions are shown in the diagram. For example, 5G-CN 152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Open Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

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

[0071] like Figure 1B As shown, gNB 160 and / or ng-eNB 162 can connect 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 a direct physical connection and / or an indirect connection via an underlying transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can connect to UE 156 via the Uu interface. For example, as... Figure 1B As shown, the gNB 160A can connect to the UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface can be... Figure 1B The network elements in the system are used to exchange data and signaling messages, and can include two planes: a user plane and a control plane. The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

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

[0073] The gNB 160 can provide NR user plane and control plane protocol termination to UE 156 via the Uu interface. For example, the 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. The 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 3GPP 4G radio access technology. For example, the 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.

[0074] 5G-CN 152 is described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that NR can potentially connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B The diagram shows only one AMF / UPF 158, but a gNB or ng-eNB can connect to multiple AMF / UPF nodes to provide redundancy and / or load sharing across those multiple AMF / UPF nodes.

[0075] As discussed, Figure 1B The interfaces between network elements (e.g., Uu, Xn, and NG interfaces) can be associated with the protocol stack 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 handles data of interest to the user, while the control plane handles signaling messages of interest to the network elements.

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

[0077] Figure 2A The diagram illustrates a five-layer NR user plane protocol stack implemented in UE 210 and gNB 220. At the bottom of the stack, the Physical Layer (PHY) 211 and 221 provide transport services to the higher layers and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHY 211 and 221 include Media Access Control (MAC) 212 and 222, Radio Link Control (RLC) 213 and 223, Packet Data Convergence Protocol (PDCP) 214 and 224, and Service Data Application Protocol (SDAP) 215 and 225. These four protocols together can constitute Layer 2 or the Data Link Layer of the OSI model.

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

[0079] PDCP 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 their intended source. PDCP 214 and 224 can perform retransmission of undelivered packets, reordering and repackaging of packets, and removal of duplicate packets received due to, for example, intra-gNB handover. PDCP 214 and 224 can perform packet duplication to increase the likelihood of packet reception and remove any duplicate packets at the receiver. Packet duplication can be suitable for services requiring high reliability.

[0080] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in dual connectivity scenarios. Dual connectivity is a technique that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). Split bearers are those that are split when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapping split radio bearers between RLC channels belonging to a cell group.

[0081] RLCs 213 and 223 can respectively perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222. RLCs 213 and 223 can support three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM). Based on the transmission mode the RLC is operating in, the RLC can perform one or more of the aforementioned functions. RLC configuration can be based on each logical channel, independent of parameter sets and / or Transmission Time Interval (TTI) duration. Figure 3 As shown, RLC 213 and 223 can provide RLC channels as services to PDCP 214 and 224, respectively.

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

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

[0084] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A The diagram illustrates the downlink data flow through the NR user plane protocol stack to generate three IP packets (n, n+1, and m) of two TB at the gNB 220. The uplink data flow through the NR user plane protocol stack can be compared with... Figure 4A The downlink data flow described in the text is similar.

[0085] Figure 4A The downlink data flow begins when SDAP 225 receives three IP packets from one or more QoS flows and maps those three packets to a radio bearer. Figure 4A In SDAP 225, IP packets n and n+1 are mapped to the first radio bearer 402, and IP packet m is mapped to the second radio bearer 404. The SDAP header (in...) Figure 4AData units marked with "H" are added to IP packets. Data units originating from / going to a higher protocol layer are called lower protocol layer Service Data Units (SDUs), and data units originating from / going to a lower protocol layer are called higher protocol layer Protocol Data Units (PDUs). Figure 4A As shown, the data unit from SDAP225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0086] Figure 4A The remaining protocol layers can perform their associated functions (e.g., regarding...). Figure 3 This involves adding the corresponding headers and forwarding their output 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 fragmentation (e.g., as...). Figure 4A (As shown in the image regarding IP packet m) and forwards its output to MAC 222. MAC 222 can multiplex many RLC PDUs and can attach MAC subheaders to RLC PDUs to form transport blocks. In NR, MAC subheaders can be distributed throughout MAC PDUs, such as... Figure 4A As shown in the diagram. In LTE, the MAC sub-header can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU sub-header can be computed before the complete MAC PDU is assembled.

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

[0088] Figure 4B The diagram further illustrates a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B This shows two MAC CEs inserted into the MAC PDU. These can be used at the beginning of downlink transmissions within the MAC PDU (e.g., ...). Figure 4B(As shown in the diagram) and a MAC CE is inserted at the end of the uplink transmission of the MAC PDU. The MAC CE 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 repeated detection, channel state information (CSI) reports, 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 subheader with a format similar to that described with respect to the MAC SDU may precede the MAC CE, and the MAC CE may be identified by a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0090] Figure 5A and Figure 5B The mappings between logical channels, transport channels, and physical channels are shown for both downlink and uplink. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels carrying control and configuration information in the NR control plane, or as service channels carrying data in the NR user plane. Logical channels can be classified as dedicated logical channels for 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:

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

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

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

[0094] - Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure that UE; and

[0095] - Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

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

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

[0098] - Broadcast channel (BCH), which is used to carry MIBs from the BCCH;

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

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

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

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

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

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

[0105] - The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands;

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

[0107] - The Physical Uplink Control Channel (PUCCH), which carries the UCI, including HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

[0109] Similar to the physical control channel, the physical layer generates physical signals to support low-level physical layer operations. For example... Figure 5A and Figure 5B As shown, 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.

[0110] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2B As 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 protocols 217 and 237 at the top of the NR control plane protocol stack.

[0111] NAS protocols 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 CN. NAS protocols 217 and 237 can provide control plane functions between UE 210 and AMF 230 via signaling messages known as NAS messages. There is no direct path through which NAS messages can be transmitted between UE 210 and AMF 230. NAS messages can be transmitted using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0112] RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220, or more generally between UE 210 and RAN. RRC 216 and 226 can provide control plane functionality between UE 210 and gNB 220 via signaling messages known as RRC messages. RRC messages can be transmitted between UE 210 and RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC can multiplex control plane and user plane data into the same transport block (TB). RRC 216 and 226 can provide control plane functions such as: broadcasting system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of RRC connections between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of such reporting; detection and recovery of radio link failures (RLFs); and / or NAS messaging. As part of establishing an RRC connection, RRC 216 and 226 can establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0113] Figure 6 This is an example diagram illustrating the RRC state transition of the UE. The UE can interact with... Figure 1A The wireless device 106 described in the document Figure 2A and Figure 2B The UE 210 depicted herein is the same as or similar to any other wireless device described in this disclosure. Figure 6 As shown, 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).

[0114] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in RAN 104 as depicted herein; Figure 1B One of gNB 160 or ng-eNB 162 described herein; Figure 2A and Figure 2BThe gNB220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for that UE. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure 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 UE's serving base station may request a cell transfer to one of the neighboring base stations based on the reported measurements. The RRC state can be changed from RRC connection 602 to RRC idle 604 through connection release procedure 608, or to RRC inactive 606 through connection deactivation procedure 610.

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

[0116] In RRC inactivity 606, the previously established RRC context is maintained in both the UE and the base station. This allows for a faster transition to RRC connection 602 with reduced signaling overhead compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactivity 606, the UE can be in a sleep state, and the UE's mobility can be managed by the UE via cell reselection. The RRC state can transition from RRC inactivity 606 to RRC connection 602 via connection resumption procedure 614, or to RRC idle 604 via connection release procedure 616, which can be the same as or similar to connection release procedure 608.

[0117] RRC states can be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to allow the network to notify the UE of events via paging messages without having to broadcast paging messages across the entire mobile network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 allow the network to track the UE at the cell group level, so that paging messages can be broadcast on the cells in the cell group where the UE is currently camped, rather than across the entire mobile network. Mobility management mechanisms for RRC Idle 604 and RRC Inactive 606 track the UE at the cell group level. These mobility management mechanisms can do this using groupings of different granularities. For example, there can be three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

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

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

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

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

[0122] In NR, physical signals and physical channels (about Figure 5A and Figure 5B The data discussed can be mapped onto Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data via F orthogonal subcarriers (or tones). Before transmission, the data can be mapped onto a series of complex symbols called source symbols (e.g., M-QAM or M-PSK symbols) and divided into F parallel symbol streams. These F parallel symbol streams can be treated as if they were in the frequency domain and used as input to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block takes F source symbols at a time (one source symbol from each of the F parallel symbol streams) and uses each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. These F time-domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and upsampling, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This operation produces OFDM symbols precoded with Discrete Fourier Transform (DFT) 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 symbols at the receiver can be performed using the FFT block to recover the data mapped to the source symbols.

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

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

[0125] 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 This illustrates the transmission structure of the time slot duration and per subframe time slot related to the parameter set (for ease of explanation). Figure 7 (The parameter set with a subcarrier spacing of 240 kHz is not shown in the diagram). Subframes in NR can be used as a time reference independent of the parameter set, while time slots can be used as units for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be separated from the time slot duration and begin at any OFDM symbol, continuing to transmit as many symbols as needed. These partial time slot transmissions can be referred to as micro-time slots or sub-time slot transmissions.

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

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

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

[0129] NR defines Bandwidth Components (BWPs) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In the example, a BWP can be defined by a subset of consecutive Relay Buses (RBs) on a carrier. A UE can be configured (e.g., via the RRC layer) to have 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 the serving cell can be active. These one or more BWPs can be referred to as the active BWPs of the serving cell. When the serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0130] For unpaired spectrum, if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP, then the downlink BWP from the set of configured downlink BWPs can link with the uplink BWP from the set of configured uplink BWPs. For unpaired spectrum, the UE can expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0131] For a 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 domains where a UE can locate control information. The search space can be a UE-specific search space or a shared search space (potentially usable by multiple UEs). For example, the base station can configure a shared search space for the UE on a PCell or primary / secondary cell (PSCell) within an active downlink BWP.

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

[0133] One or more BWP indicator fields can be provided in the downlink control information (DCI). The value of the BWP indicator field can 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 can indicate the active uplink BWP for one or more uplink transmissions.

[0134] The base station can semi-statically configure a default downlink BWP for the UE within a 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 can be the initial active downlink BWP. The UE can determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

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

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

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

[0138] Figure 9 An example of bandwidth adaptation using three configured BWPs on an NR carrier is shown. A UE configured with these three BWPs can switch from one BWP to another at a handover point. Figure 9 In the example shown, the BWPs include: BWP 902 with a bandwidth of 40MHz and a subcarrier spacing of 15kHz; BWP 904 with a bandwidth of 10MHz and a subcarrier spacing of 15kHz; and BWP 906 with a bandwidth of 20MHz and a subcarrier spacing of 60kHz. BWP 902 can be the initial active BWP, and BWP 904 can be the default BWP. The UE can switch between BWPs at a handover point. Figure 9 In the example, the UE can switch from BWP 902 to BWP 904 at handover point 908. The handover at handover point 908 can 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 a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 906 at handover point 910 in response to receiving a DCI indicating that BWP 906 is the active BWP. The UE can switch from 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 a DCI indicating that BWP 904 is the active BWP. The UE can switch from active BWP 904 to BWP 902 at handover point 914 in response to receiving a DCI indicating that BWP 902 is the active BWP.

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

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

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

[0142] In the example, up to 32 CCs can be aggregated. Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD or FDD). The serving cell 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.

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

[0144] Configurable SCells for the UE can be activated and deactivated based on factors such as traffic and channel conditions. Deactivating an SCell can mean ceasing PDCCH and PDSCH reception on the SCell, and ceasing PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4B The MAC CE is used to activate and deactivate configured SCells. For example, the MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells for the UE (e.g., in a subset of configured SCells) are activated or deactivated. Configured SCells can be deactivated in response to the expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0145] Downlink control information for a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, a process known as self-scheduling. A cell's DCI can be transmitted on another cell, a process known as cross-carrier scheduling. Uplink control information used for aggregation cells (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. For a large number of aggregated downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0146] Figure 10B This illustrates an example of how aggregated cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. Figure 10BIn the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 in this example includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) can be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) can be transmitted in the uplink of PSCell 1061. In the example, if Figure 10B If the aggregated cell depicted is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell will transmit UCIs associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by allocating UCI transmissions between PCell 1021 and PSCell 1061.

[0147] A physical cell ID and a cell index can be assigned to a cell that includes a downlink carrier and an optional uplink carrier. The physical cell ID or cell index can identify the cell's downlink carrier and / or uplink carrier, for example, depending on the context in which the physical cell ID is used. The physical cell ID can be determined using synchronization signals transmitted on the downlink component carrier. The cell index can be determined using RRC messages. In this disclosure, the physical cell ID can be referred to as a carrier ID, and the cell index can be referred to as a carrier index. For example, when this disclosure relates to a first physical cell ID for a first downlink carrier, this disclosure can mean that the first physical cell ID is used for a cell that includes the first downlink carrier. The same / similar concepts can be applied, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification can mean that a cell including that first carrier is activated.

[0148] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In the example, the HARQ entity can operate on the serving cell. Transport blocks can be generated based on the assignment / authorization of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

[0149] In the downlink, the base station can 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, such as...). Figure 5A (As shown). In the uplink, the UE can transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, such as...). Figure 5B (As shown). PSS and SSS can be transmitted by the base station and used by the UE to synchronize the UE with the base station. PSS and SSS can be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes PSS, SSS, and PBCH. The base station can periodically transmit bursts of SS / PBCH blocks.

[0150] Figure 11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks can include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as...). Figure 11A (As shown). Bursts can be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts can be limited to half-frames (e.g., the first half-frame lasting 5 ms). It should be understood that... Figure 11A This is an example, and these parameters (the number of SS / PBCH blocks per burst, the burst period, and the burst location within a frame) can be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; the cell's parameter set or subcarrier spacing; configuration performed by the network (e.g., using RRC signaling); or any other suitable factor. In this example, the UE can 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.

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

[0152] The UE may not know the location of the SS / PBCH block in the time and frequency domains (e.g., when the UE is searching for a cell). To find and select a cell, the UE can monitor the carrier of the PSS. For example, the UE can monitor the frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE can search for the PSS at different frequency locations within the carrier, as indicated by the synchronization grating. If the PSS is found at a certain location in the time and frequency domains, the UE can determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block can be a cell-defined SS block (CD-SSB). In the example, the primary cell can be associated with the CD-SSB. The CD-SSB can be located on the synchronization grating. In the example, cell selection / search and / or reselection can be based on the CD-SSB.

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

[0154] The PBCH can use QPSK modulation and forward error correction (FEC). FEC can use polarity coding. One or more symbols spanned by the PBCH can carry one or more DMRS for PBCH demodulation. The PBCH can include an indication of the cell's current system frame number (SFN) and / or an SS / PBCH block timing index. These parameters can help the UE synchronize time with the base station. The PBCH can include a Master Information Block (MIB) to provide one or more parameters to the UE. The MIB can be used by the UE to locate the Residual Minimum System Information (RMSI) associated with the cell. The RMSI can include System Information Block Type 1 (SIB1). SIB1 can contain information required for the UE to access the cell. The UE can use one or more parameters of the MIB to monitor the PDCCH that can be used to schedule the PDSCH. The PDSCH can include SIB1. SIB1 can be decoded using the parameters provided in the MIB. The PBCH can indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE can point to a frequency. The UE can search for SS / PBCH blocks at the frequency pointed to by the UE.

[0155] 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 blocks transmitted with different SS / PBCH block indices.

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

[0157] In the example, within the carrier's frequency range, the base station can transmit multiple SS / PBCH blocks. In the example, the first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks can be different from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations can be different or the same.

[0158] CSI-RS can be transmitted by the base station and used by the UE to acquire Channel State Information (CSI). The base station can utilize one or more CSI-RS to configure the UE for channel estimation or any other suitable purpose. The base station can utilize one or more of the same / similar CSI-RS to configure the UE. The UE can measure the one or more CSI-RS. The UE can estimate the downlink channel state and / or generate a CSI report based on the measurements of the one or more downlink CSI-RS. The UE can provide the CSI report to the base station. The base station can use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

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

[0160] The base station can configure the UE to report CSI measurements. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with multiple CSI report timings and / or periods. For aperiodic CSI reporting, the base station can request CSI reports. For example, the base station can command the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reports. The base station can configure the UE using CSI-RS resource sets and CSI reports using RRC signaling.

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

[0162] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, downlink DMRS can be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network can support one or more variable and / or configurable DMRS modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. Frontload 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 using the number (e.g., maximum number) of frontload DMRS symbols used for PDSCH. A DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, a DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, a DMRS configuration can support up to four orthogonal downlink DMRS ports per UE. The radio network can (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, where DMRS locations, DMRS types, and / or scrambling sequences can be the same or different. The base station can use the same precoding matrix to transmit downlink DMRS and the corresponding PDSCH. The UE can use one or more downlink DMRS to perform consistent demodulation / channel estimation of the PDSCH.

[0163] In the example, the transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices can differ based on the first and second bandwidths being different. The UE can assume that the same precoder matrix is ​​used across the set of PRBs. This set of PRBs can be represented as a Precoder Resource Block Group (PRG).

[0164] A PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS exists on one or more layers of the PDSCH. A higher layer may configure up to three DMRS for the PDSCH.

[0165] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on RRC configuration. The presence and / or type of downlink PT-RS can be configured UE-specifically using a combination of RRC signaling and / or associated with one or more parameters (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least one MCS. NR networks 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 both 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. Downlink PT-RS can be limited to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0166] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS to perform consistent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DMRS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE using one or more uplink DMRS configurations. At least one DMRS configuration can support a frontload DMRS mode. Frontload 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 frontload DMRS symbols for PUSCH and / or PUCCH, which the UE can use to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DMRS structure for both downlink and uplink, where the DMRS location, DMRS type, and / or scrambling sequence of the DMRS can be the same or different.

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

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

[0169] The UE can 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 allows the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station can use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmissions from the UE. The base station can semi-statically configure the UE using one or more SRS resource sets. For each SRS resource set, the base station can configure the UE using one or more SRS resources. SRS resource set suitability can be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, etc.) can be transmitted at certain times (e.g., simultaneously). The UE can transmit one or more SRS resources from the SRS resource set. The NR network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, where the trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In the example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In the example, when PUSCH and SRS are transmitted in the same time slot, the UE can be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0170] The base station can 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; temporal behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); time slot, micro-time slot, and / or subframe level period; time slots of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiating OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0171] An antenna port is defined such that a symbol on the antenna port, through the channel through which it is transmitted, can be inferred from another symbol on the same antenna port, through the same channel through which it is transmitted. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel used to transmit the second symbol on the antenna port (e.g., fade gain, multipath delay, etc.) from the channel used to transmit the first symbol on the antenna port. A first antenna port and a second antenna port can be referred to as quasi-co-located (QCLed) if one or more large-scale properties can be inferred from the channel through which the second symbol on the second antenna port is transmitted. These 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 reception (Rx) parameters.

[0172] Channels using beamforming require beam management. Beam management can include beam measurement, beam selection, and beam indication. A beam can be associated with one or more reference signals. For example, a beam can be identified by one or more beamforming reference signals. The UE can perform downlink beam measurements and generate a beam measurement report based on downlink reference signals (e.g., Channel State Information Reference Signal (CSI-RS)). After setting up an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0173] 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 may represent a resource block (RB) within the cell's bandwidth. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters can be configured for CSI-RS resource configuration via higher-layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, Code Division Multiplexing (CDM) type parameters, frequency density, transport comb, Quasi-Co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

[0175] CSI-RS, such as Figure 11BThose shown (e.g., CSI-RS1101, 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) configured with CSI-RS resources. The base station can configure the UE using a reporting configuration, and the UE can report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can determine one or more Transmission Configuration Indication (TCI) states, including multiple reference signals, based on the reported measurement results. In the 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 downlink transmissions with a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter for the transmit (Tx) beam based on the spatial domain filter corresponding to the Rx beam. If the UE does not have beam correspondence capability, the UE can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The UE can perform the uplink beam selection procedure based on one or more Sounding Reference Signal (SRS) resources configured for the UE by the base station. The base station can select and indicate the UE's uplink beam based on measurements of one or more SRS resources transmitted by the UE.

[0176] In the beam management procedure, the UE can assess (e.g., measure) the channel quality of one or more beampup links, including beampup links containing transmit beams transmitted by the base station, and receive beams received by the UE. Based on this assessment, the UE can transmit a beam measurement report indicating one or more beampup 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).

[0177] Figure 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurement of the transmit (Tx) beams for a Transport Receive 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 the beam set (shown as an ellipse rotating counterclockwise in the top rows of P1 and P2, indicated by the dashed arrows). Beamforming at the UE can include Rx beam sweeping for the beam set (shown as an ellipse rotating clockwise in the bottom rows of P1 and P3, indicated by the dashed arrows). Procedure P2 can be used to enable UE measurement of the Tx beams for a TRP (shown as an ellipse rotating counterclockwise in the top row of P2, indicated by the dashed arrows). The UE and / or base station may perform procedure P2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0178] Figure 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the UE's Tx beam, 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, an Rx beam sweep from the beam set (shown as an ellipse rotating clockwise in the bottom rows of U1 and U3, indicated by the dashed arrow). Beamforming at the base station can include, for example, an Rx beam sweep from the beam set (shown as an ellipse rotating counterclockwise in the top rows of U1 and U2, indicated by the dashed arrow). When the UE uses a fixed Tx beam, procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or base station can perform procedure U2 using a smaller beam set than that used in procedure P1, or using a narrower beam than that used in procedure P1. This can be called beam refinement. The UE can execute procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0179] The UE can initiate a beam fault recovery (BFR) procedure based on the detection of a beam fault. The UE can transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE can detect a beam fault based on the determination that the quality of the beam pair link in the associated control channel is unsatisfactory (e.g., an error rate higher than the error rate threshold, received signal power lower than the received signal power threshold, timer expiration, etc.).

[0180] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, which may include one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRS). The quality of the beamp-link can 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 reception quality (RSRQ) value, and / or CSI value measured on the RS resources. The base station may indicate one or more DM-RS quasi-co-located (QCLed) RS resources and channels (e.g., control channels, shared data channels, etc.). The one or more DMRS of the RS resources and channels may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from the transmission to the UE via the RS resources are similar to or the same as the channel characteristics from the transmission to the UE via the channels.

[0181] The network (e.g., gNB and / or the network's ng-eNB) and / or the UE can initiate a random access procedure. A UE in the RRC_IDLE state and / or RRC_INACTIVE state can initiate a random access procedure to request connection settings to the network. A UE can initiate a random access procedure from the RRC_CONNECTED state. A UE can initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). A UE can initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). A UE can initiate a random access procedure for beam fault recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

[0182] Figure 13A A four-step contention-based random access procedure is shown. Before initiating this procedure, the base station may transmit configuration message 1310 to the UE. Figure 13AThe procedure shown involves 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).

[0183] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. These one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. These 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 these one or more RRC messages to one or more UEs. These 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 RRC_INACTIVE state). The UE may determine the time and frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on these one or more RACH parameters. Based on these one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0184] The one or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting Msg 11311. These one or more PRACH timings may be predefined. These one or more RACH parameters may indicate one or more available sets of one or more PRACH timings (e.g., prach-ConfigIndex). These one or more RACH parameters may indicate a relationship between (a) one or more PRACH timings and (b) one or more reference signals. These one or more RACH parameters may indicate a relationship between (a) one or more preambles and (b) one or more reference signals. These one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, these one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

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

[0186] Msg 1 1311 may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine the preamble group based on path loss measurements and / or the magnitude of Msg 3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by 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.

[0187] 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: the 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 an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE can determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH timings. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting the preamble and for determining the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate the association between the PRACH timing and the one or more reference signals.

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

[0189] The Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 was received by the base station. Msg 2 1312 may include a time comparison command that the UE can use to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE can determine when to initiate a time window based on the PRACH timing in which it transmits the preamble. For example, the UE can initiate a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH timing starting from the end of the preamble transmission). This one or more symbols can be determined based on a set of parameters. The PDCCH can be in a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The UE can identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI can be used depending on one or more events that initiate a random access procedure. The UE can use a Random Access RNTI (RA-RNTI). The RA-RNTI can be associated with the PRACH timing in which the UE transmits the preamble. For example, the UE can determine the RA-RNTI based on: the OFDM symbol index; the time slot index; the frequency domain index; and / or the UL carrier indicator of the PRACH timing. An example of an RA-RNTI is as follows:

[0190] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0191] Where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carriers and 1 for SUL carriers).

[0192] The UE may transmit Msg 3 1313 in response to successful reception of Msg 2 1312 (e.g., using the resource identified in Msg 2 1312). Msg 3 1313 can be used for, for example... Figure 13A The diagram illustrates contention resolution in a contention-based random access procedure. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to each UE. If these multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 if a C-RNTI is assigned, and / or any other suitable identifier).

[0193] Msg 4 1314 can be received after or in response to the transmission of Msg 3 1313. If Msg 3 1313 includes a C-RNTI, the base station will use the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been successfully completed. If Msg 3 1313 includes a TC-RNTI (e.g., if the UE is in RRC_IDLE state or 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 (e.g., is transmitted) the CCCH SDU sent in Msg 3 1313, the UE can determine that contention resolution was successful and / or the UE can determine that the random access procedure was successfully completed.

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

[0195] Figure 13B This illustrates a two-step contention-free random access procedure. (Compared to...) Figure 13A Similar to the four-step contention-based random access procedure shown, the base station can transmit configuration message 1320 to the UE before the procedure is initiated. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The program shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 can be similar in some respects to... Figure 13A The Msg 1 1311 and Msg2 1312 are shown. (As from...) Figure 13A and Figure 13B It will be understood that a contention-free random access procedure may not include messages such as Msg 3 1313 and / or Msg4 1314.

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

[0197] After transmitting the preamble, the UE can initiate a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the event of a beam failure recovery request, the base station can configure the UE with a separate time window and / or a separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE can monitor the PDCCH transmission of the Cell RNTI (C-RNTI) addressed to the search space. Figure 13B In the contention-free random access procedure shown, the UE can determine that the random access procedure was 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 addresses to the C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with the preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that this response is an indication of confirmation of the SI request.

[0198] Figure 13C Another two-step random access procedure is shown. (Compared to...) Figure 13A and Figure 13B Similar to the random access procedure shown, the base station can transmit configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The program shown includes the transmission of two messages: Msg A1331 and Msg B1332.

[0199] Msg A 1331 can be transmitted by the UE in uplink transmission. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include... Figure 13A The content shown in Msg 3 1313 is similar to and / or equivalent to that of Msg 3 1313. Transport block 1342 may include UCIs (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 to and / or equivalent to Msg 3 1313. Figure 13A and Figure 13B The Msg 2 1312 shown (e.g., RAR) and / or Figure 13A The content shown in Msg 4 1314 is similar to and / or equivalent to the content shown in Msg 4 1314.

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

[0201] The UE can determine the radio resources and / or uplink transmission power of the preamble 1341 and / or transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in 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 transport block 1342. The time-frequency resources (e.g., PRACH) for the transmission of the preamble 1341 and the 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 enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0202] Transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing advanced 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., a C-RNTI or a TC-RNTI). The UE can determine that the two-step random access procedure was successfully completed if: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

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

[0204] 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-shared PDCCH (GC-PDCCH) common to the UE group.

[0205] A base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to the DCI to aid in the detection of transmission errors. When the DCI is intended for use with a UE (or a group of UEs), the base station can scramble the CRC parity bits with the UE's identifier (or the UE group's identifier). Scrambling the CRC parity bits with the identifier can include a Modulo-2 appending (or an exclusive OR operation) of the identifier value and the CRC parity bits. This identifier can include the 16-bit value of the Radio Network Temporary Identifier (RNTI).

[0206] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled using the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled using the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled using the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled using the Cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled using the Temporary Cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13AThe Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the UE may include: the configured scheduling RNTI (CS-RNTI), transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0207] 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 can be used for PUSCH scheduling in a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used for PUSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used for PDSCH scheduling in a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used for PDSCH scheduling in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide slot format indication to UE groups. DCI format 2_1 can be used to notify UE groups of physical resource blocks and / or OFDM symbols, where UEs may assume that transmission to UEs is not expected. DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. New DCI formats for new features can be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

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

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

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

[0211] The base station can transmit an RRC message to the UE, including configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters can indicate: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring period and PDCCH monitoring type; 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 can be predefined and known to the UE. The set of CCEs in the UE-specific search space set can be configured based on the UE's identifier (e.g., C-RNTI).

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

[0213] The UE can transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling transmission may include a Hybrid Automatic Repeat Request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. Uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station can determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment, CSI report, SR, etc.) via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The UE may use one of several PUCCH formats to transmit uplink control signaling via the PUCCH.

[0214] Five PUCCH formats can exist, and the UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols transmitted in the UCI 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 more than one or two symbols are transmitted and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with 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 between four and fourteen OFDM symbols and can include two or fewer bits. If four or more symbols are transmitted 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 more than one or two symbols are transmitted and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal overlay code, the UE can use PUCCH format 3. PUCCH format 4 can occupy between four and fourteen OFDM symbols and can include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal overlay code, the UE can use PUCCH format 4.

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

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

[0217] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of this 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 shown or any other communication network. Figure 15 The diagram shows only one wireless device 1502 and one base station 1504, but it should be understood that a mobile communication network may include more than one UE and / or more than one base station, which have the same characteristics as... Figure 15 The same or similar configurations shown.

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

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

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

[0221] At base station 1504, receiving processing system 1512 can receive uplink transmissions from wireless device 1502. At wireless device 1502, receiving processing system 1522 can receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping of the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

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

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

[0224] Processing system 1508 and / or 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 gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or 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 wireless device 1502 and base station 1504 to operate in a wireless environment.

[0225] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, 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.). Processing system 1508 and / or 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 aforementioned one or more peripheral devices. The processing system 1518 in wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in wireless device 1502. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof. Processing system 1508 and / or processing system 1518 may be connected to GPS chipset 1517 and GPS chipset 1527, respectively. GPS chipset 1517 and GPS chipset 1527 may be configured to provide geographic location information for wireless device 1502 and base station 1504, respectively.

[0226] Figure 16AAn exemplary structure for uplink transmission is shown. The baseband signal representing the physical uplink shared channel can perform one or more functions. These functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulation symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports; and so on. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. In the example, when transform precoding is not enabled, it can be achieved through... Figure 16A Generate CP-OFDM signals for uplink transmission. These functions are shown as examples, and other mechanisms are expected to be implemented in various implementation schemes.

[0227] Figure 16B An exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value SC-FDMA or CP-OFDM baseband signal from the antenna port and / or a complex-value Physical Random Access Channel (PRACH) baseband signal. Filtering can be applied before transmission.

[0228] Figure 16C An exemplary structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These functions may include: scrambling coded bits in a codeword to be transmitted over the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols for transmission at the antenna port; mapping the complex-valued modulation symbols for the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and so on. These functions are shown as examples, and other mechanisms are contemplated for implementation in various embodiments.

[0229] Figure 16D Another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-value OFDM baseband signal at the antenna port. Filtering can be applied before transmission.

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

[0231] A timer can begin running once started and continues running until it stops or expires. If a timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or it can start from zero and expire once it reaches that value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). Timers can be used to measure time periods / windows 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 these multiple ways of implementing a timer can be used to measure time periods / windows of a process. For example, a random access response window timer can be used to measure a time window for receiving a random access response. In the example, instead of starting and expiring the random access response window timer, the time difference between two timestamps can be used. When the timer restarts, the measurement process for the time window can be restarted. Other exemplary implementations can be provided to restart the measurement of a time window.

[0232] A base station can transmit one or more MAC PDUs to a wireless device. In the example, the MAC PDU can be a bit string with length byte alignment (e.g., alignment with multiples of octets). In the example, the bit string can 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 can be read from left to right and then in line-by-line reading order. In the example, the bit order of the parameter fields within the MAC PDU is represented by the first and most significant bits in the leftmost position and the last and least significant bits in the rightmost position.

[0233] In the example, the MAC SDU can be a bit string whose length is byte-aligned (e.g., aligned to multiples of octets). In the 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 to multiples of octets). The MAC sub-header can be a bit string whose length is byte-aligned (e.g., aligned to multiples of octets). In the example, the MAC sub-header can be placed directly before the corresponding MAC SDU, MAC CE, or padding. The MAC entity can omit the values ​​of reserved bits in the DL MAC PDU.

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

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

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

[0237] 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 MAC CEs can be placed before a MAC subPDU containing MAC SDUs or a MAC subPDU containing fillers. Figure 18B An example of a UL MAC PDU is shown. Multiple MAC CEs (such as MAC CE1 and 2) can be placed together. In an implementation, a MAC subPDU including a MAC CE can be placed after all MAC subPDUs including a MAC SDU. Alternatively, a MAC subPDU can be placed before any MAC subPDUs including filler MAC subPDUs.

[0238] In the example, the base station's MAC entity can transmit one or more MAC CEs to the wireless device's MAC entity. Figure 19 Examples of multiple LCIDs that can be associated with one or more MAC CEs are shown. The one or more MAC CEs may include at least one of the following: SP ZP CSI-RS resource set activation / deactivation MAC CE; PUCCH spatial relationship activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI report on PUCCH activation / deactivation MAC CE; TCI status indication for UE-specific PDCCH MAC CE; TCI status indication for UE-specific PDSCH MAC CE; non-periodic CSI triggered 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 the example, a MAC CE, such as a MAC CE transmitted from the base station's MAC entity to the wireless device's MAC entity, may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

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

[0240] In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. A radio device can use CA techniques, depending on its capabilities, to simultaneously receive or transmit on one or more CCs. In implementations, the radio device can support CA for continuous CCs and / or for discontinuous CCs. CCs can be organized into cells. For example, CCs can be organized into a primary cell (PCell) and one or more secondary cells (SCells). When CA is configured, the radio device can have an RRC connection to the network. During RRC connection establishment / re-establishment handover, the cell providing NAS mobility information can be the serving cell. During RRC connection re-establishment / handover procedures, the cell providing security input can be the serving cell. In the example, the serving cell can represent a PCell. In the example, the base station can transmit one or more messages to the radio device, including configuration parameters for one or more SCells, depending on the radio device's capabilities.

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

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

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

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

[0245] When an SCell is deactivated, the radio device may not perform the following operations: transmitting SRS on the SCell; reporting CQI / PMI / RI / CRI to 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 an activated SCell indicates uplink clearance or downlink assignment, the radio device may restart the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In the example, when at least one second PDCCH on the serving cell of the activated SCell (e.g., a PCell or SCell configured with PUCCH, i.e., a PUCCH SCell) indicates uplink clearance or downlink assignment for the activated SCell, the radio device may restart the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In the example, when the SCell is disabled, if there is an ongoing random access procedure on the SCell, the wireless device can terminate the ongoing random access procedure on the SCell.

[0246] Figure 21A An example of an octet of SCell activating / deactivating a MAC CE is shown. It has a first LCID (e.g., as...). Figure 19 The first MAC PDU subheader (shown as '111010') can identify an octet of SCell activation / deactivation MAC CE. An octet of SCell activation / deactivation MAC CE can have a fixed size. An octet of SCell activation / deactivation MAC CE can comprise a single octet. A single octet can comprise a first number of C fields (e.g., seven) and a second number of R fields (e.g., one).

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

[0248] exist Figure 21A and / or Figure 21B In the context of C, if an SCell with index i has been configured, then C... i The field can indicate the active / deactivated status of an SCell with SCell index i. In the example, when C i When a field is set to one, the SCell with index i is activated. In the example, when C... i Setting the field to zero disables the SCell with index i. In the example, if no SCell with index i is configured, the wireless device can ignore C. i Fields. Figure 21A and Figure 21B In this context, the R field can indicate reserved bits. The R field can be set to zero.

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

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

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

[0252] Figure 22An example of BWP handover on a cell (e.g., PCell or SCell) is illustrated. In the example, the radio device can receive at least one RRC message from a base station, which includes cell parameters 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 establishment message (e.g., RRCEestablishment); and / or an RRC connection setup message (e.g., RRCSetup). Of the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), and one BWP may be configured as the default BWP (e.g., BWP 0). The radio device may receive a command to activate the cell (e.g., an RRC message, MAC CE, or DCI) in the nth time slot. If the cell is a PCell, the radio device may not receive the command to activate the cell; for example, the radio device may activate the PCell once it receives an RRC message including the PCell's configuration parameters. The radio device may begin monitoring the PDCCH on BWP 1 in response to the activated cell.

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

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

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

[0256] In the example, if a MAC entity receives a PDCCH for BWP handover to the serving cell, and no random access procedure associated with this serving cell is in progress, the radio device can perform a BWP handover to the BWP indicated by the PDCCH. In the example, if the bandwidth portion indicator field is configured in DCI format 1_1, the bandwidth portion indicator field value can indicate the active DL BWP for DL ​​reception from the configured DL BWP set. In the example, if the bandwidth portion indicator field is configured in DCI format 0_1, the bandwidth portion indicator field value can indicate the active UL BWP for UL transmission from the configured UL BWP set.

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

[0258] In the 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 the timer value, then the wireless device procedure on the secondary cell can be the same as the wireless device procedure on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0259] In the example, if the radio device is configured with a first active DL BWP on the secondary cell or carrier via the higher-layer parameter Active-BWP-DL-SCell (Active-BWP-DL-SCell) and a first active UL BWP via the higher-layer parameter Active-BWP-UL-SCell (Active-BWP-UL-SCell), then the radio device can use the indicated DL BWP and indicated UL BWP on the secondary cell as the corresponding first active DL BWP and first active ULBWP on the secondary cell or carrier.

[0260] In the example, the set of PDCCH candidates to be monitored by the wireless device can be defined in terms of the PDCCH search space set. The search space set includes either the CSS set or the USS set. The wireless device monitors PDCCH candidates in one or more of the following search space sets: Type 0-PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB, or searchSpaceSIB1 in PDCCH-ConfigCommon, or searchSpaceZero in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by SI-RNTI on the primary cell of the MCG; Type 0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by SI-RNTI on the primary cell of the MCG; Type 1-PDCCHCSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell; and Type 2-PDCCH set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with a CRC scrambled by P-RNTI on the primary cell of the MCG. CSS sets; Type 3-PDCCH CSS sets configured only for primary cells, C-RNTI, MCS-C-RNTI, or CS-RNTI, with a SearchSpace of searchSpaceType=common in PDCCH-Config (PDCCH-Config); and USS sets configured with a SearchSpace of searchSpaceType=ue-Specific in PDCCH-Config with a SearchSpace of searchSpaceType=ue-Specific in PDCCH-Config, with a SearchSpace of searchSpaceType=ue-Specific in PDCCH-Config, with a SearchSpace of searchSpaceType=ue-Specific in PDCCH-Config, with a SearchSpace of searchSpaceType=ue-specific ...

[0261] In the example, the wireless device is based on one or more PDCCH configuration parameters (e.g., based on...). Figure 27An exemplary implementation) determines the PDCCH monitoring timing on the active DL BWP, wherein one or more PDCCH configuration parameters include: PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring type within the time slot. For the search space set (SSs), if The wireless device is then identified as number n. f The frame number is There are PDCCH monitoring opportunities in the time slots. This refers to the number of time slots in a frame when configuring the parameter set μ. s These are PDCCH configuration parameters (e.g., based on...) Figure 27 The time slot offset indicated in the exemplary implementation. s These are PDCCH configuration parameters (e.g., based on...) Figure 27 The PDCCH monitoring cycle is indicated in the exemplary implementation. The wireless device receives the data from the time slot. Begin monitoring PDCCH candidate persistence T for the search space set s A series of consecutive time slots, and in the next k... s -T s During a consecutive time slot, PDCCH candidates are not monitored for the search space set s. In the example, the USS at CCE aggregation level L∈{1,2,4,8,16} is defined by the set of PDCCH candidates for CCE aggregation level L.

[0262] In the example, the wireless device determines, for the search space set s associated with CORESETp, the value n of the carrier indicator field. CI For the corresponding service cell's activity DL BWP, in time slots In the search space set, the PDCCH candidates The corresponding CCE index for aggregation level L is For any for Y p,-1 =n RNTI ≠0, for p mod 3=0A p =39827, for p mod 3 = 1A p =39829, for p mod 3 = 2A p =39839, and D=65537; i=0,...,L-1; In CORESETp, N CCE,p This refers to the number of CCEs, numbered from 0 to N. CCE,p -1; If the wireless device is configured with the CrossCarrierSchedulingConfig field for monitoring the serving cell on its PDCCH, then nCI It is the carrier indicator field value; otherwise, including for any CSS, n CI =0; in The wireless device is configured to work with n CI For the corresponding serving cell, the number of PDCCH candidates monitored at the aggregation level L for the search space set s; for any CSS, For USS, It is the n of all configurations that pervade the CCE aggregation level L for the search space set s. CI value The maximum value; and used for n RNTI The RNTI value is C-RNTI.

[0263] In the example, the wireless device can monitor a set of PDCCH candidates based on configuration parameters of a search space set that includes multiple search spaces (SSs). The wireless device can monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. This can be based on... Figure 26 The exemplary implementation scheme is used to configure CORESET. Monitoring may include decoding one or more PDCCH candidates from a set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. Possible DCI formats may be based on Figure 23 Exemplary implementations.

[0264] Figure 23 An example of a DCI format is shown, which can be used by a base station to transmit control information to a radio device, or by the radio device to perform PDCCH monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In the example, DCI format 0_0 can be used to schedule PUSCHs in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCHs in a cell, or to indicate CG-DFI (Configured Allowed Downlink Feedback Information) for configured allowed PUSCHs, etc. The DCI formats that radio devices can monitor in the SS can be configured.

[0265] Figure 24AAn example of configuration parameters for the Primary Information Block (MIB) of a cell (e.g., PCell) is shown. In the example, the radio device can receive the MIB via the PBCH based on the received Primary Synchronization Signal (PSS) and / or Secondary Synchronization Signal (SSS). The MIB configuration parameters may include six bits of the System Frame Number (SFN), subcarrier spacing indication (subCarrierSpacingCommon), frequency domain offset in the number of subcarriers between the SSB and the entire resource block grid (ssb-SubcarrierOffset), an indication of whether the cell is barred (cellBarred), DMRS position indication (dmrs-TypeA-Position), parameters of the PDCCH CORESET and SS including the common CORESET (pdcch-ConfigSIB1), common search space, and necessary PDCCH parameters, etc.

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

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

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

[0269] Figure 24C An example configuration for SS#0 is shown. For example... Figure 24CAs shown, based on the integer value of searchSpaceZero, the wireless device can 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 for each slot.

[0270] In the example, based on the received MIB, the wireless device can monitor the PDCCH via SS#0 of CORESET#0 for receiving the DCI of Scheduling System Information Block 1 (SIB1). The SIB1 message can be based on... Figure 25 This is achieved through an exemplary implementation. The wireless device can receive a DCI with a CRC scrambled using a System Information Radio Network Temporary Identifier (SI-RNTI) specifically used for receiving SIB1.

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

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

[0273] In the example, the DownlinkConfigCommonSIB IE can include parameters for paging channel configuration. These parameters can include the paging cycle value (T, represented by the defaultPagingCycle IE), a parameter (nAndPagingFrameOffset IE) indicating the total number of paging frames (PF) and paging frame offsets (PF_offset) in the paging DRX cycle, the total number of paging opportunities (PO) per PF (Ns), and a first PDCCH monitoring opportunity indication parameter (firstPDCCH-MonitoringOccasionofPOIE) indicating the first PDCCH monitoring opportunity for each PO of the PF. Based on the PCCH configuration parameters, the wireless device can, for example, base its configuration on... Figure 28A and / or Figure 28B An exemplary implementation is provided for monitoring the PDCCH in order to receive paging messages.

[0274] In the example, the parameter first-PDCCH-MonitoringOccasionOfPO can be signaled in SIB1 for paging in the initial DL BWP. For paging in DLBWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO can be signaled in the corresponding BWP configuration.

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

[0276] like Figure 26As 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 may not 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 within the BWP of the serving cell. A CORESET can be associated with a coresetPoolIndex, which indicates the CORESET pool. A CORESET can be associated with a duration parameter (e.g., duration), which indicates the continuous duration of the CORESET in sign count. In the example, as... Figure 26 As shown, the configuration parameters of a CORESET may include at least one of the following: frequency resource indicators (e.g., frequencyDomainResources), CCE-REG mapping type indicators (e.g., cce-REG-MappingType), multiple TCI states, indicators indicating the presence of TCIs in the DCI, etc. A frequency resource indicator comprising several bits (e.g., 45 bits) can indicate frequency domain resources, with each bit corresponding to a group of 6 RBs, where the grouping begins with the first RB group in the BWP of the cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit may correspond to the first RB group in the BWP, and so on. A bit set to 1 indicates that the RB group corresponding to that bit belongs to the frequency domain resources of the CORESET. Bits corresponding to a group of RBs not fully included in the BWP in which the CORESET is configured may be set to zero.

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

[0278] In the example, a wireless device in RRC_IDLE or RRC_INACTIVE state can periodically monitor paging opportunities (POs) to receive paging messages for that wireless device. Before monitoring a PO, a wireless device in RRC_IDLE or RRC_INACTIVE state can wake up at the time preceding each PO to prepare and / or power on all components to prepare for data reception (warm-up). The interval between wake-up and PO can be long enough to accommodate all processing requirements. After warm-up, the wireless device can perform timing capture and coarse synchronization from the SSB, frequency and time tracking, time and frequency offset compensation, and / or local oscillator calibration. Afterward, the wireless device can monitor the PDCCH for paging DCI at one or more PDCCH monitoring opportunities based on the configuration parameters of the PCCH configuration configured in SIB1. The configuration parameters of the PCCH configuration can be based on the above regarding... Figure 25 The exemplary implementation described herein shall be used to achieve this.

[0279] Figure 28A An example of paging reception (or monitoring) is shown. In this example, the wireless device can use DRX for paging monitoring in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. The wireless device can monitor the PO in each DRX cycle. Figure 28AAs shown, the DRX cycle can have a radio frame length (T), which can be configured in the PCCH configuration. A PO can include a set of PDCCH monitoring opportunities. A PO can include multiple time slots (e.g., subframes or OFDM symbols) in which paging DCIs can be transmitted. A paging frame (PF) can be a radio frame and can contain one or more POs or the start point of a PO.

[0280] In the example, the wireless device can determine the radio frame for the PF based on the configuration parameters of the PCCH configuration (e.g., T, N, PF_offset) and the wireless device's identifier (UE_ID). The wireless device can determine whether a radio frame with a radio frame number (SFN) includes the PF for the wireless device based on whether (SFN+PF_offset)modT = (T div N)*(UE_ID mod N).

[0281] In the example, within each PF, the wireless device can determine the PO index (i_s) based on the configuration parameters configured in the PCCH (e.g., N, Ns) and the wireless device's identifier (UE_ID). The wireless device can determine the PO index (i_s) as floor(UE_ID / N) mod Ns.

[0282] In the example, the UE_ID of a wireless device can be determined based on its 5G-S-TMSI. The 5G-S-TMSI can be a 48-bit string. In the formulas above (PF calculation and PO calculation), the 5G-S-TMSI can be interpreted as a binary number, where the leftmost bit represents the most significant bit. If the wireless device does not have a 5G-S-TMSI, for example, when the wireless device has not yet registered on the network, the wireless device can use UE_ID = 0 as a default identifier to determine the PF and i_s.

[0283] In the example, after determining the PO and PF in the DRX loop, the wireless device can determine the PDCCH monitoring timing. The wireless device can determine the PDCCH monitoring timing for paging based on the paging PDCCH configuration parameters in SIB1. The paging PDCCH configuration parameters may include at least one of the following: pagingSearchSpace, firstPDCCH-MonitoringOccasionOfPO, and nrofPDCCH-MonitoringOccasionPerSSB-InPO, etc.

[0284] In the example, when SearchSpaceId=0 is configured for pagingSearchSpace, the PDCCH monitoring timing for paging can be the same as the PDCCH monitoring timing for other system information (e.g., RMSI). When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns=1, only one PO starts paging from the first PDCCH monitoring timing in the PF. For Ns=2, the PO is in either the first half-frame (i_s=0) or the second half-frame (i_s=1) of the PF.

[0285] In the example, when a SearchSpaceId other than 0 is configured for pagingSearchSpace, the wireless device can monitor the (i_s+1)th PO, where i_s is determined based on the exemplary implementation described above. In the example, the PO can include a set of 'S*X' consecutive PDCCH monitoring opportunities, where 'S' is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1, and X is nrofPDCCH-MonitoringOccasionPerSSB-InPO (if configured), otherwise equal to 1.

[0286] In the example, the [x*S+K]th PDCCH monitoring timing in the PO can correspond to the Kth transmitted SSB, where x = 0, 1, ..., X-1, and K = 1, 2, ..., S.

[0287] In the example, the PDCCH monitoring timings that do not overlap with the UL symbol (determined according to tdd-UL-DL-ConfigurationCommon) can be sequentially numbered from zero, starting with the first PDCCH monitoring timing from the PF. When firstPDCCH-MonitoringOccasionOfPO exists, the starting PDCCH monitoring timing number of the (i_s+1)th PO can be the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s*S*X. If X>1, the wireless device may not need to monitor subsequent PDCCH monitoring timings of that PO when it detects a PDCCH transmission addressed to the P-RNTI within its PO.

[0288] In the example, during multi-beam operation, the wireless device can determine to repeat the same paging message and the same short message in all transmitted beams. The selection of the beam used to receive the paging message and short message can be determined by the UE-specific implementation. The paging message can be the same for both RAN-initiated and CN-initiated paging.

[0289] In the example, after determining the PDCCH monitoring timing for the PF's PO, the radio device can monitor the PDCCH to receive the DCI for a scheduled paging message. In response to receiving the DCI, the radio device can retrieve paging information. If the radio device's UE ID is included in the paging message, the radio device can perform subsequent processing. The radio device can initiate an RRC connection restoration procedure upon receiving a paging initiated by the RAN. If the radio device receives a paging initiated by the CN while in the RRC_INACTIVE state, the radio device can move to RRC_IDLE and notify the NAS. If the radio device's UE ID is not included in the paging message, the radio device can return to sleep, for example, without changing the RRC state (remaining in the RRC_IDLE and / or RRC_INACTIVE states).

[0290] Figure 28B An example of paging monitoring for different wireless devices is shown. In the example, the PCCH configuration parameters can indicate T=64 frames, N=32 frames (e.g., half a frame), PF_offset=1, and Ns=2. Figure 28B As shown, there can be four wireless devices (e.g., UE1 with ID=40, UE2 with ID=41, UE3 with ID=104, and UE4 with ID=105). Based on Figure 28A In an exemplary implementation, each wireless device can determine the PO of the PF in each DRX cycle. In the example, UE1 can monitor the PO in SFN=16 of the first DRX cycle and the PO in SFN=78 of the second DRX cycle. UE2 can monitor the PO in SFN=18 of the first DRX cycle and the PO in SFN=80 of the second DRX cycle. Figure 28B As shown, based on the PO and PF calculation formulas above, UE3 can share the same PO with UE1, and UE4 can share the same PO with UE2. Sharing the same PO with multiple radio devices grouped based on UE_ID and PCCH configuration parameters can reduce the signaling overhead of paging PDCCH transmission. Each radio device within the same group (e.g., sharing the same PO in the same PF) can also check whether the radio device is being paged based on whether the paging message scheduled by the paging DCI received in the PO includes the radio device's UE ID.

[0291] In the example, based on the PF and PO determination formulas shown above, the wireless device can wake up to periodically monitor the PO for each DRX cycle (e.g., including time / frequency synchronization, blind PDCCH decoding, PDSCH reception of paging messages, etc.), even if the base station does not have a paging message for the wireless device. In some systems, the probability of a wireless device being paging can be as low as 10%. In this case, the wireless device may waste power used for waking up for most of the time during paging monitoring, even though there is no paging message for the wireless device. Some techniques can improve the power consumption of paging monitoring by introducing an Early Paging Indication (PEI) before the actual PO. The PEI can be a signal sequence, such as SSB / CSI-RS / TRS, etc. The PEI can be included in the DCI via the PDCCH. The PEI can indicate whether the wireless device should wake up to monitor the paging PDCCH in the PO. In response to the PEI indicating that the wireless device should monitor the PO, the wireless device can wake up to monitor the PO. Otherwise, the wireless device can skip monitoring the PO. Based on this technique, the base station can dynamically indicate whether the wireless device should monitor the PO. Wireless devices can reduce the power consumption when receiving paging messages. In the example, the wireless device can behave differently when it does not detect a PEI.

[0292] Figure 29A An example of PEI processing is shown. In the example, the wireless device can monitor the PEI (e.g., a signal sequence or PDCCH) at a monitoring time prior to the PO (e.g., based on the above regarding...). Figure 28A and / or Figure 28B The exemplary implementation described is used to determine the PO. In response to receiving a PEI instructing the wireless device to monitor the PO (e.g., in the case where the base station decides to page the wireless device), the wireless device can monitor the PO according to its PCCH configuration. In the example, for instance, if the base station decides not to page the wireless device, the wireless device may not receive the PEI. In response to not detecting / receiving a PEI, the wireless device may skip monitoring the PO. Not transmitting a PEI (or intentionally skipping a PEI) when there is no wireless device to be paged can reduce the base station's signaling overhead and / or reduce conflicts between PEI transmission and other downlink signal (PDCCH / PDSCH) transmissions. Not monitoring the PO (or skipping monitoring the PO) when the wireless device does not detect a PEI can reduce the power consumption of the wireless device.

[0293] Figure 29B An example of PEI processing is shown. In the example, the wireless device can monitor the PEI (e.g., a signal sequence or PDCCH) at a monitoring time prior to the PO (e.g., based on the above regarding...). Figure 28A and / or Figure 28BThe exemplary implementation described is used to determine the PO. In response to receiving a PEI indicating that the radio device should monitor the PO (e.g., in the case where the base station decides to page the radio device), the radio device can monitor the PO according to the PCCH configuration. In response to receiving a PEI indicating that the radio device should not monitor the PO (e.g., in the case where the base station decides not to page the radio device), the radio device can skip monitoring the PO. In the example, for example, if the base station decides to discard the transmission of the PEI due to a conflict with other channels, the radio device can not receive the PEI. In response to not detecting / receiving a PEI, the radio device can monitor the PO according to the PCCH configuration. In the case where PEI transmission conflicts with other downlink signal (PDCCH / PDSCH) transmissions, the base station not transmitting the PEI can reduce the conflict between PEI transmission and other downlink signals. In the case where no PEI is detected, monitoring the PO can reduce the paging waiting time of the radio device.

[0294] In 5G systems, base stations can use multiple beams to transmit SSBs. For each SSB transmission, the base station can transmit paging DCIs at multiple PDCCH monitoring times to increase the reliability of delivering paging DCIs to radio devices. SSB transmissions can be based on the above... Figure 11A , Figure 11B , Figure 24A , Figure 24B and / or Figure 25 The exemplary implementation described is used to achieve this. To facilitate proper monitoring of the paging PDCCH by the wireless device, the base station may (e.g., in the SIB1 message) configure a first number (e.g., X) (e.g., as...). Figure 25 The first number (nrofPDCCH-MonitoringOccasionPerSSB-InPO IE) indicates the number of PDCCH monitoring opportunities for each of the multiple SSBs in the paging event, and the second number (e.g., S) of the actual transmitted SSBs. Figure 25 The SSB-PositionsInBurst IE diagram is shown. Based on the first and second quantities, the wireless device can determine the total number of PDCCH monitoring opportunities in the paging opportunity as X*S. Additionally, the base station can further indicate the time offset (e.g., as shown in the diagram). Figure 25The firstPDCCH-MonitoringOccasionOfPO (as shown) indicates the first PDCCH monitoring opportunity associated with the start frame of the paging opportunity out of the total number of PDCCH monitoring opportunities. Based on nrofPDCCH-MonitoringOccasionPerSSB-InPO, ssb-PositionsInBurst, and firstPDCCH-MonitoringOccasionOfPO, the radio device can determine the correct PDCCH monitoring opportunity for receiving the paging DCI, which is scheduled for the radio device's paging message.

[0295] In the example, to further reduce the power consumption of wireless devices monitoring the paging PDCCH for receiving paging messages, there are some recommendations (e.g., such as...). Figure 29A and / or Figure 29B As shown, an Early Paging Indication (PEI) is introduced before the paging timing to indicate whether the radio device can skip monitoring the paging PDCCH. To improve the reliability of PEI transmission in high-frequency scenarios, the base station can use multiple beams to transmit the PEI.

[0296] In this disclosure, the PDCCH monitoring timing (MO) for receiving (included in DCI) PEI can be referred to as PEIPDCCH MO. The PDCCH MO for receiving paging DCI can be referred to as paging PDCCH MO.

[0297] In the example, the base station can configure the first PEIPDCCH MO (e.g., firstPDCCH - Monitoring OccasionOfPEI) among multiple PEIPDCCH MOs used to receive PEI during PEI timing. The first PEIPDCCH MO can be configured separately from the first paging PDCCH MO (e.g., firstPDCCH - Monitoring OccasionOfPO) among multiple paging PDCCH MOs used to receive paging DCI during paging timing. Each PEIPDCCH MO corresponds to a specific SSB among multiple SSBs. However, existing technologies may not support configuring multiple PEIPDCCH MOs within a single SSB. Existing technologies may reduce the transmission opportunities for PEI within an SSB, and thus increase PEI transmission latency.

[0298] In an example of implementing the prior art, the base station may configure a first quantity (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPEI) in the SIB1 message, indicating the number of PEIPDCCH MOs for each of a plurality of SSBs used to receive PEI during the PEI timing. This first quantity may be configured separately from a second quantity (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO), indicating the number of paging PDCCH MOs for each of a plurality of SSBs used to receive paging DCI during the paging timing. However, configuring both values ​​separately—a first value indicating the number of PEIPDCCH MOs for each SSB for PEI and a second value indicating the number of paging PDCCH MOs for each SSB for paging—may increase the signaling overhead of SIB1 message transmission, since the SIB1 message is broadcast to all radio devices in the cell and is transmitted with limited radio resources. The prior art may increase signaling overhead and / or increase the power consumption of radio devices detecting the SIB1 message.

[0299] Therefore, it is necessary to improve the reliability of PEI transmission and / or improve the signaling overhead of SIB1 transmission configuration PEI parameters and / or reduce the power consumption of wireless devices receiving SIB1 messages when configuring multiple SSBs.

[0300] Exemplary implementations may include an SIB1 message including configuration parameters of a PEI, received by a wireless device and / or transmitted by a base station. The configuration parameters may include a first quantity indicating the number of PDCCH MOs for each SSB in the paging time. The configuration parameters may include a first position of the starting PDCCH MO in the PDCCH MOs of the PEI time and a second position of the starting PDCCH MO in the PDCCH MO of the paging time. The wireless device may start from the first position and monitor a first PDCCH (e.g., PEIPDCCH) on a second number of PDCCH MOs at the PEI time. The second quantity is determined based on the first quantity and the number of SSBs. For example, the second quantity may be the product of the first quantity and the quantity. The wireless device may receive the PEI based on monitoring the first PDCCH. In the example, in response to receiving a PEI indicating monitoring a paging time (or an indication to monitor a second PDCCH for receiving a paging DCI), the wireless device may start from the second position and monitor a second PDCCH on a second number of PDCCH MOs at the paging time. During monitoring the second PDCCH, the wireless device may receive a DCI that schedules paging messages for the wireless device. In the example, in response to receiving a PEI indicating not to monitor paging times, the wireless device can start from the second location and skip monitoring the second PDCCH on a second number of PDCCH MOs of paging times.

[0301] In an exemplary implementation, when multiple PDCCH MOs are supported in a single SSB out of multiple SSBs, the radio device can determine that the total number of PEIPDCCH MOs in a PEI timing is the same as the total number of paging PDCCH MOs in a paging timing. In an exemplary implementation, when multiple PDCCH MOs are supported in a single SSB out of multiple SSBs, the base station can determine that the total number of PEIPDCCH MOs in a PEI timing is the same as the total number of paging PDCCH MOs in a paging timing. In an exemplary implementation, the total number of PDCCH MOs in either a PEI timing or a paging timing is determined as the product of the number of SSBs (S) and the number of PDCCH MOs (X) per SSB, where S and X are configured in the SIB1 message.

[0302] By implementing the exemplary implementation, the base station can, for example, reduce the signaling overhead of configuring PEI parameters by configuring a single value (X) for both PEI and paging, thereby reducing the power consumption of the wireless device receiving SIB1 messages. By implementing the exemplary implementation, the base station can configure separate starting PDCCH MOs for PEI timing and paging timing to flexibly adjust the transmission time of PEI and paging DCI in different radio frames.

[0303] Figure 30An exemplary implementation of PEI transmission for power saving is illustrated. In the example, the base station may transmit an RRC message (e.g., a MIB / SIB1 / SIB2 message) to the wireless device, including configuration parameters of PEI timing and paging timing. The configuration parameters may include a first quantity (e.g., Figure 30 In the context of paging, the first quantity (S) indicates the number of PDCCH MOs for each of the multiple SSBs during the paging event. The first quantity can be based on... Figure 25 This can be achieved through exemplary implementations (e.g., nrofPDCCH-MonitoringOccasionPerSSB-InPO). Configuration parameters may include a second number indicating the total number of SSBs actually transmitted (e.g., ...). Figure 30 (X in the original text). The wireless device can use S and X to determine the total number of PDCCH MOs for both PEI timing and paging timing (although the first number is only configured for paging timing).

[0304] exist Figure 30 In the example, based on S and X, the wireless device can determine M PEIPDCCH MOs in the PEI timing and N paging PDCCH MOs in the paging timing, where M = N = S * X.

[0305] In the example, the configuration parameters may also include an indication of the position of the starting PDCCH MO among the M PEIPDCCH MOs (e.g., ...). Figure 30 The configuration parameters can also include the position indication of the starting PDCCH MO among the N paging PDCCH MOs (e.g., as shown in the firstPDCCH-MonitoringOccasionOfPEI). Figure 30 The first PDCCH (Monitoring Occasion of PO) is shown.

[0306] In the example, the configuration parameters may also include the time offset between the start frame of the paging timing and the start frame of the PEI timing (e.g., as shown in the example). Figure 30 (PEI-F_offset shown).

[0307] In the example, the configuration parameters may also include configuration parameters for the PEI search space and the paging search space. The search space can be based on the above regarding... Figure 27 The exemplary implementation described herein shall be used to achieve this.

[0308] In the example, for instance, based on the above regarding Figure 25 The exemplary implementation described may further include parameters for paging timing (e.g., T indicating the paging / DRX cycle, PF_offset indicating the paging frame offset, etc.).

[0309] In the example, based on configuration parameters, the wireless device can determine M PEIPDCCH MOs starting from the position indicated by firstPDCCH-MonitoringOccasionOfPEI, such as M = S*X. The wireless device can monitor the PEIPDCCH (or the PDCCH used to receive the PEI) on the M PEIPDCCH MOs via the PEI search space. The wireless device can receive the DCI including the PEI.

[0310] In the example, based on configuration parameters, in response to receiving a PEI indicating the timing of paging monitoring (or monitoring of the paging PDCCH), the wireless device can determine N paging PDCCH MOs starting from the position indicated by firstPDCCH-MonitoringOccasionOfPO, such as N = S*X. The wireless device can monitor the paging PDCCH (or the PDCCH used to receive the paging DCI) on the N paging PDCCH MOs via the paging search space. The wireless device can receive the DCI that schedules paging messages for the wireless device.

[0311] By implementing the exemplary implementation, configuring a single value indicating the number of PDCCH MOs for each SSB for PEI timing and paging timing, and configuring two separate values ​​for the starting PDCCH MO in PEIPDCCH MO and the starting PDCCH MO in paging PDCCH MO, the wireless device can correctly position the PEIPDCCH MO and paging PDCCH MO when multiple PDCCH MOs are supported in the SSB and when the base station has different signal (DL / UL, PDCCH / PDSCH / CSI-RS / SSB) configurations in the PEI frame (where the PEI timing occurs) and the paging frame.

[0312] In the example, when different radio frames are configured with different TDD formats, the PEIPDCCH timing can overlap with the uplink transmission on the first symbol of the PEI frame. Similarly, in the example, the paging PDCCH timing can overlap with the uplink transmission on the second symbol of the paging frame. The position of the first symbol within the PEI frame may differ from the position of the second symbol within the paging frame. When multiple radio frames are configured with TDD formats, to conserve power during PEI reception, it is necessary to define the behavior of the wireless device for PDCCH monitoring to receive PEI.

[0313] In the example, the M PDCCH MOs determined based on the PEI timing (e.g., by implementing the above regarding...) Figure 30The exemplary implementation described herein allows the wireless device to configure TDD based on the TDD configuration parameters indicated by the RRC message (e.g., such as...). Figure 25 The tdd-UL-DL-ConfigurationCommon (as shown) is used to further determine whether the first PDCCH MO among the M PDCCH MOs of the PEI timing in the PEI radio frame overlaps with the first uplink transmission. In response to the first PDCCH MO overlapping with a UL symbol (determined according to tdd-UL-DL-ConfigurationCommon), the radio device can skip monitoring the first PDCCH MO among the M PDCCH MOs. After excluding PDCCH MOs overlapping with UL symbols, the radio device can sequentially number the M PDCCH MOs starting from zero, beginning with the initial PDCCH monitoring timing of the PEI timing (indicated by firstPDCCH-MonitoringOccasionOfPEI). The radio device can monitor the PEI PDCCH based on the numbering of the M PDCCH MOs.

[0314] In the example, the N PDCCH MOs determined based on the paging timing (e.g., by implementing the above regarding...) Figure 30 The exemplary implementation described herein allows the wireless device to configure TDD based on the TDD configuration parameters indicated by the RRC message (e.g., such as...). Figure 25 The tdd-UL-DL-ConfigurationCommon (as shown) is used to further determine whether the second PDCCH MO among the N PDCCH MOs in the paging timing in the paging radio frame overlaps with the second uplink transmission. In response to the second PDCCH MO overlapping with the UL symbol (determined according to tdd-UL-DL-ConfigurationCommon), the radio device can skip monitoring the second PDCCH MO among the N PDCCH MOs. After excluding PDCCH MOs overlapping with the UL symbol, the radio device can sequentially number the N PDCCH MOs starting from zero, beginning with the first PDCCH monitoring timing in the paging timing (indicated by firstPDCCH-MonitoringOccasionOfPO). In response to receiving a PEI indicating to monitor the paging PDCCH, the radio device can monitor the paging PDCCH of the paging DCI based on the numbering of the N PDCCH MOs.

[0315] By implementing the exemplary embodiment, the wireless device can determine whether the PEIPDCCH MO overlaps with the UL symbol in the PEI timing based on the TDD configuration parameters of the SIB1 message, and separately and / or independently determine whether the paging PDCCH MO overlaps with the UL symbol in the paging timing. The exemplary embodiment can allow the base station to change the TDD configuration in different radio frames (e.g., a first frame including the PEI timing and a second frame including the paging timing), and allow the wireless device to correctly position the PEIPDCCH MO in the PEI frame (e.g., by omitting / skipping PDCCH monitoring on the PEIPDCCH MO overlapping with the UL symbol), and correctly position the paging PDCCH MO in the paging frame (e.g., by omitting / skipping PDCCH monitoring on the paging PDCCH MO overlapping with the UL symbol). Otherwise, by implementing the prior art where the wireless device can perform the check for overlap between the paging PDCCH MO and the UL symbol in the paging frame including the paging timing, the wireless device may incorrectly position the PEIPDCCH MO in the PEI frame, which may have different TDD configuration parameters than the paging frame. Existing technologies may not require wireless devices to perform checks to determine whether the PEIPDCCH MO overlaps with the UL symbol in a PEI frame that includes the PEI timing.

[0316] In the example, 5G systems can be used in connected industries that may require high flexibility, high productivity and efficiency, low maintenance costs, and high operational safety. Wireless devices in such environments can include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc. The requirements for these services may be higher than LPWA (e.g., LTE-MTC / NB-IoT), but lower than URLLC and eMBB in current 5G systems. In the example, the smart city vertical can cover data collection and processing to more effectively monitor and control urban resources and provide services to city residents. Surveillance cameras can be an important part of smart cities, factories, and / or industries. Wearable use cases can include smartwatches, electronic health-related devices, personal protective equipment (PPE), and medical monitoring devices used in public safety applications. One characteristic of the use cases can be small device size. Wireless devices deployed in connected industries, smart city verticals, and / or wearable use cases may have limited capabilities compared to general wireless devices (e.g., wireless devices capable of handling URLLC and / or eMBB). In this specification, a wireless device with limited capabilities (e.g., used in the connected industry, smart city verticals, wearable use cases, etc.) may be referred to as a RedCap UE compared to a wireless device with normal capabilities. A wireless device with normal capabilities may be referred to as a non-RedCap UE, or equivalently as a NorCap UE.

[0317] Figure 31 An example comparing the capabilities of a RedCap UE and a non-RedCap UE is shown. Due to implementation cost and power consumption considerations, a RedCap UE can support a limited set of configurations. In the example, a RedCap UE can be configured with at most one receive antenna compared to a non-RedCap UE configured with 2 or 4 receive antennas. A RedCap UE can support operation within 20MHz (e.g., in FR1) or 50MHz (e.g., in FR2) compared to a non-RedCap UE supporting 100MHz (in FR1) or 200MHz (in FR2). A RedCap UE may be able to loosely handle PDSCH / PUSCH within 16–20 symbols compared to a non-RedCap UE capable of strictly handling PDSCH / PUSCH within 8–10 symbols. A RedCap UE can support up to 2 layers of MIMO transmission compared to a non-RedCap UE supporting up to 4 layers of MIMO transmission. Compared to non-RedCap UEs that support full-duplex FDD transmission (in which case the UE can transmit in the first frequency band and receive in the second frequency band simultaneously), RedCap UEs can support half-duplex FDD transmission (in which case the UE cannot transmit in the first frequency band and receive in the second frequency band simultaneously).

[0318] In the prior art, paging configurations (e.g., search space, CORESET, PCCH configuration) can be (e.g., via such as...) Figure 25 , Figure 26 and / or Figure 27 The SIB1 shown is broadcast to all radio devices. Radio devices in the RRC_INACTIVE state or the RRC_IDLE state (different from the RRC_CONNECTED state) are not connected to the base station; in this case, the base station may not be able to transmit radio device-specific messages to the radio device. Radio devices in the RRC_INACTIVE or RRC_IDLE states can periodically monitor the PO (Point of Purchase) in each DRX cycle based on the paging configuration and the radio device's UE_ID. To save power consumption when monitoring the PO, some existing technologies disclose power-saving mechanisms based on Early Paging Indication (PEI).

[0319] In some existing technologies, a base station may transmit a PEI (Paging Information Indicator) before transmitting a paging DCI (Paging Control Message), which schedules paging messages for a radio device or a group of radio devices. The PEI can indicate the existence of a paging message for that radio device or group of radio devices. Based on receiving the PEI transmitted by the base station and before starting PO (Position Request) monitoring, the radio device can determine whether to skip monitoring the PO. The PEI can be transmitted as a signal sequence (e.g., SSB / CSI-RS / TRS) or via PDCCH in the DCI.

[0320] In the example, the base station can transmit a common RRC message (e.g., in SIB1) indicating configuration parameters (e.g., search space, CORESET, DCI format, etc.) for the PDCCH dedicated to PEI. Because the common RRC message is broadcast, the PEI configuration parameters can be applied to all radio devices in either the RRC_IDLE or RRC_INACTIVE state. The PEI configuration can differ from the wake-up (or power-saving) configuration of radio devices in the RRC_CONNECTED state. The wake-up configuration of radio devices in the RRC_CONNECTED state can be transmitted in a radio device-specific RRC message.

[0321] In the example, RedCap wireless devices may be more power-constrained than non-RedCap wireless devices. RedCap wireless devices can implement power-saving operations for paging monitoring in either the RRC_INACTIVE or RRC_IDLE states. RedCap wireless devices can implement PEI-based power-saving operations for paging monitoring.

[0322] However, due to the limited capabilities of RedCap radio devices, based on existing PEI-based power-saving operations, RedCap radio devices may not be able to receive PEI. In the example, if PEI is transmitted in a frequency resource extended over a bandwidth greater than the maximum bandwidth supported by the RedCap radio device, the RedCap radio device may not receive / detect the PEI. In the example, if PEI is transmitted in a search space with a small aggregation level, the RedCap radio device may not receive / detect the PEI due to reduced reception diversity gain caused by a single receive antenna configured for the RedCap radio device. In the example, if the gap between the PEI and the PO is shorter than the processing capacity of the RedCap radio device, the RedCap radio device may not be able to process the PEI quickly enough to detect the PO after receiving it.

[0323] Given the capability differences between RedCap and non-RedCap wireless devices, for example, a single PEI configuration blindly broadcast to all wireless devices in RRC_IDLE or RRC_INACTIVE states may not be received by either RedCap or non-RedCap wireless devices. Based on existing PEI technology, RedCap wireless devices may not detect the PEI. If, when a RedCap wireless device does not detect the PEI and the PEI notifies it that a paging message is available for that RedCap wireless device, and the RedCap wireless device skips PO monitoring, the lack of PEI detection may increase the paging message delivery latency. If, when a RedCap wireless device does not detect the PEI and the PEI notifies it that no paging message is available for that RedCap wireless device, and the RedCap wireless device monitors the PO, the lack of PEI detection may increase the power consumption of the wireless device. When monitoring paging timing, it is necessary to reduce the power consumption and / or paging message latency of the RedCap wireless device.

[0324] In an exemplary implementation, for PEI transmission, the base station can configure a separate initial BWP on the cell. This initial BWP may include, for example, a first initial BWP for PEI configuration and paging for RedCap radio devices, and a second initial BWP for PEI configuration and paging for non-RedCap radio devices. RedCap radio devices can receive both PEI and paging DCI on the first initial BWP of the cell. Non-RedCap radio devices can receive both PEI and paging DCI on the second initial BWP of the cell. RedCap radio devices may not switch from the first initial BWP to the second initial BWP to receive PEI. After receiving PEI in the second initial BWP, RedCap radio devices may not switch from the second initial BWP to receive paging DCI. The PEI search space can be configured on both the first and second initial BWPs. When the radio device is a RedCap radio device, it can monitor the PEIPDCCH according to the configuration parameters of the PEI search space on the first initial BWP. When the radio device is a non-RedCap radio device, it can monitor the PEIPDCCH according to the configuration parameters of the PEI search space on the second initial BWP.

[0325] In an exemplary implementation, the base station can separate the PEI configurations (search space, CORESET, DCI format, RNTI, etc.) of RedCap and non-RedCap wireless devices. RedCap wireless devices can monitor PEI based on a PEI configuration dedicated to them. For example, when a RedCap wireless device (e.g., a sensor, camera, wearable device, etc.) has more uplink data transmission than downlink data transmission (or is uplink-centric), it may have a lower paging rate than a non-RedCap wireless device. This exemplary implementation can improve the power consumption of RedCap wireless devices.

[0326] In an exemplary implementation, for example, based on the different capabilities of different wireless device types, the base station can configure different gaps between PEI and PO for different wireless device types (e.g., RedCap type, non-RedCap type, etc.). This exemplary implementation can reduce the likelihood of not detecting a paging DCI after receiving a PEI from a RedCap wireless device.

[0327] In an exemplary implementation, when a PEI is not detected, the base station can configure different processing behaviors for RedCap and non-RedCap types. In response to the lack of a PEI, the base station can instruct RedCap radio devices to skip monitoring of POs (or any POs in the PF). For example, when a RedCap radio device is power-limited and / or data-centric, skipping PO monitoring in response to the lack of a PEI can reduce paging power consumption. In response to the lack of a PEI, the base station can instruct non-RedCap radio devices to monitor POs (or any POs in the PF). By monitoring POs (in the PF) in response to the lack of a PEI, non-RedCap radio devices can reduce paging message delivery latency.

[0328] Figure 32 An exemplary implementation of PEI-based power saving for paging wireless devices is illustrated. In this exemplary implementation, a base station may transmit one or more RRC messages, including configuration parameters of the PEI configuration, to the wireless device (or multiple wireless devices). These one or more RRC messages may be cell common messages including MIB, SIB1, SIB2, etc. These one or more RRC messages may be broadcast to multiple wireless devices, including the wireless device. Based on the above... Figure 6 In the exemplary implementation described, the wireless device (or multiple wireless devices) may be in the RRC_INACTIVE state or in the RRC_IDLE state.

[0329] In an exemplary implementation, the PEI configuration may include at least a first PEI configuration dedicated to RedCap wireless device types (or wireless device categories) and at least a second PEI configuration dedicated to non-RedCap wireless device types (or wireless device categories).

[0330] In an exemplary implementation, for a transmission of a first DCI including a first PEI, configuration parameters of at least the first PEI configuration (dedicated to the RedCap radio device type) may indicate: a first CORESET of the first PDCCH, one or more first SSBs associated with the first CORESET, one or more first search spaces, a first DCI format, a first PEI-RNTI dedicated to receiving the first PEI, and a first time offset between the first PEI and the first PO. The first PO may be configured for the RedCap radio device type. In the example, the first CORESET of at least the first PEI configuration may be predefined (or configured) as CORESET#0, for example, to ensure that RedCap radio devices with limited capabilities on supported bandwidth receive the first PEI. The first PEI may include multiple indications, each associated with a group of RedCap type radio devices, and indicating whether that group of radio devices should monitor the PO.

[0331] In an exemplary implementation, for a transmission of a second DCI including a second PEI, configuration parameters (dedicated to non-RedCap radio device types) of at least the second PEI configuration may indicate: a second CORESET of the second PDCCH, one or more second SSBs associated with the second CORESET, one or more second search spaces, a second DCI format, a second PEI-RNTI dedicated to receiving the second PEI, and a second time offset between the second PEI and the second PO. The second PO may be configured for non-RedCap radio device types. The second PEI may include multiple indications, each associated with a group of non-RedCap type radio devices, and indicating whether that group of radio devices should monitor the PO.

[0332] In an exemplary implementation, one or more first search spaces may be associated with higher aggregation levels (e.g., 8, 16, 32, etc.) compared to one or more second search spaces. The one or more first search spaces may be configured with longer monitoring periods than the one or more second search spaces. The first PEI-RNTI may differ from the second PEI-RNTI.

[0333] In an exemplary implementation, by configuring two PEI configurations, one for RedCap radio device types and the other for non-RedCap radio device types, when the base station determines it is paging a RedCap radio device, the base station can flexibly transmit a first PEI based on a first PEI configuration dedicated to the RedCap radio device type, and / or when the base station determines it is paging a non-RedCap radio device, the base station can transmit a second PEI based on a second PEI configuration dedicated to the non-RedCap radio device type. The first PEI configuration can be configured to enable RedCap radio devices to receive / detect the first PEI. The second PEI configuration can be configured to enable non-RedCap radio devices to receive / detect the second PEI. The first and second PEI configurations can be configured separately and / or independently. This exemplary implementation can improve the robustness of PEI transmission for RedCap radio devices and / or the efficiency of PEI transmission for non-RedCap radio devices.

[0334] based on Figure 32 Exemplary implementations that separate the PEI configuration between RedCap and non-RedCap wireless devices can improve the power consumption of RedCap wireless devices. For example, when a RedCap wireless device (e.g., a sensor, camera, wearable device, etc.) has more uplink data transmission than downlink data transmission, the RedCap wireless device may have a lower paging rate than a non-RedCap wireless device. By implementing the prior art, RedCap wireless devices do not need to monitor the PEI with the same monitoring cycle as non-RedCap wireless devices, even if the RedCap wireless device has a lower paging rate than the non-RedCap wireless device.

[0335] In an exemplary implementation, based on the RRC message, the wireless device can determine which PEI configuration in the PEI configuration the wireless device should monitor based on. If the wireless device is a RedCap wireless device, the wireless device can determine to monitor a first PEI based on a first PEI configuration. If the wireless device is a non-RedCap wireless device, the wireless device can determine to monitor a second PEI based on a second PEI configuration.

[0336] In the example, monitoring PEI based on PEI configuration may include monitoring PDCCHs on one or more search spaces of the CORESET for receiving DCIs that include the PEI. In the PEI configuration, RRC messages may indicate the DCI format and RNTI associated with the DCI, one or more search spaces, and / or the CORESET. In this specification, the PDCCH on which the DCI including the PEI is received may be referred to as the PEIPDCCH. The PDCCH on which the DCI scheduling paging messages is received may be referred to as the paging PDCCH. The PEIPDCCH and paging PDCCH can be configured separately and independently. In the example, the PEI PDCCH may be associated with the paging PDCCH.

[0337] In the example, the wireless device can monitor the PEIPDCCH during one of multiple PEIPDCCH monitoring times associated with the PF. The PEIPDCCH monitoring times for each PEI can be numbered sequentially from zero, starting with the first PEIPDCCH monitoring time for that PEI in the PF. The total number of PEIPDCCH monitoring times in the PF can be determined based on the PDCCH configuration parameters configured for the first PEI. The index of the PEIPDCCH monitoring times from multiple PEIPDCCH monitoring times can correspond to the index (i_s) of the PO associated with the wireless device. This can be based on the above regarding... Figure 28A and / or Figure 28B The exemplary implementation described determines the index (i_s) of the PO.

[0338] In an exemplary implementation, the base station may transmit an RRC message including a first (or first) PEIPDCCH monitoring occasion indication (firstPDCCH-MonitoringOccasionOfPEI) for multiple POs in the PF, each PO being associated with a corresponding indication in the indication. The wireless device may determine that the first PEIPDCCH monitoring occasion number of the (i_s+1)th PO can be the (i_s+1)th value of firstPDCCH-MonitoringOccasionOfPEI. For example, based on the above regarding... Figure 30 In the exemplary implementation described, firstPDCCH-MonitoringOccasionOfPEI can be configured separately and independently from firstPDCCH-MonitoringOccasionOfPO. The firstPDCCH-MonitoringOccasionOfPO configured in the PCCH IE can be used to determine the timing number for initiating paging PDCCH monitoring.

[0339] In an exemplary implementation, the [x*S+K]th PEIPDCCH monitoring timing corresponding to the PO can correspond to the Kth transmitted SSB, where x = 0, 1, ..., X-1, and K = 1, 2, ..., S. S can be the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1. X can be nrofPDCCH-MonitoringOccasionPerSSB-InPO (if configured), otherwise it can be equal to 1. S and X can be based on the above regarding... Figure 25 and Figure 30 The exemplary implementation described herein shall be used to achieve this.

[0340] In the example, in response to receiving a PEI indicating to monitor the paging PDCCH, the wireless device can, for example, base its actions on the above-mentioned... Figure 25 , Figure 28A , Figure 28B and / or Figure 30 The exemplary implementation described monitors the paging PDCCH at several PDCCH monitoring times during the paging time.

[0341] In the example, in response to receiving a PEI indicating not to monitor the paging PDCCH, the wireless device can, for example, base its actions on the above-mentioned... Figure 25 , Figure 28A , Figure 28B , Figure 29A , Figure 29B and / or Figure 30 The exemplary implementation described skips monitoring the paging PDCCH at several PDCCH monitoring times during the paging time.

[0342] In an exemplary implementation, the wireless device can reuse `firstPDCCH-MonitoringOccasionOfPO` to determine the start PEIPDCCH monitoring timing and the start paging PDCCH monitoring timing. The wireless device can determine that the start PEIPDCCH monitoring timing number for the (i_s+1)th PO from multiple PEIPDCCH monitoring timings can be the (i_s+1)th value of the `firstPDCCH-MonitoringOccasionOfPO` parameter. The wireless device can determine that the start paging PDCCH monitoring timing number for the (i_s+1)th PO from multiple paging PDCCH monitoring timings can be the (i_s+1)th value of the `firstPDCCH-MonitoringOccasionOfPO` parameter.

[0343] In an exemplary implementation, such as Figure 31As shown, based on the determined PEIPDCCH monitoring timing, search space, CORESET, DCI format, and / or PEI-RNTI, the radio device can monitor the PEIPDCCH to receive a first PEI dedicated to the RedCap radio device type. Since the radio device is a RedCap radio device type, the radio device can skip monitoring a second PEI dedicated to a non-RedCap radio device type. In response to detecting a first PEI that indicates the radio device should monitor a PO (or indicates the presence of a paging message for the radio device), the radio device can monitor the paging PDCCH to receive the paging DCI in the corresponding PO associated with the first PEI (e.g., a first PO dedicated to the RedCap radio device type). The radio device can skip monitoring a second PO dedicated to a non-RedCap radio device type. In the example, the radio device can receive the paging DCI while monitoring the paging PDCCH in the first PO. Based on the paging DCI, the radio device can receive a paging message including the radio device's UE_ID.

[0344] In the example, the wireless device can be a non-RedCap wireless device type. Based on the wireless device being a non-RedCap wireless device type, the wireless device can monitor a second PEI dedicated to the non-RedCap wireless device type and / or can skip monitoring a first PEI dedicated to the RedCap wireless device type. In response to detecting a second PEI that indicates the wireless device should monitor a PO (or indicates the presence of a paging message for the wireless device), the wireless device can monitor a paging PDCCH to receive a paging DCI in the corresponding PO associated with the second PEI (e.g., a second PO dedicated to the non-RedCap wireless device type). The wireless device can skip monitoring the first PO dedicated to the RedCap wireless device type. In the example, the wireless device can receive the paging DCI while monitoring the paging PDCCH in the second PO. Based on the paging DCI, the wireless device can receive a paging message including the wireless device's UE_ID.

[0345] based on Figure 32The exemplary implementation allows the base station to flexibly allocate radio resources for PEI and paging by separating the PEI configurations for RedCap radio device types (or RedCap types) and non-RedCap radio device types (or non-RedCap types). In the example, when a small number of RedCap radio devices are present, the base station can configure the same PEI (and / or paging) configuration parameters for both RedCap and non-RedCap types; this can be referred to as a shared PEI with shared paging configuration. In the example, when the base station considers PEI signaling overhead, the base station can configure the same PEI parameters for both RedCap and non-RedCap types, and configure different paging parameters for both RedCap and non-RedCap types; this can be referred to as a shared PEI with separate paging. In the example, when the base station considers paging signaling overhead, the base station can configure separate PEI parameters for both RedCap and non-RedCap types, and configure the same paging parameters for both RedCap and non-RedCap types; this can be referred to as a separate PEI with shared paging. In the example, when there are a large number of RedCap wireless devices, the base station can configure different PEI (and / or paging) configuration parameters for RedCap and non-RedCap types, which can be referred to as a separate PEI with separate paging configuration. Figure 33A , Figure 33B , Figure 33C and Figure 33D It shows the basis Figure 32 Various PEI and paging configurations of exemplary implementations.

[0346] Figure 33AAn exemplary implementation of a shared PEI with shared paging for both RedCap and non-RedCap types is shown. In the example, the base station may transmit an RRC message (e.g., MIB, SIB1, etc.) including configuration parameters for a first PEI / paging configuration for the RedCap type and a second PEI / paging configuration for the non-RedCap type. The first PEI / paging configuration may be associated with the same parameters as the second PEI / paging configuration. In the example, the PEIPDCCH configuration of the first PEI may be the same as the PEIPDCCH configuration of the second PEI. In the example, the PDCCH candidate of the first PEI may be different from the PDCCH candidate of the second PEI when configured with the same CORESET and the same search space. In the example, the paging PDCCH configuration of the first paging may be the same as the paging PDCCH configuration of the second paging. In the example, when the base station determines a shared PEI with shared paging for both RedCap and non-RedCap types, the base station may determine not to transmit the configuration parameters of the first PEI / paging configuration dedicated to the RedCap type. Regardless of whether the wireless device is RedCap or non-RedCap type, if the configuration parameters of the first PEI / paging configuration are not present in the RRC message, the wireless device can determine to use the configuration parameters of the second PEI / paging configuration. Figure 33A An exemplary implementation of this method, in which a shared PEI configuration with shared paging is provided, can improve the signaling overhead of the base station for PEI and paging.

[0347] Figure 33B An exemplary implementation of a shared PEI with separate paging for RedCap and non-RedCap types is shown. In the example, the base station may transmit an RRC message (e.g., MIB, SIB1, etc.) including configuration parameters for a first PEI / paging configuration for the RedCap type and a second PEI / paging configuration for the non-RedCap type. The first PEI configuration may be associated with the same parameters as the second PEI configuration. In the example, the PEIPDCCH configuration of the first PEI may be the same as the PEIPDCCH configuration of the second PEI. The first paging configuration may be associated with parameters different from the second paging configuration. The paging PDCCH configuration of the first paging may be different from the paging PDCCH configuration of the second paging. Regardless of whether the radio device is RedCap or non-RedCap type, the radio device may monitor the PEIPDCCH based on the PEI configuration. Based on a received PEI indicating the presence of a paging message for the radio device, the radio device may determine whether to monitor the first paging PDCCH or the second paging PDCCH based on whether the radio device is RedCap or non-RedCap type. Figure 33BAn exemplary implementation, with a configuration of a shared PEI for separate paging, can improve paging message delivery efficiency.

[0348] Figure 33C An exemplary implementation of separate PEIs with shared paging for RedCap and non-RedCap types is shown. In the example, the base station may transmit an RRC message (e.g., MIB, SIB1, etc.) including configuration parameters for a first PEI / paging configuration for the RedCap type and a second PEI / paging configuration for the non-RedCap type. The first PEI configuration may be associated with parameters different from the second PEI configuration. In the example, the PEIPDCCH configuration of the first PEI may be different from the PEIPDCCH configuration of the second PEI. The first paging configuration may be associated with the same parameters as the second paging configuration. The paging PDCCH configuration of the first paging may be the same as the paging PDCCH configuration of the second paging. The radio device may determine whether to monitor the first PEI or the second PEI based on whether the radio device is RedCap or non-RedCap type. Based on receiving a PEI indicating the presence of a paging message for the radio device, the radio device may determine to monitor the paging PDCCH regardless of whether the radio device is RedCap or non-RedCap type. Figure 33C An exemplary implementation, with a configuration of a separate PEI for shared paging, can improve the power consumption of RedCap UE monitoring the PEI.

[0349] Figure 33D An exemplary implementation of a separate PEI with separate paging for RedCap and non-RedCap types is shown. In the example, the base station may transmit an RRC message (e.g., MIB, SIB1, etc.) including configuration parameters for a first PEI / paging configuration for the RedCap type and a second PEI / paging configuration for the non-RedCap type. The first PEI configuration may be associated with parameters different from the second PEI configuration. In the example, the PEIPDCCH configuration of the first PEI may be different from the PEIPDCCH configuration of the second PEI. The first paging configuration may be associated with parameters different from the second paging configuration. The paging PDCCH configuration of the first paging may be different from the paging PDCCH configuration of the second paging. The radio device may determine whether to monitor the first PEI or the second PEI based on whether the radio device is RedCap or non-RedCap type. Based on receiving a PEI indicating the presence of a paging message for the radio device, the radio device may determine whether to monitor the first paging PDCCH or the second paging PDCCH based on whether the radio device is RedCap or non-RedCap type. Figure 33DAn exemplary implementation, with a configuration of a separate PEI for separate paging, can improve the power consumption of RedCap UE monitoring PEI and PO.

[0350] In the prior art, a cell's first initial BWP can be configured separately for RedCap radio equipment from a cell's second initial BWP, which can be used by non-RedCap radio equipment, for paging (e.g., paging search space, paging timing, etc.) and RACH procedures. In the prior art, a PEI (associated with PEI search space, PEI MO, etc.), distinct from paging and / or RACH procedures, can be configured only on the cell's second initial BWP for non-RedCap radio equipment. PEI and paging can be based on the above regarding... Figure 29A , Figure 29B and / or Figure 30 This is achieved through an exemplary implementation.

[0351] However, regarding PEI, by implementing existing technologies, wireless devices may not be able to determine whether to transmit PEI separately on different initial BWPs of the cell.

[0352] In the example, by implementing existing technology, the RedCap radio device can determine that the PEI (e.g., search space, PEI timing, etc.) is configured on the second initial BWP of the cell. In this case, the RedCap radio device may need to monitor the PEI on the second initial BWP and then switch to the first initial BWP to receive the paging DCI in response to receiving the PEI on the second initial BWP. Existing technology may result in unnecessary power consumption for the RedCap radio device in receiving paging messages.

[0353] In the example, by implementing existing technology, RedCap radio devices can determine that the PEI is configured on both the initial BWP and the second initial BWP of the cell. In this case, both RedCap and non-RedCap radio devices can (automatically) monitor the PEI on both initial BWPs to receive the PEI. Existing technology may increase the power consumption of radio devices.

[0354] In the example, by implementing existing technology, the RedCap radio device can determine whether the PEI and paging are configured on both the first and second initial BWPs of the cell, for example, without distinguishing between RedCap and non-RedCap. In this case, the RedCap radio device can monitor the paging PDCCH on both the first and second initial BWPs in response to receiving the PEI. Existing technology may increase the power consumption of the radio device.

[0355] When configuring multiple initial BWPs for RedCap and non-RedCap radio devices on a cell, it is necessary to reduce the power consumption of PEI and paging reception.

[0356] When the cell's initial BWP is configured for paging, Figure 32 , Figure 33A , Figure 33B , Figure 33C and / or Figure 33D The exemplary implementation can be extended to improve the power consumption of RedCap UE when paging.

[0357] Figure 34A An exemplary implementation of PEI configuration (and / or paging configuration) for RedCap and non-RedCap types on the same initial DL BWP for a cell (e.g., PCell or PSCell) is shown. In the exemplary implementation, the base station may transmit an RRC message (e.g., MIB, SIB1, etc.) that includes a first PEI configuration (and / or paging configuration) for the RedCap type and a second PEI configuration (and / or paging configuration) for the non-RedCap type on the same initial DL BWP. The SIB1 message may include a DownlinkConfigCommonSIB IE. The DownlinkConfigCommonSIB IE may include two PCCH-Config IEs. The first PEI configuration (and / or paging configuration) for the RedCap type may be included in a first PCCH configuration (e.g., a first PCCH-Config IE). The second PEI configuration (and / or paging configuration) for the non-RedCap type may be included in a second PCCH configuration (e.g., a second PCCH-Config IE). The first PCCH-Config IE and the second PCCH-Config IE may be included in the SIB1 message. The PIERNTI of the first PEI configuration (configured or predefined) may differ from the PEI RNTI of the second PEI (configured or predefined). The base station may indicate the presence of the first PCCH-Config IE based on indication parameters in the MIB. The base station may indicate the presence of the first PCCH-Config IE based on one or more bit fields (e.g., spare bits) in the MIB message that are set to predefined values.

[0358] Figure 34BExemplary implementations of PEI configurations (and / or paging configurations) for RedCap and non-RedCap types on different initial DL BWPs of a cell (e.g., PCell or PSCell) are shown. In the exemplary implementation, the base station may transmit RRC messages (e.g., MIB, SIB1, etc.) that include a first PEI configuration (and / or paging configuration) for the RedCap type and a second PEI configuration (and / or paging configuration) for the non-RedCap type on different initial DL BWPs of the cell.

[0359] In the example, the SIB1 message may include two DownlinkConfigCommonSIB IEs. The first of the two DownlinkConfigCommonSIB IEs may indicate the first initial DL BWP for the RedCap type.

[0360] In the example, on the first initial DL BWP of the cell, the first DownlinkConfigCommonSIB IE can further indicate a first PCCH-Config IE for the RedCap type. The first PCCH-Config IE may include a first PEI configuration for the RedCap type.

[0361] In the example, the second DownlinkConfigCommonSIB IE of the two DownlinkConfigCommonSIB IEs can indicate a second initial DL BWP for non-RedCap types.

[0362] In the example, on the second initial DL BWP of the cell, the second DownlinkConfigCommonSIB IE can further indicate a second PCCH-Config IE for non-RedCap types. The second PCCH-Config IE can include a second PEI configuration for non-RedCap types.

[0363] In the example, the first initial BWP for a RedCap type wireless device can be smaller than the second initial BWP for a non-RedCap type wireless device.

[0364] In the example, when the first PEI configuration and the second PEI configuration are on different initial DL BWPs, the (configured or predefined) PEI-RNTI of the first PEI configuration can be the same as the (configured or predefined) PEI-RNTI of the second PEI configuration.

[0365] In the example, the base station can indicate the presence of a DownlinkConfigCommonSIB dedicated to the RedCap type based on the indication parameters of the MIB. The base station can also indicate the presence of a DownlinkConfigCommonSIB dedicated to the RedCap type based on one or more bit fields (e.g., spare bits) in the MIB message that are set to predefined values.

[0366] In the example, in response to the radio device being of RedCap type, the radio device may determine to use a first initial DLBWP to receive the PEI and the corresponding paging DCI and paging message. In response to the radio device being of non-RedCap type, the radio device may determine to use a second initial DL BWP to receive the PEI and the corresponding paging DCI and paging message. In the example, a non-RedCap radio device may not switch to the first initial DL BWP to receive the PEI and / or paging DCI / message. A RedCap radio device may not switch to the second initial DL BWP to receive the PEI and / or paging DCI / message.

[0367] In an exemplary implementation, a wireless device may receive a message indicating a first initial BWP for a cell including a BWP and a second initial BWP for the cell, wherein the first initial BWP is associated with a first wireless device type and the second initial BWP is associated with a second wireless device type. The wireless device may determine one of the first initial BWP and the second initial BWP based on the type of the wireless device, wherein the type is one of the first wireless device type and the second wireless device type. The wireless device may receive a PEI based on a monitored PEI search space via the determined initial BWP, and receive a DCI for scheduling paging messages in response to the PEI (e.g., indicating a monitored paging PDCCH).

[0368] In an exemplary implementation, a wireless device may receive a message indicating configuration parameters of the PEI search space, a first initial BWP of a cell including a BWP, and a second initial BWP of the cell, wherein the first initial BWP is associated with a first wireless device type, and the second initial BWP is associated with a second wireless device type. The wireless device may determine one of the first initial BWP and the second initial BWP based on the type of the wireless device, wherein the type is one of the first wireless device type and the second wireless device type. The wireless device may receive a PEI based on the type of the wireless device and via the determined initial BWP, by monitoring the PEI search space according to the configuration parameters, and receive a DCI (Dispatch Indicator) for a scheduling paging message in response to the PEI.

[0369] By implementing the exemplary embodiment, based on the base station configuring PEI and paging on the same initial BWP, and configuring different initial BWPs for different types of radio devices (RedCap, non-RedCap, etc.), the radio device can persist (e.g., without switching to another initial DL BWP) on the same initial DL BWP to receive PEI, and / or receive paging DCI scheduled for the radio device in response to the PEI indicating the monitoring of the paging PDCCH. The exemplary embodiment can allow the base station to transmit different PEIs on different initial DL BWPs for different types of radio devices without requesting the radio device to switch DL BWPs to receive PEI and / or paging DCI / paging messages. The exemplary embodiment may increase PEI transmission overhead on different initial BWPs. With the increase in PEI transmission overhead, assuming that RedCap radio devices are more power-constrained than non-RedCap radio devices or the base station, the exemplary embodiment can reduce the power consumption of RedCap radio devices receiving paging messages.

[0370] Figure 30 , Figure 32 , Figure 33A , Figure 33B , Figure 33C , Figure 33D , Figure 34A and / or Figure 34B The exemplary implementation can be extended to improve the power consumption of RedCap UE when paging.

[0371] Figure 35 An exemplary implementation of the configuration for the gap between PEI and PO of RedCap and non-RedCap types is shown. In the example, the base station can transmit ( Figure 35 (Not shown) An RRC message (e.g., MIB, SIB1, etc.) includes a first PEI configuration (and / or paging configuration) for RedCap types and a second PEI configuration (and / or paging configuration) for non-RedCap types. The first PEI (and / or paging) configuration and the second PEI (and / or paging) configuration can be based on the above regarding Figure 30 , Figure 32 , Figure 33A , Figure 33B , Figure 33C , Figure 33D , Figure 34A and / or Figure 34B The exemplary implementation described is used for implementation. In the example, the PEI configuration (first PEI or second PEI) may further indicate the gap between the PEI and the corresponding PO. This gap may be several time slots (or symbols) between the last symbol of the last PEIPDCCH monitoring timing and the first symbol of the starting paging PDCCH monitoring timing.

[0372] In the example, in the first PEI configuration, the base station can configure a first gap between the PEI and the corresponding PO for RedCap types. In the second PEI configuration, the base station can configure a second gap between the PEI and the corresponding PO for non-RedCap types. In the example, for example, due to the limited processing capacity of the RedCap type, the first gap may be larger than the second gap.

[0373] In the example, such as Figure 35 As shown, the wireless device (e.g., UE1 with RedCap or UE2 without RedCap) can warm up to prepare for PEI monitoring. The wireless device can be based on the above regarding... Figure 28A and / or Figure 28B The exemplary implementation described is used for warm-up. The wireless device can perform synchronization based on the SSB. The wireless device can monitor the PEI based on the PEI configuration (e.g., a first PEI configuration or a second PEI configuration). The wireless device can be based on the above regarding... Figure 30 , Figure 32 , Figure 33A , Figure 33B , Figure 33C , Figure 33D , Figure 34A and / or Figure 34B The exemplary implementation described is used to monitor PEI.

[0374] In response to receiving a PEI in the first time slot, the radio device can determine whether to apply a first gap or a second gap to monitor the PO based on whether the radio device is a RedCap type or a non-RedCap type. If the radio device is a RedCap type (e.g., UE1 with RedCap), the radio device can apply the first gap to monitor the PO. The radio device can begin monitoring the PO from the second time slot, where the time offset between the first and second time slots can be equal to or greater than the first gap. If the radio device is a non-RedCap type (e.g., UE2 with non-RedCap), the radio device can apply the second gap to monitor the PO. The radio device can begin monitoring the PO from the third time slot, where the time offset between the first and third time slots can be equal to or greater than the second gap.

[0375] based on Figure 35 Exemplary implementations, for example, allow the base station to flexibly configure different gaps between PEI and PO for different wireless device types (e.g., RedCap type, non-RedCap type, etc.) based on their varying capabilities. Exemplary implementations can reduce the likelihood of not detecting a paging DCI after receiving a PEI from a RedCap wireless device.

[0376] Figure 30 , Figure 32 , Figure 33A , Figure 33B , Figure 33C , Figure 33D , Figure 34A , Figure 34B and / or Figure 35 The exemplary implementation can be extended to improve the power consumption of RedCap UE when paging.

[0377] Figure 36 An exemplary implementation scheme for PEI detection of both RedCap and non-RedCap types is shown. In the example, the base station can transmit ( Figure 36 (Not shown) An RRC message (e.g., MIB, SIB1, etc.) includes a first PEI configuration (and / or paging configuration) for RedCap types and a second PEI configuration (and / or paging configuration) for non-RedCap types. The first PEI (and / or paging) configuration and the second PEI (and / or paging) configuration can be based on the above regarding Figure 30 , Figure 32 , Figure 33A , Figure 33B , Figure 33C , Figure 33D , Figure 34A , Figure 34B and / or Figure 35 The exemplary implementation described is used to achieve this. In the example, the first PEI configuration may include a first parameter indicating whether a RedCap wireless device can skip monitoring a PO in response to the absence of a PEI. The second PEI configuration may include a second parameter indicating whether a non-RedCap wireless device can skip monitoring a PO in response to the absence of a PEI. The first parameter may be configured separately and / or independently from the second parameter. Configuring the behavior of the wireless device not detecting a PEI allows the base station and the wireless device to align regarding whether to monitor a PO in response to the absence of a PEI.

[0378] In the example, in the first PEI configuration, the base station can instruct a RedCap radio device to skip monitoring a PO in response to the absence of a detected PEI (or any PEI preceding the corresponding PO) based on a first value of a first parameter. In the second PEI configuration, the base station can instruct a non-RedCap radio device to monitor the PO in response to the absence of a detected PEI (or any PEI preceding the corresponding PO) based on a second value of a second parameter. Configuring different behaviors for RedCap and non-RedCap types when no PEI is detected can improve the power consumption and / or paging latency of the radio device.

[0379] In an exemplary implementation, such as Figure 36 As shown, the wireless device (e.g., UE1 with RedCap or UE2 without RedCap) can warm up to prepare for PEI monitoring. The wireless device can be based on the above regarding... Figure 28A and / or Figure 28B The exemplary implementation described is used for warm-up. The wireless device can perform synchronization based on the SSB. The wireless device can monitor the PEI based on the PEI configuration (e.g., a first PEI configuration or a second PEI configuration). The wireless device can be based on the above regarding... Figure 30 , Figure 32 , Figure 33A , Figure 33B , Figure 33C , Figure 33D , Figure 34A , Figure 34B and / or Figure 35 The exemplary implementation described is used to monitor PEI.

[0380] In an exemplary implementation, in response to the absence of a PEI, the wireless device can determine whether to skip monitoring of the PO (or all POs in the PF) or monitor the PO based on whether the wireless device is a RedCap type or a non-RedCap type and based on the RRC message. In response to the wireless device being a RedCap type (e.g., ...), Figure 36 For UEs with RedCap (e.g., 1), the radio device can skip monitoring the PO based on an RRC message, which instructs a RedCap type radio device to skip monitoring the PO in response to the absence of a PEI. In response to a non-RedCap type (e.g., 1), Figure 36 In the case of a non-RedCap UE 2), the radio device can monitor the PO based on an RRC message, which instructs the non-RedCap type radio device to monitor the PO in response to the absence of a PEI.

[0381] In an exemplary implementation, the base station may not configure a first parameter for the RedCap radio device type. The first parameter may not be present in the RRC message. For example, when the first parameter is absent in the RRC message, the RedCap radio device may determine a default behavior regarding monitoring POs in response to the absence of a PEI. In an exemplary implementation, the RedCap radio device may determine a first default behavior that includes skipping monitoring of the PO (or any PO in the PF) in response to the absence of a PEI. In an exemplary implementation, the RedCap radio device may determine a second default behavior that includes monitoring the PO (or any PO in the PF) in response to the absence of a PEI. The RedCap radio device may determine whether to apply the first or second default behavior through predefined rules or through the base station's configuration.

[0382] In an exemplary implementation, the base station may not configure a second parameter for non-RedCap radio device types. The second parameter may not be present in the RRC message. For example, when the second parameter is absent in the RRC message, a non-RedCap radio device may determine a default behavior regarding monitoring POs in response to the absence of a PEI. In an exemplary implementation, a non-RedCap radio device may determine a default behavior including skipping monitoring of POs (or any POs in the PF) in response to the absence of a PEI. In an exemplary implementation, a non-RedCap radio device may determine a default behavior including monitoring POs (or any POs in the PF) in response to the absence of a PEI. The default behavior of a non-RedCap radio device may be the same as or different from the default behavior of a RedCap radio device. A non-RedCap radio device may determine whether to apply a first default behavior or a second default behavior through predefined rules or through the base station's configuration.

[0383] based on Figure 36 Exemplary implementations, such as when a RedCap wireless device is power-constrained and / or data-centric, can reduce paging power consumption by skipping monitoring of the PO (or any PO in the PF) in response to the absence of a detected PEI. Based on exemplary implementations, non-RedCap wireless devices can reduce paging message delivery latency by monitoring the PO (in the PF) in response to the absence of a detected PEI.

[0384] In an exemplary embodiment, the base station may transmit and / or the wireless device may receive a message indicating a first parameter of a first PEI associated with a first wireless device type and a second parameter of a second PEI associated with a second wireless device type. In response to the wireless device being of the first wireless device type and based on the first parameter, the wireless device may monitor a first PDCCH of the first PEI. The wireless device may monitor a first PO of a paging message based on the first PEI. In response to the wireless device being of the second wireless device type and based on the second parameter, the wireless device may monitor a second PDCCH of the second PEI. The wireless device may monitor a second PO of a paging message based on the second PEI. The wireless device may receive a paging message including the identifier of the wireless device.

[0385] In an exemplary implementation, the first parameter may indicate that the first PEI is configured with a wireless device in either an RRC IDLE state or an RRC INACTIVE state. The message may include at least one of a MIB message and a SIB1 message.

[0386] In an exemplary implementation, the first parameter may indicate at least one of the following: a first control resource set of a first PDCCH associated with a first PEI, one or more first search spaces of the first PDCCH, and a first time offset between the first PEI and the first PO.

[0387] In an exemplary implementation, the first control resource set may be associated with a control resource set index that identifies the first control resource set. The first control resource set may be associated with at least one of the following: a frequency resource indicator, a time-domain duration indicator, and an indicator of a CCE-to-REG mapping type.

[0388] In an exemplary embodiment, each of the one or more first search spaces may be associated with at least one of the following: a search space index identifying the search space, a control resource set index identifying the control resource set associated with the search space, one or more time-domain resource allocation parameters of the search space, a search space type, and the number of aggregation levels of the search space. The one or more time-domain resource allocation parameters may include at least one of the following: the period value of the first PDCCH, the slot offset of the start point of the first PDCCH, and the number of symbols of the first PDCCH.

[0389] In an exemplary implementation, the second parameter may include at least one of the following: a second control resource set of the second PDCCH associated with the second PEI, one or more second search spaces of the second PDCCH, and a second time offset between the second PEI and the second PO.

[0390] In an exemplary embodiment, the first control resource set may be the same as the second control resource set. One or more first search spaces may be the same as one or more second search spaces. The first time offset may be the same as the second time offset.

[0391] In an exemplary implementation, the message may also include a first parameter of a first PO associated with a first wireless device type and a second parameter of a second PO associated with a second wireless device type.

[0392] In an exemplary implementation, the first parameter may include at least one of the following: paging cycle, number of paging frames in the paging cycle, paging frame offset in the paging cycle, total number of POs including the first PO in the paging frames, and the first PDCCH monitoring timing of the first PO.

[0393] In an exemplary embodiment, the first parameter of the first PO may include at least one of the following: a first control resource set for monitoring the second PDCCH of the first PO and one or more first search spaces of the second PDCCH.

[0394] In an exemplary embodiment, the second parameter of the second PO may include at least one of the following: a second control resource set for monitoring the second PDCCH of the second PO and one or more second search spaces of the second PDCCH.

[0395] In an exemplary implementation, the first control resource set may be identical to the second control resource set. The first and second control resource sets being identical includes both control resource sets having the same configuration parameters. One or more first search spaces may be identical to one or more second search spaces. The first and second search spaces being identical includes both search spaces having the same configuration parameters.

[0396] In an exemplary implementation, the first parameter may instruct the first PDCCH to be transmitted in the first initial bandwidth portion (BWP) of the cell associated with the first radio device type.

[0397] In an exemplary implementation, the second parameter may instruct the second PDCCH to be transmitted in the second initial BWP associated with the second wireless device type in the cell.

[0398] In the example, the first initial BWP can be different from the second initial BWP.

[0399] In the example, the first initial BWP can be the same as the second initial BWP.

[0400] In an exemplary implementation, in response to the wireless device being a first wireless device type, the wireless device may utilize a first RNTI (PEI-RNTI) associated with a first PEI to monitor a first PDCCH (e.g., on the first initial BWP of the cell).

[0401] In the example, the first PEI-RNTI can be predefined as a fixed value or configured in the RRC message. The first PEI-RNTI can be the same as the P-RNTI used by the DCI for receiving dispatch paging messages. The first PEI-RNTI can also be different from the P-RNTI. Different values ​​can be predefined for the P-RNTI for different radio device types (e.g., RedCap type, non-RedCap type). The same value can be predefined for the P-RNTI for different radio device types (e.g., RedCap type, non-RedCap type).

[0402] In an exemplary implementation, in response to the wireless device being a second wireless device type, the wireless device may utilize the second PEI-RNTI to monitor the second PDCCH (e.g., in the cell's second initial BWP).

[0403] In the example, the second PEI-RNTI can be predefined as a fixed value or configured in the RRC message. The second PEI-RNTI can be different from the first PEI-RNTI, or it can be the same as the first PEI-RNTI. The second PEI-RNTI can be the same as the P-RNTI of the DCI used to receive dispatch paging messages. The second PEI-RNTI can be different from the P-RNTI.

[0404] In an exemplary implementation, in response to belonging to a first wireless device type, the wireless device may be configured with a first number of receiving antennas. In response to belonging to a second wireless device type, the wireless device may be configured with a second number of receiving antennas, wherein the second number is greater than the first number.

[0405] In an exemplary implementation, in response to belonging to a first wireless device type, the wireless device may be able to operate within a first bandwidth. In response to belonging to a second wireless device type, the wireless device may be able to operate within a second bandwidth, wherein the second bandwidth is greater than the first bandwidth.

[0406] In an exemplary implementation, in response to receiving a first PEI instructing the wireless device to monitor a first PO, the wireless device may monitor the first PO (e.g., on a first initial BWP). Monitoring the first PO may include a second PDCCH that uses a paging RNTI to monitor the DCI. The paging RNTI may be different from either the first PEI-RNTI or the second PEI-RNTI. The DCI may indicate scheduling information for the paging message.

[0407] In an exemplary implementation, in response to receiving a second PEI instructing the wireless device to monitor the second PO, the wireless device can monitor the second PO (e.g., on the second initial BWP).

[0408] In an exemplary embodiment, the base station may transmit an SIB message including a first parameter of a first PEI associated with a first radio device type and a second parameter of a second PEI associated with a second radio device type. The base station may transmit the first PEI via a first PDCCH for a first radio device having the first radio device type based on the first parameter. The base station may transmit a first DCI to the first radio device in a first PO based on the transmission of the first PEI. The base station may transmit a first paging message to the first radio device based on the first DCI. The base station may transmit a second PEI via a second PDCCH for a second radio device having the second radio device type based on the second parameter. The base station may transmit a second DCI to the second radio device in a second PO based on the transmission of the second PEI. The base station may transmit a second paging message to the second radio device based on the second DCI.

[0409] In an exemplary implementation, a wireless device can receive from a base station a message including parameters of a Point of Interest (PO) and multiple time offsets, each time offset being associated with a corresponding wireless device type among multiple wireless device types. Each time offset can indicate a time offset value between a Point of Interest (PEI) and a PO. The wireless device can monitor the PEI in a first time slot that occurs at a first time offset prior to a second time slot. The first time offset can be determined based on the multiple time offsets, based on the wireless device being a first wireless device type among multiple wireless device types. The second time slot can be determined based on the parameters of the PO. The second time slot can be determined based on the identifier of the wireless device. The wireless device can monitor the PO in the second time slot based on the PEI indicating the PO to receive downlink control information for scheduling paging messages. The wireless device can receive paging messages based on receiving downlink control information.

[0410] In an exemplary embodiment, the wireless device may receive a message including parameters of PEI and PO, a first parameter associated with a first wireless device type and indicating that PO should be monitored in response to the absence of PEI, and a second parameter associated with a second wireless device type and indicating that monitoring of PO should be skipped in response to the absence of PEI. The wireless device may monitor a first PDCCH for receiving PEI based on these parameters. Based on the absence of PEI and the wireless device being the first wireless device type, the wireless device may monitor PO to receive a DCI for scheduling paging messages. The wireless device may receive paging messages based on receiving downlink control information.

Claims

1. A paging monitoring method, the method comprising: Parameters are received by the wireless device, and the parameters indicate: The first physical downlink control channel (PDCCH) monitoring timing (MO) for each SSB in the synchronization signal block (SSB) during paging; The first position of the starting PDCCH MO in the first PDCCH MO indicating the early PEI timing; and The second position of the starting PDCCH MO in the second PDCCH MO of the paging timing; Based on monitoring the first PDCCH receiving PEI on a second number of first PDCCH MOs starting from the first position and at the PEI timing, wherein the second number is determined based on the following: The first quantity; and The number of SSBs; and In response to the PEI, a second PDCCH is monitored starting from the second position and on a second number of second PDCCH MOs at the paging time.

2. The method of claim 1, wherein the parameter indicates that the PEI is configured with the wireless device in a Radio Resource Control (RRC) idle state or an RRC inactive state.

3. The method of claim 1, wherein the first quantity is determined for both of the following: The first PDCCH MO at the PEI timing; and The second PDCCH MO of the paging timing.

4. The method of claim 1, wherein the second PDCCH MO of the paging timing and the first PDCCH MO of the PEI timing are in the same initial BWP of a cell comprising multiple bandwidth portion BWPs.

5. The method of claim 1, wherein the first PDCCH MO of the PEI timing is different from the second PDCCH MO of the paging timing.

6. The method of claim 1, wherein the first PDCCH is monitored using a first radio network temporary identifier (RNTI) associated with the PEI.

7. The method of claim 1, further comprising receiving the paging message based on a DCI that receives a scheduled paging message during monitoring of the second PDCCH, wherein the second PDCCH is monitored using a second RNTI, the second RNTI being used to receive the paging message in response to receiving a PEI indicating monitoring of the second PDCCH.

8. The method of claim 1, wherein the parameter for the paging timing includes at least one of the following: The paging search space of the PDCCH MO for the paging timing; and A second set of control resources associated with the paging search space.

9. The method of claim 8, wherein the parameter indicates: Paging loop; The number of paging frames in the paging loop; The paging frame offset in the paging loop; and The number of paging opportunities in a paging frame.

10. The method of claim 1, wherein in a PDCCH MO that overlaps with a first uplink transmission, the first PDCCH is not monitored for the PEI.

11. The method of claim 1, wherein the second number of first PDCCH MOs at the PEI timing comprises a plurality of PDCCH MOs, the plurality of PDCCH MOs being: It does not overlap with the first uplink transmission; and Numbering is performed sequentially starting from zero based on the first position.

12. The method of claim 7, wherein the paging timing includes a plurality of wireless device identifiers, the plurality of wireless device identifiers including a first wireless device identifier associated with the wireless device.

13. A wireless device, the wireless device comprising: One or more processors; and A memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method as described in any one of claims 1 to 12.

14. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to perform the method as described in any one of claims 1 to 12.

Images