On-demand synchronization signal block transmission in cell

Abstract

A method can include receiving, by a wireless device from a base station, one or more radio resource control (RRC) messages of a configuration of a secondary cell (SCell). These messages can include an on-demand synchronization signal block (OD-SSB) configuration of one or more OD-SSBs of the SCell, an initial state of the OD-SSB configuration indicating whether the one or more OD-SSBs are transmitted by the base station at the time of configuration of the SCell, or both the initial states of the OD-SSB configuration and the OD-SSB configuration.

Description

Cross-reference to related applications

[0001] This application claims priority to U.S. Provisional Application 63 / 539,737, filed September 21, 2023, the entire contents of which are incorporated herein by reference. Attached Figure Description

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

[0003] Figure 1A and Figure 1B An example mobile communication network in which embodiments of the present disclosure can be implemented is shown.

[0004] Figure 2A and Figure 2B The protocol stacks for the New Radio (NR) user plane and control plane are shown respectively.

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

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

[0007] Figure 4B This shows an example format of the MAC subheader in a MAC PDU.

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

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

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

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

[0012] Figure 9 An example of bandwidth adaptation using three configured BWPs with NR carriers is shown.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0032] Figure 24B An example configuration for CORESET 0 is shown.

[0033] Figure 24C An example configuration for search space 0 is shown.

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

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

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

[0037] Figure 28 An example of cell pauses for power saving in wireless devices is shown.

[0038] Figure 29 An example of DRX configuration for wireless devices is shown.

[0039] Figure 30 An example of DRX operation for wireless devices is shown.

[0040] Figure 31A and Figure 31B Examples of wake-up and sleep signals for power saving in wireless devices are shown.

[0041] Figure 32A and Figure 32B An example of search space cluster group switching for power saving in wireless devices is shown.

[0042] Figure 33 An example of PDCCH skipping for power saving in wireless devices is shown.

[0043] Figure 34 Examples of activation and deactivation of cell DTX configurations for network energy saving are shown.

[0044] Figure 35An example of PDCCH monitoring timing is shown for DCI that indicates activation / deactivation of cell DTX configuration for network energy saving.

[0045] Figure 36 An example of an SSB configuration is shown.

[0046] Figure 37 An example of SSB transmission is shown.

[0047] Figure 38 An example of SSB transmission is shown.

[0048] Figure 39 An example of SCell activation delay is shown.

[0049] Figure 40 An example of a layer 3 beam / cell measurement process is shown.

[0050] Figure 41 An example of a layer 3 measurement configuration is shown.

[0051] Figure 42 An example of a layer 3 measurement configuration is shown.

[0052] Figure 43 An example of a layer 3 measurement configuration is shown.

[0053] Figure 44 An example of a layer 3 measurement configuration is shown.

[0054] Figure 45 An example problem of SSB and / or DRS transmission in a cell is shown.

[0055] Figure 46 An example implementation of SSB and / or DRS transmission in a cell is shown.

[0056] Figure 47 An example implementation of SSB and / or DRS transmission in a cell is shown.

[0057] Figure 48 An example implementation of SSB and / or DRS transmission in a cell is shown.

[0058] Figure 49 An example implementation of SSB and / or DRS transmission in a cell is shown.

[0059] Figure 50 An example implementation of SSB and / or DRS transmission in a cell is shown. Detailed Implementation

[0060] In this disclosure, various embodiments are presented as 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 can be made therein without departing from the scope of the invention. Indeed, alternative embodiments will be apparent to those skilled in the art upon reading the specification. 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 can 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, any actions listed in any flowchart can be reordered or used only optionally in certain embodiments.

[0061] 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. Example 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 example implementation schemes can be applied when one or more criteria are met. Therefore, example implementation schemes that selectively implement the disclosed protocols can be implemented.

[0062] A base station can communicate with a hybrid of wireless devices. The 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 can refer to a subset of the total number of wireless devices in the coverage area. For example, this disclosure can mean multiple wireless devices having a given capability and in a given sector of a base station using a given LTE or 5G version. Multiple wireless devices in this disclosure can 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.

[0063] In this disclosure, “a(a)” and “an(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 variety of suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The 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.

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

[0065] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings 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.

[0066] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, and parameter (IE)M contains parameter (IE)K, and parameter (IE)K contains parameter (information element)J, then, for example, N contains K, and N contains J. In an example implementation, when one or more messages contain 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.

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

[0068] 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 as 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 a software routine written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement 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 typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure the connections between internal hardware modules with limited functionality on the programmable device. The aforementioned techniques are often used in combination to achieve the result of functional modules.

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

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

[0071] 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 the two duplexing technologies.

[0072] 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 computer, 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 equipment.

[0073] RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to refer to and encompass: 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 ​​a donor node; Next Generation Evolved Node B (ng-eNB); First 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).

[0074] 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 of the base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of the cells 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.

[0075] 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 unit coupled to the RRH can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. 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.

[0076] 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 femtocell base stations.

[0077] 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 can be applied 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.

[0078] Figure 1BAnother example mobile communication network 150 in which embodiments of the present disclosure can 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 manner as the corresponding components described.

[0079] 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).

[0080] 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 1B These 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 interconnecting 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.

[0081] 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., paging retransmission control and execution), 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.

[0082] 5G-CN 152 may include, for clarity Figure 1B One or more additional network functions not 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).

[0083] 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, denoted as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, denoted 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.

[0084] like Figure 1BAs 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.

[0085] 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 AMF 158A 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.

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

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

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

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

[0090] Figure 2A The diagram illustrates the 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 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 Serving Data Application Protocol (SDAP) 215 and 225. These four protocols together constitute Layer 2 of the OSI model, or the Data Link Layer.

[0091] Figure 3 This illustrates an example of services provided between protocol layers in the NR user plane protocol stack. From Figure 2A and Figure 3Starting 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 the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). SDAPs 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between QoS flows and data radio bearers can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between QoS flows and data radio bearers through reflected mapping or control signaling received from gNB 220. For reflective mapping, SDAP 225 at gNB 220 can mark downlink packets with QoS flow indicators (QFIs), which can be observed by SDAP 215 at UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

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

[0093] although Figure 3 Although not shown, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows 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 occur 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.

[0094] 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 the logical channel, independent of the parameter set 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.

[0095] 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, MACs 212 and 222 can provide logical channels as services to RLCs 213 and 223.

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

[0097] Figure 4A An example downlink data flow is shown that passes through the NR user plane protocol stack. Figure 4AThe diagram illustrates the flow through the NR user plane protocol stack to generate three IP packets of two TB at the gNB 220. n , n+1 and m The downlink data stream. The uplink data stream flowing through the NR user plane protocol stack can be... Figure 4A The downlink data flow described in the text is similar.

[0098] 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 the middle, SDAP 225 will send IP packets n and n+1 Mapped to the first radio bearer 402, and the IP packet... m Mapped to the second radio bearer 404. SDAP header (in Figure 4A Data 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 SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of SDAP 225.

[0099] 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 Regarding IP packets m (As shown) 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 across 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.

[0100] Figure 4BAn example 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.

[0101] 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. MAC CEs can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those used for PDCP repeated detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC 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.

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

[0103] Figure 5A and Figure 5BThe 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: --Paging Control Channel (PCCH), which carries paging messages for paging UEs whose location is unknown to the network at the cell level; --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 it operates within the cell; --Common Control Channel (CCCH), which is used to carry control messages and random access; --Dedicated Control Channel (DCCH), used to carry control messages to a specific UE / carry control messages from a specific UE to configure the UE; and --Dedicated Service Channel (DTCH), which is used to carry user data to a specific UE or carry user data from a specific UE.

[0104] 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: --Paging Channel (PCH), which is used to carry paging messages originating from PCCH; --Broadcast channel (BCH), which is used to carry MIBs from the BCCH; --Downlink Shared Channel (DL-SCH), which carries downlink data and signaling messages, including SIBs from BCCH; --Uplink Shared Channel (UL-SCH), used to carry uplink data and signaling messages; and --Random Access Channel (RACH), which is used to allow a UE to access the network without any prior scheduling.

[0105] 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 (called L1 / L2 control channels). The set of physical channels and physical control channels defined by the NR includes, for example: --Physical Broadcast Channel (PBCH), which is used to carry MIBs from the BCH; --Physical Downlink Shared Channel (PDSCH), which carries downlink data and signaling messages from DL-SCH and paging messages from PCH; --Physical downlink control channel (PDCCH), which carries downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands; --Physical Uplink Shared Channel (PUSCH), which is used to carry uplink data and signaling messages from UL-SCH, and in some cases carries uplink control information (UCI) as described below; --Physical Uplink Control Channel (PUCCH), which carries the UCI, which may include HARQ acknowledgment, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and --Physical Random Access Channel (PRACH), which is used for random access.

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

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

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

[0109] 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 radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of said reports; 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.

[0110] 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).

[0111] 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 2B The gNB 220 depicted in this disclosure; or any other base station described herein. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may contain 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.

[0112] 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 periodically wake up (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. UE 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.

[0113] 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 connected 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.

[0114] 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).

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

[0116] 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 contain 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 the RAN notification area assigned to it, the UE can perform a notification area update on the RAN to update its RAN notification area.

[0117] The base station storing the RRC context for the UE, or the UE's last serving base station, may 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.

[0118] gNB, such as Figure 1B The 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 can contain RRC, PDCP, and SDAP. The gNB-DU can contain RLC, MAC, and PHY.

[0119] In NR, physical signals and physical channels (about Figure 5A and Figure 5B The concepts discussed can be mapped to Orthogonal Frequency Division Multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that uses... F Data is transmitted via orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-QAM symbols or M-PSK symbols) and divided into... F A parallel symbol stream. FThe parallel symbol streams can be viewed as if they were in the frequency domain and used as input to blocks of Inverse Fast Fourier Transform (IFFT) that transform them to the time domain. An IFFT block can take... F Source symbols (from) F One source symbol is taken from each of the parallel symbol streams, and each source symbol is used to modulate the signal. F Corresponding to each orthogonal subcarrier F The amplitude and phase of one of the sinusoidal basis functions. The output of the IFFT block can represent... F The sum of orthogonal subcarriers F Each time-domain sample. F Each time-domain sample can form a single OFDM symbol. After some processing (e.g., the addition of a cyclic prefix) and upconversion, the OFDM symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. F The parallel symbol streams can be mixed using an FFT block before being processed by an 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 OFDM symbols can be inversely processed at the receiver using an FFT block to recover the data mapped to the source symbols.

[0120] Figure 7 An example 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.

[0121] The duration of a time slot can depend on the set of parameters used for the OFDM symbols in that time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mmWave range). The parameter set can be defined in terms of subcarrier spacing and cyclic prefix duration. For the parameter set in NR, the subcarrier spacing can be scaled up from a baseline subcarrier spacing of 15 kHz by powers of two, and the 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.

[0122] 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 (A 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.

[0123] Figure 8 An example configuration of time slots in the time and frequency domains of an NR carrier is shown. The time slots include resource elements (REs) and resource blocks (RBs). 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 in the diagram. RB spans twelve consecutive REs in the frequency domain, as... Figure 8 As shown in the diagram, the NR carrier can be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. If this limitation is used, the NR carrier can be limited to 50 MHz, 100 MHz, 200 MHz, and 400 MHz for subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively, where the 400 MHz bandwidth can be set based on a bandwidth limit of 400 MHz per carrier.

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

[0125] NR can support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). 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.

[0126] The NR defines a Bandwidth Component (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of consecutive Relays (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.

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

[0128] For a set of configured downlink BWPs on the 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 time-domain and frequency-domain locations where a UE can locate control information. The search space can be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, the base station can configure a common search space for the UE on the PCell or primary / secondary cell (PSCell) within active downlink BWPs.

[0129] 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).

[0130] One or more BWP indicator fields may 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.

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

[0132] The base station can configure the BWP inactivity timer value for the UE using 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 under the following circumstances: a When the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or ( b When the UE detects a DCI (Distributed Indication Code) for unpaired spectrum operation, indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP, the UE can proceed as follows: If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE can advance the BWP inactivity timer towards its expiration (e.g., by incrementing from zero to the BWP inactivity timer value, or decrementing from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE can switch from the active downlink BWP to the default downlink BWP.

[0133] 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).

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

[0135] 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: BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 can be the initial active BWP, and BWP904 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.

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

[0137] 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, with one serving cell per CC. A CC can have three configurations in the frequency domain.

[0138] Figure 10AThree 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).

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

[0140] 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).

[0141] The configured SCell for the UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmissions on the SCell. (The remaining text appears to be incomplete and requires further context.) Figure 4BThe 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).

[0142] Downlink control information for a cell (such as scheduling assignment and scheduling grant) 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 aggregation downlink CCs, the PCell's PUCCH may become overloaded. Cells can be divided into multiple PUCCH groups.

[0143] 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 10B In 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 SCells (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 10BIf 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.

[0144] 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 carriers. 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 containing 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 containing the first carrier is activated.

[0145] 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 / grant of each serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to the serving cell.

[0146] 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 diagram). 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 in the diagram). 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.

[0147] 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 in the diagram). 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 periodicity of the burst, 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 factors. 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.

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

[0149] 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 locations 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.

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

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

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

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

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

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

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

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

[0158] The 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 blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0159] 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 the 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.

[0160] 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. The set of PRBs can be represented as a Precode Resource Block Group (PRG).

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

[0162] 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 association with one or more parameters (e.g., modulation and coding scheme (MCS)) indicated by the DCI for other purposes. When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters containing at least one MCS. NR networks can support multiple PT-RS densities defined in the time and / or frequency domains. 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 restricted to the UE's scheduled time / frequency duration. Downlink PT-RS can be transmitted on symbols to facilitate phase tracking at the receiver.

[0163] 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 of 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.

[0164] A PUSCH can contain one or more layers, and a UE can transmit at least one symbol with DMRS present on one or more layers of the PUSCH. In the example, a higher layer can configure up to three DMRS for the PUSCH.

[0165] 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 that include 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.

[0166] 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 to 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 some point (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, wherein the one or more 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.

[0167] 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 periodicity; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; initiation OFDM symbols for SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0168] Antenna ports are defined such that a symbol on an antenna port, transmitted via its channel, can be inferred from another symbol on the same antenna port, transmitted via its channel. 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., fading 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, and the channel through which the first symbol on the first antenna port is transmitted. The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0169] 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 establishing an RRC connection with the base station, the UE can perform the downlink beam measurement procedure.

[0170] Figure 11B An example of a Channel State Information Reference Signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11B The square shown can represent a resource block (RB) within the cell's bandwidth. The base station can transmit one or more RRC messages containing 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, and 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.

[0171] Figure 11BThe three beams shown can be configured for use in a UE-specific configuration. Figure 11B The diagram shows 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-RS 1101) 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.

[0172] CSI-RS, such as Figure 11B Those shown (e.g., CSI-RS 1101, 1102, 1103) can be transmitted by the base station and used by the UE for one or more measurements. For example, the UE can measure the Reference Signal Received Power (RSRP) 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 containing 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.

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

[0174] Figure 12A Examples 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.

[0175] Figure 12BExamples 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, a Tx 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.

[0176] The UE can initiate a beam failure recovery (BFR) procedure based on the detection of beam failure. 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 beam failure 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.).

[0177] The UE can use one or more reference signals (RS) to measure the quality of the beamp-link, which 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 can 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 can 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.

[0178] 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 failure recovery requests. The network can initiate random access procedures for handover and / or for establishing time alignment for SCell additions.

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

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

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

[0182] 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).

[0183] Msg 1 1311 may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may contain 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 the RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp- ThresholdCSI-RS For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or a selected preamble group.

[0184] The UE can determine the preamble based on 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 This can indicate the correlation between the PRACH timing and the one or more reference signals.

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

[0186] 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 permission 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 The UE can monitor the PDCCH of Msg 21312. 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). The 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: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. Examples of RA-RNTIs include: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, 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).

[0187] 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. A conflict may occur if the multiple UEs interpret the RAR as corresponding to themselves. 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).

[0188] 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 an 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 contains 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.

[0189] 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).

[0190] 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 Msg 4 1314.

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

[0192] 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 search the space indicated by the RRC message (e.g., recoverySearchSpaceIdConfigure the UE using a separate time window and / or a separate PDCCH. The UE can monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) in 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 C-RNTI, the UE can determine that the random access procedure was successfully completed. For example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR contains a MAC sub-PDU with a preamble identifier, the UE can determine that the random access procedure was successfully completed. The UE can determine that the response is an indication of confirmation of the SI request.

[0193] 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 involves the transmission of two messages: Msg A1331 and Msg B1332.

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

[0195] UE can initiate [activities] on licensed spectrum and / or unlicensed spectrum. Figure 13CThe 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. The 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.

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

[0197] Transport block 1342 may contain 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 contain at least one of the following: a preamble identifier; a timing advanced command; a power control command; 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).

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

[0199] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling permission 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.

[0200] 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 involve a modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can contain a 16-bit value of the Radio Network Temporary Identifier (RNTI).

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

[0202] 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 TPC command groups 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.

[0203] 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. A CCE can contain a number of resource element groups (REGs) (e.g., 6). A REG can contain resource blocks in OFDM symbols. The mapping of the coded and modulated DCI onto resource elements can be based on a mapping between CCEs and REGs (e.g., CCE-to-REG mapping).

[0204] 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 contain time-frequency resources in which the 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 of 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 of the time slot. The fourth CORESET 1404 appears at the seventh symbol of the time slot. CORESETs can have different numbers of resource blocks in the frequency domain.

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

[0206] The base station can transmit an RRC message to the UE containing 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 contain 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).

[0207] 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.).

[0208] 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 can 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 can transmit uplink control signaling via PUCCH using one of several PUCCH formats.

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

[0210] 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; and multiple PUCCH resources (e.g., PUCCH resource resources identified by PUCCH resource identifiers). pucch-Resourceid The UE can transmit multiple (e.g., a maximum number) UCI ​​information bits using one of the multiple PUCCH resources in a PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one of the multiple PUCCH resource sets (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE can select a first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE can select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE can select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to the third value (e.g., 1406), the UE can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0211] 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).

[0212] Figure 15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of this disclosure is shown. Both the wireless device 1502 and the base station 1504 can 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.

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

[0214] 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. The data can be provided to processing system 1508 via, for example, a core network. In the uplink, data to be transmitted from wireless device 1502 to base station 1504 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, information about… Figure 2A , Figure 2B , Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer, and MAC layer are included. Layer 3 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer. Figure 2B The RRC layer.

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

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

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

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

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

[0220] 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 1526 and / or provide user output data to the aforementioned one or more peripheral devices. Processing system 1518 in wireless device 1502 may receive power from a power source and / or may 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, a solar cell unit, a fuel cell unit, 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.

[0221] Figure 16AAn example architecture 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 of complex-valued symbols; mapping precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals for antenna ports, etc. In one 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.

[0222] Figure 16B An example architecture for modulation and upsampling 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.

[0223] Figure 16C An example 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 transmission 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, etc. These functions are shown as examples, and other mechanisms are expected to be implemented in various embodiments.

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

[0225] 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 the multiple cells. The one or more messages (e.g., as part of the configuration parameters) can include parameters for configuring the wireless device at the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, and RRC layer. For example, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, etc. For example, the configuration parameters may include parameters indicating the values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0226] A timer can begin running once started and continues running until it stops or expires. If the timer is not running, it can be started, or if it is running, it can be restarted. The timer can be associated with a value (e.g., the 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 the timer may not be updated until the timer stops or expires (e.g., due to BWP switching). The timer can be used to measure time periods / windows of a process. When the specification refers to embodiments and procedures relating to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways 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 example embodiments for restarting the measurement of a time window can be provided.

[0227] 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 aligned to a length byte (e.g., aligned to a multiple of an octet). 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 the order of line reading. 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.

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

[0229] In the example, a MAC PDU can contain one or more MAC subPDUs. A MAC subPDU within one or more MAC subPDUs can contain: 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 can have a variable size. A MAC subheader can correspond to a MAC SDU, a MAC CE, or padding.

[0230] In the example, when the MAC subheader corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC subheader may contain: 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.

[0231] Figure 17A An example of a MAC subheader with R, F, LCID, and L fields is shown. Figure 17A In the example 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 example MAC subheader shown, the LCID field can be six digits long, and the R field can be two digits long.

[0232] 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 sub-PDU containing MAC CEs can be placed before a MAC sub-PDU containing MAC SDUs or a MAC sub-PDU containing padding. Figure 18B An example of a UL MAC PDU is shown. Multiple MAC CEs (such as MAC CE 1 and 2) can be placed together. In one embodiment, the MAC sub-PDU containing the MAC CE can be placed after all the MAC sub-PDUs containing the MAC SDU. Alternatively, the MAC sub-PDU can be placed before the MAC sub-PDU containing the filler.

[0233] 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 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; radio device contention resolution identity MAC CE; timing advance command MAC CE; DRX command MAC CE; long DRX command MAC CE; SCell activation / deactivation MAC CE (1 octet); SCell activation / deactivation MAC CE (4 octets); and / or 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.

[0234] 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 20Examples of one or more MAC CEs are shown. The one or more MAC CEs may include at least one of the following: Short Buffer Status Report (BSR) MAC CE; Beam Failure Recovery (BFR) MAC CE; Truncated BFR MAC CE; Truncated Enhanced BFR MAC CE; Long BSR MAC CE; C-RNTI MAC CE; Configuration Grant Acknowledgment MAC CE; Single-Entry PHR MAC CE; Multi-Entry PHR MAC CE; Short Truncated BSR; and / or Long Truncated BSR, etc. 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, the LCID given by 43 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a truncated Enhanced BFR MAC CE.

[0235] In carrier aggregation (CA), two or more component carriers (CCs) can be aggregated. A wireless device can use CA techniques, depending on its capabilities, to simultaneously receive or transmit on one or more CCs. In implementations, the wireless 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 wireless 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 the RRC connection re-establishment / handover procedure, the cell providing security input can be the serving cell. In an example, the serving cell can indicate the PCell. In an example, the base station can transmit one or more messages containing configuration parameters for multiple or more SCells to the wireless device, depending on its capabilities.

[0236] When 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 the one or more SCells. Depending on the SCell configuration, an SCell can be deactivated immediately unless the SCell state associated with the SCell is set to "activated" or "dormant".

[0237] The wireless device can activate / deactivate the SCell in response to receiving a SCell activation / deactivation MAC CE. In the example, the base station can transmit to the wireless device a message containing the SCell timer (e.g., ...). sCellDeactivationTimerOne or more messages. In the example, the wireless device can deactivate the SCell in response to the expiration of the SCell timer.

[0238] When a wireless device receives a SCell activation / deactivation MAC CE, it 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; 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 When a SCell activation / deactivation MAC CE is received for an activated SCell, the wireless device can start or restart the first SCell timer in a time slot. In the example, in response to SCell activation, the wireless device can (re)initialize one or more suspended configured uplink permissions of configured permission type 1 associated with the SCell based on the stored configuration. In the example, in response to SCell activation, the wireless device can trigger a PHR.

[0239] When a wireless device receives a SCell activation / deactivation MAC CE that deactivates an activated SCell, the wireless device can deactivate the activated SCell. In the example, when the first SCell timer associated with the activated SCell (e.g., ...) is activated... sCellDeactivationTimer Upon expiration, the wireless device can deactivate the activated SCell. 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 permissions of configured uplink permission 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 permissions of configured uplink permission type 1 associated with the activated SCell; and / or clear the HARQ buffer associated with the activated SCell.

[0240] When an SCell is deactivated, the wireless 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 the activated SCell indicates uplink grant or downlink assignment, the wireless device may restart the first SCell timer associated with the activated SCell (e.g., ...). sCellDeactivationTimer 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 permission or downlink assignment for the activated SCell, the radio device may restart the first SCell timer associated with the activated SCell (e.g., ...). sCellDeactivationTimer In the example, when the SCell is deactivated, if there is an ongoing random access procedure on the SCell, the wireless device can abort the ongoing random access procedure on the SCell.

[0241] Figure 21A An example of an octet SCell activation / deactivation 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 contain a single octet. A single octet can contain a first number of C fields (e.g., seven) and a second number of R fields (e.g., one).

[0242] Figure 21B An example of a SCell activation / deactivation MAC CE with four octets is shown. It has a second LCID (e.g., as...). Figure 19 The 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 contain four octets. The four octets can contain a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0243] 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 state of the SCell with 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 deactivates 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.

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

[0245] 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 the example, for a TDD system, one DL / UL BWP pair can be active at some point in the active serving cell. Operating on one UL BWP and one DL BWP (or one DL / UL pair) can improve radio device battery consumption. BWPs other than the one active UL BWP and one active DL BWP on which the radio device can operate can be deactivated. On a deactivated BWP, the radio device may: not monitor the PDCCH; and / or not transmit on the PUCCH, PRACH, and UL-SCH.

[0246] In the example, the serving cell can be configured with a maximum of a first number (e.g., four) BWPs. In the example, for an active serving cell, there may be an active BWP at any given time. In the example, BWP handover for the serving cell can be used to simultaneously activate an inactive BWP and deactivate the active BWP. In the example, BWP handover can be controlled by a PDCCH indicating downlink assignment or uplink permission. In the example, BWP handover can be controlled by a BWP inactivity timer (e.g., ...). bwp-InactivityTimer Control. In the example, BWP handover can be controlled by the MAC entity in response to initiating a random access procedure. When adding a SpCell or activating an SCell, a BWP can initially be active without receiving a PDCCH indicating downlink assignment or uplink permission. The active BWP for the serving cell can be indicated by RRC and / or PDCCH. In the 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.

[0247] Figure 22 An example of BWP handover on a cell (e.g., PCell or SCell) is shown. In the example, the wireless device can receive at least one RRC message from the base station, the at least one RRC message containing cell parameters and one or more BWPs associated with the cell. The RRC message may include: an RRC connection reconfiguration message (e.g., RRCReconfiguration ); RRC connection rebuild message (e.g., RRCReestablishment); and / or RRC connection setup messages (e.g., RRCSetup Of the one or more BWPs, at least one BWP can be configured as the first active BWP (e.g., BWP 1), and one BWP is configured as the default BWP (e.g., BWP 0). The radio device can 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 can activate the PCell once it receives an RRC message including the PCell's configuration parameters. The radio device can begin monitoring the PDCCH on BWP 1 in response to the activated cell.

[0248] In one example, in response to receiving a DCI indicating DL assignment on BWP 1, the wireless device can... m Start (or restart) the BWP inactive timer at each time slot (e.g., bwp-InactivityTimer When the BWP inactivity timer expires, the wireless device can... s At each time slot, switch back to the default BWP (e.g., BWP 0) as the active BWP. When sCellDeactivationTimer Upon expiration (e.g., if the cell is a SCell), the radio device can deactivate the cell and / or stop the BWP inactivity timer. In response to a PCell, the radio device may not deactivate the cell and may not apply any changes to the PCell. sCellDeactivationTimer .

[0249] 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 permission of configured permission type 1 according to the stored configuration (if any).

[0250] 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 grants of configured grant type 2; and / or suspend any configured uplink grants of configured type 1.

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

[0252] 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 initial active DL BWP is used. In the example, the default DL BWP can be provided via the higher-layer parameter... bwp-InactivityTimer Provide the wireless device with a timer value for the primary cell. If configured, the wireless device may 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 wireless device fails to detect DCI format 1_1 for paired spectrum operation, or fails to detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation.

[0253] In the example, if the wireless device is configured to have higher-layer parameters that indicate the default DL BWP among the configured DL BWPs. Default-DL-BWP The auxiliary cell, and the wireless device is configured with higher-layer parameters indicating the timer value. bwp-InactivityTimer Then the radio device program on the secondary cell can be the same as the radio device program on the primary cell that uses the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0254] In the example, if the wireless device passes through higher-layer parameters on a secondary cell or carrier... Active-BWP-DL- SCell (Active-BWP-DL-SCell) is configured with the first active DL BWP and is configured via higher-level parameters. Active-BWP-UL- SCellIf (Active-BWP-UL-SCell) is configured with a first active UL BWP, 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.

[0255] In the example, the set of PDCCH candidates to be monitored by the wireless device can be defined with respect to the PDCCH search space set. The search space set includes either the CSS set or the USS set. The wireless device monitors PDCCH candidates from one or more of the following search space sets: MIB In pdcch-ConfigSIB1 Or by PDCCH-ConfigCommon In searchSpaceSIB1 Or by PDCCH-ConfigCommon In searchSpaceZero For the Type 0-PDCCH CSS set configured with a DCI format CRC scrambled by SI-RNTI on the primary cell of the MCG; for the Type 0A-PDCCH CSS set configured with a DCI format CRC scrambled by SI-RNTI on the primary cell of the MCG, as defined in searchSpaceOtherSystemInformation in PDCCH-ConfigCommon; PDCCH-ConfigCommon In ra-SearchSpace For Type 1-PDCCHCSS sets with DCI format configurations of CRCs scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell; by PDCCH-ConfigCommon In pagingSearchSpace For the Type 2-PDCCH CSS set with a DCI format configuration of CRC scrambled by P-RNTI on the primary cell of the MCG; by PDCCH-Config (PDCCH-Configuration) with searchSpaceType = common of SearchSpace For DCI formats with CRCs scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI, and for Type 3-PDCCH CSS sets configured only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI; and for those configured by PDCCH-Config The ones with searchSpaceType = ue-Specific of SearchSpaceFor USS sets configured with DCI format scrambled CRCs by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

[0256] In one example, the wireless device is configured based on one or more PDCCH parameters (e.g., based on those described later). Figure 27 The example implementation determines the PDCCH monitoring timing on the active DL BWP, wherein one or more PDCCH configuration parameters include: PDCCH monitoring periodicity, PDCCH monitoring offset, and PDCCH monitoring mode within the time slot. For the search space set (SS) s ),if Then the wireless device is identified as numbered The frame number is There are PDCCH monitoring opportunities in the time slots. In the configuration parameter set µ The number of time slots in a time frame. These are PDCCH configuration parameters (e.g., based on...) Figure 27 The time slot offset indicated in the example implementation (e.g.) These are PDCCH configuration parameters (e.g., based on...) Figure 27 The PDCCH monitoring periodicity is indicated in the example implementation (as per the example implementation). The wireless device monitors from the time slot. Begin monitoring PDCCH candidate persistence for the search space set A series of consecutive time slots, and in the following The consecutive time slots are not targeted at the search space set. Monitor PDCCH candidates. In the example, CCE aggregation level. The USS below is based on the CCE aggregation level The set of PDCCH candidates is used to define it.

[0257] In the example, the wireless device is designed for use with CORESET. Related search space set The decision is made regarding the value of the carrier indicator field. For the corresponding service cell's activity DL BWP, in time slots In the search space set, the PDCCH candidates Corresponding aggregation level The CCE index is , For USS , ,for ,for ,for ,and In CORESET middle, This refers to the number of CCEs, numbered from 0 to... If the wireless device is configured with the CrossCarrierSchedulingConfig field for monitoring the serving cell on its PDCCH, then It is the carrier indicator field value; otherwise, including for any CSS, ; ,in The wireless device is configured to be compatible with... For the corresponding service cell, this is for the search space set aggregation level The number of PDCCH candidates monitored; for any CSS, For USS, It is pervasive for the search space set CCE aggregation level All configurations value The maximum value; and used for The RNTI value is C-RNTI.

[0258] In the example, the wireless device can monitor a set of PDCCH candidates based on configuration parameters that include a set of 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 what will be described later. Figure 26 Example implementations are 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 public SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. Possible DCI formats may be based on Figure 23 Example implementation scheme.

[0259] Figure 23An 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 contain different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In the example, DCI format 0_0 can be used to schedule PUSCH in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCH in a cell, or to indicate a configured PUSCH permission CG-DFI (Configured Downlink Permission Feedback Information), etc. The DCI formats that the radio device can monitor in the SS can be configured.

[0260] Figure 24A An example of configuration parameters for the Master Information Block (MIB) of a cell (e.g., PCell) is shown. In this example, the radio device receives 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). systemFrameNumber Subcarrier spacing indication ( subCarrierSpacingCommon The frequency domain offset between the SSB and the entire resource block grid in terms of the number of subcarriers. ssb-SubcarrierOffset Indicators indicating whether a residential area is prohibited ( ) cellBarred ), DMRS location indication (indicating the location of DMRS) dmrs-TypeA-Position ), including the parameters of the PDCCH CORESET and SS, which contain the common CORESET. pdcch-ConfigSIB1 ), public search space, and necessary PDCCH parameters, etc.

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

[0262] Figure 24B An example configuration for CORESET#0 is shown. Figure 24B As shown, based on controlResourceSetZero The integer value allows the wireless device to 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.

[0263] In the example, pdcch-ConfigSIB1A second parameter can be included (e.g., searchSpaceZero ), which indicates the public search space with the initial BWP ID #0 (e.g., SS#0) of the cell. searchSpaceZero It can be an integer between 0 and 15. Each integer between 0 and 15 can identify the configuration of SS#0.

[0264] Figure 24C An example configuration for SS#0 is shown. For example... Figure 24C As shown, based on searchSpaceZero The integer value allows the wireless device to determine one or more parameters for time slot determination used in PDCCH monitoring (e.g., O, M ), the number of first symbol indexes used for PDCCH monitoring and / or the number of search spaces per time slot.

[0265] In the example, based on the received MIB, the wireless device can monitor the PDCCH via SS#0 of CORESET#0 to receive the DCI of Scheduling System Information Block 1 (SIB1). The SIB1 message can be based on... Figure 25 The example implementation can be used to implement this. 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.

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

[0267] In the example, DownlinkConfigCommonSIBIt may include parameters of the initial downlink BWP of the serving cell (e.g., SpCell). initialDownlinkBWP (IE). The parameters of the initial downlink BWP can be included. BWP- DownlinkCommon In IE (e.g.) Figure 26 (As shown). BWP-DownlinkCommon The IE (Internet Explorer) can be used to configure common parameters of the serving cell's downlink BWP (Background Power Controller). The base station can be configured... locationAndBandwidth This ensures that the initial downlink BWP includes the entire CORESET#0 of the serving cell in the frequency domain. The radio device can apply this field upon receiving it. locationAndBandwidth (For example, determine about this) locationAndBandwidth The frequency position of the described signal is [not specified], but it remains at CORESET#0 until [the signal is received]. RRCSetup / RRCResume / RRCReestablishment after.

[0268] In the example, DownlinkConfigCommonSIB The IE can contain parameters for paging channel configuration. These parameters can include paging loop values ​​( T ,Depend on defaultPagingCycle IE indicates the paging frame (PF) and paging frame offset in the paging DRX cycle. PF_offset The total number of ) N ) parameters ( nAndPagingFrameOffset IE), the total number of paging opportunities (PO) per PF ( N ), indicating the first PDCCH monitoring timing of each PO paging of the PF (First PDCCH Monitoring Timing Indication Parameter). firstPDCCH-MonitoringOccasionofPO (IE). Based on the parameters configured in the PCCH, wireless devices can monitor the PDCCH to receive paging messages.

[0269] In the example, it is possible to SIB1 Transmit signal notification parameters first-PDCCH- MonitoringOccasionOfPO This is used for paging in the initial DL BWP. For paging in DLBWPs other than the initial DL BWP, parameters can be signaled in the corresponding BWP configuration. first-PDCCH- MonitoringOccasionOfPO .

[0270] Figure 26 The following diagram shows the RRC configuration parameters in the downlink BWP of the serving cell (e.g., BWP- DownlinkCommon Example of an IE (Internet Interface). A base station can transmit one or more configuration parameters of the serving cell's downlink BWP (e.g., the initial downlink BWP) to radio devices (or multiple radio devices). For example... Figure 26As shown, one or more configuration parameters of the downlink BWP may include: one or more general BWP parameters of the downlink BWP, and one or more cell-specific parameters of the downlink BWP's PDCCH (e.g., using...). pdcch-ConfigCommon IE indicates that one or more cell-specific parameters of this BWP's PDSCH (e.g., in the context of IE). pdsch-ConfigCommon (IE indicates) and one or more other parameters. pdcch-ConfigCommon IE can include the parameter COESET #0 (for example, controlResourceSetZero It can be used in any public or UE-specific search space. controlResourceSetZero The value can be like MIBpdcch-ConfigSIB1 The corresponding bits in the same way are interpreted. pdcch-ConfigCommon IE can include parameters from other common control resource sets (e.g., using...). commonControlResourceSet (This indicates that) the additional set of public control resources can be configured and used in any public or UE-specific search space. If the network configures this field, then for this... ControlResourceSet It uses all numbers except 0. ControlResourceSetId Network configuration SIB1 In commonControlResourceSet This ensures that it is included in the bandwidth of CORESET#0. pdcch-ConfigCommon IE can include parameters for a list of other public search spaces (e.g., with...). commonSearchSpaceList (This can be based on what will be described later). Figure 27 The example demonstrates how to implement parameters for the search space. pdcch-ConfigCommon IE can indicate the search space used for paging from the list of search spaces (e.g., pagingSearchSpace ), and the search space for random access procedures (e.g., ra-SearchSpace ), and the search space for SIB1 messages (e.g., searchSpaceSIB1 ), public search space #0 (e.g., searchSpaceZero ) and one or more other search spaces.

[0271] like Figure 26 As shown, the control resource set (CORESET) can be associated with the CORESET index (e.g., ControlResourceSetId This is related to the above. Figure 14A and / or Figure 14B The example implementation described illustrates how to implement CORESET. A CORESET index with a value of 0 can be identified in... MIB China and in ServingCellConfigCommon ( controlResourceSetZero The public core set configured in () and not available in ControlResourceSet Used in IE. A CORESET index with other values ​​can identify information generated by dedicated signaling or... SIB1The CORESET configured in the middle. controlResourceSetId It is unique within the BWP of the serving cell. CORESET can be associated with an index of the CORESET pool that indicates the CORESET. coresetPoolIndex Associated with CORESET. CORESET can be associated with duration parameters (e.g., Duration Time Associated with this, the duration parameter indicates the continuous duration of CORESET in terms of the number of signs. In the example, such as... Figure 26 As shown, CORESET's configuration parameters may include at least one of the following: frequency resource indication (e.g., frequencyDomainResources ), CCE-REG mapping type indicator (e.g., cce-REG-MappingType ), multiple TCI states, indicators indicating whether a TCI exists in the DCI, etc.

[0272] Figure 27 The configuration of the search space is shown (e.g., SearchSpace Example (IE). In the example, one or more search space configuration parameters may include at least one of the following: search space ID ( searchSpaceId ), Control Resource Set ID ( controlResourceSetId ), monitoring time slot periodicity and offset parameters ( monitoringSlotPeriodicityAndOffset ), search space duration value ( Duration ), monitoring symbol indication ( monitoringSymbolsWithinSlot ), the number of candidates for the aggregation level ( nrofCandidates ) and / or the SS type indicating the public SS type or the UE-specific SS type ( searchSpaceType Monitoring slot periodicity and offset parameters can indicate the slots used for PDCCH monitoring (e.g., within a radio frame) and the slot offset (e.g., relative to the start of a radio frame). Monitoring symbol indication can indicate on which (and which) symbols of a slot the wireless device can monitor the PDCCH on the SS. Control resource set ID can identify the control resource set on which the SS can reside.

[0273] 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... The example implementation described is used to achieve this.

[0274] Figure 25 An example of the transition between a quiescent state and a non-quiescent state on an SCell is shown. In the example, the base station may transmit one or more RRC messages to the radio device, including configuration parameters of the SCell, where the SCell includes multiple BWPs. Among these multiple BWPs, the first BWP (e.g., Figure 28 BWP 3 in the configuration can be configured as a non-resting BWP, and / or a second BWP (e.g., Figure 28 BWP 1) in the configuration can be configured to pause BWP. In the example, the default BWP (e.g., Figure 28 A BWP (Best-Packed WP) can be configured among these multiple BWPs. In the example, a non-resting BWP can be a BWP that the wireless device can activate in response to transitioning a SCell from a resting state to a resting state. In the example, a resting BWP can be a BWP that the wireless device can switch to in response to transitioning a SCell from a resting state to a resting state. In the example, configuration parameters can indicate one or more search spaces and / or CORESETs configured on a non-resting BWP. Configuration parameters can indicate that no search space or CORESET is configured on a resting BWP. Configuration parameters can indicate CSI reporting configuration parameters for a resting BWP.

[0275] In the example, the default BWP can be different from the resting BWP. Configuration parameters can indicate one or more search spaces or one or more CORESETs configured on the default BWP. When a BWP inactivity timer expires or a DCI indication is received indicating a switch to the default BWP, the wireless device can switch to the default BWP as the active BWP. When the default BWP is active, the wireless device can perform at least one of the following: monitor the PDCCH on the default BWP of the SCell; receive the PDSCH on the default BWP of the SCell; transmit the PUSCH on the default BWP of the SCell; transmit the SRS on the default BWP of the SCell; and / or transmit a CSI report (e.g., periodic, aperiodic, and / or semi-persistent) for the default BWP of the SCell. In the example, when a rest / non-rest indication indicating a resting state of the SCell is received, the wireless device can switch to the resting BWP as the active BWP of the SCell. In response to switching to a quiescent BWP, the radio device may perform at least one of the following: suppress PDCCH on the quiescent BWP monitoring SCell (or suppress monitoring SCell if the SCell is scheduled across carriers by another cell); suppress PDSCH on the quiescent BWP receiving SCell; suppress PUSCH on the quiescent BWP transmitting SCell; suppress SRS on the quiescent BWP transmitting SCell; and / or transmit CSI reports for the quiescent BWP of the SCell (e.g., periodic, aperiodic, and / or semi-persistent).

[0276] like Figure 28 As shown, a base station can transmit a DCI to a radio device via PDCCH resources. This DCI includes a rest / non-rest indication indicating the resting or non-resting state of a SCell. In response to the rest / non-rest indication indicating the resting state of the SCell, the radio device can perform the following actions: if the SCell was in a non-resting state before receiving the DCI, transition the SCell to a resting state; or if the SCell was in a resting state before receiving the DCI, maintain the SCell in a resting state. Transitioning the SCell to a resting state may include switching to the SCell's resting BWP (e.g., configured by the base station). In response to the rest / non-rest indication indicating the non-resting state of the SCell, the radio device can perform the following actions: if the SCell was in a resting state before receiving the DCI, transition the SCell to a non-resting state; or if the SCell was in a non-resting state before receiving the DCI, maintain the SCell in a non-resting state. Transitioning the SCell to a non-resting state may include switching to the SCell's non-resting BWP (e.g., configured by the base station).

[0277] like Figure 28As shown, in response to transitioning the SCell from a dormant state to a non-dormant state, the wireless device can switch to a non-dormant BWP configured by the base station (e.g., as...). Figure 28 The BWP shown is 3) acting as the active BWP for the SCell. Based on the switch to a non-resting BWP as the active BWP for the SCell, the radio device may perform at least one of the following: monitor the PDCCH on the active BWP of the SCell (or monitor the PDCCH for the SCell when the SCell is configured to await cross-carrier scheduling by another cell); receive the PDSCH on the active BWP of the SCell; and / or transmit the PUCCH / PUSCH / RACH / SRS on the active BWP (e.g., if the active BWP is an uplink BWP).

[0278] like Figure 28 As shown, in response to transitioning the SCell from a non-resting state to a resting state, the wireless device can switch to a resting BWP configured by the base station (e.g., as...). Figure 28 The BWP for the SCell shown is 1). Based on the quiescent BWP switched to the SCell, the radio device may perform at least one of the following: suppress monitoring of the PDCCH on the quiescent BWP of the SCell (or suppress monitoring of the PDCCH for the SCell when the SCell is configured to await cross-carrier scheduling by another cell); suppress receiving the PDSCH on the quiescent BWP of the SCell; suppress transmission of PUCCH / PUSCH / RACH / SRS on the quiescent BWP (e.g., if the quiescent BWP is an uplink BWP); and / or transmit CSI reports for the quiescent BWP of the SCell based on the CSI report configuration parameters configured on the quiescent BWP of the SCell.

[0279] In the example implementation, DRX operation can be used by the wireless device to improve its battery life. With DRX configured, the wireless device can discontinuously monitor downlink control channels, such as PDCCH or EPDCCH. The base station can configure DRX operation using a set of DRX parameters (e.g., using RRC configuration). The DRX parameter set can be selected based on application type, allowing the wireless device to reduce power and resource consumption. In response to DRX being configured / activated, the wireless device can receive packets with extended latency because the wireless device may be in a DRX sleep / off state when data arrives, and the base station can wait until the wireless device transitions to a DRX-on state.

[0280] In the example implementation, during DRX mode, the wireless device can shut down most of its circuitry when there are no packets to receive. The wireless device can monitor the PDCCH discontinuously in DRX mode. When DRX operation is not configured, the wireless device can monitor the PDCCH continuously. During this period, the wireless device listens to the downlink (DL) (or monitors the PDCCH) in a state known as DRX activity. The time during which the wireless device does not listen to / monitor the PDCCH in DRX mode is called the DRX sleep state.

[0281] Figure 28 An example of an implementation scheme is shown. The base station can transmit an RRC message including one or more DRX parameters for a DRX cycle. These parameters may include a first parameter and / or a second parameter. The first parameter may indicate a first time / window value for the DRX activity state of the DRX cycle (e.g., DRX on duration). The second parameter may indicate a second time for the DRX sleep state of the DRX cycle (e.g., DRX off duration). These parameters may also include the duration of the DRX cycle. During the DRX activity state, the radio device can monitor the PDCCH to detect one or more DCIs on the serving cell. During the DRX sleep state, the radio device can stop monitoring the PDCCH on the serving cell. When multiple cells are active, the radio device can monitor all PDCCHs on (or for) all cells during the DRX activity state. During the DRX off duration, the radio device can stop monitoring all PDCCHs on (or for) all cells. The radio device can repeat the DRX operation based on these one or more DRX parameters.

[0282] In the example implementation, DRX can be beneficial to the base station. In this example, if DRX is not configured, the radio device can frequently (e.g., based on configuration) transmit periodic CSI and / or SRS. With DRX, the radio device can refrain from transmitting periodic CSI and / or SRS during DRX-off periods. The base station can then allocate these resources to other UEs to improve resource utilization efficiency.

[0283] In the example implementation, the MAC entity can be configured by an RRC with DRX functionality, which controls the downlink control channel (e.g., PDCCH) of the radio device to monitor the activity of multiple RNTIs for the MAC entity. The multiple RNTIs can include at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. In the example, in response to being in RRC_CONNECTED, if DRX is configured, the MAC entity can monitor the PDCCH discontinuously using DRX operation; otherwise, the MAC entity can monitor the PDCCH continuously.

[0284] In the example implementation, RRC can control DRX operation by configuring multiple timers. These multiple timers may include: a DRX enable duration timer (e.g., ...). Figure 29 ); DRX inactive timer (e.g., drx-onDurationTimer Downlink DRX HARQ round-trip time (RTT) timer (e.g., [[ID=?]]drx-InactivityTimer drx-HARQ- ); Uplink DRX HARQ RTT timer (e.g., RTT-TimerDL Downlink retransmission timer (e.g., drx-HARQ-RTT-TimerUL ); Uplink retransmission timer (e.g., drx-RetransmissionTimerDL drx- ); one or more parameters of the short DRX configuration (e.g., RetransmissionTimerUL and / or drx-ShortCycle drx- ) and one or more parameters of the long DRX configuration (e.g., ShortCycleTimer In the example, the time granularity of the DRX timer can be based on PDCCH subframes (e.g., indicated as psf in the DRX configuration) or on milliseconds.

[0285] In the example implementation, in response to the configuration of a DRX loop, the active time of the DRX operation may include the time during which at least one timer is running. This at least one timer may include... drx-LongCycle , drx-onDurationTimer drx- , InactivityTimer , drx-RetransmissionTimerDL or drx-RetransmissionTimerUL During the active period of DRX operation, wireless devices can monitor PDCCHs with RNTIs affected by the DRX operation. RNTIs may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and / or AI-RNTI.

[0286] In the example implementation, mac- The (drx-inactive-timer) specifies the duration for which the wireless device can be active after successfully decoding a PDCCH indicating a new transmission (UL, DL, or SL). This timer can be restarted upon receiving a PDCCH for a new transmission (UL, DL, or SL). The wireless device can transition to DRX mode (e.g., using a short or long DRX cycle) in response to the expiration of this timer. In the example, ContentionResolutionTimer This could be the first type of DRX loop that a wireless device needs to follow when entering DRX mode (e.g., if configured). In the example, drx-Inactivity-Timer IE indicates the length of a short loop. drx-ShortCycle It can be expressed as multiple DRX-Config A timer can indicate the number of initial DRX cycles that follow a short DRX cycle before entering a long DRX cycle. drx-ShortCycleTimer You can specify the duration at which the DRX cycle begins (for example, when DRX is enabled). shortDRX-Cycle drx-onDurationTimer It can indicate the duration before entering sleep mode (DRX off). drx- onDurationTimer You can specify the minimum duration from the moment a new transmission is received, before the wireless device might expect a retransmission of the same packet. This timer can be fixed and is not configurable by RRC. drx-HARQ-RTT- It can indicate the maximum duration for which a wireless device can monitor the PDCCH when it anticipates a retransmission from the base station.

[0287] In response to a DRX cycle being configured, the active time may include the time during which a scheduling request is sent on the PUCCH and pending. In the example, in response to a DRX cycle being configured, the active time may include the time during which an uplink grant for a pending HARQ retransmission can occur and data exists in the corresponding HARQ buffer used to synchronize the HARQ process. In response to a DRX cycle being configured, the active time may include the time during which a PDCCH indicating a new transmission addressing a MAC entity's C-RNTI has not been received after a successful reception of a random access response with a preamble not selected by the MAC entity.

[0288] In the example implementation, the DL HARQ RTT timer (e.g., TimerDL The data may expire in a subframe, and the corresponding HARQ process may not have been successfully decoded. A MAC entity can start the corresponding HARQ process. drx-RetransmissionTimerDL UL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL It can expire in a subframe. The MAC entity can be started for the corresponding HARQ process. drx-RetransmissionTimerDL .

[0289] In the example, the wireless device can (e.g., based on the above regarding...) drx-HARQ-RTT-TimerUL The described example implementation receives a DRX command MAC CE or a long DRX command MAC CE. In response to receiving a DRX command MAC CE and / or a long DRX command MAC CE, the MAC entity of the wireless device can stop... drx-RetransmissionTimerUL And / or stop Figure 19 In the example, if drx-onDurationTimer If the MAC entity expires and a short DRX cycle is being configured, it can start or restart. drx-InactivityTimer And a short DRX loop can be used. Otherwise, a MAC entity can use a long DRX loop.

[0290] In the example, drx-InactivityTimer It can expire in a subframe. MAC entities can use long DRX loops. In the example, a MAC control element can receive long DRX commands. MAC entities can stop. drx-ShortCycleTimer And long DRX loops can be used.

[0291] In the example implementation, if a short DRX cycle is used and [(SFN * 10) + subframe number] modulo ( drx-ShortCycleTimer drx-ShortCycleTimer )=( DRX- )mold( ShortCycle Then the wireless device can start from the beginning of the subframe. drxStartOffset Then begin drx-ShortCycle ,in drx-SlotOffset drx-onDurationTimer drx-SlotOffset There seems to be an issue with the "drx-InactivityTimer" tag where it's repeated with a "?" in the middle. Please check and correct the original text if possible for a more accurate translation. It can be an instruction at startup drx-onDurationTimer The previous delay value (configured in the DRX configuration parameters). In the example, if a long DRX loop is used and [(SFN * 10) + subframe number] modulo ( drx-longCycle )= drxStartOffset Then the wireless device can start from the beginning of the subframe. drx-SlotOffset Then begin drx-onDurationTimer ,in drx-SlotOffset It can be an instruction at startup drx-onDurationTimer The previous delay value (configured in the DRX configuration parameters).

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

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

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

[0295] Figure 31AAn example of a power-saving mechanism based on wake-up indication is shown. The base station can transmit one or more messages to the wireless device including parameters such as the wake-up duration (e.g., power-saving duration or power-saving channel (PSCH) timing). The wake-up duration can be located in multiple time slots (or symbols) preceding the DRX on-time of the DRX cycle. This can be based on the above regarding... Figure 29 The described example implementation implements DRX cyclical operation. The gaps between the multiple time slots (or symbols), or wake-up durations, and the DRX enable duration, can be configured in the one or more RRC messages or predefined as fixed values. These gaps can be used for at least one of the following: synchronization with the base station; measurement of reference signals; and / or retuning RF parameters. The gaps can be determined based on the capabilities of the wireless device and / or the base station. In the example, parameters for the wake-up duration can be predefined without RRC configuration. In the example, the wake-up mechanism can be based on a wake-up indication via the PSCH. Parameters for the wake-up duration can include at least one of the following: the PSCH channel format (e.g., parameter set, DCI format, PDCCH format); the periodicity of the PSCH; the control resource set and / or search space of the PSCH. When parameters for the wake-up duration are configured, the wireless device can monitor the wake-up signal or PSCH during the wake-up duration. When parameters for the PSCH timing are configured, the wireless device can monitor the PSCH during the PSCH timing to detect a wake-up indication. In response to receiving a wake-up signal / channel (or a wake-up indication received via PSCH), the wireless device can wake up during the DRX active time of the next DRX cycle to monitor the PDCCH, according to the DRX configuration. In the example, in response to receiving a wake-up indication via PSCH, the wireless device can wake up during the DRX active time (e.g., when...). drx-onDurationTimer (During runtime) the wireless device monitors the PDCCH. If no PDCCH is received during the DRX active period, the wireless device can continue to sleep. The wireless device can remain asleep during the DRX off duration of the DRX cycle. In the example, if the wireless device does not receive a wake-up signal / channel (or a wake-up indication received via PSCH) during the wake-up duration (or PSCH timing), the wireless device can skip monitoring the PDCCH during the DRX active period. In the example, if the wireless device receives an indication to skip PDCCH monitoring during the wake-up duration (or PSCH timing), the wireless device can skip monitoring the PDCCH during the DRX active period.

[0296] In the example, the power-saving mechanism could be based on a sleep instruction via the PSCH. Figure 31BAn example of power saving based on sleep indication is shown. In response to receiving a sleep indication via the PSCH, the wireless device can continue to sleep and skip monitoring the PDCCH during the DRX active period (e.g., the next DRX on duration of a DRX cycle). In the example, if the wireless device does not receive a sleep indication via the PSCH during the wake-up duration, the wireless device monitors the PDCCH during the DRX active period according to the configuration parameters of DRX operation. This mechanism can reduce the power consumption of PDCCH monitoring during the DRX active period.

[0297] In the example, it can be done by... Figure 31A and Figure 31B A power-saving mechanism is implemented through a combination of methods. The base station can transmit a power-saving indication in the DCI via the PSCH, thereby instructing the radio device to wake up or skip the next DRX-enabled duration. The radio device can receive the DCI via the PSCH. In response to the power-saving indication instructing the radio device to wake up for the next DRX-enabled duration, the radio device may wake up for the next DRX-enabled duration. The radio device monitors the PDCCH in response to being woken up. In response to the power-saving indication instructing the radio device to skip (or sleep) for the next DRX-enabled duration, the radio device may sleep or skip for the next DRX-enabled duration. In response to the power-saving indication instructing the radio device to potentially sleep for the next DRX-enabled duration, the radio device skips monitoring the PDCCH for the next DRX-enabled duration.

[0298] In the example, it can be expanded or combined. Figure 30 , Figure 31A and / or Figure 31B One or more implementations are available to further improve the power consumption of wireless devices and / or the signaling overhead of base stations.

[0299] Figure 32A This indicates a switching instruction for one or more search space cluster groups (or SSSGs). Or search space cluster Group switching flagAn example of DCI format 2_0 is provided. In the example, DCI format 2_0 may include one or more slot format indicators (e.g., slot format indicator 1, slot format indicator 2, ... slot format indicator N), one or more available RB set indicators, one or more COT duration indicators, and one or more SSS group handover flags. In the example, each SSS group handover flag in the one or more SSS group handover flags may correspond to a corresponding cell group in multiple cell groups. Each cell group in the multiple cell groups may include one or more cells. When set to a first value, the SSS group handover flag in the one or more SSS group handover flags corresponding to the cell group may indicate that each cell in the cell group is handing over from the first SSS group to the second SSS group. When set to a second value, the SSS group handover flag may indicate that each cell in the cell group is handing over from the second SSS group to the first SSS group. The wireless device may be based on Figure 32B The example implementation scheme is used to perform SSS group switching.

[0300] Figure 32B This shows a DCI-based (e.g., DCI format 2_0 or) Figure 23 Examples of SSS group switching (in other DCI formats described herein). In the examples, it can be achieved by... searchSpaceGroupIdList (For example, based on) Figure 27 (Example implementation) provides wireless devices with a group index of search space sets (e.g., Type 3-PDCCH CSS set, USS set, or any other type of search space set) for PDCCH monitoring on the serving cell.

[0301] In the example, it is possible not to provide the search space set to the wireless device. searchSpaceGroupIdList If the search space set is not configured searchSpaceGroupIdList ,but Figure 32B The implementation scheme may not be suitable for monitoring PDCCH in the search space. Based on the lack of application... Figure 32B In this implementation scheme, the wireless device can monitor the search space set on the BWP without switching off from the search space set monitored by the PDCCH.

[0302] In the example, if (e.g., based on) Figure 26 The example implementation shown provides a wireless device with an indication of one or more groups of serving cells. cellGroupsForSwitchList ,but Figure 32B The implementation scheme can be applied to all serving cells within each group. If wireless equipment is not provided... cellGroupsForSwitchList ,but Figure 32B The implementation scheme can be applied only to wireless devices that are provided. searchSpaceGroupIdList The service area.

[0303] In the example, if providing to a wireless device searchSpaceGroupIdList If by searchSpaceGroupIdList Provided, wireless devices can reset PDCCH monitoring based on a search space set with group index 0.

[0304] In the example, it can provide to wireless devices. searchSpaceSwitchDelay (For example, such as) Figure 26 As shown in the figure, the number of symbols is based on the processing power of the wireless device (e.g., wireless device processing power 1, wireless device processing power 2, etc.). and SCS configuration Unless the wireless device indicates support for Wireless Device Processing Capability 2, this is used for SCS configuration. Wireless device processing capability 1 may be applicable. In the example, wireless device capability 1... and Wireless device capability 1 Wireless device capability 1 Wireless device capability 2 Wireless device capability 2 and wireless device capability 2 ,etc.

[0305] In the example, it can be made by searchSpaceSwitchTimer (For example, such as) Figure 26 As shown, (in time slots) the wireless device is provided with the information for the wireless device to be provided. searchSpaceGroupIdList The timer value for the serving cell, or, if provided, the timer value for the serving cell. cellGroupsForSwitchList The timer value provided for the serving cell set. The wireless device can decrement the timer value by one after each time slot based on a reference SCS configuration, which is the smallest SCS configuration among all configured DL BWPs in the serving cell or the serving cell set. Wireless devices can maintain a reference SCS configuration during the timer decrement procedure.

[0306] In the example, searchSpaceSwitchTimer This can be defined as a time-slot-based value used to monitor the PDCCH in the active DL BWP of the serving cell before moving to the default search space group (e.g., search space group 0). For a 15kHz SCS, the effective timer value may be one of {1, …, 20}. For a 30kHz SCS, the effective timer value may be one of {1, …, 40}. For a 60kHz SCS, the effective timer value may be one of {1, …, 80}. In the example, the base station can be the same. CellGroupForSwitch All serving cells are configured with the same timer value.

[0307] like Figure 32B As shown, a wireless device can monitor the PDCCH on the first SSS group (e.g., the first SSS group or the SSS with group index 0) based on the configuration of the cell's BWP SSS group. This can be achieved by... SearchSpaceSwitchTrigger The location of the search space cluster group switching flag field for providing services to wireless devices in DCI format 2_0. SearchSpaceSwitchTrigger Based on Figure 27 The example implementation is used for configuration. The wireless device can receive DCI (e.g., Figure 32B The first DCI has DCI format 2_0. For example, when the value of the SSS group handover flag field in DCI format 2_0 is 1, the DCI can indicate an SSS group handover of the cell. In response to receiving the DCI, the radio device can start monitoring the PDCCH according to the second SSS group (e.g., the 2nd SSS group or the SSS with group index 1) and stop monitoring the PDCCH on the first SSS group (or the SSS with group index 0 of the serving cell). The radio device can start monitoring the PDCCH on the second SSS group (e.g., the 2nd SSS group or the SSS with group index 1) at least after the last symbol of the PDCCH with DCI format 2_0. Monitoring of the PDCCH on the first SSS group ceases at the first time slot of the symbol. Based on the received DCI, the wireless device can set the timer value of the search space switching timer to be determined by... searchSpaceSwitchTimer The value provided.

[0308] In the example, the wireless device can monitor the PDCCH on the second SSS group (e.g., the 2nd SSS group or the SSS with group index 1) based on the configuration of the cell's BWP SSS group. This can be achieved by... SearchSpaceSwitchTrigger The location of the search space cluster group handover flag field for the serving cell is provided to the radio device in DCI format 2_0. The radio device can receive the DCI. The DCI can indicate the SSS group handover of the cell; for example, when the value of the search space cluster group handover flag field in DCI format 2_0 is 0, the radio device can start monitoring the PDCCH according to the search space set with group index 0, and stop monitoring the PDCCH according to the search space set with group index 1 of the serving cell. The radio device can at least after the last symbol of the PDCCH with DCI format 2_0 At the first time slot of a symbol, PDCCH monitoring begins based on the search space set with group index 0, and stops based on the search space set with group 1.

[0309] In the example, if a wireless device monitors the serving cell's PDCCH according to a first SSS group (e.g., a search space set with group index 1), the wireless device can begin monitoring the serving cell's PDCCH according to a second SSS group (e.g., a search space set with group index 0) and stop monitoring the PDCCH according to the first SSS group. For the serving cell at the beginning of the first time slot, this first time slot is at least [missing information] after the timer expires. The last symbol, or after the last symbol of the remaining channel occupancy duration of the serving cell as indicated by DCI format 2_0.

[0310] In the example, the wireless device may not be served by the cell. SearchSpaceSwitchTrigger ,For example, SearchSpaceSwitchTrigger Does not exist SlotFormatIndicator Among the configuration parameters, SlotFormatIndicator Configured to monitor the group public PDCCH against the Slot Format Indicator (SFI). In response to the lack of a provided... SearchSpaceSwitchTrigger DCI format 2_0 may not include the SSS group switching flag field. When not provided... SearchSpaceSwitchTrigger If a radio device detects a DCI format by monitoring the PDCCH according to a first SSS group (e.g., a search space set with group index 0), the radio device may begin monitoring the PDCCH according to a second SSS group (e.g., a search space set with group index 1) and cease monitoring the PDCCH for the serving cell according to the first SSS group. The radio device may monitor the PDCCH with the DCI format at least after the last symbol of the PDCCH. The wireless device begins monitoring the PDCCH according to the second SSS group at the first time slot of the symbol and stops monitoring the PDCCH according to the first SSS group. If the wireless device detects the DCI format by monitoring the PDCCH in any search space set, the wireless device can set (or restart) the timer value to the specified value. searchSpaceSwitchTimer The value provided.

[0311] In the example, the wireless device may not be served by the cell. SearchSpaceSwitchTrigger When not provided SearchSpaceSwitchTrigger If a radio device monitors the serving cell's PDCCH according to a first SSS group (e.g., a search space set with group index 1), the radio device may begin monitoring the serving cell's PDCCH according to a second SSS group (e.g., a search space set with group index 0) and cease monitoring the PDCCH according to the first SSS group. For a serving cell at the beginning of a first time slot, this first time slot must be at least [missing information] after the timer expires. The symbol, or if the radio device is provided with a search space set to monitor the PDCCH to detect DCI format 2_0, is after the last symbol of the remaining channel occupancy duration of the serving cell indicated by DCI format 2_0.

[0312] In the example, the wireless device can be configured based on the information provided to the wireless device. searchSpaceGroupIdList The search space set of the serving cell is used to determine the time slot and symbols in the time slot to start or stop PDCCH monitoring, or if provided cellGroupsForSwitchList Then, based on the minimum SCS configuration among all configurations in the serving cell or the set of serving cells in the DL BWP, it is determined. To determine the time slots and symbols in the time slots for starting or stopping PDCCH monitoring for the serving cell set, and, if applicable, in the serving cells of the corresponding DCI format 2_0 that the radio device receives the PDCCH and detects the start or stop of PDCCH monitoring based on the search space set.

[0313] In the example, the wireless device can implement the PDCCH skipping mechanism for power-saving operations.

[0314] Figure 33 An example of power-saving operation based on PDCCH skipping is shown.

[0315] In the example, the base station can transmit one or more RRC messages to the radio device, which include configuration parameters of the cell's BWP's PDCCH (e.g., based on the above regarding...). Figure 26 and / or Figure 27 (Example implementation described above). Based on the configuration parameters of the PDCCH, the wireless device can monitor the PDCCH on the BWP. The BWP can be an active downlink BWP. The wireless device can, based on the above description... Figure 22 The example implementation described is used to activate BWP.

[0316] like Figure 33 As shown, the wireless device can receive a first DCI (e.g., a first DCI indicating that the PDCCH should be skipped with a time window). The time value of the time window can be indicated by the first DCI and / or configured by one or more RRC messages. In response to receiving the first DCI, the wireless device can stop monitoring the PDCCH on the BWP. Stopping monitoring the PDCCH on the BWP can include stopping monitoring the PDCCH on one or more SSS groups configured on the BWP. The wireless device maintains the active state of the BWP. The first DCI may not indicate a handover of the active BWP. In the example, during the time window (or when the timer associated with the time window is running), the base station may not transmit the PDCCH to the wireless device.

[0317] like Figure 33 As shown, when the time window expires / ends, the radio device can resume PDCCH monitoring on the BWP. Based on the resumption of PDCCH monitoring, the radio device can receive a second DCI (e.g., a second DCI) scheduled via PDSCH. The radio device can receive the TB via PDSCH scheduled by the second DCI. In the example, in response to the expiration of the time window, the base station can transmit the second DCI to the radio device.

[0318] In the example, network energy-saving operations may include cell DTX / DRX configuration / mode / state / operation (e.g., similar to UE DRX configuration, as referenced above). Figure 29 , Figure 30 , Figure 31A and / or Figure 31B The UE DRX configuration is described. Unlike the UE DRX configuration, the cell DTX / DRX configuration applies to all UEs within the cell. During cell DTX operation, the base station can periodically turn on the cell (or multiple cells) for a first duration, and then turn it off for a second duration. In this specification, the UE DRX configuration specifically configured for radio devices may be referred to as the C-DRX configuration or simply the DRX configuration, which differs from the cell DRX configuration applied to all radio devices within the cell.

[0319] When a cell DTX configuration is configured for a cell (and the cell DTX configuration is activated if an explicit activation command is required), during the first duration of the cell DTX configuration (e.g., during the cell DTX activation time in the first power state / mode, during the cell DTX on duration, etc.), the base station may transmit periodic downlink signals (e.g., SIB / SSB / CSI-RS / TRS), downlink control channel (PDCCH), downlink shared channel (PDSCH), etc., as the base station would do for the cell under normal conditions (e.g., when the cell DTX configuration is not configured as in legacy systems). During the second duration of the cell DTX configuration (e.g., in the second power state / mode, during the cell DTX inactive / inactive period, during the cell DTX off duration, etc.), the base station may reduce the transmission power / bandwidth / beam of the periodic downlink signal (e.g., CSI-RS), stop the transmission of the periodic downlink signal (e.g., CSI-RS), maintain the transmission SSB, and / or stop the transmission of PDCCH / PDSCH (e.g., SPS PDSCH and / or dynamically scheduled PDSCH) via the cell. Radio devices may stop receiving periodic downlink signals and PDCCH / PDSCH via the cell. The base station may, for example, perform cell DTX operations periodically (for each DTX cycle) on the cell by configuring the periodicity of DTX cycles including a first duration and / or a second duration.

[0320] When a cell DRX configuration is configured for a cell (and the cell DRX configuration is activated if an explicit activation command is required), during the first duration of the cell DRX configuration (e.g., in the first power state / mode, during the cell DRX activation period, during the cell DRX on period, etc.), the base station may receive and / or the radio device may transmit PUSCH / PUCCH / SRS via the cell, as the base station does in the normal state of the cell (e.g., when the cell DRX configuration is not configured as in legacy systems). During the second duration of the cell DRX configuration (e.g., in the second power state / mode, during the cell DRX inactive / non-active period, during the cell DRX off period, etc.), the base station may stop receiving and / or the radio device may stop transmitting PUSCH (e.g., dynamically scheduled PUSCH and / or configured permitted PUSCH), PUCCH (e.g., SR / CSI / HARQ-ACK), and / or SRS via the cell. The base station can periodically perform cell DRX operations for each DRX cycle, for example, by configuring the periodicity of DRX cycles including a first duration and / or a second duration.

[0321] In the examples, cell DTX configuration and cell DRX configuration can be configured / activated / deactivated individually or jointly. In this specification, one or more implementations described for cell DTX configuration may be applied to cell DRX configuration, where applicable, and the cell DTX configuration and cell DRX configuration may be interchanged.

[0322] Figure 34 An example of cell DTX (which is similarly applied to cell DRX) for network energy saving is shown. In the example, at the first time (e.g., T0), the radio device (UE) may receive and / or the base station (gNB) may transmit one or more RRC messages including configuration parameters of the cell (or multiple cells). This can be based on the above regarding... Figure 10A or Figure 10B The described example implementation scheme implements a cell. The cell can be a PCell / PSCell. In the example, the cell can be an SCell.

[0323] In the example, one or more RRC messages may include configuration parameters (first parameters) specific to the radio device's DRX configuration. The DRX configuration may be referred to as a UE-specific DRX configuration (UE DRX configuration, C-DRX configuration, or DRX configuration). Different radio devices may receive different configuration parameters for the DRX configuration. The configuration parameters of the DRX configuration are specific to the radio device receiving the UE-specific RRC messages. The DRX configuration may be based on the above regarding... Figure 29 and / or Figure 30 The described example implementation is used. In the example, configuration parameters for DRX configuration of the wireless device may include: the value of the DRX cycle (short cycle or long cycle) of the DRX configuration, and the time offset value of the start point of the DRX cycle relative to the reference subframe (e.g., subframe 0 of the radio frame). drx_StartOffset ), the first timer value of the DRX start duration timer ( drx-onDurationTimer ), used to determine the time slot offset value for the delay (e.g., multiple time slots) before starting the DRX enable duration timer at the beginning of a subframe. drx_SlotOffset ), the second timer value of the DRX inactive timer ( drx-InactivityTimer ), the third timer value of the DRX retransmission timer ( drx-RetransmissionTimerDL or drx-RetransmissionTimerUL ) and / or the fourth timer value of the DRX HARQ RTT timer ( drx-HARQ-RTT-TimerDL or drx-HARQ-RTT-TimerUL ).

[0324] In the example, one or more RRC messages may include configuration parameters (second parameters) of the cell DTX configuration. One or more RRC messages may include cell-wide RRC messages (e.g., MIB, SIB1 / SIB2 / SIB3 / ... etc.). The cell DTX configuration may be referred to as cell-level DTX configuration (or cell DTX configuration, DTX configuration, cell-wide DTX configuration, etc.), which is applied to all radio devices in the cell. The configuration parameters of the cell DTX configuration may include the periodicity value of the cell DTX cycle and the time offset value of the start point of the cell DTX cycle. In the example, the configuration parameters of the cell DTX configuration may include at least one of the following: a first length indication of a first time period of the cell DTX active time (or cell DTX on duration) of the cell DTX cycle and / or a second length indication of a second time period of the cell DTX inactive / non-active time (or cell DTX off duration) of the DTX cycle.

[0325] In the example, for instance, if the cell is a SCell, the wireless device can receive a SCell activation / deactivation MAC CE indicating the cell's activation. Based on the received SCell activation / deactivation MAC CE, the wireless device can, for example, base its actions on the above-mentioned... Figure 21A , Figure 21B and / or Figure 22 The described example implementation scheme is used to activate SCell. Wireless devices can be based on the above description... Figure 22 The described example implementation performs downlink reception and / or uplink transmission via an activated SCell.

[0326] exist Figure 34 In the example, the wireless device may receive the first message at a second time (e.g., T1), which includes parameters indicating the activation (or triggering, activation, initiation, etc.) of the cell's DTX configuration. If the cell is a SCell, the wireless device may receive the first message after the cell has been activated (e.g., based on receiving a SCell activation / deactivation MAC CE indicating cell activation).

[0327] In the example, the first message may include at least one of the following: an RRC message (which may differ from one or more RRC messages received within T0 that configure UE DRX configuration and / or cell DTX configuration), a MAC CE, a DCI, or any combination thereof. The MAC CE enabling cell DTX configuration may differ from an existing MAC CE (e.g., such as...). Figure 19 (As shown in the diagram). The DCI used to enable / activate the cell DTX configuration can differ from the existing DCI format (e.g., as shown in the diagram). Figure 23(As shown in the diagram). DCI can be a group common DCI transmitted to multiple wireless devices in a cell.

[0328] In the example, when cell DTX configuration is enabled / activated (or subsequently), during the first duration of the cell DTX active time in the DTX cycle used for cell DTX configuration, the base station can transmit periodic downlink signals (e.g., SIB / SSB / CSI-RS / TRS), PDCCH / PDSCH, etc., as the base station does in the normal state of the cell. When cell DTX configuration is enabled / activated (or subsequently), during the second duration of the cell DTX inactive / non-active time in the DTX cycle used for cell DTX configuration, the base station can reduce the transmission power / bandwidth / beam of CSI-RS, stop CSI-RS transmission, and / or stop PDCCH / PDSCH transmission, while the base station can maintain the transmission of MIB / SSB / SIB (which can be used for synchronization of legacy radio equipment or radio equipment in RRC_IDLE or RRC_INACTIVE states).

[0329] exist Figure 34 In the example, in response to receiving a first message indicating that cell DTX configuration is enabled (or triggered, activated, initiated, etc.), the radio device can perform UE DRX operation (if configured) based on both the first parameter of the UE DRX configuration and the second parameter of the cell DTX configuration. In response to receiving a first message indicating that cell DTX configuration is enabled (or triggered, activated, initiated, etc.), if UE DRX is not configured, the radio device can perform cell DTX based on the second parameter of the cell DTX configuration.

[0330] In the example, if the UE DRX configuration is configured, the wireless device can perform UE DRX operations, which include, according to... Figure 29 The example implementation is within the first duration of the cell DTX activity time (indicated by the second parameter) during the UE DRX activity time (for the purposes of the above). Figure 29 The UE DRX configuration shown indicates that one or more RNTIs associated with it are discontinuously monitoring the PDCCH. According to... Figure 29 In an example implementation, the wireless device can skip PDCCH monitoring for one or more RNTIs associated with UE DRX operation during UE DRX inactivity time, which may be during a first duration of cell DTX activity time or a second duration of cell DTX inactivity time.

[0331] In the example, the radio device may not be configured with UE DRX configuration. In this case, the radio device can monitor / receive MIB / SSB / SIB / CSI-RS / PDSCH / PDCCH during the first time of the cell DTX active time of the cell DTX cycle configured with cell DTX, and stop monitoring / receiving CSI-RS / PDSCH / PDCCH during the second time of the cell DTX inactive time of the cell DTX cycle after the cell DTX configuration is activated.

[0332] exist Figure 34 In the example, the base station may determine to disable (or release, deactivate, clear, etc.) the cell DTX configuration, for example, when an increasing number of active radio devices enter or move into the cell, and / or when an increasing amount of (urgent) downlink / uplink data awaits transmission. When an increasing number of active radio devices enter or move into the cell, and / or when an increasing amount of (urgent) downlink / uplink data awaits transmission, the cell-level DTX configuration (always maintained, including periodic transitions between cell DTX active and inactive periods) may not guarantee data transmission latency for these situations. To improve transmission latency, the base station may, for example, transmit a second message at T2 indicating that the cell DTX configuration is disabled (or released, deactivated, cleared, etc.). In response to deactivating the cell DTX configuration, in addition to maintaining the transmission of MIB / SSB / SIB via the cell, the base station may also resume the transmission of CSI-RS / TRS / PDCCH / PDSCH via the cell based on the downlink signal configuration parameters.

[0333] In the example, the second message may include at least one of the following: an RRC message (which may differ from the first message received in T1 to enable / activate the cell DTX configuration), a MAC CE, a DCI, or any combination thereof. The DCI and the corresponding PDCCH configuration may be based on what will be described below. Figure 35 This can be implemented using an example.

[0334] exist Figure 34 In the example, based on receiving a second message disabling / deactivating the cell DTX configuration, the radio device can assume / determine that the cell is (always) in an on state (or a first power state / mode or normal power state). Based on the disabling / deactivating cell DTX operation and determining that the cell is in an on state (or a first power state / mode or normal power state), the radio device can, for example, perform a UE-specific DRX operation (if configured) by ignoring the second parameter of the cell DTX configuration. If UE-specific DRX is configured for the radio device, the radio device can, based on the above regarding... Figure 29 and / or Figure 30The described example implementation scheme is used to perform UE-specific DRX operations.

[0335] Figure 35 It shows the basis Figure 34 Example implementation of a PDCCH timing for activating / deactivating the DCI in a cell DTX configuration. In the example, the base station may transmit and / or the radio device may receive one or more RRC messages, which include configuration parameters for the PDCCH indicating the activation / deactivation of the DCI in the cell DTX configuration. The configuration parameters may indicate one or more search spaces (sets), one or more control resource sets, the DCI format for the DCI (and / or an indication of the size of the DCI format), the time window for receiving the DCI, and the time interval between the end of the time window and the start of the cell DTX configuration. The one or more RRC messages include... Figure 34 The example cell DTX configuration parameters.

[0336] In the example, a time window can appear periodically before cell DTX configuration begins. The time interval can be based on the UE's ability to receive DCI and activate / deactivate cell DTX configuration. Within the time window, one or more PDCCH monitoring opportunities (or PDCCH opportunities) can exist based on configuration parameters of one or more search spaces and / or one or more control resource sets. The periodicity of the time window can be the same as or a multiple of the cell DTX configuration periodicity. Figure 35 In the example, the periodicity of the time window is the same as the periodicity of the cell DTX configuration.

[0337] In the example, the configuration parameters of the PDCCH used to indicate the activation / deactivation of the DCI configured in the cell DTX configuration can be per BWP configured for the cell, where each BWP configured on the cell is associated with BWP-specific configuration parameters for activating / deactivating the DCI configured in the cell DTX configuration. Configuring the parameters on each BWP allows radio devices to switch active BWPs without losing the DCI.

[0338] In the example, the configuration parameters of the PDCCH used to indicate the activation / deactivation of the DCI in the cell's DTX configuration can be configured only on the cell's first active downlink BWP or initial downlink BWP. By transmitting the DCI only via the first active downlink BWP or initial downlink BWP, configuring the parameters only on the first active downlink BWP or initial downlink BWP can reduce the signaling overhead of the DCI.

[0339] In the example, the wireless device is based on the configuration parameters of the PDCCH used for DCI (e.g., based on...). Figure 27(Example implementation) to determine the PDCCH monitoring timing on the active DL BWP for indicative cell DTX configuration activation / deactivation of the DCI. In the example, one or more PDCCH monitoring timings may exist within a time window for indicative cell DTX configuration activation / deactivation of the DCI.

[0340] exist Figure 35 In the example, the DCI used for cell DTX configuration activation / deactivation can be a new DCI (e.g., DCI format 2_8, DCI format 2_9, or DCI format 2_x, which is different from the existing DCI format 2_6 used for UE wake-up or the existing DCI format 2_7 used for paging early indication). The DCI can be a group common DCI addressed to all radio devices in the cell.

[0341] In the example, in response to receiving an active DCI indicating cell DTX configuration during PDCCH monitoring within the time window for DCI configuration, the radio device can, based on the above regarding... Figure 34 The described example implementation activates the cell DTX configuration. After the cell DTX configuration is activated, the base station can transmit downlink signals (MIB / SSB / SIB / CSI-RS / PDCCH / PDSCH) during the cell DTX active period and stop transmitting CSI-RS / PDCCH / PDSCH during the cell DTX inactive period, and repeat this operation for each DTX cycle of the cell DTX configuration. Transmitting downlink signals during the cell DTX active period and stopping downlink signal transmission during the cell DTX inactive period, or omitting one or more downlink signals, can be referred to as discontinuous transmission of the cell.

[0342] In the example, in response to receiving a deactivated DCI indicating the cell's DTX configuration during PDCCH monitoring within a time window configured for DCI, the radio device can, based on the above regarding... Figure 34 The described example implementation is used to deactivate the cell DTX configuration. After the cell DTX configuration is deactivated, the cell can be considered to be in a normal power state, where the base station can transmit downlink signals normally and continuously (e.g., in the case where no cell DTX configuration is configured in a legacy system).

[0343] In the example, the base station can periodically transmit one or more SSBs to one or more wireless devices. Wireless devices (in RRC_idle, RRC_inactive, or RRC_connected states) can use one or more SSBs to synchronize time and frequency with the base station's cell. SSBs containing the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Physical Broadcast Channel (PBCH), and PBCH DM-RS can be based on the above information regarding... Figure 11A The example implementation described is used for transmission. For example... Figure 11A As shown, an SSB can occupy multiple (e.g., 4) OFDM symbols. A base station can transmit one or more SSBs within an SSB burst, for example, to achieve beam scanning for the PSS / SSS and PBCH. An SSB burst comprises a set of SSBs, each potentially transmitted on a different beam. SSBs within an SSB burst can be transmitted in a time-division multiplexing manner. In the example, an SSB burst can always be limited to a 5 ms window and located in either the first or second half of a 10 ms radio frame. In this specification, an SSB burst can be equivalently referred to as the transmission window (e.g., 5 ms) in which the set of SSBs is transmitted.

[0344] In the example, the base station can communicate via RRC messages (e.g. SIB1 message ServingCellConfigCommonSIB In ssb-PeriodicityServingCell Or serving the community ServingCellConfigCommon The transmission periodicity of an SSB is indicated by a periodicity value. Candidate values ​​for transmission periodicity can be in the range of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms}. The maximum number of candidate SSBs within an SSB burst (L) is also specified. max This depends on the cell's carrier frequency / band. In the example, if f c <=3GHz, then L max =4, where f c That's the carrier frequency of the cell. If it's 3GHz... <f c <=6GHz, then L max =8. If f c >=6GHz, then L max =64 etc.

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

[0346] Figure 36 An example of determining the starting OFDM symbol index is shown.

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

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

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

[0350] In the example, the base station can transmit an RRC message (such as SIB1 and / or ServingCellConfigCommon IE) indicating the cell-specific configuration parameters of the SSB transmission of the serving cell (such as PCell or SCell). The cell-specific configuration parameters can include the value of the transmission periodicity of the SSB burst ( ssb-PeriodicityServingCellThe location of multiple SSBs (e.g., active SSBs) included in an SSB burst. Multiple candidate SSBs can be based on the above regarding... Figure 37 The example implementation described is used for implementation. Cell-specific configuration parameters may include an indication of the location of the SSB in an SSB burst (e.g., ssb-PositionsInBurst The location indication may include a first-order map indicating the location of multiple SSBs contained in an SSB burst (e.g., groupPresence ) and second bitmap (e.g., inOneGroup ).

[0351] In the example, the base station can transmit a Master Information Block (MIB) on the PBCH to indicate configuration parameters (for CORESET#0) for the radio device to monitor the PDCCH to receive SIB1 messages. The base station can transmit the MIB message at a transmission period of 80 milliseconds (ms). The same MIB message can be repeated within 80 ms (depending on the SSB periodicity). The content of the MIB message is identical within the 80 ms period. The same MIB is transmitted on all SSBs within the SS burst. In the example, the PBCH can indicate that there is no associated SIB1. In this case, the radio device can point to another frequency from which it searches for an SSB associated with SIB1, and the radio device can assume that there is no SSB associated with SIB1 within a frequency range. The indicated frequency range can be limited to continuous spectrum allocations within the same operator where the SSB was detected.

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

[0353] In the example, the base station can transmit SSBs through each of the multiple serving cells (e.g., PCell or SCell) configured for the radio device. The base station can transmit SSBs through some of the multiple serving cells and can transmit SSBs without using the others. A serving cell without an SSB can be called an SSB-free serving cell. A serving cell with an SSB that is always transmitted by the base station can be called a normally-on SSB serving cell. Besides normally-on SSBs and SSB-free, the base station can also transmit SSBs through serving cells based on indications from the radio device or another base station and / or triggered by the base station itself (e.g., by transmitting SCell activation / deactivation MAC CE). When there is no indication from the radio device or another base station, or no trigger from the base station, the base station can stop transmitting SSBs. SSBs transmitted / stopped upon request can be called on-demand SSBs.

[0354] Figure 38 Examples of various SSB transmissions are shown.

[0355] In the example, the base station can use a normally open SSB to configure the serving cell (e.g., PCell or SCell). Figure 38 In cell 1), in this case, the base station maintains a periodic (e.g.,) configuration based on the SSB. ssb- PeriodicityServingCell SSB can be transmitted (e.g., by...). ssb-PositionsInBurst Multiple SSBs (as indicated) are included in the SSB burst and are based on periodicity (e.g., according to...) Figure 37 (Example) SSBs are transmitted in a way that periodically transmits SSB bursts. In the example, normally open SSBs can be forced to be configured on the PCell, and optionally on the SCell. Radio devices can use periodically transmitted SSBs to achieve time and / or frequency synchronization (and / or beam alignment) with the serving cell. Always transmitting SSBs may increase the power consumption of the base station.

[0356] like Figure 38 As shown, the base station can configure the serving cell (e.g., SCell) without SSB transmission. Figure 38 Cell 2 in the context of the serving cell can be referenced, for example, to reduce power consumption in the serving cell. Wireless devices can refer to another serving cell (e.g., PCell, PSCell, or SCell). Figure 38 Cell 1) in the context of the serving cell obtains time and / or frequency synchronization with this serving cell. The PCell / PSCell / SCell used as the reference for the SSB of this serving cell (e.g., or the SSB reference cell) can be generated by the RRC message of the serving cell (e.g., ...). ServingCellConfigCommonThe SSB reference cell can be configured using an IE (Inter-band Interface). It can be deployed in-band (within the same frequency band) or inter-band (within a different frequency band) with the serving cell. The SSB-free configuration for the serving cell is limited to the following: when an SSB reference cell is always present in carrier aggregation (CA) or dual connectivity (DC) deployments, and / or when the time / frequency synchronization error between the SSB reference cell and the serving cell is within a threshold, and / or when the SSB reference cell and the serving cell are deployed in the same frequency range (FR). Allowing the serving cell to not perform SSB transmissions can reduce base station power consumption.

[0357] like Figure 38 As shown, a base station can utilize on-demand SSB transmission to configure a serving cell (e.g., SCell, such as cell 3), for example, to provide an SSB for time / frequency synchronization and / or, in parallel, reduce the power consumption of the serving cell, especially when there is no SSB reference cell for this serving cell (e.g., due to a single-cell deployment, or a time / frequency synchronization error between the SSB reference cell and this serving cell exceeding a threshold). There are several ways to provide on-demand SSB for this serving cell.

[0358] As a provider of on-demand SSBs for the service community (such as...) Figure 38 In the first approach shown, the base station can trigger the transmission of an on-demand SSB based on receiving an uplink wake-up signal (WUS) from the radio device. The WUS can be based on existing technologies (e.g., preambles, SRS, and / or SR) or a new signal specifically designed for on-demand SSB requests. The radio device can trigger the transmission of the WUS based on its traffic load and / or power level. In the example, the radio device can trigger the transmission of the WUS based on channel measurements of the serving cell's discovery reference signal (DRS), if configured. The DRS can be a simplified SSB with only a PSS and no SSS and PBCH, a simplified SSB with only an SSS and no PSS and PBCH, a CSI-RS, a location RS, or a newly defined RS specifically for on-demand SSB requests. Before triggering the on-demand SSB for the serving cell, the base station can (optionally) transmit the DRS to allow the radio device to perform channel measurements (which the radio device can use to determine whether to trigger the transmission of the WUS). Upon receiving (e.g., an indication of wake-up) a WUS, the base station can begin transmitting the on-demand SSB. When a WUS (Wave-Use Notification) is received (e.g., indicating sleep mode), or when no WUS indicating wake-up is received at the WUS time, the base station may stop (or skip) transmitting on-demand SSBs. Allowing radio devices to request on-demand SSB transmissions (or request to stop on-demand transmissions) when there are no active radio devices in this serving cell enables the base station to stop SSB transmissions for power / energy conservation.

[0359] As a provider of on-demand SSBs for the service community (such as...) Figure 38 In the second method (as shown), the base station can trigger the transmission of on-demand SSBs by activating the SCell. The base station can (e.g., based on...) Figure 21A and / or Figure 21B (Example) SCells for radio devices are activated by transmitting SCell activation / deactivation MAC CEs. Before a SCell is activated, the base station may skip (or not) transmitting on-demand SSBs. After a SCell is activated, the base station may begin transmitting on-demand SSBs. The base station may determine when / whether to activate a SCell (and transmit on-demand SSBs) based on the radio device's traffic load / requests and / or requests from another base station via a backhaul link. In the example, the DRS described above may optionally be transmitted by the base station. The radio device may transmit channel measurements of the serving cell based on the DRS to help the base station determine when / whether to activate the serving cell.

[0360] Figure 39 Examples of various SCell activation mechanisms are shown. In the examples, the wireless device can activate the SCell based on a normally open SSB. SCell activation with a normally open SSB can differ from fast SCell activation utilizing a tracking reference signal (TRS). The TRS can be an aperiodic CSI-RS based on an RRC configuration of the SCell.

[0361] like Figure 39 As shown, when a normally open SSB is configured, the UE should be able to activate or deactivate an inactive SCell within it. The delay (e.g., SCell activation delay) depends on the specified conditions. When in a time slot... n When the UE receives a SCell activation command (e.g., SCell activation MAC CE), it should be able to respond no later than the time slot. Transmit a valid CSI report and apply the actions associated with the activation command used to activate the SCell, where T (in milliseconds) HARQ T is the timing between DL data transmission and acknowledgment. activation_time The SCell activation delay is measured in milliseconds, and its value is based on T. FirstSSB T rs and T FirstSSB_MAX The value of T and whether the SCell is known or unknown and / or whether the SCell belongs to FR1 or FR2 (e.g., according to the SCell activation delay requirements in Section 8.3.2 of 3GPP TS 38.133 for deactivated SCells) are determined. FirstSSB It is the time when the first complete SSB burst ends, as indicated by the SMTC, or in the time slot. Within the next 5ms (if SMTC is not configured).

[0362] like Figure 39 As shown, when a TRS (e.g., A-TRS, A-CSI-RS) is configured, the UE should be able to activate or deactivate a SCell within it. The delay (e.g., SCell activation delay) depends on the specified conditions. If the UE is assigned a TRS for fast SCell activation, the UE does not need to use the SSB of the target SCell. When in a time slot... n When the UE receives a SCell activation command (e.g., SCell activation MAC CE), it should be able to respond no later than the time slot. Transmit a valid CSI report and apply the actions associated with the activation command used to activate the SCell, where T (in milliseconds) HARQ T is the timing between DL data transmission and acknowledgment. activation_time The SCell activation delay is measured in milliseconds, and its value is based on T. FirstATRS T gap and T ATRS The value of T and whether the SCell is known or unknown and / or whether the SCell belongs to FR1 or FR2 (e.g., according to the fast SCell activation delay requirements in section 8.3.16 of 3GPP TS 38.133 for deactivated SCells) are determined. FirstATRS In the time slot The time after which the first full CSI-RS burst for SCell activation ends, where a CSI-RS burst is defined as four CSI-RS resources in two consecutive time slots.

[0363] In the example, a SCell in FR1 is known if it meets the following conditions; otherwise, a SCell in FR1 is unknown: - Before receiving the SCell activation command, at a value equal to max(5*) used for FR1 measCycleSCell During the period of a 5*DRX cycle: -The UE has sent a valid measurement report for the activated SCell, and -Based on the cell identification conditions, the measured SSB remains detectable.

[0364] - equal to max(5*) measCycleSCell The SSB measured during the 5*DRX cycle period also remains detectable during the SCell activation delay, depending on the cell identification conditions. measCycleSCell It can be configured in SCell's RRC measurement configuration parameters (e.g., as will be described below). Figure 42(As shown in the diagram). The length of the DRX loop can be configured in the RRC message.

[0365] For the first SCell activation in the FR2 band, the SCell is known if it meets the following conditions; otherwise, the first SCell in the FR2 band is unknown: - Before the UE receives the last activation command for PDCCH TCI, PDSCH TCI (where applicable), and semi-persistent CSI-RS (where applicable) for CQI reporting, during a period of 4 seconds for UEs supporting power categories 1 / 5 and 3 seconds for UEs supporting power categories 2 / 3 / 4: -The UE has sent a valid L3-RSRP measurement report with an SSB index, and The SCell activation command is received after the L3-RSRP report and no later than the time the UE receives the MAC-CE command for TCI activation. - During the period from L3-RSRP report to valid CQI report, the SSB of the report with index remains detectable according to the specified cell identification conditions, and the TCI status is selected based on the latest reported SSB index in the latest reported SSB index.

[0366] exist Figure 39 In the example, the SCell activation delay for a SCell configured with a normally open SSB can be longer than the SCell activation delay for a SCell configured with a TRS.

[0367] Figure 40 An example of SSB / CSI-RS beam and cell measurements for a serving cell (e.g., PCell or SCell) is shown. In the example, the base station may transmit RRC messages (e.g., SIB1, UE-specific RRC messages, cell-specific RRC messages) to a radio device or a group of radio devices.

[0368] In the example, the base station (or network) can be based on measObject The parameters configured in the middle (e.g., the maximum number of beams to be averaged and the beam combining threshold) and reportConfig The parameters configured in the middle (to be measured) rsType The SS / PBCH block or CSI-RS transmits an RRC message to the radio device indicating that the radio device has exported the RSRP, RSRQ, and SINR measurement results associated with each cell's NR measurement object in the RRC_CONNECTED.

[0369] In the example, the base station (or network) can transmit RRC messages to wireless devices, which instruct wireless devices in RRC_IDLE or RRC_INACTIVE mode to base their settings on the specified conditions. VarMeasIdleConfig within measIdleCarrierListNR The parameters configured in the system are used to derive RSRP and RSRQ measurement results for each cell associated with the NR carrier.

[0370] In the example, the RRC message may include scheduling information related to assessing whether to allow a radio device to access the cell, as well as other system information. The RRC message may include radio resource configuration information shared by the radio device and prohibition information applied to access control. The RRC message can be based on the above information... Figure 25 and / or Figure 26 The example implementation described is used to achieve this. When the RRC message includes a SIB1 message, the SIB1 message can be transmitted in 160ms cycles. Within 160ms, the base station can transmit repetitions of the SIB1 message, each repetition having the same SIB1 content.

[0371] In the example, the base station can transmit scheduling SIB1 messages via the cell's type 0 common search space. Figure 40 (not shown) group common DCI (e.g., DCI format 1_0 with CRC scrambled by SI-RNTI). For example, based on the above regarding Figure 24A The example implementation described shows that the Type 0 public space can be indicated via MIB messages using one or more configuration parameters (control resource set indication, search space indication, etc.).

[0372] like Figure 40 As shown, the SIB1 message can indicate the value of the SSB's transmission power (DL Tx power) (e.g., based on...). Figure 25 Example, ss-PBCH-BlockPower ). ss-PBCH-BlockPower The value can indicate the average energy per resource element (EPRE), in dBm, of the resource elements (REs) carrying SSS used by the base station for SSB transmission. Resource elements can be based on the above regarding... Figure 8 The example implementation described above can be used to achieve this. SSB transport can be based on the above regarding... Figure 36 and / or Figure 37 The described example implementation scheme is used to achieve this. Based on the above references... Figure 36 and / or Figure 37 In the described example implementation, the SIB1 message can also indicate the SSB cycle in an SSB burst (e.g. Figure 25 shown ssb-PeriodicityServingCell ) and location (e.g.) Figure 25 shown ssb-PositionsInBurst The base station can transmit SSBs at a default period of 20ms.

[0373] like Figure 40 As shown, based on the SIB1 message, the base station can use the information in the SIB1 message... ss-PBCH- BlockPower The downlink transmission power (DL Tx power) determined by the indicated EPRE value is used to transmit SSBs (within SSB bursts). The base station can transmit SSBs at a period determined based on the period and location of the SSB indicated by the SIB1 message.

[0374] In the example, based on the received SIB1 message, the wireless device can measure the SSB to determine the beam / cell channel quality parameters, which include: L1-RSRP of one or more beams in the cell, L3-RSRP of the cell, channel state information (CSI), path loss, and Tx / Rx beam determination (e.g., based on the above reference). Figure 12A and / or Figure 12B Examples of implementation schemes described, etc.

[0375] In the example, the base station (or network) can configure the RRC_CONNECTED wireless device to perform measurements. The network can configure the wireless device to report these measurements based on the measurement configuration, or to perform conditional reconfiguration assessments based on conditional reconfiguration. For example, using... RRCReconfiguration or RRC Resume Measurement configuration is provided using dedicated signaling.

[0376] In the example, the network can configure wireless devices to perform various types of measurements, including NR measurements, RAT-to-RAT measurements on E-UTRA frequencies, and / or RAT-to-RAT measurements on UTRA-FDD frequencies.

[0377] In the example, the network can configure wireless devices to report measurement information based on SS / PBCH blocks, including measurement results for each SS / PBCH block, and measurement results for each cell based on SS / PBCH blocks and / or SS / PBCH block indexes.

[0378] In the example, the network can configure wireless devices to report measurement information based on CSI-RS resources, including measurement results for each CSI-RS resource, and measurement results for each cell based on CSI-RS resources and / or CSI-RS resource measurement identifiers.

[0379] In the example, the network can configure wireless devices to perform CBR measurements for both NR and V2X sidelinks. The network can configure wireless devices to report CLI (Cross-Link Interference) measurement information based on SRS resources, including the measurement results and SRS resource index for each SRS resource. The network can also configure wireless devices to report CLI measurement information based on CLI-RSSI resources, including the measurement results and CLI-RSSI resource index for each CLI-RSSI resource.

[0380] In the example, the measurement configuration (transmitted by the base station in the RRC message) includes parameters such as the measurement object, reporting configuration, measurement identifier, quantity configuration, and / or measurement gap.

[0381] In the example, the measurement object (MO) includes a list of objects on which the wireless device performs measurements.

[0382] Figure 41 An example of a measurement configuration for SCell is shown. In this example, the wireless device can perform Layer 3 cell / beam measurements against the serving cell. For example... Figure 41 As shown, in order to instruct a wireless device to perform Layer 3 cell / beam measurements for the serving cell, a base station may transmit one or more RRC messages, which include configuration parameters for the cell / beam measurements of the serving cell. The one or more RRC messages may include... Serving Cell Config IE. ServingCellConfig IE can include an indication of the measurement object ID ( Meas Object Id )of serving Cell MO IE. The servingCellMO IE indicates the cell associated with the serving cell. Meas Config In Meas Object NR of measObjectId Regarding this Meas Object NR The following relationship applies to the serving cell. Serving Cell Config Common This in Meas Object NR and frequency Info DL Between: If ssb Frequency If configured, its value is the same as absolute Frequency SSB same. Figure 41 It shows Serving Cell Config Common IE. measObjectId It can indicate the measurement object used for NR (e.g.) Meas Object NR IE).

[0383] Figure 42 An example of a measurement configuration for a serving cell is shown. Meas Object NR The IE can include multiple parameters for cell / beam measurements. In the example, these parameters may include the frequency indication of the SSB (Square Sub-Band). ssb Frequency IE), SCS instructions for SSB (ssb Subcarrier Spacing IE), SSB measurement timing configuration (e.g.) smtc1 IE), thresholds used for SSB measurement (e.g.) abs Thresh SS-Blocks Consolidation IE) and / or measuring the length of the cycle (e.g. meas Cycle SCell IE), etc. Only when SCell is configured by meas Object NR It is only used when the indicated frequency is high and the device is in a deactivated state. meas Cycle SCell IE.

[0384] In the example, the reporting configuration includes a list of reporting configurations, where each measurement object can have one or more reporting configurations. Each measurement report configuration consists of: a reporting standard that triggers the wireless device to send a measurement report, which can be periodic or a single event description; the RS type (SS / PBCH block or CSI-RS) for the wireless device to use for beam and cell measurement results; and / or a report format, where the number of each cell and each beam included by the wireless device in the measurement report (e.g., RSRP) and other associated information such as the maximum number of cells and the maximum number of beams per cell to be reported. In the case of conditional reconfiguration, each configuration consists of: the execution standard for the wireless device to perform conditional reconfiguration, and the RS type for the wireless device to obtain (SS / PBCH block-based or CSI-RS-based) beam and cell measurement results for evaluating the conditions for conditional reconfiguration execution.

[0385] In the example, for a measurement report, the measurement identifier includes a list of measurement identifiers, where each measurement identifier links a measurement object to a report configuration. By configuring multiple measurement identifiers, it is possible to link more than one measurement object to the same report configuration, or more than one report configuration to the same measurement object. Measurement identifiers are also included in the measurement report that triggers the report to serve as a reference to the network. For conditional reconfiguration triggers, one measurement identifier is linked to exactly one conditional reconfiguration trigger configuration. And up to two measurement identifiers can be linked to a single conditional reconfiguration execution condition.

[0386] In the example, the quantity configuration defines the measurement filtering configuration used for all event assessments and related reporting, as well as for periodic reporting of the measurement. For NR measurements, the network can configure up to two quantity configurations, which have references to the configuration to be used in the NR measurement object. Within each configuration, different filter coefficients can be configured for different measurement quantities, different RS types, and measurements per cell and per beam.

[0387] In the example, the measurement gap defines the period during which the wireless device can perform measurements.

[0388] In the example, the wireless device in RRC_CONNECTED state maintains a list of measurement objects, a list of report configurations, and a list of measurement identifiers according to signaling and procedures. The list of measurement objects may include NR measurement objects, CLI measurement objects, and inter-RAT objects. Similarly, the list of report configurations includes NR and inter-RAT report configurations. Any measurement object can be linked to any report configuration of the same RAT type. Some report configurations may not be linked to measurement objects. Likewise, some measurement objects may not be linked to any report configuration.

[0389] In the example, the measurement process distinguishes the following types of cells: NR serving cells – these NR serving cells are SpCells and one or more SCells; listed cells – these listed cells are cells listed within the measurement object; and detected cells – these detected cells are cells not listed within the measurement object but detected by the wireless device at the SSB frequency and subcarrier spacing indicated by the measurement object.

[0390] In the examples, for NR measurements, the wireless device measures and reports the serving cell, the listed cells, and / or the detected cells. For E-UTRA inter-RAT measurements, the wireless device measures and reports the listed cells and the detected cells, and for RSSI and channel occupancy measurements, the wireless device measures and reports the configured resources on the indicated frequency. For UTRA-FDD inter-RAT measurements, the wireless device measures and reports the listed cells. For CLI measurements, the wireless device measures and reports the configured measurement resources (e.g., SRS resources and / or CLI-RSSI resources).

[0391] In the example, the network application follows this procedure: ensuring that whenever a wireless device has a measConfig associated with a CG (cell group), that measConfig includes information for the SpCell and for each NR SCell of the CG to be measured. meas Object Use it report Type Set as report CGI The report configuration spans all CG configurations with a maximum of one measurement identifier, using a method with... ul-Delay Value Config The report configuration allows for a maximum of one measurement identifier per CG configuration; ensure that the report is associated with a CG. meas Config In China: For all SSB-based measurements, at most one measurement object has the same ssb Frequency ; and included in having the same ssb Frequency In any measurement object smtc1 Having the same value, and being included in those having the same ssb Frequency In any measurement object smtc2 Having the same value, and being included in those having the same ssb Frequency In any measurement objectsmtc3list Have the same value; ensure they are configured with the same ssb Frequency All measurement objects have the same ssb Subcarrier Spacing Ensure that if the measurement object associated with MCG has the same characteristics as the measurement object associated with SCG... ssb Frequency Then: for that ssb Frequency According to the configuration by MCG ​ The measurement window includes parameters configured by SCG. ​ The measurement window, or vice versa, where the accuracy is the maximum received timing difference; and if both measurement objects are used for RSSI measurements, then the accuracy of the two objects corresponding to the same time slot is... ​ The bits in the array are set to the same value. Furthermore, ​ They are identical in both objects; this ensures that if the measurement object has the same characteristics as the configured measurement object... ​ Then: for that ​ According to the configuration ​ The measurement window includes parameters based on the configuration. ​ The measurement window, or vice versa, where the accuracy is the maximum received timing difference, and if both measurement objects are used for RSSI measurements, then the accuracy of the two objects corresponding to the same time slot is... ​ The bits in the array are set to the same value. Furthermore, ​ It is the same in both objects; and in the example, when the wireless device is in NE-DC, NR-DC, or NR-independent mode, the network application process uses which one ​ Set as ​ The report configuration spans all CG configurations with a maximum of one measurement identifier.

[0392] In the example, for CSI-RS resources, the network applies the following procedure: ensuring that all CSI-RS resources configured in each measurement object have the same center frequency, ( ​ +floor( ​ / 2)); and ensure that the total number of CSI-RS resources configured in each measurement object does not exceed the maximum number.

[0393] In the example, the wireless device can: if it receives ​ include ​ If so, then the measurement object removal process is executed; if the received ​ include ​ Then execute the measurement object addition / modification process; if the received ​ include ​ If the received report configuration is removed, the removal process will be executed; ​ include ​ Then execute the report configuration add / modify process; if received​ include ​ If the received quantity configuration process is executed; ​ include ​ If the received measurement identifier removal process is executed; ​ include ​ Then execute the measurement identifier addition / modification process; if received ​ include ​ Then execute the measurement gap configuration process; if the received ​ include ​ Then, the measurement gap sharing configuration procedure is executed. In the example, if the received... ​ include ​ If ​ Set as ​ Then the wireless device will ​ within s-MeasureConfig parameters ssb-RSRP Set by s-MeasureConfig The received value indicates the lowest value in the RSRP range; otherwise, the wireless device will... VarMeasConfig within s-MeasureConfig parameters csi-RSRP Set by s-MeasureConfig The received value indicates the lowest value in the RSRP range.

[0394] In the example, the wireless device can... smtc1 The configuration provides (for the following conditions) Periodicity and Offset The value received periodicityAndOffset Parameters are used to set the measurement timing configuration (SMTC) for the first SS / PBCH block. The first subframe of each SMTC timing occurs at the SFN and subframe of the NR SpCell that meet the following conditions: SFN mode T =(FLOOR( Offset / 10)); if Periodicity Greater than sf5 Then subframe = Offset Modulo 10, otherwise subframe = Offset or( Offset +5), of which T =CEIL( Periodicity / 10).

[0395] In the example, if smtc2 If it exists, then for the same MeasObjectNR In smtc2 In pci-List The cell indicated in the parameters allows wireless devices to... smtc2 Received in the configuration periodicity Parameters are used to set the measurement timing configuration (SMTC) for the additional SS / PBCH block, and (from parameters) periodicityAndOffset (Exported from) Offset and from smtc1 Configuration duration Parameters. The first subframe of each SMTC timing occurs at the SFN and subframe of the NRSpCell that satisfy the above conditions.

[0396] In the example, if smtc2-LP If it exists, then for in smtc2-LP In pci-List The parameters indicate whether the cells are at the same frequency (for intra-frequency cell reselection) or different frequencies (for inter-frequency cell reselection). The wireless device can then... smtc2-LP Received in the configuration periodicity Parameters are used to set the measurement timing configuration (SMTC) for the additional SS / PBCH block, and (from parameters) periodicityAndOffset (Exported from) Offset and from the frequency used smtc Configuration duration Parameters. The first subframe of each SMTC timing occurs at the NR SpCell or the SFN and subframe of the serving cell (for cell reselection) that meets the above conditions.

[0397] In the example, if smtc3list If it exists, then for the same MeasObjectNR Each of the lists SSB- MTC3 In elements pci-List The cell indicated in the parameters, IAB-MT can be based on the received data in each SSB-MTC3 configuration. periodicityAndOffset Parameters (used with) smtc1 The same conditions are used to identify the SFN and subframe used for SMTC timing to set the additional SS block measurement timing configuration, and the duration and... are used from each SSB-MTC3 configuration. ssb- ToMeasure parameter.

[0398] In the example, in the indicated ssbFrequency For RRM measurements based on SS / PBCH blocks and RRM measurements based on CSI-RS other than SFTD measurements, the wireless device may disregard SS / PBCH block transmissions in subframes outside of the SMTC timing.

[0399] In the example, the RRC_CONNECTED wireless device can derive cell measurement results by measuring one or more beams of each associated cell as configured by the network. For all cell measurement results except RSSI and CLI measurement results in RRC_CONNECTED, the wireless device applies Layer 3 filtering before using the measurement results to evaluate reporting criteria, measurement reports, or criteria used to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP, or EcN0 as the trigger number. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as the trigger number. For cell and beam measurements, the reporting number can be any combination of numbers (e.g., RSRP only; RSRQ only; SINR only; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ, and SINR; RSCP only; EcN0 only; RSCP and EcN0), regardless of the trigger number, and for CLI measurements, the reporting number can be SRS-RSRP or CLI-RSSI. For conditional reconfiguration, the network can be configured to use up to two quantities of the same RS type. Wireless devices should not apply layer 3 filtering to derive CBR measurements.

[0400] In the example, the network can also configure the wireless device to report measurement information for each beam (which can be the measurement results for each beam with its corresponding beam identifier or just the beam identifier). If the beam measurement information is configured to be included in the measurement report, the wireless device applies Layer 3 beam filtering. On the other hand, the precise L1 filtering of the beam measurements used to derive the cell measurement results is implementation-specific.

[0401] In the example, whenever it is configured measConfig At that time, wireless devices were all configured for them. servingCellMO Perform RSRP and RSRQ measurements for each serving cell. If included in... VarMeasConfig within measIdList at least one of them measId Related reportConfig Include is set to ssb of rsType and ssb- ConfigMobility In the servingCellMO Instructions measObject If configured in [the relevant block], the wireless device can derive serving cell measurements based on the SS / PBCH block. If included in [the relevant block]... VarMeasConfig within measIdList at least one of them measId Related reportConfig Include reportQuantityRS-Indexes and maxNrofRS- IndexesToReport And includes being set to ssb of rsType Then, the wireless device can derive the layer 3 filtered RSRP and RSRQ for each beam of the serving cell based on the SS / PBCH block.

[0402] In the example, if it is included VarMeasConfig within measIdList at least one of them measId Related reportConfig Include is set to csi-rs of rsType and CSI-RS- ResourceConfigMobility In the servingCellMO Instructions measObject If configured in, then if included in VarMeasConfig within measIdList at least one of them measId Related reportConfig Include reportQuantityRS-Indexes and maxNrofRS-IndexesToReport And includes being set to csi-rs of rsType The wireless device then derives the layer 3 filtered RSRP and RSRQ for each beam used in the serving cell based on CSI-RS. If included in... VarMeasConfig within measIdList at least one of them measId Related reportConfig Include is set to csi-rs of rsType and CSI-RS-ResourceConfigMobility In the servingCellMO Instructions measObject If configured, wireless devices can export serving cell measurement results based on CSI-RS.

[0403] In the example, for its configuration servingCellMO Each serving cell, if included in VarMeasConfig within measIdList at least one of them measId Related reportConfig If SINR is included as the trigger number and / or report number, then if reportConfig Include is set to ssb of rsType and ssb- ConfigMobility exist servingCellMO It is configured in, and if reportConfig Include reportQuantityRS-Indexes and maxNrofRS-IndexesToReport The wireless device then derives the layer 3 filtered SINR for each beam used in the serving cell based on the SS / PBCH block. If included in...VarMeasConfig within measIdList at least one of them measId Related reportConfig Include SINR as the trigger number and / or report number, and if reportConfig Include is set to ssb of rsType and ssb-ConfigMobility exist servingCellMO If configured in this way, the wireless device can derive the serving cell SINR based on the SS / PBCH block. In the example, if reportConfig Include is set to csi-rs of rsType and CSI-RS-ResourceConfigMobility exist servingCellMO If configured in this way, the UE can derive the serving cell SINR based on CSI-RS, and if reportConfig Include reportQuantityRS-Indexes and maxNrofRS-IndexesToReport Then the UE can derive the SINR of the layer 3 filter for each beam of the serving cell based on CSI-RS.

[0404] In the example, for those included VarMeasConfig within measIdList Each of them measId If used for related reportConfig of reportType yes periodical , eventTriggered or condTriggerConfig ,if s-MeasureConfig Set as ssb-RSRP Furthermore, the RSRP of NRSpCell based on the SS / PBCH block is lower than that after layer 3 filtering. ssb-RSRP , or if s-MeasureConfig Set as csi-RSRP Furthermore, the NR SpCell RSRP based on CSI-RS is lower than that after layer 3 filtering. csi-RSRP If used for associated reportConfig The reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured and if measObject Associated with NR and rsType Set as csi-rs Then use the associated measObject The parameters are based on the number of triggers and in reportQuantityCellThe CSI-RS for each measurement quantity indicated in the report are used to derive cell measurement results, and if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured, the results can be derived solely based on the CSI-RS for each measurement quantity indicated in the reportConfig. reportQuantityRS-Indexes The number of CSI-RS measurements indicated in the text is used to derive the beam measurements of the layer 3 filter.

[0405] In the example, for those included VarMeasConfig within measIdList Each of them measId If used for related reportConfig of reportType yes periodical , eventTriggered or condTriggerConfig ,if s-MeasureConfig Set as ssb-RSRP Furthermore, the RSRP of NRSpCell based on the SS / PBCH block is lower than that after layer 3 filtering. ssb-RSRP , or if s-MeasureConfig Set as csi-RSRP Furthermore, the NR SpCell RSRP based on CSI-RS is lower than that after layer 3 filtering. csi-RSRP If reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured for the associated reportConfig and if measObject Associated with NR, and if measObject Associated with NR and rsType Set as ssb Then the wireless device can use data from the associated network. measObject The parameters are based on the number of triggers and in reportQuantityCell The cell measurement results are derived from the CSI-RS for each measurement quantity indicated in the data. Wireless devices can use data from the associated... measObject The parameters are based on the number of triggers and in reportQuantityCell The number of SS / PBCH blocks indicated in the report is used to derive cell measurement results, and if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured, the radio device can only derive cell measurement results based on the number of SS / PBCH blocks for each measurement specified in the reportConfig. reportQuantityRS-Indexes The number of SS / PBCH blocks indicated in the diagram is used to derive the layer 3 beam measurements.

[0406] In the example, for the number of cell measurements, the number of beam measurements, the number of sidelink measurements, and the number of CLI measurements performed by the wireless device, the wireless device can use the following formula (e.g., ...) before using the measurement results to evaluate reporting standards or for measurement reporting. Figure 40 (As shown in the figure) to filter the measurement result: F n = (1 – a )* F n-1 + a * M n in M n It is the latest measurement result received from the physical layer. F n It is a filtered measurement result used to evaluate reporting standards or to update measurement reports, and F n-1 It is the old (or previous) filtered measurement result, where the first measurement result from the physical layer is received. F 0 is set to M 1. Regarding MeasObjectNR , a =1 / 2 (ki / 4) ,in k i It is used for quantityConfigNR-List The first in iQuantityConfigNR The corresponding number of measurements filterCoefficient ,and i Depend on MeasObjectNR In quantityConfigIndex Instructions; for other measurements, a =1 / 2 (k / 4) ,in k It is used by quantityConfig The corresponding number of measurements received filterCoefficient For UTRA-FDD, a = 1 / 2 (k / 4) , where k is used by QuantityConfig In quantityConfigUTRA-FDD The received filterCoefficient corresponding to the number of measurements. QuantityConfig IE can be based on Figure 43 The example shown specifies the number of measurements and layer 3 filter coefficients used for measurements between NR and RAT.

[0407] exist Figure 43 In the example, ssb-FilterConfig The L3 filter configuration can be specified for SS-RSRP, SS-RSRQ, and SS-SINR measurements from the L1 filter.FilterCoefficient IE allows you to specify the measurement filter coefficients, where the values ​​are... fc0 Corresponding to k = 0, fc1 Corresponding to k = 1, etc.

[0408] In the example, the wireless device can adapt the filter so that its time characteristics are preserved at different input rates, thus allowing observation. filterCoefficient k A sampling rate of X ms is used; assuming non-DRX operation, the value of X is equivalent to the L1 measurement period within a frequency range and depends on the frequency range.

[0409] In the example, if k If set to 0, layer 3 filtering is not applied. In the example, filtering can be performed in the same domain as used for evaluation reporting criteria or for measurement reporting, i.e., logarithmic filtering for logarithmic measurements.

[0410] In the example, the network (or base station) can configure wireless devices in RRC_CONNECTED state to be based on... measObject (e.g., the maximum number of beams to be averaged and the beam combining threshold) and reportConfig (To be measured) rsType The parameters configured in the SS / PBCH block or CSI-RS are used to derive the RSRP, RSRQ, and SINR measurements for each cell associated with the NR measurement object. The network can configure radio devices in RRC_IDLE or RRC_INACTIVE mode to be based on... VarMeasIdleConfig within measIdleCarrierListNR The parameters configured in the system are used to derive RSRP and RSRQ measurement results for each cell associated with the NR carrier.

[0411] In the example, the wireless device can derive cell measurement results based on beam measurements of the SS / PBCH block and / or CSI-RS on the cell.

[0412] For the number of measurements per cell to be derived based on the SS / PBCH block, if nrofSS-BlocksToAverage Not associated with RRC_CONNECTED measObject China or not in VarMeasIdleConfig within measIdleCarrierListNR It is configured in the associated entity of RRC_IDLE / RRC_INACTIVE, or if absThreshSS-BlocksConsolidation Not associated with RRC_CONNECTED measObject China or not in VarMeasIdleConfig within measIdleCarrierListNRIt is configured in the associated entry of RRC_IDLE / RRC_INACTIVE, or if the highest beam measurement quantity value is less than or equal to absThreshSS- BlocksConsolidation If the maximum number of beam measurements is specified, the wireless device can derive the number of measurements per cell as the highest beam measurement value based on the SS / PBCH block (e.g., where the number of measurements per beam is described below and / or also in the specification of TS 38.215); otherwise, the wireless device can derive the number of measurements per cell as a higher value based on the SS / PBCH block. absThreshSS- BlocksConsolidation The linear power scale average of the highest beam measurement count, where the total number of average beams does not exceed [the value of the highest beam measurement count]. nrofSS-BlocksToAverage The number of measurements for each beam is described below and / or also in the specification TS38.215. After obtaining cell measurements based on the SS / PBCH block, if in RRC_CONNECTED state, the radio device can apply layer 3 cell filtering to the number of measurements.

[0413] For the number of measurements per cell to be derived based on CSI-RS, when the CSI-RS resources of interest are included, including the associated... measObject In CSI-RS-ResourceConfigMobility The community in the middle physCellId of csi-rs-CellMobility In this case, wireless devices can treat CSI-RS resources as suitable for exporting cell measurements. If associated with... measObject In nrofCSI-RS-ResourcesToAverage Not configured, or if associated measObject In absThreshCSI-RS-Consolidation Not configured, or if the highest beam measurement count is less than or equal to absThreshCSI-RS-Consolidation If the number of measurements per cell is specified, the wireless device can derive the maximum number of beam measurements based on the applicable CSI-RS resources for the cell, where the number of measurements per beam is described below and / or also in the specification of TS 38.215; otherwise, the wireless device can derive the number of measurements per cell based on CSI-RS as a higher value than the specified value. absThreshCSI-RS-Consolidation The linear power scale average of the highest beam measurement count, where the total number of average beams does not exceed [the value of the highest beam measurement count]. nrofCSI-RS-ResourcesToAverage After obtaining CSI-RS-based cell measurements, the wireless device can apply Layer 3 cell filtering to the measurement count.

[0414] In the example, the wireless device can derive the layer 3 beamfilter measurements based on the SS / PBCH block and / or CSI-RS. For the number of layer 3 beamfilter measurements to be derived based on the SS / PBCH block, the wireless device can derive the number of beam measurements for each configuration based on the SS / PBCH block as described below and / or also in the specification of TS 38.215, and apply the layer 3 beamfilter. For the number of layer 3 beamfilter measurements to be derived based on the CSI-RS, the wireless device can derive the number of beam measurements for each configuration based on the CSI-RS as described below and / or also in the specification of TS 38.215, and apply the layer 3 beamfilter.

[0415] In this specification, the RSRP / RSRQ / SINR filtered at a higher layer, compared to the RSRP / RSRQ / SINR measured at the physical layer, can be referred to as L3-RSRP / RSRQ / SINR. A higher-layer filter configured with L3 filter coefficients for L3 measurement can be referred to as an L3 filter. The RSRP / RSRQ / SINR measured at the physical layer before filtering by the L3 filter of the wireless device can be referred to as L1-RSRP / RSRQ / SINR, which is the RSRP / RSRQ / SINR measured by the physical layer of the wireless device.

[0416] In the example, the wireless device can measure the SS-RSRP (L1-RSRP) (also described in the TS 38.215 specification) based on the SS-RSRP during the SMTC timing. The SS-RSRP is defined as the linear average of the power contribution (in [W]) of the RE carrying the SSS. For PBCH-based DM-RS SS-RS determination, and if indicated by a higher layer, the wireless device can also use CSI-RS for SS-RSRP measurement in addition to the SSS. The wireless device can measure the SS-RSRP using DM-RS for either PBCH or CSI-RS by linearly averaging the power contribution of the RE carrying the corresponding RS, taking into account power scaling of the RS. Additional CSI-RS SS-RSRP determination is not applicable if the SS-RSRP is not used for L1-RSRP. The wireless device can measure the SS-RSRP only in reference signals corresponding to SS / PBCH blocks with the same SS / PBCH block index and the same physical layer cell identity. If the SS-RSRP is not used for L1-RSRP and the higher layer indicates a set of SS / PBCH blocks for performing the SS-RSRP measurement, the wireless device can measure the SS-RSRP only from the indicated set of SS / PBCH blocks. The wireless device can determine a reference point for the SS-RSRP measurement as its antenna connector for frequency range 1. For frequency range 2, the wireless device can measure the SS-RSRP based on combined signals from antenna elements corresponding to a given receiver branch. For both frequency ranges 1 and 2, if the wireless device is using receiver diversity, it can report an SS-RSRP with a value not lower than the corresponding SS-RSRP of any of the individual receiver branches.

[0417] In the example, the wireless device can measure CSI-RSRP (L1-RSRP) (also described in the TS38.215 specification) based on CSI-RSRP, which is defined as the linear average of the power contribution (in [W]) of the resource elements at an antenna port carrying a CSI reference signal configured for RSRP measurement within the considered measurement frequency bandwidth during the configured CSI-RSRP timing. For CSI-RSRP determination, the CSI reference signal transmitted on antenna port 3000 can be used. If CSI-RSRP is used for L1-RSRP, the CSI reference signals transmitted on antenna ports 3000 and 3001 can be used for CSI-RSRP determination. For in-frequency CSI-RSRP measurement, if no measurement gap is configured, the wireless device does not expect to measure CSI-RS resources outside the effective downlink bandwidth portion. For frequency range 1, the reference point for CSI-RSRP can be the UE's antenna connector. For frequency range 2, CSI-RSRP can be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For frequency ranges 1 and 2, if the UE is using receiver diversity, the reported CSI-RSRP value must not be lower than the corresponding CSI-RSRP of any of the individual receiver branches.

[0418] In the example, the wireless device can measure SS-RSRQ (L1-RSRQ) based on the ratio N × SS-RSRP / NR carrier RSSI (also described in the specification TS 38.215), where N is the number of resource blocks in the NR carrier RSSI measurement bandwidth. Measurements in the numerator and denominator can be made on the same set of resource blocks. The NR carrier received signal strength indicator (NR carrier RSSI) comprises a linear average of the total received power (in [W]) observed only in certain OFDM symbols of the measurement time resource, in the measurement bandwidth, across N number of resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. For cell selection, the measurement time resource for NR carrier RSSI is unconstrained. Otherwise, the measurement time resource for NR carrier RSSI is limited to the duration of the SMTC window. If indicated by a higher layer, and if no measurement gap is used, then the measurement time resource is determined by higher layer parameters. measurementSlots The RSSI of the NR carrier is measured in the time slots within the indicated SMTC window duration and in predefined OFDM symbols, and if measurement gaps are used, in the time slots determined by higher-level parameters. measurementSlotsThe NR carrier RSSI is measured in time slots within the indicated SMTC window duration and in predefined OFDM symbols overlapping with the measurement gap. For intra-frequency measurements, the NR carrier RSSI is measured with a timing reference corresponding to the serving cell in the frequency layer. For inter-frequency measurements, the NR carrier RSSI is measured with a timing reference corresponding to any cell in the target frequency layer. Otherwise, if not indicated by a higher layer, the NR carrier RSSI is measured from OFDM symbols within the SMTC window duration if no measurement gap is used, and if a measurement gap is used, the NR carrier RSSI is measured from OFDM symbols corresponding to the overlapping time span between the SMTC window duration and the measurement gap. If a higher layer indicates certain SS / PBCH blocks for performing SS-RSRQ measurements, SS-RSRP is measured only from the indicated set of SS / PBCH blocks. For frequency range 1, the reference point for SS-RSRQ can be the UE's antenna connector. For frequency range 2, the NR carrier RSSI can be measured based on a combination of signals from antenna elements corresponding to a given receiver branch, where the combination used for the NR carrier RSSI can be the same as the combination used for SS-RSRP measurements. For frequency ranges 1 and 2, if the UE is using receiver diversity, the reported SS-RSRQ value must not be lower than the corresponding SS-RSRQ of any of the individual receiver branches.

[0419] In the example, the wireless device can measure CSI-RSRQ (L1-RSRQ) based on the CSI-RSRQ being defined as the ratio of N × CSI-RSRP to CSI-RSSI (also described in the specification TS 38.215), where N is the number of resource blocks in the CSI-RSSI measurement bandwidth. Measurements in both the numerator and denominator can be made on the same set of resource blocks. The CSI Received Signal Strength Indicator (CSI-RSSI) comprises the linear average of the total received power (in [W]) observed only in the OFDM symbols of the measurement time resource, across the measurement bandwidth, from N resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. The measurement time resource for CSI-RSSI corresponds to an OFDM symbol containing the configured CSI-RS timing. For CSI-RSRQ determination, the CSI reference signal transmitted on antenna port 3000 can be used. For in-frequency CSI-RSRQ measurements, if no measurement gap is configured, the radio device does not expect to measure CSI-RS resources outside the effective downlink bandwidth portion. For frequency range 1, the reference point for CSI-RSRQ can be the UE's antenna connector. For frequency range 2, CSI-RSSI can be measured based on a combination of signals from antenna elements corresponding to a given receiver branch, where the combination used for CSI-RSSI can be the same as the combination used for CSI-RSRP measurements. For frequency ranges 1 and 2, if the UE is using receiver diversity, the reported CSI-RSRQ value must not be lower than the corresponding CSI-RSRQ of any of the individual receiver branches.

[0420] In the example, the wireless device can measure SS-SINR (L1-SINR) based on the linear average of the power contribution (in [W]) of the resource element carrying the SS signal, divided by the linear average of the power contribution (in [W]) of the noise and interference (also described in the specification TS 38.215). If SS-SINR is used for L1-SINR reporting with dedicated interference measurement resources, interference and noise are measured on the resources indicated by the higher layer. Otherwise, interference and noise are measured on resource elements carrying the SS signal within the same frequency bandwidth. The measurement time resources used for SS-SINR are limited to the duration of the SMTC window. If SS-SINR is configured for L1-SINR as in the reporting configuration, the measurement time resource limitation of the SMTC window duration does not apply. For SS-SINR determination, in addition to the secondary synchronization signal, the demodulation reference signal for the Physical Broadcast Channel (PBCH) can also be used. If SS-SINR is not used for L1-SINR and a higher layer indicates certain SS / PBCH blocks for performing SS-SINR measurements, then SS-SINR is measured only from the indicated set of SS / PBCH blocks. For frequency range 1, the reference point for SS-SINR can be the UE's antenna connector. For frequency range 2, SS-SINR can be measured based on combined signals from antenna elements corresponding to a given receiver branch. For both frequency ranges 1 and 2, if the UE is using receiver diversity, the reported SS-SINR value cannot be lower than the corresponding SS-SINR of any of the individual receiver branches.

[0421] In the example, the wireless device can measure CSI-SINR (L1-SINR) based on the linear average of the power contribution (in [W]) of the resource element carrying the CSI reference signal, divided by the linear average of the power contribution (in [W]) of the noise and interference (also described in the specification TS 38.215). If CSI-SINR is used for L1-SINR reporting with dedicated interference measurement resources, interference and noise are measured on the resources indicated by the higher layer. Otherwise, interference and noise are measured on resource elements carrying the CSI reference signal within the same frequency bandwidth. For CSI-SINR determination, the CSI reference signal transmitted on antenna port 3000 can be used. If CSI-SINR is used for L1-SINR, the CSI reference signals transmitted on antenna ports 3000 and 3001 can be used for CSI-SINR determination. For CSI-SINR measurements within frequencies not used for L1-SINR reporting, if no measurement gap is configured, the radio device does not expect to measure CSI-RS resources outside the effective downlink ...

Claims

1. A method comprising: A wireless device receives one or more Radio Resource Control (RRC) messages for configuring a secondary cell (SCell), wherein the one or more RRC messages include at least one of the following: SCell status indicator, which indicates whether the SCell is active in the configuration of the SCell; The OD-SSB configuration of one or more on-demand synchronization signal blocks (OD-SSBs) of the SCell; as well as The initial state of the OD-SSB configuration, which indicates whether the OD-SSB configuration of the SCell is enabled or disabled when the OD-SSB configuration is performed; The SCell is activated based on the SCell status indicator indicating that the SCell is in an active state when the SCell is configured. as well as Based on the initial state, the OD-SSB configuration is enabled for the SCell to transmit cell measurement reports of the SCell measured by the one or more OD-SSBs of the SCell.

2. A method comprising: A wireless device receives one or more Radio Resource Control (RRC) messages from a base station for configuring a secondary cell (SCell), wherein the one or more RRC messages include at least one of the following: SCell status indicator, which indicates whether the SCell is active in the configuration of the SCell; The OD-SSB configuration of one or more on-demand synchronization signal blocks (OD-SSBs) of the SCell; as well as Initial state, the initial state indicating whether the one or more OD-SSBs are transmitted by the base station when the OD-SSB is configured; The SCell is activated based on the SCell status indicator indicating that the SCell is in an active state when the SCell is configured. as well as Based on the initial state, one or more OD-SSBs are transmitted to transmit cell measurement reports of the SCell measured by the one or more OD-SSBs of the SCell.

3. A method comprising: A wireless device receives one or more Radio Resource Control (RRC) messages for configuring a secondary cell (SCell), wherein the one or more RRC messages include at least one of the following: SCell status indicator, which indicates whether the SCell is active in the configuration of the SCell; The OD-SSB configuration of one or more on-demand synchronization signal blocks (OD-SSBs) of the SCell; as well as The initial state of the OD-SSB configuration of the SCell; The SCell is activated based on the SCell status indicator indicating that the SCell is in an active state when the SCell is configured. as well as Based on the value of the initial state, the cell measurement report of the SCell, measured by the one or more OD-SSBs of the SCell, is transmitted.

4. A method comprising: A wireless device receives one or more Radio Resource Control (RRC) messages from a base station for configuring a secondary cell (SCell), wherein the one or more RRC messages include at least one of the following: SCell status indicator, which indicates whether the SCell is active in the configuration of the SCell; The OD-SSB configuration of one or more on-demand synchronization signal blocks (OD-SSBs) of the SCell; as well as The initial state of the OD-SSB configuration, which indicates whether the one or more OD-SSBs are transmitted by the base station when the SCell is activated.

5. A method comprising: A wireless device receives one or more Radio Resource Control (RRC) messages configured for a secondary cell (SCell) from a base station, wherein the one or more RRC messages include at least one of the following: The OD-SSB configuration of one or more on-demand synchronization signal blocks (OD-SSBs) of the SCell; and The initial state of the OD-SSB configuration, which indicates whether the one or more OD-SSBs are transmitted by the base station when the SCell is configured.

6. The method of any one of claims 1 to 5, wherein the OD-SSB configuration is associated with one or more parameters included in the one or more RRC messages, the one or more parameters indicating that the OD-SSB is triggered by the base station based on at least one of the following: The initial state included in the one or more RRC messages, the initial state indicating that the OD-SSB configuration is enabled / activated; and A Media Access Control (MAC) CE indicates the activation of the OD-SSB configuration.

7. The method of any one of claims 1 to 6, wherein one or more parameters included in one or more RRC messages comprise at least one of the following: One or more SSB periodic values ​​for the one or more OD-SSBs; The subcarrier spacing of the one or more OD-SSBs; The transmission power of the one or more OD-SSBs; and Frequency location indication of the one or more OD-SSBs.

8. The method of claim 7, wherein the one or more SSB periodic values ​​associated with the OD-SSB configuration are different from the SSB periodic values ​​associated with the normally open SSB of the SCell.

9. The method of any one of claims 7 to 8, wherein the one or more SSB periodicity values ​​associated with the OD-SSB configuration are less than the SSB periodicity value associated with the normally open SSB of the SCell.

10. The method of any one of claims 1 to 9, wherein the normally open SSB is transmitted by the base station via the SCell during the configuration of the SCell, and until the SCell is released or the configuration of the normally open SSB is released by a second RRC message.

11. The method of any one of claims 7 to 10, wherein the one or more SSB periodic values ​​present in the OD-SSB configuration indicate that the OD-SSB is triggered by the base station.

12. The method of any one of claims 1 to 11, wherein the frequency position indication is different from the second frequency position indication for the normally open SSB of the SCell, wherein the normally open SSB is transmitted via the SCell and in the frequency resource indicated by the second frequency position indication when the SCell is configured.

13. The method of any one of claims 1 to 12, wherein a frequency location indicator present in the OD-SSB configuration indicates that the OD-SSB is triggered by the base station.

14. The method of any one of claims 1 to 13, wherein the one or more RRC messages include a configuration of the normally open SSB of the SCell, wherein the one or more RRC messages include a frequency location indication for the normally open SSB, wherein the normally open SSB is transmitted by the base station after the configuration of the SCell until at least one of the following: The SCell is released by the second RRC message; and The configuration of the normally open SSB is released by the third RRC message.

15. The method of any one of claims 1 to 14, wherein the one or more RRC messages include the configuration of the normally open SSB of the SCell, wherein the one or more RRC messages include at least one of the following: Subcarrier spacing indication for the normally open SSB; The transmission power of the normally open SSB; and The transmission periodicity of the normally open SSB.

16. The method of any one of claims 1 to 15, wherein the absence of a frequency position indication of the normally open SSB in the one or more RRC messages indicates that the normally open SSB is not configured and is not transmitted on the SCell.

17. The method of any one of claims 1 to 16, wherein the initial state is applied during / after the configuration of the SCell and before the SCell is activated, and / or before receiving a command indicating a change in the state of the OD-SSB configuration, wherein the SCell state indication is absent in the one or more RRC messages indicating that the SCell was in a deactivated state during the configuration of the SCell.

18. The method of any one of claims 1 to 17, wherein the initial state is applied when / after the SCell is configured and activated and / or before receiving a command indicating a change in the state of the OD-SSB configuration, wherein the SCell state indication present in one or more RRC messages indicates that the SCell was in an active state when the SCell was configured.

19. The method of any one of claims 1 to 18, wherein the command instructing the state change of the OD-SSB configuration instructs at least one of the following: Activate the OD-SSB configuration that was in a deactivated / disabled state before receiving the command; and Deactivate the OD-SSB configuration that was in an activated / enabled state before receiving the command.

20. The method of any one of claims 1 to 19, further comprising at least one of the following operations: In response to the initial state indicating that the one or more OD-SSBs are transmitted upon activation of the SCell, in the activation state, cell measurement reports of the SCell measured by the one or more OD-SSBs of the SCell are transmitted based on one or more parameters configured by the OD-SSBs; and In response to the initial state indicating that one or more OD-SSBs were not transmitted when the SCell was activated, the transmission of the cell measurement report was skipped.

21. The method of any one of claims 1 to 20, further comprising at least one of the following operations: In response to the initial state indicating that the one or more OD-SSBs are transmitted during the configuration of the SCell, a cell measurement report of the SCell measured by the one or more OD-SSBs of the SCell is transmitted based on one or more parameters of the OD-SSB configuration; and In response to the initial state indicating that one or more OD-SSBs were not transmitted during the configuration of the SCell, the transmission of the cell measurement report is skipped.

22. The method of any one of claims 1 to 21, wherein the initial state indicating that the OD-SSB configuration of the SCell is enabled includes at least one of the following: The OD-SSB configuration is activated upon receiving one or more RRC messages that include the OD-SSB configuration; as well as The one or more OD-SSBs are transmitted upon receiving the one or more RRC messages including the configuration of the OD-SSBs; as well as The OD-SSB configuration is activated upon receiving one or more RRC messages that include the OD-SSB configuration; The one or more OD-SSBs are transmitted after receiving the one or more RRC messages including the configuration of the OD-SSB.

23. The method of any one of claims 1 to 22, wherein the initial state indicating that the OD-SSB configuration of the SCell is disabled includes at least one of the following: The OD-SSB configuration is deactivated upon receiving one or more RRC messages that include the OD-SSB configuration; as well as The one or more OD-SSBs are not transmitted by the base station when they receive the one or more RRC messages including the configuration of the OD-SSB; as well as The OD-SSB configuration is deactivated after receiving one or more RRC messages including the OD-SSB configuration; The one or more OD-SSBs are not transmitted by the base station after receiving the one or more RRC messages including the configuration of the OD-SSB.

24. The method of any one of claims 1 to 23, wherein the initial state comprises a value, wherein: The value set to the first value indicates that the OD-SSB configuration is enabled; and The value set to the second value indicates that the OD-SSB configuration is disabled.

25. The method of any one of claims 1 to 24, wherein, during the OD-SSB configuration, the wireless device does not perform cell measurements via the one or more OD-SSBs for the SCell based on at least one of the following: The initial state indicates that the OD-SSB configuration is disabled for the SCell; The initial state indication is for deactivating the OD-SSB configuration for the SCell; and The initial state indicates that one or more OD-SSBs are not transmitted by the base station on the SCell.

26. The method of any one of claims 1 to 25, further comprising at least one of the following operations: Receive from the base station a first command instructing the SCell to deactivate the OD-SSB configuration; and Based on the first command, stop transmitting the cell measurement report of the SCell through the one or more OD-SSB measurements for the SCell.

27. The method of any one of claims 1 to 26, wherein the wireless device determines that the one or more OD-SSBs are stopped / unavailable on the SCell based on receiving a first command indicating the deactivation of the OD-SSB configuration of the SCell.

28. The method of any one of claims 26 to 27, wherein the first command does not change the activation / deactivation state of the SCell, wherein the wireless device maintains the activation / deactivation state of the SCell unchanged when it receives the first command.

29. The method of any one of claims 26 to 28, wherein the first command comprises at least one of the following: Second RRC message; MAC CE; and Downlink Control Information (DCI).

30. The method of any one of claims 26 to 29, further comprising performing at least one of the following operations based on receiving the first command indicating the deactivation of the OD-SSB configuration of the SCell: Stop downlink positioning measurements via the downlink positioning reference signal PRS of the SCell; Stop the CSI measurement and / or reporting process used for the SCell; and Stop / disable / do not start the beam fault recovery (BFR) process for the SCell.

31. The method of any one of claims 1 to 30, further comprising at least one of the following operations: Receive from the base station a second command indicating the activation of the OD-SSB configuration of the SCell; and The second command is used to transmit the cell measurement report of the SCell through the one or more OD-SSBs used for the SCell, wherein the one or more OD-SSBs are measured based on one or more parameters configured in the OD-SSB configuration.

32. The method of claim 31, wherein the second command comprises at least one of the following: Second RRC message; and MAC CE.

33. The method of any one of claims 1 to 32, further comprising, in response to receiving a MAC CE indicating the activation of the OD-SSB configuration, notifying the physical layer of the wireless device of the activation of the OD-SSB configuration from the MAC entity of the wireless device.

34. The method of any one of claims 1 to 33, further comprising, upon / after the activation of the OD-SSB configuration being notified from the MAC entity of the wireless device to the physical layer of the wireless device, the physical layer of the wireless device performing downlink synchronization and / or cell measurement for the SCell based on the one or more OD-SSBs of the SCell.

35. The method of any one of claims 31 to 34, wherein the second command includes an activated MAC CE indicating the OD-SSB configuration.

36. The method of any one of claims 31 to 35, wherein the second command is the same as the SCell activation / deactivation MAC CE that indicates the activation of the SCell.

37. The method of any one of claims 31 to 35, wherein the second command is different from the SCell activation / deactivation MAC CE that indicates the activation of the SCell.

38. The method of any one of claims 1 to 37, wherein the wireless device is in an RRC connection state.

39. The method of any one of claims 1 to 38, wherein when the wireless device is in the RRC connection state, the wireless device performs the cell measurement and / or the downlink synchronization for the SCell.

40. The method of any one of claims 1 to 39, further comprising transmitting a cell measurement report of the SCell to the base station based on the cell measurement of the SCell.

41. The method of any one of claims 1 to 40, further comprising at least one of the following operations: Receive the SCell activation / deactivation MAC CE indicating the activation of the SCell; and The SCell is activated based on the received SCell activation / deactivation MAC CE.

42. The method of claim 41, wherein after the wireless device transmits the cell measurement report of the SCell to the base station, the wireless device receives the SCell activation / deactivation MAC CE.

43. The method of any one of claims 1 to 42, wherein the one or more RRC messages include parameters for configuring the cell measurement of the SCell, wherein the parameters include at least one of the following: The SSB measurement timing configuration SMTC for the one or more OD-SSBs; Measurement thresholds for the one or more OD-SSBs; and One or more reference signals RS type indicators set to the first value indicate that the one or more OD-SSBs are used for the cell measurement.

44. The method of any one of claims 1 to 43, wherein the parameters of the cell measurement configuration indicate whether the cell measurement of the SCell is enabled or disabled on the SCell configured with the OD-SSB configuration.

45. The method of any one of claims 1 to 44, wherein when the OD-SSB configuration is activated, the wireless device performs the cell measurement via the one or more OD-SSBs for the SCell based on parameters indicating that cell measurement of the SCell is enabled on the SCell configured with the OD-SSB configuration.

46. ​​The method of any one of claims 1 to 45, wherein the wireless device skips the cell measurement for the SCell based on a parameter indicating that the cell measurement of the SCell is disabled on the SCell configured with the OD-SSB configuration.

47. The method of any one of claims 1 to 46, wherein the wireless device performs the cell measurement via the one or more OD-SSBs of the SCell based on one or more RS type indications of the configuration of the cell measurement, the one or more RS type indications indicating that the one or more OD-SSBs are used for the cell measurement.

48. The method of any one of claims 1 to 47, wherein the cell measurement is a layer 3 cell measurement.

49. The method according to any one of claims 1 to 48, wherein: In response to the presence of a SCell status indication in one or more RRC messages, the SCell is in an active state during the configuration of the SCell; and In response to the absence of a SCell status indication in one or more RRC messages, the SCell is in an inactive state during the configuration of the SCell.

50. The method of any one of claims 1 to 49, wherein, for the purpose of the cell measurement, the wireless device measures the normally open SSB of the SCell when: The SCell is in a deactivated state; and The normally open SSB is configured on the SCell.

51. The method of any one of claims 1 to 50, wherein the wireless device receives the one or more RRC messages via a second cell, wherein the second cell comprises at least one of the following: The main cell PCell; and A second SCell that is different from the SCell described above.

52. The method of any one of claims 1 to 51, wherein the primary cell PCell associated with the wireless device: OD-SSB configuration is not configured; and It is configured with a normally open SSB.

53. The method according to any one of claims 1 to 52, further comprising: The initial state based on the OD-SSB configuration indicates that the OD-SSB configuration is disabled / deactivated to skip cell measurements and / or downlink synchronization on the SCell; Receive an enabled / activated MAC CE indicating the OD-SSB configuration; Upon receiving the MAC CE from the base station, it is determined that the OD-SSB was transmitted by the base station; as well as Based on the determination, the cell measurement and / or downlink synchronization on the SCell shall be initiated.

54. An apparatus comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the apparatus to perform at least the method as claimed in any one of claims 1 to 53.

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

Images