Configured Grant-Based Small Data Transmission (CG-SDT) in RRC Inactive State

Abstract

A user equipment (UE) configured for multi-beam operation in a fifth generation new radio (5G-NR) system may decode a physical downlink control channel. When a DCI format for a configured grant-based small data transmission (SDT) (CG-SDT) is detected and a transport block (TB) is received on the corresponding physical downlink shared channel (PDSCH), the UE may assume that a demodulation reference signal (DM-RS) antenna port associated with PDCCH reception and a DM-RS antenna port associated with PDSCH reception are quasi-colocated (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT. During the CG-SDT, the UE may encode the PUCCH for transmission using the same spatial domain transmit filter as the last PUSCH transmission.

Description

[Technical field]

[0001] Claiming priority This application claims priority to U.S. Provisional Patent Application No. 63 / 169,602, filed April 1, 2021 [Reference No. AD5648-Z], U.S. Provisional Patent Application No. 63 / 181,067, filed April 28, 2021 [Reference No. AD6212-Z], U.S. Provisional Patent Application No. 63 / 250,161, filed September 29, 2021 [Reference No. AD9164-Z], and U.S. Provisional Patent Application No. 63 / 284,561, filed November 30, 2021 [Reference No. AE0625-Z], which are incorporated by reference in their entireties herein.

[0002] Technical Field Some embodiments relate to wireless communications. Some embodiments relate to wireless networks, including 3GPP (3rd Generation Partnership Project) and fifth generation (5G) networks, including 5G New Radio (NR) (or 5G-NR) networks. Some embodiments relate to sixth generation (6G) networks. Some embodiments relate to configured grant (CG) based small data transmission (SDT) (CG-SDT). [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. The use of 3GPP 5G NR systems is increasing with an increase in different types of devices communicating with various network devices. The penetration of mobile devices (user equipment or UE) in modern society continues to drive the demand for a wide variety of networked devices in many different environments. 5G NR wireless systems are coming and are expected to further improve speed, connectivity, and usability, with improved throughput, coverage, robustness, and reduced latency and operational and capital expenses. 5G-NR networks will continue to evolve based on 3GPP LTE-Advanced with additional potential new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions that deliver high speed and rich content and services. As current cellular network frequencies are saturated, higher frequencies such as millimeter wave (mmWave) frequencies can be beneficial due to their higher bandwidth. Summary of the Invention

[0004] One issue with configured grant (CG) based small data transmission (SDT) (CG-SDT) is multi-beam operation. [Brief description of the drawings]

[0005] [Figure 1A] FIG. 1A illustrates a network architecture in accordance with some embodiments. [Figure 1B] 1B and 1C are diagrams illustrating a non-roaming 5G system architecture according to some embodiments. [Figure 1C] 1B and 1C are diagrams illustrating a non-roaming 5G system architecture according to some embodiments. [Figure 2A] FIG. 2A illustrates a four-step RACH procedure in accordance with some embodiments. [Figure 2B] FIG. 2B illustrates a two-step RACH procedure in accordance with some embodiments. [Diagram 3] FIG. 3 is a diagram illustrating beam operation for PUSCH initial transmission in accordance with some embodiments. [Figure 4] FIG. 4 is a diagram illustrating beam operation in case of PUSCH retransmission according to some embodiments. [Diagram 5] FIG. 5 is a diagram illustrating beam operation for PDCCH / PDSCH and PUCCH transmissions according to some embodiments. [Figure 6] FIG. 6 is a diagram illustrating validation of PUSCH occasions for CG-SDT when repetition for CG-PUSCH resources is configured according to some embodiments. [Figure 7] FIG. 7 is a diagram illustrating an example of an association between two SSBs and four DMRS resources according to some embodiments. [Figure 8] FIG. 8 is a diagram illustrating an example of association between four SSBs and four DMRS APs, according to some embodiments. [Figure 9] FIG. 9 illustrates a functional block diagram of a wireless communication device according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] The following description and drawings sufficiently illustrate certain embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for those of other embodiments. The embodiments set forth in the claims encompass all available equivalents of those claims.

[0007] Some embodiments are directed to the quasi-co-located (QCL) assumption for PDCCH / PDSCH transmission during CG-SDT operation. These embodiments are described in more detail below. Two antenna ports are said to be quasi-co-located if the characteristics of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried.

[0008] Some embodiments are directed to a user equipment (UE) configured for multi-beam operation in a fifth generation new radio (5G-NR) system. In these embodiments, the UE is configured to decode a physical downlink control channel (PDCCH). When a DCI format for a configured grant (CG)-based small data transmission (SDT) (CG-SDT) is detected and a transport block (TB) is received in a corresponding physical downlink shared channel (PDSCH), the UE may assume that a demodulation reference signal (DM-RS) antenna port associated with the PDCCH transmission and a DM-RS antenna port associated with the PDSCH transmission are quasi-colocated (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT. In these embodiments, during the CG-SDT, the UE may encode the PUCCH for transmission using the same spatial domain transmit filter as the last PUSCH transmission, although the scope of the embodiments is not limited in this respect. These embodiments are described in more detail below.

[0009] In these embodiments, if a DCI format for CG-SDT is detected, a quasi-co-location (QCL) relationship between the downlink reference signals (e.g., PDCCH, PDSCH, and SS / PBCH) and the demodulation reference signal (DM-RS) ports is assumed. In these embodiments, for the QCL assumption, the same TX beam is applied at the gNB for transmission of associated DM-RS for SSB / PDCCH / PDSCH and PDSCH / PDCCH. In some embodiments, the last PUSCH transmission may be scheduled by DCI. In some embodiments, the last PUSCH transmission is a CG-PUSCH that is not scheduled by DCI, although the scope of the embodiments is not limited in this respect.

[0010] In some embodiments, the detected DCI format includes DCI format 1_0 for CG-SDT. In some of these embodiments, when DCI format 1_0 or DCI format 1_1 for CG-SDT is detected, a QCL relationship between the downlink reference signal (e.g., PDCCH, PDSCH, and SS / PBCH) and the demodulation reference signal (DM-RS) port is assumed. In some embodiments, the DCI format may include a Cyclic Redundancy Check (CRC) scrambled by a Cell specific-Radio Network Temporary Identifier (C-RNTI) or scrambled by an RNTI, although the scope of the embodiments is not limited in this respect.

[0011] In some embodiments, there is an association between SSB resources and CG-PUSCH resources. In some embodiments, the UE may decode a CG-PUSCH configuration that indicates the number of SS / PBCH block indices that map to valid PUSCH occasions and associated DM-RS resources for transmission of the PUSCH. The UE may map the number of SS / PBCH block indices to valid PUSCH occasions and associated DM-RS resources first in ascending order of DM-RS port index and then in ascending order of DM-RS sequence index.

[0012] In some embodiments, if there is a set of associated DM-RS resources and PUSCH occasions that has not been mapped to an SS / PBCH block index after an integer number of SS / PBCH block indices for the associated DM-RS resource mapping cycle and PUSCH occasion within an association period, the UE may refrain from further mapping the SS / PBCH block index to a PUSCH occasion and set of associated DM-RS resources. The UE may also refrain from using the set of PUSCH occasions and associated DM-RS resources for any further PUSCH transmissions, although the scope of the embodiments is not limited in this respect.

[0013] In some embodiments, the association period is determined such that the pattern between PUSCH occasions and associated DM-RS resources and SS / PBCH block index is repeated at most every 640 ms.

[0014] In some embodiments, the UE may also encode a PUSCH for transmission during the CG-SDT (CG-PUSCH). The CG-PUSCH may be a direct data transmission performed by the UE when operating in an RRC_INACTIVE mode. In some embodiments, the transmission of the PUSCH in the CG-SDT is a direct data transmission performed without an associated PRACH preamble transmission, although the scope of the embodiments is not limited in this respect. In these embodiments, a four-step PRACH (Type 2) or two-step RACH (Type 1) procedure may not need to be performed since the timing advance (TA) is within the length of the cyclic prefix (CP) or varies only slightly depending on the deployment, although the scope of the embodiments is not limited in this respect.

[0015] In some embodiments, the DM-RS antenna port associated with PDCCH reception and the DM-RS antenna port associated with the PDSCH reception are assumed to be the SS / PBCH and QCL associated with a PUSCH in terms of Type-D properties including average gain and spatial receiver (RX) parameters, although the scope of embodiments is not limited in this respect.

[0016] In some embodiments, the DM-RS antenna port associated with PDSCH reception is assumed to be the SS / PBCH and QCL associated with the PUSCH with respect to Doppler shift, Doppler spread, average delay, and delay spread (i.e., Type A characteristics), although the scope of the embodiments is not limited in this respect.

[0017] In some embodiments, based on the assumption that the DM-RS antenna port associated with PDCCH reception is the SS / PBCH and QCL associated with the PUSCH resource for the CG-SDT, the UE may apply the same receive (RX) beam parameters as for synchronization signal block (SSB) reception, PDCCH reception, and PDSCH reception.

[0018] In some embodiments, to apply the same RX ray parameters, the UE may demodulate the PDSCH using the DM-RS based on the assumption that the DM-RS antenna port associated with the PDSCH reception is the SS / PBCH and QCL associated with the PUSCH resource for the CG-SDT. The UE may also demodulate the PDCCH using the DM-RS based on the assumption that the DM-RS antenna port associated with PDCCH reception is the SS / PBCH and QCL associated with the PUSCH resource for the CG-SDT. In some of these embodiments, the same spatial receive filter (QCL Type D property) may be applied for SSB reception, PDCCH reception, and PDSCH reception. In these embodiments, the UE uses the same Rx beam for SSB / PDCCH / PDSCH reception, although the scope of the embodiments is not limited in this respect.

[0019] Some embodiments are directed to a non-transitory computer-readable storage medium storing instructions for execution by a processing circuit of a user equipment (UE) configured for multi-beam operation in a fifth generation new radio (5G-NR) system. In these examples, the processing circuit may decode a physical downlink control channel (PDCCH), and when a DCI format for a configured grant (CG)-based small data transmission (SDT) (CG-SDT) is detected and a transport block (TB) is received on a corresponding physical downlink shared channel (PDSCH), the processing circuit may assume that a demodulation reference signal (DM-RS) antenna port associated with PDCCH reception and a DM-RS antenna port associated with PDSCH reception are quasi-co-located (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT. In these embodiments, during the CG-SDT, the processing circuit may encode the PUCCH for transmission using the same spatial domain transmit filter as the last PUSCH transmission, although the scope of the embodiments is not limited in this respect.

[0020] Some embodiments are directed to a gNodeB (gNB) configured for operation in a fifth generation new radio (5G-NR) system. In these embodiments, for a user equipment (UE) configured for multi-beam operation, the gNB may encode a physical downlink control channel (PDCCH) transmission (PDCCH transmission) and may encode a physical downlink shared channel (PDSCH) transmission including a transport block (TB) for transmission to the UE. In these embodiments, the PDCCH transmission may be encoded to carry a DCI format for a grant (CG)-based small data transmission (SDT) (CG-SDT) configured for detection by the UE along with the TB. In these embodiments, the gNB may configure a demodulation reference signal (DM-RS) antenna port associated with the PDCCH transmission and a DM-RS antenna port associated with the PDSCH transmission to quasi-co-locate (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT. In these embodiments, the gNB may decode a PUCCH during the CG-SDT transmitted by the UE. The UE may use the same spatial domain transmit filter as the last PUSCH transmission. In these embodiments, to decode the PUCCH during the CG-SDT, the gNB may assume that the UE used the same spatial domain transmit filter as the last PUSCH transmission, although the scope of the embodiments is not limited in this respect.

[0021] In some embodiments, a gNB may encode a CG-PUSCH configuration that indicates the number of SS / PBCH block indices that map to valid PUSCH occasions and associated DM-RS resources for transmission of PUSCH. The numbers of SS / PBCH block indices may be mapped to the valid PUSCH occasions and associated DM-RS resources first in ascending order of DM-RS port index and then in ascending order of DM-RS sequence index, although the scope of the embodiments is not limited in this respect.

[0022] In some embodiments, the gNB may determine the association period such that a pattern between PUSCH occasions and associated DM-RS resources and SS / PBCH block indexes is repeated up to every 640 ms, although the scope of the embodiments is not limited in this respect.

[0023] 1A is a diagram illustrating a network architecture according to some embodiments. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or other computing devices that include wired and / or wireless communication interfaces. UE 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0024] Any of the wireless links described herein (eg, as used in network 140A or any other illustrated network) may operate according to any example wireless communication technology and / or standard.

[0025] LTE and LTE-Advanced are standards for high-speed data wireless communications for UEs, such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique in which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used when one or more component carriers operate on unlicensed frequencies.

[0026] The embodiments described herein may be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in the 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and beyond frequencies, and Spectrum Access System (SAS) in the 3.55-3.7 GHz and beyond frequencies).

[0027] The embodiments described herein may also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), especially 3GPP New Radio (NR), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0028] In some embodiments, any of the UEs 101 and 102 may comprise Internet of Things (IoT) UEs or Cellular IoT (CIoT) UEs, which may comprise a network access layer designed for low-power IoT applications that utilize short-lived UE connections. In some embodiments, any of the UEs 101 and 102 may comprise Narrowband (NB) IoT UEs (e.g., Enhanced NB-IoT (eNB-IoT) UEs and Further Enhanced (FeNB-IoT) UEs, etc.). The IoT UEs may utilize technologies such as Machine-to-Machine (M2M) or Machine-Type Communication (MTC) to exchange data with MTC servers or devices over Public Land Mobile Networks (PLMNs), Proximity-Based Services (ProSe) or Device-to-Device (D2D) communications, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. The IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with temporary connections. The IoT UE may run background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0029] In some embodiments, any of the UEs 101 and 102 may include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0030] The UEs 101 and 102 may be configured to connect, for example, be communicatively coupled, to a Radio Access Network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS), a Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communication interface or layer (described in further detail below); in this example, connections 103 and 104 are shown as air interfaces for enabling communication coupling and may be consistent with cellular communication protocols such as Global System for Mobile Communications (GSM) protocols, Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, PTT over Cellular (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 3 GPP Long Term Evolution (LTE) protocols, Fifth Generation (5G) protocols, New Radio (NR) protocols, and the like.

[0031] In an aspect, the UEs 101 and 102 may further directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0032] The UE 102 is shown configured to access an access point (AP) 106 via a connection 107. The connection 107 may comprise a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, where the AP 106 may comprise a Wireless Fidelity (WiFi) router. In this example, the AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (described in more detail below).

[0033] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (AN) may be referred to as base stations (BS), Node Bs, evolved Node Bs (eNBs), next-generation Node Bs (gNBs), RAN nodes, etc., and may comprise terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some embodiments, the communication nodes 111 and 112 may be transmit / receive points (TRPs). If the communication nodes 111 and 112 are Node Bs (e.g., eNBs or gNBs), one or more TRPs may function within a communication cell of the Node B. The RAN 110 may include one or more RAN nodes for providing a macro cell, e.g., a macro RAN node 111, and one or more RAN nodes for providing a femto cell or a pico cell (e.g., a cell having a smaller coverage area, a smaller user capacity, or a higher bandwidth compared to a macro cell), e.g., a low power (LP) RAN node 112.

[0034] Either of the RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for the UEs 101 and 102. In some embodiments, either of the RAN nodes 111 and 112 may perform various logical functions for the RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and radio network controller (RNC) functions such as mobility management. In one example, either of the nodes 111 and / or 112 may be a new generation Node B (gNB), an evolved Node B (eNB), or another type of RAN node.

[0035] The RAN 110 is shown communicatively coupled to a Core Network (CN) 120 via an S1 interface 113. In an embodiment, the CN 120 may be an Evolved Packet Core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as described with reference to FIGS. 1B-1C ). In this aspect, the S1 interface 113 is split into two parts: an S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and a Serving Gateway (S-GW) 122, and an S1-Mobility Management Entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and the MME 121.

[0036] In this aspect, the CN 120 comprises an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be similar in function to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility embodiments in access, such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support network entity handling of communication sessions. The CN 120 may comprise one or more HSSs 124, depending on the number of mobile subscribers, equipment capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0037] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0038] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element that provides applications that use IP bearer resources in conjunction with a core network (e.g., UMTS Packet Service (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0039] The P-GW 123 may further be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0040] In some embodiments, the communication network 140A may be an IoT network or a 5G network, including a 5G new wireless network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is Narrowband IoT (NB-IoT).

[0041] The NG system architecture may include a RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 may include multiple nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., 5G Core Network or 5GC) may include an Access and Mobility Function (AMF) and / or a User Plane Function (UPF). The AMF and UPF may be communicatively coupled to the gNBs and NG-eNBs via an NG interface. More specifically, in some embodiments, the gNBs and NG-eNBs may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNBs and NG-eNBs may be coupled to each other via an Xn interface.

[0042] In some embodiments, the NG system architecture may use reference points between various nodes such as those provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some embodiments, in a 5G architecture, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN).

[0043] FIG. 1B illustrates a non-roaming 5G system architecture according to some embodiments. Referring to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an Access and Mobility Management Function (AMF) 132, a Session Management Function (SMF) 136, a Policy Control Function (PCF) 148, an Application Function (AF) 150, a User Plane Function (UPF) 134, a Network Slice Selection Function (NSSF) 142, an Authentication Server Function (AUSF) 144, and a Unified Data Management (UDM) / Home Subscriber Server (HSS) 146. The UPF 134 can provide connectivity to a Data Network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility, and can also include a network slice selection function. The SMF 136 may be configured to set up and manage various sessions according to network policies. The UPF 134 may be deployed in one or more configurations according to the desired service type. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0044] In some embodiments, the 5G system architecture 140B includes multiple IP Multimedia Core Network subsystem entities, such as an IP Multimedia Subsystem (IMS) 168B and a Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF that can act as a Proxy CSCF (P-CSCF) 162BE, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be a first point of contact for the UE 102 in the IM Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state within the network, and the E-CSCF can be configured to handle some aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B may be configured to act as a contact point within the operator's network for all IMS connections destined for that network operator's subscribers or roaming subscribers currently located within that network operator's service area. In some embodiments, the I-CSCF 166B may be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[0045] In some embodiments, the UDM / HSS 146 may be coupled to an application server (AS) 160B, which may include a telephony application server (TAS) or another application server. The AS 160B may be coupled to an IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0046] The reference point representation indicates that there may be interactions between corresponding NF services. For example, FIG. 1B shows N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UFM 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between UE 102 and AMF 132, not shown), N12 (between UE 102 and AMF 132, not shown), N13 (between UE 102 and AMF 132, not shown), N14 (between UE 102 and AMF 132, not shown), N15 (between UE 102 and AMF 132, not shown), N16 (between UE 102 and AMF 132, not shown), N17 (between SMF 136 and PCF 148, not shown), N18 (between UFM 146 and AMF 132, not shown), N19 (between two UPFs 134, not shown), N20 (between UDM 146 and SMF 136, not shown), N21 (between UE 102 and AMF 132, not shown), N22 (between UE 102 and AMF 1B shows the following reference points: N12 (between AMF 132 and SMF 136, not shown), N13 (between AUSF 144 and AMF 132, not shown), N14 (between two AMFs 132, not shown), N15 (between PCF 148 and AMF 132 in case of a non-roaming scenario, or between PCF 148, visited network, and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. 1B may also be used.

[0047] 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in FIG. 1B, the system architecture 140C may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, the 5G system architecture may be service-based, and interactions between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0048] In some embodiments, as shown in Figure 1C, a service-based representation may be used to represent network functions in the control plane that allow other authorized network functions to access those services. In this regard, the 5G system architecture 140C may include service-based interfaces, namely, Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (e.g., Nudr, N5g-eir, and Nudsf) may also be used.

[0049] In some embodiments, any of the UEs or base stations described with respect to Figures 1A-1C may be configured to perform the functions described herein.

[0050] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. Next-generation wireless communications systems, 5G, or new radio (NR), provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network / system that targets to meet widely different and sometimes competing performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with further potential new radio access technologies (RATs) to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR will enable everything to be connected wirelessly, delivering high speed and rich content and services.

[0051] Rel-15 NR systems are designed to operate on licensed spectrum. NR Unlicensed (NR-U) is shorthand for NR-based access to unlicensed spectrum, a technology that enables operation of NR systems on unlicensed spectrum.

[0052] In Rel-15NR, a four-step random access (RACH) procedure was defined. As shown in FIG. 2A, in the first step, the UE transmits a physical random access channel (PRACH) in the uplink by selecting one preamble signature. Then, in the second step, the gNB feeds back a random access response (RAR) carrying timing advance (TA) command information and an uplink grant for uplink transmission. Furthermore, in the third step, the UE transmits a Msg3 physical uplink shared channel (PUSCH) which may carry a contention resolution ID. In the fourth step, the gNB transmits a contention resolution message in a physical downlink shared channel (PDSCH).

[0053] In Rel-16NR, a two-step RACH procedure was further defined to enable fast access and low latency uplink transmission. As shown in Figure 2B, in the first step, the UE transmits a PRACH preamble and an associated MsgA PUSCH on the configured time and frequency resources, which may carry at least the equivalent content of Msg3 in the four-step RACH. In the second step, after successfully detecting the PRACH preamble and decoding the MsgA PUSCH, the gNB transmits MsgB, which may carry the equivalent content of Msg2 and Msg4 in the four-step RACH.

[0054] It should be noted that in some scenarios, e.g., small cell networks or industrial wireless sensor networks (IWSNs) where most of the sensors are stationary, PRACH preamble transmission in the 4-step PRACH procedure or 2-step RACH procedure is not required since the Timing Advance (TA) is within the length of the Cyclic Prefix (CP) or hardly changes with the deployment.

[0055] In this case, direct data transmission on the PUSCH in the configured grant may be considered without an associated PRACH preamble transmission, which may help to reduce data transmission delay and save UE power consumption. Furthermore, for UEs in RRC_INACTIVE mode, small data transmissions can be completed without transitioning to RRC_CONNECTED mode, thereby saving state transition signaling overhead.

[0056] For configured grant-based small data transmission (CG-SDT), in case of multiple beam operation, a set of synchronization signal blocks (SSBs) may be configured for the UE such that the UE may select one of the SSBs having a reference signal received power (RSRP) greater than a threshold, and then transmit data on the CG-PUSCH resource associated with the selected SSB according to the SSB-to-CG resource association. Furthermore, multiple DL and UL transmissions may be allowed during CG-SDT. In this case, some mechanisms may need to be defined for beam management for DL ​​and UL transmissions corresponding to the case of multi-beam operation. Among other things, embodiments of the present disclosure are directed to configured grant-based small data transmission (CG-SDT) in multi-beam operation. In particular, some embodiments are directed to the following: * Beam operation for multiple DL / UL transmissions during CG-SDT and RACH-based small data transmission (RA-SDT) * Timing Advance (TA) verification for CG-SDT * Verification of PUSCH occasions in case of repetition on CG-PUSCH resources for CG-SDT * Configuring the association between SSB and CG-PUSCH resources

[0057] Beam operation for multiple DL / UL transmissions during CG-SDT and RA-SDT

[0058] As mentioned above, in some scenarios, e.g., small cell networks or industrial wireless sensor networks (IWSNs) where most of the sensors are stationary, PRACH preamble transmission in the 4-step PRACH procedure or 2-step RACH procedure may not be required since the Timing Advance (TA) is within the length of the Cyclic Prefix (CP) or changes very little with the deployment.

[0059] In this case, direct data transmission on the physical uplink shared channel (PUSCH) in the configured grant may be considered without an associated physical random access (PRACH) preamble transmission, which may help to reduce data transmission delay and save UE power consumption. Furthermore, for UEs in RRC_INACTIVE mode, small data transmissions can be completed without transitioning to RRC_CONNECTED mode, thereby saving state transition signaling overhead.

[0060] For configured grant-based small data transmission (CG-SDT), in case of multiple beam operation, a set of synchronization signal blocks (SSBs) may be configured for the UE such that the UE may select one of the SSBs having a reference signal received power (RSRP) greater than a threshold, and then transmit data on the CG-PUSCH resource associated with the selected SSB according to the SSB-to-CG resource association. Furthermore, multiple DL and UL transmissions may be allowed during CG-SDT. In this case, some mechanisms may need to be defined for beam management for DL ​​and UL transmissions corresponding to the case of multi-beam operation.

[0061] An embodiment of the beam operation for multiple DL / UL transmissions during CG-SDT and Random Access-SDT (RA-SDT) is provided as follows:

[0062] In some embodiments, during CG-SDT, the UE transmits a scheduled PUSCH with downlink control information (DCI) format 0_0 or 0_1 scrambled by a Cell-Specific Radio Network Temporary Identifier (C-RNTI) or an RNTI configured for CG-SDT using the same spatial domain transmit filter in the same active UL bandwidth portion (BWP) as the CG-PUSCH transmission.

[0063] In some other embodiments, during CG-SDT, the UE transmits a PUSCH scheduled with DCI format 0_0 or 0_1 scrambled by the C-RNTI or the RNTI configured for CG-SDT using the same spatial domain transmit filter within the same active UL BWP as the last PUSCH or PUCCH transmission carrying the corresponding or last PDSCH HARQ-ACK feedback.

[0064] Figure 3 shows an example of beam operation in the case of PUSCH initial transmission. In this example, after CG-PUSCH transmission, the gNB may transmit a physical downlink control channel (PDCCH) in the UL grant to schedule the PUSCH with initial transmission. In this case, the transmission beam used for the PUSCH with initial transmission may be the same as the transmission beam of the CG-PUSCH transmission.

[0065] FIG. 4 shows an example of beam operation in case of PUSCH retransmission. In this example, after CG-PUSCH transmission, the gNB may transmit a PDCCH with UL grant to schedule a PUSCH with initial transmission. However, the gNB may not be able to successfully decode the PUSCH initial transmission. The gNB then transmits a PDCCH with UL grant to schedule a PUSCH retransmission. In this case, the Tx beam used for the PUSCH with retransmission may be the same as the Tx beam of the PUSCH initial transmission or the last PUSCH transmission.

[0066] In another embodiment, during CG-SDT, if the UE detects DCI format 1_0 or 1_1 with a CRC scrambled by a C-RNTI or an RNTI configured for CG-SDT and receives a transport block in a corresponding physical downlink shared channel (PDSCH), or detects DCI format 0_0 or 0_1 with a CRC scrambled by a C_RNTI or an RNTI configured for CG-SDT, the UE may assume the same demodulation reference signal (DM-RS) antenna port quasi-co-location property with respect to SSB blocks or channel state information reference signal (CSI-RS) resources used for CG-PUSCH association, regardless of whether the UE is provided with a transmission configuration indicator (TCI) state for a control resource set (CORESET) on which the UE receives a PDCCH with DCI format 1_0 or 1_1.

[0067] Additionally, during the CG-SDT, the Physical Uplink Control Channel (PUCCH), carrying the Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) response of the PDSCH transmission, is transmitted in the same spatial domain transmit filter within the same active UL BWP as the CG-PUSCH transmission.

[0068] In some other embodiments, during the CG-SDT, the PUCCH carrying the HARQ-ACK response of the PDSCH transmission is transmitted in the same active UL BWP as the last PUSCH transmission and with the same spatial domain transmit filter.

[0069] It should be noted that the UE may provide HARQ-ACK feedback for a PDSCH transmission on the PUCCH during the RA-SDT and CG-SDT only if the Timing Advance Timer (TAT) has not expired.

[0070] Figure 5 shows an example of beam operation in case of PDCCH / PDSCH and PUCCH transmission. In this example, after CG-PUSCH transmission, the gNB may transmit a PDCCH with DL grant and corresponding PDSCH. In this case, the UE may assume the same QCL assumptions for the PDCCH and corresponding PDSCH as for the SSB used for CG-PUSCH association. Furthermore, after successful decoding of the PDSCH, the UE may transmit a PUCCH carrying HARQ-ACK feedback for the PDSCH. In this case, the PUCCH may be transmitted with the same spatial domain transmit filter as the CG-PUSCH transmission.

[0071] In another embodiment, during CG-SDT, a PDCCH with DCI format 1_0 with CRC scrambled by the C-RNTI or RNTI configured for CG-SDT may be used to carry HARQ-ACK feedback for the corresponding CG-PUSCH transmission. In this case, the UE may assume the same DMRS antenna port quasi-co-location property with respect to the SSB blocks or CSI-RS resources that the UE uses for CG-PUSCH association, regardless of whether the UE is provided with a transmission configuration indicator (TCI) state for the control resource set (CORESET) on which it receives a PDCCH with DCI format 1_0 or 1_1, respectively.

[0072] In another embodiment, if during RA-SDT the UE detects DCI format 1_0 or 1_1 with CRC scrambled by the C-RNTI or the RNTI configured for RA-SDT and receives a transport block in the corresponding PDSCH or detects DCI format 0_0 or 0_1 with CRC scrambled by the C_RNTI or the RNTI configured for RA-SDT, the UE may assume the same DM-RS antenna port quasi-co-location property with respect to the SSB blocks or CSI-RS resources used by the UE for PRACH association, regardless of whether the UE is provided with a TCI state for the CORESET to receive a PDCCH with DCI format 1_0 or 1_1, respectively.

[0073] In some embodiments, if a UE detects DCI format 1_0 or 1_1 with a CRC scrambled by a C-RNTI or an RNTI configured for a RA-SDT and receives a transport block in a corresponding PDSCH, or detects DCI format 0_0 or 0_1 with a CRC scrambled by a C_RNTI or an RNTI configured for a C_RNTI or RA-SDT, the UE may assume the same DM-RS antenna port quasi-co-location property for a PDCCH with DCI format 1_0 with a CRC scrambled by a RA-RNTI or MsgB-RNTI, respectively, regardless of whether the UE is provided with a TCI state for a CORESET receiving a PDCCH with DCI format 1_0 or 1_1.

[0074] Furthermore, during RA-SDT, a PUCCH carrying a HARQ-ACK response for a PDSCH transmission is transmitted using the same spatial domain transmit filter in the same active UL BWP as a PUSCH transmission scheduled by a RAR or fallbackRAR UL grant for a 4-step RACH and / or a PUSCH transmission scheduled by a 2-step RACH or a PUCCH with Msg4 or MsgB HARQ-ACK feedback.

[0075] In some other embodiments, during the RA-SDT, the PUCCH carrying the HARQ-ACK response of the PDSCH transmission is transmitted using the same spatial domain transmit filter within the same active UL BWP as the last PUSCH transmission.

[0076] In another embodiment, during RA-SDT, the UE transmits PUSCH scheduled with DCI format 0_0 or 0_1 scrambled with C-RNTI or RNTI configured for RA-SDT using the same spatial domain transmit filter within the same active UL BWP as Msg3 PUSCH transmission scheduled with RAR or fallbackRAR UL grant for 4-step RACH and / or MsgA PUSCH for 2-step RACH or PUCCH with Msg4R or MsgB HARQ-ACK feedback.

[0077] In some other embodiments, the UE transmits a PUSCH scheduled with DCI format 0_0 or 0_1 scrambled with a C-RNTI or an RNTI configured for RA-SDT using the same spatial domain transmit filter in the same active UL BWP as the last PUSCH or PUCCH transmission.

[0078] In another embodiment, when beam failure recovery (BFR) is triggered by the UE during CG-SDT or RA-SDT, existing mechanisms may be applied to the Tx beams of PUSCH and PUCCH transmissions for subsequent data transmissions. Specifically, the PUCCH carrying the HARQ-ACK response of a PDSCH transmission is transmitted using the same spatial domain transmit filter within the same active UL BWP as the last PUSCH transmission or the PRACH transmission triggered by the BFR.

[0079] The UE shall also transmit PUSCH scheduled with DCI format 0_0 or 0_1 scrambled by the RNTI configured for the C-RNTI or CG-SDT with the same active UL BWP and using the same spatial domain transmit filter as the last PUSCH or BFR triggered PRACH or PUCCH transmission.

[0080] Timing Advance (TA) Verification for CG-SDT

[0081] An embodiment of TA validation for CG-SDT is provided as follows:

[0082] In some embodiments, a set of Reference Signal Received Power (RSRP) thresholds may be configured by higher layers via Minimum System Information (MSI), Residual Minimum System Information (RMSSI), Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling. In particular, this set of RSRP thresholds may include an RSRP increase threshold and an RSRP decrease threshold, e.g., the UE may assume that TA is valid when the measured RSRP value does not increase by more than the configured RSRP increase threshold or does not decrease by more than the configured RSRP decrease threshold.

[0083] When a set of SSBs is configured by higher layers via RRC signaling for association with CG-PUSCH resources for a CG-PUSCH configuration, if the measured RSRP values ​​for SSBs in the set of SSBs do not increase more than the configured RSRP increase threshold or decrease more than the configured RSRP decrease threshold, the UE may determine that TA is valid for the CG-PUSCH configuration; if the measured RSRP values ​​for any SSBs in the set of SSBs increase more than the configured RSRP increase threshold or decrease more than the configured RSRP decrease threshold, the UE may determine that TA is not valid for the CG-PUSCH configuration.

[0084] In another embodiment, two sets of RSRP thresholds may be configured by higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling. In particular, one set of RSRP thresholds may include an RSRP increase threshold and an RSRP decrease threshold, for example, the UE may assume that TA is valid when the measured RSRP value does not increase by more than the configured RSRP increase threshold or does not decrease by more than the configured RSRP decrease threshold.

[0085] Furthermore, assuming that the Tx beam used for transmitting the RRC release message is based on an SSB having index A, if the newly detected SSB index for the CG-PUSCH transmission is the same as SSB index A, a first set of RSRP thresholds is used to determine whether TA is valid, whereas if the newly detected SSB index for the CG-PUSCH transmission is different from SSB index A, a second set of RSRP thresholds is used to determine whether TA is valid.

[0086] In another embodiment, two sets of RSRP thresholds may be configured by higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling. Furthermore, two groups of SSBs may be configured by higher layers. When a newly detected SSB index for a CG-PUSCH transmission is in the first group, the first set of RSRP thresholds is used to determine whether TA is valid, while when a newly detected SSB index for a CG-PUSCH transmission is in the second group, the second set of RSRP thresholds is used to determine whether TA is valid.

[0087] Verification of PUSCH occasions in the case of repetition for CG-PUSCH resources for CG-SDT

[0088] An embodiment of the verification of PUSCH occasions in case of repetition on CG-PUSCH resources for CG-SDT is provided as follows:

[0089] In some embodiments, the disabling rules for PUSCH occasions for CG-SDT may be similar to those defined for the disabling rules for PUSCH occasions for two-step RACH, as specified in Section 8.1A of TS 38.213 [1]. Furthermore, a PUSCH occasion for CG-SDT is valid if it does not overlap in time and frequency with any PUSCH occasion for two-step RACH or associated with a type 2 random access procedure.

[0090] In another embodiment, when repetitions are configured for a CG-PUSCH resource, every repetition of a CG-PUSCH transmission is considered a CG-PUSCH occasion, in which case the same spatial domain transmit filter is used for every repetition of the CG-PUSCH.

[0091] In another embodiment, when repetition is configured for a CG-PUSCH resource, if the repetition in the CG-PUSCH resource does not satisfy the validation rule for the CG-PUSCH occasion for the CG-SDT, the UE does not transmit the CG-PUSCH in the repetition. In addition, the PUSCH occasion for the CG-SDT is disabled only when all repetitions are disabled.

[0092] Figure 6 shows an example of validation of PUSCH occasions for CG-SDT when repetitions are configured for a CG-PUSCH resource. In this example, four repetitions are configured for the CG-PUSCH resource. Also, CG-PUSCH repetition #1 is not valid due to the invalidation rule. In this case, the UE does not transmit the second CG-PUSCH repetition but still considers the CG-PUSCH occasion valid.

[0093] In some other embodiments, a PUSCH occasion for a CG-SDT is valid only if all repetitions are valid, in which case the UE does not transmit a CG-PUSCH in a repetition if any of the repetitions for the CG-PUSCH does not satisfy the validation rules for the CG-PUSCH occasion for a CG-SDT.

[0094] Configuring the Association Between SSB and CG-PUSCH Resources

[0095] An embodiment of the configuration of the association between SSB resources and CG-PUSCH resources is provided as follows:

[0096] In some embodiments, a list of SSB indices can be configured as part of the CG-PUSCH configuration, and a list of DMRS resources including sequences and / or DMRS APs for the configured CG-PUSCH can each be associated with a list of SSB indices. In particular, each DMRS resource can be associated with an SSB from the configured set of SSB indices. In this case, the linkage between the SSB resources and the CG-PUSCH resources can be established by configuring a set of SSB indices for the CG-PUSCH configuration. For CG-SDT operation, the UE selects one of the SSBs having an SS-RSRP change within the threshold and then utilizes the associated CG-PUSCH resource for UL data transmission.

[0097] Note that when both DMRS AP and sequence are configured for DMRS resources, the ordering of DMRS resource indexes is determined first by ascending order of DMRS port index and second by ascending order of DMRS sequence index. The configuration of DMRS sequence may be defined similarly to the DMRS sequence for MsgA PUSCH for 2-step RACH.

[0098] Furthermore, in the configuration of association between SSBs and CG-PUSCH resources, the same or different SSBs may be associated with different CG-PUSCH resources, and vice versa. When the same SSB is associated with two or more CG-PUSCH resources, this can be considered as a one-to-many mapping between SSBs and CG-PUSCH resources. When two or more SSBs are associated with one CG-PUSCH resource, this can be considered as a many-to-one mapping between SSBs and CG-PUSCH resources.

[0099] Table 1 shows an example of an association between SSBs and CG-PUSCH resources in a CG-PUSCH configuration. In this case, a list of SSB indices and DMRS APs can be configured. In the table, maxNrofSSBIndex is the number of SSB indices for CG-SDT operation. Assuming that two SSB indices are configured for CG-SDT operation, the first SSB index is associated with the first DMRS AP and the second SSB index is associated with the second DMRS AP.

[0100] [Table 1]

[0101] Table 2 shows an example of an association between SSBs in a CG-PUSCH configuration and CG-PUSCH resources. In the table, maxNrofSSBIndex is the number of SSB indices for CG-SDT operation. Furthermore, one SSB index is associated with one DMRS AP.

[0102] [Table 2]

[0103] It should be noted that the above design principle can be easily extended to the case where more than one SSB is associated with a CG-PUSCH resource, or one SSB is associated with more than one CG-PUSCH resource, in which case a mapping ratio between SSBs and CG-PUSCH resources can be derived based on the number of configured SSB indices and the number of CG-PUCSH resources that contain DMRS APs or sequences.

[0104] In one embodiment, assuming four SSBs and two DMRS APs are configured for a CG-PUSCH configuration, the mapping ratio is a two-to-one mapping, where the first two SSB indices are associated with a first DMRS AP and the second two SSB indices are associated with a second DMRS AP.

[0105] In another embodiment, assuming that one SSB and four DMRS resources are configured for a CG-PUSCH configuration, the mapping ratio is one to two mapping. Figure 7 shows an embodiment of the association between two SSBs and four DMRS resources. In this embodiment, the first SSB index is associated with two first DMRS resources, and the second SSB index is associated with two second DMRS resources.

[0106] In another embodiment, a mapping ratio is defined between SSBs and CG-PUSCH occasions. In particular, one-to-one and / or many-to-one and / or one-to-many mappings between SSBs and CG-PUSCH occasions may be supported and configured as part of the CG-PUSCH configuration.

[0107] In one option, only one DMRS resource is configured as part of the CG-PUSCH resources, in which case antennaPort in the CG-PUSCH configuration indicates the DMRS antenna port for CG-PUSCH transmission.

[0108] In some other embodiments, multiple DMRS resources may be configured for a CG-PUSCH occasion. As mentioned above, a DMRS resource may include several DMRS APs and / or DMRS sequences. The configuration for the DMRS AP may reuse or extend that defined as MsgA PUSCH. In particular, if DMRS type 1 is configured, a one-bit indication is used to indicate the index(es) of the CDM group, e.g., bit 0 indicates the first CDM group and bit 1 indicates the second CDM group; if not configured, both CDM groups are used.

[0109] If DMRS Type 1 is configured, a 2-bit indication of the index(es) of the CDM group(s), e.g., bit 00 indicates the first CDM group, bit 01 indicates the second CDM group; bit 10 indicates the third CDM group, bit 11 indicates the first and second CDM groups; if not configured, both CDM groups are used. Note that other options for indicating the CDM group combinations for a DMRS AP can be easily extended.

[0110] Additionally, a one-bit indication is used to indicate the port number, e.g., 0 indicates one port per CDM group, 1 indicates two ports per CDM group, and if not configured, four ports per CDM group are used.

[0111] Furthermore, if multiple DMRS APs are configured for a CG-PUSCH occasion, antennaPort or DMRS AP in the CG-PUSCH configuration may be used to indicate the initiating DMRS AP for association between SSBs and CG-PUSCH resources. Alternatively, antennaPort is not configured in the CG-PUSCH configuration. In this case, the first DMRS AP in the indicated multiple DMRS APs is the initiating DMRS AP for association between SSBs and CG-PUSCH resources.

[0112] In one embodiment, assume that a 4-to-1 mapping is configured for SSB to CG-PUSCH occasion mapping, which indicates that four SSBs are associated with one CG-PUSCH occasion. Also, in a CG-PUSCH configuration, DMRS type 1, and one DMRS symbol, both DMRS CDM groups are configured, and two ports in each CDM group are used for DMRS. In this case, DMRS APs with indexes 0, 1, 2, and 3 are used for CG-SDT operation. Figure 8 shows a typical example of association between four SSBs and four DMRS APs.

[0113] In another embodiment, a mapping ratio is defined between SSBs and CG-PUSCH resources. Similarly, one-to-one and / or many-to-one and / or one-to-many mappings between SSBs and CG-PUSCH resources may be supported and configured as part of the CG-PUSCH configuration.

[0114] The configuration of one or more DMRS resources may be defined as described above. Additionally, similarly, antennaPort may be configured to indicate the start of the DMRS AP for association between SSB and CG-PUSCH resources.

[0115] In some embodiments, for RA-SDT, a cell-specific PUCCH resource set may be adopted for PUCCH transmissions carrying HARQ-ACK feedback of Msg4 for 4-step RACH-based SDT and MsgB for 2-step RACH-based SDT. Note that a separate pucch-ResourceCommon may be configured for SDT operation compared to conventional 4-step RACH and 2-step RACH procedures, which may help to minimize the impact on legacy systems. If a separate pucch-ResourceCommon is not configured, the same pucch-ResourceCommon configured for conventional RACH procedures may be applied for HARQ-ACK feedback of Msg4 / MsgB for RA-SDT procedures.

[0116] In another embodiment, for RA-SDT and / or CG-SDT, a cell-specific PUCCH resource set may be adopted for PUCCH transmission carrying HARQ-ACK feedback of a subsequent data transmission. In this case, a separate pucch-ResourceCommon may be configured for SDT operation compared to conventional 4-step RACH and 2-step RACH procedures. If a separate ResourceCommon is not configured, the same pucch-ResourceCommon configured for conventional RACH procedures may be applied for HARQ-ACK feedback of a subsequent PDSCH transmission during RA-SDT and CG-SDT procedures.

[0117] In some other embodiments, a UE-specific PUCCH resource set may be configured for a UE for a PUCCH transmission carrying HARQ-ACK feedback of a subsequent data transmission. In particular, only PUCCH resource sets with a UCI size of less than 3 bits may be configured for a UE for carrying HARQ-ACK feedback of a subsequent PDSCH transmission during RA-SDT and CG-SDT procedures.

[0118] In another embodiment, some or all parameters in the PDSCH-Config and / or PUSCH-Config may be configured for the UE during the RRC Release message for subsequent data transmissions during the RA-SDT and CG-SDT procedures. In this case, the UE should follow the parameters configured by the PDSCH-Config and / or PUSCH-Config for PDSCH and PUSCH transmissions scheduled by DCI during RA-SDT and CG-SDT operations. If the PDSCH-Config and / or PUSCH-Config are not configured, default values ​​may be applied for the corresponding PDSCH and PUSCH transmissions scheduled by DCI during RA-SDT and CG-SDT operations.

[0119] In another embodiment, after an integer number of SSB blocks to a PUSCH occasion and associated DM-RS resource mapping cycle within an association period, N SS / PECH PUSCH If there is a set of PUSCH occasions and associated DM-RS resources that are not mapped to an SS / PBCH block index, then the SS / PBCH block index is not mapped to a set of PUSCH occasions and associated DM-RS resources.

[0120] Further, an association pattern period includes one or more association periods and is determined such that a pattern between PUSCH occasions and associated DM-RS resources, and SS / PBCH block indexes is repeated at most every 640 ms. PUSCH occasions and associated DM-RS resources, if any, that are not associated with an SS / PBCH block index after an integer number of association periods are not used for PUSCH transmission.

[0121] After an integer number of SS / PBCH blocks to a PUSCH occasion and associated DM-RS resource mapping cycle within an association period, N SS / PECH PUSCH If there is a set of PUSCH occasions and associated DM-RS resources that are not mapped to an SS / PBCH block index, then the SS / PBCH block index is not mapped to a set of PUSCH occasions and associated DM-RS resources. An association pattern period includes one or more association periods and is determined such that the pattern between PUSCH occasions and associated DM-RS resources and SS / PBCH block indexes is repeated at most every 640 ms. PUSCH occasions and associated DM-RS resources that are not associated with an SS / PBCH block index after an integer number of association periods, if any, are not used for PUSCH transmission.

[0122] 9 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. The wireless communication device 900 may be suitable for use as a UE or gNB configured for operation in a 5G NR network.

[0123] The communication device 900 may include a communication circuit 902 and a transceiver 910 for transmitting and receiving signals to and from other communication devices using one or more antennas 901. The communication circuit 902 may include circuitry capable of operating physical layer (PHY) communications and / or medium access control (MAC) communications for controlling access to a wireless medium, and / or any other communication layer for transmitting and receiving signals. The communication device 900 may also include a processing circuit 906 and a memory 908 configured to perform operations described herein. In some embodiments, the communication circuit 902 and the processing circuit 906 may be configured to perform operations detailed in the figures, diagrams, and flows above.

[0124] According to some embodiments, the communication circuitry 902 can be arranged to contend for the wireless medium and compose frames or packets for communication over the wireless medium. The communication circuitry 902 can be configured to transmit and receive signals. The communication circuitry 902 can also include circuitry for modulation / demodulation, upconversion / downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 906 of the communication device 900 can include one or more processors. In other embodiments, two or more antennas 901 may be coupled to the communication circuitry 902 arranged to transmit and receive signals. The memory 908 can store information for configuring the processing circuitry 906 to perform operations for composing and transmitting message frames and for performing various operations described herein. The memory 908 can include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 908 can include computer-readable storage devices, read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and other storage devices and media.

[0125] In some embodiments, communication device 900 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capabilities, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computing device, or another device that can receive and / or transmit information wirelessly.

[0126] In some embodiments, the communication device 900 may include one or more antennas 901. The antennas 901 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmitting RF signals. In some embodiments, a single antenna with multiple apertures may be used instead of two or more antennas. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated due to spatial diversity and different channel characteristics that may occur between each of the antennas and the antenna of the transmitting device.

[0127] In some embodiments, the communications device 900 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, a speaker, and other mobile device elements. The display may be an LCD screen, including a touch screen.

[0128] Although communications device 900 is shown as having several separate functional elements, two or more of the functional elements may be combined and implemented by a combination of software components, such as processing elements including digital signal processors (DSPs), and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RF ICs), and combinations of various hardware and logic circuits to perform at least the functions described herein. In some embodiments, the functional elements of communications device 900 may refer to one or more processes operating on one or more processing elements.

[0129] Working Example:

[0130] Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, comprising:

[0131] detecting, by the UE, a downlink control information (DCI) format 0_0 or 0_1 scrambled by a cell-specific radio network primary identifier (C-RNTI) or a configured RNTI for a configured grant small data transmission (CG-SDT);

[0132] and transmitting, by the UE, a physical uplink shared channel (PUSCH) in the same active UL bandwidth portion (BWP) and using the same spatial domain transmit filter as a CG-PUSCH transmission.

[0133] Example 2 may include the method of example 1 or any other example herein, wherein during the CG-SDT, the UE transmits a PUSCH scheduled with DCI format 0_0 or 0_1 scrambled by a C-RNTI or an RNTI configured for the CG-SDT using the same spatial domain transmit filter in the same active UL BWP as the last PUSCH or a physical uplink control channel (PUCCH) transmission carrying a corresponding or last physical downlink shared channel (PDSCH) HARQ-ACK feedback.

[0134] Example 3 may include the method of example 1 or any other example herein, wherein during the CG-SDT, if the UE detects DCI format 1_0 or 1_1 with a CRC scrambled by a C-RNTI or an RNTI configured for the CG-SDT and receives a transport block in a corresponding physical downlink shared channel (PDSCH) or DCI format 0_0 or 0_1 with a CRC scrambled by a C_RNTI or an RNTI configured for the CG-SDT, the UE may assume the same demodulation reference signal (DM-RS) antenna port quasi-co-location property with respect to an SSB block or channel state information reference signal (CSI-RS) resource used for the CG-PUSCH association, regardless of whether the UE is provided with a transmission configuration indicator (TCI) state for a control resource set (CORESET) on which the UE receives a PDCCH with DCI format 1_0 or 1_1.

[0135] Example 4 may include the method of example 1 or any other example herein, wherein during the CG-SDT, a physical uplink control channel (PUCCH) carrying a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) response for a PDSCH transmission is transmitted in the same spatial domain transmit filter within the same active UL BWP as the CG-PUSCH transmission.

[0136] Example 5 may include the method of example 1 or any other example herein, wherein during the CG-SDT, a PUCCH carrying a HARQ-ACK response for a PDSCH transmission is transmitted in the same active UL BWP and using the same spatial domain transmit filter as the last PUSCH transmission.

[0137] Example 6 may include the method of example 1 or any other example herein, wherein the UE may provide HARQ-ACK feedback for a PDSCH transmission on the PUCCH during the RA-SDT and CG-SDT when a timing advance timer (TAT) has not expired.

[0138] Example 7 may include the method of Example 1 or any other example herein, and during RA-SDT, if the UE detects DCI format 1_0 or 1_1 with a CRC scrambled by a C-RNTI or an RNTI configured for RA-SDT and receives a transport block in a corresponding PDSCH, or detects DCI format 0_0 or 0_1 with a CRC scrambled by a C_RNTI or an RNTI configured for CG-SDT, the UE may assume the same DM-RS antenna port quasi-co-location property with respect to SSB blocks or CSI-RS resources used by the UE for PRACH association, regardless of whether the UE is provided with a TCI state for a CORESET in which the UE receives a PDCCH having DCI format 1_0 or 1_1, respectively.

[0139] Example 8 may include the method of Example 1 or any other example herein, and when a UE detects DCI format 1_0 or 1_1 having a CRC scrambled by an RNTI configured for a C-RNTI or a RA-SDT and receives a corresponding PDSCH transport block, or detects DCI format 0_0 or 0_1 having a CRC scrambled by an RNTI configured for a C_RNTI or a RA-SDT, the UE may assume the same DM-RS antenna port quasi-co-location property for a PDCCH having DCI format 1_0 having a CRC scrambled by an RA-RNTI or an MsgB-RNTI, respectively, regardless of whether the UE is provided with a TCI state for a CORESET receiving a PDCCH having DCI format 1_0 or 1_1.

[0140] Example 9 may include the method of example 1 or any other example herein, wherein during RA-SDT, a PUCCH carrying a HARQ-ACK response for a PDSCH transmission is transmitted using the same spatial-domain transmit filter in the same active UL BWP as a PUSCH transmission scheduled by a RAR or fallbackRAR UL grant for a 4-step RACH and / or a PUSCH transmission scheduled by a 2-step RACH or a PUCCH with HARQ-ACK feedback of Msg4 or MsgB.

[0141] Example 10 may include the method of example 1 or any other example herein, wherein during the RA-SDT, a PUCCH carrying a HARQ-ACK response for a PDSCH transmission is transmitted using the same spatial domain transmit filter within the same active UL BWP as the last PUSCH transmission.

[0142] Example 11 may include the method of example 1 or any other example herein, wherein during RA-SDT, the UE transmits PUSCH scheduled by DCI format 0_0 or 0_1 scrambled by C-RNTI or RNTI configured for RA-SDT using the same spatial domain transmit filter in the same active UL BWP as Msg3 PUSCH transmission scheduled by RAR or fallbackRAR UL grant for 4-step RACH, and / or MsgA PUSCH for 2-step RACH or PUCCH with Msg4R or MsgB HARQ-ACK feedback.

[0143] Example 12 may include the method of example 1 or any other example herein, wherein the UE transmits a PUSCH scheduled with DCI format 0_0 or 0_1 scrambled with a C-RNTI or an RNTI configured for the RA-SDT using the same spatial domain transmit filter within the same active UL BWP as the last PUSCH transmission or PUCCH transmission.

[0144] Example 13 may include the method of Example 1 or any other example herein, wherein when a set of SSBs is configured by higher layers via RRC signaling for association with CG-PUSCH resources for a CG-PUSCH configuration, if a measured RSRP value for an SSB in the set of SSBs does not increase by more than a configured RSRP increase threshold or does not decrease by more than a configured RSRP decrease threshold, the UE may determine that TA is valid for the CG-PUSCH configuration.

[0145] Example 14 may include the method of example 1 or any other example herein, and if the measured RSRP value for any SSB in the set of SSBs increases more than a configured RSRP increase threshold or decreases more than a configured RSRP decrease threshold, the UE may determine that TA is not valid for the CG-PUSCH configuration.

[0146] Example 15 may include the method of example 1 or any other example herein, and the two sets of RSRP thresholds may be configured by higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling.

[0147] Example 16 may include the method of Example 1 or any other example herein, and assuming that the Tx beam used for transmitting the RRC release message is based on an SSB having index A, if the newly detected SSB index for the CG-PUSCH transmission is the same as SSB index A, a first set of RSRP thresholds is used to determine whether TA is valid; whereas, if the newly detected SSB index for the CG-PUSCH transmission is different from SSB index A, a second set of RSRP thresholds is used to determine whether TA is valid.

[0148] Example 17 may include the method of example 1 or any other example herein, wherein two groups of SSBs may be configured by an upper layer, where when a newly detected SSB index for a CG-PUSCH transmission is in the first group, a first set of RSRP thresholds is used to determine whether TA is valid; whereas, when a newly detected SSB index for a CG-PUSCH transmission is in the second group, a second set of RSRP thresholds is used to determine whether TA is valid.

[0149] Example 18 may include the method of Example 1 or any other example herein, wherein the PUSCH occasion for the CG-SDT is valid if it does not overlap in time and frequency with any PUSCH occasion for the two-step RACH or associated with the Type 2 random access procedure.

[0150] Example 19 may include the method of Example 1 or any other example herein, wherein when repetition is configured for a CG-PUSCH resource, if the repetition in the CG-PUSCH does not satisfy a verification rule for a CG-PUSCH occasion for a CG-SDT, the UE does not transmit a CG-PUSCH in the repetition; the PUSCH occasion for the CG-SDT is disabled only when all repetitions are disabled.

[0151] Example 20 may include the method of Example 1 or any other example herein, wherein a PUSCH occasion for a CG-SDT is valid only when all repetitions are valid; if any of the repetitions for the CG-PUSCH does not satisfy a validation rule for a CG-PUSCH occasion for a CG-SDT, the UE does not transmit a CG-PUSCH in the repetition.

[0152] Example 21 may include the method of example 1 or any other example herein, wherein the list of SSB indices may be configured as part of the CG-PUSCH configuration, and a list of DMRS resources including sequences and / or DMRS APs for the configured CG-PUSCH may each be associated with the list of SSB indices.

[0153] Example 22 may include the method of Example 1 or any other example herein, and the UE may derive a mapping ratio between SSBs and CG-PUSCH resources based on the number of configured SSB indexes and the number of CG-PUCSH resources including DMRS APs or sequences.

[0154] Example 23 may include the method of example 1 or any other example herein, wherein a mapping ratio is defined between SSBs and CG-PUSCH occasions, and in particular, one-to-one and / or many-to-one and / or one-to-many mapping between SSBs and CG-PUSCH occasions may be supported and configured as part of the CG-PUSCH configuration.

[0155] Example 24 may include the method of example 1 or any other example herein, wherein only one DMRS resource is configured as part of the CG-PUSCH resource.

[0156] Example 25 may include the method of Example 1 or any other example herein, wherein a plurality of DMRS resources may be configured for a CG-PUSCH occasion, and an antennaPort in the CG-PUSCH configuration may be used to indicate an initiating DMRS AP for association between an SSB and the CG-PUSCH resource.

[0157] Example 26 may include the method of example 1 or any other example herein, wherein a mapping ratio is defined between SSBs and CG-PUSCH resources, and one-to-one and / or many-to-one and / or one-to-many mapping between SSBs and CG-PUSCH resources may be supported and configured as part of the CG-PUSCH configuration.

[0158] Example 27 may include the method of example 1 or any other example herein, and for RA-SDT, a cell-specific PUCCH resource set may be adopted for PUCCH transmission carrying HARQ-ACK feedback of Msg4 for 4-step RACH based SDT and MsgB for 2-step RACH based SDT; a separate pucch-ResourceCommon may be configured for SDT operation compared to the conventional 4-step RACH and 2-step RACH procedures.

[0159] Example 28 may include the method of Example 1 or any other example herein, and in the case of RA-SDT and / or CG-SDT, a cell-specific PUCCH resource set may be adopted for PUCCH transmission carrying HARQ-ACK feedback for a subsequent data transmission.

[0160] Example 29 may include the method of Example 1 or some other examples in this specification, and a UE-specific PUCCH resource set may be configured for the UE for PUCCH transmission carrying HARQ-ACK feedback for a subsequent data transmission.

[0161] Example 30 may include the method of Example 1 or any other example herein, wherein some or all of the parameters in the PDSCH-Config and / or PUSCH-Config may be configured for the UE in an RRC release message for subsequent data transmission during the RA-SDT and CG-SDT procedures.

[0162] Example 31 includes a method for a user equipment (UE):

[0163] receiving downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) transmission by the UE, the DCI being scrambled by a cell-specific radio network temporary identifier (C-RNTI) or an RNTI configured for grant-based small data transmission (CG-SDT) configured using a spatial domain transmit filter;

[0164] and encoding the PUSCH message for transmission based on the DCI.

[0165] Example 32 may include the method of example 31 or any other example herein, wherein the spatial domain transmit filter is common with the spatial domain transmit filter in the active UL bandwidth portion (BWP) of the configured grant PUSCH (CG-PUSCH) transmission.

[0166] Example 33 may include the method of Example 31 or any other example herein, wherein the spatial domain transmit filter is common to the spatial domain transmit filter in a PUCCH transmission carrying an active UL BWP of a previous PUSCH or HARQ-ACK feedback of a corresponding or previous PDSCH.

[0167] Example 34 may include the method of Example 31 or any other example herein, and further includes encoding the CG-PUSCH message for transmission before encoding the PUSCH message for transmission.

[0168] Example 35 may include the method of Example 34 or any other example herein, and further includes a step of receiving a physical downlink control channel (PDCCH) having an uplink (UL) grant to schedule the PUSCH transmission.

[0169] Example 36 may include the method of Example 35 or any other example herein, wherein a transmit (Tx) beam used for PUSCH transmission is common to a TX beam used for CG-PUSCH transmission.

[0170] Example 37 can include the method of example 31 or any other example herein:

[0171] receiving, following the PUSCH transmission, an UL grant PDCCH for scheduling a PUSCH retransmission;

[0172] and encoding the PUSCH message for retransmission based on the PDCCH.

[0173] Example 38 may include the method of Example 37 or any other example herein, wherein the Tx beam used for the PUSCH retransmission is common to the Tx beam used for the PUSCH transmission or the previous PUSCH transmission.

[0174] Example 39 includes a method for a user equipment (UE):

[0175] encoding the CG-PUSCH message for transmission to a next generation Node B (gNB);

[0176] receiving a PDCCH and a corresponding PDSCH having a DL grant from a gNB;

[0177] and encoding a PUCCH message for transmission to the gNB, the PUCCH message carrying an indication of HARQ-ACK feedback for the PDSCH.

[0178] Example 40 can include the method of example 39 or any other example herein.

[0179] The PUCCH is transmitted using a common spatial domain transmit filter with the CG-PUSCH transmission.

[0180] Example 41 may include the method of Example 40 or any other example herein, wherein the PDCCH includes a DCI having a CRC scrambled by the C-RNTI or an RNTI configured for the CG-SDT to indicate HARQ-ACK feedback of a corresponding CG-PUSCH transmission.

[0181] Example 42 may include the method of Example 41 or any other example herein, and further includes a step of determining a demodulation reference signal (DMRS) antenna port quasi-co-location characteristic common to the SSB block or CSI-RS resource used by the UE for the CG-PUSCH association.

[0182] Example 43 may include the method of Example 40 or any other example herein, wherein the DCI is DCI format 1_0 or 1_1 having a CRC scrambled by the C-RNTI or the RNTI configured for the RA-SDT.

[0183] Example 44 includes a method for a user equipment (UE):

[0184] receiving CG-PUSCH configuration information including a list of SSB indices and a list of DMRS resources associated with the list of SSB indices;

[0185] and deriving a mapping ratio between the SSB and the CG-PUSCH resources based on the CG-PUSCH configuration information.

[0186] Example 45 may include the method of example 44 or any other example herein, wherein the list of DMRS resources includes an indication of a DMRS AP or sequence for the configured CG-PUSCH.

[0187] Example 46 may include the method of example 44 or any other example herein, wherein a mapping ratio is defined between SSB and CG-PUSCH occasions.

[0188] Example 47 may include the method of Example 46 or any other example herein, wherein the mapping ratio is one-to-one, many-to-one, or one-to-many mapping between SSB and CG-PUSCH occasions.

[0189] Example 48 may include the method of example 44 or any other example herein, wherein the single DMRS resource is configured as a portion of the CG-PUSCH resource.

[0190] Example 49 may include the method of Example 44 or any other example herein, wherein a plurality of DMRS resources are configured for a CG-PUSCH occasion.

[0191] Example 50 may include the method of Example 46 or any other example herein, wherein the antenna port indicator in the CG-PUSCH configuration information is for indicating an initiating DMRS AP for association between the SSB and the CG-PUSCH resource.

[0192] Example 51 may include the method of Example 39 or any other example herein, wherein a cell-specific PUCCH resource set for RA-SDT is adopted for PUCCH transmission.

[0193] Example 52 may include the method of Example 51 or any other example herein, wherein the PUCCH transmission includes an indication of HARQ-ACK feedback for Msg4 for 4-step RACH-based SDT and MsgB for 2-step RACH-based SDT.

[0194] Example 53 may include the method of Example 39 or any other example herein, wherein a cell-specific PUCCH resource set for RA-SDT or CG-SDT is adopted for PUCCH transmission; The PUCCH transmission includes an indication of HARQ-ACK feedback for the subsequent data transmission.

[0195] Example 54 may include the method of example 1 or any other example herein, wherein a UE-specific PUCCH resource set is configured for the UE for PUCCH transmission.

[0196] The Abstract is provided to comply with 37 CFR. Section 1.72(b) requires an Abstract that will allow the reader to ascertain the nature and summary of the technical disclosure. This Abstract is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

1. 1. An apparatus for a user equipment (UE) configured for operation in a fifth generation new radio (5G-NR) system, the apparatus comprising: a processing circuit and a memory; For a physical uplink shared channel (PUSCH) transmission in a radio resource control (RRC) inactive state (RRC_INACTIVE state), the processing circuitry decodes a physical downlink control channel (PDCCH) to detect a downlink control information (DCI) format; When a DCI format for a configured grant-based small data transmission (SDT) (CG-SDT) is detected and a transport block (TB) is received on a corresponding physical downlink shared channel (PDSCH), the processing circuitry: Assume that a demodulation reference signal (DM-RS) antenna port associated with PDCCH reception and a DM-RS antenna port associated with PDSCH reception are quasi-co-located (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT; configured to encode a PUCCH for transmission using the same spatial domain transmit filter as a last PUSCH transmission during the CG-SDT; the memory is configured to store parameters for the spatial domain transmit filter. Device.

2. The detected DCI format includes DCI format 1_0 for the CG-SDT; 2. The apparatus of claim 1.

3. The processing circuitry further comprises: Decoding a CG-PUSCH configuration indicating a number of valid PUSCH occasions and SS / PBCH block indices that map to associated DM-RS resources for transmission of the PUSCH; configured to map the number of SS / PBCH block indices to the valid PUSCH occasions and associated DM-RS resources, first in ascending order of DM-RS port index, and then in ascending order of DM-RS sequence index.

3. The apparatus of claim 2.

4. If there is a set of associated DM-RS resources and PUSCH occasions that is not mapped to the SS / PBCH block index after an integer number of SS / PBCH block indexes for an associated DM-RS resource mapping cycle and PUSCH occasion within an association period, the processing circuitry refrains from further mapping the SS / PBCH block index to a PUSCH occasion and a set of associated DM-RS resources.

4. The apparatus of claim 3.

5. The association period is determined such that a pattern between the PUSCH occasions and associated DM-RS resources and SS / PBCH block index is repeated at most every 640 milliseconds.

5. The apparatus of claim 4.

6. The PUSCH transmission in the CG-SDT includes a configured grant PUSCH (CG-PUSCH), and the CG-PUSCH is performed without a PRACH preamble transmission by the UE when operating in the RRC_INACTIVE state.

4. The apparatus of claim 3.

7. The DM-RS antenna port associated with the PDCCH reception and the DM-RS antenna port associated with the PDSCH reception are assumed to be the SS / PBCH and QCL associated with the PUSCH in terms of Type D properties including average gain and spatial receiver (RX) parameters.

7. The apparatus of claim 6.

8. Based on an assumption that the DM-RS antenna port associated with PDCCH reception and the DM-RS antenna port associated with PDSCH reception are the SS / PBCH and QCL associated with PUSCH resources for the CG-SDT, the processing circuit is configured to apply the same spatial receive (RX) parameters (same spatial RX parameters) as for synchronization signal block (SSB) reception, PDCCH reception, and PDSCH reception.

8. The apparatus of claim 7.

9. To apply the same spatial RX parameters, The processing circuitry includes: Demodulate the PDSCH using the DM-RS based on the assumption that the DM-RS antenna port associated with the PDSCH reception is the SS / PBCH and QCL associated with the PUSCH resource for the CG-SDT; The DM-RS is configured to demodulate the PDCCH using the DM-RS based on an assumption that the DM-RS antenna port associated with the PDCCH reception is the SS / PBCH and QCL associated with the PUSCH resource for the CG-SDT.

9. The apparatus of claim 8.

10. the processing circuitry comprises a baseband processor; 2. The apparatus of claim 1.

11. 1. A non-transitory computer-readable storage medium storing instructions for execution by a processing circuit of a user equipment (UE), the instructions comprising: for a physical uplink shared channel (PUSCH) transmission in a radio resource control (RRC) inactive (RRC_INACTIVE) state, causing the processing circuitry to decode a physical downlink control channel (PDCCH) to detect a downlink control information (DCI) format; a DCI format for a configured grant-based small data transmission (SDT) (CG-SDT) is detected and a transport block (TB) is received on a corresponding physical downlink shared channel (PDSCH), the processing circuitry comprising: Assume that a demodulation reference signal (DM-RS) antenna port associated with PDCCH reception and a DM-RS antenna port associated with PDSCH reception are quasi-co-located (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT; configured to cause a PUCCH to be encoded for transmission using the same spatial domain transmit filter as a last PUSCH transmission during the CG-SDT. A non-transitory computer-readable storage medium.

12. The detected DCI formats include DCI format 1_0 for CG-SDT; The non-transitory computer-readable storage medium of claim 11.

13. The instructions further cause the processing circuit to: Decoding a CG-PUSCH configuration indicating a number of valid PUSCH occasions and SS / PBCH block indices that map to associated DM-RS resources for transmission of the PUSCH; configured to map the number of SS / PBCH block indices to the valid PUSCH occasions and associated DM-RS resources first in ascending order of DM-RS port index and then in ascending order of DM-RS sequence index.

13. The non-transitory computer-readable storage medium of claim 12.

14. causing the processing circuitry to refrain from further mapping the SS / PBCH block index to a PUSCH occasion and a set of associated DM-RS resources if there is a set of associated DM-RS resources and PUSCH occasions that is not mapped to the SS / PBCH block index after an integer number of SS / PBCH block indexes for the associated DM-RS resource mapping cycle and PUSCH occasion within an association period.

14. The non-transitory computer-readable storage medium of claim 13.

15. The association period is determined such that a pattern between the PUSCH occasions and associated DM-RS resources and SS / PBCH block index is repeated at most every 640 milliseconds.

15. The non-transitory computer-readable storage medium of claim 14.

16. The PUSCH transmission in the CG-SDT includes a configured grant PUSCH (CG-PUSCH), and the CG-PUSCH is performed without a PRACH preamble transmission by the UE when operating in an RRC_INACTIVE state.

14. The non-transitory computer-readable storage medium of claim 13.

17. The DM-RS antenna port associated with the PDCCH reception and the DM-RS antenna port associated with the PDSCH reception are assumed to be the SS / PBCH and QCL associated with the PUSCH in terms of Type D properties including average gain and spatial receiver (RX) parameters.

20. The non-transitory computer-readable storage medium of claim 16.

18. An apparatus for a gNodeB (gNB) configured for operation in a fifth generation new radio (5G-NR) system, comprising: the apparatus comprises a processing circuit and a memory; For a physical uplink shared channel (PUSCH) transmission in a radio resource control (RRC) inactive (RRC_INACTIVE) state, the processing circuitry decodes a physical downlink control channel (PDCCH) to detect a downlink control information (DCI) format; When a DCI format for a configured grant-based small data transmission (SDT) (CG-SDT) is detected and a transport block (TB) is received on a corresponding physical downlink shared channel (PDSCH), the processing circuitry: Assume that a demodulation reference signal (DM-RS) antenna port associated with PDCCH reception and a DM-RS antenna port associated with PDSCH reception are quasi-co-located (QCL) with a synchronization signal / physical broadcast channel (SS / PBCH) associated with a physical uplink shared channel (PUSCH) resource for the CG-SDT; configured to encode a PUCCH for transmission using the same spatial domain transmit filter as a last PUSCH transmission during the CG-SDT; the memory is configured to store parameters for the spatial domain transmit filter. Device.

19. The detected DCI formats include DCI format 1_0 for CG-SDT; 20. The apparatus of claim 18.

20. The processing circuitry further comprises: Decoding a CG-PUSCH configuration indicating a number of valid PUSCH occasions and SS / PBCH block indices that map to associated DM-RS resources for transmission of the PUSCH; configured to map the number of SS / PBCH block indices to the valid PUSCH occasions and associated DM-RS resources, first in ascending order of DM-RS port index, and then in ascending order of DM-RS sequence index.

20. The apparatus of claim 19.

21. If there is a set of associated DM-RS resources and PUSCH occasions that is not mapped to the SS / PBCH block index after an integer number of SS / PBCH block indexes for an associated DM-RS resource mapping cycle and PUSCH occasion within an association period, the processing circuitry refrains from further mapping the SS / PBCH block index to a PUSCH occasion and a set of associated DM-RS resources.

21. The apparatus of claim 20.

22. The association period is determined such that a pattern between the PUSCH occasions and associated DM-RS resources and SS / PBCH block index is repeated at most every 640 milliseconds.

22. The apparatus of claim 21.

Images