Multiple physical downlink shared channel transmission

Abstract

A wireless device receives a configuration parameter indicating a first downlink control information (DCI) format associated with scheduling a physical downlink shared channel (PDSCH) in a time slot and a second DCI format associated with scheduling multiple PDSCHs in multiple time slots. Based on monitoring a first physical downlink control channel (PDCCH) monitoring opportunity for the first DCI format, a first DCI scheduling a first transport block (TB) is received via a first PDSCH resource in a first time slot. Based on monitoring a second PDCCH monitoring opportunity for the second DCI format, a second DCI scheduling a second TB is received via a second PDSCH resource in a second time slot.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 137,648, filed January 14, 2021, which is hereby incorporated by reference in its entirety. Technical Field

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

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

[0005] Figure 2A and Figure 2B The New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0006] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Shows the flow Figure 2A Example downlink data flow of the NR user plane protocol stack.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0024] Figure 17A 、 Figure 17B and Figure 17C An example of a MAC subheader is shown according to some embodiments.

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

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

[0027] Figure 19 Examples of multiple LCIDs for a downlink are shown according to some embodiments.

[0028] Figure 20Examples of multiple LCIDs for an uplink are shown according to some embodiments.

[0029] Figure 21A and Figure 21B An example of a SCell activation / deactivation MAC CE format according to some embodiments is shown.

[0030] Figure 22 An example of BWP activation / deactivation on a SCell according to some embodiments is shown.

[0031] Figure 23A 、 Figure 23B and Figure 23C An example of an RRC message for configuration parameters of a cell according to some embodiments is shown.

[0032] Figure 24 An example of an RRC message illustrating configuration parameters for a search space according to some embodiments is shown.

[0033] Figure 25 An example of an RRC message controlling configuration parameters of a resource set (CORESET) is shown according to some embodiments.

[0034] Figure 26 Examples of search space configurations according to some embodiments are shown.

[0035] Figure 27 Examples of search space configurations according to some embodiments are shown.

[0036] Figure 28 An example of PDCCH monitoring based on the period and duration of the SS is shown according to some embodiments.

[0037] Figure 29 Examples of DCI formats according to some embodiments are shown.

[0038] Figure 30A and Figure 30B Examples of single PDSCH scheduling and multiple PDSCH scheduling according to some embodiments are shown.

[0039] Figure 31 An example of PDCCH monitoring for different DCI formats on the SS of a BWP is shown according to some embodiments.

[0040] Figure 32 An example of PDCCH monitoring for different DCI formats on the SS of a BWP is shown according to some embodiments.

[0041] Figure 33An example of PDCCH monitoring adaptation for multiple PDSCH scheduling according to some embodiments is shown.

[0042] Figure 34 An example of single PDSCH scheduling according to some embodiments is shown.

[0043] Figure 35 An example of multiple PDSCH scheduling according to some embodiments is shown.

[0044] Figure 36 An example of PDCCH monitoring skipping for multiple PDSCH scheduling according to some embodiments is shown. DETAILED DESCRIPTION

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

[0046] Implementations can be configured to operate as desired. For example, the disclosed mechanisms can be implemented when certain criteria are met in a wireless device, base station, radio environment, network, or combinations thereof. Exemplary criteria can be based, at least in part, on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, or combinations thereof. When one or more criteria are met, various exemplary implementations can be applied. Thus, exemplary implementations that selectively implement the disclosed protocol can be implemented.

[0047] A base station may communicate with a mixture of wireless devices. A wireless device and / or base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device class and / or capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with given capabilities and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed methods, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0048] In this disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In this disclosure, the term "may" is to be interpreted as "may, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of one suitable possibility among multiple suitable possibilities that may or may not be used for one or more embodiments in various embodiments. As used herein, the terms "comprising" and "consisting of" list one or more components of the element being described. The terms "comprising" and "including" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of" provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed 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.

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

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

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

[0052] Many of the features presented are described as optional, either by using the word "may" or by using parentheses. For the sake of brevity and readability, this disclosure does not explicitly recite every permutation that can be obtained by selecting from the set 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, namely, having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0053] Many elements described in the disclosed embodiments can be implemented as modules. Modules are defined here as elements that perform defined functions and have defined interfaces to other elements. The modules described in this disclosure can be implemented with hardware, software, firmware, wetware (e.g., hardware with biological elements) or a combination thereof in conjunction with hardware, all of which can be equivalent in behavior. For example, a module can be implemented as a software routine written in a computer language that is configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement a module using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between the smaller internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

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

[0055] The CN 102 may provide an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-carrier DNs, for the wireless device 106. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

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

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

[0058] The 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: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a forwarder node or relay node used to extend the coverage area of ​​a donor node; a next-generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an 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).

[0059] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the wireless devices 106 over the 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 a cell may be determined by the range at which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

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

[0061] The RAN 104 can be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high-level transmit power. The 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 that overlap with the relatively larger coverage area provided by macrocell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hotspots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

[0063] Figure 1B Another exemplary mobile communication network 150 is shown in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG, a 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). Figure 1A The corresponding components described herein are implemented and operate in the same or similar manner.

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

[0065] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. Figure 1BIn the figure, they are shown as one component AMF / UPF 158. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification to support 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 verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs and / or a fulcrum to support multi-homed PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

[0066] The AMF 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policy), network slicing support and / or session management function (SMF) selection. NAS may refer to a function operating between the CN and the UE, and AS may refer to a function operating between the UE and the RAN.

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

[0068] The NG-RAN 154 can connect the 5G-CN 152 to the UE 156 via radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, shown as gNB 160A and gNB 160B (collectively, gNB 160), and / or one or more ng-eNBs, shown as ng-eNB 162A and ng-eNB 162B (collectively, ng-eNB 162). The gNBs 160 and ng-eNB 162 may be more generally referred to as base stations. The gNBs 160 and ng-eNB 162 may include one or more antennas for communicating with the 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 antennas to control three cells (or sectors), respectively. The cells of gNB 160 and ng-eNB 162 may together provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

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

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

[0071] The gNB 160 can provide NR user plane and control plane protocol termination to the UE 156 via a Uu interface. For example, the gNB 160A can provide NR user plane and control plane protocol termination to the UE 156A via a 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 the UE 156 via a Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B can provide E-UTRA user plane and control plane protocol termination to the UE 156B via a Uu interface associated with the second protocol stack.

[0072] The 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 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 Only one AMF / UPF 158 is shown in the figure, but one gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0073] As discussed, Figure 1B The interfaces between network elements in a network (e.g., Uu, Xn, and NG interfaces) can be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack can include two planes: the user plane and the control plane. The user plane can handle data of interest to users, while the control plane can handle signaling messages of interest to network elements.

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

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

[0076] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3 Starting from the top, SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services via a PDU session, which can be a logical connection between UE 210 and a DN. A PDU session can have one or more QoS flows. The UPF of the CN (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of latency, data rate, and / or error rate). 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 reflective mapping or control signaling received from gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between QoS flows and data radio bearers.

[0077] PDCPs 214 and 224 can perform header compression / decompression to reduce the amount of data transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection to ensure that control messages originate from the intended source. PDCPs 214 and 224 can also perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate packets received due to, for example, intra-gNB handovers. PDCPs 214 and 224 can also 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.

[0078] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in dual connectivity scenarios. Dual connectivity is a technology 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 split bearers 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 / demapped split radio bearers between RLC channels belonging to a cell group.

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

[0080] MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from PHYs 211 and 221. MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs using dynamic scheduling. Scheduling may be performed in gNB 220 (at MAC 222) for both downlink and uplink. MACs 212 and 222 may be configured to perform error correction using hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of UE 210 using logical channel prioritization, and / or padding. MACs 212 and 222 may support one or more parameter sets and / or transmission timing. In an example, mapping restrictions in logical channel prioritization can control which parameter sets and / or transmission timings a logical channel can use. Figure 3 As shown, MAC 212 and 222 may provide logical channels as a service to RLC 213 and 223 .

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

[0082] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A The figure shows the downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two TBs at the gNB 220. The uplink data flow flowing through the NR user plane protocol stack can be the same as Figure 4A The downlink data flow is similar to that depicted in .

[0083] Figure 4A The downlink data flow of starts when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. Figure 4A In the SDAP header (in Figure 4AThe data unit from / to the higher protocol layer is called the service data unit (SDU) of the lower protocol layer, and the data unit to / from the lower protocol layer is called the protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data units from SDAP 225 are SDUs of the lower protocol layer PDCP 224 and are PDUs of SDAP 225 .

[0084] Figure 4A The remaining protocol layers in the Figure 3 ), add the corresponding headers and forward their corresponding output to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 2) and forwards its output to the MAC 222. The MAC 222 may multiplex many RLC PDUs and may append MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDUs, as shown in FIG. Figure 4A In LTE, the MAC subheader 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 subheader can be calculated before assembling the complete MAC PDU.

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

[0086] Figure 4B Further shown is a MAC Control Element (CE) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, Figure 4B Two MAC CEs are shown inserted into the MAC PDU. Figure 4B) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE may be used for in-band control signaling. Exemplary MAC CEs include: scheduling-related MAC CEs, such as buffer status report and power headroom report; activation / deactivation MAC CEs, such as those used for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader having a format similar to that described with respect to a MAC SDU may precede the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0087] Before describing the NR control plane protocol stack, we 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 described later below.

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

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

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

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

[0092] - a dedicated control channel (DCCH), which is used to carry control messages to / from a specific UE to configure that UE; and

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

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

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

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

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

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

[0099] - Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

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

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

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

[0103] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

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

[0105] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and scheduling request (SR); and

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

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

[0108] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2B As shown in FIG, the NR control plane protocol stack may use the same / similar first four protocol layers as the exemplary NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0109] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., AMF 158A), or more generally between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages known as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which NAS messages may be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

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

[0111] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG or any other wireless device described in this disclosure is the same or similar. Figure 6 As shown in FIG, a UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, RRC_INACTIVE).

[0112] 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 the RAN 104 depicted in FIG; Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG; Figure 2A and Figure 2Bor any other base station described in the present disclosure. 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 include parameters used 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. While 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 a 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 handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

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

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

[0115] The RRC state 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 communications network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 can allow the network to track the UE at a cell group level, so that paging messages can be broadcast to cells in the cell group in which the UE is currently residing, rather than across the entire mobile communications network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 track the UE at a cell group level. These mobility management mechanisms can do so using groupings of different granularities. For example, there can be three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas, known as tracking areas and identified by a Tracking Area Identifier (TAI).

[0116] Tracking areas can be used to track UEs 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 that is not included in the list of TAIs associated with the UE's registration area through cell reselection, the UE can perform a registration update on the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

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

[0118] The base station that stores the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least for the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or for the period of time that the UE remains in RRC inactivity 606.

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

[0120] In NR, physical signals and physical channels (about Figure 5A and Figure 5B Discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be treated as if they were in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams) and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. This operation produces discrete Fourier transform (DFT) precoded OFDM symbols and can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbols at the receiver to restore the data mapped to the source symbols.

[0121] Figure 7 An exemplary configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As shown, an NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of 1 ms duration. A subframe may be divided into time slots, which may include, for example, 14 OFDM symbols per time slot.

[0122] The duration of a timeslot may depend on the parameter set used for the OFDM symbol for that timeslot. 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). Parameter sets may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

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

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

[0125] Figure 8A single parameter set is shown used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

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

[0127] NR defines bandwidth parts (BWPs) 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 contiguous RBs on a carrier. The UE can be configured (e.g., via the RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell can be active. The one or more BWPs can be referred to as the active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

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

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

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

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

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

[0133] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in 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 indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., incrementing the BWP inactivity timer value from zero to, or decrementing the BWP inactivity timer value from zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0134] In an example, the base station may semi-statically configure the UE with one or more BWPs. The UE may 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 expiration of a BWP inactivity timer (e.g., when the second BWP is the default BWP).

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

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

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

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

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

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

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

[0142] The configured SCell for a 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 transmission on the SCell. Figure 4B The configured SCells may be activated and deactivated using a MAC CE. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

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

[0144] Figure 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 may each include one or more downlink CCs. Figure 10BIn the example of FIG, 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 may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) may be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted in the uplink of PSCell 1061. In this example, if Figure 10B If the aggregated cell depicted in FIG is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell transmits UCI associated with the downlink CC, and the PCell may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

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

[0146] In carrier aggregation, the multi-carrier nature of the PHY can be exposed to the MAC. In this example, the HARQ entity can operate on the serving cell. A transport block can be generated based on the assignment / grant of each serving cell. A transport block and potential HARQ retransmissions of that transport block can be mapped to the serving cell.

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

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

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

[0150] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). In order to find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If no PSS is found after a certain duration (for example, 20ms), the UE may search for the PSS at different frequency positions within the carrier, as indicated by the synchronization raster. If the PSS is found at a certain position in the time and frequency domains, the UE may determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In an example, the primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

[0151] 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 pattern in which the SS / PBCH block is a known distance from the frame boundary.

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

[0153] The UE may assume that one or more SS / PBCH blocks transmitted with 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.

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

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

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

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

[0158] The base station can configure the UE to report CSI measurement values. 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 the timing and / or period of multiple CSI reports. For aperiodic CSI reporting, the base station can request a CSI report. For example, the base station can command the UE to measure the configured CSI-RS resources and provide a CSI report related to the measurement value. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station can configure the UE with a CSI-RS resource set and CSI reporting using RRC signaling.

[0159] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and 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 blocks (PRBs) configured for the CORESET. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and SS / PBCH blocks 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 PRBs configured for the SS / PBCH blocks.

[0160] Downlink DMRS can be transmitted by the base station and used by the UE for channel estimation. For example, the downlink DMRS can be used for 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 patterns for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS pattern. The frontload DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PDSCH. The DMRS configuration can support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration can support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration can support up to 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 the DMRS position, DMRS pattern and / or scrambling sequence can be the same or different. The base station may use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE may use the one or more downlink DMRSs to perform consistent demodulation / channel estimation on the PDSCH.

[0161] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0162] The PDSCH may include one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. Higher layers may configure up to three DMRS for the PDSCH.

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

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

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

[0166] Depending on the RRC configuration of the UE, 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 UE specificity through a combination of RRC signaling and / or one or more parameters indicated by the DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least the 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 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 restricted to the scheduled time / frequency duration of the UE.

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

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

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

[0170] 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 beam measurement reports based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)). After setting up an RRC connection with a base station, the UE can perform a downlink beam measurement procedure.

[0171] Figure 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Figure 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured for the 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 a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0172] Figure 11B The three beams shown may be configured for a UE in a UE-specific configuration. Figure 11B Three beams (beam #1, beam #2, and beam #3) are illustrated in FIG, and more or fewer beams may be configured. CSI-RS 1101 may be allocated to beam #1, which may be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS 1102 may be allocated to beam #2, which may be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS 1103 may be allocated to beam #3, which may be transmitted in one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in the same RB (e.g., those subcarriers 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), a beam for a UE may be configured such that the beam for the UE uses symbols from beams of other UEs.

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

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

[0175] Figure 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of Tx beams of the TRPs (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or base station may perform procedure P2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam 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.

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

[0177] The UE may initiate a beam failure recovery (BFR) procedure based on the detection of a beam failure. The UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having an error rate above an error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

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

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

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

[0181] The 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-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0182] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that may be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities, and (b) one or more reference signals. The one or more RACH parameters may indicate an 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 the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

[0183] The one or more RACH parameters provided in the configuration message 1310 may 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 may indicate a reference power for preamble transmission (e.g., a received target power and / or an initial power for preamble transmission). One or more power offsets may be present as indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramp step size; a power offset between an SSB and a CSI-RS; a power offset between transmissions of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and / or a CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplementary uplink (SUL) carrier).

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

[0185] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a 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 may 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 may determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) to select a preamble and to determine a PRACH opportunity. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

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

[0187] 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 alignment command, which may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may initiate a time window (e.g., a RA-ResponseWindow) to monitor the PDCCH for Msg 2 1312. The UE may determine when to initiate the time window based on the PRACH opportunity used by the UE to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events for initiating a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTI may be as follows:

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

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

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

[0191] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If a C-RNTI is included in Msg 3 1313, 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 a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in the RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was successfully completed.

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

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

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

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

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

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

[0198] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Figure 13C 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 include: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; the cell size; the RRC state of the UE; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0199] The UE may 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 the configuration message 1330. The RACH parameters may 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) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0200] Transport block 1342 may include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure is 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).

[0201] The UE and the base station may 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.

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

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

[0204] DCI can be used for different 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 with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. The P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or the triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Figure 13AThe other RNTIs configured by the base station to the UE may include: the configured scheduling RNTI (CS-RNTI), transmit power control PUCCH RNTI (TPC-PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), interruption 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.

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

[0206] After scrambling the DCI with the RNTI, the base station can process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling and / or QPSK modulation. The base station can map the coded and modulated DCI on resource elements used for and / or configured for PDCCH. Based on the payload size of the DCI and / or the coverage of the base station, 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. CCE may include the number of resource element groups (REGs) (e.g., 6). REG may include a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements can be based on the mapping of CCEs and REGs (e.g., CCE to REG mapping).

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

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

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

[0210] like Figure 14B As shown, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE to REG mapping of the CORESET based on the configuration parameters of the CORESET (e.g., interleaving or non-interleaving and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). The UE may monitor a set of PDCCH candidates based on the configuration parameters of the search space set. The UE may 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 based on the monitored DCI format. Monitoring may include decoding DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE may determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, etc.).

[0211] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling transmission may include a hybrid automatic repeat request (HARQ) acknowledgment for the received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. The 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 may determine the transport format parameters for downlink transmission (e.g., including multiple antennas and beamforming schemes). The uplink control signaling may include a scheduling request (SR). The UE may transmit the SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgment (HARQ-ACK), CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0212] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE may use PUCCH format 0 to transmit UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may 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 may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. If the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

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

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

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

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

[0217] In the downlink, data to be transmitted from the base station 1504 to the wireless device 1502 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 via, for example, the core network. In the uplink, data to be transmitted from the wireless device 1502 to the base station 1504 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may 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 Layer 3 may include the SDAP layer, PDCP layer, RLC layer and MAC layer. Figure 2B RRC layer.

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

[0219] At base station 1504, receive processing system 1512 may receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 may receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and the like.

[0220] like Figure 15 As shown, wireless device 1502 and base station 1504 may include multiple antennas. The multiple antennas may be used to implement 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.

[0221] Processing system 1508 and processing system 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 may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Figure 15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive 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 may be executed to perform one or more of their respective functions.

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

[0223] The processing system 1508 and / or the processing system 1518 can 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 the one or more peripheral devices 1526 can include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touchpad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 can receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

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

[0225] Figure 16B An exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. Filtering can be employed prior to transmission.

[0226] Figure 16C An exemplary structure for downlink transmission is shown. The baseband signal representing the physical downlink channel can perform one or more functions. These one or more functions may include: scrambling coded bits in a codeword to be transmitted on 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 on the layers for transmission on the antenna ports; mapping the complex-valued modulation symbols for the antenna ports to resource elements; generating a complex-valued time-domain OFDM signal for the antenna ports; and so on. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0227] Figure 16D Another exemplary structure for modulation and up-conversion 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.

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

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

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

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

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

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

[0234] Figure 17A An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Figure 17A In the exemplary MAC subheader of , the LCID field may be six bits in length and the L field may be eight bits in length. Figure 17B An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Figure 17B In the exemplary MAC subheader shown in FIG, the LCID field may be six bits long, and the L field may 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 having a two-bit length and an LCID field having a multi-bit length. Figure 17C An example of a MAC subheader having an R field and an LCID field is shown. Figure 17C In the exemplary MAC subheader shown in , the LCID field may be six bits in length and the R field may be two bits in length.

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

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

[0237] In an example, a MAC entity of a wireless device may transmit one or more MAC CEs to a MAC entity of a base station. Figure 20An example of one or more MAC CEs is shown. The one or more MAC CEs may include at least one of the following: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grant confirmation MAC CE; a single-entry PHR MAC CE; a multi-entry PHR MAC CE; a short truncated BSR; and / or a long truncated BSR. In the example, the MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short truncated command MAC CE.

[0238] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may receive or transmit simultaneously on one or more CCs using CA techniques depending on the capabilities of the wireless device. In an embodiment, a wireless device may support CA for contiguous CCs and / or for non-contiguous CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device may have one RRC connection with the network. During RRC connection establishment / reestablishment switching, the cell that provides NAS mobility information may be a serving cell. During the RRC connection establishment / handover procedure, the cell that provides security input may be a serving cell. In an example, the serving cell may represent a PCell. In an example, the base station may transmit one or more messages including configuration parameters for multiple one or more SCells to the wireless device depending on the capabilities of the wireless device.

[0239] When configured with Carrier Access Control (CA), the base station and / or wireless device can employ SCell activation / deactivation mechanisms to improve battery and power consumption in 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. Following SCell configuration, the SCell can be deactivated immediately unless the SCell state associated with the SCell is set to "activated" or "dormant."

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

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

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

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

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

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

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

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

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

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

[0250] In an example, in response to receiving a DCI indicating a DL assignment on BWP 1, the wireless device may 个 The BWP inactivity timer (e.g., BWP-InactivityTimer) is restarted at the beginning of the time slot. When the BWP inactivity timer expires, the wireless device can s The wireless device may switch back to the default BWP (e.g., BWP 0) as the active BWP for each time slot. When the sCellDeactivationTimer expires, the wireless device may deactivate the cell and / or stop the BWP inactivity timer.

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

[0252] In an example, on an inactive BWP for each activated 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.

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

[0254] In an example, for a primary cell, a default DL BWP among the configured DL BWPs may be provided to the wireless device via the higher layer parameter Default-DL-BWP. If no default DL BWP is provided to the wireless device via the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a timer value for the primary cell may be provided to the wireless device via the higher layer parameter bwp-InactivityTimer. If configured, the wireless device may increment the timer (if running) at intervals of 1 millisecond for frequency range 1 or 0.5 milliseconds for frequency range 2 if, during the 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.

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

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

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

[0258] In an example, the wireless device determines the PDCCH monitoring occasions on the active DL BWP based on one or more PDCCH configuration parameters including: PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring pattern within a time slot. For a search space set (SS s), if Then the wireless device determines that the number of PDCCH monitoring opportunities exists in n f The number of frames is in the time slot. is the number of time slots in a frame when the parameter set μ is configured. s k is the slot offset indicated in the PDCCH configuration parameter. s The PDCCH monitoring period is indicated in the PDCCH configuration parameter. Start monitoring PDCCH candidates for the search space set for T s consecutive time slots, and in the next k s -T s No PDCCH candidates are monitored for the search space set s during consecutive time slots.In an example, the USSs at CCE aggregation level L∈{1,2,4,8,16} are defined by the set of PDCCH candidates for CCE aggregation level L.

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

[0260] In an example, a wireless device may monitor a set of PDCCH candidates based on configuration parameters of a search space set including multiple search spaces (SSs). The wireless device may 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 based on the monitored DCI format. Monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding.

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

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

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

[0264] In an example, based on receiving the MIB, the wireless device may monitor the PDCCH via SS#0 of CORESET#0 for receiving DCI scheduling system information block 1 (SIB1). The wireless device may receive the DCI with a CRC scrambled with a system information radio network temporary identifier (SI-RNTI) dedicated to receiving SIB1.

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

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

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

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

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

[0270] Figure 26An example of a configuration of a search space (e.g., SearchSpace IE) is shown. In the example, one or more search space configuration parameters of the search space may include at least one of the following: a search space ID (searchSpaceId), a control resource set ID (controlResourceSetId), a monitoring slot period and offset parameter (monitoringSlotPeriodicityAndOffset), a search space duration value (duration), a monitoring symbol indication (monitoringSymbolsWithinSlot), the number of candidates for the aggregation level (nrofCandidates), and / or an SS type indicator (searchSpaceType) indicating a common SS type or a UE-specific SS type. The monitoring slot period and offset parameter may indicate a time slot (e.g., within a radio frame) and a time slot offset (e.g., relative to the start of a radio frame) for periodic PDCCH monitoring. The monitoring symbol indication may indicate on which symbol(s) of a time slot a wireless device may monitor for PDCCH on an SS. The control resource set ID may identify a control resource set on which an SS may be located. The search space duration value may indicate the number of (consecutive) time slots that the SS lasts in each opportunity (e.g., each period given in monitoringSlotPeriodicityAndOffset). If the search space duration value is not present, the wireless device may apply a value of 1 time slot, except for DCI format 2_0. For DCI format 2_0, the wireless device may ignore this field. The maximum valid duration may be periodicity-1 (the period given in monitoringSlotPeriodicityAndOffset). In an example, the SS type indicator may indicate whether the SS is a common search space (current) or a UE-specific search space and the DCI format to monitor. The DCI format configured by the searchSpaceType of SearchSpace may include at least one of the following: DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, DCI format 2_0, DCI format 2_1, DCI format 2_2, DCI format 2_3, DCI format 1_2, DCI format 0_2, DCI format 3_0, DCI format 3_1, etc. Based on Figure 29 , can realize multiple DCI formats.

[0271] Figure 27 An example of the configuration of a search space (eg, SearchSpaceExt-r16) is shown. In the example, in addition to the configuration of Figure 26In addition to the first parameters configured by SearchSpace as shown, the configuration parameters configured by SearchSpaceExt-r16 may be the second parameters for the SS. The configuration parameters configured by SearchSpaceExt-r16 may include a CORESET ID that identifies the corresponding CORESET of the SS. When the CORESET ID is present in SearchSpaceExt-r16, the wireless device may ignore the controlResourceSetId configured in the SearchSpace of the SS. In an example, the configuration parameters of the SS configured by SearchSpaceExt-r16 may include an SS type indication (e.g., searchSpaceType-r16) that indicates whether the SS is a common search space (current) or a UE-specific search space and the DCI format to be monitored. The DCI format configured by searchSpaceType-r16 may include DCI format 2_4, DCI format 2_5, DCI format 2_6, etc. Based on Figure 29 , can realize multiple DCI formats.

[0272] In an example, the configuration parameters of the SS configured by SearchSpaceExt-r16 may include a search space group list (e.g., searchSpaceGroupIdList), which indicates a list of search space group IDs with which the SS is associated. In an example, the configuration parameters of the SS configured by SearchSpaceExt-r16 may include a frequency monitoring location indication bitmap (e.g., freqMonitorLocations). A value of 1 for a bit of the bitmap may indicate that a frequency domain resource allocation copied from a pattern configured in an associated CORESET is mapped to a corresponding resource block (RB) set. The LSB of the bitmap may correspond to the lowest RB set in the BWP. For the RB set indicated in the bitmap, the first PRB of the frequency domain monitoring location restricted to within the RB set is aligned with {the first PRB of the RB set + rb-Offset} provided by the associated CORESET.

[0273] Figure 28 An example of PDCCH monitoring of SS based on the configuration of SS is shown. Figure 26 and / or Figure 27 In the described exemplary embodiments, the wireless device may be configured with an SS. The wireless device may determine a PDCCH monitoring opportunity within a time slot on an active DL BWP based on one or more configuration parameters of the SSs, including a PDCCH monitoring period (k s )), PDCCH monitoring duration (T s), PDCCH monitoring offset (o s ) and PDCCH monitoring mode (monitoringSymbolsWithinSlot). For SSs, if (n f . The wireless device can then determine the number n f The frame number is There is a PDCCH monitoring opportunity in the time slot. It can be multiple time slots in a frame. Figure 7 The exemplary embodiment described implements a frame structure. A wireless device may Starting T s PDCCH candidates of monitoring SSs in consecutive time slots and not in the next k s -T s The search space s for monitoring PDCCH candidates in consecutive time slots. Figure 28 As shown, T s =3,k s =6. Based on T s and k s , the wireless device may monitor PDCCH in slot 0, slot 1, and slot 2. The wireless device may skip monitoring PDCCH in slot 3, slot 4, and slot 5. The wireless device may monitor PDCCH candidates based on the exemplary embodiments described in the previous paragraphs of this specification.

[0274] Figure 29 Examples of DCI formats that can be used when a first wireless device (e.g., a base station) transmits control information to a second wireless device (e.g., a terminal) are shown. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In the example, DCI format 0_0 can be used to schedule PUSCH in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCHs in a cell, or to indicate CG-DFI (configured grant-Downlink feedback information) of a configured granted PUSCH, etc. The DCI formats that a wireless device can monitor in an SS can be based on information about Figure 26 and / or Figure 27 .

[0275] Figure 30A An example of PDSCH scheduling based on DCI is shown. In the example, the wireless device can monitor PDCCH via one or more SSs on the BWP of the cell. One or more SSs can be based on the above Figure 26 and / or Figure 27The exemplary embodiment described is configured. The wireless device may monitor the PDCCH in one or more time slots based on the PDCCH monitoring period and PDCCH monitoring duration configured for one or more SSs. In the example, the wireless device may receive DCI during the PDCCH monitoring period in the time slot. The DCI may include a downlink assignment (or uplink grant) indicating the PDSCH resources (or PUSCH resources) used to transmit the TB. Each DCI may schedule a TB corresponding to a HARQ process. The TB may include a single codeword (e.g., in response to the wireless device not supporting spatial multiplexing). The TB may include two codewords (e.g., in response to the wireless device supporting spatial multiplexing), each codeword being associated with a corresponding MCS indication, an NDI indication, and / or an RV indication. The downlink assignment for the TB may include one or more symbols of the time slot.

[0276] like Figure 30A As shown, different DCIs may indicate downlink assignments corresponding to different PDSCHs (for different TBs). DCI1 in the first time slot may indicate a downlink assignment for PDSCH1. DCI2 in the second time slot may indicate a downlink assignment for PDSCH2. DCI3 in the second time slot may indicate a downlink assignment for PDSCH3, and so on. Each PDSCH (e.g., PDSCH1, PDSCH2, PDSCH3) may be used to transmit a TB corresponding to a HARQ process. In the example, a time slot may include resources for PDCCH and / or PDSCH. Based on the above description of Figure 7 The resources used for PDCCH / PDSCH can be based on the above Figure 14A 、 Figure 14B 、 Figure 25 、 Figure 26 and / or Figure 27 The exemplary embodiments described are configured.

[0277] like Figure 30AAs shown, the DCI may indicate the PDSCH resources for the TB corresponding to the HARQ process. Scheduling a TB based on DCI may be referred to as a single PDSCH scheduling scheme. Compared to a single PDSCH scheduling scheme, a DCI that schedules multiple PDSCHs may be referred to as a multiple-PDSCH (or multi-PDSCH) scheduling scheme. Scheduling multiple PDSCHs based on a single DCI (e.g., each PDSCH is associated with a corresponding TB) may reduce signaling overhead and / or reduce power consumption for PDCCH monitoring. The multi-PDSCH scheduling scheme may be beneficial for wireless systems deployed at high frequencies (e.g., above 50 GHz), where the slot length may be 15.6 us for a 960 kHz subcarrier spacing compared to 1 ms for a 15 kHz subcarrier spacing at low frequencies (e.g., 2 GHz). Figure 30B An example of a multiple PDSCH scheduling scheme is shown.

[0278] like Figure 30B As shown, a wireless device may receive DCI during a PDCCH monitoring period in a time slot. The DCI may include a set of downlink assignments (or uplink grants) indicating multiple PDSCH resources (or PUSCH resources) for transmitting multiple TBs. The DCI may schedule multiple TBs, each associated with a corresponding HARQ process. Each of the multiple TBs may be transmitted in a corresponding time slot indicated by one of the PDSCH resources associated with the TB.

[0279] like Figure 30B As shown, DCI 1 in the first time slot (e.g., time slot y) may indicate downlink assignments for PDSCH 1, PDSCH 2, PDSCH 3, and PDSCH 4. PDSCH 1 may be in time slot x and used to transmit TB 1. PDSCH 2 may be in time slot x+1 and used to transmit TB 2. PDSCH 3 may be in time slot x+2 and used to transmit TB 3. PDSCH 4 may be in time slot x+3 and used to transmit TB 4. Scheduling multiple PDSCHs in a DCI may reduce signaling overhead and / or reduce power consumption of a wireless device.

[0280] In an example, when a wireless system is deployed at a high frequency (e.g., above 50 GHz), the scheduling unit (e.g., time slot) can be much shorter than at a low frequency (e.g., 2 GHz). A wireless device can monitor the PDCCH more frequently at a high frequency than at a low frequency. For example, when a 960 KHz SCS is used at a high frequency, the length of a time slot can be approximately 1 / 64 of the length of a time slot when a 15 KHz SCS is used at a low frequency. If a wireless device is configured to monitor the PDCCH at a granularity of a time slot, the wireless device can monitor the PDCCH in a system configured with a 960 KHz SCS with 64 times the complexity of PDCCH monitoring in a system configured with a 15 KHz SCS. This may increase the power consumption of the wireless device. In an example, if the SCS is 15 kHz, the maximum number of PDCCH candidates per time slot on the BWP may be 44, if the SCS of the BWP is 30 kHz, the maximum number is 36, if the SCS of the BWP is 60 kHz, the maximum number is 22, or if the SCS of the BWP is 120 kHz, the maximum number is 20. As the SCS increases, the maximum number of PDCCH candidates per time slot may decrease. The reduced number of PDCCH candidates may reduce the throughput of signaling transmission.

[0281] In an example, in order to improve power consumption of wireless devices operating at high frequencies and / or increase signaling throughput, a base station may, based on the above description of Figure 30B The exemplary embodiment described is used to transmit DCI that schedules multiple PDSCHs. In the example, the base station can transmit configuration parameters of the first SS of the first BWP to the wireless device at a high frequency, where the configuration parameters indicate the first PDCCH monitoring period and the first PDCCH monitoring duration (e.g., T s=1 time slot), where for the second BWP, the first PDCCH monitoring period may be longer than the second PDCCH monitoring period of the second SS, and / or for the second BWP, the first PDCCH monitoring duration may be shorter than the second PDCCH monitoring duration. Based on the prior art, the wireless device may monitor PDCCHs with different DCI formats configured on the first SS with a first PDCCH monitoring period and a first PDCCH monitoring duration. In the example, some DCI formats (e.g., DCI format 0_0 / 1_0, DCI format 2_x, etc.) may not be suitable for transmission based on the first PDCCH monitoring period and the first PDCCH monitoring duration. DCI format 1_0 (or 0_0) may be used only for scheduling a single PDSCH (or a single PUSCH). Based on backward compatibility / device cost considerations, DCI format 1_0 (or 0_0) may not be used for scheduling multiple PDSCHs (or multiple PUSCHs). DCI format 2_x (e.g., 2_0 / 2_1 / 2_2 / 2_3 / 2_4 / 2_5 / 2_6) may not be used for scheduling PDSCH / PUSCH. Monitoring DCI format 0_0 / 1_0 and / or DCI format 2_x according to a longer PDCCH monitoring period and a shorter PDCCH monitoring duration configured for multi-PDSCH scheduling may increase the waiting time for system information delivery (e.g., when system information is scheduled by DCI format 1_0), or increase the waiting time for group common control information delivery (e.g., when group common control information is scheduled by DCI format 2_x). When the PDCCH monitoring period and / or PDCCH monitoring duration are configured for multi-PDSCH scheduling, the prior art may increase the waiting time for system information or group common control information delivery. When multi-PDSCH scheduling is supported, for example, at high frequencies, it is necessary to reduce the waiting time for system information or group common control information delivery.

[0282] In an exemplary embodiment, the base station may transmit configuration parameters to the wireless device, including a DCI format-specific PDCCH monitoring period / duration on the SS of the BWP. The wireless device may determine the PDCCH monitoring timing for different DCI formats based on different DCI format-specific PDCCH monitoring periods and / or different DCI format-specific PDCCH monitoring durations. When supporting multiple PDSCH scheduling, the exemplary embodiment may reduce the latency of system information or group common control information delivery. When supporting multiple PDSCH scheduling, the exemplary embodiment may reduce the power consumption of PDCCH monitoring for UE-specific TB scheduling.

[0283] In an exemplary embodiment, upon receiving a DCI scheduling multiple PDSCHs, the wireless device may ignore the PDCCH monitoring period / duration of the SS configured by the RRC message. Ignoring the PDCCH monitoring period / duration may include skipping monitoring the PDCCH in a certain number of time slots after receiving the DCI, where the number may be determined based on the total number of PDSCHs scheduled by the DCI.

[0284] In an exemplary embodiment, the base station may maintain the configuration parameters of the SS unchanged. The wireless device may adapt PDCCH monitoring based on whether the DCI schedules a single PDSCH or schedules PDSCHs in multiple time slots. The exemplary embodiment may reduce the power consumption of the wireless device and / or the delivery latency of system information.

[0285] In an exemplary embodiment, the wireless device may use a first DCI format (e.g., Figure 29 The wireless device may monitor the PDCCH in a first PDCCH monitoring opportunity for the DCI format 1_0 / 0_0 shown, or other group common DCI formats 2-0 / 2-1 / 2-2 / 2-3 / 2-4 / 2-5 / 2-6) for single PDSCH / PUSCH scheduling. The wireless device may monitor the PDCCH in a second PDCCH monitoring opportunity for the second DCI format (e.g., DCI format 1_1 / 0_1 or DCI format 1_2 / 0_2) for multiple PDSCH / PUSCH scheduling. The first PDCCH monitoring opportunity may have a shorter period than the second PDCCH monitoring opportunity. The first PDCCH monitoring opportunity may have a longer duration (in time slots) than the second PDCCH monitoring opportunity. The first PDCCH monitoring opportunity and the second PDCCH monitoring opportunity may be associated with a single SS (e.g., CSS or USS) or different SSs. Based on monitoring the first PDCCH monitoring opportunity, the wireless device may monitor the PDCCH via PDSCH / PUSCH (or indication such as Figure 29The wireless device receives a first DCI with a first DCI format that schedules a TB based on a group common command of DCI format 2_0 / 2_1 / 2_2 / 2_3 / 2_4 / 2_5 / 2_6 as shown. The TB can be a system information message or a broadcast message. The wireless device can receive the TB via PDSCH or transmit the TB via PUSCH. In the example, based on monitoring a second PDCCH monitoring opportunity, the wireless device can receive a second DCI with a second DCI format that schedules multiple TBs via multiple PDSCH / PUSCH in multiple time slots. The multiple time slots can be continuous or discontinuous. Each of the multiple TBs can be associated with a different HARQ process (or belong to a different HARQ process). The wireless device can receive the multiple TBs via multiple PDSCHs in multiple time slots (if the DCI includes a downlink assignment indication) or transmit the multiple TBs via multiple PUSCHs in multiple time slots (if the DCI includes an uplink grant indication). When supporting multiple PDSCH scheduling, the exemplary embodiment can reduce the waiting time for delivery of system information or group common control information. When multiple PDSCH scheduling is supported, exemplary embodiments may reduce power consumption for PDCCH monitoring for UE-specific TB scheduling.

[0286] Figure 31 An exemplary embodiment of a PDCCH monitoring configuration for multi-PDSCH scheduling in a BWP is shown. In the example, a wireless device may receive parameters for a search space (SS) on a BWP of a cell from a base station. The parameters may be transmitted in one or more RRC messages. The parameters may include a first plurality of PDCCH monitoring periods and a second plurality of PDCCH monitoring durations. The parameters may indicate whether the SS belongs to a common SS or a UE-specific SS. The parameters may indicate a third number of DCI formats. Each PDCCH monitoring period in the first plurality of PDCCH monitoring periods may be associated with a corresponding DCI format in the third number of DCI formats. Each PDCCH monitoring duration in the second plurality of PDCCH monitoring durations may be associated with a corresponding DCI format in the third number of DCI formats. In the example, a DCI format in the third number of DCI formats may be associated with a corresponding PDCCH monitoring period in the first plurality of PDCCH monitoring periods. A DCI format in the third number of DCI formats may be associated with a corresponding PDCCH monitoring duration in the second plurality of PDCCH monitoring durations.

[0287] In an example, the third number of DCI formats may include Figure 29The one or more first DCI formats shown. The one or more first DCI formats may include at least one of the following: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 2_0, DCI format 2_1, DCI format 2_2, DCI format 2_3, DCI format 2_4, DCI format 2_5, DCI format 2_6, DCI format 3_0 and / or DCI format 3_1. The third number of DCI formats may include different Figure 29 One or more second DCI formats of the one or more first DCI formats shown. One of the one or more second DCI formats may be designed for signaling delivery in a short time slot length. One of the one or more second DCI formats (e.g., DCI formats 1_3) may be designed for scheduling multiple PDSCHs by DCI. One of the one or more second DCI formats (e.g., DCI formats 0_3) may be designed for scheduling multiple PUSCHs by DCI. One of the one or more second DCI formats may be designed for scheduling PDSCH and PUSCH by DCI.

[0288] In the example, the DCI format 1_0 (or DCI format 0_0) configured on the SS can be associated with the first PDCCH monitoring period and / or the first PDCCH monitoring duration. The DCI format 1_1 (or DCI format 0_1) configured on the SS can be associated with the second PDCCH monitoring period and / or the second PDCCH monitoring duration. The DCI format 1_2 (or DCI format 0_2) configured on the SS can be associated with the third PDCCH monitoring period and / or the third PDCCH monitoring duration. DCI format 2_0 (or DCI format 2_1, DCI format 2_2, etc.) can be associated with the fourth PDCCH monitoring period and / or the fourth PDCCH monitoring duration. DCI format 1_3 (or DCI format 1_3, or a new DCI format designed for multiple PDSCH / PUSCH scheduling) can be associated with the fifth PDCCH monitoring period and / or the fifth PDCCH monitoring duration.

[0289] In an example, the first PDCCH monitoring period of DCI format 1_0 (or DCI format 0_0) may be shorter than other PDCCH monitoring periods of other DCI formats. The first PDCCH monitoring duration of DCI format 1_0 (or DCI format 0_0) may be longer than other PDCCH monitoring durations of other DCI formats. Configuring a shorter monitoring period and / or a longer monitoring duration for DCI format 1_0 / 0_0 may reduce the latency of delivery of system information (or paging, PDCCH command, RAR message, etc.) scheduled by compact DCI (e.g., DCI format 1_0 / 0_0).

[0290] In an example, the second PDCCH monitoring period of DCI format 1_1 (or DCI format 0_1) can be longer than other PDCCH monitoring periods of other DCI formats. The second PDCCH monitoring duration of DCI format 1_1 (or DCI format 0_1) can be shorter than other PDCCH monitoring durations. If DCI format 1_1 / 0_1 is used to schedule multiple PDSCHs (or PUSCHs), configuring DCI format 1_1 / 0_1 with a longer monitoring period and / or a shorter monitoring duration can reduce power consumption when the PDCCH schedules multiple PDSCHs / PUSCHs, for example, when the wireless device is operating at a high frequency configured with a larger SCS (e.g., 480 kHz, 960 kHz, etc.).

[0291] In an example, the base station may transmit a new DCI format for multi-PDSCH scheduling (e.g., DCI format 1_3, which is different from DCI format 1_0, DCI format 1_1, and / or DCI format 1_2). For the new DCI format, the base station may configure a PDCCH monitoring period that is longer than other PDCCH monitoring periods for other DCI formats. For the new DCI format, the base station may configure a PDCCH monitoring duration that is shorter than other PDCCH monitoring durations for other DCI formats.

[0292] In an example, based on the parameters of the SS on the BWP of the cell, the wireless device may monitor the PDCCH of different DCI formats with different monitoring periods and / or different monitoring durations. Figure 31 As shown, the wireless device may monitor the PDCCH of the first DCI format on the BWP with a first monitoring period and / or a first monitoring duration. During the monitoring of the PDCCH, the wireless device may receive a first DCI with the first DCI format and a second DCI with the first DCI format. The wireless device may receive a first DCI with the first DCI format and a second DCI with the first DCI format based on the above Figure 28 The described exemplary embodiment determines the PDCCH monitoring opportunity according to the monitoring period and / or monitoring duration. Figure 32In an exemplary embodiment, the wireless device may determine a per-DCI format PDCCH monitoring opportunity based on a per-DCI format monitoring period and / or a per-DCI format monitoring duration. In an example, a first DCI may schedule a TB via a PDSCH / PUSCH, where the TB may be a system information message, a paging message, a PDCCH command, a short message delivered by the first DCI, etc. In response to receiving the first DCI, the wireless device may receive / transmit the TB based on the first DCI.

[0293] like Figure 31 As shown, the wireless device may monitor the PDCCH of the second DCI format on the BWP with a second monitoring period and / or a second monitoring duration. During the monitoring of the PDCCH, the wireless device may receive a third DCI with the second DCI format and a fourth DCI with the second DCI format. The wireless device may receive a third DCI with the second DCI format and a fourth DCI with the second DCI format based on the above Figure 28 The described exemplary embodiment determines the PDCCH monitoring timing based on the monitoring period and / or monitoring duration. In the example, the third DCI can schedule multiple TBs via multiple PDSCHs, where each of the multiple TBs is associated with a corresponding HARQ process. The multiple PDSCHs can be in consecutive time slots. Each of the multiple PDSCHs can be associated with one or more symbols in the corresponding time slot associated with the PDSCH. In response to receiving the third DCI, the wireless device can receive multiple TBs in consecutive time slots based on the third DCI.

[0294] In an example, a fourth DCI may schedule multiple TBs via multiple PUSCHs. Each of the multiple TBs may be associated with a corresponding HARQ process. The multiple PUSCHs may be in consecutive time slots. Each of the multiple PUSCHs may be associated with one or more symbols in the corresponding time slot associated with the PUSCH. In response to receiving the fourth DCI, the wireless device may transmit the multiple TBs in the consecutive time slots based on the fourth DCI.

[0295] based on Figure 31In an exemplary embodiment, the base station configures a DCI format-specific PDCCH monitoring period and / or PDCCH monitoring duration for one or more DCI formats associated with the SS on the BWP. In the example, different DCI formats configured on the SS can be associated with different or separate PDCCH monitoring periods and / or PDCCH monitoring durations. Based on this configuration, the wireless device can adapt PDCCH monitoring for different DCI formats according to different or separate PDCCH monitoring periods and / or different PDCCH monitoring durations. When multiple PDSCH scheduling is supported, the exemplary embodiment can reduce the waiting time for the delivery of system information or group common control information. When multiple PDSCH scheduling is supported, the exemplary embodiment can reduce the power consumption of PDCCH monitoring for UE-specific TB scheduling.

[0296] Figure 32 FIG. 4 shows an exemplary embodiment of a PDCCH monitoring period / duration configured per DCI format. Figure 32 As shown, the wireless device may be configured with a first period and a first duration for monitoring the PDCCH according to a first DCI format on the SS of the BWP of the cell. The wireless device may be configured with a second period and a second duration for monitoring the PDCCH according to a second DCI format on the SS. The wireless device may be configured with a third period and a third duration for monitoring the PDCCH according to a third DCI format on the SS. The configuration of multiple periods and / or multiple durations may be based on the above description of Figure 31 The exemplary embodiments described are implemented.

[0297] like Figure 32 As shown, based on the first cycle and the first duration, the wireless device may perform the following operations at a second number (eg, Figure 32 5) of the time slots, in a first number (e.g., Figure 32 After the first number of time slots, the wireless device may skip monitoring the PDCCH for the first DCI format in the remaining time slots in the second number of time slots.

[0298] like Figure 32 As shown, based on the second period and the second duration, the wireless device may perform the following operations at a second number (eg, Figure 32 4) of the time slots, in a first number (e.g., Figure 32 After the first number of time slots, the wireless device may skip monitoring the PDCCH for the second DCI format in the remaining time slots in the second number of time slots.

[0299] like Figure 32 As shown, based on the third cycle and the third duration, the wireless device may perform the second number (eg, Figure 32 3) of the time slots, in a first number (e.g., Figure 32 After the first number of time slots, the wireless device may skip monitoring the PDCCH for the third DCI format in the remaining time slots in the second number of time slots.

[0300] based on Figure 31 and / or Figure 32 In an exemplary embodiment, a wireless device may determine PDCCH monitoring opportunities for different DCI formats based on different / individual DCI format-specific PDCCH monitoring periods and / or different / individual DCI format-specific PDCCH monitoring durations. When supporting multiple PDSCH scheduling, the exemplary embodiment may reduce latency for delivery of system information or group-common control information. When supporting multiple PDSCH scheduling, the exemplary embodiment may reduce power consumption for PDCCH monitoring for UE-specific TB scheduling.

[0301] Figure 31 and / or Figure 32 It can be extended to improve the signaling overhead of PDCCH configuration in RRC messages. In an example, different DCI formats configured on an SS can be associated with the same PDCCH monitoring period and different / separate PDCCH monitoring durations. Figure 31 and / or Figure 32 , the wireless device may monitor PDCCHs of different DCI formats based on the same PDCCH period and different / separate PDCCH monitoring durations. In an example, different DCI formats configured for a SS may be associated with the same PDCCH monitoring duration and different / separate PDCCH monitoring period. Figure 31 and / or Figure 32 , the wireless device can monitor PDCCHs of different DCI formats based on the same PDCCH duration and different / separate PDCCH monitoring periods.

[0302] In an example, the PDCCH monitoring period and / or duration configured per DCI format may increase the signaling overhead of the RRC message. For backward compatibility, it may be beneficial to keep the PDCCH configuration parameters unchanged (e.g., in some cases). Example embodiments may include adjusting / adapting PDCCH monitoring based on the PDSCH scheduling configuration (e.g., single PDSCH scheduling or multiple PDSCH scheduling, etc.).

[0303] Figure 33 An exemplary embodiment of PDCCH monitoring for multiple PDSCH scheduling is shown. In the example, the wireless device can receive configuration parameters of the BWP of the cell from the base station. The configuration parameters may include a first parameter of a search space (SS) set on the BWP of the cell. The first parameter may be transmitted in one or more RRC messages. The first parameter may include a PDCCH monitoring period and a PDCCH monitoring duration. The first parameter may indicate a plurality of DCI formats configured on the SS (DCI format 1_0 / 1_1 / 1_2 for multiple PDSCH scheduling, DCI format 1_3, etc.). The configuration parameters may be based on the above Figure 26 and / or Figure 27 The exemplary embodiments described are implemented.

[0304] In an example, the configuration parameter may include a second parameter of the PDSCH on the BWP. The second parameter may include at least one of the following: a data scrambling identifier of the PDSCH, one or more DMRS mapping parameters, one or more TCI states, a resource allocation type indication, one or more PDSCH time domain allocation lists, a PDSCH aggregation factor, one or more rate matching modes, an MCS table indicator, a maximum number of codewords scheduled by the DCI, a PRB bundling parameter, an RS configuration parameter, etc.

[0305] In an example, the one or more PDSCH time domain allocation lists may include a first PDSCH time domain allocation list associated with a single PDSCH schedule (e.g., including a first number of K0, S, and L combinations). The first number may be 4, 8, 16, 32, or 64. The first PDSCH time domain allocation list associated with a single PDSCH schedule may be based on Figure 34 The first PDSCH time domain allocation list may be associated with a first number of DCI formats (eg, DCI format 1_0, DCI format 1_2).

[0306] In an example, the one or more PDSCH time domain allocation lists may include a second PDSCH time domain allocation list associated with multiple PDSCH scheduling. The second PDSCH time domain allocation list may have multiple (e.g., 4, 8, 16, 32, or 64) entries. Each entry may include a K0 value and multiple startSymbolAndLength (S and L) indications. Each indication in the multiple startSymbolAndLength indications may correspond to a specific PDSCH. The total number of multiple startSymbolAndLength indications (e.g., Figure 33The N shown in FIG4 may indicate how many PDSCHs the DCI may schedule for multiple (continuous) time slots. In an example, the total number may be 2, 4, 8, 16, or any number configured by the base station. The second PDSCH time domain allocation list associated with multiple PDSCH scheduling may be based on the following example: Figure 35 The exemplary embodiment shown is implemented. The second PDSCH time domain allocation list can be associated with a second number of DCI formats (e.g., DCI format 1_1, DCI format 1_3 for multi-PDSCH scheduling). Different DCI formats associated with different PDSCH time domain allocation lists can allow the base station to schedule system information or group common control information through a compact DCI format (e.g., DCI format 1_0 / 0_0) with a single PDSCH scheduling. Different DCI formats associated with different PDSCH time domain allocation lists can allow the base station to schedule UE-specific data through a full-size DCI format (e.g., DCI format 1_1 / 1_2 / 1_3, etc.) with multi-PDSCH scheduling. The exemplary embodiment can improve the latency of system information delivery and / or reduce the power consumption of PDCCH monitoring.

[0307] In an example, based on the PDCCH monitoring period and PDCCH monitoring duration of the SS, the wireless device may, for example, implement the above-mentioned Figure 28 The described exemplary embodiments monitor the PDCCH on the SS for receiving DCI.

[0308] like Figure 33 As shown, a wireless device may receive a first DCI while monitoring a PDCCH on an SS of a BWP. In response to receiving the first DCI having a first DCI format and including a TDRA field indicating an entry of a first PDSCH time domain allocation list, the wireless device may receive a first TB via the PDSCH indicated by the first DCI. The TDRA field of the first DCI indicates an entry of the first PDSCH time domain allocation list based on the first DCI having the first DCI format. The wireless device may determine a time domain resource of the PDSCH based on the TDRA field of the DCI. The wireless device may continue to monitor the PDCCH according to the PDCCH monitoring period and PDCCH monitoring duration of the SS.

[0309] like Figure 33As shown, the wireless device may receive a second DCI while monitoring a PDCCH on an SS of a BWP. In response to receiving the second DCI having a second DCI format and including a TDRA field indicating an entry of a second PDSCH time domain allocation list, the wireless device may determine that the second DCI schedules multiple PDSCHs. The TDRA field of the second DCI indicates an entry of a second PDSCH time domain allocation list based on the second DCI having the second DCI format. Based on the TDRA field of the second DCI, the wireless device may determine time domain resources for multiple PDSCHs in different time slots for multiple TBs. The wireless device may receive multiple TBs based on the second DCI. In this example, in response to receiving the second DCI scheduling multiple PDSCHs, the wireless device may skip monitoring the PDCCH having the second DCI format in multiple time slots by ignoring the period and duration of the SS. The wireless device may determine a number of time slots in which the wireless device may skip monitoring the PDCCH having the second DCI format as N-1 time slots, where N is the total number of PDSCHs scheduled by the second DCI or the total number of multiple startSymbolAndLength indications of entries of the second PDSCH time domain allocation list (e.g., as shown in FIG. Figure 35 shown).

[0310] based on Figure 33 In an exemplary embodiment, in response to a wireless device receiving a DCI that schedules multiple PDSCHs in consecutive time slots, the wireless device may skip PDCCH monitoring in the multiple time slots by ignoring the PDCCH monitoring period and the PDCCH monitoring duration. If the prior art is implemented, the wireless device may continue to monitor the PDCCH in the multiple consecutive time slots according to the PDCCH monitoring duration (e.g., if the PDCCH monitoring duration is configured to be 2 or more time slots), even if the wireless device receives a DCI that schedules multiple PDSCHs. Based on the exemplary embodiment, when receiving a DCI that schedules multiple PDSCHs, the wireless device may ignore the PDCCH monitoring period and / or the PDCCH monitoring duration by skipping monitoring the PDCCH in a certain number of time slots after receiving the DCI, where the number may be determined based on the total number of PDSCHs scheduled by the DCI.

[0311] based on Figure 33In an exemplary embodiment, without changing configuration parameters of the SS (e.g., a PDCCH monitoring period and / or a PDCCH monitoring duration), the wireless device may adapt PDCCH monitoring based on whether the DCI schedules a single PDSCH or multiple PDSCHs. In an example, the wireless device may monitor a PDCCH of a first DCI (e.g., having a first DCI format) that schedules a single PDSCH according to the configured PDCCH monitoring period and / or the configured PDCCH monitoring duration. In an example, based on receiving a second DCI (e.g., having a second DCI format) that schedules multiple PDSCHs, the wireless device may ignore the configured PDCCH monitoring period and / or the configured PDCCH monitoring duration for a plurality of time slots. Ignoring the configured PDCCH monitoring period and / or the configured PDCCH monitoring duration for a plurality of time slots may include skipping monitoring the PDCCH of the second DCI format for a plurality of time slots even if the PDCCH monitoring period and / or the PDCCH monitoring duration of the SS instructs the wireless device to monitor the PDCCH on the SS. The exemplary embodiment may maintain backward compatibility by keeping the configuration parameters of the SS unchanged. Based on keeping the configuration parameters of the SS unchanged, the exemplary embodiment can enable the wireless device to adapt PDCCH monitoring based on whether the DCI schedules a single PDSCH or schedules PDSCHs in multiple time slots. The exemplary embodiment can reduce the power consumption of the wireless device and / or the delivery latency of system information / paging / group common control information / PDCCH commands, etc.

[0312] In the example, Figure 33 Can be extended to further reduce the power consumption of PDCCH monitoring. The wireless device can determine the (actual) PDCCH monitoring period and / or duration for PDCCH monitoring for receiving DCI that schedules multiple PDSCHs based on the configured PDCCH monitoring period / duration and the total number of PDSCHs that the DCI can schedule. Unlike the prior art that determines the PDCCH monitoring timing based on the PDCCH monitoring period / duration of the SS, the exemplary embodiment includes determining the PDCCH monitoring timing based not only on the PDCCH monitoring period / duration of the SS, but also based on the total number of PDSCHs that the DCI can schedule. The exemplary embodiment can reduce the power consumption of the wireless device, for example, without increasing the latency of control signaling delivery.

[0313] In an example, if the configured PDCCH monitoring period of the SS is x slots, and the total number of PDSCHs that can be scheduled by DCI is y, the wireless device may determine the actual PDCCH monitoring period for receiving DCI as the least common multiple of x and y (e.g., 12 if x=3 and y=4). The wireless device may determine the actual PDCCH monitoring period as the maximum of x and y (e.g., 4 if x=3 and y=4). The wireless device may determine the actual PDCCH monitoring period as the minimum of x and y (e.g., 3 if x=3 and y=4).

[0314] In an example, if the configured PDCCH monitoring duration of the SS is m slots, and the total number of PDSCHs that can be scheduled by DCI is y, the wireless device may determine the actual PDCCH monitoring duration for receiving DCI as a number equal to floor(m / y) (e.g., 1 if m=3 and y=4, or 2 if m=8 and y=4, etc.).

[0315] Figure 34 An exemplary implementation of a single PDSCH scheduling scheme is shown. In the example, the base station may transmit an RRC message including configuration parameters for the PDSCH to the wireless device on the BWP of the cell. The configuration parameters may include a list of PDSCH resource allocation configurations for single PDSCH scheduling on the BWP. The list may include multiple entries indicating the PDSCH time domain resource allocation in a time slot. Each entry in the list may include a K0 value that indicates the time slot offset of the second time slot in which the PDSCH is transmitted relative to the first time slot in which the DCI corresponding to the PDSCH is transmitted. Each entry in the list may also include one or more start symbols and length indications that indicate the start symbol (S) of the time slot of the PDSCH and the length (L) of the multiple symbols of the PDSCH in the time slot. The total number of entries in the list may be 4, 8, 16, 32, 64, etc. In the example, the TDRA field of the DCI may indicate an entry of the PDSCH time domain resource indication list. If the total number of entries is 4, the TDRA field may have 2 bits, if the total number is 8, 3 bits, if the total number is 16, 4 bits, and so on. Figure 34As shown, DCI1 may include a TDRA field indicating the second entry of the list. The second entry of the list may indicate K0=2, S=2, and L=9. In response to receiving DCI1 with the TDRA field in time slot x, the wireless device may determine that the PDSCH scheduled by DCI1 is in time slot x+2 (e.g., K0=2), the second symbol of the time slot (e.g., S=2) is the starting symbol of the PDSCH, and the total number of PDSCH symbols is 9 (e.g., L=9). Based on the determined PDSCH resources in time slot x+2, the wireless device may receive the TB via the PDSCH resources.

[0316] Figure 35 An example of a multi-PDSCH scheduling scheme is shown. In the example, the base station may transmit an RRC message including configuration parameters of the PDSCH to the wireless device on the BWP of the cell. The configuration parameters may include a list of PDSCH resource allocation configurations for multi-PDSCH scheduling on the BWP. The list may include a first number of entries indicating the PDSCH time domain resource allocation in a second number of (contiguous) time slots. The total number of entries in the list (the first number) may be 4, 8, 16, 32, 64, etc. Each entry in the list may include a K0 value indicating a time slot offset of a starting time slot of the starting PDSCH for transmitting multiple PDSCHs relative to a first time slot for transmitting the DCI for scheduling the multiple PDSCHs. The wireless device may implement the above with respect to Figure 31 、 Figure 32 and / or Figure 33 The exemplary embodiment described is based on PDCCH monitoring to receive DCI. Each entry in the list may also include a second number of starting symbols and length indications, each starting symbol and length indication being associated with a corresponding PDSCH in a plurality of PDSCHs. The second number may indicate how many PDSCHs the DCI can schedule. The second number may be configured in the RRC message (or predefined as a fixed value) for the PDSCH configuration. Each starting symbol and length indication may indicate the starting symbol (S) of the time slot of the corresponding PDSCH and the length (L) of the multiple symbols of the PDSCH in the time slot. Figure 35 As shown, the first starting symbol and length indication of entry 1 may indicate S=1 and L=9 for PDSCH 1 in the starting slot. The second starting symbol and length indication of entry 1 may indicate S=1 and L=10 for PDSCH 2 in the next slot after the starting slot. The third starting symbol and length indication of entry 1 may indicate S=1 and L=9 for PDSCH 3 in the slot after the next slot, and so on.

[0317] In an example, a DCI that schedules multiple PDSCHs (e.g., Figure 35The TDRA field of the DCI1 in the PDSCH may indicate an entry of the PDSCH time domain resource indication list. If the total number of entries is 4, the TDRA field may have 2 bits, if the total number is 8, it may have 3 bits, if the total number is 16, it may have 4 bits, and so on. Figure 35 As shown, DCI1 may include a TDRA field indicating the second entry of the list. The second entry of the list may indicate K0=1, S=2 and L=9 for PDSCH 1, S=2 and L=10 for PDSCH 2, S=2 and L=9 for PDSCH 3, and so on. In response to receiving DCI1 with a TDRA field (e.g., in time slot x), the wireless device may determine that the time slots with multiple PDSCHs scheduled by DCI1 include time slots x+1, x+2, x+3, and so on (e.g., K0=1). In the example, based on K0=1, the first PDSCH of the multiple PDSCHs may be in time slot x+1. The first PDSCH may have the second symbol of time slot x+1 (e.g., S=2) as the starting symbol of the first PDSCH, and the total number of symbols of the first PDSCH is 9 (e.g., L=9). A second PDSCH among the multiple PDSCHs may be in time slot x+2, with the second symbol of time slot x+2 (e.g., S=2) serving as a starting symbol of the second PDSCH, and a total number of symbols of the second PDSCH being 10 (e.g., L=10). A third PDSCH among the multiple PDSCHs may be in time slot x+3, with the second symbol of time slot x+3 (e.g., S=2) serving as a starting symbol of the third PDSCH, and a total number of symbols of the third PDSCH being 9 (e.g., L=9).

[0318] Based on the determined plurality of PDSCHs, the wireless device may receive a plurality of TBs via the plurality of PDSCHs, each TB being received in a corresponding PDSCH in the plurality of PDSCHs. In an example, the wireless device may receive a first TB in PDSCH 1 in slot x+1, a second TB in PDSCH 2 in slot x+2, a third TB in PDSCH 3 in slot x+3, and so on.

[0319] Figure 36 An exemplary embodiment of PDCCH monitoring for multi-PDSCH scheduling is shown. In the example, the wireless device may receive an RRC message from a base station, the RRC message including configuration parameters of the SS in the BWP of the cell. Figure 33 The described exemplary embodiments implement configuration parameters.

[0320] like Figure 36 As shown, the wireless device can monitor the PDCCH based on the PDCCH monitoring period / duration associated with the SS. The wireless device can monitor the PDCCH based on the above Figure 28The wireless device may receive multiple PDSCHs scheduled in time slot 0 (e.g., PDSCH1 in time slot 1, PDSCH2 in time slot 2, PDSCH3 in time slot 3, and PDSCH4 in time slot 4, as shown in FIG. Figure 36 In response to receiving the first DCI, the wireless device may receive multiple TBs via several PDSCHs (e.g., a first TB in PDSCH1, a second TB in PDSCH2, a third TB in PDSCH3, and a fourth TB in PDSCH4). In response to receiving the first DCI, the wireless device may skip multiple (e.g., Figure 36 The number of time slots that the wireless device may skip PDCCH monitoring may be determined based on the total number of the multiple PDSCHs. In an example, if the total number of the multiple PDSCHs scheduled by the first DCI is 4, the wireless device may skip PDCCH monitoring in 1, 2, or 3 time slots (e.g., time slot 1, time slot 2, and / or time slot 3) after time slot 0, even if the PDCCH monitoring period and / or PDCCH monitoring duration of the SS instructs the wireless device to monitor time slot 1, time slot 2, and / or time slot 3 (e.g., if the PDCCH monitoring duration is configured to be 3 or more time slots). By ignoring PDCCH configuration parameters (e.g., PDCCH monitoring period / duration) and skipping PDCCH monitoring in multiple time slots after receiving a DCI scheduling multiple PDSCHs, power consumption of the wireless device may be improved.

[0321] Similarly, if Figure 36As shown, after skipping 3 slots for PDCCH monitoring, the wireless device may resume (or start) monitoring the PDCCH in slot 4. The wireless device may resume (or start) monitoring the PDCCH in slot 4 based on receiving a first DCI that schedules 4 PDSCHs in 4 consecutive slots. While monitoring the PDCCH in slot 4, the wireless device may receive a second DCI that schedules multiple PDSCHs (e.g., PDSCH 5 in slot 5, PDSCH 6 in slot 6, PDSCH 7 in slot 7, and PDSCH 8 in slot 8). The wireless device may receive multiple TBs via the multiple PDSCHs (e.g., TB 5 via PDSCH 5, TB 6 via PDSCH 6, TB 7 via PDSCH 7, and TB 8 via PDSCH 8, etc.). In response to receiving the second DCI in time slot 4, the wireless device skips PDCCH monitoring in the next three time slots after time slot 4 (e.g., time slot 5, time slot 6, and time slot 7), even if the PDCCH monitoring period and / or PDCCH monitoring duration of the SS instructs the wireless device to monitor time slot 5, time slot 6, and / or time slot 7 (e.g., if the PDCCH monitoring duration is configured to be 3 or more time slots).

[0322] In an example, if multiple PDSCH scheduling is configured, it may be difficult for the wireless device to determine whether PDCCH monitoring can be skipped. If the received DCI schedules multiple PDSCHs in consecutive time slots, the wireless device may skip PDCCH monitoring in some time slots. However, depending on the PDCCH monitoring duration of the PDCCH, if the PDCCH monitoring duration of the PDCCH is configured to be more than 1 time slot, the wireless device may need to monitor PDCCHs in multiple time slots. The prior art may increase the power consumption of the wireless device. The prior art may cause the PDCCH monitoring behavior between the base station and the wireless device to be misaligned. The exemplary embodiment ignores the PDCCH monitoring period / duration configured by the RRC message, and when the wireless device receives a DCI scheduling multiple PDSCHs via the PDCCH, the wireless device can skip PDCCH monitoring in multiple time slots. The exemplary embodiment can improve the power consumption of the wireless device.

[0323] In an exemplary embodiment, a wireless device monitors a search space of a BWP for a first PDCCH in a first DCI format based on a first period and a first duration. While monitoring the first PDCCH, the wireless device receives, via a PDSCH in a time slot, first DCI in the first DCI format indicating a first TB. The wireless device monitors a search space of the BWP for a second PDCCH in a second DCI format based on a second period and a second duration. While monitoring the second PDCCH, the wireless device receives, via a plurality of PDSCHs in a plurality of time slots, second DCI in a second DCI format indicating a plurality of TBs, each TB being associated with a corresponding PDSCH in a corresponding time slot.

[0324] In an exemplary embodiment, the wireless device receives parameters of a search space on a bandwidth portion via an RRC message, wherein the parameters indicate that a first DCI format is associated with a first period and a first duration, and a second DCI format is associated with a second period and a second duration.

[0325] In an exemplary embodiment, the first DCI format includes DCI format 1_0. The second DCI format includes DCI format 1_1.

[0326] In an exemplary embodiment, a cell includes a plurality of BWPs including a BWP.

[0327] In an exemplary embodiment, monitoring the first PDCCH of the first DCI format includes attempting to decode the first DCI having the first DCI format via resource elements associated with a search space over a first number of time slots in a second number of time slots, wherein the first number is determined based on the first duration and / or the second number is determined based on the first period. The wireless device skips monitoring the first PDCCH of the first DCI format in one or more remaining time slots in the second number of time slots other than the first number of time slots.

[0328] In an exemplary embodiment, monitoring the second PDCCH of the second DCI format includes attempting to decode the second DCI having the second DCI format via resource elements associated with a search space over a first number of time slots in a second number of time slots, wherein the first number is determined based on a second duration and / or the second number is determined based on a second period. The wireless device skips monitoring the second PDCCH of the second DCI format in one or more remaining time slots of the second number of time slots other than the first number of time slots.

[0329] In an exemplary embodiment, the wireless device receives one or more PDSCH configuration parameters of a BWP, wherein the one or more PDSCH configuration parameters indicate a first PDSCH resource allocation configuration list associated with a first DCI format and a second PDSCH resource allocation configuration list associated with a second DCI format.

[0330] In an exemplary embodiment, each entry of the first PDSCH resource allocation configuration list includes at least one of the following: a slot offset of a second time slot of the first PDSCH relative to a first time slot on which the wireless device receives the first DCI, a starting symbol of the first PDSCH in the second time slot, and a number of symbols of the first PDSCH in the second time slot, counted from the starting symbol. The first DCI format includes a time domain resource allocation (TDRA) field indicating an entry of the first PDSCH resource allocation configuration list, the entry indicating: a slot offset of the second time slot of the first PDSCH relative to the first time slot on which the wireless device receives the first DCI, a starting symbol of the first PDSCH in the second time slot, and a number of symbols of the first PDSCH in the second time slot, counted from the starting symbol. The wireless device receives the first TB via the PDSCH based on the slot offset, the starting symbol, and the number of symbols.

[0331] In an exemplary embodiment, each entry of the second PDSCH resource allocation configuration list includes at least one of the following: a slot offset of a second time slot of a starting PDSCH in the plurality of PDSCHs relative to a first time slot in which the wireless device receives the second DCI, a plurality of starting symbols, and a length indication, wherein each starting symbol and length indication associated with a corresponding PDSCH in the plurality of PDSCHs in the plurality of PDSCHs indicates: a starting symbol of the corresponding PDSCH in the time slot associated with the corresponding PDSCH, and a number of symbols of the corresponding PDSCH in the time slot, counted from the starting symbol. The second DCI format includes a time domain resource allocation (TDRA) field indicating an entry of the second PDSCH resource allocation configuration list, the entry indicating: a slot offset of the second time slot of the starting PDSCH relative to the first time slot in which the wireless device receives the second DCI, and a plurality of starting symbols and length indications for the plurality of PDSCHs. The wireless device receives the plurality of TBs via the plurality of PDSCHs based on the slot offset and the plurality of starting symbols and length indications for the plurality of PDSCHs.

[0332] In an exemplary embodiment, the search space is a wireless device specific search space type.The search space is a cell common search space type.

[0333] In an exemplary embodiment, the first period is shorter than the second period.The first duration is greater than the second duration.

[0334] In an exemplary embodiment, a wireless device receives one or more RRC messages including parameters for a search space on a BWP, wherein the parameters include: a period for monitoring PDCCHs in the search space, a duration for monitoring PDCCHs in the search space, and a plurality of DCI formats. The wireless device monitors PDCCHs of the plurality of DCI formats based on the period and the duration. The wireless device receives, via a PDSCH, a first DCI indicating a first TB in a first DCI format from among the plurality of DCI formats. The wireless device continues monitoring the PDCCH of the first DCI format based on the period and the duration. The wireless device receives, via a plurality of PDSCHs, a second DCI indicating a plurality of TBs in a second DCI format from among the plurality of DCI formats, each TB being associated with a corresponding PDSCH. The wireless device skips monitoring the PDCCH of the second DCI format for a number of time slots by ignoring the period and the duration, wherein the number is determined based on the total number of the plurality of PDSCHs.

[0335] In an exemplary embodiment, a wireless device receives one or more RRC messages including parameters for a search space on a BWP, wherein the parameters include a period for monitoring PDCCHs in the search space, a duration for monitoring PDCCHs in the search space, and a plurality of DCI formats. The wireless device monitors PDCCHs of the plurality of DCI formats based on the period and the duration. The wireless device receives, via a plurality of PDSCHs in a plurality of time slots, DCI in a first DCI format from among a plurality of DCI formats, indicating a plurality of TBs, each TB being associated with a corresponding PDSCH. The wireless device skips monitoring PDCCHs of the first DCI format for a number of time slots by ignoring the period and the duration, wherein the number is determined based on a total number of the plurality of PDSCHs.

Claims

1. A method for transmitting multiple physical downlink shared channels (PDSCHs), the method comprising: A radio resource control (RRC) message is received by a wireless device, including configuration parameters, the configuration parameters including: a first PDSCH time domain allocation list associated with a first downlink control information (DCI) format for scheduling a PDSCH in a time slot; and a second PDSCH time domain allocation list associated with a second DCI format for scheduling a plurality of PDSCHs in a plurality of time slots; receiving a first DCI having the second DCI format, the second DCI format indicating a first entry of a second PDSCH time domain allocation list; and A plurality of transport blocks (TBs) determined based on the first entry are received in a plurality of first time slots and via a plurality of PDSCH resources, wherein each of the plurality of TBs is associated with a corresponding hybrid automatic repeat request process.

2. The method of claim 1, further comprising: A first search space for receiving the first DCI having the second DCI format is monitored, wherein a first monitoring period of the first search space is greater than a second monitoring period of a second search space for receiving the second DCI having the first DCI format.

3. The method of claim 2, wherein the first search space is a wireless device-specific search space and the second search space is a common search space.

4. The method of claim 2, further comprising: Based on monitoring the second search space, a second DCI having the first DCI format is received, where the first DCI format includes a TDRA field, and the TDRA field indicates a second entry of the first PDSCH time domain allocation list.

5. The method of claim 4, further comprising: A second TB determined based on the second entry is received in a second time slot and via a second PDSCH resource, wherein the second TB is associated with a second hybrid automatic repeat request process.

6. The method of claim 1 , wherein receiving a plurality of TBs in a plurality of first time slots comprises: Each of the plurality of TBs is received in a corresponding time slot of the plurality of first time slots.

7. The method of claim 1 , wherein a first entry of the second PDSCH time domain allocation list indicates a plurality of PDSCH resources in the plurality of first time slots, and wherein each of the plurality of PDSCH resources in a corresponding time slot in the plurality of first time slots is associated with: timeslot offset indication; and Start symbol and length indication.

8. A method for transmitting multiple physical downlink shared channels (PDSCHs), the method comprising: A radio resource control (RRC) message including configuration parameters is transmitted by a base station to a wireless device, wherein the configuration parameters include: a first PDSCH time domain allocation list associated with a first downlink control information (DCI) format for scheduling a PDSCH in a time slot; and a second PDSCH time domain allocation list associated with a second DCI format for scheduling a plurality of PDSCHs in a plurality of time slots; transmitting a first DCI having the second DCI format, wherein the second DCI format indicates a first entry of a second PDSCH time domain allocation list; and A plurality of transport blocks (TBs) determined based on the first entry are transmitted in a plurality of first time slots and via a plurality of PDSCH resources, wherein each of the plurality of TBs is associated with a corresponding hybrid automatic repeat request process.

9. The method of claim 8, wherein the configuration parameters further cause the wireless device to monitor a first search space for receiving a first DCI having the second DCI format, wherein a first monitoring period of the first search space is greater than a second monitoring period of a second search space for receiving a second DCI having the first DCI format.

10. The method of claim 9, wherein the first search space is a wireless device-specific search space and the second search space is a common search space.

11. The method of claim 9, further comprising: A second DCI having the first DCI format is transmitted, the first DCI format including a TDRA field, the TDRA field indicating a second entry of the first PDSCH time domain allocation list.

12. The method of claim 11, further comprising: A second TB determined based on the second entry is transmitted in a second time slot and via a second PDSCH resource, wherein the second TB is associated with a second hybrid automatic repeat request process.

13. The method of claim 8, wherein transmitting the plurality of TBs in the plurality of first time slots comprises: Each of the plurality of TBs is transmitted in a corresponding time slot of the plurality of first time slots.

14. An apparatus for transmitting multiple physical downlink shared channels (PDSCHs), the apparatus comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 13.

15. A computer-readable medium comprising instructions which, when executed by one or more processors of a device, cause the device to perform the method of any one of claims 1 to 13.

Images