Small data transmission method and related devices

Abstract

A method and related apparatus for Small Data Transmission (SDT) are provided. In this method, configuration is received from a base station (BS). This configuration indicates a first Reference Signal Received Power (RSRP) threshold and a second RSRP threshold. In response to a downlink path loss (DL) reference RSRP exceeding the first RSRP threshold, an SDT procedure is initiated based on the configured granted CG resources. In response to initiating the SDT procedure based on the CG resources, the method further includes: a Synchronization Signal / Physical Broadcast Channel Block (SSB) from the SSB set if the SSB has an RSRP exceeding the second RSRP threshold. In response to no SSB in the SSB set having an RSRP exceeding the second RSRP threshold, a Random Access (RA) procedure is initiated.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 131,486, filed December 29, 2020, entitled “CONFIGURED UPLINK RESOURCE IN RRC INACTIVE”, Attorney No. US83788; U.S. Provisional Application Serial No. 63 / 131,500, filed December 29, 2020, entitled “SMALL DATA TRANSMISSION BASED ON BEAM OPERATION”, Attorney No. US83789; and U.S. Provisional Application Serial No. 63 / 131,510, filed December 29, 2020, entitled “METHOD AND APPARATUS FOR SMALL DATA TRANSMISSION”, Attorney No. US83790, the contents of which are hereby incorporated by reference in their entirety. Technical Field

[0003] This invention generally relates to wireless communication, and more specifically, to methods and related devices for small data transmission.

[0004] With the massive growth in the number of connected devices and the rapid increase in user / network traffic, various efforts have been made to improve all aspects of wireless communication in next-generation wireless communication systems, such as fifth-generation (5G) New Radio (NR), by increasing data rates, latency, reliability, and mobility. 5G NR systems are designed to provide flexibility and configurability to optimize network services and types to adapt to various use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Summary of the Invention

[0005] This disclosure relates to a method and related apparatus for small data transmission (SDT).

[0006] According to one or more embodiments of this disclosure, a method for a user equipment to perform small data transmission SDT is provided. The method includes, but is not limited to, the following steps: Receiving configuration from a base station (BS). The configuration indicates a first reference signal received power (RSRP) threshold and a second RSRP threshold. In response to a downlink path loss (DL) reference RSRP being higher than the first RSRP threshold, initiating an SDT procedure based on the configuration-granted CG resources. In response to initiating the SDT procedure based on the CG resources, the method further includes: If a physical broadcast channel block (SSB) has an RSRP higher than the second RSRP threshold, a synchronization signal / SSB from an SSB group. In response to no SSB in the SSB group having an RSRP higher than the second RSRP threshold, initiating a random access (RA) procedure.

[0007] According to one or more embodiments of this disclosure, a user equipment (UE) is provided. The UE includes, but is not limited to, a transceiver, a memory, and a processor. The transceiver is used to transmit or receive signals. The memory is used to store instructions. The processor is coupled to the transceiver and the memory. The processor is configured to execute the instructions to perform the following steps: Receiving configuration from a base station (BS). The configuration indicates a first reference signal received power (RSRP) threshold and a second RSRP threshold. In response to a downlink path loss (DL) reference RSRP being higher than the first RSRP threshold, initiating an SDT (Signal Transfer Procedure) procedure by configuring authorized CG resources. In response to initiating the SDT procedure via the CG resources, the method further includes: Receiving a synchronization signal / SSB from a group of SSBs if the physical broadcast channel block (SSB) has an RSRP higher than the second RSRP threshold. In response to no SSB in the SSB group having an RSRP higher than the second RSRP threshold, initiating a random access (RA) procedure. Attached Figure Description

[0008] The various aspects of this exemplary disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. For clarity of discussion, the various features are not drawn to scale, and the dimensions of the various features may be arbitrarily increased or decreased.

[0009] Figure 1 This is a flowchart illustrating a potential process of CG-based SDT according to an exemplary embodiment of this application.

[0010] Figure 2 This is a flowchart illustrating a potential process of RA-based SDT according to an exemplary embodiment of this application.

[0011] Figure 3 This is a schematic diagram illustrating the association between SSB and CG resources and / or CG resource timing, according to an exemplary embodiment of this application.

[0012] Figure 4 This is a flowchart illustrating a method for SDT applicable to a UE according to an exemplary embodiment of this application.

[0013] Figure 5 This is a schematic diagram illustrating an index of CG resources / timings according to an exemplary embodiment of this application.

[0014] Figure 6A This is a schematic diagram illustrating the mapping between SSB (index) and CG resources / timings according to an exemplary embodiment of this application.

[0015] Figure 6B This is a schematic diagram illustrating the association / mapping between SSB (index) and CG resources / timings according to an exemplary embodiment of this application.

[0016] Figure 7 This is a flowchart illustrating a method for a network suitable for SDT according to an exemplary embodiment of this application.

[0017] Figure 8 This is a flowchart illustrating a method for SDT applicable to a UE according to an exemplary embodiment of this application.

[0018] Figure 9 This is a flowchart illustrating a method for SDT applicable to a UE according to an exemplary embodiment of this application.

[0019] Figure 10 This is a flowchart illustrating a CG-based SDT according to an exemplary embodiment of this application.

[0020] Figure 11 This is a flowchart illustrating a method for a network suitable for SDT according to an exemplary embodiment of this application.

[0021] Figure 12 This is a flowchart illustrating a method for a network suitable for SDT according to an exemplary embodiment of this application.

[0022] Figure 13 This is a block diagram illustrating a node for wireless communication according to various aspects of this application. Detailed Implementation

[0023] The abbreviations used in this application are defined as follows, and unless otherwise stated, the abbreviations have the following meanings: full name of the abbreviation

[0024] 3rd Generation Partnership Project (3GPP)

[0025] Acknowledgment (ACK)

[0026] Base Station (BS)

[0027] Buffer Status Request (BSR)

[0028] Bandwidth Part (BWP)

[0029] Control Element (CE)

[0030] Configured Grant (CG)

[0031] Control Resource Set (CORESET)

[0032] Cell-Radio Network Temporary Identifier (C-RNTI) Cyclic Redundancy Check (CRC)

[0033] Channel State Information (CSI)

[0034] Configured Scheduling RNTI (CS-RNTI)

[0035] Common Search Space (CSS)

[0036] Downlink Control Information (DCI)

[0037] Downlink (DL)

[0038] Demodulation Reference Signal (DM-RS)

[0039] Data Radio Bearer (DRB)

[0040] Frequency-Division Duplex (FDD)

[0041] Frequency Range (FR)

[0042] Hybrid Automatic Repeat reQuest (HARQ)

[0043] Information Elements (IE)

[0044] Layer 1 (L1)

[0045] Logical Channel Group (LCG)

[0046] Logical Channel (LCH)

[0047] Medium Access Control (MAC)

[0048] Master Cell Group (MCG)

[0049] Maximum Permissible Exposure (MPE)

[0050] Message (Msg / MSG)

[0051] Negative Acknowledgment (NACK)

[0052] New Radio (NR)

[0053] Network (NW)

[0054] Normal uplink (NUL)

[0055] Physical Broadcast Channel (PBCH)

[0056] Primacy Cell (PCell)

[0057] Configured Maximum Output Power (PCMAX), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Protocol Data Unit (PDU)

[0058] Physical Layer (PHY)

[0059] Physical Random Access Channel (PRACH)

[0060] Primary Secondary Cell Group Cell (PSCell)

[0061] Physical Uplink Control Channel (PUCCH)

[0062] Physical Uplink Shared Channel (PUSCH)

[0063] Quasi-co-location (QCL)

[0064] Random Access (RA)

[0065] Random Access Channel (RACH)

[0066] Radio Access Network (RAN)

[0067] Random Access Response (RAR)

[0068] Release (Rel)

[0069] Radio Network Temporary Identifier (RNTI) and Radio Resource Control (RRC)

[0070] Reference Signal (RS)

[0071] Reference Signal Received Power (RSRP)

[0072] Reference Signal Received Quality (RSRQ)

[0073] Receive (Reception, Rx)

[0074] Secondary Cell (SCell)

[0075] Secondary Cell Group (SCG)

[0076] Synchronization Channel (SCH)

[0077] Subcarrier Spacing (SCS)

[0078] Small Data Transmission (SDT)

[0079] Service Data Unit (SDU)

[0080] System Frame Number (SFN)

[0081] System Information (SI)

[0082] System Information Block (SIB)

[0083] Special Cell (SpCell)

[0084] Signaling Radio Bearer (SRB)

[0085] Synchronization Signal (SS)

[0086] SS / PBCH Block (SSB)

[0087] Supplementary Uplink (SUL)

[0088] Timing Advance (TA)

[0089] Transport Block (TB)

[0090] Transmission Configuration Indicator (TCI)

[0091] Time-Division Duplex (TDD)

[0092] Transmission (Tx)

[0093] Transport Block Size (TBS)

[0094] Transmission and Reception Point (TRP)

[0095] Tracking Reference Signal (TRS)

[0096] Uplink Control Information (UCI)

[0097] User Equipment (UE)

[0098] The following description contains specific information relating to the exemplary embodiments in this disclosure. The accompanying drawings and detailed description are merely exemplary embodiments. However, this disclosure is not limited to these exemplary embodiments. Other variations and embodiments of this disclosure will occur to those skilled in the art. Unless otherwise stated, the same or corresponding parts in the drawings may be indicated by the same or corresponding reference numerals. Furthermore, the drawings and illustrations in this disclosure are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

[0099] For the purposes of consistency and ease of understanding, the same reference numerals are used to indicate the same features in the exemplary drawings (although this is not the case in some examples). However, features in different embodiments may differ in other respects, and therefore should not be narrowly limited to the features shown in the drawings.

[0100] Descriptions using the phrases "one implementation" or "some implementations" can each be considered as one or more identical or different implementations. Descriptions using the phrases "one embodiment" or "some embodiments" can each be considered as one or more identical or different embodiments. The term "coupled" is defined as a direct or indirect connection via an intermediate component and is not necessarily limited to a physical connection. The term "comprising" when used means "including but not limited to"; it explicitly indicates members of an open-ended combination, group, series, and equivalent. The phrase "at least one of A, B, and C" or "at least one of A, B, and C" means "only A, or only B, or only C, or any combination of A, B, and C."

[0101] Any sentence, paragraph, (sub)item, point, action, behavior, term, alternative, aspect, example, or claim described in this disclosure may be logically, reasonably, and appropriately combined to form a particular method. Any sentence, paragraph, (sub)item, point, action, behavior, term, alternative, aspect, example, or claim described in this disclosure may be implemented independently and separately to form a particular method. Dependencies, such as “based on,” “more specifically,” “in some embodiments,” “in an alternative,” “in an example,” “in an aspect,” etc., are merely possible examples in this disclosure and do not limit the particular method. One aspect of this disclosure may be used, for example, in communications, communication devices (e.g., mobile phone devices, base station devices, wireless LAN devices, and / or sensor devices), integrated circuits (e.g., communication chips), and / or programs. According to any sentence, paragraph, (sub)item, point, action, behavior, term, alternative, aspect, example, implementation, or claim in this disclosure, “X / Y” may include the meaning of “X or Y.” "X / Y" may also include the meaning of "X and / or Y" in any sentence, paragraph, (sub)item, point, action, behavior, term, alternative, aspect, example, implementation, or claim described in this disclosure.

[0102] Furthermore, for purposes of explanation and non-restriction, specific details such as functional entities, technologies, protocols, standards, and equivalents are provided to offer an understanding of the described technologies. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, and equivalents are omitted to avoid unnecessarily obscuring the description.

[0103] Those skilled in the art will readily recognize that any one or more network functions or algorithms described in this disclosure can be implemented by hardware, software, or a combination of software and hardware. The described functions may correspond to modules, which may be software, hardware, firmware, or any combination thereof. Software implementations may include computer-executable instructions stored on a computer-readable medium such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions to perform the described one or more network functions or algorithms. The microprocessor or general-purpose computer may be constructed from application-specific integrated circuits (ASICs), programmable logic arrays, and / or using one or more digital signal processors (DSPs). While the several exemplary embodiments described in this specification are directed to software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware or hardware or a combination of hardware and software are also within the scope of this disclosure.

[0104] Computer-readable media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), magnetic tape, magnetic tape, disk storage devices, or any other equivalent medium capable of storing computer-readable instructions.

[0105] Wireless communication network architectures (e.g., Long Term Evolution (LTE) systems, LTE-A systems, LTE-Pro systems, or 5G NR Radio Access Networks (RANs)) typically include at least one base station, at least one UE, and one or more optional network components that provide connectivity to the network. The UE communicates with the network (e.g., Core Network (CN), Evolved Packet Core (EPC) network, Evolved Universal Terrestrial Radio Access network (E-UTRAN), 5G Core (5GC), or the Internet) through the RAN established by one or more base stations.

[0106] It should be noted that, in this application, the UE may include, but is not limited to, a mobile station, mobile terminal, device, or user communication radio terminal. For example, the UE may be a portable wireless device, including but not limited to mobile phones, tablet computers, wearable devices, sensors, vehicles, or personal digital assistants (PDAs) with wireless communication capabilities. The UE may be configured to receive and transmit signals to one or more cells in a radio access network via an air interface.

[0107] The base station is configured to provide communication services according to at least one of the following Radio Access Technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, commonly referred to as 2G), GSM Evolution with Enhanced Datarates for GSM Evolution (EDGE) Radio Access Network (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS, commonly referred to as 3G) based on Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, Evolved Long-Term Evolution (eLTE, e.g., LTE linked to 5GC), NR (commonly referred to as 5G), and / or LTE-A Pro. However, the scope of this application is not limited to the above-mentioned protocols.

[0108] Base stations may include, but are not limited to, node Bs (NBs) in UMTS, evolved node Bs (eNBs) in LTE or LTE-A, radio network controllers (RNCs) in UMTS, base station controllers (BSCs) in GSM / GSM Enhanced Data Rates for GSM Evolution (EDGE) radio access networks (GERAN), next-generation eNBs (ng-eNBs) in evolved global terrestrial radio access (E-UTRA) BSs connected to 5GC, next-generation node Bs (gNBs) in 5G access networks (5G-AN), and any other devices capable of controlling radio communications and managing radio resources within the cell. A BS can serve one or more UEs through its radio interface to the network.

[0109] A base station (BS) can be operable to provide radio coverage to a specific geographic area using multiple cells included in the RAN. The BS can support cell operation. Each cell can be operable to provide service to at least one UE within its radio coverage area. Specifically, each cell (typically referred to as the serving cell) can provide service to one or more UEs within its radio coverage area (e.g., each cell schedules downlink (DL) resources and optional uplink (UL) resources to at least one UE within its radio coverage area for DL ​​and optional UL packet transmissions). The BS can communicate with one or more UEs in a radio communication system through multiple cells.

[0110] Cells can be allocated sidelink (SL) resources to support Proximity Service (ProSe) or Vehicle to Everything (V2X) services. Each cell can have coverage areas overlapping with other cells. In the case of Multi-RAT Dual Connectivity (MR-DC), the primary cell of a Master Cell Group (MCG) or Secondary Cell Group (SCG) can be referred to as a Special Cell (SpCell). A Primary Cell (PCell) can refer to the SpCell of an MCG. A Primary SCG Cell (PSCell) can refer to the SpCell of an SCG. An MCG can refer to a group of serving cells associated with a Master Node (MN), including SpCells and one or more optional Secondary Cells (SCells). An SCG can refer to a group of serving cells associated with a Secondary Node (SN), including SpCells and one or more optional SCells.

[0111] As mentioned above, the NR frame structure supports flexible configuration to adapt to various next-generation (e.g., 5G) communication requirements, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), ultra-reliable and low-latency communication (URLLC), while meeting the requirements of high reliability, high data rate, and low latency. As agreed in 3GPP, orthogonal frequency division multiplexing (OFDM) technology can be used as the baseline for NR waveforms. An extended set of OFDM parameters, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP), can also be used. In addition, two coding schemes for NR are considered: (1) low-density parity-check (LDPC) codes and (2) polar codes. The adaptability of the coding scheme can be configured based on channel conditions and / or service applications.

[0112] Furthermore, it is also considered that the transmission time interval (TX) of a single NR frame should include at least downlink (DL) transmission data, protection time segmentation, and uplink (UL) transmission data. Each component of the DL transmission data, protection time segmentation, and UL transmission data should be configurable, for example, based on NR network dynamics. Additionally, sidelink resources can also be provided in the NR frame to support ProSe service, (E-UTRA / NR) sidelink service, or (E-UTRA / NR) V2X service.

[0113] Furthermore, the terms "system" and "network" are used interchangeably in this document. The term "and / or" is used only to describe the relationship between related objects and indicates that three relationships can exist. For example, A and / or B can indicate that A exists alone, A and B exist simultaneously, or B exists alone. Additionally, the character " / " in this document generally indicates that the former and the latter related objects are in an "or" relationship.

[0114] As mentioned above, next-generation (e.g., 5G NR) wireless networks will support more capacity, data, and services. UEs configured with multiple connectivity can connect to a master node (MN) acting as the anchor and one or more secondary nodes (SNs) for data transmission. Each of these nodes can be formed by a cell group comprising one or more cells. For example, a master cell group (MCG) can be formed by an MN, and a secondary cell group (SCG) can be formed by an SN. In other words, for a UE configured with dual connectivity (DC), an MCG is a group of one or more serving cells, including PCells and zero or more secondary cells. Conversely, an SCG is a group of one or more serving cells, including PSCells and zero or more secondary cells.

[0115] As described above, the Primary Cell (PCell) can be an MCG cell operating on the primary frequency, where the UE performs the initial connection establishment procedure or initiates a connection re-establishment procedure. In MR-DC mode, the PCell can belong to the MN. The Primary SCG Cell (PSCell) can be an SCG cell where the UE performs random access (e.g., when performing reconfiguration using a synchronization procedure). In MR-DC, the PSCell can belong to the SN. A Special Cell (SpCell) can refer to either the PCell of an MCG or the PSCell of an SCG, depending on whether the MAC entity is associated with an MCG or an SCG. Otherwise, the term Special Cell can refer to the PCell. A Special Cell can support Physical Uplink Control Channel (PUCCH) transmission and contention-based Random Access (CBRA) and can always be active. Additionally, for a UE in the RRC_CONNECTED state without a configured CA / DC, it can communicate only with the serving cell (SCell) that is the primary cell. Conversely, for a UE in the RRC_CONNECTED state configured using CA / DC, a set of serving cells, including the special cell and all secondary cells, can communicate with the UE.

[0116] First, let me introduce some related technologies.

[0117] SDT: SDT can be UL data transmission during RRC_INACTIVE. The packet size (or data volume) of the UL data can be below a threshold. UL data in SDT can be transmitted during the SDT process. UL data in SDT can be transmitted via Msg 3 (e.g., based on a 4-step RA), via MsgA (e.g., based on a 2-step RA), and / or via CG resources (e.g., CG type 1). When the UE is in RRC_INACTIVE, UL data in SDT can be transmitted based on dynamic scheduling and / or semi-persistent scheduling.

[0118] User Equipment (UE): UE can be referred to as a PHY / MAC / RLC / PDCP / SDAP / RRC entity.

[0119] Network (NW): NW can be a network node, TRP, cell (e.g., SpCell, PCell, PSCell and / or SCell), eNB, gNB and / or base station.

[0120] Serving cell: PCell, PSell, or SCell (secondary cell). The serving cell can be active or deactivated.

[0121] Special Cell (SpCell): For dual-connectivity operation, the term "Special Cell" refers to the PCell of the MCG (Primary Cell Group) or the PSCell of the SCG (Secondary Cell Group), depending on whether the MAC entity is associated with the MCG or SCG respectively. Otherwise, the term "Special Cell" refers to the PCell. Special cells support PUCCH (Physical Uplink Control Channel) transmission and contention-based random access, and are always active.

[0122] Beam (SSB / TRS / CSI-RS / Auxiliary RS / TCI State): The term "beam" or "SSB / TRS / CSI-RS / Auxiliary RS / TCI State" can be replaced by a spatial filter. For example, when a UE reports a preference for the gNB TX beam, the UE is essentially selecting the spatial filter used by the gNB. The term "beam information" can be used to provide information about which beam / spatial filter is being used / selected. In one example, a single reference signal is transmitted by applying a single beam (spatial filter). Therefore, the beam or beam information can be represented by a reference signal resource index. The beam can be a DL and / or UL beam. The beam can be a Tx beam and / or an Rx beam. The beam can be a UE beam and / or an NW beam. The beam can reference a reference signal (e.g., SSB / TRS / CSI-RS / Auxiliary RS / TCI State) and / or a TCI state. The beam can be indicated by reference signals (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI status) and / or TCI status.

[0123] SSB parameters: The UE can be configured to have one or more of the following configurations for SSB.

[0124] absoluteFrequencySSB: The frequency of the SSB used for this serving cell. Unless otherwise specified, SSB-related parameters (such as the SSB index) provided for the serving cell reference this SSB frequency. The cell-defined SSB of the PCell is always located on the synchronization grating. If the frequency can also be identified by the GSCN value (e.g., as specified in 3GPP TS 38.101-1), the frequency is considered to be on the synchronization grating. If this field is absent, SSB-related parameters may not exist, such as ssb-PositionsInBurst, ssb-periodicityServingCell, and subcarrierSpacing in the ServingCellConfigCommon IE. If this field is absent, the UE can obtain a timing reference from the SpCell. This is only supported when the SCell and SpCell are located in the same frequency band.

[0125] ssb-PositionsInBurst: Indicates the temporal bit settings of the SS blocks transmitted in a half-frame and the SS / PBCH blocks defined in 3GPP TS 38.213. The first / leftmost bit corresponds to SS / PBCH block index 0, the second bit corresponds to SS / PBCH block index 1, and so on. A value of 0 in the bitmap indicates that the corresponding SS / PBCH block was not transmitted, while a value of 1 indicates that the corresponding SS / PBCH block was transmitted. The network can be configured in this field with the same mode as the corresponding field in ServingCellConfigCommonSIB.

[0126] ssb-periodicityServingCel: SSB period (milliseconds) used for rate matching. If this field is not present, the UE applies the value ms5. (As specified in 3GPP TS 38.213, for example).

[0127] ssbSubcarrierSpacing: Subcarrier spacing of the SSB. Values ​​of 15kHz or 30kHz (FR1) and 120kHz or 240kHz (FR2) may be applicable.

[0128] TCI Status: The TCI status indicates the quasi-co-address information of the DM-RS antenna port, used for PDCCH reception in the corresponding CORESET. The TCI status can be used to provide a QCL relationship between the DL RS and the PDCCH DMRS port in an RS group (TCI status).

[0129] Small Data Transmission (SDT)

[0130] NR supports the RRC_INACTIVE state, and UEs with infrequent (e.g., periodic and / or aperiodic) data transmissions are typically maintained by the network in the RRC_INACTIVE state. Prior to Rel-16, RRC_INACTIVE did not support data transmission. Therefore, for any DL reception and / or UL data transmission, the UE had to restore the connection (i.e., move to the RRC_CONNECTED state). Regardless of how small and infrequent the data packets were, a connection setup and subsequent release to the RRC_INACTIVE state occurred with each data transmission. This resulted in unnecessary power consumption and signaling overhead.

[0131] Signaling overhead from UEs in the RRC_INACTIVE state due to the transmission of small data packets is a common problem, and it will become a critical issue as the number of UEs increases in NR, affecting not only network performance and efficiency but also UE battery performance. Typically, any device with intermittent small data packets in the RRC_INACTIVE state will benefit from enabling small data transmission in this state.

[0132] The key enabling factors for small data transfers in NR, namely RRC_INACTIVE, 2-step, 4-step RACH, and / or configuration authorization type 1, have been designated as part of the legacy protocol. Therefore, one or more of the embodiments described above build upon these building blocks to enable small data transfers in the RRC_INACTIVE state of NR.

[0133] Solutions for small data transfer in UL within RRC_INACTIVE may be service-agnostic, satisfying different service requirements. In one or more embodiments disclosed herein, candidate solutions may be assumed to possess one or more of the following characteristics:

[0134] Small data transfers can be performed using RACH-based schemes (e.g., 2-step and / or 4-step RACH procedures) and / or pre-configured PUSCH resources (e.g., reusing configured license type 1).

[0135] The UE AS context used for uplink data transmission in RRC_INACTIVE (e.g., the UE Inactive AS context) should be the same as that used during the state transition from RRC_INACTIVE to RRC_CONNECTED. The UE AS context is located and identified in the network by an "AS context ID," which is assigned by the network and stored in the UE (and the network) when the UE enters RRC_INACTIVE. This AS context is used to locate the AS context in cases where the UE attempts to transmit small data and / or performs a transition to RRC_CONNECTED. The UE AS context can be stored in the "anchor" / source gNB and can be extracted to the new serving gNB when needed, triggering small data transmission and / or a transition from RRC_INACTIVE to RRC_CONNECTED. The UE ID uniquely identifies the UE context in the RAN.

[0136] Small data transmissions can use the AS context ID transmitted in the "First" message for contention resolution (e.g., at least when using RACH). Upon receiving the "First" message with small UL data, the network should be able to inform the UE that it should move to the connected RRC_CONNECTED via a DL-RRC message (e.g., RRCConnectionResume). If necessary, the "First" message with small UL data can provide information enabling the network to apply overload control and prioritization.

[0137] The UE provides all the necessary information in the “first” message with initial uplink data transmission to enable the network to move the UE to the RRC_CONNECTED state or to enable the network to keep the UE in the RRC_INACTIVE state, for example, BSR.

[0138] Small data transfer solutions can at least support the RLC ARQ mechanism.

[0139] When the UE transmits small data in RRC_INACTIVE, the network should be able to perform a context update. This update should depend on RRC signaling and should be completed in a "second" message (e.g., an RRCConnectionResume message triggered by the small data transmission or a control response message).

[0140] The UE context in RRC_INACTIVE can include configurations such as radio bearers, logical channels, and / or security.

[0141] The UE can maintain the same PDCP entity as in RRC_CONNECTED, and maintain the PDCP COUNT and PDCP SN.

[0142] Multiple DRBs (and / or SRBs) can be maintained in RRC_INACTIVE, and data transmission can occur on the DRB associated with the relevant service. For small data transmissions in RRC_INACTIVE, the UE should use the currently configured DRB. If a bearer with configured QoS is permitted for UL small data transmissions, QoS compliance may still be required.

[0143] An RRC connection restoration request may contain at least the information required by the network to perform contention resolution, identify the UE context, and verify that it is correct. Upon receiving a response from the network (e.g., "RRC Connection Restoration"), the UE should be able to recognize that it is the correct network, perform contention resolution and receive DL data, and either remain in RRC_INACTIVE or restore its previously suspended connection, i.e., move to the RRC_CONNECTED state.

[0144] It can support DL transmission / response and subsequent UL transmission without requiring the UE to move to RRC_CONNECTED.

[0145] When transmitting MSG3, HARQ ACK / NACK transmission can be supported in the same way as in LTE (i.e., once the UE transmits the first UL packet, the UE is expected to continuously monitor the DL PDCCH-like channel, and DL RLC ACK / NACK messages can be scheduled normally while the UE is still listening to the DL channel).

[0146] The UE provides information so that the network can decide whether to put the UE in RRC_INACTIVE or move it to RRC_CONNECTED.

[0147] Configured Grant (CG)

[0148] By configuring authorization, network devices such as gNBs can allocate uplink resources for the initial HARQ transmission to the UE. Two types of uplink authorization configurations are defined:

[0149] Through Type 1 (e.g., CG Type 1), RRC directly provides the configured uplink grant (including periodicity).

[0150] With type 2 (e.g., CG type 2), RRC defines the period of configured uplink grant, while PDCCH addressed to CS-RNTI can transmit signals to activate or deactivate the configured uplink grant; for example, PDCCH addressed to CS-RNTI indicates that the uplink grant can be implicitly reused according to the period defined by RRC until it is deactivated.

[0151] When CG type 1 is configured, NW and / or RRC can be configured with the following parameters:

[0152] cs-RNTI: CS-RNTI used for retransmission;

[0153] periodicity: Configures the period for authorization type 1;

[0154] timeDomainOffset: In the time domain, the offset of the resource relative to SFN=0;

[0155] timeDomainAllocation: Allocates the configured uplink grant in the time domain that includes startSymbolAndLength (i.e., SLIV in 3GPP TS 38.214);

[0156] nrofHARQ-Processes: Configures the number of authorized HARQ processes.

[0157] When configuring CG type 1 for use in the serving cell via upper-layer configuration, the UE (or MAC entity) can:

[0158] Store the uplink grant provided by the upper layer as the configured uplink grant (for the indicated serving cell);

[0159] Initialize or reinitialize the configured uplink grant to begin in the symbol according to timeDomainOffset and S (derived from SLIV as specified in 3GPP TS 38.214) and reappear periodically.

[0160] CG-based SDT

[0161] Figure 1This is a flowchart illustrating a potential process of a CG-based SDT according to an exemplary embodiment of this disclosure. Reference Figure 1 Note that the order of the steps in this figure can be changed according to the embodiment. For example, step S120 may occur before step S110, and so on.

[0162] Step S110: When UE 110 is in RRC_CONNECTED and / or RRC_INACTIVE, UE 110 may transmit a CG configuration request to network 120 to indicate its preference for RRC_INACTIVE configuration of CG type 1.

[0163] Step S120: NW 120 can decide to move UE 110 to RRC_INACTIVE by transmitting an RRC release (including suspendconfig) message to UE 110. The RRC release message may include CG configuration to configure CG resources to UE 110. Alternatively, when UE 110 is in RRC_CONNECTED, CG configuration can be provided in RRC reconfiguration. CG configuration may include, but is not limited to, the following information:

[0164] CG cycle

[0165] TBS

[0166] The number of CG resources implicitly released

[0167] CG timer

[0168] retransmission timer

[0169] Number of HARQ processes reserved for CG in SDT

[0170] RSRP threshold selected for SSB and the correlation between SSB and CG resources

[0171] TA-related parameters (such as TA timer)

[0172] Step S130: UE 110 can perform SDT via CG resources (in RRC_INACTIVE) according to CG configuration (e.g., configured in step 120).

[0173] Step S140: Subsequent data transmission may be the transmission of multiple UL and / or DL ​​packets as part of the same SDT mechanism, and does not transition to RRC_CONNECTED (e.g., the UE remains in RRC_INACTIVE). UE 110 may monitor the PDCCH in a specific search space (e.g., SDT search space) via a specific RNTI (e.g., C-RNTI and / or CS-RNTI) to receive dynamic scheduling of new UL and / or DL ​​transmissions and / or corresponding retransmissions. UE 110 may monitor the PDCCH in a specific search space (e.g., SDT search space) via a UE-specific RNTI (e.g., C-RNTI and / or CS-RNTI) to receive dynamic scheduling of retransmissions of CG type 1. UE 110 may perform subsequent data transmission via CG according to the CG configuration (e.g., configured in step S120).

[0174] Step S150: NW 120 may transmit an RRC release message to keep UE 110 in RRC_INACTIVE or move UE 110 to RRC_IDLE. Alternatively, NW 120 may transmit an RRC recovery message to move UE 110 to RRC_CONNECTED.

[0175] SDT based on RA

[0176] Figure 2 This is a flowchart illustrating a potential process of RA-based SDT according to an exemplary embodiment of this disclosure. Reference Figure 2 Note that the order of the steps in this figure can be changed according to the embodiment. For example, step S220 may occur before step S210, and so on.

[0177] Step S210: When UE 110 in RRC_INACTIVE state has UL data available for transmission, it can initiate an RA-based SDT procedure for transmitting the UL data. UE 110 can select either a 4-step RA type or a 2-step RA type. Furthermore, the PRACH resources used for the RA-based SDT procedure (e.g., an RA preamble with small data indication) and the normal RA procedure (e.g., an RA preamble without small data indication) may differ. Here, UE 110 can select PRACH resources for the RA-based SDT procedure.

[0178] Step S220: After transmitting the RA preamble, UE 110 may transmit an RRC message via MSG3 (when the 4-step RA type is selected) or MSGA (when the 2-step RA type is selected). The RRC message may be an RRCResumeRequest message. In addition to the RRC message, MAC CE (e.g., BSR) and DRB data packets (e.g., small data) may also be included in MSG3 / MSGA.

[0179] Step S230: Once MSG3 / MSGA has been transmitted, UE 110 can monitor RA-RNTI / MSGB-RNTI for MSG4 / MSGB, which will carry the contention resolution ID. Additionally, NW can transmit RRC messages in MSGA / MSGB. RRC messages can be RRCRelease messages (with suspendConfig IE) or RRCResume messages. If UE 110 receives an RRCRelease message (with suspendConfig IE), it can maintain RRC_INACTIVE; if UE 110 receives an RRCResume message, it can enter RRC_CONNECTED. Furthermore, MAC CEs (e.g., BSR) and SRB / DRB data packets (e.g., small data) can also be included in MSG4 / MSGB.

[0180] Steps S240 / S250: Once the RA procedure is successfully completed, UE 110 may monitor a specific RNTI (e.g., C-RNTI / CS-RNTI) for subsequent data transmission. Subsequent data transmission may be the transmission of multiple UL and / or DL ​​packets as part of the same SDT mechanism and does not transition to RRC_CONNECTED (e.g., UE 110 remains in RRC_INACTIVE). UE 110 may monitor the PDCCH via a specific RNTI (e.g., C-RNTI / CS-RNTI) to receive dynamic scheduling of new UL and / or DL ​​transmissions and / or corresponding retransmissions. UE 110 may monitor the PDCCH via a UE-specific RNTI (e.g., C-RNTI or CS-RNTI) to receive dynamic scheduling of CG type 1 retransmissions.

[0181] Step S260: Once the RRRCrease message (with suspendConfig IE) is received, UE 110 can stop monitoring C-RNTI and enter the normal INACTIVE state.

[0182] CG-based SDT beam operation

[0183] In order to perform SDT in RRC_INACTIVE, the UE may need to perform beam alignment with the network to enable data transmission. In RA-based SDT, beam and network alignment is obtained through the RA procedure. For CG-based SDT, since the RA procedure is skipped, it is necessary to consider how to obtain beam alignment with the network.

[0184] One implementation relies on the association between CG resources and SSBs. Note that in this disclosure, SSB or SSB index may refer to a beam, and a beam may refer to an SSB or SSB index. Figure 3 This is a schematic diagram illustrating the association between SSB and CG assets and / or CG asset timing, according to an exemplary embodiment of this disclosure. Initial beam alignment is obtained, such as... Figure 3 As shown. Since the UE can perform SSB-based measurements under RRC_INACTIVE, the SSB measurement results can be used to select the appropriate beam for CG transmission. When the NW receives UL data on a specific CG resource, the NW can know on which DL beam (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI state) the DL response is transmitted based on the association between the SSB and the CG resource. When the UE receives a DL response that may be a PDCCH / DCI indication and / or L1 ACK, the UE can consider that it has achieved beam alignment with the network.

[0185] The underlying process of SDT beam manipulation based on CG:

[0186] When the UE is transferred to the RRC_INACTIVE state, CG resources and their association with SSB and / or SSB groups can be provided by the NW and stored by the UE as UE inactive AS content.

[0187] The UE can perform SSB-based measurements in RRC_INACTIVE and select an SSB with an RSRP higher than a threshold (e.g., RSRP-ThresholdSSB) from the relevant SSBs before initiating a CG-based SDT and / or transmitting small data via CG resources. The UE can then transmit UL data via the CG resources associated with the selected SSB. The NW can then determine which DL beam (e.g., SSB / TRS / CSI-RS / Secondary RS / TCI state) is suitable for the UE. Additionally and optionally, the UE can explicitly / implicitly indicate beam information (e.g., selected / candidate / qualified SSB index) to the NW via CG resources. Beam information can be indicated via RRC signaling, MAC signaling (e.g., MAC CE), and / or PHY signaling.

[0188] The UE can receive DL responses from the NW based on the selected SSB.

[0189] Correlation / mapping between beam / SSB and CG

[0190] Figure 4 This is a flowchart illustrating a method suitable for a UE to use SDT according to an exemplary embodiment of this disclosure. Reference Figure 4 The UE receives the CG configuration for SDT from the BS (step S410). The UE receives the SSB group from the BS (step S430). The UE receives the mapping ratio configuration from the BS (step S450). The mapping ratio configuration indicates the number of SSBs for each CG resource. The SSBs are configured by the SSB group, and the CG resources are configured by the CG configuration for SDT. The UE determines the mapping between the SSB index of the SSB and the CG resource based on the mapping ratio configuration and the ascending order of the CG resource indexes (step S470).

[0191] In one embodiment, the CG configuration for SDT is indicated to the UE by the NW. CG resources / timing can be configured through the CG configuration for SDT.

[0192] In one embodiment, the CG configuration may include a configuration of the association / mapping between SSB / SSB indexes and CG resources / timing. Specifically, the CG configuration can be used to configure CG resources for the UE in SDT and / or RRC_INACTIVE.

[0193] In one embodiment, the mapping ratio configuration may be included in the CG configuration used for SDT.

[0194] In one embodiment, CG configuration may be included in a dedicated RRC resource, an RRC reconfiguration message, and / or an RRC release message (including suspendconfig).

[0195] In one embodiment, the configuration of the association / mapping between beams (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI status) and CG resources / timings may include parameters indicating which CG resource / timing is associated / mapped with an SSB (index). Specifically, an SSB index may be associated / mapped to one or more CG resources / timings. Alternatively, a CG resource / timing may be associated / mapped to one or more SSBs (indexes).

[0196] In one embodiment, NW may indicate the same transport block size (TBS) for all CG resources / timings associated with different beams.

[0197] In one embodiment, the configuration of the association / mapping between SSB / SSB indexes and CG resources / timings can be indicated from the NW to the UE via dedicated RRC messages, RRC release messages (including suspendconfig), RRC reconfiguration messages and / or system information (e.g., SIBx, where x is an integer).

[0198] In one embodiment, one or more SSBs can be configured by an SSB group indicated from the NW to the UE. That is, an SSB group may include one or more SSB / SSB indexes.

[0199] In one embodiment, an SSB group or one or more SSB / SSB indexes can be configured for a UE from the NW via an RRC release message (including suspendconfig) or via system information (e.g., SIBx, where x is an integer).

[0200] In some embodiments, an SSB group or one or more SSB / SSB indexes can be configured for a UE from the NW via system information. For example, an SSB group or SSB (index) may be provided in SIB 1 (e.g., via ssb-PositionsInBurst) and / or in the ServingCellConfigCommon IE. That is, system information may be indicated by SIB 1 or the ServingCellConfigCommon IE.

[0201] In one embodiment, if an SSB group or SSB / SSB index is not configured via an RRC release message, an SSB group or one or more SSB / SSB indexes can be configured for a UE via system information from the NW.

[0202] In one embodiment, when the UE is in RRC_CONNECTED, the UE can receive the CG configuration and / or the association / mapping between SSB / SSB index and CG resource / CG timing in an RRC reconfiguration message. When the UE is in RRC_CONNECTED and / or when the UE enters RRC_INACTIVE, the UE can store the configuration. Then, when the UE switches to RRC_INACTIVE, the UE can apply the stored configuration. When the UE receives an RRC release message (with a suspended configuration), the UE can apply the stored configuration. When the UE receives an RRC release message (with a suspended configuration) and a specific indication included in the RRC release message instructs the UE to apply it, the UE can apply the stored configuration.

[0203] In one embodiment, the configuration of the association / mapping between SSB / SSB indexes and CG resources / opportunities may include a mapping ratio configuration indicated by the NW, and the UE may configure this mapping ratio configuration. The mapping ratio configuration indicates the number of SSBs for each CG resource / opportunity. For example, the value "oneEighth" may correspond to one SSB associated with 8 CG resources / opportunities, the value "oneFourth" may correspond to one SSB associated with 4 CG resources / opportunities, and so on.

[0204] In some embodiments, based on the mapping ratio configuration, a UE can be provided with the number N of SSBs (indices) associated with a CG resource / opportunity. In one embodiment, if N < 1, then one SSB (indice) can be associated / mapped with 1 / N consecutive (valid) CG resources / opportunities. In one embodiment, if N >= 1, then all N consecutive SSBs (indices) can be associated / mapped with one CG resource / opportunity.

[0205] In some embodiments, the mapping between SSBs (indexes) and CG resources / timings can be determined based on the ascending order of the CG resource / timing indexes. Specifically, SSBs (indexes) can be mapped to (valid) CG resources / timings based on one or more of the following rules:

[0206] In an alternative scheme, the CG resource / timing guide is a CG-specific guide. For example, the mapping can be determined in ascending order of CG-specific indices (e.g., DM-RS resource index, CG index, CG periodic index, etc.).

[0207] In some implementations, each consecutive number of N SSB indices can be mapped to a valid CG resource / opportunity (e.g., a PUSCH opportunity) and an associated DM-RS resource.

[0208] First, in the PUSCH timing, the DM-RS resource index is determined in ascending order, where the DM-RS resource index can be determined first in ascending order of the DM-RS port index, and then in ascending order of the DM-RS sequence index.

[0209] Secondly, configure the periodic index in ascending order (e.g., PUSCH configures the periodic index).

[0210] In an alternative approach, the index of CG resources / timing can be the frequency resource index of the CG resources / timing. For example, the mapping can be determined according to the ascending order of the frequency resource indexes of the frequency (multiplexed) CG resources / timing.

[0211] In an alternative approach, the index of CG resources / timings can be a time resource index of CG resources / timings. For example, the mapping can be determined according to the ascending order of the resource indices of CG resources / timings and / or CG cycles configured by the configuration (e.g., PUSCH configuration).

[0212] In an alternative approach, the index of CG resources / timing can be an index of symbol / slot / subframe / ms / s. For example, the mapping can be determined by ascending order of the index of symbol / slot / subframe / ms / s (e.g., PUSCH symbol / slot / subframe).

[0213] In an alternative approach, the index for CG resources / timing can be the index for CG cycles. For example, the mapping can be determined in ascending order of the CG cycle index.

[0214] In an alternative approach, the index of the CG resource / timing can be the index of the DM-RS resource. For example, for a demodulation scheme, the mapping can be determined by the ascending order of the DM-RS resource indices.

[0215] In an alternative approach, the CG resource / timing can be referred to as the PUSCH resource / timing.

[0216] Figure 5 This is a schematic diagram illustrating an index of CG resources / timings according to an exemplary embodiment of this disclosure. Reference Figure 5 CG resources / opportunities may include two CG indices (e.g., CG index 0 and CG index 1). Time resources / opportunities (indices) may include four CG resources / opportunities in the frequency domain (e.g., frequency index 0 to frequency index 3 in ascending order of frequency resource indices). In the time domain, the time periods / intervals of CG resources / opportunities can be configured to the UE. For example, a period / interval can be allocated between time index 0 and time index 1. Time index 0, time index 1, and time index 2 will form the ascending order of time resource indices.

[0217] Figure 6A This is a schematic diagram illustrating the mapping between SSB (Index) and CG resources / timings according to an exemplary embodiment of this disclosure. Reference Figure 6A The association / mapping between SSB and CG resources / timing can be based on examples. Figure 5Confirmed. An SSB group may include 8 SSB / SSB indices. Each SSB (index) may be associated with / mapped to a combination of CG, frequency, and / or time indices. A combination of CG, frequency, and time indices can be a CG resource / timing. For example, SSB1 ma is associated with / mapped to a combination of CG index 0, frequency index 0, and time index 0, SSB2 is associated with / mapped to a combination of CG index 1, frequency index 0, and time index 0, and so on. Therefore, the mapping ratio is configured as one SSB per CG resource.

[0218] In one embodiment, the UE may select an SSB from an SSB group during the SDT procedure. The SSB selected from the SSB group has an RSRP higher than the corresponding RSRP threshold. In one embodiment, the UE may select a CG resource corresponding to the selected SSB in response to determining the association / mapping between the SSB index of the selected SSB and the CG resource / timing.

[0219] In one embodiment, an SSB group or one or more SSB / SSB indexes can be configured for a UE from the NW via an RRC release message or via system information.

[0220] In an alternative scheme, an SSB group can be an SSB subgroup (e.g., configured by an SDT SSB subgroup configuration). For an SSB-to-CG PUSCH mapping within a CG configuration, the SSB group can be indicated by the NW. If an SSB group is missing, the UE can assume that the SSB group includes all actually transmitted SSBs configured by SIB1.

[0221] In some embodiments, the UE may be provided by an SSB group with multiple SS / PBCH block indices to map to multiple valid CG / PUSCH timings for PUSCH transmission in associated periods. If no SSB group is provided to the UE, the UE may determine the mapping based on the value of ssb-PositionsInBurst in SIB1 or via ServingCellConfigCommon. The CG / PUSCH timing for PUSCH transmission may be defined by time resources and / or frequency resources, and / or may be associated with the DM-RS provided by cg-DMRS-Configuration for the configuration of PUSCH transmission.

[0222] In some embodiments, an SSB group or one or more SSB / SSB indexes are configured for a UE via system information from the NW. For example, the SSB group or SSB (index) may be provided in SIB 1 (e.g., via ssb-PositionsInBurst) and / or in the ServingCellConfigCommon IE. That is, the system information is indicated by SIB 1 or the ServingCellConfigCommon IE.

[0223] In one embodiment, the CG configuration for SDT configures multiple CG resources / opportunities, and the groups / bundles of transmissions via these CG resources / opportunities are mapped to the same SSB / SSB index in the SSB group.

[0224] In some embodiments, the UE may be configured with beam resource groups / lists (e.g., SSB groups / lists (e.g., indicated by sdt-SSB-subset)) for beam measurements in a CG-based SDT. The UE may perform beam measurements before / during the SDT via the CG. The UE may select a beam / SSB (from the SSB group) based on the SSB measurements.

[0225] In some embodiments, the UE can determine the next available CG resource / opportunity from the CG resource / opportunity corresponding to the selected beam / SSB.

[0226] In some embodiments, the UE may randomly select CG resources / opportunities with equal probability from consecutive CG resources / opportunities corresponding to the selected beam / SSB.

[0227] In some embodiments, the UE may consider possible measurement gaps when determining the next available CG / PUSCH timing corresponding to the selected beam / SSB. For example, the UE may not consider a CG / PUSCH timing that overlaps with a measurement gap and / or a PRACH timing (in the time domain) as an available / valid CG / PUSCH timing. For example, if a CG / PUSCH timing does not overlap with a PRACH timing, the UE may consider the CG / PUSCH timing valid.

[0228] Alternatively, during the measurement gap, the UE may or may not perform measurements. The UE can determine the available CG / PUSCH timing corresponding to the selected beam / SSB, which is the measurement result before the measurement gap. After the measurement gap, the UE can determine the available CG timing corresponding to the newly selected beam / SSB, which is the measurement result during the measurement gap used for SDT.

[0229] In some embodiments, the association period for mapping N SS / PBCH block indices to PUSCH timings, starting from frame 0 and / or frame x, can be the minimum value in a group determined by the PUSCH configuration period, such that the SS / PBCH block indices can be mapped to a PUSCH timing at least once within the association period. For example, the UE obtains N from the value of ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. If, within the association period, after an integer number of SS / PBCH block index to PUSCH timing mapping periods, a group of CG resources / timings is not mapped to N SS / PBCH block indices, then no SS / PBCH block indices are mapped to a group of CG resources / timings. The association pattern period may include one or more association periods and is determined such that the pattern between CG resources / timings and SS / PBCH block indices can be repeated at most once every X milliseconds. CG resources / timings not associated with SS / PBCH block indices after an integer number of association periods (if any) are not used for UL transmission.

[0230] In some embodiments, the association period starting from frame x, used to map N SS / PBCH block indices from the number of SS / PBCH block indices to a valid PUSCH timing and / or associated DM-RS resource, can be the minimum value in a group determined by the PUSCH configuration period, such that the N SS / PBCH block indices are mapped to a valid PUSCH timing and associated DM-RS resource at least once during the association period.

[0231] In some embodiments, the UE may be provided by IE sdt-SSB-perCG-PUSCH with multiple SS / PBCH block indices associated with PUSCH timing and DM-RS resources. If, after an integer number of SS / PBCH block indexes to PUSCH timing mapping periods within an association period, there exists a set of CG / PUSCH timings not mapped to N SS / PBCH block indices, then no SS / PBCH block indices are mapped to the CG / PUSCH timing group. The association pattern period includes one or more association periods and may be determined such that the pattern between CG / PUSCH timings and SS / PBCH block indices repeats at most once every X milliseconds (e.g., 640 ms). CG / PUSCH timings not associated with SS / PBCH block indices after an integer number of association periods (if any) are not used for PUSCH transmission.

[0232] HARQ ID confirmed

[0233] Based on 3GPP TS 38.321, the HARQ process ID used for UL CG transmission and / or DL ​​SPS reception can be derived in some of the ways described below, for example,

[0234] Equations without offset

[0235] Equations with offsets

[0236] The UE implementation is used to select a HARQ process ID from the HARQ process IDs available for the configured authorization configuration.

[0237] For uplink authorizations where neither harq-ProcID-Offset2 nor cg-RetransmissionTimer is configured, the HARQ process ID associated with the first symbol of the UL transmission is derived from the following equation:

[0238] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes…(1)

[0239] For uplink grants configured using harq-ProcID-Offset2, the HARQ process ID associated with the first symbol of the UL transmission is derived from the following equation:

[0240] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-ProcID-Offset2…(2)

[0241] Where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + number of slots in the frame × numberOfSymbolsPerSlot + number of symbols in the slot), numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots in each frame and the number of consecutive symbols in each slot, respectively, which conforms to the requirements of 3GPP TS 38.211.

[0242] For uplink grants configured with cg-RetransmissionTimer, the UE instance selects a HARQ process ID from the HARQ process IDs available for configuring the grant configuration. The UE should prioritize retransmissions before the initial transmission. The UE should switch the NDI in CG-UCI for new transmissions, but not during retransmissions.

[0243] Note that the current CURRENT_symbol refers to the symbol index of the first transmission timing of the repeated bundle.

[0244] Note that if the cg retransmission timer is not configured, the HARQ process will not be shared between different configuration licenses within the same BWP.

[0245] For CG-based SDT, there are some characteristics that differ from traditional CG mechanisms. For example, when the UE is in RRC_INACTIVE, the CG used for SDT can be used / configured (only). The CG used for SDT can be configured via RRC release (with suspendconfig) messages. The CG used for SDT can be configured with associations / mapping between beams / SSBs and CG resources / timing. The number of (UL) HARQ processes can be configured specifically for CG-based SDT. Therefore, it may be necessary to define a new method for the UE to determine the HARQ process ID for the CG used for SDT.

[0246] Configuration

[0247] In one embodiment, the UE may be configured with parameters for determining the HARQ process ID, for example...

[0248] periodicity: Configures the periodicity for authorization type 1 (used for SDT and / or RRC_INACTIVE).

[0249] nrofHARQ-Processes: Configures the number of HARQ processes authorized (for SDT and / or RRC_INACTIVE).

[0250] harq-ProcID-OffsetX:offset of HARQ process for configured grant(forSDT and / or for RRC_INACTIVE)

[0251] harq-ProcID-OffsetX: Configures the offset of the licensed HARQ process (for SDT and / or RRC_INACTIVE).

[0252] In one embodiment, the parameters used for HARQ process ID determination can be configured in dedicated RRC messages, RRC release (including suspendconfig) messages, RRC reconfiguration messages, and / or system information (e.g., SIBx, where x can be an integer). The parameters used for HARQ process ID determination can also be configured in CG configuration (e.g., for SDT).

[0253] In one embodiment, when the UE is in RRC_CONNECTED state, the UE can receive parameters for HARQ process ID determination in an RRC reconfiguration message. When the UE is in RRC_CONNECTED and / or RRC_INACTIVE state, the UE can store the configuration. Then, when the UE switches to RRC_INACTIVE state, the UE can apply the stored configuration. When the UE receives an RRC release message (with a suspended configuration), the UE can apply the stored configuration. When the UE receives an RRC release message (with a suspended configuration) and a specific indication included in the RRC release message instructing the UE to apply it, the UE can apply the stored configuration.

[0254] Single HARQ process

[0255] In some embodiments, the UE may support only one HARQ process for SDT.

[0256] In one embodiment, nrofHARQ-Processes may not be configured by NW (e.g., an IE may not have nrofHARQ-Processes).

[0257] In one embodiment, the value of nrofHARQ-Processes can be set to 1 by NW.

[0258] In one embodiment, the HARQ process ID associated with the first symbol of the SDT can be derived from the following equation:

[0259] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo 1...(3)

[0260] In one embodiment, for SDT via CG, the UE may (only) use a specific HARQ process identifier (e.g., HARQ process ID 0). The specific HARQ process identifier may be predefined in the UE's specification and / or may be configured by the NW (e.g., in the CG configuration). In one embodiment, the pre-configured HARQ process identifier may be overridden by the HARQ process identifier configured by the NW (e.g., in the CG configuration).

[0261] In one embodiment, if the UE has only configured one HARQ process for SDT, the UE may ignore the HARQ process field in the DCI received on a specific CORESET / search space. In another embodiment, if the UE has only configured one HARQ process for SDT, the HARQ process field in the DCI may not exist. In yet another embodiment, if the UE has only configured one HARQ process for SDT, the HARQ process field in the DCI may always need to indicate a specific HARQ process ID (e.g., HARQ process ID 0).

[0262] Multiple HARQ processes

[0263] In some embodiments, the UE may support multiple HARQ processes for SDT.

[0264] In one embodiment, the HARQ process ID associated with the first symbol of the SDT can be derived from the following equation:

[0265] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes…(4)

[0266] In one embodiment, the HARQ process ID associated with the first symbol of the SDT can be derived from the following equation:

[0267] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-ProcID-OffsetX…(5)

[0268] In one embodiment, the UE embodiment selects a HARQ process ID from the HARQ process IDs available for the configured authorization configuration (for SDT).

[0269] In one embodiment, the UE may indicate HARQ process ID information to the NW via specific signaling transmitted over the CG based on SDT. The specific signaling may be PHY signaling, UCI, MAC CE, and / or RRC signaling.

[0270] In one embodiment, when selecting a HARQ process ID for the CG resources of the SDT, the UE may prioritize the HARQ process ID used for retransmission over the HARQ process ID used for new / initial transmission.

[0271] In one embodiment, when selecting a HARQ process ID for the CG resources of the SDT, the UE may prioritize the HARQ process ID used for new / initial transmissions over the HARQ process ID used for retransmissions.

[0272] In one embodiment, the UE can select (for CG) a HARQ process that does not have data waiting to be retransmitted. For example, when a specific timer for the HARQ process (e.g., the CG timer and / or the window / timer for monitoring the PDCCH) is running, the UE may not select a HARQ process (for CG). For example, when a specific timer for the HARQ process (e.g., the CG timer and / or the window / timer for monitoring the PDCCH) is not running, the UE may select only a HARQ process (for CG).

[0273] In one embodiment, after transmitting UL data (e.g., small data in RRC_INACTIVE), the UE can (re)start the window / timer (e.g., configured in the CG configuration), for example, at the first PDCCH timing specified in 3GPP TS 38.213 after the end of UL data transmission.

[0274] In one embodiment, the UE can monitor the PDCCH (e.g., on a specific search space configured in the CG configuration) via a specific RNTI (e.g., C-RNTI / CS-RNTI) during window / timer runtime.

[0275] For monitoring PDCCH, in one embodiment, the UE may attempt to detect a specific DCI (e.g., DCI format 1_0) with a CRC scrambled by a specific RNTI (e.g., C-RNTI / CS-RNTI) during a window / timer period.

[0276] In one embodiment, the window / timer can be restarted at the first symbol of the earliest CORESET. The UE is configured to receive PDCCHs for a specific search space group (e.g., Type 1 PDCCH CSS group), which can be at least X (e.g., one) symbols (or a pre-configured offset) after the last symbol of the timing corresponding to the transmission of UL data. The symbol duration and / or offset can correspond to the SCS for the specific search space group. Based on the SCS for the specific search space group, the length of the window / timer can be the number of symbols / slots / subframes / ms.

[0277] Beam / SSB-based HARQ process ID determination

[0278] Note that the association / mapping between beams (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI state) and CG resources / timings can be configured. Note that details have been described in the foregoing embodiments. Before / during SDT using CG, the UE can select a beam / SSB to determine which CG resource / timing is applied to UL transmission. The UE can then transmit UL data on the specific CG resource / timing associated with the selected beam (e.g., the selected SSB).

[0279] In one embodiment, different beams / SSBs may be associated with different CG resources / timings in different resources / timings (e.g., different symbols, hour slots, time slots, subframes, system frames, ms, s, etc.). For example, a UE may be configured with two beams (e.g., two SSBs). A first beam (e.g., a first SSB) may be associated with a first CG resource / timing in a first symbol, and a second beam (e.g., a second SSB) may be associated with a second CG resource / timing in a second symbol. Based on the current HARQ process ID determination method, if the UE selects different beams / SSBs for SDT via CG, the UE can derive different HARQ process IDs for transmission. Since the UE can select only one beam for transmission, it is beneficial to align the HARQ process IDs with the CG resources / timings associated with different beams used for a single UL transmission.

[0280] Figure 6B This is a schematic diagram illustrating the association / mapping between SSB (Index) and CG resources / timings according to an exemplary embodiment of this disclosure. Reference Figure 6B The UE can be configured with beam 0, beam 1, and beam 2, wherein beam 0 is associated with CG resources / timing in time index 0, beam 1 is associated with CG resources / timing in time index 1, and beam 2 is associated with CG resources / timing in time index 2. The UE can perform one or more of the following embodiments:

[0281] In one embodiment, the UE can derive the HARQ process ID of the CG based on a specific time index (e.g., symbol index) of the CG resource / opportunity. The CG resource / opportunity is one of multiple CG resources / opportunities associated with a configured beam / SSB (beam / SSB group / list), regardless of which beam / SSB the UE selects.

[0282] In one example, the UE can derive the HARQ process ID of the CG based on the first (earliest or lowest) time index of the CG resource / opportunity. The CG resource / opportunity is one of multiple CG resources / opportunities associated with a configured beam / SSB (beam / SSB group / list), regardless of which beam / SSB the UE selects. Figure 6BFor example, the UE can derive the HARQ process ID for CG based on time index 0 associated with the first CG resource / opportunity, for example, regardless of whether the UE selects beam 0, beam 1 or beam 2.

[0283] In one example, the UE can derive the HARQ process ID for the CG based on the last (latest or highest) time index of the CG resource / opportunity, where the CG resource / opportunity is one of multiple CG resources / opportunities associated with a configured beam / SSB (beam / SSB group / list), regardless of which beam the UE selects. Figure 6B For example, the UE can derive the HARQ process ID for CG based on the time index 2 associated with the last CG resource / timing, for example, regardless of whether the UE selects beam 0, beam 1 or beam 2.

[0284] In one embodiment, CURRENT_symbol may refer to a specific time index (e.g., symbol index) of a CG resource / opportunity. A CG resource / opportunity is one of several CG resources / opportunities associated with a configured beam / SSB (beam / SSB group / list), for example, regardless of which beam / SSB the UE selects.

[0285] In one example, `CURRENT_symbol` can refer to the first (earliest or lowest) time index of a CG resource / opportunity. A CG resource / opportunity is one of several CG resources / opportunities associated with a configured beam / SSB (beam / SSB group / list), regardless of which beam / SSB the UE selects. Figure 6B For example, CURRENT_symbol can refer to time index 0 associated with the first CG resource / opportunity, for example, regardless of whether the UE selects beam 0, beam 1 or beam 2.

[0286] In one example, `CURRENT_symbol` can refer to the last (most recent, or highest) time index of a CG resource / opportunity. A CG resource / opportunity is one of several CG resources / opportunities associated with a configured beam / SSB (beam / SSB group / list), regardless of which beam / SSB the UE selects. Figure 6B For example, CURRENT_symbol can refer to the time index 2 associated with the last CG resource / timing, for example, regardless of whether the UE selects beam 0, beam 1 or beam 2.

[0287] In one embodiment, the UE can derive a HARQ process ID for CG based on a time index (e.g., a symbol index) of the CG resource / opportunity, which is associated with one of the configured beams / SSBs (beam / SSB groups / lists) with a specific index, for example, regardless of which beam / SSB the UE selects.

[0288] In one example, the UE can derive the HARQ process ID for the CG based on the time index (e.g., symbol index) of the CG resource / opportunity, which is associated with the configured beam / SSB with the lowest index, regardless of which beam the UE selects. Figure 6B For example, the UE can derive the HARQ process ID for CG based on time index 0 associated with the beam with the lowest index, regardless of whether the UE selects beam 0, beam 1, or beam 2.

[0289] In one example, the UE can derive the HARQ process ID for the CG based on the time index (e.g., symbol index) of the CG resource / opportunity, which is associated with the configured beam / SSB with the highest index, regardless of which beam the UE selects. Figure 6B For example, the UE can derive the HARQ process ID of the CG based on the time index 2 associated with the beam with the highest index, for example, regardless of whether the UE selects beam 0, beam 1 or beam 2.

[0290] In one example, a specific index can be associated with the default beam / SSB. Alternatively, the specific index of the default beam / SSB can be pre-configured by the NW. Or, the specific index of the default beam / SSB can be predefined in the specification.

[0291] In one embodiment, CURRENT_symbol may refer to a time index (e.g., symbol index) of a CG resource / occurrence, which is associated with one of the configuration beams / SSBs (beam / SSB groups / lists) with a specific index, for example, regardless of which beam / SSB the UE selects.

[0292] In one example, `CURRENT_symbol` can refer to the time index (e.g., symbol index) of the CG resource / timing associated with the configuration beam / SSB with the lowest index, regardless of which beam / SSB the UE selects. Figure 6B For example, CURRENT_symbol can refer to time index 0 associated with the beam / SSB with the lowest index, for example, regardless of whether the UE selects beam 0, beam 1 or beam 2.

[0293] In one embodiment, multiple CG resources / opportunities associated with a configured beam / SSB (beam / SBB group / list) can be configured / treated as a group / bundle for transmission. The UE can derive the HARQ process ID based on one of the CG resources / opportunities in the group / bundle (associated with the configured beam / SSB (beam / SSB group / list)). Transmission bundles via multiple CG resources / opportunities can be associated with the same beam / SSB. In one example, the UE can derive the HARQ process ID for the CG resource / opportunity based on a transmission opportunity (e.g., a first transmission opportunity) of the occurring group / bundle.

[0294] In one example, CURRENT_symbol can refer to the symbol index of one of the transmission moments (e.g., the first transmission moment) that occurs in a group / set / bundle.

[0295] In one embodiment, the number of CG resources / timing and / or beams / SSBs within a group / set / bundle can be configured by specific values ​​(e.g., provided by the NW, RRC layer, and / or PHY layer).

[0296] In one embodiment, the number of CG resources / timings and / or beams / SSBs within a group / set / bundle can be based on the number of beam / SSB indices in the resource list.

[0297] In one embodiment, to determine the HARQ process ID for CG transmissions used in SDT and / or RRC_INACTIVE, the UE may derive the HARQ process ID based on a specific time unit level (e.g., a slot or subframe) rather than the symbol level. In one example, HARQ process ID = [floor(CURRENT_slot / periodicity)]modulo nrofHARQ-Processes.

[0298] In one embodiment, the CG resource / timing can be the transmission timing for SDT.

[0299] In one embodiment, for each serving cell and / or each configured uplink grant, if configured and activated, the UE may set the HARQ process ID to the HARQ process ID associated with the PUSCH duration if / when the configured uplink grant PUSCH duration is associated with the selected beam / SSB.

[0300] In one embodiment, if the MAC entity / UE has configured (Type 1) CG (when the UE is in RRC_INACTIVE) and the CG resource / timing configured for the CG is associated with the selected beam / SSB, then the UL-SCH resource / timing (CG for SDT) can be considered available / valid.

[0301] In one embodiment, if the MAC entity / UE has configured (Type 1) CG (when the UE is in RRC_INACTIVE), but the CG resource / timing configured for the CG is not associated with the selected beam / SSB, then the UL-SCH resource / timing (CG for SDT) can be considered unavailable / valid.

[0302] Figure 7 This is a flowchart of a method for a network adapted for SDT according to an exemplary embodiment of this disclosure. (Reference) Figure 7 The network (e.g., BS) transmits the CG configuration for SDT to the UE (step S710). The network transmits the SSB group to the UE (step S730). The network transmits the mapping ratio configuration to the UE (step S750). The mapping between the SSB index and the CG resource / timing is determined based on the increasing order of the mapping ratio configuration and the CG resource / timing index. Details of steps S710 to S750 can be found in [reference]. Figures 4-6B And it will be omitted.

[0303] SDT process

[0304] Figure 8 This is a flowchart illustrating a method suitable for a UE to use SDT according to an exemplary embodiment of this disclosure. Reference Figure 8 The UE receives configuration from the NW (e.g., BS) (step S810). This configuration may indicate a first RSRP threshold and / or a second RSRP threshold. The UE may initiate an SDT procedure based on CG resources (e.g., provided by the CG configuration for SDT) in response to the RSRP of the DL path loss reference being higher than the first RSRP threshold (step S830). In response to initiating an SDT procedure based on CG resources: if the SSB has an RSRP higher than the second RSRP threshold, the UE may select an SSB from the SSB group (step S850). The UE may initiate an RA procedure in response to no SSB in the SSB group having an RSRP higher than the second RSRP threshold (step S870).

[0305] Figure 9 This is a flowchart illustrating a method suitable for a UE to use SDT according to an exemplary embodiment of this disclosure. Reference Figure 9The UE initiates the SDT procedure (step S910). During the SDT procedure, the UE selects an SSB (step S930). During the SDT procedure, the UE performs a transmission based on the selected SSB (step S950). In response to performing the transmission, the UE starts or restarts a timer (step S970). The UE monitors the PDCCH during timer operation by assuming that the PDCCH has the same DM-RS antenna port quasi-co-address attributes as the selected SSB associated with the transmission (step S990).

[0306] Specifically Figure 10 This is a flowchart illustrating a CG-based SDT according to one of the exemplary embodiments disclosed herein. Reference Figure 10 For CG-based SDT, UE 110 can initiate / execute procedures for SDT (e.g., SDT procedures). UE 110 can receive CG configuration from NW 120 (e.g., via RRC release messages and / or RRC reconfiguration messages) (step S1010).

[0307] In one embodiment, the UE may receive CG configuration (for SDT) via RRC release with a pending configuration message.

[0308] In one embodiment, when the UE is in RRC_CONNECTED, the UE can receive the CG configuration in an RRC reconfiguration message. When the UE is in RRC_CONNECTED and / or when the UE is in RRC_INACTIVE, the UE can store the CG configuration. Then, when the UE switches / enters RRC_INACTIVE, the UE can apply the stored configuration. When the UE receives an RRC release message (with a suspended configuration), the UE can apply the stored configuration. When the UE receives an RRC release message (with a suspended configuration) and a specific indication included in the RRC release message instructs the UE to apply it, the UE can apply the stored configuration.

[0309] In one embodiment, CG configuration may include beam information (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI state group / list), CG information (e.g., period, TBS, number of implicitly released CG resources, CG timer, retransmission timer, number of HARQ processes reserved for CG in SDT, LCH / DRB information (e.g., logicalChannelIdentity, DRB-identity), RSRP threshold for SSB selection, and association / mapping between SSB (index) and CG resources, TA-related parameters (e.g., TA timer), etc.) and / or association / mapping between beam and CG resources / timing.

[0310] SDT process initialization

[0311] In one embodiment, the UE can trigger / initiate an SDT procedure based on certain conditions. The SDT procedure can be a RA procedure (e.g., RA-based SDT). Alternatively, the SDT procedure can be a procedure transmitted via CG (e.g., CG-based SDT). More specifically, there may be two types of SDT procedures. One type is based on an RA procedure (e.g., 2-step or 4-step RA). The other type is based on CG (e.g., Type 1 CG). The UE can transmit UL / DL data during the SDT procedure. At any given time, only one SDT procedure may be in progress. The SDT procedure can only be triggered / initiated when the UE is in RRC_INACTIVE.

[0312] In one embodiment, the SDT process can be triggered / initiated by the NW or UE (e.g., RRC entity, MAC entity) itself.

[0313] In one embodiment, the UE can trigger / initiate an SDT procedure if / when the UE receives a DL indication from the NW. In one embodiment, the DL indication may be an RRC release (with suspendconfig) message. In one embodiment, the DL indication may include configuration for SDT. Specifically, the DL indication may include CG configuration (for SDT). In one embodiment, the DL indication may include fields / parameters for triggering / initiating the SDT procedure.

[0314] In one embodiment, when the UE enters RRC_INACTIVE, the UE can trigger / initiate the SDT procedure.

[0315] In one embodiment, the UE may trigger / initiate an SDT procedure upon / after determining that at least one CG configuration / resource is valid. Note that the criteria used to determine CG validity are described in the following disclosure.

[0316] In one embodiment, the UE can trigger / initiate an SDT procedure when / after at least one LCH / SRB / DRB configured for SDT has pending data. For example, data may only be available for transmission of SRB / DRBs with SDT enabled.

[0317] In one embodiment, when the UE transitions from RRC_CONNECTED to RRC_INACTIVE after the RRC connection release procedure, it may not suspend / release the LCH / SRB / DRB configured for SDT (or may restore the LCH / DRB configured for SDT).

[0318] In one embodiment, the LCH / SRB / DRB configured for SDT can be configured by NW via dedicated RRC signaling, such as in CG configuration.

[0319] In one embodiment, if the amount of data used for transmission (e.g., for SDT) is lower than the configured threshold for SDT, the UE can trigger / initiate the SDT procedure. Note that the data amount can be calculated as the amount of LCH / SRB / DRB configured for SDT.

[0320] In one embodiment, the UE can trigger / initiate an SDT procedure if the RSRP is greater than / higher than the RSRP threshold configured for SDT. For example, if the RSRP of the DL path loss reference is higher than the corresponding RSRP threshold, the UE triggers / initiates an SDT procedure. Alternatively, if the RSRP of the DL path loss reference is not higher than the corresponding RSRP threshold, the UE stops / cancels the SDT procedure or considers the SDT procedure unsuccessful. In one embodiment, the RSRP threshold used for comparison with the RSRP of the DL path loss reference can be configured via SDT configuration.

[0321] In one embodiment, if CG resources / timing are invalid, the UE can initiate a RA procedure for SDT.

[0322] Beam measurement

[0323] refer to Figure 10 UE 110 can perform beam measurements (e.g., measuring SSB / TRS / CSI-RS / auxiliary RS / TCI status) based on the configured beams (step S1020). Specifically, beams can be configured in the CG configuration (e.g., via SSB groups). In one embodiment, beam measurement can be L1-RSRP measurement. In one embodiment, beams can be configured in a configuration for SDT. In one embodiment, the UE can be configured with a list of RS resources (e.g., SSB groups) for beam measurements (for CG-based SDT). However, in one embodiment, after the UE receives the beam configuration or CG configuration, the UE may need to determine "when" to perform the measurement. In one embodiment, the UE can perform beam measurements based on one or more of the following conditions or a combination of the following conditions:

[0324] In one embodiment, the UE can perform beam measurement when it receives an RRC release (with suspendconfig IE) message / after receiving an RRC release (with suspendconfig IE) message and / or when the UE enters RRC_INACTIVE.

[0325] In one embodiment, the UE may perform beam measurements during / after receiving the CG configuration and / or beam configuration (as associated with the CG). For example, during / after receiving the CG configuration and / or beam configuration (as associated with the CG), Layer 1 (e.g., the UE's PHY layer) may evaluate the radio link quality (based on the configured beam / RS group, e.g., for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the UE's MAC layer).

[0326] In one embodiment, the UE may perform beam measurement when / after initiating an SDT procedure (e.g., CG-based) and / or while the SDT procedure is running.

[0327] For example, when / after an SDT procedure is initiated (e.g., based on CG) and / or while the SDT procedure is running, Layer 1 (e.g., the PHY layer of the UE) can assess the radio link quality (based on the configured beam / RS group, e.g. for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0328] In one embodiment, the UE may perform beam measurement when / after determining that at least one CG configuration / resource is valid.

[0329] For example, upon determining that at least one CG configuration / resource is valid, Layer 1 (e.g., the PHY layer of the UE) can assess the radio link quality (based on the configured beam / RS group, e.g., for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE). The criteria for determining CG validity are described in the following disclosure.

[0330] In one embodiment, the UE may perform beam measurements (only) on specific beams associated with valid CG configurations / resources.

[0331] In one embodiment, the UE may (only) measure beams associated with valid CG configurations / resources. The UE may not measure beams associated with invalid CG configurations / resources. The UE may exclude beams associated with invalid CG configurations / resources used for beam measurement.

[0332] In one embodiment, a valid CG configuration / resource is a CG that has not yet been released / suspended. An invalid CG configuration / resource is a CG that has been released / suspended.

[0333] For example, Layer 1 (e.g., the PHY layer of the UE) can assess radio link quality (based on the configured beam / RS group, e.g. for CG-based SDT) and / or provide the corresponding RSRP measurement group of the configured beam with valid CG configuration / resources to the upper layer (e.g., the MAC layer of the UE).

[0334] In one embodiment, the UE can perform beam measurements when / after at least one LCH / SRB / DRB is configured to have pending data in an SDT.

[0335] In one embodiment, when the UE transitions from RRC_CONNECTED to RRC_INACTIVE after the RRC connection release procedure, the LCH / SRB / DRB configured for SDT may not be suspended / released (or the LCH / SRB / DRB configured for SDT may be restored).

[0336] In one embodiment, the LCH / SRB / DRB configured for SDT can be configured by NW via dedicated RRC signaling, for example, in CG configuration.

[0337] For example, when running / after running on an LCH / SRB / DRB, which is configured for SDT with pending data, Layer 1 (e.g., the PHY layer of the UE) can assess radio link quality (depending on the configured beam / RS group, e.g. for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0338] In one embodiment, the UE may perform beam measurement when / after at least the process for generating MAC CE is triggered (e.g., BSR is triggered, PHR is triggered, etc.).

[0339] For example, when / after at least the process for generating MAC CE is triggered (e.g., BSR is triggered, PHR is triggered, etc.), Layer 1 (e.g., the PHY layer of the UE) can assess radio link quality (based on the configured beam / RS group, e.g., for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0340] In one embodiment, the UE may perform beam measurement prior to UL transmission of SDT via CG.

[0341] Specifically, the UE can perform beam measurement during / before the (pre)configuration period prior to UL transmission via CG for SDT. This period can take into account the PUSCH preparation process time (e.g., section 6.4 of 3GPP TS 38.214). Therefore, after determining that the measured beam quality is good (i.e., beam measurement is performed), the UE has sufficient time to generate TB / MAC PDUs for transmission on CG resources.

[0342] For example, before performing UL transmission of SDT via CG, Layer 1 (e.g., the PHY layer of the UE) can assess radio link quality (based on the configured beam / RS group, e.g. for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0343] For example, during / before the (pre)configuration period prior to the UL transmission of SDT via CG, Layer 1 (e.g., the PHY layer of the UE) can assess radio link quality (based on the configured beam / RS group, e.g. for CG-based SDT) and / or provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0344] In one embodiment, the UE can perform beam measurements periodically (e.g., based on periodic IE configured by NW).

[0345] Specifically, for example, the period value can be a fixed value pre-configured / predefined to the UE. For example, the UE can receive the period value in the CG configuration, in the information element associated with the beam configuration (e.g., in the CG configuration), in the RRC release message (including suspend configuration), and / or in the RRC reconfiguration message. For example, the periodic value can be associated with the DRX period.

[0346] In one embodiment, periodicity can be configured via IE SSB-periodicity and / or ssb-periodicityServingCell. If IE is not present, the UE can apply default values ​​(e.g., 5ms).

[0347] For example, the UE can perform beam measurements within the duration of each cycle. The duration value can be less than the cycle value.

[0348] For example, Layer 1 (e.g., the PHY layer of the UE) can assess radio link quality (based on the configured beam / RS group, e.g., for CG-based SDT) and / or periodically provide a set of corresponding RSRP measurements (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0349] For example, the UE can perform beam measurement when monitoring paging timing. For example, the UE can perform beam measurement when it is in the on-duration period within a DRX cycle. In one embodiment, the UE can perform beam measurement based on a timer.

[0350] In one embodiment, the UE may receive the timer value in the CG configuration, in an information element associated with the beam configuration (e.g., in the CG configuration), in an RRC release message (including suspendconfiguration), and / or in an RRC reconfiguration message.

[0351] In one embodiment, when / after the UE performs beam measurement and / or beam selection, the UE may (restart) the timer. While the timer is running, the UE may not perform beam measurement and / or beam selection. When / after the timer expires, the UE may perform beam measurement and / or beam selection.

[0352] For example, when / after a timer expires, Layer 1 (e.g., the PHY layer of the UE) can assess the radio link quality (depending on the configured beam / RS group, e.g. for CG-based SDT) and / or periodically provide the corresponding RSRP measurement group (for the configured beam) to the upper layer (e.g., the MAC layer of the UE).

[0353] More specifically, the UE behavior of beam measurement may imply that the UE measures the configured beams (groups / lists) and / or the UE's upper layer (e.g., the MAC layer) may request the UE's Layer 1 (e.g., the PHY layer) to provide the beam index of the corresponding L1-RSRP measurement from the configured beams (groups / lists) and greater than or equal to the configured RSRP threshold (e.g., rsrp-ThresholdSSB).

[0354] Beam selection

[0355] refer to Figure 10 During the process and / or after receiving the CG configuration and / or after performing beam measurement, UE 110 may perform beam selection (step S1030), for example, selecting an SSB (e.g., based on an RSRP threshold used to select an SSB for the CG). Specifically, UE 110 may determine whether at least one SSB has an SS-RSRP higher than the RSRP threshold (among the SSBs in the SSB list).

[0356] In one embodiment, if at least one of the beams (e.g., SSB) whose RSRP (e.g., SS-RSRP) is higher than the RSRP threshold (among the beams in the configured beam list), the UE can select one of the beams (for SDT).

[0357] In one embodiment, the UE can select any beam (e.g., SSB) whose RSRP (e.g., SS-RSRP) is higher than the RSRP threshold (among the beams in the configured beam list).

[0358] In an alternative scheme, the UE can select the beam with the highest measured RSRP (e.g., SS-RSRP).

[0359] In an alternative scheme, the UE can select the beam with the highest / lowest ID (e.g., SSB-ID).

[0360] In an alternative scheme, the UE can select a beam associated with CG resources / timing and / or with the HARQ process ID (e.g., determined based on the HARQ process ID), where the HARQ process does not have data waiting to be retransmitted (e.g., when the CG timer and / or the window / timer used for the HARQ process are running).

[0361] In one embodiment, if there is no beam (e.g., SSB) in the configured beam list whose RSRP (e.g., SS-RSRP) is higher than the RSRP threshold, the UE can initiate an RA procedure for the SDT.

[0362] In one embodiment, if there is no beam (e.g., SSB) whose RSRP (e.g., SS-RSRP) is higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate an RRC recovery request procedure.

[0363] In one embodiment, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can stop / cancel the CG-based SDT process, or consider the CG-based SDT process to be unsuccessful.

[0364] In one embodiment, the UE can select CG resources / timings corresponding to a selected beam (e.g., SSB) where the RSRP is higher than the RSRP threshold.

[0365] In one embodiment, the RSRP threshold used for comparison with the beam's RSRP is configured by the CG configuration.

[0366] More specifically, when the UE determines whether there is an SSB with SS-RSRP higher than rsrp-ThresholdSSB or a CSI-RS with CSI-RSRP higher than rsrp-ThresholdCSI-RS, the UE can use the latest unfiltered RSRP (e.g., L1-RSRP) measurement (which can be provided by Layer 1).

[0367] Alternatively, the UE behavior of beam selection may mean that the upper layer of the UE (e.g., the MAC layer) may request the UE's layer 1 (e.g., the PHY layer) to provide beam indices from a configured beam (group / list) and corresponding L1-RSRP measurements, which are greater than or equal to a configured RSRP threshold (e.g., rsrp-ThresholdSSB) and / or the UE may choose one of the beams provided from layer 1 (e.g., the PHY layer).

[0368] More specifically, the upper layer of the UE (e.g., the MAC layer) may, in response to selecting an SSB with an SS-RSRP higher than the RSRP threshold, indicate the SSB index of the selected SSB to the UE's layer 1 (e.g., the PHY layer).

[0369] SDT

[0370] refer to Figure 10 UE 110 can perform SDT via CG based on the selected SSB (step S1040). For example, UE 110 can transmit UL data via CG resources / timing associated with the selected SSB (e.g., on PUSCH).

[0371] In one embodiment, the transmission (e.g., SDT) is carried over the Physical Uplink Control Channel (PUSCH). For example, UE 110 may transmit UL data via the PUSCH.

[0372] In one embodiment, the UE can select a CG resource / opportunity corresponding to a selected SSB for transmission and perform transmission on the selected CG resource / opportunity.

[0373] In one embodiment, if a CG resource / opportunity exists associated with the selected beam, the UE can determine the next available CG resource / opportunity corresponding to the selected beam. The UE can then perform SDT on the determined CG resource / opportunity.

[0374] In one embodiment, if there are no CG resources / opportunities associated with the selected beam, the UE can determine the next available CG resource / opportunity corresponding to the SSB quasi-co-located with the selected beam (e.g., from the RS list / SSB group configured in the CG configuration). The UE can then perform SDT on the determined CG resource / opportunity.

[0375] In one embodiment, the MAC entity / UE can randomly select CG resources / opportunities that occur simultaneously on different subcarriers, corresponding to the selected beam.

[0376] In one embodiment, the MAC entity / UE may consider the possibility of measurement gaps and / or PRACH timings when determining the next available CG resource / opportunity corresponding to the selected beam.

[0377] PDCCH monitoring

[0378] refer to Figure 10 In one embodiment, after transmitting UL data (e.g., small data in RRC_INACTIVE) and / or receiving DL data, UE 110 may (re)start a window / timer (e.g., configured in the CG configuration), for example, at the first PDCCH timing specified in 3GPP TS 38.213 upon the end of UL data transmission. More specifically, UE 110 may monitor the PDCCH (e.g., on a specific search space configured in the CG configuration) via a specific RNTI (e.g., C-RNTI / CS-RNTI) during window / timer operation.

[0379] In one embodiment, for monitoring PDCCH, the UE may attempt to detect a specific DCI (e.g., DCI format 1_0) with a CRC scrambled by a specific RNTI (e.g., C-RNTI / CS-RNTI) during a window / timer period.

[0380] In one embodiment, the window / timer can be started or restarted at the first symbol of the earliest CORESET UE to receive / monitor the PDCCH for a specific search space group (e.g., Type 1-PDCCH CSS group and / or Type 1A-PDCCH CSS group), the symbol of which can be at least X (e.g., one) symbols (or a pre-configured offset) following the last symbol corresponding to the transmission time of UL data. The symbol duration and / or offset can correspond to the SCS of the specific search space group. Based on the SCS of the specific search space group, the length of the window / timer can be the number of symbols / slots / subframes / ms.

[0381] In one embodiment, the specific search space for SDT settings can be configured by IE sdt-CG-SearchSpace.

[0382] In one embodiment, the UE may be equipped with a USS set by sdt-CG-SearchSpace or a CSS set by sdt-SearchSpace to monitor the PDCCH to detect a DCI format with a CRC scrambled by C-RNTI or CS-RNTI for scheduling the respective PUSCH transmission or PDSCH reception.

[0383] In one embodiment, if the UE is not provided with an SDT search space for the Type 1A PDCCH CSS group, the UE can use a CRC scrambled by C-RNTI / CS-RNTI in the Type 1 PDCCH CSS group to monitor the PDCCH candidates of DCI format 1_0.

[0384] In one embodiment, for monitoring the PDCCH, the UE may assume that the UE’s beam (SSB / TRS / CSI-RS / auxiliary RS / TCI state) used for CG association has the same DM-RS antenna port quasi-co-address attributes (as described in 3GPP TS 38.214) used by the UE for CG association (e.g., association / mapping between beam and CG resources / timing), for example, regardless of whether the TCI state of CORESET is provided to the UE, where the UE receives a PDCCH with a specific DCI format.

[0385] In one embodiment, for monitoring of PDCCH and / or PDCCH reception, the UE may assume that the PDCCH has the same demodulation reference signal (DM-RS) antenna port quasi-co-address characteristics as the selected SSB associated with the transmission.

[0386] In one embodiment, the UE may assume that the DM-RS antenna port associated with PDCCH reception, the DM-RS antenna port associated with PDSCH reception, and the SS / PBCH block associated with PUSCH transmission are quasi-co-located with respect to the average gain and the quasi-co-location "Type A" or "Type D" attribute.

[0387] Optionally, for PDCCH monitoring, the UE may assume the same DM-RS antenna port quasi-co-address characteristics (for CG resource / timing transmission) as the beam selected by the UE (SSB / TRS / CSI-RS / auxiliary RS / TCI state).

[0388] Optionally, for monitoring PDCCH, the UE may assume the same DM-RS antenna port quasi-co-address attributes as the UE used to monitor paging (e.g., DCI scrambled by P-RNTI) beam (SSB / TRS / CSI-RS / auxiliary RS / TCI state). For example, regardless of whether the TCI state of CORESET is provided to the UE, the UE receives PDCCH with a specific DCI format in CORESET.

[0389] refer to Figure 10 If UE 110 receives a DL indication / response on the PDCCH (when the window / timer is running) (step S1050), UE 110 may apply one or more of the following:

[0390] In one embodiment, if the UE receives a DL indication / response on the PDCH (while the window / timer is running), the UE may consider the procedure (for SDT) to have been successfully completed and / or unsuccessfully completed.

[0391] In one embodiment, if the UE receives a DL indication / response on the PDCCH (when the window / timer is running), the UE can continue to perform subsequent data transmissions (e.g., keep monitoring the PDCCH for C-RNTI / CS-RNTI) (step S1060).

[0392] In one embodiment, for monitoring of the PDCCH (for receiving DL indication / response and / or after receiving DL indication / response), the UE may assume the same DM-RS antenna port quasi-co-address characteristics as the beam (SSB / TRS / CSI-RS / auxiliary RS / TCI state) indicated by the DL indication / response (as described in 3GPP TS 38.214).

[0393] Alternatively, for monitoring the PDCCH (for receiving DL indications / responses and / or after receiving DL indications / responses), the UE may assume the same DM-RS antenna port quasi-co-address attributes (as described in 3GPP TS 38.214) as the beam (SSB / TRS / CSI-RS / auxiliary RS / TCI state) used by the UE for CG association (e.g., association between SSB / beam and CG resource / timing), for example, if the DL indication / response does not indicate any beam information (e.g., TCI state).

[0394] Alternatively, it can be used to monitor the PDCCH (for receiving DL indications / responses and / or after receiving DL indications / responses). For example, if the DL indication / response does not indicate any beam information (e.g., TCI status), the UE may assume the same DM-RS antenna port quasi-co-address attributes (as described in 3GPP TS38.214) as the beam selected by the UE (SSB / TRS / CSI-RS / auxiliary RS / TCI status).

[0395] In one embodiment, if the UE receives a DL indication / response on the PDCCH (when the window / timer is running), the UE can use / activate / (re)initiate the CG configuration / resource / timing associated with the selected beam (for subsequent data transmission).

[0396] In one embodiment, if the UE receives a DL indication / response on the PDCCH (when the window / timer is running), the UE can start or stop beam measurement.

[0397] In one embodiment, if the UE receives a DL indication / response on the PDCCH (when the window / timer is running), the UE may not select a beam for the next CG resource / timing.

[0398] In one embodiment, if the UE receives a DL indication / response on the PDCCH (when the window / timer is running), the UE can release / suspend / discard / clear other CG resources / opportunities unrelated to the selected beam.

[0399] More specifically, the DL indication / response can be ACK and / or NACK.

[0400] In one embodiment, if the UE does not receive a DL indication / response on the PDCCH (when the window / timer is running), and / or if the DL indication / response indicates NACK, and / or if the window / timer expires, and / or if there are no CG resources / opportunities associated with the selected beam, the UE may apply one or more of the following actions:

[0401] In one embodiment, the UE can perform CG resource / timing selection and / or beam measurement / beam selection again (during the process). Specifically, the UE can select the same beam or another beam that was not selected (during the process).

[0402] Specifically, the UE can determine the next available CG resource / opportunity from the CG resources / opportunities corresponding to the (newly) selected beam.

[0403] In one embodiment, the UE may perform UL transmission (for SDT) via (another) selected CG resource / timing and / or beam configuration / resource / timing.

[0404] Specifically, the UE can perform UL transmission on the next available CG resource / opportunity corresponding to the (newly) selected beam.

[0405] In one embodiment, the UE can increment a counter by 1. Specifically, the counter can be used to calculate the number of UL transmissions / beam selections via CG (the process for CG-based SDT). Alternatively, the counter can be used for power boosting. Specifically, the counter can be used for UL skipping.

[0406] In one embodiment, when the CG-based SDT counter reaches its maximum value, the UE may (only) perform one or more of the following actions:

[0407] In an alternative approach, when the counter for the CG-based SDT reaches its maximum value, the UE can stop / cancel the CG-based SDT process and / or consider the CG-based SDT process to be unsuccessful.

[0408] In an alternative, in one possible scenario, the UE can initiate a RA procedure (for SDT) when the counter used for CG-based SDT reaches its maximum value. For example, the UE can transmit a specific preamble at a specific PRACH timing. Specific preambles and / or specific PRACH timings can be configured for SDT.

[0409] In one embodiment, for a CORESET (e.g., except for a CORESET with index 0), if the UE is not provided with a TCI state configuration (e.g., by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for the CORESET), or has been provided with an initial configuration of more than one TCI state for the CORESET (e.g., by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList), but has not received a MAC CE activation command for one of the TCI states as described in 3GPP TS 38.321, the UE may assume that the DM-RS antenna port associated with the PDCCH receives quasi-co-addressed beams (e.g., SS / PBCH blocks) identified / selected / determined by the UE during the (CG / RA) process of the SDT.

[0410] Reduced CG resource consumption

[0411] For CG-based SDT, the UE can be configured with a list of SSB resources (e.g., via SSB groups), CG configuration, and / or association / mapping between SSBs and CG configured resources / opportunities. In multi-beam systems, it can be seen that multiple SSBs can be configured to the UE, for example, for beam measurement and / or beam selection. For example, suppose one SSB is associated with one CG resource / opportunity, and the UE is configured with four SSBs. Four CG resources / opportunities should be configured for the mapping of the four SSBs. However, for data transmission, the UE can select only one SSB (e.g., with better RSRP). In other words, the UE can use only one of the four CG resources / opportunities to perform UL data transmission in a single transmission, without using the other CG resources / opportunities. Since CG resources used for SDT can be dedicated resources, i.e., CG resources can only be used by the UE configured with that CG resource, it is inefficient to maintain / retain / store so many CG resources for a long time if they are not used. This disclosure provides some methods to improve the efficiency of CG resource utilization.

[0412] In some embodiments, the UE can release / suspend / discard / clear some or all of the configured CG resources / UL licenses.

[0413] In one embodiment, the UE may be configured with multiple SSB resources (e.g., via SSB groups, CG configurations (including multiple CG resources / timings), and / or associations / mappings between SSBs and CG resources / timings). The UE may perform SSB measurements based on the configured SSB resources (e.g., when the UE is in RRC_INACTIVE). The UE may select an SSB (e.g., if SS-RSRP is above a threshold), for example, before determining (available) CG resources / timings for UL data transmission. The UE may select a first SSB and may transmit UL data via a first CG resource / timing associated with the first SSB. After the UE selects an SSB and / or the corresponding CG resource / timing, the UE may release / suspend / discard / clear other CG resources / timings. In one embodiment, another CG resource / timing may not be the first CG resource / timing. In one embodiment, another CG resource / timing may not be associated with the first SSB. In one embodiment, the UE may not release / suspend / discard / clear the first CG resource / timing. In one embodiment, the UE may store / maintain / retain the first CG resource / timing. In one embodiment, the UE may or may not perform measurements of the SSB / RS associated with the CG, where the CG has been released / suspended / discarded / cleared. In one embodiment, the UE may or may not select an SSB unrelated to any CG. In one embodiment, the UE may or may only select an SSB configured to be associated with at least one CG resource / occurrence (and the CG resource has not yet been released / suspended / discarded / cleared).

[0414] In one embodiment, the UE can (at a specific time interval) release / suspend / discard / clear other CG resources / opportunities.

[0415] In one embodiment, when / after the UE selects an SSB (for CG resources / opportunities), the UE can release / suspend / discard / clear other CG resources / opportunities.

[0416] In one embodiment, if the RSRP of the selected SSB is higher than a threshold, the UE may release / suspend / discard / clear other CG resources / opportunities only.

[0417] In one embodiment, if the RSRP of the selected SSB is not higher than a threshold, the UE may not release / suspend / discard / clear other CG resources / opportunities.

[0418] In one embodiment, the UE may release / suspend / discard / clear other CG resources / opportunities when / after receiving an indication from the NW (for UL transmission via the first CG resource / opportunity).

[0419] In one embodiment, the indication may be a feedback (e.g., ACK) for UL transmission via a first CG resource / timing. Specifically, the first CG resource / timing is associated with a selected SSB.

[0420] In one embodiment, the indication may be a DL response transmitted via a first CG resource / timing. Specifically, the first CG resource / timing is associated with a selected SSB.

[0421] In one embodiment, the indication may be DL signaling. In one example, an RRCResume message (with suspendConfig IE) responds to the transmission of a UL RRC message on the first CG resource / timing. Specifically, the UL RRC message transmitted on the first CG resource may be an RRCResumeRequest message. In one example, DL signaling may indicate that the CG (associated with the beam) is invalid (or no longer supported).

[0422] In one embodiment, the indication can be provided via SI, RRC release (with suspendConfig) message, RRC reconfiguration, and / or DCI.

[0423] In one embodiment, the UE can release / suspend / discard / clear other CG resources / opportunities during / after a specific time period.

[0424] In one embodiment, the UE may be configured with a value for that period.

[0425] In one embodiment, when transmitting UL data via CG after selecting SSB, the UE can (re)start a window / timer. While the window / timer is running, the UE can monitor the PDCCH. If the window / timer expires, the UE can release / suspend / discard / clear other CG resources / opportunities. If the window / timer expires and the UE does not receive a DL response from NW, the UE can release / suspend / discard / clear other CG resources / opportunities. Figure 10 As shown in step S1050, if the UE receives a DL response from the NW before the window / time expires, the UE can perform subsequent data transmission (step S1060).

[0426] In one embodiment, when / after successfully transmitting a report to the NW, the UE can release / suspend / discard / clear other CG resources / opportunities.

[0427] In one embodiment, when / after receiving feedback / response from NW, UE may release / suspend / discard / clear other CG resources / opportunities for transmitting reports.

[0428] In one embodiment, the report may be a beam measurement report.

[0429] In one embodiment, the report may indicate (selected) (one or more) SSB (indexes).

[0430] In one embodiment, the report may include a field indicating the presence of an SSB index field. For example, if at least one SSB in the configured list of SSB resources (e.g., including CG-SSB-resource) has an SS-RSRP higher than a threshold, the field may be set to a first value (e.g., 1); otherwise, it may be set to a second value (e.g., 0).

[0431] In one embodiment, the report may include a field that is set to index the SSB that has SS-RSRP higher than rsrp-ThresholdBFR (among SSBs in the configured list of SSB resources, such as including CG-SSB-resource).

[0432] In one embodiment, the report may indicate SSB guidance and its measurement results (e.g., the value of RSRP).

[0433] In one embodiment, reports can be transmitted via RRC signaling / MAC CE / PHY signaling.

[0434] In one embodiment, the report may be transmitted via a first CG resource / time.

[0435] In one embodiment, the report can be used to notify the NW which SSB is qualified, and then the NW can transmit a DL signal to the UE based on that SSB.

[0436] In one embodiment, the UE may trigger / generate / transmit a report to the NW.

[0437] In one embodiment, the UE can trigger / generate / transmit a report to the NW via the CG on each UL transmission.

[0438] In one embodiment, the UE can trigger / generate / transmit a report to the NW when / after selecting the SSB (for CG resources / timing).

[0439] In one embodiment, when / after the selected SSB changes (i.e., a change in the selected SSB), the UE may trigger / generate / transmit a report to the NW. For example, the UE may first select a first SSB and perform a UL transmission via a first CG resource / opportunity. Afterward, the UE may select a second SSB and perform a UL transmission via a second CG resource / opportunity. When / after the UE selects the second SSB, the UE may need to trigger a report. The UE may need to transmit the report to the NW via the second CG resource / opportunity. If the second SSB is the same as the first SSB, the UE may not need to trigger / generate / transmit a report to the NW.

[0440] In one embodiment, when / after the RSRP of the selected SSB falls below a threshold, the UE can trigger / generate / transmit a report to the NW.

[0441] In one embodiment, for multiple UL transmissions via CG, the UE can trigger / generate / transmit a report to NW once. For example, the UE can use a counter to control the triggering / generation / transmission of the report.

[0442] In one example, the UE can count the number of times it skips UL transmissions (via CG). When the counter reaches a pre-configured maximum value, the UE can trigger / generate / transmit a report to the NW.

[0443] In one example, the UE can count the number of times a UL transmission is performed (via the CG). When the counter value reaches a pre-configured maximum value, the UE can trigger / generate / transmit a report to the NW.

[0444] In one example, the UE can count the number of times it fails to transmit UL data (via CG), for example, when the UE does not receive feedback / response from the NW, or when the UE receives a NACK from the NW. When the counter value reaches a pre-configured maximum value, the UE can trigger / generate / transmit a report to the NW.

[0445] In one example, the UE can count the number of times it fails to find / select a qualified beam associated with a specific CG resource.

[0446] In one embodiment, the UE can periodically trigger / generate / transmit reports to the NW. For example, the UE can be configured with a timer to control the triggering / generation / transmission of reports. The timer can only be used when the UE is in RRC_INACTIVE mode. The timer can be configured in the CG configuration.

[0447] In one embodiment, the UE can (re)start the timer when / after the UE triggers / generates / transmits a report to the NW.

[0448] In one embodiment, the UE may (re)start the timer when at least one of the following conditions is met.

[0449] The UE (successfully) performed the transmission on the CG resource (corresponding to the CG configuration).

[0450] The UE receives an indication in response to a transmission on CG resources (corresponding to the CG configuration).

[0451] The indication could be ACK / NACK.

[0452] The indication can be a DL response (e.g., an RRC message, such as an RRC Release message).

[0453] The UE can trigger / generate / transmit a report to the NW when the timer expires.

[0454] In one embodiment, the UE can (re)start the disable timer when / after triggering / generating / transmitting a report to the NW. For example, the UE cannot trigger / transmit / generate / another report while the disable timer is running.

[0455] In one embodiment, the UE may trigger / generate / transmit a report (to trigger the report) when / after receiving an indication from the NW.

[0456] In some embodiments, the UE may release / suspend / discard / clear a specific CG resource / occasion associated with a specific SSB based on certain criteria. The specific CG resource / occasion may be one of the CG resources / occasiones configured in the CG configuration. Releasing / suspending / discarding / clearing a specific CG resource / occasion may mean that the UE will maintain / retain / store other CG resources / occasiones (not the specific CG resource / occasion).

[0457] In one embodiment, when / after a specific SSB is unqualified, the UE can release / suspend / discard / clear a specific CG resource / opportunity. Specifically, when a specific SSB is unqualified (e.g., the RSRP of the specific SSB is below a threshold), the lower layer of the UE (e.g., the PHY layer) can indicate this to the upper layer of the UE (e.g., the MAC layer).

[0458] In one example, the UE can measure a specific SSB and derive the RSRP of that specific SSB. If the RSRP of a specific SSB is below a threshold (and / or an indication has been received from the lower layer), the UE can release / suspend / discard / clear the specific CG resource / opportunity.

[0459] In one example, the UE can measure a specific SSB and derive its RSRP. If the RSRP of the specific SSB is below a threshold for a period of time (and / or an indication has been received from the lower layer), the UE can release / suspend / discard / clear the specific CG resource / opportunity. The time period can be controlled by a timer. When the RSRP of the specific SSB is not lower than (or higher than) the threshold (and / or no indication has been received from the lower layer), the timer can be (re)started. When the timer expires, the UE can release / suspend / discard / clear the specific CG resource / opportunity. The UE can receive the timer value along with the CG configuration. Alternatively, the timer value can be pre-configured or predefined for the UE.

[0460] In one example, the UE can measure a specific SSB and derive its RSRP. If the RSRP of the specific SSB is below a threshold (and / or an indication has been received from the lower layer), the UE can increment the value of a specific counter by 1. This specific counter can be associated with a specific SSB and / or a specific CG resource / opportunity. If the value of the specific counter reaches its maximum value, the UE can release / suspend / discard / clear the specific CG resource / opportunity.

[0461] In one embodiment, a specific counter and / or the maximum value of a specific counter can be configured in the CG configuration.

[0462] In one embodiment, a specific counter can be reset when a specific timer expires. Specific timers and / or their values ​​can be configured in the CG configuration. A specific timer can be (re)started when the RSRP of a specific SSB falls below a threshold (and / or an indication has been received from the lower layer).

[0463] In one embodiment, a specific counter can be reset when a CG resource / configuration is deemed invalid.

[0464] In one embodiment, when the UE fails to transmit UL data multiple times via a specific CG resource / opportunity, the UE may release / suspend / discard / clear the specific CG resource / opportunity.

[0465] In one example, a (transmission) counter can be used to count the number of times the UE (failed) to transmit UL data via a specific CG resource / opportunity. The UE can determine that a UL data transmission is a (failed) transmission based on whether the UE receives feedback (e.g., ACK / NACK) from the HARQ process used to transmit UL data from the NW. If the UE does not receive feedback from the NW (e.g., ACK), the UE can increment the (transmission) counter by 1. If the UE receives feedback from the NW (e.g., NACK), the UE can increment the (transmission) counter by 1. When the counter reaches its maximum value, the UE can release / suspend / discard / clear the specific CG resource / opportunity.

[0466] In one embodiment, a (transfer) counter and / or a maximum value of the counter can be configured in the CG configuration.

[0467] In one embodiment, the (transmission) counter may be associated with a specific CG resource / timing and / or a specific SSB.

[0468] In one embodiment, the (transmission) counter can be reset when the UE successfully performs a UL transmission. For example, the UE receives feedback / response (e.g., ACK) from the NW.

[0469] In one embodiment, the (transfer) counter can be reset when the CG resource / configuration is deemed invalid.

[0470] In one embodiment, when / after the UE has skipped (or not generated MAC PDU / TB) UL transmissions via a specific CG resource / opportunity (for the HARQ process) multiple times, the UE can release / suspend / discard / clear the specific CG resource / opportunity.

[0471] In one example, the (UL skip) counter can be used to count the number of times the UE skips (or does not generate a MAC PDU / TB) UL transmission via a specific CG resource / timing (for the HARQ process). The UE can determine whether to skip this UL data transmission (or not generate a MAC PDU / TB) (for the HARQ process) based on one or more of the following rules:

[0472] When the beam associated with the CG resource is not qualified.

[0473] When no beam is qualified. For example, the UE determines that none of the (configured) beams have an RSRP higher than a threshold.

[0474] When the UE is configured with a parameter that sets its value to true for UL skipping, the UE can receive the UL skipping parameter along with the CG configuration.

[0475] When the authorization indicated to the HARQ entity is addressed to C-RNTI or when the authorization indicated to the HARQ entity is a configured uplink authorization.

[0476] When the PUSCH transmission request is not a non-periodic CSI as specified in 3GPP TS 38.212.

[0477] When the MAC PDU / TB contains zero MAC SDU.

[0478] When the MAC PDU / TB only includes periodic BSRs and no LCGs are available, or when the MAC PDU only includes filler BSRs.

[0479] In one embodiment, if the UE skips UL transmission (or does not generate MAC PDU / TB) via a specific CG resource / opportunity (for the HARQ process), the UE can increment the (UL skip) counter by 1. When the (UL skip) counter reaches its maximum value, the UE can release / suspend / discard / clear the specific CG resource / opportunity.

[0480] In one embodiment, the (UL skip) counter and / or the maximum value of the counter can be configured in the CG configuration.

[0481] In one embodiment, the (UL skip) counter may be associated with a specific CG resource / timing and / or a specific SSB.

[0482] In one embodiment, when a CG resource / configuration is deemed invalid, the counter can be reset (UL skipped).

[0483] In one embodiment, if the UE does not select a specific SSB for a period of time (or multiple times), the UE can release / suspend / discard / clear the specific CG resource / opportunity.

[0484] In one example, when the UE selects a specific SSB (e.g., for a specific CG transmission), the UE can (re)start a timer (for the specific SSB and / or the specific CG). When the timer expires, the UE can release / suspend / discard / clear the specific CG resource / opportunity. The UE can configure the timer value along with the CG configuration. Alternatively, the timer value can be pre-configured or predefined for the UE.

[0485] In one embodiment, the UE may notify the NW that it has released / suspended / discarded / cleared a specific CG resource / time.

[0486] In one example, if the UE releases / suspends / discards / clears a specific CG resource / occasion, the UE can trigger a specific report and / or indicate a specific instruction to the NW.

[0487] In one embodiment, a particular report and / or particular indication may include information from the SSB (e.g., the SSB index) and / or the CG (e.g., the CG index).

[0488] In one embodiment, specific reports and / or specific instructions may be transmitted via UL authorization provided by dynamic authorization, CG, Msg3 and / or MsgA.

[0489] NUL and SUL

[0490] In one embodiment, a supplementary uplink (SUL) is provided. The UE can be configured with an additional supplementary uplink (SUL) by combining a UL / DL carrier pair (FDD band) or a two-way carrier (TDD band). The difference between a SUL and an aggregated uplink is that the UE can be scheduled to transmit on the supplementary uplink or on the uplink of the supplemented carrier, but not simultaneously on both.

[0491] In one embodiment, two UL carriers (NUL and SUL) can be configured for the serving cell. These two carriers can have different characteristics (e.g., different frequency bands FR1 / FR2). Since the payload size of the CG-based SDT PUSCH resource can be larger, it is also beneficial to support the configuration of CG-SDT resources on the SUL carrier. For example, CG resources for SDT can be configured separately for NUL and SUL; that is, RRC release / RRC reconfiguration messages can provide CG-SDT resources for both NUL and SUL.

[0492] In some embodiments, the UE can select one of a NUL and a SUL carrier to perform CG-based SDT, for example, when a CG-based SDT procedure is initiated. The UE can select one of the NUL and SUL carriers based on an RSRP threshold. For example, if the RSRP of the DL loss reference is less than the threshold (for SUL), the UE can select the SUL carrier; otherwise, the UE can select the NUL carrier. If the UE selects the NUL carrier, the UE can use the CG configuration / resources configured for the NUL carrier to perform SDT. If the UE selects the SUL carrier, the UE can use the CG configuration / resources configured for the SUL carrier to perform SDT.

[0493] In some embodiments, the UE (from the NW) may be instructed to switch to one of the NUL and SUL carriers to perform CG-based SDT, for example, when the CG-based SDT procedure is initiated. The UE may select one of the NUL and SUL carriers based on an indication from the NW. The indication may be transmitted via SI, RRC release (with suspendconfi) message, RRC reconfiguration message, and / or DCI. The indication may be feedback from the NW (e.g., ACK / NACK).

[0494] In some embodiments, a first CG configuration / resource can be configured for the NUL carrier, and a second CG configuration / resource can be configured for the SUL carrier. The UE can release / suspend / discard / clear the first CG configuration / resource, the second CG configuration / resource, and / or both based on certain criteria:

[0495] In one embodiment, if the UE selects a SUL carrier (for performing CG-based SDT), the UE can release / suspend / discard / clear the first CG configuration / resource. More specifically, if the UE selects a SUL carrier (for performing CG-based SDT), the UE can choose not to release / suspend / discard / clear the second CG configuration / resource.

[0496] In one embodiment, if the UE selects an NUL carrier (for performing CG-based SDT), the UE can release / suspend / discard / clear the second CG configuration / resources. More specifically, if the UE selects an NUL carrier (for performing CG-based SDT), the UE can choose not to release / suspend / discard / clear the first CG configuration / resources.

[0497] More specifically, if the UE selects a NUL carrier (for performing CG-based SDT), the UE can set PCMAX to the P of the NUL carrier. CMAX,f,c .

[0498] More specifically, if the UE selects a SUL carrier (for performing CG-based SDT), the UE can set PCMAX to the P of the SUL carrier. CMAX,f,c .

[0499] SDT Beam Failure Detection

[0500] Note that the UE may be configured with multiple beams, for example via a group or list (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI state), so that the UE can determine / select the beam for SDT (e.g., during the SDT procedure). The UE may select the beam based on beam measurements (e.g., L1-RSRP measurements). The selected beam may be associated with a specific CG resource / occurrence. For example, when the UE is in RRC_INACTIVE, the UE may transmit UL data (e.g., small data) via a specific CG resource / occurrence (associated with the selected beam).

[0501] In one embodiment, the UE may be provided with a group / list of (periodic) beams (e.g., SSB / TRS / CSI-RS / auxiliary RS / TCI status). In one embodiment, the group / list of (periodic) beams may be used for failure detection (e.g., for a UE in RRC_INACTIVE). In one embodiment, the beam may be configured in the CG configuration (for SDT). In one embodiment, the beam may be indicated for the association between CG resources / timing. In one embodiment, the UE may determine the group / list of beams to include a periodic RS resource configuration index whose value is the same as the RS index in the RS group indicated by the CG configuration and / or RRC release message, and / or an indication of the TCI status of each CORESET used by the UE to monitor the PDCCH, for example, if the UE has not provided a group / list of (periodic) beams.

[0502] In one embodiment, the UE can evaluate radio quality based on a configured beamgroup / list. Specifically, Layer 1 (e.g., the UE's PHY layer) can evaluate radio link quality (based on the configured beamgroup, e.g., for CG-based SDT). Specifically, the UE can be configured with a (RSRP) threshold for determining whether a radio link is qualified.

[0503] In one embodiment, Layer 1 (e.g., the PHY layer of the UE) may provide a corresponding RSRP measurement set (for configured beams) to the upper layer (e.g., the MAC layer of the UE) and / or provide an indication to the upper layer (e.g., the MAC layer of the UE), for example, when the radio link quality is worse than a configured (RSRP) threshold. Specifically, when the radio link quality is lower than a configured threshold with periodicity, Layer 1 (e.g., the PHY layer of the UE) may provide an indication to the upper layer (e.g., the MAC layer of the UE).

[0504] In one embodiment, all configured beams (for SDT) are determined to be unqualified, which may be referred to in this disclosure as SDT beam failure. In this case, if the UE selects one of the unqualified beams to perform UL transmission via CG, the UE may be unable to receive DL responses from NW because of the unqualified radio quality. Therefore, the UE may need to perform some procedures to detect whether SDT beam failure has occurred and / or perform some actions when SDT beam failure occurs (or no beam is qualified).

[0505] The UE behavior was unacceptable on all beams.

[0506] In one embodiment, if the UE cannot select any beam via CG to perform SDT, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE may perform one or more of the following embodiments:

[0507] In one embodiment, if the UE cannot select any beam to perform SDT via the CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can select any beam. In one embodiment, the UE can select the last selected beam. In one embodiment, the UE can select the beam used to monitor the PDCCH (last time). In one embodiment, the UE can select the beam indicated by the NW (e.g., based on TCI status). In one embodiment, the UE can select the beam with the highest radio quality (e.g., SS-RSRP, SS-RSRQ) among all beams. In one embodiment, the UE can select the beam with the highest / lowest ID (e.g., SSB-ID).

[0508] In one embodiment, if the UE cannot select any beam to perform SDT via the CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can select a default beam. In one embodiment, the default beam may be the lowest / highest index of the configured beams. In one embodiment, the default beam may be a pre-configured beam with a specific index. In one embodiment, the default beam may be the beam with the best quality (e.g., the highest RSRP measurement).

[0509] In one embodiment, if the UE cannot select any beam to perform SDT via CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (e.g., SS-RSRP) (among the beams in the configured beam list), the UE can skip SDT via CG. Specifically, the UE can skip SDT for a period of time (e.g., based on a timer and / or a backoff value). The UE can re-perform beam selection and / or CG resource selection after the timer expires and / or the backoff time.

[0510] In one embodiment, if the UE cannot select any beam via CG to perform SDT, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE may consider the CG configuration / resources to be invalid.

[0511] In one embodiment, if the UE cannot select any beam via CG to perform SDT, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE may consider a timer (e.g., a TAT timer or a beam active timer) as an expiration and / or stop and / or release timer.

[0512] In one embodiment, the UE may receive the timer value in the CG configuration, in an information element associated with the beam configuration (e.g., in the CG configuration), in an RRC release message (including suspendconfiguration), and / or in an RRC reconfiguration message.

[0513] In one example, the timer could be a TA timer. For instance, when the TA timer is running, the UE may consider the TA to be valid. When the TA timer is not running, the UE considers the TA to be invalid.

[0514] In one example, the timer could be a window / timer used to monitor the PDCCH. For instance, after transmitting UL data (e.g., small data in RRC_INACTIVE), the UE could (re)start the window / timer (e.g., configured in the CG configuration), such as at the first PDCCH timing specified in 3GPP TS 38.213 after the end of UL data transmission. More specifically, the UE could monitor the PDCCH (e.g., on a specific search space configured in the CG configuration) via a specific RNTI (e.g., C-RNTI / CS-RNTI) while the window / timer is running.

[0515] In one example, the timer could be a beam-dependent timer. For instance, the UE can (restart) the timer when / after performing beam measurement and / or beam selection. The UE may not perform beam measurement and / or beam selection while the timer is running. The UE can perform beam measurement and / or beam selection when / after the timer expires.

[0516] In one embodiment, if the UE cannot select any beam to perform SDT via CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), then the UE can release / clear / suspend / store (all) CG configuration / resources / timings (for SDT).

[0517] In one embodiment, if the UE cannot select any beam to perform SDT via CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate an RA procedure (for SDT).

[0518] In one embodiment, if the UE cannot select any beam to perform SDT via CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate an RRC (connection) recovery procedure.

[0519] In one example, if the UE cannot select any beam to perform SDT via the CG, for example, if there is no beam (e.g., SS-RSRP) in the beam (e.g., SSB) above the RSRP threshold (among the beams in the configured beam list), then the UE can initiate the transmission of the RRCResumeRequest message or RRCResumeRequest1 according to 5.3.13.3 of 3GPP TS 38.331.

[0520] In one embodiment, if the UE cannot select any beam to perform SDT via the CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can trigger / generate / transmit a message / report to indicate this situation to the NW (e.g., beam failure and / or no beam is qualified). More specifically, the message / report can be used to instruct the NW to release / suspend / deactivate the corresponding CG configuration / resource by the UE. Alternatively, if the UE triggers this message / report, the UE can trigger / initiate an RA procedure. More specifically, the message / report can be transmitted via Msg3 and / or MsgA. Alternatively, the message / report can be transmitted via RRC signaling, MAC-CE, and / or PHY signaling.

[0521] In one embodiment, if the UE cannot select any beam through the CG to perform SDT, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can perform SDT with ramp-shifted power (in dB). The amount of ramp-shifted power (dB) depends on pre-configured parameters (e.g., in the CG configuration and / or RRC release message). For example, the pre-configured parameter might be powerRampingStep.

[0522] In one embodiment, if the UE cannot select any beam to perform SDT via the CG, for example, if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate / execute a cell reselection procedure. For example, the UE can remain in RRC_INACTIVE and perform cell reselection. For example, the UE can enter RRC_IDLE and perform cell reselection.

[0523] SDT Beam Failure Detection

[0524] In one embodiment, the UE may perform a process for detecting beam failure of SDT (e.g., CG-based SDT) based on one or more of the following embodiments.

[0525] In one embodiment, the UE can determine whether a beam failure of the SDT has been detected by calculating a specific instance indication from the UE's lower layer (e.g., PHY layer) to the UE's upper layer (e.g., MAC entity).

[0526] In one embodiment, when the radio link quality of all corresponding resource configurations in the group / list of the configuration beams used by the UE to evaluate radio link quality is worse than a pre-configured threshold, a specific instance indication may be provided by the lower layer. In one embodiment, the group / list of (periodic) beams may be used for failure detection (e.g., for a UE in RRC_INACTIVE). In one embodiment, the beam may be configured in the CG configuration (for SDT). In one embodiment, the beam may be indicated for the association between CG resources / timings. In one embodiment, the UE may determine the group / list of beams to include a periodic RS resource configuration index whose value is the same as the RS index in the RS group indicated by the CG configuration and / or RRC release message, and / or a TCI status indication by the individual CORESETs used by the UE to monitor the PDCCH, for example, if the UE does not provide a group / list of (periodic) beams.

[0527] In one embodiment, the UE (e.g., a MAC entity) may maintain a counter to count the number of specific indications received from a lower layer. More specifically, the counter may be configured according to the CG configuration and / or according to CG resources. The counter may initially be set to 0. The value of the counter may be incremented (1) when, for example, a specific instance indication is received from a lower layer. In one embodiment, the UE may evaluate radio quality based on a configured beamgroup / beam list. In one embodiment, Layer 1 (e.g., the UE's PHY layer) may evaluate radio link quality (based on the configured beamgroup, e.g., for CG-based SDT). In one embodiment, the UE may be configured with a (RSRP) threshold for determining whether a radio link is qualified. In one embodiment, Layer 1 (e.g., the UE's PHY layer) may provide a corresponding RSRP measurement set (for the configured beams) to an upper layer (e.g., the UE's MAC layer) and / or provide indications to an upper layer (e.g., the UE's MAC layer), for example, in cases where the radio link quality is worse than the configured (RSRP) threshold. In one embodiment, when the radio link quality is below a periodic configuration threshold, Layer 1 (e.g., the PHY layer of the UE) may provide an indication to the upper layer (e.g., the MAC layer of the UE).

[0528] In one embodiment, if the counter count reaches its maximum value, the UE can determine that a beam failure of the SDT has been detected. The UE can be configured with a maximum value for the counter.

[0529] In one embodiment, the counter can be reset when one or more of the following criteria are met:

[0530] In one embodiment, the counter can be reset when a specific timer expires. A specific timer can be (re)started when, for example, a specific instance indication is received from a lower layer.

[0531] In one embodiment, the counter can be reset when the UE successfully transmits UL data (via CG).

[0532] In one embodiment, the counter can be reset when the UE receives a DL response (e.g., ACK / NACK) from the NW. The DL response can be a PDCCH addressed to a specific RNTI (e.g., C-RNTI / CS-RNTI). The DL response can be received within a window / timer period. After UL transmission via CG, the window / timer can (re)start (offset).

[0533] In one embodiment, the counter can be reset when the UE enters RRC_CONNECTED and / or RRC_IDLE.

[0534] In one embodiment, the counter can be reset when the corresponding CG configuration / resource is released / suspended / cleared and / or the corresponding CG configuration / resource is deemed invalid.

[0535] In one embodiment, the counter can be reset when the SDT (CG-based and / or RA-based) process is stopped / cancelled and / or when the SDT (CG-based and / or RA-based) process is initialized. In one embodiment, the UE can determine whether an SDT beam failure has been detected by counting the number of times the UE has failed to perform a UL transmission via CG resources.

[0536] In one embodiment, the UE may maintain a counter to count the number of times the UE failed to perform a UL transmission via CG resources. More specifically, the counter may be configured based on CG configuration and / or based on CG resources. The counter may initially be set to 0.

[0537] In one embodiment, if the UE fails to perform a UL transmission via CG resources and / or any CG resources configured by the CG, the UE may increment a counter (1).

[0538] In one embodiment, if the UE performs a UL transmission via CG resources and / or any CG resources configured by the CG, but the UE cannot receive a DL response from the CG resources from the NW, for example, during a window / timer period, the UE can increment a counter (1). The DL response can be a PDCCH addressed to a specific RNTI (e.g., C-RNTI / CS-RNTI). After the UL transmission via the CG, the window / timer can (re)start (offset).

[0539] In one embodiment, if the counter count reaches its maximum value, the UE can determine that a beam failure of the SDT has been detected. The UE can be configured with a maximum value for the counter.

[0540] In one embodiment, the counter can be reset when one or more of the following criteria are met:

[0541] In one embodiment, the counter can be reset when the UE successfully transmits UL data (via CG).

[0542] In one embodiment, the counter can be reset when a specific timer expires. A specific timer can be restarted when the UE successfully performs a UL transmission via the CG. A specific timer can be restarted when the UE receives a DL response (e.g., ACK / NACK) from the NW. The DL response can be a PDCCH addressed to a specific RNTI (e.g., C-RNTI / CS-RNTI). The DL response can be received within the window / timer's time period. After a UL transmission via the CG, the window / timer can be restarted (offset).

[0543] In one embodiment, the counter can be reset when the UE receives a DL response (e.g., ACK / NACK) from the NW. The DL response can be a PDCCH addressed to a specific RNTI (e.g., C-RNTI / CS-RNTI). The DL response can be received within a window / timer period. After UL transmission via CG, the window / timer can (re)start (offset).

[0544] In one embodiment, the counter can be reset when the UE enters RRC_CONNECTED and / or RRC_IDLE.

[0545] In one embodiment, the counter can be reset when the corresponding CG configuration / resource is released / suspended / cleared and / or the corresponding CG configuration / resource is deemed invalid.

[0546] In one embodiment, the counter can be reset when an SDT (CG-based and / or RA-based) process is stopped / cancelled and / or when an SDT (CG-based and / or RA-based) process is initialized.

[0547] In one embodiment, the UE can determine whether a beam failure of the SDT is detected by calculating the number of UL transmissions that the UE skips (and / or does not generate MAC PDU / TB) via CG resources.

[0548] In one embodiment, the UE may maintain a counter to count the number of times the UE skips UL transmissions (and / or fails to generate MAC PDU / TB) via CG resources and / or any CG resources configured by the CG. More specifically, the counter may be configured based on the CG configuration and / or the CG resources. The counter may initially be set to 0.

[0549] In one embodiment, if the UE skips UL transmission (and / or does not generate MAC PDU / TB) via CG resources and / or any CG resources configured by the CG, the UE may increment the counter (1). The UE may increment the counter (1) if one or more of the following criteria are met:

[0550] When the beam associated with the CG resource is not qualified.

[0551] When no beam (for SDT) is qualified. For example, the UE determines that the RSRP of no (configured) beam is higher than a threshold.

[0552] When the UE is configured with a parameter that sets its value to true for UL skipping, the UE can receive the UL skipping parameter along with the CG configuration.

[0553] When the authorization indicated to the HARQ entity is addressed to C-RNTI or when the authorization indicated to the HARQ entity is a configured uplink authorization.

[0554] When there is no non-periodic CSI for the PUSCH transmission request as specified in 3GPP TS 38.212.

[0555] When the MAC PDU / TB includes zero MAC SDU.

[0556] When the MAC PDU / TB only includes periodic BSRs and no LCGs are available, or when the MAC PDU only includes filler BSRs.

[0557] In one embodiment, if the counter count reaches its maximum value, the UE can determine that a beam failure of the SDT has been detected. The UE can be configured with a maximum value for the counter.

[0558] In one embodiment, the counter can be reset when one or more of the following criteria are met:

[0559] In one embodiment, the counter can be reset when the UE successfully transmits UL data (via CG).

[0560] In one embodiment, the counter can be reset when a specific timer expires. The specific timer can (re)start when the UE successfully performs a UL transmission via the CG. The specific timer can (re)start when the UE receives a DL response (e.g., ACK / NACK) from the NW. The DL response can be a PDCCH addressed to a specific RNTI (e.g., C-RNTI / CS-RNTI). The DL response can be received within the window / timer's time period. After a UL transmission via the CG, the window / timer can (re)start (offset).

[0561] In one embodiment, the counter can be reset when the UE receives a DL response (e.g., ACK / NACK) from the NW. The DL response can be a PDCCH addressed to a specific RNTI (e.g., C-RNTI / CS-RNTI). The DL response can be received within a window / timer period. After UL transmission via CG, the window / timer can (re)start (offset).

[0562] In one embodiment, the counter can be reset when the UE enters RRC_CONNECTED and / or RRC_IDLE.

[0563] In one embodiment, the counter can be reset when the corresponding CG configuration / resource is released / suspended / cleared and / or the corresponding CG configuration / resource is deemed invalid.

[0564] In one embodiment, the counter can be reset when an SDT (CG-based and / or RA-based) process is stopped / cancelled and / or when an SDT (CG-based and / or RA-based) process is initialized.

[0565] Detecting UE behavior when SDT beam failure

[0566] In one embodiment, if the UE detects a beam failure in the SDT, the UE may perform one or more of the following actions:

[0567] In one embodiment, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can skip the SDT via the CG. Specifically, the UE can skip the SDT for a period of time (e.g., based on a timer and / or a backoff value). The UE can re-perform beam selection and / or CG resource selection after the timer expires and / or the backoff time has elapsed.

[0568] In one embodiment, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP threshold (e.g., SSRRSRP) higher than the RSRP threshold (e.g., in the beams in the configured beam list), the UE may consider the CG configuration / resources to be invalid.

[0569] In one embodiment, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE may consider the timer (e.g., TAT timer or beam active timer) to be expired and / or stopped.

[0570] Specifically, the UE may receive the timer value in the CG configuration, in the information element associated with the beam configuration (e.g., in the CG configuration), in the RRC release message (including suspendconfiguration), and / or in the RRC reconfiguration message.

[0571] In one example, the timer could be a TA timer. For instance, when the TA timer is running, the UE might consider the TA to be valid. When the TA timer is not running, the UE might consider the TA to be invalid.

[0572] In one example, the timer could be a window / timer used to monitor the PDCCH. For instance, after transmitting UL data (e.g., small data in RRC_INACTIVE), the UE can (re)start the window / timer (e.g., configured in the CG configuration), such as at the first PDCCH timing specified in 3GPP TS 38.213 after the end of UL data transmission. More specifically, the UE can monitor the PDCCH (e.g., on a specific search space configured in the CG configuration) via a specific RNTI (e.g., C-RNTI / CS-RNTI) while the window / timer is running.

[0573] In one example, the timer could be a beam-dependent timer. For instance, the UE can (restart) the timer when / after performing beam measurement and / or beam selection. The UE may not perform beam measurement and / or beam selection while the timer is running. The UE can perform beam measurement and / or beam selection when / after the timer expires.

[0574] In one embodiment, if a beam failure of the SDT is detected and / or if there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can release / clear / suspend / store (all) CG configuration / resources / timing (for the SDT).

[0575] In one embodiment, if a beam failure of SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate an RA procedure (for SDT).

[0576] In one embodiment, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate an RRC (connection) recovery procedure.

[0577] In one example, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among beams in the configured beam list), the UE may initiate the transmission of an RCResumeRequest message or RCResumeRequest1 according to 5.3.13.3 of 3GPP TS38.331.

[0578] In one embodiment, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among beams in the configured beam list), the UE can trigger / generate / transmit a message / report to indicate this situation to the NW (e.g., beam failure and / or no beam qualified). In one embodiment, the message / report can be used to instruct the NW to release / suspend / deactivate the corresponding CG configuration / resource by the UE. In one embodiment, if the UE triggers this message / report, the UE can trigger / initiate an RA procedure. More specifically, the message / report can be transmitted via Msg3 and / or MsgA. In one embodiment, the message / report can be transmitted via RRC signaling, MAC-CE, and / or PHY signaling.

[0579] In one embodiment, if a beam failure of SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can ramp power (in dB) to perform SDT. The amount of ramp power (dB) depends on pre-configured parameters (e.g., in CG configuration and / or RRC release messages). For example, the pre-configured parameter might be powerRampingStep.

[0580] In one embodiment, if a beam failure of the SDT is detected and / or there is no beam (e.g., SSB) with an RSRP (e.g., SS-RSRP) higher than the RSRP threshold (among the beams in the configured beam list), the UE can initiate / execute a cell reselection procedure. For example, the UE can remain in RRC_INACTIVE and perform cell reselection. For example, the UE can enter RRC_IDLE and perform cell reselection.

[0581] In one embodiment, when the UE triggers / initiates a procedure for (CG-based) SDT, it may also trigger a procedure for detecting beam failure in SDT. In one embodiment, when the UE receives CG configuration (for SDT), it may trigger a procedure for detecting beam failure in SDT. In one embodiment, when the UE receives an RRC release (with suspendconfig) message, it may trigger a procedure for detecting beam failure in SDT. In one embodiment, the UE may execute only the procedure for CG-based SDT.

[0582] CG (re)initialization

[0583] In some embodiments, if a CG has been suspended (e.g., instead of being released / discarded / cleared), the CG may be (re)initialized based on one or more of the following conditions (e.g., via NW). For example, the UE may (re)initialize any suspended configuration license of configuration license type 1 based on one or more of the following conditions.

[0584] In one embodiment, the UE can (re)initialize the CG when / after receiving a specific instruction from the NW.

[0585] In one embodiment, the UE may receive a specific indication from the NW, which may instruct (re)initialization of one or more (pending) CG configurations / resources. In one embodiment, the specific indication may be received via SIB, RRC release message, RRC reconfiguration message, MAC CE, and / or DCI.

[0586] In one embodiment, the UE can (re)initialize the CG after the CG (and / or its associated beam) has been determined to be valid.

[0587] In one embodiment, if the UE determines that the channel quality (e.g., RSRP) of the beam is higher than a threshold, the UE can (re)initialize the (suspended) CG associated with the beam.

[0588] In one embodiment, when the UE selects a beam for performing UL transmissions for SDT, the UE can (re)initialize the (suspended) CG associated with the beam.

[0589] In one embodiment, the UE can (re)initialize the CG after transmitting a specific instruction to the NW.

[0590] In one embodiment, the UE can (re)initialize (suspended) CG (associated with the beam) after transmitting a specific instruction to the NW.

[0591] In one embodiment, the specific indication could be a beam measurement report. This specific indication could indicate that the beam is qualified. The UE can then (re)initialize the (pending) CG (associated with the qualified beam).

[0592] In one embodiment, the specific indication may be a request message. The specific indication may be used to indicate that the CG (beam-related) is valid.

[0593] In one embodiment, the UE can (re)initialize the CG after the UE selects a specific carrier (e.g., NUL / SUL).

[0594] In one embodiment, a first CG configuration / resource can be configured for an NUL carrier, and a second CG configuration / resource can be configured for an SUL carrier. For example, if the UE does not select a first carrier associated with the first CG configuration / resource (e.g., NUL), the UE can suspend the first CG configuration / resource. Then, after the UE selects the first carrier again (e.g., NUL), the UE can (re)initialize the first CG configuration / resource.

[0595] CG valid determination

[0596] In one embodiment, the UE may determine whether the CG resources / configuration are valid based on one or more of the following criteria:

[0597] In one embodiment, the validity of a CG resource / configuration is determined based on whether the associated beam is valid. The validity of the associated beam may be based on an RSRP threshold.

[0598] In one example, if at least one beam has an RSRP higher than the RSRP threshold, the UE can consider the CG resource / configuration to be valid.

[0599] In one example, if there is no beam with an RSRP greater than the RSRP threshold, the UE can consider the CG resource / configuration invalid.

[0600] In one embodiment, the validity of CG resources / configuration is determined based on the validity of the TA (Transaction Transfer). The UE can determine that the CG resources / configuration is valid when the TA is valid. If the TA is invalid, the UE can consider the CG resources / configuration to be invalid.

[0601] In one embodiment, the validity of the TA can be based on the TA timer. For example, the UE may consider the TA valid when the TA timer is running. When the TA timer is not running, the UE may consider the TA invalid.

[0602] In one embodiment, the validity of a TA can be based on the change in RSRP. For example, if the change in RSRP is higher than a threshold, the UE may consider the TA invalid.

[0603] In one embodiment, the validity of a CG resource / configuration is determined based on whether the CG resource / configuration is valid.

[0604] In one embodiment, the CG resource configuration can be valid when it is initialized.

[0605] In one embodiment, the CG resource configuration is invalid when it is released / suspended.

[0606] In one embodiment, when the UE is on a specific carrier (e.g., NUL or SUL) or a selected specific carrier (SDT), CG resources / configurations configured for the specific carrier can be considered valid, and CG resources / configurations configured for other carriers can be considered invalid.

[0607] In one embodiment, the validity of CG resources / configurations depends on whether the data is only available for transports of DRBs that have SDT enabled.

[0608] In one embodiment, the UE may be configured with one or more DRB / LCHs dedicated to SDT.

[0609] In one embodiment, the validity of a CG resource / configuration is determined based on whether the RSRP is greater than the RSRP threshold configured for the SDT.

[0610] In one embodiment, the validity of CG resources / configuration is determined based on whether the amount of data used for transmission is below a configuration threshold for SDT.

[0611] In one embodiment, the validity of a CG resource / configuration is determined based on (explicit) instructions received from the NW.

[0612] In one embodiment, the indicator may indicate whether the CG (associated with the beam) is valid.

[0613] In one embodiment, the validity of a CG resource / configuration is determined based on whether a timer (e.g., T319 or a timer similar to T319) is running.

[0614] In one embodiment, the UE may consider the CG resources / configuration to be valid while the timer is running. The UE may consider the CG resources / configuration to be invalid when the timer is not running or when the timer expires.

[0615] In one embodiment, if the change in RSRP (i.e., the amount of RSRP change) is not greater than an RSRP threshold, the UE may consider the CG resource / configuration invalid. In one embodiment, the RSRP threshold used for comparison with the RSRP change is indicated by the configuration of the SDT from the NW.

[0616] In one embodiment, if CG resources are configured on a selected UL carrier, the UE may consider the CG resources / configuration to be valid. In one embodiment, the selected UL carrier may be a Normal Uplink (NUL) carrier or a Supplemental Uplink (SUL) carrier.

[0617] In one embodiment, a timer can be used to detect SDT failures.

[0618] In one embodiment, when the UE is in RRC_INACTIVE state, the timer can (re)start during UL data transmission. The timer can (re)start during small data transmission. The timer can (re)start during RRC recovery request transmission.

[0619] In one embodiment, the timer may stop upon receiving an RRCResume, RRCSetup, RRCRelease, an RRCRelease message with suspendConfig or RRCReject, cell reselection, and upper layer aborting connection establishment.

[0620] In one embodiment, when the timer expires, the UE may enter action upon entering RRC_IDLE (e.g., with a specific RRC recovery reason).

[0621] Figure 11 This is a flowchart of a method for a network adapted for SDT according to an exemplary embodiment of this disclosure. (Reference) Figure 11 The network (e.g., the BS) transmits a configuration to the UE (step S1110). This configuration indicates a first RSRP threshold. The network performs an SDT procedure based on CG resources in response to the RSRP of the DL path loss reference being higher than the first RSRP threshold (step S1130). Details of steps S1110 to S1130 can be found in [reference needed]. Figures 8-10 And it will be omitted.

[0622] Figure 12 This is a flowchart of a method for a network adapted for SDT according to an exemplary embodiment of this disclosure. (Reference) Figure 12 The network (e.g., BS) transmits the CG configuration for SDT to the UE (step S1210). In response to transmitting the CG configuration, the network performs the transmission via CG resources / timing (step S1230). Details of steps S1210 to S1250 can be found in [reference missing]. Figures 8-10 And it will be omitted.

[0623] Subsequent data transmission

[0624] In one embodiment, for SDT, the UE may transmit assistance information / reports (e.g., indications, BSRs, and / or PHRs) to the NW to indicate whether follow-up data is available. Therefore, some issues arise, such as...

[0625] How can the UE determine whether subsequent data exists?

[0626] If there is subsequent data, how to trigger / generate assistance information / report NW?

[0627] Which information should be included in the auxiliary information (e.g., instructions and / or BSR)?

[0628] How to determine if there is follow-up data?

[0629] In some embodiments, the UE may determine whether subsequent data exists based on one or more of the following embodiments:

[0630] In one embodiment, the UE may determine whether subsequent data exists based on whether UL data for the SRB / DRB / LCH (belonging to the LCG) becomes available (for the MAC entity) and / or whether the UL data belongs to an LCH with a higher priority than any LCH containing available UL data belonging to any LCG.

[0631] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT (specifically).

[0632] In one embodiment, the UE may consider only SRB / DRB, LCH and / or LCG, which are configured for the SDT used to determine UL data.

[0633] In one embodiment, the UE does not consider SRB / DRB, LCH, and / or LCG, which are not configured for the SDT used to determine UL data.

[0634] In one embodiment, the UE may determine whether subsequent data exists based on whether UL data of the DRB / LCH (belonging to the LCG) becomes available (for MAC entities) and / or whether the LCH belonging to the LCH does not contain any available UL data.

[0635] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT.

[0636] In one embodiment, the UE may consider only SRB / DRB, LCH and / or LCG, which are configured for the SDT used to determine UL data.

[0637] In one embodiment, the UE does not consider SRB / DRB, LCH, and / or LCG, which are not configured for the SDT used to determine UL data.

[0638] In one embodiment, the UE can determine whether there is subsequent data based on whether the data volume (for DRB, LCH, and / or LCH) is higher or lower than a threshold.

[0639] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT (specifically).

[0640] In one embodiment, the UE may only consider SRB / DRB, LCH and / or LCG, which are configured for the SDT used to determine the amount of data.

[0641] In one embodiment, the UE does not consider SRB / DRB, LCH and / or LCG, which are not configured for SDT used to determine the amount of data.

[0642] In one embodiment, the UE can determine whether there is subsequent data based on whether the UE has (more) data to transmit or receive in the near future.

[0643] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT (specifically).

[0644] In one embodiment, the UE may only consider SRB / DRB, LCH and / or LCG, which are configured for SDT to determine whether there is data to be transmitted or received in the near future.

[0645] In one embodiment, the UE does not consider SRB / DRB, LCH and / or LCG, which are not configured for SDT to determine whether there is data to be transmitted or received in the near future.

[0646] In one embodiment, the UE may determine whether subsequent data exists based on whether subsequent DL or UL transmissions are expected.

[0647] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT (specifically).

[0648] In one embodiment, the UE may consider only SRB / DRB, LCH and / or LCG, which are configured for SDT to determine whether subsequent DL or UL transmissions are expected.

[0649] In one embodiment, the UE does not consider SRB / DRB, LCH and / or LCG, which are not configured for SDT to determine whether subsequent DL or UL transmissions are expected.

[0650] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT (specifically). In one embodiment, the UE may consider only the DRB, LCH, and / or LCG configured for SDT to determine whether subsequent data exists. In one embodiment, the UE does not consider DRB, LCH, and / or LCG, which are not configured for SDT to determine whether subsequent data exists.

[0651] How to trigger auxiliary information / reports

[0652] In some embodiments, the UE may trigger / generate / transmit auxiliary information / reports based on one or more of the following embodiments:

[0653] In one embodiment, if the UE determines that there is subsequent data, the UE may trigger / generate / transmit auxiliary information / report.

[0654] In one example, if UL data of an SRB / DRB / LCH (belonging to an LCG) becomes available (for a MAC entity) and / or the UL data belongs to an LCH with a higher priority than any LCH containing available UL data belonging to any LCG, the UE can trigger / generate / transmit auxiliary information / reports.

[0655] In one example, if UL data for the SRB / DRB / LCH (belonging to the LCG) becomes available (for the MAC entity) and / or the LCH (belonging to the LCH) does not contain any available UL data, the UE can trigger / generate / transmit auxiliary information / reports.

[0656] In one example, if the amount of data (for SRB / DRB, LCH and / or LCH) is higher or lower than a threshold, the UE can trigger / generate / transmit auxiliary information / reports.

[0657] In one example, if the UE has (more) data to transmit or receive in the near future, the UE can trigger / generate / transmit auxiliary information / reports.

[0658] In one example, if subsequent DL or UL transmissions are expected, the UE can trigger / generate / transmit auxiliary information / reports.

[0659] In one embodiment, SRB / DRB, LCH, and / or LCG can be configured for SDT (specifically). In one embodiment, the UE only considers SRB / DRB, LCH, and / or LCG, which are configured for SDT to determine whether to trigger / generate / transmit auxiliary information / reports. In one embodiment, the UE does not consider SRB / DRB, LCH, and / or LCG, which are not configured for SDT to determine whether to trigger / generate / transmit auxiliary information / reports.

[0660] In one example, if the UE is configured with a specific IE to allow the transmission of auxiliary information / reports on msg3 / MSGA, the UE can always trigger auxiliary information / reports and cancel the triggering of auxiliary information / reports after they are transmitted on msg3 / MSGA.

[0661] In one embodiment, if the first timer (e.g., a limit timer) is not running, the UE may trigger / generate / transmit auxiliary information / reports. If the first timer (e.g., a limit timer) is running, the UE may not trigger / generate / transmit auxiliary information / reports.

[0662] In one embodiment, when / after the UE transmits auxiliary information / reports, the first timer can be (re)started.

[0663] In one embodiment, if a second timer (e.g., a periodic timer or a retransmission timer) expires, the UE may trigger / generate / transmit auxiliary information / reports.

[0664] In one embodiment, a second timer can be restarted when / after the UE transmits auxiliary information / reports.

[0665] What information should be included in the supplementary information / report?

[0666] In one embodiment, auxiliary information / reports can be used to provide the service gNB with information on whether subsequent DL and / or UL transmissions are expected.

[0667] In one embodiment, the auxiliary information / report may be an indication with zero or one or more bits or code points / indices.

[0668] In one embodiment, auxiliary information / reports can be used to indicate whether follow-up data exists.

[0669] In one embodiment, auxiliary information / reports may be used to indicate whether DL and / or UL data transfer is expected.

[0670] In one embodiment, the auxiliary information / report may be a BSR.

[0671] In one embodiment, as shown in 3GPP TS 38.321, the Buffer Status Report (BSR) procedure is used to provide the serving gNB with information about the amount of UL data in the MAC entity.

[0672] In one embodiment, a BSR can be a regular BSR, a periodic BSR, and / or a filled BSR.

[0673] In one embodiment, the Buffer Status Report (BSR) MAC CE may include:

[0674] Short BSR format (fixed size); or

[0675] Long BSR format (variable size); or

[0676] Short truncated BSR format (fixed size); or

[0677] Long truncated BSR format (variable size).

[0678] In one embodiment, auxiliary information / reports (e.g., a buffer size field) may, after MAC PDU construction, indicate the total amount of data available on all logical channels of a logical channel group (which is configured as SDT) according to the data volume calculation procedures in 3GPP TS 38.322 and TS 38.323 (i.e., after the logical channel prioritization process, this may result in a buffer size field value of zero). The data volume is expressed in bytes. The sizes of the RLC header and MAC subheader are not considered in the buffer size calculation. Alternatively, auxiliary information / reports (e.g., a buffer size field) may, after MAC PDU construction, indicate the total amount of data available on logical channels (which are configured as SDT) of a logical channel group (which is configured as SDT) according to the data volume calculation procedures in 3GPP TS 38.322 and TS 38.323 (i.e., after the logical channel prioritization process, this may result in a buffer size field value of zero). The data volume is indicated in bytes. The sizes of the RLC header and MAC subheader are not considered in the buffer size calculation.

[0679] In one embodiment, the auxiliary information / report may be a PHR.

[0680] In one embodiment, the power margin reporting process can be used to provide the following information to the serving gNB:

[0681] Type 1 Power Margin: The difference between the nominal maximum transmit power of the UE and the estimated power of UL-SCH transmission for each active serving cell;

[0682] Type 2 Power Margin: The difference between the nominal maximum transmit power of the UE and the estimated power of UL-SCH and PUCCH transmissions on the SpCell of other MAC entities (i.e., E-UTRA MAC entities in the cases of EN-DC, NE-DC, and NGEN-DC).

[0683] Type 3 power margin: The difference between the nominal maximum transmit power of the UE and the estimated power of SRS transmission for each active serving cell;

[0684] MPE P-MPR: UE applies power backoff to meet the MPE FR2 requirements of the serving cell.

[0685] In one embodiment, the auxiliary information / report may be a beam report.

[0686] In one embodiment, auxiliary information / reports may indicate (selected) (one or more) SSBs (indices).

[0687] In one embodiment, auxiliary information / reports may include a field indicating the presence of an SSB index field. For example, if at least one SSB in the configured list of SSB resources (e.g., including CG SSB resources) has an SS-RSRP higher than a threshold, the field may be set to a first value (e.g., 1); otherwise, it may be set to a second value (e.g., 0).

[0688] In one embodiment, auxiliary information / reports may include a field that is set to index the SSBs whose SS-RSRP is higher than rsrp-ThresholdBFR (among SSBs in the configured SSB resource list (e.g., including C CG-SSB-resource)).

[0689] In one embodiment, auxiliary information / reports may indicate the SSB index and its measurement results (e.g., the value of RSRP).

[0690] In one embodiment, auxiliary information / reports can be transmitted via RRC signaling / MAC CE / PHY signaling.

[0691] In one embodiment, auxiliary information / reports may be transmitted via a first CG resource / timing.

[0692] In one embodiment, auxiliary information / reports can be used to notify the NW which SSB is qualified, and then the NW can transmit DL signaling to the UE based on that SSB.

[0693] In one embodiment, the auxiliary information / report may indicate quantitative patterns (e.g., cycle amount, offset, resource quantity, data quantity, etc.).

[0694] In one embodiment, auxiliary information / reports may be triggered by an upper layer (e.g., the RRC layer) and / or by a MAC entity.

[0695] In one embodiment, the auxiliary information / report can be PHY signaling / MAC CE / RRC signaling.

[0696] In one embodiment, if the UE determines that there is no further data, the UE can cancel the triggered assistance information / report. Furthermore, the UE can only cancel the triggered assistance information / report if the NW has already configured a specific IE for the UE. A specific IE can be configured in an RRC release message (with a suspend configuration).

[0697] In one embodiment, if the UE determines that there is no subsequent data, the UE may trigger / generate / transmit a BSR with a transmission buffer size of zero bytes.

[0698] In one embodiment, the UE can generate a short BSR format, a long BSR format (variable size), a short truncated BSR format (fixed size), or a long truncated BSR format (variable size).

[0699] In one embodiment, the UE can set the value of all LCH ID / LCHi fields (in the BSR MAC CE) to 1 or 0. Alternatively, the UE can set the value of the LCH ID / LCHi field (in the BSR MAC CE) for the SDT configuration to a specific value (e.g., 0 or 1).

[0700] In one embodiment, the UE can set the buffer size field (in BSR MAC CE) to a specific value (e.g., 0).

[0701] In one embodiment, if the UE determines that there is no subsequent data, the UE may not trigger / generate / transmit auxiliary information / reports.

[0702] In one embodiment, when assistance information / reports have been triggered, the assistance information / reports may have a higher priority than data from any logical channel, except for data from the UL-CCCH, for example, only if the logical channel priority, including assistance information / reports, does not require segmentation of the RLC SDU in the generated MAC PDU. Otherwise, data from the LCH may have a higher priority than assistance information / reports.

[0703] In one embodiment, for SDT (e.g., via CG), auxiliary information / reports are triggered due to logical channel priority, but are not included in the MAC PDU generated by the MAC SDU, and the (triggered) auxiliary information / reports may be canceled.

[0704] In one embodiment, after transmitting UL data (e.g., small data in RRC_INACTIVE), including auxiliary information / reports, the UE may (re)start the window / timer (e.g., configured in the CG configuration), for example, at the first PDCCH timing specified in 3GPP TS 38.213 after the end of UL data transmission. In one embodiment, the UE may monitor the PDCCH (e.g., on a specific search space configured in the CG configuration) via a specific RNTI (e.g., C-RNTI / CS-RNTI) while the window / timer is running.

[0705] In one embodiment, if the auxiliary information / report indicates that the buffer size is greater than 0, the UE can (re)start the window / timer and / or monitor the PDCCH.

[0706] In one embodiment, if the auxiliary information / report indicates that the buffer size is 0, the UE may not (re)start the window / timer and / or monitor the PDCCH.

[0707] In one embodiment, for monitoring PDCCH, the UE may attempt to detect a specific DCI (e.g., DCI format 1_0) with a CRC scrambled by a specific RNTI (e.g., C-RNTI / CS-RNTI) during a window / timer period.

[0708] Dependence

[0709] In one embodiment, one or more of the aforementioned (specific) counters may be reset when the UE performs a cell (re)selection or RAN notification area (RNA) update procedure.

[0710] In one embodiment, one or more of the aforementioned (specific) counters may be reset when the UE changes its serving cell to another cell or when the UE camps on a new (suitable / acceptable) cell.

[0711] In one embodiment, when the UE determines that the CG resource / configuration is invalid or when the received signal quality (e.g., RSRP / RSRQ) of all configured SSBs is below the corresponding threshold, one or more of the aforementioned (specific) counters may be reset.

[0712] In one embodiment, when the UE changes its RRC state from RRC Inactive to RRC Idle or RRC Connected (e.g., when it receives an RRC Release message and / or an RRC Resume message, and / or when a specific timer (e.g., T319) expires), one or more of the aforementioned (specific) counters can be reset (e.g., in this case, the UE may not change its serving / camping cell).

[0713] In one embodiment, when the UE performs a MAC reset, one or more of the aforementioned (specific) counters can be reset.

[0714] In one embodiment, when the UE initiates the RA / CG procedure (for SDT), one or more of the aforementioned (specific) counters can be reset.

[0715] In one embodiment, when the UE considers the process (for SDT, for CG-based SDT and / or for RA-based SDT) to be successful / unsuccessful, it may reset one or more of the aforementioned (specific) counters.

[0716] In one embodiment, when the UE stops the process (for SDT, for CG-based SDT and / or for RA-based SDT), one or more of the aforementioned (specific) counters can be reset.

[0717] In one embodiment, one or more of the aforementioned (specific) counters can be reset when the UE switches / selects from NUL to SUL and / or from SUL to NUL. For example, one or more of the aforementioned (specific) counters can be configured via SIB, RRC release (with suspendconfig) message, RRC reconfiguration, DCI and / or CG configuration. For example, one or more of the aforementioned (specific) counters can be reset when the beam configuration (corresponding to the counter) is released / reconfigured.

[0718] In one example, the NW can reconfigure the beam configuration via the RRRCRelease message. For instance, when the NW reconfigures the CG configuration (corresponding to the counters), one or more of the aforementioned (specific) counters can be reset.

[0719] In one example, the NW can reconfigure the beam configuration via the RRCRelease message. For instance, when the UE receives a specific indication that CG transmission in RRC_INACTIVE is no longer supported in the serving cell, it can reset one or more of the aforementioned (specific) counters.

[0720] In one embodiment, when the UE performs a cell (re)selection or RAN notification area (RNA) update process, one or more of the aforementioned (specific) timers can be (re)started / stopped.

[0721] In one embodiment, when the UE changes its serving cell to another cell or when the UE camps on a new (suitable / acceptable) cell, one or more of the aforementioned (specific) timers can be (re)started / stopped.

[0722] In one embodiment, when the UE determines that the CG resource / configuration is invalid or when the received signal quality (e.g., RSRP / RSRQ) of all configured SSBs is below the corresponding threshold, it can (re)start / stop one or more of the aforementioned (specific) timers.

[0723] In one embodiment, when the UE changes its RRC state from RRC Inactive to RRC Idle or RRC Connected (e.g., when it receives an RRC Release message and / or an RRC Resume message, and / or when a specific timer (e.g., T319) expires), one or more of the aforementioned (specific) timers can be (re)initiated / stopped (e.g., in this case, the UE may not change its serving / camping cell).

[0724] In one embodiment, when the UE performs a MAC reset, one or more of the aforementioned timers can be restarted / stopped. In one embodiment, when the UE initiates an RA / CG procedure (for SDT), one or more of the aforementioned timers can be restarted / stopped.

[0725] In one embodiment, when the UE considers the process (for SDT, for CG-based SDT and / or for RA-based SDT) to be successful / unsuccessful, it can (re)start / stop one or more of the aforementioned (specific) timers.

[0726] In one embodiment, when the UE stops the process (for SDT, for CG-based SDT and / or for RA-based SDT), one or more of the aforementioned timers can be (re)started / stopped.

[0727] In one embodiment, when the UE switches / selects from NUL to SUL and / or from SUL to NUL, one or more of the aforementioned specific timers can be (re)started / stopped. For example, one or more of the aforementioned specific timers can be configured via SIB, RRC release (with suspendconfig) message, RRC reconfiguration, DCI and / or CG configuration. For example, when the beam configuration (corresponding to the counter) is released / reconfigured, one or more of the aforementioned specific timers can be (re)started / stopped.

[0728] In one example, the NW can reconfigure the beam configuration via the RRRCRelease message. For instance, when the CG configuration (corresponding to the counter) is reconfigured by the NW, one or more of the aforementioned timers can be (re)started / stopped.

[0729] In one example, the NW can reconfigure the beam configuration via the RRCRelease message. For instance, when the UE receives a specific indication that CG transmission in RRC_INACTIVE is no longer supported in the serving cell, it can (re)start / stop one or more of the aforementioned (specific) timers.

[0730] In one embodiment, the NW may also maintain the aforementioned (specific) counter and / or timer. The operation of the aforementioned (specific) counter and / or timer may be identical for both the UE and the NW.

[0731] In one embodiment, the NW can also release / suspend / discard / clear CG resources / opportunities based on the same conditions / criteria mentioned for the UE in this disclosure.

[0732] In one embodiment, "resources" and "timing" may be used interchangeably in some embodiments of this disclosure.

[0733] In one embodiment, “beam,” “SSB,” “TRS,” “CSI-RS,” “auxiliary RS,” and “TCI status” may be used interchangeably in some embodiments disclosed herein.

[0734] In one embodiment, “associated,” “corresponding to,” and “mapped to” may be used interchangeably in some embodiments of this disclosure.

[0735] Figure 13 A block diagram of a node for wireless communication according to various aspects of this disclosure is shown. Figure 13 As shown, node 1300 may include a transceiver 1320, a processor 1328, a memory 1334, one or more presentation components 1338, and at least one antenna 1336. Node 1300 may also include an RF band module, a base station communication module, a network communication module, and a system communication management module, input / output (I / O) ports, I / O components, and a power supply (not shown in the diagram). Figure 7 (as clearly shown in the diagram). The components can communicate directly or indirectly with each other via one or more buses 740. In one embodiment, node 1300 may perform the various functions described in this disclosure (e.g., see reference 1340). Figures 1 to 13 -1) UE or base station.

[0736] Transceiver 1320 includes a transmitter 1322 (e.g., transmit / transmit circuitry) and a receiver 1324 (e.g., receive / receive circuitry). Transceiver 1320 can be configured to transmit and / or receive time and / or frequency resource allocation information. In some embodiments, transceiver 1320 can be configured to transmit in different types of subframes and time slots, including, but not limited to, available, unavailable, and flexibly usable subframe and time slot formats. Transceiver 1320 can be configured to receive data and control signaling.

[0737] Node 1300 may include a variety of computer-readable media. Computer-readable media may be any available media accessible by Node 1300, and includes volatile and non-volatile media, removable and non-removable media. As a non-limiting example, computer-readable media may include computer storage media and communication media. Computer storage media may include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing computer-readable information.

[0738] Computer storage media may include RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, Digital Versatile Disk (DVD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Computer storage media does not include transmitted data signals. Communication media can generally be embodied as computer-readable instructions, data structures, program modules, or other data in modulated data signals (such as carrier waves or other transmission mechanisms), and includes any information transmission medium. The term "modulated data signal" can indicate that one or more characteristics of this signal are set or altered to encode data into this signal. By way of example and not limitation, communication media includes wired media such as wired networks or direct wired connections, and wireless media such as acoustic, RF, infrared, and other wireless media. Any combination of the above should also be included within the scope of computer-readable media.

[0739] Memory 1334 may comprise a computer storage medium in the form of volatile and / or non-volatile memory. Memory 1334 may be removable, non-removable, or a combination thereof. Exemplary memory may include solid-state memory, hard disk, optical disk drive, etc. As shown in Figure 13, memory 1334 may store computer-readable, computer-executable instructions 1332 (e.g., software code) configured to, when executed, cause processor 1328 to perform various functions described herein, for example, referencing... Figures 1 to 13 -1. Alternatively, instruction 1332 may not be executed directly by processor 1328, but may be configured to cause node 1300 (e.g., when compiled and executed) to perform the various functions described herein.

[0740] Processor 1328 (e.g., having processing circuitry) may include intelligent hardware devices, such as a central processing unit (CPU), microcontroller, ASIC, etc. Processor 1328 may include memory. Processor 1328 can process data 1330 and instructions 1332 received from memory 1334, and information transmitted via transceiver 1320, baseband communication module, and / or network communication module. Processor 1328 can also process information to be transmitted to transceiver 1320 for transmission via antenna 1336, and to network communication module for transmission to the core network.

[0741] One or more presentation components 1338 may present data indications to a person or other device. Exemplary one or more presentation components 1338 include display devices, speakers, printing components, vibrating components, etc.

[0742] Based on the above description, various techniques can be used to implement the concepts described in this application without departing from the scope of these concepts. Furthermore, although these concepts have been specifically described with reference to certain embodiments, those skilled in the art will recognize that changes in form and detail can be made without departing from the scope of these concepts. Therefore, the described embodiments should be considered illustrative rather than restrictive in all respects. It should be understood that this application is not limited to the specific embodiments described above, and many rearrangements, modifications, and substitutions of these embodiments are possible without departing from the scope of this disclosure.

Claims

1. A method for small data transmission SDT, applied to user equipment (UE), characterized in that, The method includes: Receive configuration from base station BS, wherein the configuration indicates a first reference signal received power (RSRP) threshold and a second RSRP threshold; In response to the downlink DL path loss reference RSRP being higher than the first RSRP threshold, an SDT process is initiated based on the configured authorized CG resources; In response to initiating the SDT procedure based on the CG resource: If a first RSRP higher than the second RSRP threshold exists in the Synchronization Signal / Physical Broadcast Channel Block (SSB), then the SSB is selected from the SSB group; and If no SSB in the SSB group has an RSRP higher than the second RSRP threshold, the CG resource is considered invalid and a random access RA procedure is initiated.

2. The method as described in claim 1, characterized in that, The configuration is configured via the BS through a Radio Resource Control (RRC) release message.

3. The method as described in claim 1, characterized in that, The SSB group is configured via the BS through Radio Resource Control (RRC) release messages or through system information.

4. The method as described in claim 1, characterized in that, The method further includes: If the first RSRP is higher than the second RSRP threshold, then a CG resource timing corresponding to the selected SSB is selected.

5. The method as described in claim 1, characterized in that, The first RSRP threshold is configured by the SDT configuration in the configuration.

6. The method as described in claim 1, characterized in that, The second RSRP threshold is configured by the CG configuration in the configuration.

7. The method as described in claim 1, characterized in that, The configuration also indicates a third RSRP threshold, and the method further includes: If the change in RSRP does not exceed the third RSRP threshold, the CG resource is considered valid.

8. The method as described in claim 1, characterized in that, The method further includes: Select the uplink UL carrier; and In response to the CG resource being configured on the selected UL carrier, the CG resource is considered valid.

9. The method as described in claim 8, characterized in that, The selected UL carrier is either a conventional uplink NUL carrier or a supplementary uplink SUL carrier.

10. A user equipment (UE), characterized in that, include: A transceiver is used to send or receive signals; Memory, used to store instructions; and The processor, coupled to the transceiver and the memory, is configured to execute the instructions to cause the UE to: The transceiver receives a configuration from the base station BS, wherein the configuration indicates a first reference signal received power (RSRP) threshold and a second RSRP threshold. In response to the downlink DL path loss reference RSRP being higher than the first RSRP threshold, an SDT process is initiated by configuring authorized CG resources; In response to initiating the SDT procedure via the CG resource: If a first RSRP higher than the second RSRP threshold exists in the Synchronization Signal / Physical Broadcast Channel Block (SSB), then the SSB is selected from the SSB group; and If no SSB in the SSB group has an RSRP higher than the second RSRP threshold, the CG resource is considered invalid and a random access RA procedure is initiated.

11. The UE as claimed in claim 10, characterized in that, The configuration is configured via the BS through a Radio Resource Control (RRC) release message.

12. The UE as claimed in claim 10, characterized in that, The SSB group is configured via the BS through Radio Resource Control (RRC) release messages or through system information.

13. The UE as claimed in claim 10, characterized in that, The processor is also configured to: If the first RSRP is higher than the second RSRP threshold, then a CG resource timing corresponding to the selected SSB is selected.

14. The UE as claimed in claim 10, characterized in that, The first RSRP threshold is configured by the SDT configuration in the configuration.

15. The UE as claimed in claim 10, characterized in that, The second RSRP threshold is configured by the CG configuration in the configuration.

16. The UE as claimed in claim 10, characterized in that, The processor is also configured to: If the change in RSRP does not exceed the third RSRP threshold, the CG resource is considered valid.

17. The UE as claimed in claim 10, characterized in that, The processor is also configured to: Select the uplink UL carrier; and In response to the CG resource being configured on the selected UL carrier, the CG resource is considered valid.

18. The UE as claimed in claim 17, characterized in that, The selected UL carrier is either a conventional uplink NUL carrier or a supplementary uplink SUL carrier.

Images