Method, device and medium for reliable transmission of multicast and broadcast services

Abstract

A wireless device receives group common downlink control information (DCI) that schedules first data of a transport block via a first search space (SS) in common frequency resources of a bandwidth portion (BWP) and associated with a multicast transmission. The wireless device receives, via a second SS in the BWP, a unicast DCI that schedules second data. The second data is determined to be retransmission of the transport block based on the first process index of the group common DCI being the same as the second process index of the unicast DCI.

Description

[0001] Divisional application

[0002] This application is a divisional application of the Chinese invention patent application with application number 2021800849365, filed on October 21, 2021, and entitled “Reliable transmission methods, devices and media for multicast and broadcast services”.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims the benefit of U.S. Provisional Application No. 63 / 094,854, filed on October 21, 2020, the entire contents of which are hereby incorporated by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0009] Figure 4A Shows the flow Figure 2A Figure 2 shows an exemplary downlink data flow of the NR user plane protocol stack.

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

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

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

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

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

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

[0016] Fig. 10A Three carrier aggregation configurations with two component carriers are shown.

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

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

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

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

[0021] Fig.13A , Fig. 13B and Fig. 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.

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

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

[0024] Fig.15 An example of a wireless device in communication with a base station is shown.

[0025] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Exemplary structures for uplink and downlink transmissions are shown.

[0026] Fig.17A , Fig. 17B and Fig. 17C An example of a MAC subheader according to some embodiments is shown.

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

[0028] Fig.18BAn example of a UL MAC PDU is shown according to some embodiments.

[0029] Fig.19 An exemplary LCID for a downlink is shown according to some embodiments.

[0030] Fig. 20 Example LCIDs for uplinks are shown according to some embodiments.

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

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

[0033] Fig.23A , Fig. 23B and Fig.23C Examples of configuration parameters for a MIB according to some embodiments are shown.

[0034] Fig.24 An example of RRC configuration for SIB1 messages according to some embodiments is shown.

[0035] Fig.25 An example of RRC configuration for a downlink BWP according to some embodiments is shown.

[0036] Fig.26 An example of RRC configuration of a search space according to some embodiments is shown.

[0037] Fig.27A and Fig.27B Examples of unicast, broadcast, and multicast transmissions are shown according to some embodiments.

[0038] Fig.28A and Fig.28B An example of MBS resource allocation according to some embodiments is shown.

[0039] Fig.29 An example of HARQ process management in a HARQ entity according to some embodiments is shown.

[0040] Fig.30 An example of HARQ retransmission according to some embodiments is shown.

[0041] Fig.31A and Fig.31B Examples of multicast retransmission of an MBS TB and unicast retransmission of an MBS TB according to some embodiments are shown.

[0042] Fig.32 is a flow chart illustrating an example of HARQ retransmission of an MBS TB according to some embodiments.

[0043] Fig.33 An example of HARQ process management according to some embodiments is shown.

[0044] Fig.34 An example of HARQ retransmissions for an MBS TB according to some embodiments is shown.

[0045] Fig.35 is a flow chart illustrating an example of HARQ retransmission of an MBS TB according to some embodiments.

[0046] Fig.36 is a flow chart illustrating an example of HARQ retransmission of an MBS TB according to some embodiments. DETAILED DESCRIPTION

[0047] 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. Restrictions, features and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided only for illustrative purposes. The disclosed architecture is flexible and configurable enough so 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.

[0048] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various exemplary embodiments may be applied. Therefore, exemplary embodiments that selectively implement the disclosed protocol may be implemented.

[0049] 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 category 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 a given capability 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.

[0050] In the present 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 the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of a 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.

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

[0052] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may 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 state or a non-operational state.

[0053] 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 a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

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

[0055] Many elements described in the disclosed embodiments can be implemented as modules.Modules are defined here as elements that perform defined functions and have defined interfaces to other elements.Modules described in the present disclosure can be implemented by hardware, software, firmware, wetware (for example, hardware with biological elements) in combination with hardware, or a combination thereof, all of which can be equivalent in behavior.For example, a module can be implemented as a software routine written in a computer language, which 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 LabVIEWMathScript).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, C++, etc. 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 less functional internal hardware blocks on the programmable device. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0056] 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, the mobile communication network 100 includes a core network (CN) 102 , a radio access network (RAN) 104 , and wireless devices 106 .

[0057] The CN 102 may provide an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-carrier DN, 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.

[0058] The RAN 104 may connect the CN 102 to the wireless device 106 via radio communications over an air interface. As part of the radio communications, the RAN 104 may 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 may be separated from uplink transmissions using frequency division duplex (FDD), time division duplex (TDD), and / or some combination of the two duplex technologies.

[0059] The term "wireless device" may be used throughout this disclosure to mean and encompass any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device may 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, a car, 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.

[0060] The RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: 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 repeater 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).

[0061] 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 the 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. The cells of the base stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0062] 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 unit coupled to the RRH may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be centralized in a baseband processing unit pool 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 eliminate noise before amplifying and rebroadcasting the radio signal.

[0063] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, a small cell base station may be used to provide a small coverage area, such as a coverage area that overlaps with a relatively large coverage area provided by a macrocell base station. Small coverage areas may be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0064] The Third Generation Partnership Project (3GPP) was established in 1998 to Figure 1A 3GPP provides global specification standardization for mobile communication networks similar to the mobile communication network 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). 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 may be applicable to the RAN of other mobile communication networks, such as Figure 1A The RAN 104 in 5G networks, the RAN of early 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.

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

[0066] 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 UE 156. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CN of the 3GPP 4G network, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of 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).

[0067] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1BThey are shown as one component AMF / UPF 158 in FIG. 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 for supporting multi-host 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.

[0068] 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 functions operating between the CN and the UE, and AS may refer to functions operating between the UE and the RAN.

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

[0070] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via radio communications over an air interface. The NG-RAN 154 may include: one or more gNBs, shown as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, shown as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). The gNB 160 and ng-eNB 162 may be more generally referred to as base stations. The gNB 160 and ng-eNB 162 may include one or more groups of antennas for communicating with the UE 156 over an air interface. For example, one or more gNBs in the gNB 160 and / or one or more ng-eNBs in the ng-eNB 162 may include three groups of 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.

[0071] 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 a direct physical connection and / or an indirect connection 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. 1 , gNB 160A may be connected to UE 156A via a Uu interface. NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface may be composed of Figure 1B The network elements in a network are used to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data that the user is interested in. The control plane may process signaling messages that the network elements are interested in.

[0072] 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, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of a NG user plane (NG-U) interface. The NG-U interface may provide 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 by means of a 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.

[0073] The gNB 160 may provide NR user plane and control plane protocol terminations to the UE 156 via a Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations to the UE 156A via a Uu interface associated with the first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations 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 may provide E-UTRA user plane and control plane protocol terminations to the UE 156B via a Uu interface associated with the second protocol stack.

[0074] 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 a gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

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

[0076] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface 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 UE156A and gNB 160A shown in are the same or similar.

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

[0078] 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 of , SDAPs 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and 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 delay, 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 the QoS flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the 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 / demapping between QoS flows and data radio bearers.

[0079] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0080] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. 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). A split bearer is a split bearer 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.

[0081] RLC 213 and 223 can perform segmentation, retransmission through 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 based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

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

[0083] 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 , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

[0084] Figure 4A An exemplary downlink data flow through the NR user plane protocol stack is shown. Figure 4A 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 is shown. 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 .

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

[0086] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs 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 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, 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.

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

[0088] 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 reports and power headroom reports; 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 for a MAC SDU may be present before 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.

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

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

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

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

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

[0094] - a dedicated control channel (DCCH) used to carry control messages to / from a specific UE to configure the UE; and

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

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

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

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

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

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

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

[0102] 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 of one or more transport channels. The PHY may generate control information to support low-level operation of the PHY and provide control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

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

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

[0105] - 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;

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

[0107] - 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

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

[0109] Similar to the physical control channel, the physical layer generates physical signals to support the lower-level operations of the physical layer. Figure 5A and Figure 5B As shown in , the physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS) and phase tracking reference signal (PT-RS). These physical layer signals will be described in more detail below.

[0110] Figure 2B An exemplary NR control plane protocol stack is shown. Figure 2B As shown in , 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.

[0111] The NAS protocols 217 and 237 may provide control plane functions 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 functions between the UE 210 and the AMF 230 via signaling messages referred to 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 functions such as authentication, security, connection setup, mobility management, and session management.

[0112] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220, or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The 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 AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of an RRC connection between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of 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.

[0113] 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. 1 and any other wireless device described in the present disclosure may be the same or similar. Figure 6 As shown in , the 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).

[0114] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in the RAN 104 depicted in FIG. Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG. Figure 2A and Figure 2BgNB220 depicted in ; or 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 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., involving data radio bearers, signaling radio bearers, logical channels, QoS flows and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP and / or SDAP layer configuration information. When in RRC connection 602, the mobility of the UE 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 .

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

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

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

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

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

[0120] The base station storing 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 during the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

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

[0122] In NR, physical signals and physical channels (about Figure 5A and Figure 5B Discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through 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 are in the frequency domain and used as input to the 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 a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the peak to average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbol at the receiver to restore the data mapped to the source symbol.

[0123] 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 be repeated with a period of 1024 frames. As shown, a NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. A subframe may be divided into time slots that include, for example, 14 OFDM symbols per time slot.

[0124] The duration of a time slot may depend on the parameter set of the OFDM symbol used for the time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mm-wave 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.

[0125] 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 each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in Figure 1). Subframes in NR can be used as a time reference independent of the parameter set, while slots 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 to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

[0126] Figure 8 An exemplary configuration of a time slot in the time and frequency domain 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, such as Figure 8 As shown in Figure 1. RB spans twelve consecutive REs in the frequency domain, as Figure 8 As shown. The NR carrier can be limited to a width of 275RB or 275×12=3300 subcarriers. If this restriction is used, the NR carrier can be limited to 50MHz, 100MHz, 200MHz and 400MHz for subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively, where the 400MHz bandwidth can be set based on the 400MHz bandwidth limit per carrier.

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

[0128] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). 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 may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0129] NR defines bandwidth parts (BWPs) to support UEs that cannot receive the full carrier bandwidth and supports bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. The UE may 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 the serving cell may be active. The one or more BWPs may be referred to as the active BWP of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0130] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a 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.

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

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

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

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

[0135] 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., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

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

[0137] Downlink and uplink BWP switching can be performed independently in paired spectrum (where BWP switching refers to switching from a currently active BWP to a 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 a BWP inactivity timer, and / or initiation of random access.

[0138] Fig. 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. A UE configured with the three BWPs can switch from one BWP to another at a switching point. Fig. 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. Fig. 9 904. In the example of FIG. 906, 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 an 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 an 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 an 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 an active BWP.

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

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

[0141] Fig. 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 are located directly adjacent to each other in the frequency band. In the intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (Band A) and are separated by a gap in the frequency band. In the inter-band configuration 1006, the two CCs are located in the frequency bands (Band A and Band B).

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

[0143] When CA is used, one of the aggregated cells for the UE may be referred to as a primary cell (PCell). The PCell may be a 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 via 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).

[0144] 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 MAC CE may be used to activate and deactivate the configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in 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).

[0145] 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. Uplink control information for aggregated cells (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.

[0146] Fig. 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 include one or more downlink CCs, respectively. Fig. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. 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 the example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050 , a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061 , overload can be prevented.

[0147] 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 a downlink carrier and / or an uplink carrier of a 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.

[0148] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an 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 the transport block can be mapped to a serving cell.

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

[0150] Fig.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 Fig.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 with a duration of 5 ms). It should be understood that Fig.11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst position within a frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; a parameter set or subcarrier spacing for 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.

[0151] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Fig.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.

[0152] 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 the PSS is not 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, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

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

[0154] The PBCH may use QPSK modulation and may use 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 contribute to the time synchronization of the UE with 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 pointing.

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

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

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

[0158] 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 CSI-RSs of the same / similar CSI-RS. The UE may measure the one or more CSI-RSs. 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-RSs. 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.

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

[0160] The base station can configure the UE to report CSI 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.

[0161] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbol for 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 employ the same OFDM symbol for 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.

[0162] 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 modes for data demodulation. At least one downlink DMRS configuration can support a frontload DMRS mode. 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 4 orthogonal downlink DMRS ports per UE. The radio network may (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 may be the same or different. The base station may transmit the downlink DMRS and the corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

[0163] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a 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 throughout a set of PRBs. The set of PRBs may be represented as a precoding resource block group (PRG).

[0164] 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. The higher layers may configure up to 3 DMRS for the PDSCH.

[0165] The downlink PT-RS may be transmitted by a base station and used by a UE for phase noise compensation. Whether a downlink PT-RS exists may depend on an RRC configuration. The presence and / or type of a downlink PT-RS may be configured based on a UE-specific configuration using a combination of RRC signaling and / or an association with one or more parameters for other purposes (e.g., a modulation and coding scheme (MCS)) that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters including at least an MCS. The NR network 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 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 limited 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.

[0166] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently 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 front-load DMRS mode. The front-load 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 front-load DMRS symbols for the PUSCH and / or PUCCH, and the UE may use the front-load DMRS symbol to schedule a single-symbol DMRS and / or a dual-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 positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

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

[0168] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. 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 limited to the scheduled time / frequency duration of the UE.

[0169] The UE may transmit an SRS to a 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 a higher layer parameter indicates beam management, the SRS resources in the SRS resource set 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 transmission of PUSCH and corresponding uplink DMRS.

[0170] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: 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 non-periodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resources; the start OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0171] The antenna ports are defined such that the channel through which a symbol on the antenna port is communicated can be inferred from the channel through 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 used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port (e.g., fading gain, multipath delay, etc.). If one or more large-scale properties of the channel through which the first symbol on the first antenna port is communicated can be inferred from the channel through 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.

[0172] Channels using beamforming require beam management. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may 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 may perform a downlink beam measurement procedure.

[0173] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 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-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through 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.

[0174] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are illustrated in FIG. 1 , 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 so that the beam for the UE uses symbols from beams of other UEs.

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

[0176] In the beam management procedure, the UE may assess (e.g., measure) the channel quality of one or more beam pair links, beam pair links including a transmit beam transmitted by a base station, and a 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, the one or more beam pair quality parameters including, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI) and / or rank indicator (RI).

[0177] Fig. 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 a TRP (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the 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.

[0178] Fig. 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 beams, 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). Procedure U2 can be used to enable a base station to adjust its Rx beam when the UE uses a fixed Tx 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.

[0179] The UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., 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.).

[0180] The UE may measure the quality of a beam-to-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-to-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-RS 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 a transmission to the UE via the RS resource are similar or identical to the channel characteristics from a transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

[0181] 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 a 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.

[0182] Fig.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. Fig.13AThe procedure shown includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

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

[0184] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that can 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.

[0185] 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 Msg3 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). There may be one or more power offsets 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 SSB and 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., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplementary uplink (SUL) carrier).

[0186] 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). The 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 above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by the RRC message, the UE may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0187] 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) for selecting a preamble and for determining 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.

[0188] If no response is received after the preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power 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 the 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 is not successfully completed.

[0189] 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 is received by the base station. Msg 2 1312 may include a time alignment command that may be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity that the UE uses 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 that initiate 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-RNTIs may be as follows:

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

[0191] The UE may transmit Msg3 1313 in response to successfully receiving Msg 2 1312 (eg, using the resources identified in Msg 2 1312). Msg 3 1313 may be used, for example, Fig.13A Contention resolution in a contention-based random access procedure as shown in . In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) 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 Msg2 1312 and / or any other suitable identifier).

[0192] 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 address the UE on the PDCCH using the C-RNTI. If a unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in an 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 is successful and / or the UE may determine that the random access procedure is successfully completed.

[0193] 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 an uplink carrier. For example, a 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., Msg1 1311 and / or Msg 3 1313) of 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).

[0194] Fig. 13B The two-step contention-free random access procedure is shown. Fig.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. Fig. 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 Fig.13A As shown in Msg 1 1311 and Msg 2 1312. Fig.13A and Fig. 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 .

[0195] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 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.

[0196] 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. Fig. 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission is addressed to the C-RNTI, the UE may determine that the random access procedure is successfully completed. For example, if the UE receives a RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a preamble identifier, the UE may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of a confirmation of the SI request.

[0197] Fig. 13C Another two-step random access procedure is shown. Fig.13A and Fig. 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. Fig. 13C The procedure shown includes the transmission of two messages: Msg A 1331 and Msg B 1332.

[0198] 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 Fig.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 that of Msg 3 1313 shown in FIG. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg 4 1314 shown is similar and / or identical.

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

[0200] The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in the 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 the 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 the Msg B 1332.

[0201] The transmission 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 as a 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 a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the following conditions exist: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., transmission block 1342).

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

[0203] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transport format; time slot format information; preemption indication; power control command; 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.

[0204] 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 of the UE (or an identifier of 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).

[0205] 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 hexadecimal "FFFE". 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 hexadecimal "FFFF". 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 Fig.13AThe other RNTIs configured by the base station to the UE may include: a configured scheduling RNTI (CS-RNTI), a transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), a transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmission power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0206] 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 of 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 of 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 of 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 of 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 transmission power control (TPC) command for PUCCH or PUSCH. DCI formats 2_3 may be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0207] After scrambling the DCI with the RNTI, the base station may process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station may 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 may transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. 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 may be based on the mapping of CCEs and REGs (e.g., CCE to REG mapping).

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

[0209] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE to REG mapping can be an interlaced mapping (e.g., for the purpose of providing frequency diversity) or a non-interlaced 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 antenna port quasi-co-location (QCL) parameters. The antenna port QCL parameters can indicate the QCL information of the demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0210] 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 an association between a search space set and a 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 for each aggregation level; the PDCCH monitoring period and the PDCCH monitoring type; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set 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 UE's identity (e.g., C-RNTI).

[0211] like Fig. 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., interlaced or non-interlaced 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 according to 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 according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH 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, time slot format indications, downlink preemption, etc.).

[0212] 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) confirmation for the received DL-SCH transport block. The UE may transmit the HARQ confirmation 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 transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ confirmation (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 PUCCH using one of several PUCCH formats.

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

[0214] 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".

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

[0216] Fig.15 An example of a wireless device 1502 communicating 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. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same Fig.15 Configurations the same or similar to those shown.

[0217] The base station 1504 may connect the wireless device 1502 to a core network (not shown) by radio communication via 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 may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0218] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process 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 following: Figure 2B RRC layer.

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

[0220] 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 functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For reception 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, etc.

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

[0222] 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 codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.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.

[0223] 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, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0224] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touch pad, 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 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from the 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 the GPS chipset 1517 and the GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide the geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0225] Fig.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 a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; 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 Fig.16A Generate 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.

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

[0227] Fig. 16C An exemplary structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0228] Fig.16D Another exemplary structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

[0229] The wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters of multiple cells (e.g., primary cells, secondary cells) from a base station. 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, and the like. 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.

[0230] Once started, a timer can start running and continue running until it stops or until it expires. If the timer is not running, it can be started, or if it is running, it can be restarted. A timer can be associated with a value (e.g., a timer can start or restart from a certain value, or can start from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer stops or expires (e.g., due to BWP switching). A timer can be used for a time period / window of a measurement process. When the specification refers to implementations and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing the timer can be used for a time period / window of a measurement procedure. For example, a random access response window timer can be used to measure a 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 measurement process of the time window can be restarted. Other exemplary embodiments can be provided to restart the measurement of the time window.

[0231] 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, wherein 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 lines are read. In an example, the bit order of the parameter fields within the MAC PDU is represented by the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0232] In an example, the 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. The MAC CE may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). The 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 the reserved bit in the DL MAC PDU.

[0233] 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: only a MAC subheader (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.

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

[0235] Fig.17A An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Fig.17A In an exemplary MAC subheader of , the LCID field may be six bits in length and the L field may be eight bits in length. Fig. 17B An example of a MAC subheader having an R field, an F field, an LCID field, and an L field is shown. Fig. 17B In the exemplary MAC subheader shown in , the length of the LCID field may be six bits, and the length of the L field may be sixteen bits. When the MAC subheader corresponds to a fixed-size MAC CE or padding, the MAC subheader may include: an R field having a length of two bits and an LCID field having a length of multiple bits. Fig. 17C An example of a MAC subheader having an R field and an LCID field is shown. Fig. 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.

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

[0237] In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device. Fig.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 a MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0238] 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. Fig. 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, the 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.

[0239] 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 the techniques of CA 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 a primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device may have an RRC connection with a network. During RRC connection establishment / reestablishment switching, the cell that provides NAS mobility information may be a serving cell. During the RRC connection establishment / switching procedure, the cell that provides security input may be a serving cell. In an example, a serving cell may represent a PCell. In an example, a base station may transmit one or more messages including configuration parameters of multiple one or more SCells to a wireless device depending on the capabilities of the wireless device.

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

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

[0242] 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 (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in a time slot 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.

[0243] 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, when the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may deactivate the activated SCell. In response to deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In an example, in response to deactivating the activated SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink grants of 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.

[0244] When the 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 a downlink assignment, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when at least one second PDCCH on a serving cell (e.g., a PCell or SCell configured with a PUCCH, i.e., a PUCCH SCell) that schedules the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when the SCell is deactivated, if there is an ongoing random access procedure on the SCell, the wireless device may abort the ongoing random access procedure on the SCell.

[0245] Fig.21A An example of an octet SCell activation / deactivation MAC CE is shown. Fig.19 The first MAC PDU subheader of the SCell activation / deactivation MAC CE (shown as '111010' in FIG. 1 ) may identify an octet SCell activation / deactivation MAC CE. The octet SCell activation / deactivation MAC CE may have a fixed size. The octet SCell activation / deactivation MAC CE may include a single octet. The single octet may include a first number of C fields (e.g., seven) and a second number of R fields (e.g., one). Fig. 21B An example of a four-octet SCell activation / deactivation MAC CE is shown. Fig.19 The second MAC PDU subheader of the MAC PDU (e.g., '111001' shown in ) 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).

[0246] exist Fig.21A and / or Fig. 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. i When the field is set to one, the SCell with SCell index i can be activated. i When the C 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. Fig.21A and Fig. 21B In the , the R field can indicate a reserved bit. The R field can be set to zero.

[0247] 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 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 a paired spectrum (e.g., FDD), the base station and / or the wireless device may switch the DL BWP and the UL BWP independently. In an unpaired spectrum (e.g., TDD), the base station and / or the wireless device may switch the DLBWP and the UL BWP simultaneously.

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

[0249] 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 an active BWP at any point in time. In an example, BWP switching for a serving cell may be used to simultaneously activate an inactive BWP and deactivate an active BWP. In an example, BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. In an example, BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). In an example, BWP switching may be controlled by a MAC entity in response to initiating a random access procedure. When adding a serving cell (e.g., SpCell) or activating an SCell, a BWP may initially be active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP for a serving cell may be indicated by 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 to both UL and DL.

[0250] Fig. 22An example of BWP switching on a cell (e.g., a PCell or an SCell) is shown. In the 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., RRCRestablishment); and / or an RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP may be configured as 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 an nth time slot. The wireless device may start a cell deactivation timer (e.g., sCellDeactivationTimer) and start a CSI-related action for the cell, and / or start a CSI-related action for the first active BWP of the cell. The wireless device may start monitoring the PDCCH on BWP 1 in response to activating the cell.

[0251] 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 start of the time slot. When the BWP inactivity timer expires, the wireless device may switch back to the default BWP (e.g., BWP 0) as the active BWP in the sth time slot. When the sCellDeactivationTimer expires, the wireless device may deactivate the cell and / or stop the BWP inactivity timer.

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

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

[0254] 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 this 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 a 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 a configured UL BWP set.

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

[0256] In an example, if the wireless device is configured for a secondary cell having 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.

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

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

[0259] In an example, the wireless device determines a PDCCH monitoring opportunity on an active DL BWP based on one or more PDCCH configuration parameters, including: a PDCCH monitoring period, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a time slot. For a search space set (SSs), the wireless device determines that a PDCCH monitoring opportunity exists in a numbered In the time slot numbered n f if 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 is the PDCCH monitoring period indicated in the PDCCH configuration parameter. s PDCCH candidates in the continuous time slot monitoring search space set, from time slot Start, and for the next k s -T s The PDCCH candidates of the search space set s are not monitored in consecutive time slots. In the example, the USS at CCE aggregation level L∈{1,2,4,8,16} is defined by the PDCCH candidate set of CCE aggregation level L.

[0260] In the example, the wireless device is associated with CORESET p for the search space set s, and the CCE index L of the aggregation level corresponds to the PDCCH candidate m s,nCI Search space set in time slot The active DL BWPm for the serving cell corresponding to the carrier indicator field value CI As in, For any CSS, For USS Y p,-1 =n RNTI ≠0,A p =39827 for p mod 3 = 0, A p =39829 for p mod 3 = 1, A p =39839 for p mod 3 = 2, and D = 65537; i = 0, ..., L-1; N CCE,p is the number of CCEs, numbered from 0 to N CCE,p -1, p in CORESET; n CI is the Carrier Indicator field value if the wireless device is configured with the Carrier Indicator field by the CrossCarrierSchedulingConfig of the serving cell on which it monitors the PDCCH; otherwise, for any CSS included, n CI =0; in is the number of PDCCH candidates that the wireless device is configured to monitor for aggregation level L of the search space set s for the serving cell n corresponding to the following CI ; For any CSS, For USS, is the maximum value Overall configuration CI The value of the CCE aggregation level L, the search space set s; and the RNTI value n for the following RNTI It is C-RNTI.

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

[0262] Fig.23A An example of configuration parameters of a master information block (MIB) of a cell (e.g., PCell) is shown. In the example, based on receiving a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS), the 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 indication (subCarrierSpacingCommon), a frequency domain offset in 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 of the CORESET and SS of the PDCCH including the common CORESET (pdcch-ConfigSIB1), a common search space, and necessary PDCCH parameters.

[0263] 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. Fig. 23B An example of the configuration of CORESET#0 is shown. Fig. 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.

[0264] In an example, pdcch-ConfigSIB1 may include a second parameter (e.g., searchSpaceZero) common search space with 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. Fig.23C An example of the configuration of SS#0 is shown. Fig.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.

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

[0266] Fig.24 An example of RRC configuration parameters of 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 an example, a base station may transmit one or more SIB information to a wireless device (or multiple wireless devices). Fig.24As shown, the parameters of the one or more SIB information may include: one or more parameters of 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: a common downlink parameter of the serving cell (e.g., represented by DownlinkConfigCommonSIB IE), a common uplink parameter of the serving cell (e.g., represented by UplinkConfigCommonSIB IE), and other parameters.

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

[0268] 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 the necessary alignment with corresponding parameters of other wireless devices. 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.

[0269] Fig.25An example of RRC configuration parameters (e.g., BWP-DownlinkCommon IE) in a downlink BWP of a serving cell is shown. The base station may transmit one or more configuration parameters of a downlink BWP (e.g., an initial downlink BWP) of a serving cell to a wireless device (or multiple wireless devices). Fig.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 the pdcch-ConfigCommon IE), one or more cell-specific parameters of the PDSCH of the BWP (for example, represented by the 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. Fig.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 a list of additional common search spaces (e.g., represented by commonSearchSpaceList). The parameters of the search space may be based on Fig.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 a random access procedure (e.g., ra-SearchSpace), a search space for SIB1 messages (e.g., searchSpaceSIB1), a common search space #0 (e.g., searchSpaceZero), and one or more other search spaces.

[0270] like Fig.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 indicating an index of a 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, Fig.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 multiple bits (e.g., 45 bits) indicates frequency domain resources, each bit of the indication corresponds to a group of 6 RBs (resource block groups or RBGs in this specification), and 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 fully contained in the BWP in which the CORESET is configured are set to zero.

[0271] Fig.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 (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., in a radio frame) and a time slot offset (e.g., related to the start of a radio frame) for PDCCH monitoring. The monitoring symbol indication may indicate which symbol(s) of a time slot the wireless device may monitor for PDCCH on the SS. The control resource set ID may identify a control resource set on which the SS may be located.

[0272] In an embodiment, a base station may transmit or a wireless device may receive TBs scheduled in a unicast transmission, a broadcast transmission, a multicast transmission, or a combination thereof. Fig.27A and Fig.27B Examples of unicast transmission, broadcast transmission, and multicast transmission are shown.

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

[0274] like Fig.27AAs shown, a wireless device may receive a multicast TB (or groupcast TB) of a multicast service (e.g., MBS) from a base station, which may be received by a group of wireless devices (e.g., WD2, WD3, WD4, etc.) within the coverage of the base station. In order to receive the multicast TB, the group of wireless devices may be allocated / configured with a group-specific RNTI (e.g., G-RNTI or SC-RNTI, or MBS-RNTI). Based on the configured group-specific RNTI, the wireless device group may monitor the PDCCH to receive a DCI with a CRC scrambled by the group-specific RNTI, which schedules the multicast TB. In the example, a wireless device (e.g., WD1) that is not configured with a group-specific RNTI may not receive the multicast TB. In the example, the MBS may carry messages for applications, including at least one of the following: V2X, public safety, live video (e.g., concerts or sports), IOT software updates, industry applications, etc. An MBS that carries one type of application data may be defined as an MBS session. Different MBS sessions may be used for different applications. A wireless device interested in an MBS provided by a base station may indicate to the base station that the wireless device is interested in the MBS service. The base station may accordingly transmit to the wireless device an MBS configuration parameter including an RNTI dedicated to receiving a DCI that schedules an MBS TB. By assigning a dedicated RNTI to a wireless device receiving an MBS, the base station may know which wireless device or how many wireless devices have subscribed to the MBS. MBS is different from a broadcast message, in which the base station does not know which wireless device or how many wireless devices are receiving the broadcast message. In an example, a network operator may determine an MBS transmission strategy or a pricing strategy based on the number of subscribers to the MBS by using multicast / groupcast scheduling.

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

[0276] In an embodiment, a base station may transmit an MBS TB to a group of wireless devices via a BWP of a plurality of BWPs of a cell.

[0277] Fig.28A and Fig.28B An example of MBS configuration when a plurality of BWPs are configured in a cell is shown.

[0278] like Fig.28A As shown, a BWP for transmitting an MBS TB (e.g., which may be referred to as an MBS BWP in this specification) may be configured separately and / or independently from a BWP for transmitting a unicast TB and / or a broadcast TB (e.g., which may be referred to as a unicast BWP in this specification). The MBS BWP in this specification may be defined as a BWP of a cell, on which an MBS PDCCH / PDSCH may be transmitted. The unicast BWP in this specification may be defined as a BWP of a cell, on which a unicast PDCCH / PDSCH (and / or a broadcast PDCCH / PDSCH) may be transmitted.

[0279] In an example, a base station may transmit one or more RRC messages including configuration parameters of a cell to a wireless device, the cell including multiple BWPs. One or more RRC messages may indicate that a first set of multiple BWPs is dedicated as a unicast BWP (e.g., BWP n, BWP m, etc., for unicast PDCCH / PDSCH transmission, or broadcast system information transmission, or broadcast paging message transmission). In an example, one or more RRC messages may indicate that a second set of multiple BWPs is dedicated as an MBS BWP (e.g., BWPx, BWP y, etc., for MBS PDCCH / PDSCH transmission). In an embodiment, different MBSs (e.g., V2X, public safety, live video, IOT software updates, industry applications, etc.) targeting different groups of wireless devices may be configured on different BWPs. MBSBWP may be used to transmit different MBS TBs associated with different MBS configurations (e.g., V2X, public safety, live video, IOT software updates, industry applications, etc.). In an example, configuring a separate BWP for MBS from a unicast BWP may improve system throughput and reduce scheduling restrictions / impacts on unicast PDSCH scheduling. In an embodiment, to support a separate BWP configured with MBS, a wireless device may be required to support multiple active BWPs in a cell.

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

[0281] In an embodiment, different MBSs targeting different groups of wireless devices may be configured on different sets of frequency resource blocks within a unicast BWP. Fig.28B As shown, frequency resource blocks for MBS can be allocated on different unicast BWPs. In an example, configuring frequency resources for MBS within a unicast BWP can simplify the implementation of the wireless device and reduce the power consumption of the wireless device. In an example, by supporting the configuration of frequency resources for MBS within a unicast BWP, the wireless device can be required to support a single active BWP in a cell.

[0282] In an example, a wireless device may receive a downlink assignment on a PDCCH (e.g., in a DCI) indicating the presence of a transmission on a downlink shared channel (DL-SCH) of a MAC entity of the wireless device and providing HARQ information. The HARQ information may include, among other things, a new data indicator (NDI), a transport block size (TBS), a redundancy version (RV), and a HARQ process ID. The MAC entity of the wireless device may be configured with a wireless device-specific identifier (e.g., a C-RNTI, a TC-RNTI, or a CS-RNTI). The MAC entity of the wireless device may monitor the PDCCH for PDCCH timing and cells.

[0283] In an embodiment, if a downlink assignment (for PDCCH opportunity and cell) has been received on the PDCCH of the C-RNTI / TC-RNTI of the MAC entity, and if this is the first downlink assignment for the TC-RNTI, the MAC entity can determine that the NDI (bit) has been switched. If a downlink assignment has been received on the PDCCH of the C-RNTI / TC-RNTI of the MAC entity, the downlink assignment is for the C-RNTI of the MAC entity, and the previous downlink assignment indicated to the HARQ entity of the same HARQ process is a downlink assignment received for the CS-RNTI of the MAC entity or a configured downlink assignment, the MAC entity can determine that the NDI has been switched, regardless of the value of the NDI. Based on the determined NDI, the MAC entity can indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity of the wireless device of the cell.

[0284] In an embodiment, if the wireless device receives a downlink assignment on the PDCCH for the CS-RNTI of the MAC entity for a PDCCH opportunity and for a cell, the MAC entity may determine that the NDI (based on the downlink assignment) of the corresponding HARQ process has not been switched if the NDI (based on the downlink assignment) in the received HARQ information is 1. The wireless device may indicate the presence of the downlink assignment for the cell and deliver the associated HARQ information to the HARQ entity associated with the cell.

[0285] In an embodiment, if the wireless device receives a downlink assignment on the PDCCH for the CS-RNTI of the MAC entity for a PDCCH opportunity and for a cell, then if the NDI (based on the downlink assignment) in the received HARQ information is 0, then the MAC entity may perform activation associated with SPS activation / deactivation.

[0286] In an implementation scheme, the wireless device may be configured with a configured downlink assignment on a cell. The wireless device may activate the configured downlink assignment based on the CS-RNTI of the MAC entity. Based on the configured downlink assignment being configured and activated, if the PDSCH duration of the configured downlink assignment (referred to as a semi-persistent downlink assignment, or SPS in this specification) does not overlap with the PDSCH duration of the downlink assignment received on the cell's PDCCH (referred to as a dynamic downlink assignment in this specification), the MAC entity of the wireless device may instruct the physical layer to receive the TB on the DL-SCH during the PDSCH duration according to the configured downlink assignment and deliver it to the HARQ entity associated with the cell. The MAC entity may set the HARQ process ID to the HARQ process ID associated with the PDSCH duration. The MAC entity may determine that the NDI bit of the corresponding HARQ process has been switched. The MAC entity may indicate the presence of the configured downlink assignment and deliver the stored HARQ information to the HARQ entity.

[0287] In an embodiment, for a downlink assignment without a configuration of a higher layer HARQ process ID offset value (e.g., harq-ProcID-Offset), the wireless device may derive the HARQ process ID associated with the time slot where the DL transmission starts based on the following equation: HARQ Process ID = [floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))] modulo nrofHARQ-Processes. CURRENT_slot = [(SFN×numberOfSlotsPerFrame)+time slot number in a frame] and numberOfSlotsPerFrame refers to the number of consecutive time slots per frame. SFN may be the system frame number of the time slot.

[0288] In an embodiment, for a configured downlink assignment with a higher layer HARQ process ID offset value (e.g., harq-ProcID-Offset), the wireless device may derive the HARQ process ID associated with the time slot where the DL transmission starts based on the following equation: HARQ Process ID = [floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))] modulo nrofHARQ-Processes+harq-ProcID-Offset. CURRENT_slot = [(SFN×numberOfSlotsPerFrame)+time slot number in a frame] and numberOfSlotsPerFrame refers to the number of consecutive time slots per frame. SFN may be the system frame number of the time slot.

[0289] When the MAC entity needs to receive BCCH, if a downlink assignment for the PDCCH opportunity has been received on the PDCCH of the SI-RNTI, the MAC entity can indicate the downlink assignment and redundant version of the dedicated broadcast HARQ process to the HARQ entity based on the scheduling information from the RRC.

[0290] The MAC entity of the wireless device may include a HARQ entity for each serving cell. The HARQ entity may maintain multiple parallel HARQ processes. The HARQ entity may direct the HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ process.

[0291] When the physical layer is not configured for downlink spatial multiplexing, a HARQ process can support one TB. When the physical layer is configured for downlink spatial multiplexing, a HARQ process can support one or two TBs. A HARQ process can be associated with a HARQ process identifier (ID). A dedicated broadcast HARQ process is used for broadcast logical channel (BCCH) transmissions.

[0292] In response to a downlink assignment being indicated, the MAC entity of the wireless device may allocate the TBs and associated HARQ information received from the physical layer of the wireless device to the HARQ process indicated by the associated HARQ information (e.g., NDI, TBS, RV, and HARQ process ID). The MAC entity may allocate the received TBs to the broadcast HARQ process in response to a downlink assignment indicated for the broadcast HARQ process.

[0293] Fig.29 An example of a HARQ entity configured with multiple HARQ processes according to some embodiments is shown. Fig.29As shown, the HARQ entity may include multiple parallel HARQ processes (e.g., process #m, process #n, etc.). Process #m may be identified by a first HARQ process identifier (e.g., m). Process #n may be identified by a second HARQ process identifier (e.g., n). In an example, when receiving downlink data from a base station, the wireless device may process TB 1 in process #m. The wireless device may process TB 2 in process #n. In response to TB 1 not being successfully decoded by the wireless device, the wireless device may store the received data of TB 1 in a soft buffer of process #m. The wireless device may transmit a negative acknowledgement (NACK) of TB 1 to the base station. In response to the NACK, the base station may retransmit TB 1. The wireless device may attempt to decode TB 1 based on the data of TB 1 stored in the soft buffer and the data received in the retransmission of TB 1. In an exemplary embodiment, in response to TB 2 being successfully decoded, the wireless device may transmit a positive acknowledgement (ACK) of TB 2 to the base station. In response to TB 2 being successfully decoded, the wireless device may deliver the decoded data (e.g., MAC PDU) to the demultiplexing and demultiplexing entity of the wireless device. In response to receiving the positive acknowledgement, the base station may transmit a new transport block (e.g., TB 3) by using process #n.

[0294] In an embodiment, when transmitting for a HARQ process, a HARQ entity (eg, of a wireless device) may deliver one or two (in case of downlink spatial multiplexing) TBs (received) and associated HARQ information to the HARQ process.

[0295] For a received TB and associated HARQ information, if the NDI has been switched compared to the value of the previously received transmission corresponding to the received TB; or if the HARQ process is equal to the broadcast process and this is the first received transmission of the TB scheduled according to the system information indicated by the RRC; or if this is the first received transmission of the TB (for example, there is no previous NDI for the TB), the HARQ process (of the HARQ entity of the wireless device) may determine the transmission (associated with the TB) as a new transmission. Otherwise, the HARQ process may determine that the transmission (associated with the TB) is a retransmission. Based on determining that the transmission is a new transmission, the MAC entity may attempt to decode the received data. Based on determining that the transmission is a retransmission, the MAC entity may instruct the physical layer to combine the received data with the data currently in the soft buffer of the TB, and attempt to decode the combined data if the data of the TB has not been successfully decoded.

[0296] If the data that the MAC entity attempts to decode is successfully decoded for the TB, or if the data for the TB was successfully decoded before, if the HARQ process is equal to the broadcast process, the MAC entity can deliver the decoded MAC PDU to the upper layer. If the data that the MAC entity attempts to decode is successfully decoded for the TB, or if the data for the TB was successfully decoded before, if this is the first successful decoding of the data for the TB, the MAC entity can pass the decoded MAC PDU to the decomposition and demultiplexing entity.

[0297] If the data that the MAC entity attempted to decode was not successfully decoded for the TB, and if the data of the TB was not successfully decoded before, the MAC entity can instruct the physical layer to replace the data in the soft buffer of the TB with the data that the MAC entity attempted to decode.

[0298] If the HARQ process is associated with a transmission indicated by a TC-RNTI and contention resolution has not succeeded, or if the HARQ process is associated with a transmission indicated by a MSGB-RNTI and the random access procedure has not been successfully completed, or if the HARQ process is equal to a broadcast process, or if the timeAlignmentTimer associated with the TAG containing the cell on which HARQ feedback is to be attempted stops or expires, the MAC entity may not instruct the physical layer to generate an acknowledgement of the data in the TB. Otherwise, the MAC entity may instruct the physical layer to generate an acknowledgement of the data in the TB.

[0299] The MAC entity may ignore the NDI received in all downlink assignments on the PDCCH for its TC-RNTI when determining whether the NDI on the PDCCH for its C-RNTI has toggled compared to the value in the previous transmission. If the MAC entity receives a retransmitted TB size that is different from the last TB size signaled for that TB, the behavior of the wireless device may depend on the implementation of the wireless device.

[0300] Fig.30 An example of a downlink TB (re)transmission mechanism based on a HARQ process according to some embodiments is shown. In the example, a base station (e.g., a gNB) may attempt to send a first downlink control information (DCI) including a downlink assignment and one or more HARQ information to a wireless device (e.g., a UE). The one or more HARQ information may include a HARQ process ID (e.g., such as Fig.30 As shown, process ID=k), a first NDI value (e.g., first NDI=1), etc. The physical layer of the wireless device may receive the first TB of data based on the downlink assignment. Before receiving the first DCI, the wireless device may have a current NDI value (e.g., Fig.30 As shown, the current NDI = 0).

[0301] In response to receiving the first DCI, the wireless device may determine that the first NDI has been switched in response to the first NDI value (1) being different from the current NDI value (0). In response to the first NDI being switched, the MAC entity of the wireless device may determine that the transmission of the first TB is a new transmission and attempt to decode the received data of the first TB. The MAC entity may not be able to successfully decode the received data. In response to not successfully decoding the received data, the MAC entity may instruct the physical layer to replace the soft buffer of the first TB with the data that the MAC entity attempted to decode. The MAC entity may instruct the physical layer to generate a NACK for the data in the first TB. In an example, in response to not successfully decoding the received data, the wireless device may transmit a NACK to the base station.

[0302] In response to receiving the NACK, the base station may transmit a second DCI indicating retransmission of the first TB, wherein the second DCI includes the same HARQ process ID as the first HARQ process ID, a second downlink assignment, an RV value, and a second NDI value (eg, second NDI=1).

[0303] In response to the second NDI value (1) being equal to the first NDI value (1), the UE may determine that the second NDI has not been switched and that the first NDI value is now the new current NDI value. The physical layer may receive the retransmitted first TB of data via the second downlink assignment. In response to the second NDI not being switched, the MAC entity of the wireless device may determine that the transmission via the second downlink assignment is a retransmission of the first TB. In an example, the wireless device may attempt to decode the first TB based on the newly received data for the first TB and the current data in the soft buffer associated with the HARQ process identified by the HARQ process ID k.

[0304] In an example, the MAC entity may successfully decode the received data of the first TB. In response to successfully decoding the received data, the MAC entity may deliver the decoded data (e.g., MAC PDU) to the decomposition and demultiplexing entity of the wireless device. The MAC entity may instruct the physical layer to generate an ACK for the data in the first TB. The wireless device may transmit an ACK for the first TB to the base station.

[0305] In an example, a wireless device may receive one or more TBs of an MBS session from a base station. An MBS session may require a higher QoS than a periodic broadcast message. An MBS session including V2X application data may require lower latency transmission than a periodic broadcast message. An MBS session including IOT industry application data may require higher reliability than a periodic broadcast message. An MBS session including live video application data may require higher throughput and higher reliability than a periodic broadcast message, etc.

[0306] In order to meet the QoS requirement of the transmission of MBS TB, when the wireless device subscribed to the MBS session does not successfully receive the MBS TB, the base station can apply the HARQ mechanism to retransmit the MBS TB. The base station can retransmit the MBS TB in unicast transmission or multicast transmission.

[0307] Fig.31A and Fig.31B Examples of unicast retransmission of an MBS TB and multicast retransmission of an MBS TB according to some embodiments are shown.

[0308] like Fig.31A As shown, when subscribing to an MBS session, the wireless device may receive an initial transmission of an MBS TB (or TBs). The wireless device may receive the initial transmission based on receiving a DCI with a CRC scrambled by an MBS-RNTI associated with the MBS session. The wireless device may receive the DCI while the wireless device is monitoring the PDCCH on a search space (associated with a CORESET) configured for the MBS session. The wireless device may attempt to decode the MBS TB based on the MBS-RNTI. The wireless device may not successfully decode the TB (e.g., with an incorrect CRC check). The wireless device may buffer received data for the TB based on not successfully decoding the TB.

[0309] like Fig.31A As shown, the wireless device may transmit a HARQ NACK indicating that the wireless device did not successfully decode the TB. The base station may transmit a second DCI with a CRC scrambled by the MBS-RNTI based on the received HARQ NACK. The second DCI may indicate a retransmission of the MBS TB. The second DCI is transmitted to a group of wireless devices subscribed to the MBS session. The retransmission of the MBS TB is for the group of wireless devices. Based on transmitting the HARQ NACK, the wireless device may monitor the PDCCH on the search space configured for the MBS session to receive a second DCI indicating the retransmission of the MBS TB. The wireless device may receive the retransmitted MBS TB based on receiving the second DCI. The wireless device may combine the first received data (e.g., the first TB received based on the first DCI initialization) and the second received data (e.g., the new received data of the MBS TB based on the second DCI). The wireless device may attempt to decode the combined first data and the second data of the MBS TB based on the MBS-RNTI.

[0310] In an example, the wireless device may successfully decode the combined data.The wireless device may deliver the decoded MAC PDU contained in the MBS TB to the decomposition and demultiplexing entity of the wireless device.

[0311] In an example, the wireless device may not successfully decode the combined data. Based on not successfully decoding the combined data, the wireless device may determine to request a retransmission based on the examples of the above embodiments.

[0312] Retransmission of MBS TBs in multicast transmission may increase signaling overhead, for example, when multiple wireless devices subscribed to an MBS session request retransmission of the MBS TB in response to the MBS TB being unsuccessfully decoded by the multiple wireless devices. Retransmission of MBS TBs in multicast transmission may reduce multicast transmission throughput because the base station may retransmit the MBS TB in multicast transmission when there is a wireless device among the multiple wireless devices that did not correctly decode the MBS TB even if one or more other wireless devices among the multiple wireless devices correctly decoded the MBS TB.

[0313] Fig.31B An example of a unicast retransmission of an MBS TB according to some embodiments is shown. When subscribing to an MBS session, the wireless device may receive an initial transmission of an MBS TB (or TBs). The wireless device may receive the initial transmission based on receiving a DCI with a CRC scrambled by an MBS-RNTI associated with the MBS session. The wireless device may receive the DCI while the wireless device is monitoring the PDCCH on a search space (associated with a CORESET) configured for the MBS session. The wireless device may attempt to decode the MBS TB based on the MBS-RNTI. The wireless device may unsuccessfully decode the TB. The wireless device may buffer received data for the TB based on unsuccessfully decoding the TB.

[0314] like Fig.31B As shown, the wireless device may transmit a HARQ NACK indicating that the wireless device did not successfully decode the TB. The base station may transmit a second DCI with a CRC scrambled by the C-RNTI based on the received HARQ NACK. The second DCI may indicate a retransmission of the MBS TB in a unicast transmission. The second DCI is transmitted exclusively to the wireless device (rather than to a second wireless device other than the wireless device). The retransmission of the MBS TB scheduled by the second DCI is transmitted exclusively to the wireless device. The wireless device may receive the retransmitted MBS TB based on receiving the second DCI. The wireless device may combine the first received data (e.g., the initial received TB data based on the first DCI) and the second received data (e.g., the new received TB data based on the second DCI) of the MBS TB. The wireless device may attempt to decode the combined first data and second data of the MBS TB.

[0315] In an example, the wireless device may successfully decode the combined data.The wireless device may deliver the decoded MAC PDU contained in the MBS TB to the decomposition and demultiplexing entity of the wireless device.

[0316] In an example, the wireless device may not successfully decode the combined data. Based on not successfully decoding the combined data, the wireless device may determine to request a retransmission based on the examples of the above embodiments.

[0317] Retransmission of MBS TBs in unicast transmission can improve multicast transmission throughput because the base station transmits a new MBS TB at each multicast transmission opportunity (or does not perform retransmission of old MBS TBs). Retransmission of MBS TBs in unicast transmission can increase signaling overhead, for example, when multiple wireless devices subscribed to an MBS session request retransmission of the MBS TB and the base station can retransmit the MBS TB to each of the multiple wireless devices separately.

[0318] In an example, a wireless device may receive a multicast initial transmission of an MBS TB and a multicast retransmission of an MBS TB. A wireless device may receive a multicast initial transmission of an MBS TB and a unicast retransmission of an MBS TB. By using existing technologies, a wireless device may be required to support two types of retransmissions, such as a multicast retransmission type and a unicast retransmission type. By supporting these two types of retransmissions, a wireless device may be required to monitor a first PDCCH on an MBS-dedicated search space to receive a first DCI for multicast retransmissions, and to monitor a second PDCCH on a unicast search space to receive a second DCI for unicast retransmissions. Monitoring two PDCCHs for retransmissions of an MBS may increase power consumption of the wireless device and / or increase implementation complexity of the wireless device. Reception of MBS TB retransmissions needs to be efficiently handled to reduce power consumption of the wireless device.

[0319] In the prior art, for example, when a base station receives HARQ feedback indicating a failure to receive an MBS TB, the base station may transmit a unicast DCI (initially scheduled by a multicast DCI) indicating a retransmission of the MBS TB. The base station may transmit a unicast DCI indicating a retransmission of the MBS TB based on the following: the unicast DCI and the multicast DCI include the same HARQ process ID, and interlock the first NDI of the multicast DCI and the second NDI of the unicast DCI (e.g., by not switching the second NDI compared to the first NDI). In the prior art, the unicast DCI and the multicast DCI may be received by a wireless device in the same search space or the same control resource set of a cell. Comparing two DCIs received in the same search space or the same control resource set (e.g., comparing two NDIs and / or two HARQ process IDs) may not be a problem for wireless devices in cells with narrow bandwidths. Similarly, combining two data received in the same frequency range of a cell (one received with multicast transmission and the other received with unicast transmission) may not be a problem for wireless devices in cells with narrow bandwidths.

[0320] In the NR system, when a cell with a large bandwidth is divided into multiple BWPs (e.g. Fig. 9 ) and the frequency resources for MBS transmission are configured separately from the frequency resources for unicast transmission within the unicast BWP (e.g., as Fig.28B As shown in the figure, when the wireless device receives a unicast DCI in the unicast search space of the BWP, the wireless device may not be able to decode the MBS TB based on the soft combination of the first data (scrambled by the MBS RNTI) and the second data (scrambled by the C-RNTI) by implementing the prior art. Based on the prior art, the wireless device may incorrectly determine whether the unicast DCI received in the unicast search space of the BWP is for the unicast TB or for the retransmission of the MBS TB previously scheduled by the MBSDCI received in the MBS search space. The MBS search space may be configured with common frequency resources associated with the MBS within the unicast BWP. The unicast search space may be configured (for example, outside the common frequency resources) and within the unicast BWP. The prior art may reduce the system throughput of a cell (or BWP) supporting unicast transmission and MBS transmission. When the MBS TB is initially scheduled by the MBSDCI in the common search space and the MBS TB is retransmitted based on the unicast DCI in the unicast search space, it is necessary to effectively handle the reception of the retransmission of the MBS TB to reduce the power consumption of the wireless device.

[0321] In an exemplary embodiment, the base station may transmit one or more configuration parameters for the MBS session to the wireless device. The configuration parameters may include an MBS-specific RNTI associated with the MBS session (e.g., MBS-RNTI, G-RNTI, SC-RNTI, etc.). The configuration parameters may include a retransmission type parameter that indicates whether the base station will use unicast retransmission or multicast retransmission for the MBS TB. The wireless device may receive a multicast initial transmission of the MBS TB and may not be able to successfully decode the MBS TB. The wireless device may send a HARQ NACK to the base station indicating that the wireless device did not successfully decode the MBS TB.

[0322] In an exemplary embodiment, based on the retransmission type indicating that unicast retransmission is for the MBS TB, the wireless device may monitor the PDCCH (e.g., via the unicast search space) to receive a DCI (with a CRC scrambled by the C-RNTI) scheduling the unicast retransmission of the MBS TB. The wireless device may combine the unicast retransmission of the MBS TB (scrambled by the C-RNTI) and the multicast initial transmission of the MBS TB (scrambled by the MBS-RNTI) and decode the combined data of the MBS TB.

[0323] In an exemplary embodiment, based on indicating that multicast retransmission is a retransmission type scheduled for an MBS TB, the wireless device may monitor the PDCCH (e.g., via a common search space associated with the MBS) to receive a DCI (with a CRC scrambled by the MBS-RNTI) scheduling a multicast retransmission of the MBS TB. The wireless device may combine the multicast retransmission of the MBS TB (scrambled by the MBS-RNTI) with the multicast initial transmission of the MBS TB (scrambled by the MBS-RNTI).

[0324] In an exemplary embodiment, based on the retransmission type indicating that multicast retransmission is for an MBS TB, the wireless device may monitor the PDCCH to receive a DCI (with a CRC scrambled by the MBS-C-RNTI) scheduling multicast retransmission of the MBS TB. The base station may configure the MBS-C-RNTI for scheduling retransmissions of the MBS TB in the multicast transmission. For the initial transmission of the MBS TB, the MBS-C-RNTI may be configured separately or independently from the MBS-RNTI. In an exemplary embodiment, when the wireless device does not successfully decode an MBS TB scheduled by a DCI with a CRC scrambled by the MBS-RNTI, the wireless device may monitor the PDCCH to receive a second DCI with a CRC scrambled by the MBS-C-RNTI for retransmission of the MBS TB.

[0325] In an exemplary embodiment, the retransmission type may be configured per MBS session, per BWP, per cell, per cell group, or any combination thereof.

[0326] In an exemplary embodiment, the retransmission type may be configured per MBS session. The base station may send configuration parameters for multiple MBS sessions, each MBS session being associated with a retransmission type. The retransmission type may indicate whether unicast retransmission or multicast retransmission is used for an MBS TB.

[0327] In an exemplary embodiment, the retransmission type may be configured per BWP. The base station may transmit configuration parameters of multiple BWPs of a cell. Each BWP may be associated with one or more MBS sessions. Each BWP may be configured with a retransmission type for one or more MBS sessions, which indicates whether unicast retransmission or multicast retransmission is used for the MBS TBs of the one or more MBS sessions.

[0328] In an exemplary embodiment, the retransmission type may be configured per cell. The base station may transmit configuration parameters for multiple cells (e.g., PCell or SCell). Each cell may be associated with one or more MBS sessions. Each cell may be configured with a retransmission type for one or more MBS sessions, which indicates whether unicast retransmission or multicast retransmission is used for the MBS TBs of the one or more MBS sessions.

[0329] In an exemplary embodiment, the retransmission type may be indicated in the DCI. The DCI may be a DCI that schedules an initial transmission of an MBS TB (e.g., with a CRC scrambled by the MBS-RNTI). The wireless device may determine the retransmission type for the retransmission of the MBS TB based on the retransmission type in the DCI.

[0330] In an exemplary embodiment, the wireless device may determine the retransmission type based on the RRC message and the DCI. The wireless device may determine the retransmission type based on the RRC message including the retransmission type and the DCI not including the retransmission type. The wireless device may determine the retransmission type based on the RRC message not including the retransmission type and the DCI including the retransmission type. The wireless device may determine the retransmission type based on the second retransmission type indicated in the DCI overriding the first retransmission type indicated in the RRC message.

[0331] Fig.32 An example of retransmission of an MBS TB according to some embodiments is shown. In an exemplary embodiment, a base station may transmit and / or a wireless device may receive one or more RRC messages including configuration parameters for an MBS session. The configuration parameters may include an MBS-specific RNTI associated with the MBS session (e.g., MBS-RNTI, MBS-C-RNTI, G-RNTI, SC-RNTI, etc.). The configuration parameters may include a retransmission type (mode, configuration, indication, etc.) parameter that indicates whether the base station will use unicast retransmission or multicast retransmission for the MBS TB retransmission. The one or more RRC messages may further indicate configuration parameters for frequency resources for the MBS session (e.g., based on the number of packets relative to the MBS session). Fig.28A and / or Fig.28B The one or more RRC messages may further indicate configuration parameters of a PDCCH for MBS (e.g., referred to as MBS PDCCH), where the MBS PDCCH may carry a DCI with a CRC scrambled by an MBS specific / dedicated RNTI (e.g., MBS-RNTI, SC-RNTI, G-RNTI, etc.). In this specification, MBS specific / dedicated RNTI, MBS-RNTI, SC-RNTI, and G-RNTI are interchangeable in that they are different from C-RNTI. The configuration parameters may indicate a search space and / or frequency resource allocation and time domain allocation of a CORESET for receiving the MBS PDCCH in the BWP. In contrast to a UE-specific search space, the search space may be a common search space. The common search space and / or the UE-specific search space may be based on the above with respect to Fig. 22 In the example, the frequency resource allocation and time domain allocation of the search space and / or CORESET can be based on the relative Fig.25 and / or Fig.26 The exemplary embodiments described are implemented.

[0332] In an exemplary embodiment, the one or more RRC messages may also include a C-RNTI (CS-RNTI, MCS-C-RNTI, etc.) associated with the wireless device. The one or more RRC messages may further indicate configuration parameters of a PDCCH for a unicast transmission (e.g., referred to as a unicast PDCCH), wherein the unicast PDCCH may carry a DCI with a CRC scrambled by a wireless device-specific RNTI (e.g., C-RNTI, CS-RNTI, MCS-C-RNTI, etc.). The configuration parameters may indicate a search space and / or a frequency resource allocation and a time domain allocation of a CORESET for receiving the unicast PDCCH in the BWP. In an example, the frequency resource allocation and the time domain allocation of the search space and / or the CORESET may be based on the frequency resource allocation relative to the wireless device. Fig.25 and / or Fig.26 The exemplary embodiments described are implemented.

[0333] In an exemplary embodiment, the wireless device may receive a DCI with a CRC scrambled by the MBS-RNTI via the MBS PDCCH in the BWP ( Fig.32 (not shown in the figure), where the DCI indicates the downlink assignment of MBS PDSCH resources for the initial transmission of the MBS TB. The MBS TB scrambled by the MBS-RNTI is transmitted to a group of wireless devices configured with the MBS-RNTI. Fig.32 As shown, the wireless device may receive a multicast initial transmission (first data) of an MBS TB based on the DCI. The DCI (or group-common DCI) and the MBS PDSCH (or group-common PDSCH) may be received in common frequency resources associated with the MBS within the BWP. The wireless device may not be able to successfully decode the MBS TB.

[0334] In an exemplary embodiment, the DCI may be one of a traditional DCI format (e.g., DCI format 1_0 / 1_1 / 1_2) or a new DCI format different from the traditional DCI format. The DCI may have less DCI payload than the traditional DCI format 1_0. In an example, the DCI may include at least one of the following: a time domain resource assignment indication, a VRB to PRB mapping indication, an MCS indication, an NDI, a redundancy version, a HARQ process number, a PUCCH resource indicator, a PDSCH to HARQ feedback timing indicator, a ChannelAccess-CPext, etc. In an exemplary embodiment, one or more DCI fields (e.g., NDI, a redundancy version, a PUCCH resource indicator, a PDSCH to HARQ feedback timing indicator, and / or a ChannelAccess-CPext, etc.) may not exist in the DCI scheduled by MBSPDSCH.

[0335] like Fig.32 As shown, the wireless device may transmit HARQ NACK signaling indicating that the wireless device did not successfully decode the MBS TB. The wireless device may transmit the HARQ NACK signaling included in the UCI via the PUCCH resource.

[0336] like Fig.32 As shown, the wireless device may determine whether the retransmission type parameter indicates a unicast retransmission type or a multicast retransmission type. In response to the retransmission type parameter indicating a unicast retransmission type, the wireless device may monitor the unicast PDCCH on the search space / CORESE associated with the unicast PDCCH for receiving a first DCI (with a CRC scrambled by the C-RNTI / CS-RNTI) scheduling a unicast retransmission of the MBS TB. Based on the monitoring of the unicast PDCCH, the wireless device may receive the first DCI. The wireless device may receive the unicast retransmission of the MBS TB ( Fig.32 The wireless device may combine the initially transmitted data ( Fig.32 The first data in) and the retransmitted data ( Fig.32 Based on the combination, the wireless device can decode the MBSTB. In an example, the wireless device can decode the MBSTB based on Fig.33 , Fig.34 , Fig.35 and / or Fig.36 An exemplary embodiment of the invention determines whether a unicast PDCCH schedules a retransmission of an MBS TB or an initial transmission of a unicast TB.

[0337] In an exemplary embodiment, the wireless device may determine that the retransmission type parameter indicates a multicast retransmission type. In response to the retransmission type parameter indicating the multicast retransmission type, the wireless device may monitor the multicast PDCCH on the search space / CORESE associated with the multicast PDCCH for receiving a second DCI (with a CRC scrambled by the MBS-RNTI) scheduling a multicast retransmission of the MBS TB. Based on the monitoring of the multicast PDCCH, the wireless device may receive the second DCI. The wireless device may receive the multicast retransmission of the MBS TB ( Fig.32 The wireless device may combine the initially transmitted data ( Fig.32 The first data in) and the retransmitted data ( Fig.32 Based on the combination, the wireless device can decode the MBS TB.

[0338] As compared to Fig.32 The described exemplary embodiments may improve the signaling overhead of MBS TB retransmissions. The exemplary embodiments may improve multicast throughput and / or reduce the implementation complexity of wireless devices receiving retransmissions of MBS TBs.

[0339] In an exemplary embodiment, the base station may determine the retransmission type of the MBS TB of the MBS session based on one or more criteria, the one or more criteria including at least one of the following: the number of wireless devices subscribed to the MBS session, the frequency resource configuration of the MBS session, the QoS requirements of the MBS session, the wireless device capabilities for handling the retransmission of the MBS TB, etc. In an exemplary embodiment, for example, when the base station determines that the number of wireless devices subscribed to the MBS session is less than a threshold, the base station may determine the unicast retransmission type of the MBS TB. For example, when the base station determines that the number of wireless devices subscribed to the MBS session is greater than a threshold, the base station may determine the multicast retransmission type of the MBS TB. In an exemplary embodiment, for example, when the base station determines that the frequency resources of the MBS session are within the unicast BWP, the base station may determine the unicast retransmission type of the MBS TB. For example, when the base station determines that an MBS-dedicated BWP is configured on the cell and the MBS-dedicated BWP is different from the unicast BWP of the cell, the base station may determine the multicast retransmission type of the MBSTB.

[0340] In an exemplary embodiment, the wireless device may send a wireless device capability message to the base station, the wireless device capability message including a retransmission type indication indicating whether the wireless device supports retransmission of MBS TBs via unicast transmission or retransmission of MBS TBs via multicast transmission. The retransmission type indication may be indicated per MBS session, per cell, per cell group, per frequency range, etc. The wireless device capability message may further indicate whether the wireless device supports unicast retransmission of MBS TBs scrambled by an MBS-RNTI associated with the MBS session, or whether the wireless device supports unicast retransmission of MBS TBs scrambled by a C-RNTI associated with the wireless device. In response to receiving a wireless device capability request message from the base station, the wireless device may transmit the wireless device capability message. Based on the received wireless device capability message, the base station may transmit a retransmission type parameter to the wireless device.

[0341] In an exemplary embodiment, the retransmission type may be indicated in the DCI.The DCI may be a DCI scheduling the initial transmission of the MBS TB (eg, with a CRC scrambled by the MBS-RNTI).

[0342] In an exemplary embodiment, a DCI including a retransmission type field (e.g., a new DCI format having a different format from the legacy DCI format 1_0 / 1_1 / 1_2) may indicate whether the MBS TB will be retransmitted in a unicast transmission or in a multicast transmission if a retransmission is requested. The wireless device may determine the retransmission type for the retransmission of the MBS TB based on the retransmission type in the DCI.

[0343] In an exemplary embodiment, a DCI (e.g., having a conventional DCI format) in which one or more DCI fields (e.g., downlink assignment index, PDSCH to HARQ feedback timing indicator, etc.) are set to predefined values ​​may indicate whether the MBS TB will be retransmitted in unicast transmission or in multicast transmission in the case of a retransmission request. The wireless device may determine the retransmission type for the retransmission of the MBS TB based on one or more values ​​of the one or more DCI fields of the DCI.

[0344] In an exemplary embodiment, the base station may determine the RNTI for data scrambling of the retransmission of the MBS TB based on at least one of the following: the number of wireless devices subscribed to the MBS session, the frequency resource configuration of the MBS session, the QoS requirements of the MBS session, the capabilities of the wireless device, etc. In an exemplary embodiment, for the retransmission of the MBS TB, in response to determining that the retransmission is a multicast retransmission type, the base station may scramble the MBS TB with the MBS-RNTI. In response to determining that the retransmission is a multicast retransmission type, the base station may scramble the MBS TB with the MBS-C-RNTI, wherein the MBS-C-RNTI is different from the MBS-RNTI configured for the initial transmission. In response to determining that the retransmission is a unicast retransmission type, the base station may scramble the MBS TB with the C-RNTI. In an exemplary embodiment, in response to determining that the retransmission is a unicast retransmission type, the base station may scramble the MBS TB with the MBS-RNTI.

[0345] In an exemplary embodiment, in response to a unicast retransmission of an MBS TB being scrambled by an MBS-RNTI, the wireless device may combine an initial transmission of an MBS TB scrambled by an MBS-RNTI and a retransmission of an MBS TB scrambled by an MBS-RNTI. The wireless device may decode the combined data of the MBS TB. The retransmission of an MBS TB scrambled in a unicast transmission and with an MBS-RNTI may simplify the decoding complexity of the wireless device.

[0346] In an exemplary embodiment, in response to a unicast retransmission of an MBS TB being scrambled by a C-RNTI, the wireless device may combine an initial transmission of an MBS TB scrambled by the MBS-RNTI and a retransmission of an MBS TB scrambled by the C-RNTI. The wireless device may decode the combined data of the MBS TB. The retransmission of an MBS TB scrambled in a unicast transmission and with the C-RNTI may improve the transmission security of the MBS TB.

[0347] In an exemplary embodiment, when the base station determines a unicast retransmission of an MBS TB of an MBS session, the base station may scramble the MBS TB with the MBS-RNTI associated with the MBS session and retransmit the scrambled MBS TB in a unicast PDSCH resource. mod 2 to scramble multiple bits of the MBS TB codeword (e.g., Scrambling sequence c (q) (i) can be generated according to the following equation:

[0348] c(n)=(x 1 (n+N C )+x 2 (n+N C ))mod2

[0349] x 1 (n+31)=(x 1 (n+3)+x 1 (n))mod2

[0350] x 2 (n+31)=(x 2 (n+3)+x 2 (n+2)+x 2 (n+1)+x 2 (n))mod2

[0351] Where N C =1600 and the first m sequence x 1 (n) should be x 1 (0)=1,x 1 (n)=0,n=1,2,...,30 to initialize.

[0352] In an exemplary embodiment, the scrambling sequence generator of the scrambling sequence may be c init =n RNTI 2 15 +q·2 14 +n ID To initialize, where n RNTI Corresponds to the MBS-RNTI associated with the MBS session. ID It can be equal to the data scrambling identifier configured for MBSPDSCH or for MBS session. ID (e.g., a new dataScrambingIdentityMBS-PDSCH IE configured in the configuration parameters of the MBS configuration) may be configured differently or separately from the higher layer parameter dataScramblingIdentityPDSCH configured for unicast PDSCH transmission. Separate configuration for MBS PDSCH (or group common PDSCH dedicated to MBS) and unicast PDSCH ID The transmission security of MBS sessions can be increased.

[0353] In an example, when the DCI scheduling unicast PDSCH transmission is CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI, and the DCI is not DCI format 1_0 received in the common search space, the higher layer parameter dataScramblingIdentityPDSCH may be applied to determine n IDFor unicast PDSCH scheduled by DCI, if the higher layer parameter dataScramblingIdentityPDSCH is not configured, or if the RNTI of the DCI is not equal to C-RNTI, MCS-C-RNTI or CS-RNTI, or if the DCI is DCI format 1_0 via common search space, then n ID May be equal to the cell identifier of the cell.

[0354] Based on this exemplary embodiment, the base station may transmit and / or the wireless device may receive an RRC message, the RRC message including a first configuration parameter for the MBS session and a second configuration parameter for unicast transmission. The first configuration parameter and / or the second configuration parameter may be based on the above with respect to Fig.28B , Fig.31A , Fig.31B and / or Fig.32 In an exemplary embodiment, the first configuration parameter may indicate that the common frequency resources of the MBS session are configured within the BWP (e.g., based on the above with respect to Fig.28B The first configuration parameter may indicate a first RNTI (e.g., MBS-RNTI, SC-RNTI, G-RNTI, etc.) associated with the MBS session. The first configuration parameter may indicate a first PDSCH data scrambling identifier associated with the MBS session. The first configuration parameter may indicate a resource configuration parameter of a group common PDCCH associated with the MBS session.

[0355] In an exemplary embodiment, the second configuration parameter may include a configuration parameter of the BWP. The second configuration parameter may indicate a second RNTI (e.g., C-RNTI, CS-RNTI, MCS-C-RNTI, etc.) associated with a unicast transmission dedicated to the wireless device. The second configuration parameter may indicate a second PDSCH data scrambling identifier associated with a unicast transmission dedicated to the wireless device. The second configuration parameter may indicate a resource configuration parameter of a unicast PDCCH associated with the unicast transmission. In an example, the second RNTI may be different from the first RNTI. The second PDSCH data scrambling identifier may be different from the first PDSCH data scrambling identifier.

[0356] In an exemplary embodiment, the wireless device may receive a group-common DCI for a transport block scheduling an MBS session based on a first RNTI and via common frequency resources. The group-common DCI may be received in a first DCI format (e.g., DCI format 1_0 / 1_1 / 1_2 as described above, or a new DCI format different from DCI format 1_0 / 1_1 / 1_2 as described above). The wireless device may select a first PDSCH data scrambling identifier from a first PDSCH data scrambling identifier and a second PDSCH data scrambling identifier based on the group-common DCI received based on the first RNTI. In the example, the wireless device may select the first PDSCH data scrambling identifier regardless of whether the group-common DCI is received in DCI format 1_0. Based on the transport block being scrambled with a scrambling sequence, the wireless device may receive (decode or detect) the transport block via common frequency resources, wherein the scrambling sequence is initialized by the selected first PDSCH data scrambling identifier and the first RNTI.

[0357] In an exemplary embodiment, the wireless device may receive a unicast DCI based on a second RNTI and via a BWP (e.g., outside of a common frequency resource associated with an MBS session), the unicast DCI scheduling a second transport block dedicated to the wireless device. The wireless device may select a second PDSCH data scrambling identifier from a first PDSCH data scrambling identifier and a second PDSCH data scrambling identifier based on the unicast DCI received based on the second RNTI. Based on the second transport block being scrambled with a second scrambling sequence, the wireless device may receive (decode or detect) the second transport block via a BWP (e.g., outside of a common frequency resource associated with an MBS session), wherein the second scrambling sequence is initialized by the selected second PDSCH data scrambling identifier and the second RNTI. Based on determining that the scrambling sequence is initialized by the data scrambling identifier associated with the MBS session and the RNTI associated with the MBS session, the exemplary embodiment may increase the robustness of multicast transmission of the MBS session to multiple wireless devices configured with the MBS session.

[0358] In an exemplary embodiment, the scrambling sequence generator of the scrambling sequence may be c init =n RNTI 2 15 +q·2 14 +n ID To initialize, where n RNTI corresponds to the MBS-RNTI associated with the MBS session. In this example, n ID can be equal to zero. In the example, n ID It may be equal to the cell ID of the cell via which the wireless device receives the MBS TB for the MBS session.

[0359] In an exemplary embodiment, when the base station determines a multicast retransmission of an MBS TB of an MBS session, the base station may scramble the MBS TB with an MBS-C-RNTI associated with the MBS session, wherein the MBS-C-RNTI may be configured exclusively for retransmission of the MBS TB in multicast transmission. In an exemplary embodiment, when the base station determines a multicast retransmission of an MBS TB of an MBS session, the base station may scramble the MBS TB with an MBS-RNTI associated with the MBS session, wherein the MBS-RNTI may be configured to be the same for initial transmission and retransmission of the MBS TB.

[0360] Fig.33 According to some embodiments (e.g., based on the above relative Fig.32 An example of HARQ process management for an MBS session for an extension of the exemplary embodiment described herein). The wireless device may receive one or more RRC messages including configuration parameters of a cell from a base station. The configuration parameters may indicate a plurality of HARQ processes associated with the cell (HARQ process x, HARQ process y, ..., HARQ process m, HARQ process n, etc.). The configuration parameters may indicate that the plurality of HARQ processes are grouped into HARQ process groups, each HARQ process group including one or more HARQ processes of the plurality of HARQ processes. A first HARQ process group (e.g., including HARQ process m, HARQ process n, etc.) may be associated with a unicast PDSCH transmission. One or more second HARQ process groups (e.g., including HARQ process x, HARQ process y, etc.) may be associated with an MBS transmission.

[0361] In an exemplary embodiment, each MBS session of the plurality of MBS sessions may be associated with a corresponding HARQ process group of the one or more second HARQ process groups.

[0362] In an example, a plurality of MBS sessions of the plurality of MBS sessions may be associated with a shared HARQ process group of the one or more second HARQ process groups.

[0363] In an exemplary embodiment, separating the HARQ processes for unicast transmission and MBS transmission can enable a base station or wireless device to flexibly manage the HARQ process. When a retransmitted MBS TB is scheduled by a unicast DCI and transmitted in a unicast PDSCH resource, separating the HARQ processes for unicast transmission and MBS transmission can enable the wireless device to correctly decode the retransmitted MBS TB.

[0364] Fig.32 and Fig.33 In an exemplary embodiment, based on HARQ process grouping (e.g., Fig.33), the wireless device may determine whether the retransmission of the MBS TB is via multicast transmission or via unicast transmission (e.g., as shown in Fig.32 shown).

[0365] Fig.34 According to some embodiments (e.g., based on the above relative Fig.32 and / or Fig.33 An example of retransmitting an MBS TB in a unicast PDSCH resource is an extension of the exemplary embodiment described in the present disclosure. In an exemplary embodiment, the wireless device may receive one or more RRC messages from a base station, the one or more RRC messages including configuration parameters for the MBS session. The one or more RRC messages may be based on the information relative to the Fig.32 The exemplary embodiments described are implemented.

[0366] In an exemplary embodiment, the wireless device may receive a first DCI ( CRC scrambled by MBS-RNTI) via the MBS PDCCH in the BWP. Fig.34 The first DCI may be received in a first SS associated with the MBS session. The first DCI may be received in a first control resource set associated with the MBS session. The first DCI may be received in a common frequency resource associated with the MBS session. The first DCI may indicate an MBS TB( Fig.34 The first DCI may include a downlink assignment of MBS PDSCH resources for initial transmission of the first TB in the MBS TB. The MBS TB scrambled by the MBS-RNTI is transmitted to a group of wireless devices configured with the MBS-RNTI. The first DCI may include a HARQ process ID ( Fig.34 The first DCI may include a first new data indicator (NDI) value.

[0367] like Fig.34 As shown, the wireless device may receive a multicast initial transmission of an MBS TB via a first PDSCH resource indicated by a first DCI. The wireless device may fail to successfully decode the MBS TB. Based on the failure to successfully decode the MBS TB, the wireless device may buffer the received data of the MBS TB in a HARQ buffer associated with a HARQ process (identified by a HARQ process ID).

[0368] In an exemplary embodiment, the first DCI may be a traditional DCI format (e.g., DCI format 1_0 / 1_1 / 1_2) or one of the new DCI formats that are different from the traditional DCI format. The first DCI may have less DCI payload than the traditional DCI format 1_0. In an example, the first DCI may include at least one of the following: time domain resource assignment indication, VRB to PRB mapping indication, MCS indication, NDI, redundancy version, HARQ process number, PUCCH resource indicator, PDSCH to HARQ feedback timing indicator, ChannelAccess-CPext, etc. In an exemplary embodiment, one or more DCI fields (e.g., NDI, redundancy version, PUCCH resource indicator, PDSCH to HARQ feedback timing indicator and / or ChannelAccess-CPext, etc.) may not exist in the first DCI scheduled by MBS PDSCH.

[0369] like Fig.34 As shown, the wireless device may transmit HARQ NACK signaling indicating that the wireless device did not successfully decode the MBS TB. Based on the received HARQ NACK signaling, the base station may determine a unicast retransmission of the MBS TB. The base station may determine a unicast retransmission of the MBS TB based on the received HARQ NACK signaling. Fig.32 The exemplary embodiment described herein determines the unicast retransmission of the MBS TB. The base station may transmit a second DCI ( Fig.34 The second DCI may be received in a second search space, which is a wireless device-specific search space different from the first search space, where the first search space is a common search space. The second DCI may be received in a BWP (e.g., outside of a common frequency resource associated with the MBS session). The second DCI may be received in a second control resource set different from the first control resource set associated with the MBS session. The second DCI may indicate a downlink assignment of unicast PDSCH resources for retransmissions of the MBS TB. Retransmissions of the MBS TB scrambled by the MBS-RNTI or by the C-RNTI are transmitted exclusively to the wireless device. The second DCI may include a HARQ process ID ( Fig.34 PID=k in .

[0370] like Fig.34As shown, the wireless device receives a second DCI. The wireless device may receive data via a second PDSCH resource indicated by the second DCI. In response to the HARQ ID of the second DCI being the same as the HARQ ID of the first DCI, and the second DCI being a CRC scrambled by the C-RNTI, and the first DCI being a CRC scrambled by the MBS-RNTI, the wireless device may determine that the received data in the second PDSCH resource is a retransmission of an MBS TB originally transmitted in the first PDSCH resource. Based on the HARQ ID of the second DCI being the same as the HARQ ID of the first DCI, the first DCI is received in a search space different from the second DCI, and the first DCI is received in a common frequency resource, wherein the second DCI is received outside the common frequency resource, the wireless device may determine that the received data in the second PDSCH resource is a retransmission of an MBS TB originally transmitted in the first PDSCH resource.

[0371] In an exemplary embodiment, the wireless device may determine that the NDI associated with the HARQ process identified by the HARQ ID has not been switched (e.g., by comparing the second NDI of the second DCI with the first NDI of the first DCI). The wireless device may determine that the NDI associated with the HARQ process identified by the HARQ ID has not been switched (e.g., by comparing the second NDI of the second DCI with the first NDI of the first DCI). Fig.29 The exemplary embodiments described herein determine whether the NDI may be switched or not.

[0372] In an example, in response to the HARQ ID of the second DCI being the same as the HARQ ID of the first DCI, and the second DCI being a CRC scrambled by C-RNTI, and the first DCI being a CRC scrambled by MBS-RNTI, the wireless device may determine that the NDI is not switched regardless of the NDI value of the second DCI. In response to the HARQ ID of the second DCI being the same as the HARQ ID of the first DCI, and the second DCI being a CRC scrambled by C-RNTI, and the first DCI being a CRC scrambled by MBS-RNTI, the wireless device may ignore the NDI value of the second DCI.

[0373] In an example, based on the NDI not being switched and / or the HARQ ID of the second DCI being the same as the HARQ ID of the first DCI, the wireless device may determine that the received data in the second PDSCH resource is a retransmission of an MBS TB originally transmitted in the first PDSCH resource. Based on the NDI not being switched and / or the HARQ ID of the second DCI being the same as the HARQ ID of the first DCI, the wireless device may combine the buffered data with the data received in the second PDSCH resource of the MBS TB. The wireless device may decode the combined data.

[0374] based on Fig.32 , Fig.33 and / or Fig.34 In the example shown in , the wireless device may determine the combination of the multicast initial transmission of the MBS TB and the unicast retransmission of the MBS TB, for example, based on at least one of the following: the second NDI of the unicast DCI received in the UE-specific search space and outside the common frequency resources of the BWP is the same as (or is not switched in comparison to) the first NDI of the group-common DCI received in the common search space and in the common frequency resources within the BWP, and the second HARQ process index of the unicast DCI is the same as the first HARQ process index of the group-common DCI. When HARQ is supported for an MBS session, the exemplary embodiment may improve system throughput.

[0375] Fig.32 , Fig.33 and / or Fig.34 The exemplary embodiments of can be combined. In the example, the base station can be based on the above relative Fig.32 The exemplary embodiments described herein can be used to configure (e.g., based on an indication of wireless device capabilities or no indication of wireless device capabilities) the retransmission type (or mode) of the MBS TB. Based on the retransmission type, the base station can, for example, configure the retransmission type (or mode) of the MBS TB based on the above with respect to Fig.33 The exemplary embodiment described groups multiple HARQ processes into a first HARQ process associated with an MBS session and a second HARQ process associated with a unicast transmission. Based on the configured retransmission type and / or grouping of multiple HARQ processes, the wireless device may perform the following steps based on the above with respect to Fig.34 The described exemplary embodiments determine the receipt of retransmissions of MBS TBs. The exemplary embodiments may improve power consumption of wireless devices, and / or system throughput of base stations for MBS transmissions.

[0376] Fig.35 An example of retransmission of TBs is shown according to some embodiments, when unicast retransmission of unicast TBs and unicast retransmission of MBS TBs are supported.

[0377] like Fig.35 As shown, the wireless device may receive a first DCI (first DCI) that first indicates a downlink assignment of a first PDSCH resource for a first TB associated with a HARQ process (PID=k). The wireless device may receive first data for the TB via the first PDSCH resource indicated by the first DCI. The wireless device may receive first data for the TB based on the first PDSCH resource with respect to the HARQ process (PID=k). Fig.29 and / or Fig.30 The exemplary embodiments are described to store HARQ information of a HARQ process.

[0378] The wireless device may receive a second DCI (second) indicating a downlink assignment of a second PDSCH resource for a second TB associated with the same HARQ process (PID=k) as the first DCI. The wireless device may receive second data for the second TB via the second PDSCH resource indicated by the second DCI. The second DCI may have a CRC scrambled by the C-RNTI. The second DCI may include an NDI value.

[0379] like Fig.35 As shown, the wireless device may determine the RNTI value of the first DCI based on decoding the first DCI.

[0380] In response to the RNTI value of the first DCI being the MBS-RNTI, the RNTI value of the second DCI being the C-RNTI, and the HARQ process ID of the second DCI being the same as the first DCI, the wireless device may, based on the above with respect to Fig.34 An exemplary embodiment described determines that a unicast transmission scheduled by a second DCI is a retransmission of a multicast transmission of an MBS TB. In the example, based on the RNTI value of the first DCI being the MBS-RNTI, the RNTI value of the second DCI being the C-RNTI, and the HARQ process ID of the second DCI being the same as the first DCI, the wireless device can determine the NDI associated with the HARQ process k that has not been switched (e.g., regardless of the NDI value of the second DCI). Based on the NDI not being switched and / or the HARQ process ID of the second DCI being the same as the first DCI, the wireless device can determine that the second TB is the same as the first TB, and that the second data received in the second PDSCH resource is a retransmission of the first TB originally received in the first PDSCH resource. Based on the NDI not being switched and / or the HARQ process ID of the second DCI being the same as the first DCI, the wireless device can combine the first data and the second data of the TB. The wireless device can decode the combined data.

[0381] In response to the RNTI value of the first DCI being a CS-RNTI (e.g., for semi-persistent scheduling of periodic PDSCH resources configured via semi-persistent scheduling), the RNTI value of the second DCI being a C-RNTI, and the HARQ process ID of the second DCI being the same as the first DCI, the wireless device may determine the NDI associated with the switched HARQ process k regardless of the NDI value of the second DCI. Based on the NDI being switched, the wireless device may determine that the second TB is different from the first TB and that the second data received in the second PDSCH resource is an initial transmission of the second TB. Based on the NDI being switched, the wireless device may decode the second TB based on the second data (rather than based on the first data).

[0382] Based on relative to Fig.35The described exemplary embodiments allow the wireless device to manage HARQ retransmissions for SPS and MBS. When HARQ is supported for an MBS session, the exemplary embodiments may improve system throughput.

[0383] Fig.36 An example of retransmission of TBs is shown according to some embodiments when unicast TBs and unicast retransmission of MBS TBs are supported.

[0384] like Fig.36 As shown, the wireless device may receive one or more RRC messages including configuration parameters of a cell from a base station. The configuration parameters may indicate a plurality of HARQ processes associated with the cell (HARQ process x, HARQ process y, ..., HARQ process m, HARQ process n, etc.). The configuration parameters may indicate that the plurality of HARQ processes are grouped into HARQ process groups, each HARQ process group including one or more HARQ processes among the plurality of HARQ processes. A first HARQ process group (e.g., including HARQ process m, HARQ process n, etc.) may be associated with a unicast PDSCH transmission. One or more second HARQ process groups (e.g., including HARQ process x, HARQ process y, etc.) may be associated with an MBS transmission. The grouping of the plurality of HARQ processes may be based on relative to Fig.33 The exemplary embodiments described are implemented.

[0385] like Fig.36 As shown, the wireless device may receive a DCI that first indicates a downlink assignment of a first PDSCH resource of a first TB associated with a HARQ process (PID=k). The DCI whose CRC is scrambled by the C-RNTI may include a HARQ process ID indicating the HARQ process, and an NDI value.

[0386] The wireless device may receive data of the TB via the first PDSCH resource indicated by the DCI. The wireless device may receive data of the TB based on the first PDSCH resource indicated by the DCI. Fig.29 and / or Fig.30 An exemplary embodiment of the present invention stores HARQ information of a HARQ process and / or stores received data in a HARQ buffer of a HARQ process.

[0387] In an exemplary embodiment, the wireless device may be based on the Fig. 22 The exemplary embodiment described herein may be used to deactivate the active BWP. The wireless device may flush the HARQ buffer of the MBS in response to deactivating the active BWP. When the MBS-specific BWP is deactivated, the wireless device may flush the HARQ buffer of the MBS.

[0388] like Fig.36As shown, the wireless device may determine whether a HARQ process belongs to a first HARQ process group or to one or more second HARQ process groups.

[0389] In response to the HARQ process belonging to the first HARQ process group, the wireless device may determine that the first TB is an initial transmission or a retransmission of a unicast TB. The wireless device may, for example, implement Fig.30 In the described exemplary embodiment, it is determined whether the first TB is an initial transmission or a retransmission of a unicast TB based on the NDI value of the DCI. In response to the HARQ process belonging to the first HARQ process group, the wireless device can determine whether the NDI is switched based on the NDI value of the DCI and the stored NDI value of the same HARQ process. In response to the NDI being switched, the wireless device can determine that the data received in the first PDSCH resource is a new (or initial) transmission of the first TB. The wireless device can decode the received data of the first TB. In response to the NDI not being switched, the wireless device can determine that the data received in the first PDSCH resource is a retransmission of the first TB previously received. The wireless device can combine the data received in the first PDSCH resource and the data previously stored in the HARQ buffer. The wireless device can decode the combined data of the first TB.

[0390] In response to the HARQ process belonging to one or more second HARQ process groups, the wireless device may determine that the first TB is a unicast retransmission of the MBS TB. In response to the HARQ process belonging to one or more second HARQ process groups, the wireless device may determine that the NDI is not switched, regardless of the NDI value of the DCI. Based on the NDI not being switched, the wireless device may combine the received data in the first PDSCH and the buffered data of the MBS TB. The wireless device may decode the combined data of the MBS TB.

[0391] Fig.32 , Fig.33 , Fig.34 , Fig.35 and / or Fig.36 The exemplary embodiments of can be combined into an embodiment. In the example, the base station can be based on the above relative to Fig.32 The exemplary embodiments described herein can be used to configure (e.g., based on an indication of wireless device capabilities or no indication of wireless device capabilities) the retransmission type (or mode) of the MBS TB. Based on the retransmission type, the base station can, for example, configure the retransmission type (or mode) of the MBS TB based on the above with respect to Fig.33 The exemplary embodiment described groups multiple HARQ processes into a first HARQ process associated with an MBS session and a second HARQ process associated with a unicast transmission. Based on the configured retransmission type and / or grouping of multiple HARQ processes, the wireless device may perform the following steps based on the above with respect to Fig.34 and / or Fig.36The described exemplary embodiments determine the receipt of a retransmission of an MBS TB.

[0392] In an example, the wireless device may be based on the above relative Fig.34 The exemplary embodiment described above receives a group common DCI indicating a multicast transmission of the first data of the TB. The group common DCI may indicate the first HARQ process index. Fig.33 In the exemplary embodiment described, the first HARQ process index may belong to a first HARQ process index group among a plurality of HARQ process index groups. The first HARQ process index group may be exclusively associated with MBS transmission. The wireless device may determine that the first data of a TB is associated with a multicast transmission of an MBS session (which may be referred to as a multicast TB in this specification) based on the first HARQ process index belonging to the first HARQ process index group. The wireless device may determine that the first data of a TB is associated with a multicast transmission of an MBS session based on the first HARQ process index not belonging to a HARQ process index group associated with a unicast transmission.

[0393] In the example, based on the above relative to Fig.34 In the described example embodiments, in response to a failure to decode a multicast TB based on the first data, the wireless device may transmit negative HARQ feedback.

[0394] In an example, the wireless device may be based on the above relative Fig.34 The exemplary embodiment described herein is used to receive a unicast DCI that schedules a unicast transmission of second data. The unicast DCI may include a second HARQ process index and a second NDI value. The wireless device may determine whether the second HARQ process index belongs to the first HARQ process index group or the second HARQ process index group based on, for example, the above relative to Fig.36 The described exemplary embodiments determine whether a unicast DCI schedules a unicast TB or schedules a retransmission of a multicast TB.

[0395] In an example, in response to the second HARQ process index of the unicast DCI belonging to a second HARQ process index group associated with a unicast transmission, the wireless device may determine that the second data is for a unicast TB. The wireless device may decode the unicast TB based on the second data. The wireless device may not combine the second data with the first data to decode the unicast TB or to decode the multicast TB.

[0396] In an example, in response to the second HARQ process index of the unicast DCI belonging to the first HARQ process index group associated with the MBS transmission, the wireless device may determine whether the second data is for retransmission of the multicast TB based on at least one of the following: whether the second HARQ process index of the unicast DCI is the same as the first HARQ process of the multicast DCI, whether the second NDI of the unicast DCI is the same as the first NDI of the multicast DCI, for example, based on the above with respect to Fig.34 An exemplary embodiment described. In the example, the wireless device may determine that the second data is used for retransmission of a multicast TB based on at least one of the following: the second HARQ process index of the unicast DCI is the same as the first HARQ process of the multicast DCI, and the second NDI of the unicast DCI is the same as the first NDI of the multicast DCI. In the example, the wireless device may determine that the second data is used for initial transmission of a second multicast TB based on at least one of the following: the second HARQ process index of the unicast DCI is different from the first HARQ process of the multicast DCI, and the second NDI of the unicast DCI is different from the first NDI of the multicast DCI. The second HARQ process index may belong to the first HARQ process index group associated with the MBS transmission. The second HARQ process index may not belong to the second HARQ process index group associated with the unicast transmission. The exemplary embodiment can improve the power consumption of the wireless device, and / or the system throughput of the base station for MBS transmission.

[0397] In an exemplary embodiment, the wireless device may receive a first DCI from a base station and based on an MBS identifier, the first DCI indicating the transmission of an MBS TB of an MBS session. Based on the first DCI, the wireless device may receive first data of an MBS TB associated with a HARQ process. The wireless device may transmit negative feedback to the MBS TB. The wireless device may receive second data based on a second DCI with a second identifier, the second DCI including an NDI value and a HARQ process identifier. In response to a CRC bit of the second DCI indicating the HARQ process identifier of the HARQ process and scrambled by the second identifier, the wireless device may determine that the NDI of the HARQ process has not been switched, regardless of the NDI value of the second DCI. Based on the NDI not being switched, the wireless device may decode the MBS TB based on a combination of the first data and the second data.

[0398] In an exemplary embodiment, the wireless device may receive configuration parameters of a bandwidth portion of a cell from a base station, wherein the configuration parameters indicate an MBS identifier having an MBS session and a second identifier associated with the wireless device.

[0399] In an exemplary embodiment, in response to unsuccessful decoding of the MBS TB, the wireless device may transmit negative feedback for the MBS TB via uplink control channel resources.

[0400] In an exemplary embodiment, the second identifier may be a C-RNTI associated with the wireless device.The MBS identifier may be an MBS-RNTI associated with the MBS session.

[0401] In an exemplary embodiment, the wireless device may receive a first DCI in a first search space configured for an MBS session on a BWP of a cell. The wireless device may receive a second DCI in a second search space configured for the wireless device to receive a unicast PDCCH on a BWP of a cell.

[0402] In an exemplary embodiment, the wireless device may monitor the PDCCH via the second search space based on the second identifier.The wireless device may store the first data in a HARQ buffer associated with the HARQ process.

[0403] In an exemplary embodiment, the first data of the MBS TB may be scrambled by the MBS identifier. The second data of the MBS TB may be scrambled by the MBS identifier or the second identifier.

[0404] In an exemplary embodiment, the MBS TB may be transmitted to a group of wireless devices configured with an MBS session. The group of wireless devices may be configured with an MBS identifier based on the group of wireless devices subscribing to the MBS session.

[0405] In an exemplary embodiment, the wireless device may be configured with an MBS identifier based on the wireless device subscribing to an MBS session. The wireless device may transmit MBS interest information to a base station indicating that the wireless device is interested in the MBS session. The wireless device may receive an MBS command instructing the base station to start the MBS session. The wireless device may monitor the PDCCH of the first DCI based on the MBS start command.

[0406] In an exemplary embodiment, in response to successfully decoding the MBS TB based on a combination of the first data and the second data, the wireless device may skip transmitting a positive acknowledgement of the MBS TB. In response to successfully decoding the MBS TB based on a combination of the first data and the second data, the wireless device may transmit a positive acknowledgement of the MBS TB. In an exemplary embodiment, in response to unsuccessfully decoding the MBS TB based on a combination of the first data and the second data, the wireless device may transmit a negative acknowledgement of the MBS TB.

[0407] In an example, the wireless device may receive a retransmission type indication from a base station, the retransmission type indication indicating that the MBS TB is retransmitted in a PDSCH resource dedicated to the wireless device and / or the retransmission of the MBS TB is scheduled by a unicast DCI addressed to the wireless device. The retransmission type indication is included in at least one of the following: one or more radio resource control messages and / or the first DCI.

[0408] In an example, the wireless device may receive a configuration parameter from a base station indicating that a plurality of HARQ processes are grouped into a first HARQ process group for unicast transmission and a second HARQ process group for MBS transmission. The wireless device may receive a DCI indicating a transmission of first data of a TB associated with the HARQ process based on the C-RNTI. The wireless device may receive the first data of the TB associated with the HARQ process. In response to determining that the HARQ process belongs to the second HARQ process group, the wireless device may combine the first data with the buffered data of the TB. The wireless device may decode the TB based on combining the first data with the buffered data.

[0409] In an example, the DCI may include an NDI value and a HARQ process identifier identifying the HARQ process. The wireless device may determine that the NDI of the HARQ process is not switched, regardless of the NDI value of the DCI, based on determining that the HARQ process belongs to a second HARQ process group and that data is stored in a HARQ buffer associated with the HARQ process. The wireless device may determine that the NDI of the HARQ process is not switched, regardless of the NDI value of the DCI, based on determining that the second data of the TB is not successfully decoded, wherein the second data is scheduled by a second DCI with an MBS-RNTI, and the second DCI indicates the HARQ process. The wireless device may store the second data in the HARQ buffer of the HARQ process. The buffered data may be the stored second data.

Claims

1. A method, comprising: A parameter is received by a wireless device, the parameter indicating: a first search space (SS) in common frequency resources associated with a multicast transmission within a bandwidth part (BWP); as well as a second SS associated with unicast transmission in the BWP; receiving, via the first SS in the common frequency resources, group common downlink control information (DCI) scheduling first data of a transport block of the multicast transmission; receiving, via the second SS outside the common frequency resources and in the BWP, a unicast DCI scheduling second data for the unicast transmission; Determining that the second data is a retransmission of the transport block is based on: A first new data indication (NDI) of the group common DCI is the same as a second NDI of the unicast DCI; and The first process index of the group common DCI is the same as the second process index of the unicast DCI; as well as The first data and the second data are combined based on the determination to decode the transport block.

2. A method comprising: receiving, by the wireless device, group common downlink control information (DCI) scheduling first data of a transport block via a first search space (SS) in common frequency resources of a bandwidth part (BWP) and associated with a multicast transmission; receiving, via a second SS outside the common frequency resources and in the BWP, a unicast DCI scheduling second data; as well as Determining that the second data is a retransmission of the transport block is based on: The first process index of the group common DCI is the same as the second process index of the unicast DCI; and The first new data indication (NDI) of the group common DCI is the same as the second NDI of the unicast DCI.

3. A method comprising: receiving, by the wireless device, group common downlink control information (DCI) scheduling first data of a transport block via a first search space (SS) in common frequency resources of a bandwidth part (BWP) and associated with a multicast transmission; receiving, via a second SS in the BWP, a unicast DCI scheduling second data; as well as Based on the fact that the first process index of the group common DCI is the same as the second process index of the unicast DCI, it is determined that the second data is a retransmission of the transport block.

4. The method of any one of claims 2 to 3, wherein the second SS is outside the common frequency resource of the BWP.

5. The method of any one of claims 2 to 4, wherein the determination is based on the first process index being the same as the second process index, and a first new data indication (NDI) of the group common DCI being the same as a second NDI of the unicast DCI.

6. The method according to any one of claims 2 to 5, further comprising: Receives configuration parameters indicating: The first SS is in the common frequency resource associated with a multicast transmission within the BWP; and The second SS is associated with unicast transmission in the BWP. The method of claim 6 , wherein the transport block belongs to the multicast transmission.

8. The method according to any one of claims 5 to 7, wherein the second data belongs to the unicast transmission.

9. The method according to any one of claims 2 to 8, further comprising: The first data and the second data are combined based on the determination to decode the transport block.

10. The method of any one of claims 2 to 4 and 6 to 9, wherein the second data is determined as the retransmission of the transport block regardless of whether a second new data indication (NDI) value of the unicast DCI is the same as a first NDI value of the group common DCI.

11. The method of any one of claims 2 to 4 and 6 to 9, wherein the second data is determined as the retransmission of the transport block independent of the first NDI value of the group common DCI.

12. The method of any one of claims 2 to 11, wherein in the BWP, the unicast DCI is received via the second SS outside the common frequency resources associated with the multicast transmission.

13. The method of any one of claims 2 to 12, wherein determining the second data as the retransmission of the transport block is further based on: The group-common DCI is received in the first SS within the common frequency resources; and The unicast DCI is received in the second SS of the BWP.

14. The method of any one of claims 2 to 13, wherein the first process index is a Hybrid Acknowledgement Repeat Request (HARQ) process index identifying a HARQ process.

15. The method of any one of claims 2 to 14, wherein the group common DCI comprises a frequency domain resource allocation field indicating the number of one or more resource blocks (RBs) within the common frequency resources of the BWP.

16. The method of any one of claims 2 to 15, wherein the wireless device is in a radio resource control (RRC) connected state.

17. The method of any one of claims 2 to 16, wherein the multicast transmission comprises: The group common DCI is addressed to the plurality of wireless devices including the wireless device; as well as The transport blocks scheduled by the set common DCI are addressed to the plurality of wireless devices.

18. The method of any one of claims 9 to 17, further comprising: decoding the transport block based on the combining; as well as HARQ feedback for the transport block is transmitted based on the decoding.

19. The method of any one of claims 2 to 18, further comprising receiving, within the BWP, the first data of the transport block in the common frequency resources associated with the multicast transmission.

20. The method of any one of claims 2 to 19, further comprising receiving the second data via a unicast physical downlink shared channel (PDSCH) based on the unicast DCI.

21. The method of any one of claims 2 to 20, wherein the unicast PDSCH is located outside the common frequency resources and within the BWP.

22. The method of any one of claims 2 to 21, wherein the set of common DCIs having a first DCI format comprises: the first process index; First NDI value; as well as A frequency domain resource assignment field is provided, wherein the frequency domain resource assignment field indicates a group common PDSCH resource used for the first data in the common frequency resource associated with the multicast transmission.

23. The method of any one of claims 2 to 22, wherein the unicast DCI having a second DCI format comprises: the second process index; Second NDI value; as well as A frequency domain resource assignment field indicating a unicast PDSCH resource of the BWP of the second data, wherein the second DCI format is different from the first DCI format of the group common DCI.

24. The method of any one of claims 2 to 23, further comprising receiving one or more radio resource control (RRC) messages including a first parameter indicating one or more retransmission modes for the multicast transmission, wherein the one or more retransmission modes include at least one of: a first mode indicating that the retransmission of the transport block of the multicast transmission is scheduled by the unicast DCI, wherein the unicast DCI is received in the BWP; and A second mode, the second mode indicating that the retransmission of the transport block of the multicast transmission is scheduled by a second set of common DCI, wherein the second set of common DCI is received within the common frequency resources of the multicast transmission.

25. The method of claim 24, wherein the second data is determined as the retransmission of the transport block further based on the first parameter indicating the first mode.

26. The method of any one of claims 24 to 25, further comprising transmitting, by the wireless device, a capability message comprising a capability parameter indicating that the wireless device supports the first mode, wherein the first mode indicates that the retransmission of the transport block of the multicast transmission is scheduled by the unicast DCI.

27. The method of claim 26, further comprising decoding the transport block based on supporting the first mode based on a combination of: the first data of the transport block, wherein CRC bits are scrambled by a first RNTI; and The second data of the transport block, wherein CRC bits are scrambled by a second RNTI, wherein the second RNTI is different from the first RNTI.

28. The method of any one of claims 2 to 27, further comprising receiving one or more RRC messages including configuration parameters of a multicast and broadcast service (MBS) session associated with the multicast transmission, wherein the configuration parameters include at least one of: a first radio network temporary identifier (RNTI) for receiving the set common DCI and the transport block; one or more sets of control resources associated with the multicast transmission in the common frequency resources of the BWP; and The first SS is associated with the multicast transmission in the common frequency resources of the BWP.

29. The method of claim 28, further comprising monitoring a group common physical downlink control channel (PDCCH) via the first SS in the one or more control resource sets of the common frequency resources for receiving the group common DCI.

30. The method of any one of claims 2 to 29, further comprising: receiving the first data of the transport block based on the first group common DCI and via a group common PDSCH resource of the common frequency resources; decoding the transport block based on the first data; as well as Transmitting HARQ feedback for the transport block.

31. The method of claim 30, wherein the HARQ feedback comprises: positive feedback in response to the transport block being successfully decoded; as well as Negative feedback in response to the transport block being unsuccessfully decoded.

32. The method of any one of claims 2 to 31, wherein the second data is determined as the retransmission of the transport block further based on a decoding failure of the first data of the transport block scheduled by the group common DCI.

33. The method of claim 32, further comprising transmitting a negative acknowledgement for the transport block, the negative acknowledgement indicating a decoding failure for the first data of the transport block.

34. The method of claim 33, wherein the unicast DCI is received after transmitting the negative acknowledgement for the transport block.

35. The method of any one of claims 2 to 34, further comprising receiving one or more RRC messages, the one or more RRC messages comprising a configuration parameter, the configuration parameter indicating: The first SS is configured in the common frequency resources associated with multicast transmission within the BWP; and The second SS is associated with unicast transmission in the BWP.

36. The method of claim 35, wherein the second SS is configured outside the common frequency resource.

37. A method as claimed in any one of claims 35 to 36, wherein the configuration parameter indicates: a first set of control resources associated with the first SS of the multicast transmission in the common frequency resources; and A second set of control resources associated with the second SS of the unicast transmission in the BWP.

38. The method of claim 37, wherein the second set of control resources is configured outside the common frequency resources.

39. The method of any one of claims 37 to 38, wherein: The group-common DCI is received in the first SS associated with the first set of control resources; and The unicast DCI is received in the second SS associated with a second set of control resources.

40. The method of any one of claims 2 to 39, further comprising receiving one or more RRC messages, the one or more RRC messages comprising a configuration parameter, the configuration parameter indicating: a first RNTI associated with the multicast transmission; and A second RNTI associated with the unicast transmission.

41. The method of claim 40, wherein the first RNTI is different from the second RNTI.

42. The method of any one of claims 40 to 41, wherein the set common DCI is received scrambled by the first RNTI based on cyclic redundancy check (CRC) bits of the set common DCI.

43. The method of any one of claims 40 to 42, further comprising receiving the first data of the transport block scrambled by the first RNTI based on CRC bits of the first data.

44. The method of any one of claims 40 to 43, wherein the unicast DCI is received scrambled by the second RNTI based on CRC bits of the unicast DCI.

45. The method of any one of claims 40 to 44, further comprising receiving the second data scrambled by the second RNTI based on CRC bits of the second data.

46. ​​The method of any one of claims 40 to 45, further comprising decoding the transport block based on the determination based on a combination of: The first data having CRC bits in the first data is scrambled by the first RNTI; and The second data having CRC bits in the second data is scrambled by the second RNTI.

47. The method of any one of claims 2 to 46, further comprising receiving one or more RRC messages, the one or more RRC messages comprising a configuration parameter indicating a plurality of process indexes, the plurality of process indexes comprising: a first set of process indices associated with the multicast transmission, including the first process index; as well as A second set of process indices associated with the unicast transmission, wherein the first set of process indices does not include any process indices of the second set of process indices.

48. The method of claim 47, wherein the second data is determined to be a retransmission of the transport block further based on the second process index of the unicast DCI belonging to the first process index set, and wherein the second process index is the same as the first process index.

49. The method of any one of claims 47 to 48, wherein the second data is determined to be a retransmission of the transport block further based on the second process index of the unicast DCI not belonging to the second process index set.

50. The method of any one of claims 47 to 49, further comprising receiving a second unicast DCI scheduling third data and comprising a third process index.

51. The method of claim 50, further comprising determining that the third data is a unicast transmission of the second transmission block based on: The third process index does not belong to the first process index set; and The third process index belongs to the second process index set.

52. The method of claim 51, further comprising decoding the third data of the second transport block of the unicast transmission based on determining that the third data is the unicast transmission of the second transport block.

53. The method of any one of claims 6 to 52, wherein the configuration parameters are received in one or more RRC messages, the one or more RRC messages indicating that a cell includes a plurality of BWPs including the BWP, and wherein each of the plurality of BWPs: Identified by the BWP identifier; comprising one or more RBs of the cell; and Associated with BWP specific parameter set parameters including subcarrier spacing and cyclic prefix length values.

54. The method of claim 53, wherein the BWP is an initial BWP of the plurality of BWPs for the cell.

55. The method of any one of claims 53 to 54, wherein the configuration parameter indicates that the common frequency resource and the BWP have: Same subcarrier spacing; and Same cyclic prefix length value.

56. The method of any one of claims 53 to 55, wherein the BWP is not a dormant BWP among the plurality of BWPs of the cell.

57. The method of any one of claims 53 to 56, wherein the cell is a primary cell among a plurality of cells.

58. The method of any one of claims 53 to 57, wherein the one or more RRC messages are wireless device specific RRC messages dedicated to the wireless device.

59. The method of any one of claims 53 to 58, further comprising activating the BWP of the plurality of BWPs of the cell.

60. The method of any one of claims 2 to 59, further comprising receiving the configuration parameters, the configuration parameters comprising: one or more first parameters, the one or more first parameters indicating a resource block (RB) of the BWP; as well as One or more second parameters, the one or more second parameters indicating a first RB among RBs of the BWP as the common frequency resource for the multicast transmission to a plurality of wireless devices.

61. The method of claim 60, wherein for the multicast transmission, the one or more second parameters indicate: a starting RB of the first RB; and The number of the first RBs.

62. The method of claim 61, wherein an RB in the RBs comprises one or more resource elements in the frequency domain.

63. The method of any one of claims 61 to 62, wherein the first RB is a subset of the RBs of the BWP.

64. The method according to any one of claims 61 to 63, wherein the one or more second parameters indicate a frequency offset value of the starting RB of the first RB relative to a frequency reference point of the cell.

65. The method of claim 64, wherein the frequency reference point of the cell is a center of a lowest subcarrier of a lowest RB among a plurality of RBs included in the cell.

66. A method comprising: A parameter is received by a wireless device, the parameter indicating: Common frequency resources for Multicast and Broadcast Service (MBS) sessions within a Bandwidth Part (BWP); a radio network temporary identifier (RNTI) associated with the MBS session; a first physical downlink shared channel (PDSCH) data scrambling identifier associated with the MBS session; as well as A second PDSCH data scrambling identifier associated with unicast transmission; receiving, based on the RNTI and via the common frequency resources, group common downlink control information (DCI) scheduling a transport block for the MBS session; Based on the group common DCI being received based on the RNTI, selecting the first PDSCH data scrambling identifier from the first PDSCH data scrambling identifier and the second PDSCH data scrambling identifier; The transport block is received via the common frequency resource based on scrambling the transport block with a scrambling sequence, wherein the scrambling sequence is initialized by: the selected first PDSCH data scrambling identifier; and The RNTI.

67. A method comprising: A parameter is received by a wireless device, the parameter indicating: The Radio Network Temporary Identifier (RNTI) associated with a Multicast and Broadcast Service (MBS) session; a first scrambling identifier associated with the MBS session; as well as a second scrambling identifier associated with the unicast transmission; receiving group common downlink control information (DCI) scheduling a transport block for the MBS session based on the RNTI; Based on the group common DCI being received based on the RNTI, selecting the first scrambling identifier from the first scrambling identifier and the second scrambling identifier; The transport block is received based on the transport block being scrambled with a scrambling sequence, wherein the scrambling sequence is initialized by: a selected first scrambling identity; and The RNTI.

68. The method of claim 67, wherein the first scrambling identifier comprises a first physical downlink shared channel (PDSCH) data scrambling identifier, and wherein the second scrambling identifier comprises a second PDSCH data scrambling identifier.

69. The method of any one of claims 67 to 68, wherein the parameter further indicates a common frequency resource for the MBS session within a bandwidth part (BWP).

70. The method of claim 69, wherein the set of common DCI is received via the common frequency resources, and wherein the transport block is received via the common frequency resources.

71. A method comprising: One or more messages including parameters for a multicast and broadcast service (MBS) session are received by a wireless device, the parameters indicating: Radio Network Temporary Identifier (RNTI); and a data scrambling identity associated with a group common physical downlink shared channel (PDSCH); receiving group common downlink control information (DCI) for scheduling transport blocks (TBs) based on the RNTI; receiving data for the TB via a first group common PDSCH and based on the group common DCI; and The TB is decoded based on the scrambling sequence of the data by initializing: The data scrambling identifier; and The RNTI.

72. The method of any one of claims 67 to 71, wherein the group-common DCI comprises a frequency-domain resource allocation field indicating a number of one or more resource blocks (RBs) of the first group-common PDSCH, wherein: The number of the one or more RBs is within a common frequency resource associated with the MBS session; and The common frequency resources are contained in a bandwidth part (BWP).

73. The method of any one of claims 67 to 72, wherein the wireless device is in a radio resource control (RRC) connected state.

74. The method of any one of claims 67 to 73, wherein: The group common DCI is addressed to a plurality of wireless devices including the wireless device; and The TBs scheduled by the group common DCI are addressed to the plurality of wireless devices.

75. The method of any one of claims 67 to 74, wherein the data of the TBs are received in a common frequency resource associated with an MBS session within a BWP.

76. The method of any one of claims 67 to 75, wherein the set of common DCIs comprises: Hybrid Acknowledgement Repeat Request (HARQ) process index; New Data Indicator (NDI) value; as well as A frequency domain resource assignment field, wherein the frequency domain resource assignment field indicates a first set of common PDSCH resources in the common frequency resources of the TB associated with the MBS session.

77. The method of any one of claims 67 to 76, wherein the group common DCI is received based on cyclic redundancy check (CRC) bits of the group common DCI being scrambled by the RNTI.

78. The method of any one of claims 67 to 77, wherein the parameters further include at least one of the following: one or more control resource sets associated with the MBS session in common frequency resources of the BWP; and A search space (SS) associated with the MBS session in the common frequency resources of the BWP.

79. The method of claim 78, further comprising monitoring a group common physical downlink control channel (PDCCH) via the SS in the one or more control resource sets of the common frequency resources for receiving the group common DCI.

80. The method of any one of claims 67 to 79, wherein the one or more messages indicate: The first SS is configured in a common frequency resource associated with the MBS session within the BWP; and A second SS associated with unicast transmission is configured outside the common frequency resources and in the BWP.

81. The method of claim 80, wherein the one or more messages indicate: a first set of control resources associated with the first SS for the MBS session in the common frequency resources; and A second set of control resources is associated with the second SS of the unicast transmission outside the common frequency resources and in the BWP.

82. The method of claim 81, wherein the group-common DCI is received in the first SS associated with the first set of control resources.

83. The method of any one of claims 67 to 82, wherein the one or more messages indicate a second RNTI associated with a unicast transmission.

84. The method of claim 83, wherein the second RNTI is different from the RNTI.

85. The method of any one of claims 83 to 84, further comprising receiving a unicast DCI scrambled by the second RNTI based on CRC bits of the unicast DCI.

86. The method of any one of claims 83 to 84, wherein the unicast DCI is received in a second SS associated with a second set of control resources.

87. The method of any one of claims 83 to 86, further comprising receiving second data for a second TB based on the unicast DCI.

88. The method of claim 87, further comprising initializing decoding of the second TB based on a second scrambling sequence of the second data by: a second data scrambling identifier associated with the unicast transmission; and The second RNTI.

89. The method of claim 88, wherein the second data scrambling identity is different from the data scrambling identity associated with the group common PDSCH.

90. The method of any one of claims 67 to 89, wherein the one or more messages indicate that the cell comprises a plurality of BWPs, wherein each BWP in the plurality of BWPs: Identified by the BWP identifier; comprising one or more RBs of the cell; and Associated with BWP specific parameter set parameters including subcarrier spacing and cyclic prefix length values.

91. The method of claim 90, wherein the cell is a primary cell among a plurality of cells.

92. The method of any one of claims 90 to 91, wherein the one or more messages are one or more wireless device-specific RRC messages dedicated to the wireless device.

93. The method of any one of claims 90 to 92, wherein the set of common DCI is received via a BWP, wherein the BWP is an initial BWP of the plurality of BWPs for the cell.

94. The method of claim 93, further comprising activating the BWP of the plurality of BWPs of the cell.

95. The method of any one of claims 93 to 94, wherein the BWP is not a dormant BWP among the plurality of BWPs of the cell.

96. The method of any one of claims 67 to 95, wherein the one or more messages include: one or more first parameters, the one or more first parameters indicating a resource block (RB) of the BWP; as well as One or more second parameters, the one or more second parameters indicating a first RB among RBs of the BWP as a common frequency resource for the MBS session to a plurality of wireless devices.

97. The method of claim 96, wherein for the MBS session, the one or more second parameters indicate: a starting RB of the first RB; and The number of the first RBs.

98. The method of claim 97, wherein an RB in the RBs comprises one or more resource elements in the frequency domain.

99. The method of any one of claims 97 to 98, wherein the first RB is a subset of the RBs of the BWP.

100. The method as claimed in any one of claims 97 to 99, wherein the one or more second parameters indicate a frequency offset value of the starting RB of the first RB relative to a frequency reference point of the cell.

101. The method of claim 100, wherein the frequency reference point of the cell is a center of a lowest subcarrier of a lowest RB among a plurality of RBs included in the cell.

102. A wireless device, the wireless device comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the wireless device to perform a method as claimed in any one of claims 1 to 101.

103. A non-transitory computer-readable storage medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 101.

104. A method comprising: transmitting, from the base station to the wireless device, group common downlink control information (DCI) scheduling first data of a transport block via a first search space (SS) in common frequency resources of a bandwidth part (BWP) and associated with a multicast transmission; receiving a negative acknowledgment corresponding to the transport block from the wireless device; as well as and transmitting, via a second SS outside the common frequency resources and in the BWP, a unicast DCI scheduling second data, wherein the second data is a retransmission of the transport block based on: The first process index of the group common DCI is the same as the second process index of the unicast DCI; and The first new data indication (NDI) of the group common DCI is the same as the second NDI of the unicast DCI.

105. A method comprising: transmitting, from the base station to the wireless device, group common downlink control information (DCI) scheduling first data of a transport block via a first search space (SS) in common frequency resources of a bandwidth part (BWP) and associated with a multicast transmission; receiving a negative acknowledgement corresponding to the transport block from the wireless device; and Based on the second process index of the unicast DCI being the same as the first process index of the group common DCI, the unicast DCI scheduling second data is transmitted via a second SS outside the common frequency resources and in the BWP, wherein the second data is a retransmission of the transport block.

106. The method of any one of claims 104 to 105, wherein the second SS is outside the common frequency resources of the BWP.

107. The method of any one of claims 104 to 106, wherein the second data is the retransmission further based on that the first process index is the same as the second process index, and the first new data indication (NDI) of the group common DCI is the same as the second NDI of the unicast DCI.

108. The method of any one of claims 104 to 107, further comprising: Transfers configuration parameters that indicate: The first SS is in the common frequency resource associated with a multicast transmission within the BWP; and The second SS is associated with unicast transmission in the BWP.

109. The method of claim 108, wherein the transport block belongs to the multicast transmission.

110. The method of any one of claims 107 to 109, wherein the second data belongs to the unicast transmission.

111. The method of any one of claims 104 to 110, further comprising: The first data and the second data of the transmission block are combined based on the second data as the transmission.

112. A method as described in any one of claims 104 to 106 and 108 to 111, wherein the second data is the retransmission of the transport block, regardless of whether the second new data indication (NDI) value of the unicast DCI is the same as the first NDI value of the group common DCI.

113. The method of any one of claims 104 to 106 and 108 to 111, wherein the second data is the retransmission of the transport block independent of the first NDI value of the group common DCI.

114. The method of any one of claims 104 to 113, wherein in the BWP, the unicast DCI is transmitted via the second SS outside the common frequency resources associated with the multicast transmission.

115. The method of any one of claims 104 to 114, wherein the second data is the retransmission of the transport block, further based on: The group-common DCI is transmitted in the first SS within the common frequency resource; and The unicast DCI is transmitted in the second SS of the BWP.

116. The method of any one of claims 104 to 115, wherein the first process index is a hybrid acknowledgement repeat request (HARQ) process index identifying a HARQ process.

117. The method of any one of claims 104 to 116, wherein the group common DCI comprises a frequency domain resource allocation field indicating a number of one or more resource blocks (RBs) within the common frequency resources of the BWP.

118. The method of any one of claims 104 to 117, wherein the wireless device is in a radio resource control (RRC) connected state.

119. The method of any one of claims 104 to 118, wherein the multicast transmission comprises: The group common DCI is addressed to the plurality of wireless devices including the wireless device; as well as The transport blocks scheduled by the set common DCI are addressed to the plurality of wireless devices.

120. The method of any one of claims 111 to 119, further comprising: transmitting the transport block based on the combination; as well as HARQ feedback is received for the transport block based on the decoding.

121. The method of any one of claims 104 to 120, further comprising transmitting, within the BWP, the first data of the transport block in the common frequency resources associated with the multicast transmission.

122. The method of any one of claims 104 to 121, further comprising transmitting the second data via a unicast physical downlink shared channel (PDSCH) based on the unicast DCI.

123. The method of any one of claims 104 to 122, wherein the unicast PDSCH is located outside the common frequency resources and within the BWP.

124. The method of any one of claims 104 to 123, wherein the set of common DCIs having a first DCI format comprises: the first process index; First NDI value; as well as A frequency domain resource assignment field is provided, wherein the frequency domain resource assignment field indicates a group common PDSCH resource used for the first data in the common frequency resource associated with the multicast transmission.

125. The method of any one of claims 104 to 124, wherein the unicast DCI having a second DCI format comprises: the second process index; Second NDI value; as well as A frequency domain resource assignment field indicating a unicast PDSCH resource of the BWP of the second data, wherein the second DCI format is different from the first DCI format of the group common DCI.

126. The method of any one of claims 104 to 125, further comprising transmitting one or more radio resource control (RRC) messages including a first parameter indicating one or more retransmission modes for the multicast transmission, wherein the one or more retransmission modes include at least one of: a first mode indicating that the retransmission of the transport block of the multicast transmission is scheduled by the unicast DCI, wherein the unicast DCI is received in the BWP; and A second mode, the second mode indicating that the retransmission of the transport block of the multicast transmission is scheduled by a second set of common DCI, wherein the second set of common DCI is received within the common frequency resources of the multicast transmission.

127. The method of claim 126, wherein further based on the first parameter indicating the first mode, the second data is the retransmission of the transport block.

128. The method as described in any one of claims 126 to 127 further includes receiving a capability message including a capability parameter indicating that the wireless device supports the first mode from the wireless device, wherein the first mode indicates that the retransmission of the transmission block of the multicast transmission is scheduled by the unicast DCI.

129. The method of claim 128, further comprising transmitting the transport block based on a combination of: the first data of the transport block, wherein CRC bits are scrambled by a first RNTI; and The second data of the transport block, wherein CRC bits are scrambled by a second RNTI, wherein the second RNTI is different from the first RNTI.

130. The method of any one of claims 104 to 129, further comprising transmitting one or more RRC messages including configuration parameters of a multicast and broadcast service (MBS) session associated with the multicast transmission, wherein the configuration parameters include at least one of: a first radio network temporary identifier (RNTI) for receiving the set common DCI and the transport block; one or more sets of control resources associated with the multicast transmission in the common frequency resources of the BWP; and The first SS is associated with the multicast transmission in the common frequency resources of the BWP.

131. The method of claim 130, further comprising transmitting the group common DCI in a group common physical downlink control channel (PDCCH) via the first SS in the one or more control resource sets of the common frequency resources, which is monitored by the wireless device for receiving the group common DCI.

132. The method of any one of claims 104 to 131, further comprising: transmitting the first data of the transport block based on the first group common DCI and via a group common PDSCH resource of the common frequency resources; transmitting the transport block based on the first transmission; as well as A HARQ feedback is received for the transport block.

133. The method of claim 132, wherein the HARQ feedback comprises: positive feedback in response to the transport block being successfully decoded; as well as Negative feedback in response to the transport block being unsuccessfully decoded.

134. The method of any one of claims 104 to 133, wherein the second data is the retransmission of the transport block further based on a failure by the wireless device to decode the first data of the transport block scheduled by the group common DCI.

135. The method of claim 134, further comprising receiving a negative acknowledgement for the transport block from the wireless device, the negative acknowledgement indicating a decoding failure for the first data of the transport block.

136. The method of claim 135, wherein the unicast DCI is transmitted after receiving the negative acknowledgement for the transport block.

137. The method of any one of claims 104 to 136, further comprising transmitting one or more RRC messages, the one or more RRC messages comprising a configuration parameter, the configuration parameter indicating: The first SS is configured in the common frequency resources associated with multicast transmission within the BWP; and The second SS is associated with unicast transmission in the BWP.

138. The method of claim 137, wherein the second SS is configured outside the common frequency resource.

139. The method of any one of claims 137 to 138, wherein the configuration parameter indicates: a first set of control resources associated with the first SS of the multicast transmission in the common frequency resources; and A second set of control resources associated with the second SS of the unicast transmission in the BWP.

140. The method of claim 139, wherein the second set of control resources is configured outside the common frequency resources.

141. The method of any one of claims 139 to 140, wherein: The group-common DCI is received in the first SS associated with the first set of control resources; and The unicast DCI is received in the second SS associated with a second set of control resources.

142. The method of any one of claims 104 to 141, further comprising transmitting one or more RRC messages, the one or more RRC messages comprising a configuration parameter, the configuration parameter indicating: a first RNTI associated with the multicast transmission; and A second RNTI associated with the unicast transmission.

143. The method of claim 142, wherein the first RNTI is different from the second RNTI.

144. The method of any one of claims 142 to 143, wherein the group common DCI is transmitted scrambled by the first RNTI based on cyclic redundancy check (CRC) bits of the group common DCI.

145. The method of any one of claims 142 to 143, further comprising transmitting the first data of the transport block scrambled by the first RNTI based on CRC bits of the first data.

146. The method of any one of claims 142 to 145, wherein the unicast DCI is transmitted scrambled by the second RNTI based on CRC bits of the unicast DCI.

147. The method of any one of claims 142 to 146, further comprising transmitting the second data scrambled by the second RNTI based on CRC bits of the second data.

148. The method of any one of claims 142 to 147, further comprising transmitting the transport block based on the second data being the retransmission based on a combination of: The first data having CRC bits in the first data is scrambled by the first RNTI; and The second data having CRC bits in the second data is scrambled by the second RNTI.

149. The method of any one of claims 104 to 148, further comprising transmitting one or more RRC messages, the one or more RRC messages comprising a configuration parameter indicating a plurality of process indexes, the plurality of process indexes comprising: a first set of process indices associated with the multicast transmission, including the first process index; as well as A second set of process indices associated with the unicast transmission, wherein the first set of process indices does not include any process indices of the second set of process indices.

150. The method of claim 149, wherein further based on the second process index of the unicast DCI belonging to the first process index set, the second data is a retransmission of the transport block, and wherein the second process index is the same as the first process index.

151. The method of any one of claims 149 to 150, wherein further based on the second process index of the unicast DCI not belonging to the second process index set, the second data is a retransmission of the transport block.

152. The method of any one of claims 149 to 151, further comprising transmitting a second unicast DCI scheduling third data and comprising a third process index.

153. The method of claim 152, wherein the third data is a unicast transmission of the second transmission block based on: The third process index does not belong to the first process index set; and The third process index belongs to the second process index set.

154. The method of claim 153, further comprising transmitting the third data of the second transport block of the unicast transmission based on the third data being the unicast transmission of the second transport block.

155. The method of any one of claims 108 to 154, wherein the configuration parameters are transmitted in one or more RRC messages, the one or more RRC messages indicating that a cell includes a plurality of BWPs including the BWP, and wherein each of the plurality of BWPs: Identified by the BWP identifier; comprising one or more RBs of the cell; and Associated with BWP specific parameter set parameters including subcarrier spacing and cyclic prefix length values.

156. The method of claim 155, wherein the BWP is an initial BWP of the plurality of BWPs for the cell.

157. The method of any one of claims 155 to 156, wherein the configuration parameter indicates that the common frequency resource and the BWP have: Same subcarrier spacing; and Same cyclic prefix length value.

158. The method of any one of claims 155 to 157, wherein the BWP is not a dormant BWP among the plurality of BWPs of the cell.

159. The method of any one of claims 155 to 158, wherein the cell is a primary cell among a plurality of cells.

160. The method of any one of claims 155 to 159, wherein the one or more RRC messages are wireless device specific RRC messages dedicated to the wireless device.

161. The method of any one of claims 155 to 160, further comprising activating the BWP of the plurality of BWPs of the cell.

162. The method of any one of claims 104 to 161, further comprising transmitting the configuration parameters, the configuration parameters comprising: one or more first parameters, the one or more first parameters indicating a resource block (RB) of the BWP; as well as One or more second parameters, the one or more second parameters indicating a first RB among RBs of the BWP as the common frequency resource for the multicast transmission to a plurality of wireless devices.

163. The method of claim 162, wherein for the multicast transmission, the one or more second parameters indicate: a starting RB of the first RB; and The number of the first RBs.

164. The method of claim 163, wherein an RB in the RBs comprises one or more resource elements in the frequency domain.

165. The method of any one of claims 163 to 164, wherein the first RB is a subset of the RBs of the BWP.

166. The method of any one of claims 163 to 165, wherein the one or more second parameters indicate a frequency offset value relative to a frequency reference point of the cell.

167. The method of claim 166, wherein the frequency offset value belongs to the starting RB of the first RB.

168. The method of claim 167, wherein the frequency reference point of the cell is a center of a lowest subcarrier of a lowest RB among a plurality of RBs included in the cell.

169. A method comprising: A parameter is transmitted by a base station to a wireless device, the parameter indicating: The Radio Network Temporary Identifier (RNTI) associated with a Multicast and Broadcast Service (MBS) session; a first scrambling identifier associated with the MBS session; as well as a second scrambling identifier associated with the unicast transmission; transmitting group common downlink control information (DCI) scheduling a transport block for the MBS session based on the RNTI; Based on the group common DCI being transmitted based on the RNTI, selecting the first scrambling identifier from the first scrambling identifier and the second scrambling identifier; The transport block is transmitted by scrambling with a scrambling sequence based on the transport block, wherein the scrambling sequence is initialized by: a selected first scrambling identity; and The RNTI.

170. The method of claim 169, wherein the first scrambling identifier comprises a first physical downlink shared channel (PDSCH) data scrambling identifier, and wherein the second scrambling identifier comprises a second PDSCH data scrambling identifier.

171. The method of any one of claims 169 to 170, wherein the parameter further indicates a common frequency resource for the MBS session within a bandwidth part (BWP).

172. The method of claim 171, wherein the set of common DCI is transmitted via the common frequency resources, and wherein the transport block is transmitted via the common frequency resources.

173. A method comprising: One or more messages including parameters for a multicast and broadcast service (MBS) session are transmitted by a base station to a wireless device, the parameters indicating: Radio Network Temporary Identifier (RNTI); a data scrambling identity associated with a group common physical downlink shared channel (PDSCH); and transmitting a group common downlink control information (DCI) of a scheduled transport block (TB) based on the RNTI; and The data of the TB is transmitted via the first set of common PDSCHs based on: the group-common DCI; and The scrambling sequence of the data is initialized by: The data scrambling identifier; and The RNTI.

174. The method of any one of claims 169 to 173, wherein the group-common DCI comprises a frequency-domain resource allocation field indicating a number of one or more resource blocks (RBs) of the first group-common PDSCH, wherein: The number of the one or more RBs is within a common frequency resource associated with the MBS session; and The common frequency resources are contained in a bandwidth part (BWP).

175. The method of any one of claims 169 to 174, wherein the wireless device is in a radio resource control (RRC) connected state.

176. The method of any one of claims 169 to 175, wherein: The group common DCI is addressed to a plurality of wireless devices including the wireless device; and The TBs scheduled by the group common DCI are addressed to the plurality of wireless devices.

177. The method of any one of claims 169 to 176, wherein the data of the TBs are transmitted within a BWP in common frequency resources associated with an MBS session.

178. The method of any one of claims 169 to 177, wherein the set of common DCIs comprises: Hybrid Acknowledgement Repeat Request (HARQ) process index; New Data Indicator (NDI) value; as well as A frequency domain resource assignment field, wherein the frequency domain resource assignment field indicates a first set of common PDSCH resources in the common frequency resources of the TB associated with the MBS session.

179. The method of any one of claims 169 to 178, wherein the group common DCI is transmitted scrambled by the RNTI based on cyclic redundancy check (CRC) bits of the group common DCI.

180. The method of any one of claims 169 to 179, wherein the parameters further comprise at least one of: one or more control resource sets associated with the MBS session in common frequency resources of the BWP; and A search space (SS) associated with the MBS session in the common frequency resources of the BWP.

181. The method of claim 180, further comprising transmitting the group common DCI in a group common physical downlink control channel (PDCCH) via the SS in the one or more control resource sets of the common frequency resources, which is monitored by the wireless device for receiving the group common DCI.

182. The method of any one of claims 169 to 181, wherein the one or more messages indicate: The first SS is configured in a common frequency resource associated with the MBS session within the BWP; and A second SS associated with unicast transmission is configured outside the common frequency resources and in the BWP.

183. The method of claim 182, wherein the one or more messages indicate: a first set of control resources associated with the first SS for the MBS session in the common frequency resources; and A second set of control resources is associated with the second SS of the unicast transmission outside the common frequency resources and in the BWP.

184. The method of claim 183, wherein the group-common DCI is transmitted in the first SS associated with the first set of control resources.

185. The method of any one of claims 169 to 184, wherein the one or more messages indicate a second RNTI associated with a unicast transmission.

186. The method of claim 185, wherein the second RNTI is different from the RNTI.

187. The method of any one of claims 185 to 186, further comprising transmitting the unicast DCI scrambled by the second RNTI based on CRC bits of the unicast DCI.

188. The method of any one of claims 185 to 186, wherein the unicast DCI is transmitted in a second SS associated with a second set of control resources.

189. The method of any one of claims 185 to 188, further comprising transmitting second data of a second TB based on the unicast DCI.

190. The method of claim 189, further comprising transmitting the second TB by initializing based on a second scrambling sequence of the second data: a second data scrambling identifier associated with the unicast transmission; and The second RNTI.

191. The method of claim 190, wherein the second data scrambling identifier is different from the data scrambling identifier associated with the group common PDSCH.

192. The method of any one of claims 169 to 191, wherein the one or more messages indicate that the cell includes a plurality of BWPs, wherein each BWP in the plurality of BWPs: Identified by the BWP identifier; comprising one or more RBs of the cell; and Associated with BWP specific parameter set parameters including subcarrier spacing and cyclic prefix length values.

193. The method of claim 192, wherein the cell is a primary cell among a plurality of cells.

194. The method of any one of claims 192 to 193, wherein the one or more messages are one or more wireless device-specific RRC messages dedicated to the wireless device.

195. The method of any one of claims 192 to 194, wherein the group common DCI is received via a BWP, wherein the BWP is an initial BWP of the plurality of BWPs for the cell.

196. The method of claim 195, further comprising activating the BWP of the plurality of BWPs of the cell.

197. The method of any one of claims 195 to 196, wherein the BWP is not a dormant BWP among the plurality of BWPs of the cell.

198. The method of any one of claims 169 to 197, wherein the one or more messages include: one or more first parameters, the one or more first parameters indicating a resource block (RB) of the BWP; as well as One or more second parameters, the one or more second parameters indicating a first RB among RBs of the BWP as a common frequency resource for the MBS session to a plurality of wireless devices.

199. The method of claim 198, wherein for the MBS session, the one or more second parameters indicate: a starting RB of the first RB; and The number of the first RBs.

200. The method of claim 199, wherein an RB in the RBs comprises one or more resource elements in the frequency domain.

201. The method of any one of claims 199 to 200, wherein the first RB is a subset of the RBs of the BWP.

202. The method of any one of claims 199 to 201, wherein the one or more second parameters indicate a frequency offset value of the starting RB of the first RB relative to a frequency reference point of the cell.

203. The method of claim 202, wherein the frequency reference point of the cell is the center of a lowest subcarrier of a lowest RB among a plurality of RBs included in the cell.

204. A base station, the base station comprising: one or more processors; as well as A memory storing instructions which, when executed by the one or more processors, cause the base station to perform a method as claimed in any one of claims 104 to 203.

205. A non-transitory computer-readable storage medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 104 to 203.

206. A system, the system comprising: A base station, the base station comprising: one or more first processors and a first memory storing a first instruction, wherein the first instruction, when executed by the one or more first processors, causes the base station to: Transmits parameters indicating: a first search space (SS) in common frequency resources associated with a multicast transmission within a bandwidth part (BWP); and a second SS associated with unicast transmission in the BWP; transmitting, via the first SS in common frequency resources of the BWP and associated with a multicast transmission, group common downlink control information (DCI) scheduling first data of a transport block; receiving a negative acknowledgement corresponding to the transport block; and and transmitting, via a second SS outside the common frequency resources and in the BWP, a unicast DCI scheduling second data, wherein the second data is a retransmission of the transport block based on: The first process index of the group common DCI is the same as the second process index of the unicast DCI; and A first new data indication (NDI) of the group common DCI is the same as a second NDI of the unicast DCI; and A wireless device comprising: one or more second processors; and a second memory storing second instructions, the second instructions, when executed by the one or more second processors, causing the wireless device to: receiving the parameter from the base station; receiving the set of common DCI from the base station via the first SS in the common frequency resources; receiving the unicast DCI from the base station via the second SS outside the common frequency resources and in the BWP; Determining that the second data is a retransmission of the transport block is based on: The first NDI of the group common DCI is the same as the second NDI of the unicast DCI; and The first process index of the group common DCI is the same as the second process index of the unicast DCI; and The first data and the second data are combined based on the determination to decode the transport block.

207. A system, the system comprising: A base station, the base station comprising: one or more first processors and a first memory storing a first instruction, wherein the first instruction, when executed by the one or more first processors, causes the base station to: Transmits parameters indicating: The Radio Network Temporary Identifier (RNTI) associated with a Multicast and Broadcast Service (MBS) session; a first scrambling identity associated with the MBS session; and a second scrambling identifier associated with the unicast transmission; transmitting group common downlink control information (DCI) scheduling transport blocks for the MBS session based on the RNTI; and The transport block is transmitted by scrambling with a scrambling sequence based on the transport block, wherein the scrambling sequence is initialized by: a selected first scrambling identity; and the RNTI; and A wireless device comprising: one or more second processors; and a second memory storing second instructions, the second instructions, when executed by the one or more second processors, causing the wireless device to: receiving the parameter from the base station; receiving the group common DCI from the base station based on the RNTI; Based on the group common DCI being received based on the RNTI, selecting the first scrambling identifier from the first scrambling identifier and the second scrambling identifier; and The transport block is received based on the transport block being scrambled with the scrambling sequence, wherein the scrambling sequence is initialized by: a selected first scrambling identity; and The RNTI.

Images