Timing advance validation enhancements for preconfigured uplink resources

Abstract

Techniques and procedures for managing timing advance (TA) validation for configured grant small data transmission (CG-SDT) are disclosed. A scheduling entity can receive a downlink signal quality measurement of a downlink beam from a scheduled entity and a CG-SDT configuration request. The scheduling entity can transmit a CG-SDT configuration to the UE in response to receiving the CG-SDT configuration request, where the CG-SDT configuration includes a timing advance (TA) validation criterion based on the downlink signal quality measurement satisfying a configured threshold.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to Greek patent application No. 20200100468 of Lei et al., filed on August 10, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] In general, the techniques discussed below relate to wireless communication networks, and more specifically, to techniques for enhancing timing advance (TA) verification of pre-configured uplink resources (PUR) and configured permitted small data transmission (CG-SDT) processes. Background Technology

[0004] Technologies involving the Internet of Things (IoT) have become more widely used in recent years. The 3rd Generation Partnership Project (3GPP) has specified three cellular solutions for operation in licensed spectrum: Long Term Evolution (LTE) for Machine-Type Communications (LTE-M), Narrowband IoT (NB-IoT), and Extended Coverage GSM for IoT (EC-GSM-IoT). Unlike short-range and low-power wide-area (LPWA) technologies that operate in unlicensed spectrum, these 3GPP solutions operate in licensed spectrum and can provide guaranteed Quality of Service (QoS). Applications include, for example, sensors, surveillance cameras, wearable devices, smart meters, and smart meter sensors. Summary of the Invention

[0005] The following provides an overview of one or more aspects of this disclosure to offer a basic understanding of such aspects. This overview is not a general summary of all the features contemplated in this disclosure, and is neither intended to identify key or essential elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its sole purpose is to introduce some concepts of one or more aspects of this disclosure in the form of a preface to the detailed description to be given later.

[0006] In one example, a scheduling entity within a wireless communication network is disclosed, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receive a Configuration-Allowed Small Data Transmission (CG-SDT) configuration request from a user equipment (UE); and, in response to receiving the CG-SDT configuration request, send a CG-SDT configuration to the UE, the CG-SDT configuration including a timing advance (TA) verification criterion based on downlink signal quality measurements satisfying a configured threshold.

[0007] In one example, a wireless communication method for a scheduling entity in a wireless communication network is disclosed, the method comprising: receiving a Configuration-Allowed Small Data Transmission (CG-SDT) configuration request from a user equipment (UE); and sending a CG-SDT configuration to the UE in response to receiving the CG-SDT configuration request, the CG-SDT configuration including a timing advance (TA) verification criterion based on downlink signal quality measurements satisfying a configured threshold.

[0008] In one example, a user equipment (UE) within a wireless communication network is disclosed, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: transmit signal quality measurements of a configured downlink beam; transmit a configured permitted small data transmission (CG-SDT) request; receive a CG-SDT configuration including a timing advance (TA) verification criterion based on the signal quality measurements satisfying a configured threshold; verify the TA for CG-SDT transmission according to one or more of the TA verification criteria; and perform the CG-SDT configuration for communication with the wireless network.

[0009] In one example, a wireless communication method for a user equipment (UE) in a wireless communication network is disclosed, the method comprising: transmitting a signal quality measurement of a configured downlink beam; transmitting a configured permitted small data transmission (CG-SDT) request; receiving a CG-SDT configuration including a timing advance (TA) verification criterion based on the signal quality measurement satisfying a configured threshold; verifying the TA for CG-SDT configuration transmission according to one or more of the TA verification criteria; and performing the CG-SDT configuration for communication with the wireless network.

[0010] These and other aspects of the invention will become more fully understood by reading the following detailed description. Other aspects, features, and embodiments of the invention will become apparent to those skilled in the art by reading the following description of specific exemplary embodiments of the invention taken in conjunction with the accompanying drawings. Although features of the invention may be discussed below with respect to specific embodiments and figures, all embodiments of the invention may include one or more of the advantageous features discussed herein. In other words, while one or more embodiments may be discussed as having specific advantageous features, one or more such features may also be used according to the various examples of the invention discussed herein. Similarly, although exemplary embodiments may be discussed below as examples of devices, systems, or methods, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0011] Figure 1 It is an illustrative description of a wireless communication system based on certain aspects;

[0012] Figure 2 This is a conceptual illustration of an example of a radio access network based on some aspects;

[0013] Figure 3 This is a schematic diagram illustrating the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to several aspects;

[0014] Figure 4 This is a block diagram illustrating a wireless communication system that supports beamforming and / or multiple-input multiple-output (MIMO) communication according to some aspects;

[0015] Figure 5 This is a block diagram illustrating the radio protocol architecture for the user and control planes based on several aspects;

[0016] Figure 6 This is a signaling diagram illustrating the permission-based process between the UE and the scheduling entity, based on several aspects.

[0017] Figure 7 This is a signaling diagram illustrating the permissionless process between the UE and the scheduling entity based on certain aspects;

[0018] Figure 8 A signal block diagram of CG-SDT configuration 802 is shown according to some aspects;

[0019] Figure 9 The signaling diagrams for the UE and scheduling entity utilizing enhanced TA for the CG-SDT process are shown, based on several aspects.

[0020] Figure 10 This is a block diagram illustrating an example of how the hardware implementation of a UE using a processing system is performed, based on some aspects.

[0021] Figure 11 This is a block diagram illustrating an example of the hardware implementation of a scheduling entity for a processing system based on some aspects.

[0022] Figure 12 This is a flowchart illustrating an exemplary process for implementing a CG-SDT process with enhanced TA verification for a scheduling entity, based on some aspects;

[0023] Figure 13 This is a flowchart illustrating an exemplary process for implementing a CG-SDT process with enhanced TA verification for a UE, based on some aspects;

[0024] Figure 14 This is a flowchart illustrating another exemplary process for implementing a CG-SDT process with enhanced TA verification for a scheduling entity, based on some aspects; and

[0025] Figure 15 This is a flowchart illustrating another exemplary process for implementing a CG-SDT process with enhanced TA verification for a UE, based on some aspects. Detailed Implementation

[0026] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configurations through which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0027] While aspects and embodiments have been described in this application by way of example, those skilled in the art will understand that additional implementations and use cases can occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or uses can occur via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically relate to use cases or applications, a wide range of applicability to the described innovations can occur. The scope of implementations can cover a spectrum from chip-level or modular components to non-modular, non-chip-level implementations that incorporate one or more aspects of the described innovations, and further to aggregated, distributed, or OEM devices or systems. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily involve multiple components for both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are expected to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with varying sizes, shapes, and configurations.

[0028] One aspect of IoT technology, particularly for small data transmissions, is minimizing signaling overhead for IoT wireless devices or user equipment (UEs) to reduce energy consumption. Currently, Configurable Allowed Small Data Transmission (CG-SDT) (also known as PUR) is limited to providing timing advance (TA) verification criteria to IoT devices based on specific configurations, resulting in inefficient device operation. For example, current CG-SDT systems are limited or unable to customize CG-SDT transmissions to suit the characteristics of IoT devices, such as downlink signal quality measurements, downlink signal quality measurement configurations, downlink reference signals, corresponding beam indices of downlink reference signals, location information obtained from the serving cell or one or more neighboring cells, the corresponding transmit power offset for each downlink reference signal in the downlink reference signal, or thresholds for received power (RSRP) measurements or variations in RSRP measurements. Alternatively or otherwise, current CG-SDT systems are limited or unable to customize CG-SDT transmissions to accommodate aspects such as device capabilities, device radio resource control (RRC) status, device uplink coverage enhancements for CG-SDT transmissions, changes in the detection of the serving cell or transmit and receive point (TRP), TA timer configuration, and location information.

[0029] Techniques and processes for managing timing advance (TA) verification of Configurable Allowed Small Data Transmission (CG-SDT) are disclosed. The TA verification criteria are based on enhanced features including User Equipment (UE) capabilities, UE Radio Resource Control (RRC) status, DL beam configuration for one or more reference signals, location information, coverage enhancement, and UE power saving considerations (jointly configured with UE WUS timing, paging timing, and DRX-ON time intervals for measurement gaps). During the CG-SDT process, the CG-SDT configuration is configured with enhanced TA verification criteria to allow customized or common configurations for the UE, and the TA verification configuration can be jointly optimized with UE wake-up signaling, paging, and location signaling. Other aspects, features, and embodiments are also claimed and described.

[0030] Various aspects of this disclosure relate to processing CG-SDT in a wireless network, wherein timing advance (TA) verification criteria can be generated based on signal quality information such as signal quality measurements that meet configured thresholds and / or the configuration of configured downlink beams. A CG-SDT configuration request can be sent from a user equipment (UE) to a base station, wherein the base station, in response to receiving the CG-SDT configuration request, sends a CG-SDT configuration including the TA verification criteria to the UE. The UE can then verify and execute the received CG-SDT configuration for small data operations.

[0031] The various concepts presented in this disclosure can be implemented across multiple telecommunications systems, network architectures, and communication standards. See now. Figure 1 By way of illustrative example and not limitation, reference is made to wireless communication system 100 to illustrate various aspects of this disclosure. Wireless communication system 100 includes three interacting domains: core network 102, radio access network (RAN) 104, and user equipment (UE) 106. With wireless communication system 100, UE 106 is able to perform data communication with external data network 110 (such as, but not limited to, the Internet).

[0032] RAN 104 can implement any or multiple suitable wireless communication technologies for providing radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, RAN 104 can operate according to a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, commonly referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be used within the scope of this disclosure.

[0033] As shown, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from one or more cells of a UE. In different technologies, standards, or contexts, a base station may be referred to by those skilled in the art as a base transceiver unit (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), e node B (eNB), g node B (gNB), transmit and receive point (TRP), or some other suitable term. In some examples, a base station includes two or more TRPs, which may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In examples where RAN 104 operates according to both LTE and 5G NR standards, one base station may be an LTE base station, while the other may be a 5G NR base station.

[0034] RAN 104, supporting wireless communication for multiple mobile devices, is further illustrated. In 3GPP standards, a mobile device may be referred to as a User Equipment (UE), but may also be referred to by those skilled in the art as a Mobile Station (MS), User Station, Mobile Unit, User Unit, Radio Unit, Remote Unit, Mobile Device, Radio Device, Wireless Communication Device, Remote Device, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handset, Terminal, User Agent, Mobile Client, Client, or any other suitable term. A UE may be a device (e.g., a mobile device) that provides users with access to network services.

[0035] Within the scope of this disclosure, a "mobile" device does not necessarily need to have the ability to move and may be stationary. The term mobile device or mobile equipment broadly refers to a wide variety of devices and technologies. A UE includes multiple structured hardware components that are sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), laptops, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems (e.g., in relation to the "Internet of Things" (IoT)).

[0036] Mobile devices can additionally include automobiles or other vehicles, remote sensors or actuators, robots or robotic devices, satellite radios, Global Positioning System (GPS) devices, target tracking devices, drones, multi-rotor helicopters, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc.). Mobile devices can additionally include digital home or smart home devices (such as home audio, video and / or multimedia devices, home appliances, vending machines, smart lighting, home security systems, smart meters, etc.). Mobile devices can additionally include smart energy devices, security devices, solar panels or solar arrays, urban infrastructure devices controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers and / or agricultural equipment, etc. Furthermore, mobile devices can provide connected medical or telemedicine support (e.g., remote healthcare). Remote health devices include remote health monitoring devices and remote health management devices, which can be given preferential treatment or priority access to their communications compared to other types of information (e.g., priority access to and / or QoS related to the transmission of critical service data).

[0037] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to a specific aspect of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to a further aspect of this disclosure, the term uplink can refer to point-to-point transmissions originating from a UE (e.g., UE 106).

[0038] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all of the equipment and apparatus within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UE 106). That is, for scheduled communication, multiple UEs 106 (which may be scheduled entities) can utilize the resources allocated by the scheduling entity 108.

[0039] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0040] As in Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling services in the wireless communication network, including downlink service 112, and in some examples, uplink service 116 from one or more scheduled entities (e.g., one or more UEs 106) to scheduling entity 108. On the other hand, a scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., permission), synchronization or timing information, or other control information from another entity in the wireless communication network, such as scheduling entity 108).

[0041] Additionally, uplink and / or downlink control information and / or service information can be transmitted in waveforms that are time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in an Orthogonal Frequency Division Multiplexing (OFDM) waveform where each subcarrier carries one resource element (RE). A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within this disclosure, a frame can refer to a predetermined duration (e.g., 10 ms) for radio transmission, wherein each frame consists of, for example, 10 subframes, each 1 ms in length. Of course, these definitions are not mandatory, and any suitable scheme for organizing the waveform can be used, and various time divisions of the waveform can have any suitable duration.

[0042] In summary, base station 108 includes a backhaul interface for communication with the backhaul portion 120 of wireless communication system 100. Backhaul portion 120 can provide a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network can provide interconnection between the respective base stations 108. Various types of backhaul interfaces can be used, such as direct physical connections using any suitable transport network, virtual networks, etc.

[0043] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0044] Now for reference Figure 2 The illustrative illustration of a radio access network (RAN) 200 according to some aspects of this disclosure is provided as an example and not a limitation. In some examples, RAN 200 may be the same as described above and Figure 1 The same as RAN 104 shown in the figure.

[0045] The geographical area covered by RAN 200 can be divided into multiple cellular areas (cells) that can be uniquely identified by user equipment (UE) based on an identifier broadcast in the geographical area from an access point or base station. Figure 2 Cells 202, 204, 206, and 208, each comprising one or more sectors (not shown), are illustrated. A sector is a sub-area of ​​a cell. A single base station provides service to all sectors within a cell. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors can be formed by groups of antennas, where each antenna is responsible for communication with UEs in a portion of the cell.

[0046] Various base stations can be used for deployment. For example, in Figure 2 The diagram illustrates two base stations in cells 202 and 204: base station 210 and base station 212; a third base station, base station 214, is shown controlling the Remote Radio Header (RRH) 216 in cell 206. That is, the base stations can have integrated antennas, or they can be connected to an antenna or RRH 216 via feed cables. In the illustrated example, cells 202, 204, and 206 can be referred to as macrocells because base stations 210, 212, and 214 support cells with large sizes. Further, base station 218 is shown in cell 208, which can overlap with one or more macrocells. In this example, cell 208 can be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home node B, home e node B, etc.) because base station 218 supports cells with relatively small sizes. Cell size determination can be completed based on system design and component constraints.

[0047] It should be understood that RAN 200 includes any number of radio base stations and cells. Furthermore, relay nodes can be deployed to extend the size of a given cell or coverage area. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 can be the same as those described above and... Figure 1 The scheduling entity 108 shown in the figure is the same as or similar to the one shown in the figure.

[0048] Figure 2 This further includes unmanned aerial vehicles (UAVs) 220, which may be drones or quadcopter helicopters. The UAV 220 can be configured to act as a base station, or more specifically, as a mobile base station. That is, in some examples, the cell need not be fixed, and the geographical area of ​​the cell can move depending on the location of a mobile base station such as the UAV 220.

[0049] Within RAN 200, a cell includes UEs capable of communicating with one or more sectors of each cell. Further, each base station 210, 212, 214, 218, and 220 can be configured to provide access to the core network 102 (see [link to core network]) for all UEs in the corresponding cell. Figure 1 Access points. For example, UEs 222 and 224 can communicate with base station 210; UEs 226 and 228 can communicate with base station 212; UEs 230 and 232 can communicate with base station 214 via RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base station (220). In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can be access points described above and Figure 1 The UE / scheduled entity 106 shown is the same as or similar to that shown. In some examples, the UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, the UAV 220 can operate within cell 202 by communicating with base station 210.

[0050] In a further aspect of RAN 200, sidelink signaling can be used between UEs without unnecessarily relying on scheduling or control information from the base station. Sidelink communication can be utilized, for example, in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using sidelink signal 227 without relaying the communication through the base station. In some examples, UEs 238, 240, and 242 can each act as a scheduling entity or a sending and / or scheduled entity or receiving sidelink device to schedule resources and transmit sidelink signal 237 therebetween, without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also transmit sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources for sidelink communication to UEs 226 and 228.

[0051] To achieve a low block error rate (BLER) while still maintaining a very high data rate over the air interface, channel decoding can be used. In short, wireless communication can utilize appropriate error-correcting block codes. In a typical block code, the information message or sequence is broken down into code blocks (CBs), and the encoder (e.g., codec) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message improves message reliability and corrects for any bit errors that may occur due to noise.

[0052] Data decoding can be implemented in several ways. In early 5G NR specifications, quasi-cyclic low-density parity-check (LDPC) was used to decode user data using two different base maps: one base map was used for large code blocks and / or high code rates, while the other base map was used for other cases. Polarity decoding was used to decode control information and the Physical Broadcast Channel (PBCH) based on nested sequences. For these channels, puncturing, shortening, and repetition were used for rate matching.

[0053] Aspects of this disclosure can be implemented using any suitable channel code. Various implementations of the base station and UE include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) for wireless communication using one or more of these channel codes.

[0054] In RAN 200, the ability of a UE to communicate while moving independently of its location is referred to as mobility. In general, this involves establishing, maintaining, and releasing various physical channels between the UE and RAN 200 under the control of the Access and Mobility Management Function (AMF). In some scenarios, the AMF includes the Security Context Management Function (SCMF) and the Security Anchor Function (SEAF) for performing authentication. The SCMF can manage the security context of both the control plane and user plane functions, either entirely or partially.

[0055] In various aspects of this disclosure, RAN 200 can utilize DL-based mobility or UL-based mobility to enable mobility and handover (i.e., the transfer of UE connectivity from one radio channel to another). In a network configured for DL-based mobility, during a call utilizing a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can initiate a handover or transfer from the serving cell to a neighboring (target) cell. For example, UE 224 can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength or quality from its serving cell 202 for a given amount of time, UE 224 can send a report message indicating this condition to its serving base station 210. In response, UE 224 can receive a handover command and the UE can undergo a handover to cell 206.

[0056] In a network for UL-based mobility configuration, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a uniform synchronization signal (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the uniform synchronization signal, derive the carrier frequency and time slot timing from the synchronization signal, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be received concurrently by two or more cells within RAN 200 (e.g., base stations 210 and 214 / 216). Each of these cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more base stations in base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. As UE 224 moves through RAN 200, RAN 200 can continue to monitor the uplink pilot signal transmitted by UE 224. If the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, RAN 200 may or may not notify UE 224 to switch from the serving cell to a neighboring cell.

[0057] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, the synchronization signals do not necessarily represent specific cells. Instead, they can identify zones of multiple cells operating on the same frequency and / or with the same timing. The use of zones in 5G networks or other next-generation communication networks enables uplink-based mobility frameworks and improves the efficiency of both the UE and the network by reducing the number of mobility messages that need to be exchanged between the UE and the network.

[0058] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by means of a license purchased from a government regulatory agency by a mobile network operator. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-approved license. While, generally speaking, access to unlicensed spectrum still requires compliance with certain technical rules, generally speaking, any operator or device can obtain access. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required for access, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee for a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-defined conditions for obtaining access).

[0059] Devices communicating in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and to provide multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM) with CP (also known as Single Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Spread Multiple Access (RSMA), or other suitable multiple access schemes. Furthermore, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes can be used to provide multiplexing for DL ​​transmission from base station 210 to UEs 222 and 224.

[0060] Devices in the radio access network 200 can also utilize one or more duplex algorithms. Full-duplex refers to a point-to-point communication link where both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Time-division duplexing (TDD) is often used to simulate half-duplex in wireless links. In TDD, time-division multiplexing is used to separate transmissions in different directions on a given channel from each other. That is, in some scenarios, the channel is dedicated to transmissions in one direction, while at other times, the channel is dedicated to transmissions in the other direction, where this direction can change very rapidly (e.g., several times per time slot). In general, full-duplex channels in wireless links rely on physical isolation between the transmitter and receiver and appropriate interference cancellation techniques. Zero-frequency division duplexing (FDD) or space-division duplexing (SDD) is also often used to simulate full-duplex in wireless links. In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, spatial division multiplexing (SDM) is used to separate transmissions in different directions on a given channel from each other. In other examples, full-duplex communication can be implemented in unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur in different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as subband full-duplex (SBFD), also known as elastic duplex or TDD FD.

[0061] Reference Figure 3 The OFDM waveforms schematically illustrated herein illustrate various aspects of this disclosure. Those skilled in the art will understand that these various aspects of this disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein. That is, although some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0062] Now for reference Figure 3 The diagram shows an unfolded view of an exemplary subframe 302 illustrating an OFDM resource grid. However, as those skilled in the art will readily recognize, the PHY transport structure for any specific application can differ from the example described herein, depending on any number of factors. Here, time is represented horizontally in units of OFDM symbols, and frequency is represented vertically in units of subcarriers of a carrier.

[0063] Resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, the corresponding multiple resource grids 304 can be available for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE, as a 1 subcarrier × 1 symbol, is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in the specific implementation, each RE can represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or simply as a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB includes 12 subcarriers (independent of the number of digital schemes used). In some examples, depending on the digital scheme, an RB includes any suitable number of consecutive OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single communication direction (transmission or reception of a given device).

[0064] A collection of contiguous or non-contiguous resource blocks may be referred to herein as a Resource Block Group (RBG), Subband, or Bandwidth Part (BWP). A collection of subbands or BWPs spans the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource units 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE generally utilizes only a subset of the resource grid 304. In some examples, an RB may be the smallest unit of resources that can be allocated to a UE. Therefore, the more RBs scheduled for a UE, and the more sophisticated the modulation scheme selected for the air interface, the higher the UE's data rate. RBs can be scheduled by a scheduling entity such as a base station (e.g., gNB, eNB, etc.), or they can be scheduled by the UE itself implementing D2D sidelink communication.

[0065] In this diagram, RB 308 is shown occupying less than the entire bandwidth of subframe 302, where some subcarriers are shown as being above and below RB 308. In a given implementation, subframe 302 has a bandwidth corresponding to any number of one or more RB 308s. Further, in this diagram, RB 308 is shown occupying less than the entire duration of subframe 302, although this is only one possible example.

[0066] Each 1ms subframe 302 includes one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, time slots can be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot includes 7 or 14 OFDM symbols with a nominal CP. Additional examples include mini-time slots with shorter durations (e.g., 1 to 3 OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). In some cases, these mini-time slots or shortened transmission time intervals (TTIs) can be transmitted, occupying resources already scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be utilized within a subframe or time slot.

[0067] An expanded diagram of time slot 310 shows a time slot 310 including a control interval 312 and a data interval 314. In summary, the control interval 312 can carry a control channel, and the data interval 314 can carry a data channel. Of course, a time slot can contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structures shown are exemplary in nature only, and different time slot structures can be utilized, including one or more control intervals or data intervals in each of the control intervals and data intervals.

[0068] Although not in Figure 3 As shown, various REs 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide the receiving device with the ability to perform channel estimation for the corresponding channels, enabling coherent demodulation / detection of the control and / or data channels within RB 308.

[0069] In some examples, time slot 310 can be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications can refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are distributed to all devices, while multicast or groupcast communications are distributed to multiple intended receiving devices. Unicast communications can refer to point-to-point transmissions from one device to a single other device.

[0070] In an example of cellular carrier-based communication via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may (e.g., within control interval 312) allocate one or more REs 306 to one or more scheduled entities (e.g., UEs) for carrying DL control information including one or more DL control channels (such as Physical Downlink Control Channel (PDCCH)). The PDCCH carries, but is not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, and downlink control information (DCI) authorizing and / or allocating REs for DL ​​and UL transmissions. The PDCCH may further carry HARQ feedback transmissions such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well known to those skilled in the art, in which the integrity of packet transmissions can be checked for accuracy at the receiving end using any suitable integrity verification mechanism (such as checksum or Cyclic Redundancy Check (CRC)). If the integrity of the transmission is acknowledged, an ACK can be sent; otherwise, a NACK can be sent. In response to NACK, the sending device can send HARQ retransmissions, which can enable append merging, incremental redundancy, and other features.

[0071] The base station can further (e.g., in control interval 312 or data interval 314) allocate one or more REs 306 for carrying other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signals (PT-RS); channel state information (CSI) reference signals (CSI-RS); and synchronization signal blocks (SSBs). SSBs can be broadcast at regular intervals based on a period (e.g., 5, 10, 20, 30, 80, or 130 ms). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE can utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0072] The PBCH in the SSB may further include a Master Information Block (MIB), which includes various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1) including various additional system information. Together, the MIB and SIB1 provide the minimum system information (SI) for initial access. Examples of system information transmitted in the MIB include, but are not limited to, subcarrier spacing (e.g., default downlink digital scheme), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell access denied indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of residual minimum system information (RMSI) transmitted in SIB1 include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit other system information (OSI).

[0073] In UL transmissions, the scheduled entity (e.g., the UE) may utilize one or more RE 306s to carry UL control information (UCI) including one or more UL control channels such as the Physical Uplink Control Channel (PUCCH) destined for the scheduling entity. UCIs include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals include Sounding Reference Signals (SRS) and Uplink DMRS. In some examples, the UCI includes a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted in the UCI, the scheduling entity may transmit Downlink Control Information (DCI), which can schedule resources for uplink packet transmissions. UCIs may also include HARQ feedback, Channel State Feedback (CSF) such as a CSI report, or any other suitable UCI.

[0074] In addition to control information, one or more REs 306 (e.g., within data interval 314) can be allocated to data services. Such data services can be carried on one or more service channels (e.g., the Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions; or the Physical Uplink Shared Channel (PUSCH) for UL transmissions). In some examples, one or more REs 306 within data interval 314 can be configured to carry other signals, such as one or more SIBs and DMRS.

[0075] In an example of sidelink communication based on a sidelink carrier via the ProSe PC5 interface, the control section 312 of time slot 310 includes a Physical Sidelink Control Channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., Rx V2X devices or other Rx UEs). The data section 314 of time slot 310 includes a Physical Sidelink Shared Channel (PSSCH), which includes sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier by the transmitting sidelink device via the SCI. Further information can be transmitted via various REs 306 within time slot 310. For example, HARQ feedback information can be transmitted from the receiving sidelink device to the transmitting sidelink device in the Physical Sidelink Feedback Channel (PSFCH) within time slot 310. Additionally, one or more reference signals, such as the sidelink SSB, sidelink CSI-RS, sidelink SRS, and / or sidelink positioning reference signal (PRS), can be transmitted within time slot 310.

[0076] In summary, the physical channels described above are multiplexed and mapped to transport channels for processing at the Media Access Control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which corresponds to the number of bits of information, can be a parameter controlled based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0077] Figure 3 The channels or carriers shown are not necessarily all of those that can be used between devices, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, can be used in addition to those shown.

[0078] In some aspects of this disclosure, the scheduling entity and / or the scheduled entity can be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4 An example of a wireless communication system 400 supporting beamforming and / or MIMO is shown. In the MIMO system, transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Therefore, there are N×M signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of transmitter 402 and receiver 406 can be implemented, for example, within a scheduling entity, a scheduled entity, or any other suitable wireless communication device.

[0079] The use of such multi-antenna techniques enables wireless communication systems to leverage the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also known as layers) on the same time-frequency resources. Data streams can be sent to a single UE to increase the data rate, or to multiple UEs to increase the overall system capacity, the latter being known as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by different weights and phase shifts) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UEs with distinct spatial signatures, enabling each UE to recover one or more data streams destined for that UE. On the uplink, each UE transmits spatially precoded data streams, allowing the base station to identify the source of each spatially precoded data stream.

[0080] The number of data streams or layers corresponds to the transmission rank. In general, the rank of a MIMO system is limited by the number of transmit or receive antennas (404 or 408, whichever is lower). Additionally, channel conditions at the UE and other considerations such as available resources at the base station can also affect the transmission rank. For example, the rank allocated to a specific UE on the downlink (and therefore, the number of data streams) can be determined based on the rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the signal-to-interference-plus-noise ratio (SINR) measured on each of the receive antennas. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI, along with resource information (e.g., available resources and the amount of data to be scheduled to the UE), to allocate transmission ranks to the UE.

[0081] In one example, such as in Figure 4 As shown, rank-2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration sends a data stream from each transmit antenna 404. Each data stream arrives at each receive antenna 408 along a different signal path 410. Receiver 406 can then reconstruct the data stream using the received signals from each receive antenna 408.

[0082] Beamforming is a signal processing technique that can be used at transmitter 402 or receiver 406 to shape or guide an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between transmitter 402 and receiver 406. Beamforming can be achieved by combining signals transmitted via antennas 404 or 408 (e.g., antenna elements of an antenna array module) such that some signals experience constructive interference while others experience destructive interference. To create the desired constructive / destructive interference, transmitter 402 or receiver 406 can apply amplitude and / or phase offsets to each transmitted or received signal from antennas 404 or 408 associated with transmitter 402 or receiver 406.

[0083] In some examples, to select a specific beam for communication with the UE, the base station can transmit reference signals such as SSBs or Channel State Information Reference Signals (CSI-RS) on each of multiple beams (SSB beams) in a beam-scanning manner. The UE can measure the Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or SINR on each of these beams and send a beam measurement report to the base station indicating the RSRP of each of the measured beams. The base station can then select a specific beam for communication with the UE based on the beam measurement report. In other examples, when the channel is reciprocal, the base station can derive a specific beam for communication with the UE based on uplink measurements of one or more uplink reference signals such as Sounding Reference Signals (SRS). To obtain access to the cell, the UE can perform a random access procedure via the Physical Random Access Channel (PRACH). The UE can identify a random access search space from SIB1 that includes PRACH resources for initiating the RACH procedure. For example, the random access procedure can begin after the UE acquires the cell and determines that the RACH opportunity (PRACH resource) has occurred after reading the SSB and SIB1. The SSB provides the Initial System Information (SI), and SIB1 (and other SIB blocks) provides the Remaining Minimum SI (RMSI). For example, the PBCH MIB of the SSB can carry the first part of the SI required by the user equipment (UE) to access the network. The SIBs (e.g., SIB1 and SIB2) can carry the RMSI required by the UE to obtain access to the network.

[0084] The RACH procedure can be executed in a variety of scenarios, such as uplink synchronization loss, lack of available PUCCH resources, scheduling request failure, and other use cases. Furthermore, the RACH procedure can be contention-based or contention-free, and includes 2-step RACH procedures (contention-based or contention-free), 3-step RACH procedures (contention-free), or 4-step RACH procedures (contention-based).

[0085] Depending on the specific application, for example Figure 1 The radio access network 104 and / or shown in the figure Figure 2 The radio protocol architecture of a radio access network such as the radio access network 200 shown can take various forms. Figure 5 An example of a radio protocol architecture for the user plane and control plane is shown in the figure.

[0086] As in Figure 5 The radio protocol architecture for the UE and base station, as shown, comprises three layers: Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). L1 is the lowest layer and implements various physical layer signal processing functions. L1 will be referred to as Physical Layer 506 in this document. L2 508 sits above Physical Layer 506 and is responsible for the link between the UE and the base station via Physical Layer 506.

[0087] In the user plane, L2 layer 508 includes a Media Access Control (MAC) layer 510, a Radio Link Control (RLC) layer 512, a Packet Data Convergence Protocol (PDCP) layer 514, and a Service Data Adaptation Protocol (SDAP) layer 516, which are terminated at the base station on the network side. Although not shown, the UE may have several upper layers above L2 layer 508, including at least one network layer (e.g., IP layer and User Data Protocol (UDP) layer) and one or more application layers, which are terminated at the User Plane Function (UPF) on the network side.

[0088] SDAP layer 516 provides the mapping between 5G Core (5GC) Quality of Service (QoS) flows and data radio bearers, and performs QoS flow ID marking in both downlink and uplink packets. PDCP layer 514 provides packet sequence numbering, in-order distribution of packets, retransmission of PDCP Protocol Data Units (PDUs), and transmission of upper-layer data packets to lower layers. PDUs include, for example, Internet Protocol (IP) packets, Ethernet frames, and other unstructured data (i.e., Machine-Type Communication (MTC), collectively referred to below as "packets"). PDCP layer 514 also provides header compression for upper-layer data packets to reduce radio transmission overhead, provides security through packet encryption, and provides integrity protection for data packets. PDCP context can indicate whether PDCP duplication is used for unicast connections.

[0089] RLC layer 512 provides segmentation and reassembly of upper-layer data packets, error correction via Automatic Repeat Request (ARQ), and sequence numbering independent of PDCP sequence numbering. The RLC context can indicate whether an acknowledgment mode (e.g., a reordering timer) or a negative acknowledgment mode is used for RLC layer 512. MAC layer 510 provides multiplexing between logical and transport channels. MAC layer 510 is also responsible for allocating various radio resources (e.g., resource blocks) and HARQ operations within a cell among UEs. The MAC context can, for example, enable HARQ feedback schemes, resource selection algorithms, carrier aggregation, beam failure recovery, or other MAC parameters for unicast connections. Physical layer 506 is responsible for transmitting and receiving data on physical channels (e.g., within time slots). The PHY context can indicate the transmission format and radio resource configuration (e.g., bandwidth portion (BWP), digital scheme, etc.) used for unicast connections.

[0090] In the control plane, the radio protocol architecture for the UE and base station is largely the same for L1 506 and L2 508, but there is no SDAP layer in the control plane, and no header compression functionality. The control plane also includes the Radio Resource Control (RRC) layer 518 in L3 and the higher Non-Access Stratum (NAS) layer 520. The RRC layer 518 is responsible for establishing and configuring the Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB) between the base station and the UE, paging initiated by 5GC or NG-RAN, and broadcasting system information related to the Access Stratum (AS) and Non-Access Stratum (NAS). The RRC layer 518 further handles QoS management, mobility management (e.g., handover, cell selection, inter-RAT mobility), UE measurement and reporting, and security functions. The NAS layer 520 terminates at the AMF in the core network and performs various functions such as authentication, registration management, and connection management.

[0091] In some examples, the scheduled entity (UE) can operate in an operating environment that supports streamlined NR devices (also referred to as "NR Lightweight"). NR Lightweight devices can be configured to have lower device complexity and reduced power consumption compared to those that can be provided by conventional NR devices, while simultaneously having higher data rates and latency requirements compared to those that can be provided, for example, for LTE Machine-Type Communication (MTC) and Narrowband Internet of Things (NB-IoT). Regarding reduced device complexity, NR Lightweight devices can be configured to support a reduced number of TX / RX antennas on the device side, reduced minimum required device bandwidth, and / or support for devices that can only operate in half-duplex (non-simultaneous TX / RX) mode in paired spectrum. Regarding reduced device power consumption, NR Lightweight devices can be configured to have reduced complexity of PDCCH monitoring achieved by reducing the number of blind decoding requirements, and extended discontinuous reception (DRX) functionality. Those skilled in the art will recognize that the examples in this disclosure are suitable for applications using NR Lightweight, although they can also be applied in conventional NR configurations.

[0092] NR lightweight devices are configured to perform a two-step or four-step RACH process in the initial bandwidth portion (BWP) or active BWP. In some examples, this disclosure discloses the use of early reporting of CSI and / or CQI during the RACH process to improve performance. Specifically, techniques and processes are disclosed for reporting CSI measurements for short / small mobile-initiated (MO) data transmissions by a scheduled entity in an RRC IDLE / INACTIVE state or an RRC connected state in discontinuous reception (DRX) mode. In some examples, the scheduled entity can remain in the RRCIDLE / INACTIVE state after completing a short data (small data) transmission, which saves power and reduces signaling complexity by reducing signaling overhead. By utilizing link adaptation, such as CSI / CQI-based reporting, such techniques can improve the coverage, power, and spectral efficiency of NR lightweight devices during transmission / reception in the initial BWP or active BWP.

[0093] As discussed above, wireless networks typically use scheduling mechanisms implemented in the MAC layer to dynamically allocate radio resources to users while taking into account their QoS requirements. The scheduler takes into account CSI and target block error rate (BLER) to allocate channel resources for transmitting buffered data. Spectral efficiency can be improved using link adaptation based on adaptive modulation and coding. The scheduler can perform per-user allocation of available time-frequency resources to multiplex transmissions. The scheduling algorithm ensures efficient use of channels and fairness in serving multiple users while meeting their QoS requirements. For 5G NR, scheduling priorities for services can be allocated within short transmission time intervals (TTIs) to meet service requirements. In the downlink, resource allocation and dynamic link adaptation can be provided immediately through DCIs transmitted in the same TTI as the data. The UE can then quickly process control information with parameters and subsequently decode the data.

[0094] However, in the uplink, it is usually performed as follows: Figure 6 The permission-based process is shown in the diagram. Figure 6 This is a signaling diagram 600 illustrating a permission-based process between UE 602 and scheduling entity 604 (e.g., gNB) according to some aspects. When data 606 arrives in the transmit buffer of UE 602, UE 602 processes the data and waits for a specific opportunity to send a scheduling request (SR) to base station 608 before sending a scheduling request in 610. Scheduling entity 605 processes the SR signal and sends a scheduling permission 612 containing the necessary allocation and transmission parameters to UE 602 via DCI. UE 602 processes control signals and finally sends data 614 to scheduling entity 604 using the permitted resources, and scheduling entity 604 processes and receives data 604. Figure 6 As seen in the diagram, the waiting time 616 is shown as the period from when data 604 is received in the buffer of UE 602 to when the scheduling entity 604 receives data 606.

[0095] Figure 7This is a signaling diagram 700 illustrating a permissionless process between UE 702 and scheduling entity 704 (e.g., gNB) according to some aspects. In this case, the scheduling entity is configured to pre-configure resource allocation and transmission parameters for UE 702 via resource configuration 706. When data 708 (e.g., a packet) arrives, the UE processes the data and aligns it with the configured resources 710, and transmits data 712 using the pre-allocated resources, i.e., without dynamic permission from scheduling entity 704. Scheduling entity 704 then receives and processes data 708 via the pre-allocated resources. This reduces control channel overhead and reliance on control signaling, which can be error-prone and cause delays. Compared to... Figure 6 As can be seen, the waiting time 714 is shorter than that of the permission-based configuration (616).

[0096] By pre-configuring UL radio resources for transmission for UE 702 under the condition that the UE has valid timing advance (TA) (or "timing adjustment"), the operational effect of providing Configurable Allowed Small Data Transmission (CG-SDT) resources (i.e., PUR) is that the use of Msg1 and Msg2, and the need to perform legacy connection establishment procedures, are not necessary. Alternatively, in various aspects of this disclosure, UE 702 can be configured to have CG-SDT resources (e.g., acquire UE-specific radio resources, the RNTI to be used, etc.) via dedicated RRC signaling while connected. In some examples, a longer TA timer is provided for UE 702 so that the TA can be reused for subsequent CG-SDT transmissions. As explained in detail below, the UE can send a signal quality measurement of the configured downlink beam, followed by a CG-SDT request, wherein, in response to its receiving CG-SDT configuration (e.g., via 706). The CG-SDT configuration may include TA verification criteria based on the signal quality measurement meeting a configured threshold. The UE authenticates the TA used for CG-SDT transmission according to one or more TA authentication criteria and performs CG-SDT configuration for communication with the wireless network (e.g., via 712). Those skilled in the art will understand that the terms "pre-configured uplink resource (PUR)" and "configured permitted small data transmission (CG-SDT) resource" as used herein should be interpreted as synonymous.

[0097] Figure 8A signal block diagram 800 is shown based on several aspects of a CG-SDT resource configuration 802. The CG-SDT resource configuration 802 includes periodic time-frequency resources 804, modulation and coding scheme (MCS) 806, transport block size (TBS) 808, PUSCH repetition count 810, start position 812, radio network temporary identifier (e.g., CG-SDT C-RNTI) 814, TA verification criteria 816, allowed CG-SDT resource skip count 818, whether the CG-SDT resource configuration is valid for one or more of the timings 820, demodulation reference signal (DMRSS) configuration 822, power control parameters 824, PDCCH search space and PDCCH configuration 826, and one or more of the number of repetitions for coverage enhancement (CE). Depending on the application, additional data may be further included in the CG-SDT resource configuration 802.

[0098] The CG-SDT resource configuration request message can be sent by the UE (e.g., 702) to the scheduling entity while in an RRC-connected state, or triggered by the network (e.g., based on subscription information and / or the identifier of a periodic service pattern) 802. Before performing CG-SDT resource transmission, the UE evaluates the validity of the TA (816) based on the use of individual or combined attributes, including whether the serving cell has changed, whether the TA timer, which is part of the CG-SDT resource configuration, has expired, and / or whether the Reference Signal Received Power (RSRP) has changed to exceed a configured threshold since the configuration time. In some examples, it is possible to configure the TA to always be valid within a given cell, which may be suitable for small cell applications. If TA verification fails, the UE can use Early Data Transmission (EDT) (if supported) or the regular connection establishment procedure (e.g., 600) as an alternative.

[0099] If the TA verification (816) passes, the CG-SDT transmission is successfully acknowledged by the scheduling entity, and the CG-SDT procedure ends after two messages (i.e., one message in the UL and one message in the DL). Acknowledgment can be provided via Layer 1 signaling in the downlink control information (DCI) or Layer 2 / 3 signaling in the RRC message. In some examples, a hybrid automatic repeat request (HARQ) can be used to acknowledge the CG-SDT transmission, and after a configured period (e.g., 4 ms) following the end of the CG-SDT transmission, the UE can monitor in the PDCCH a DCI (826) scrambled with the CG-SDT C-RNTI, including acknowledgments or possible repeat requests within a PDCCH search space window of configurable length.

[0100] The configurable period (820) of the CG-SDT resources makes them suitable for periodic services. However, the CG-SDT can also (e.g., via 818) be configured so that the UE can skip a specific number of CG-SDT moments in a transmission row (e.g., up to 8 skips), after which the CG-SDT configuration can be implicitly released. Additionally, a shared CG-SDT scheme can be used to address applications where services are less discontinuous. For example, the UE can be configured to use the CG-SDT resources irregularly in a pseudo-variable manner for transmission.

[0101] In some examples, Layer 1 acknowledgment can be used to indicate successful reception of a UL CG-SDT transmission. If there is no pending downlink data, updating the CG-SDT configuration may not be necessary, and integrity protection may not be required. The UE is configured to support integrity and replay protection for user data between the UE and network nodes. Integrity protection is part of tamper protection, which is a set of steps taken to ensure that procedures operate properly, particularly when an entity attempts to interrupt, monitor, or alter how it operates. Acknowledgment via Layer 1 signaling can be configured to allow TA adjustments and a certain number of PUSCH repetitions, as well as indications for alternatives to Early Data Transmission (EDT) or regular connection establishment procedures (e.g., 600). In other cases, responses to transmissions in a UL using CG-SDT can be provided via Layer 2 / 3 signaling (e.g., RRC messages) not only for acknowledgment but also for transmitting user data in the downlink, modifying the CG-SDT configuration, and / or moving the UE to a connected state (if needed).

[0102] The power control parameters 824 for CG-SDT can be configured differently depending on the operating environment (e.g., LTE-M, NB-IoT, etc.). For example, for LTE-M, CG-SDT transmissions can use open-loop power control because the considered period range for CG-SDT may not be suitable for using transmit power control (TPC) commands, while CG-SDT retransmissions can utilize closed-loop power control because they can be expected to be completed in the short term through dynamic retransmission scheduling. For NB-IoT, open-loop power control can be used, and the UE's transmit power interprets the path loss estimate without considering the number of repetitions.

[0103] CG-SDT transmissions can be configured as dedicated CG-SDT or shared CG-SDT. In dedicated CG-SDT, UL time-frequency resources can be exclusively used by a single UE at a time. Dedicated CG-SDT is suitable for UEs that transmit periodically in the UL (e.g., sensors and instruments) and can be used with any signal-to-interference-plus-noise ratio (SINR) regime (e.g., both CE modes A and B for LTE-M). In shared CG-SDT, the same UL time-frequency resources can be used by multiple UEs simultaneously. Overlapping transmissions can be distinguished using orthogonal DMRS sequences. This UL multi-user multiple-input multiple-output (MU-MIMO) configuration can be used for both periodic and pseudo-variable service modes.

[0104] During operation, the scheduling entity can send a CG-SDT configuration message to the UE. Upon receiving the CG-SDT configuration message, the UE sends CG-SDT data to the scheduling entity. In some examples, the scheduling entity can send the CG-SDT configuration message periodically. In other examples, the scheduling entity sends the CG-SDT configuration message irregularly, and the CG-SDT configuration message can be configured to instruct the UE to periodically send data on the CG-SDT. TA authentication is performed by the UE based on TA authentication criteria configured by the scheduling entity. To perform TA authentication, the UE measures the DL channel or reference signal as indicated in the TA authentication criteria. In some examples, if TA authentication is successful, the UE can send UL data on the CG-SDT if the time interval between the DL channel / signal used for TA authentication and the CG-SDT (UL data transmission) is less than a specified threshold. Upon receiving the UE's CG-SDT data, the scheduling entity can respond with a CG-SDT response message.

[0105] In some examples, the TA validation criteria (816) can be enhanced to provide more control and flexibility during the CG-SDT process. Figure 9 A signaling diagram 900 is shown for UE 902 and scheduling entity 904 (e.g., gNB) for using enhanced TA in the CG-SDT procedure, according to some aspects. In this example, scheduling entity 904 may receive data associated with one or more of UE capabilities 906, RRC status 908, UL coverage 910, and UE location information 912. This data may have been received from UE 902 during a previous connection (shown in dashed lines), but may also have been received from other sources and stored in the scheduling entity's memory, alternatively or additionally.

[0106] UE capability data 902 includes data associated with UE subscription information, such as communication and / or processing capabilities (e.g., low-level UE, normal UE, high-level UE). RRC status data 908 indicates UE status (e.g., active, idle, connected). UL coverage data 910 includes data indicating that the UE appears in a configured UL range in which CG-SDT operations can be performed. In one example, UL coverage data 910 may be determined by the number of PUSCH repetitions R, where the repetition level is located at R. min and R max Between, where R min and R ma This can be determined by the network. In another example, the UL coverage data 910 can be determined by the aggregated PUSCH slot count S, where the aggregated slot count is located at S. min and S max Between, among which, S min and S max It can be determined by the network.

[0107] The scheduled entity can generate additional TA verification criteria, which can be based on the use of a single or combined application of multiple characteristics, including but not limited to: changes in the serving cell and / or transmit and receive point (TRP); whether a TA timer configured for CG-SDT transmission has expired; and / or whether changes in RSRP measurements on pre-configured DL beams have exceeded pre-configured thresholds. In this example, one or more beam indices can be notified to the UE 902 signal, and one or more DL signals used for RSRP measurements and their transmit power offsets can be notified to the UE signal. Examples of such DL signals include synchronization signal / PBCH block (SSB), tracking reference signal (TRS), positioning reference signal (PRS), channel state information reference signal (CSI-RS), paging signal, wake-up signal (WUS), and demodulation reference signal (DMRS) for PBCH / paging / WUS. Alternatively or additionally, TA verification criteria can also be based on positioning information including measurements obtained from the serving cell and / or neighboring cells. Examples of location information include Time of Arrival (ToA) measurement, Angle of Arrival (AoA) measurement, Reference Signal Time Difference (RSTD), etc. By using any one or a combination of the above criteria, scheduling entity 904 generates TA verification criteria in 914 and sends TA verification 916 for CG-SDT transmission 918.

[0108] In some examples, one or more SSB beams may be associated with each Configurable Allowed (CG) configuration for CG-SDT, wherein the TA verification mechanism for CG-SDT may be based on RSRP changes of a subset of SSB beams. The subset of SSB beams may be configured as beams within the set of SSBs, and may be configured for each or all CG configurations. In some examples, the subset of SSB beams includes the active beams as indicated in SIB1 within the entire set of SSB beams, or the maximum number of SSB beams measured to derive a subset for the UE across all CG configurations. The subset of SSB beams used for RSRP-based TA verification may be determined, for example, at least based on a configured absolute RSRP threshold.

[0109] For RRC inactive / idle UEs, DL signals 916 (e.g., SSB, TRS, PRS) used for TA authentication can be scheduled periodically and in conjunction with WUS / paging signals. In some examples, the measurement interval of UE 902 can be configured to overlap or partially overlap with signaling from WUS / paging / DRX-ON time periods. The period of UE 902 for CG-SDT transmission can also be configured to coincide with the DRX period of UE 902. In some examples, the search space and PDCCH configuration of UE 902 for CG-SDT responses from scheduling entity 904 can also be configured to overlap or partially overlap with signaling from WUS / paging / DRX-ON time periods. The time interval used between the DL signals used for TA authentication and the CG-SDT signals can also be configured to be less than a specified threshold (e.g., 160ms) so that UE 902 meets the UL initial transmission timing error requirement when transmitting CG-SDT.

[0110] CG-SDT configuration can be triggered by a UE or a scheduling entity (gNB), and the timing of CG-SDT for multiple UEs can overlap completely or partially. For two or more UEs, each UE can share the time / frequency resources used for CG-SDT transmission. UEs with the same capabilities, coverage enhancements, and / or UL service modes can be grouped and assigned to share CG-SDT. CG-SDT configuration can be sent by the scheduling entity via RRC signaling or a MAC control element (MAC CE).

[0111] Figure 10 This is a block diagram illustrating an example of the hardware implementation of a UE (Scheduled Entity) 1000 using the processing system 1014, according to some aspects. For example, the scheduled entity 1000 may be as shown in... Figure 1 , 2 User equipment (UE) shown in any one or more of the figures 6, 7 and / or 9.

[0112] The scheduled entity 1000 may be implemented using a processing system 1014 (or "processing device") including one or more processors 1004. Examples of processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, the scheduled entity 1000 may be configured to perform any one or more of the functions described herein, including but not limited to NR and NR lightweight communication including RACH procedures and / or CSI / CQI reporting as described above. That is, the processor 1004 used in the scheduled entity 1000 may be used to implement any one or more programs and procedures described herein.

[0113] In this example, processing system 1014 can be implemented using a bus architecture generally represented by bus 1002. Depending on the specific application and overall design constraints of processing system 1014, bus 1002 includes any number of interconnected buses and bridges. Bus 1002 communicatively couples together various circuits including one or more processors (generally represented by processor 1004), memory 1005, and computer-readable media (generally represented by computer-readable media 1006). Bus 1002 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1008 provides an interface between bus 1002 and transceiver 1010. Transceiver 1010 provides a communication interface or unit for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1012 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1012 is optional and can be omitted in some examples.

[0114] Processor 1004 is responsible for managing and general processing of bus 1002, including executing software stored on computer-readable medium 1006. When executed by processor 1004, the software causes processing system 1014 to perform the various functions described below for any specific device. Computer-readable medium 1006 and memory 1005 may also be used to store data manipulated by processor 1004 during software execution.

[0115] One or more processors 1004 in the processing system can execute software. Software should be broadly interpreted as representing instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description languages, or something else. Software may reside on a computer-readable medium 1006. The computer-readable medium 1006 may be a non-transitory computer-readable medium. As examples, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., compact discs (CDs) or digital versatile optical discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1006 may reside in processing system 1014, be located outside processing system 1014, or be distributed among multiple entities including processing system 1014. Computer-readable medium 1006 may be embodied in a computer program product. As an example, a computer program product includes a computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure is best implemented depending on the specific application and the overall design constraints imposed on the overall system.

[0116] In some aspects of this disclosure, processor 1004 includes circuitry configured for various functions. For example, processor 1004 includes communication and processing circuitry 1020 configured to communicate with RAN nodes (e.g., base stations such as gNBs). In some examples, communication and processing circuitry 1020 includes one or more hardware components providing units and physical structures for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission).

[0117] The communication and processing circuitry 1020 can acquire information from components of the scheduled entity 1000 (e.g., from a transceiver 1010 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process the information (e.g., decode it), and output the processed information. For example, the communication and processing circuitry 1020 can output information to another component of the processor 1004, to the memory 1005, or to the bus interface 1008. In some examples, the communication and processing circuitry 1020 can receive one or more, or any combination thereof, signals, messages, and other information. In some examples, the communication and processing circuitry 1020 can receive information via one or more channels. In some examples, the communication and processing circuitry 1020 includes functions for a unit used for receiving information.

[0118] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1020 may (e.g., from another component of processor 1004, memory 1005, or bus interface 1008) acquire information, process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1020 may output information to transceiver 1010 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1020 may transmit one or more, or any combination thereof, signals, messages, or other information. In some examples, communication and processing circuitry 1020 may transmit information via one or more channels. In some examples, communication and processing circuitry 1020 includes functionality for a unit for transmitting (e.g., a unit for transmitting).

[0119] In some examples, the communication and processing circuitry 1020 may be configured to receive and process downlink beamforming signals at mm-wave frequencies or sub-6 GHz frequencies via transceiver 1010. For example, the communication and processing circuitry 1020 may be configured to receive a corresponding reference signal on each of a plurality of downlink beams from a RAN node during beam scanning. The communication and processing circuitry 1020 may be further configured to receive paging messages from the RAN node. The communication and processing circuitry 1020 may be further configured to execute communication and processing software 1024 stored in computer-readable medium 1006 to implement one or more of the functions described herein.

[0120] Processor 1004 may further include CG-SDT circuitry 1022, which is configured to process CG-SDT signaling and TA verification from the scheduling entity to achieve the above-described combination. Figure 7-9The described unpermitted processing and procedures. CG-SDT circuit 1022 may be further configured to execute CG-SDT software 1026 stored in computer-readable medium 1006 to provide units for implementing one or more of the functions described herein.

[0121] Of course, in the example above, the circuitry included in processor 1014 is provided merely as an example, and other units for implementing the described functions may be included in various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 1006 or any other... Figure 1-2 Suitable means or units described in any of the figures in 4 and utilizing, for example, the processes and / or algorithms described herein.

[0122] Figure 11 This is a block diagram illustrating an example hardware implementation of a scheduling entity 1100 using a processing system according to some aspects. The scheduling entity 1100 is shown using processing system 1114. For example, the scheduling entity 1100 may be as shown in... Figure 1 and 2 Any one or more of the base stations (such as eNB, gNB) or other scheduling entities shown in the figures.

[0123] Scheduling entity 1100 can utilize the combination above. Figure 11 The processing system 1114 discussed is implemented similarly to the processing system 1114 and includes one or more processors 1104 that can be used to implement any one or more programs and processes described herein. In this example, the processing system 1114 can be implemented using a bus architecture generally represented by bus 1102. Depending on the specific application and overall design constraints of the processing system 1114, bus 1102 includes any number of interconnected buses and bridges. Bus 1102 communicatively couples together various circuits including one or more processors (generally represented by processor 1104), memory 1105, and computer-readable media (generally represented by computer-readable media 1106). Bus 1102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1108 provides an interface between bus 1102 and transceiver 1110. Transceiver 1110 provides a communication interface or unit for communicating with various other devices via a transmission medium (such as air). Depending on the nature of the device, a user interface 1112 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1112 is optional and may be omitted in some examples.

[0124] Processor 1104 is responsible for managing and general processing of bus 1102, including executing software stored on computer-readable medium 1106 or memory 1105. When executed by processor 1104, the software causes processing system 1114 to perform the various functions described herein for any specific device. Computer-readable medium 1106 and memory 1105 may also be used to store data manipulated by processor 1104 during software execution. One or more processors 1104 in the processing system can execute software. Software should be broadly interpreted as representing instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or anything else. Software may reside on computer-readable medium 1106, which may be connected to... Figure 10 Similar to the computer-readable medium 1106 described herein.

[0125] In some aspects of this disclosure, processor 1104 includes communication and processing circuitry 1120. Communication and processing circuitry 1120 can be configured to communicate with a UE. Communication and processing circuitry 1120 includes one or more hardware components providing a physical structure for performing various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry 1120 may further include one or more hardware components providing a physical structure for performing various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. Communication and processing circuitry 1120 may be further configured to execute software 1124 included in computer-readable medium 1106 to implement one or more of the functions described herein.

[0126] In some examples, the communication and processing circuitry 1120 may be configured to receive and process uplink beamforming signals at mm-wave frequencies or sub-6 GHz frequencies via transceiver 1110. For example, the communication and processing circuitry 1120 may be configured to receive a corresponding reference signal (e.g., SRS or DMRS) on each of a plurality of uplink beams from the UE during uplink beam scanning. In some examples, the communication and processing circuitry 1120 may be further configured to generate and transmit downlink beamforming signals at mm-wave frequencies or sub-6 GHz frequencies via transceiver 1110. For example, the communication and processing circuitry 1120 may be configured to transmit a corresponding downlink reference signal (e.g., SSB or CSI-RS) on each of a plurality of downlink beams destined for the UE during downlink beam scanning.

[0127] The communication and processing circuitry 1120 may be further configured to receive requests from the UE. For example, the request may be included in a MAC-CE carried in the PUSCH, a PUCCH, or a UCI, random access message, RRC, and / or CG-SDT configuration request message carried in the PUSCH. The communication and processing circuitry 1120 may be further configured to receive from the UE a scheduling request for uplink permission on a PUSCH carrying a MAC-CE (e.g., via a UCI in the PUCCH). The communication and processing circuitry 1120 may be further configured to receive uplink signals on one or more uplink receive beams via one or more uplink transmit beams applied to the uplink signals. For example, the communication and processing circuitry 1120 may be configured to receive uplink signals on one or more uplink receive beams. Uplink signals may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH.

[0128] The communication and processing circuitry 1120 may be further configured to generate multiple downlink transmit beams during downlink beam scanning. In some implementations where communication involves receiving information, the communication and processing circuitry 1120 may acquire information from a component of the scheduling entity 1100 (e.g., from a transceiver 1110 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process the information (e.g., decode it), and output the processed information. For example, the communication and processing circuitry 1120 may output information to another component of the processor 1104, to a memory 1105, or to a bus interface 1108. In some examples, the communication and processing circuitry 1120 may receive one or more, or any combination thereof, signals, messages, and other information. In some examples, the communication and processing circuitry 1120 may receive information via one or more channels. In some examples, the communication and processing circuitry 1120 includes functions for a unit used for receiving.

[0129] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1120 may (e.g., from another component of processor 1104, memory 1105, or bus interface 1108) acquire information, process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1120 may output information to transceiver 1110 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1120 may transmit one or more, or any combination thereof, signals, messages, or other information. In some examples, communication and processing circuitry 1120 may transmit information via one or more channels. In some examples, communication and processing circuitry 1120 includes functions for a unit used for transmission (e.g., a unit used for transmission).

[0130] Processor 1104 may further include CG-SDT circuitry 1122, which can operate in conjunction with communication and processing circuitry 1120 to configure CG-SDT transmission including TA verification. CG-SDT circuitry 1122 may be further configured to execute CG-SDT software 1126 stored in computer-readable medium 1106 to provide elements for implementing one or more of the functions described herein. In some examples, CG-SDT circuitry 1122, alone or in conjunction with communication and processing circuitry 1120, may be configured to perform the following actions: receiving a Configuration-Allowed Small Data Transmission (CG-SDT) configuration request from a user equipment (UE), and, in response to receiving the CG-SDT configuration request, sending CG-SDT configuration to the UE, the CG-SDT configuration including a timing advance (TA) verification criterion based on downlink signal quality measurements satisfying a configured threshold.

[0131] Of course, in the example above, the circuitry included in processor 1114 is provided merely as an example, and other units for implementing the described functions may be included in various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 1106 or any other... Figure 1-2 Suitable means or units are described in any of the figures 4, 6-7 and 9 and use, for example, the processes and / or algorithms described herein.

[0132] Figure 12This is a flowchart illustrating an exemplary process 1200 for a scheduling entity to implement a CG-SDT process with enhanced TA verification, according to some aspects. As described below, some or all of the features shown may be omitted in specific implementations within the scope of this disclosure, and some of the shown features may not be necessary for all examples. In some examples, process 1200 may be implemented by a scheduling entity (e.g., 1100). In some examples, process 1200 may be implemented by any suitable means or unit for implementing the functionality or algorithm described below.

[0133] In block 1202, the scheduling entity can generate a CG-SDT configuration that includes one or more timing advance (TA) verification criteria based on user equipment (UE) capabilities, UE radio resource control (RRC) status, and / or UE uplink coverage enhancement range (e.g., 906-912). For example, combined with Figure 11 The CG-SDT circuit 1122 shown and described can provide elements for generating the CG-SDT configuration. In some examples, UE capabilities include subscription information such as whether it is a low-level UE, a normal UE, or a high-level UE subscription information. In some examples, the RRC state includes one of an inactive state, an idle state, and a connected state. For either an inactive state or an idle state, sending the CG-SDT configuration includes sending the CG-SDT together with one of a periodic scheduling and wake-up signal (WUS), a paging signal, or a discontinuous reception on (DRX-ON) signal.

[0134] In some examples, transmitting CG-SDT configurations includes transmitting measurement gap configurations that at least partially overlap with WUS, paging signal, or DRX-ON time periods. Periodic scheduling includes DRX cycles configured in conjunction with CG-SDT transmission cycles. Search space configurations and PDCCH configurations that at least partially overlap with WUS, paging signal, or DRX-ON time periods can also be transmitted.

[0135] In some examples, the UE uplink coverage enhancement range includes multiple PUSCH repetition levels, and the UE uplink coverage enhancement range includes multiple aggregated PUSCH slots. TA verification criteria may also include changes in the detection of the serving cell or Transmit and Receive Point (TRP), TA timer configuration, changes in RSRP measurements on pre-configured downlink beams exceeding one or more thresholds, and one or more of the location information.

[0136] In some examples, sending CG-SDT configuration to the UE includes sending CG-SDT configuration parameters for the UE, a downlink reference signal or channel used by the UE for TA authentication, and TA authentication criteria for the UE, wherein the time gap between the downlink reference signal or channel used by the UE for TA authentication and the PUR transmission from the UE is less than a configured threshold.

[0137] In some examples, transmitting CG-SDT configuration includes sending common CG-SDT configuration information to multiple User Equipments (UEs). Common CG-SDT configuration information can be transmitted on shared radio resources in the time or frequency domain using one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams. CG-SDT configuration can be transmitted via a single Radio Resource Control (RRC) signaling or a MAC Control Element (MAC CE).

[0138] In some examples, the CG-SDT configuration includes one or more of the following: (i) TA verification criteria, (ii) periodic allocation of time-frequency resources for the Physical Uplink Shared Channel (PUSCH), (iii) the modulation and coding scheme (MCS) 806 and transport block size (TBS) of the PUSCH, (iv) the number and repeating pattern of PUSCH per CG-SDT timing, (v) demodulation reference signal (DMRS) configuration, (vi) CG-SDT Radio Network Temporary Identifier (C-RNTI), (vii) power control parameters, (viii) the allowed number of CG-SDT skips, and / or (ix) the Physical Downlink Control Channel (PDCCH) search space and PDCCH configuration for CG-SDT responses.

[0139] In block 1204, the scheduling entity can receive a CG-SDT configuration request from the UE, wherein, based on the TA verification criteria, the scheduling entity sends a CG-SDT in response to receiving the CG-SDT configuration request in block 1206. For example, combined with Figure 11 The communication and processing circuitry 1120 and the CG-SDT circuitry 1122 shown and described can provide units for transmitting CG-SDT configurations.

[0140] Figure 13This is a flowchart illustrating an exemplary process 1300 for a UE to implement a CG-SDT process with enhanced TA verification, according to some aspects. As described below, some or all of the features shown may be omitted in specific implementations within the scope of this disclosure, and some of the shown features may not be necessary for all examples. In some examples, process 1300 may be implemented by a scheduled entity (e.g., 1000). In some examples, process 1300 may be implemented by any suitable means or unit for implementing the functions or algorithms described below.

[0141] In block 1302, the UE can send a pre-configured uplink resource (CG-SDT) request. For example, combined with Figure 10 The communication and processing circuit 1020 shown and described can provide a unit for sending CG-SDT requests.

[0142] In block 1304, the UE may receive a CG-SDT configuration including one or more timing advance (TA) verification criteria based on user equipment (UE) capabilities, UE radio resource control (RRC) status, and / or UE uplink coverage enhancement range (e.g., 906-912). In block 1306, the UE verifies the CG-SDT according to one or more TA verification criteria and performs the CG-SDT. For example, combined with Figure 10 The communication and processing circuitry 1020 shown and described may provide a unit for receiving CG-SDT configuration, and the CG-SDT circuitry 1022 may provide a unit for verifying and executing CG-SDT.

[0143] In some examples, UE capabilities include subscription information, which may include subscription information for a low-level UE, a normal UE, or a high-level UE. In some examples, RRC states may include an inactive state, an idle state, or a connected state. For an inactive or idle state, receiving CG-SDT includes receiving CG-SDT together with a periodic scheduling and a wake-up signal (WUS), a paging signal, or a discontinuous reception-on (DRX-ON) signal. Receiving CG-SDT may also include receiving a measurement gap configuration that at least partially overlaps with the WUS, paging signal, or DRX-ON time period. Periodic scheduling includes DRX cycling. In some examples, receiving CG-SDT may also include receiving a search space configuration and a PDCCH configuration that at least partially overlap with the WUS, paging signal, or DRX-ON time period.

[0144] In some examples, the UE uplink coverage enhancement range includes multiple PUSCH repetition levels and multiple aggregated PUSCH slots. TA verification criteria include changes in the detection of the serving cell or Transmit and Receive Point (TRP), TA timer configuration, changes in RSRP measurements on pre-configured downlink beams exceeding one or more thresholds, and one or more of the location information.

[0145] Receiving a CG-SDT includes receiving a CG-SDT and a TA authentication on a downlink signal, wherein the time gap between the CG-SDT and the TA authentication is less than a configured threshold. In some examples, receiving a CG-SDT includes receiving a CG-SDT on shared transport resources. Receiving a CG-SDT also includes receiving a CG-SDT via a Radio Resource Control (RRC) signaling or a MAC Control Element (MAC CE).

[0146] Figure 14 This is a flowchart illustrating an exemplary process 1400 for a scheduling entity to implement a CG-SDT process with enhanced TA verification, according to some aspects. As described below, some or all of the features shown may be omitted in specific implementations within the scope of this disclosure, and some of the shown features may not be necessary for all examples. In some examples, process 1400 may be implemented by a scheduling entity (e.g., 1100). In some examples, process 1400 may be implemented by any suitable means or unit for implementing the functionality or algorithm described below.

[0147] In block 1402, the scheduling entity receives a Configuration-Allowed Small Data Transmission (CG-SDT) configuration request from the user equipment (UE). For example, in conjunction with Figure 11 The CG-SDT circuit 1122 shown and described can provide a unit for receiving CG-SDT configuration requests.

[0148] In block 1404, the scheduling entity, in response to receiving a CG-SDT configuration request, sends CG-SDT configuration to the UE. The CG-SDT configuration includes timing advance (TA) verification criteria based on downlink signal quality measurements meeting a configured threshold. For example, combined with... Figure 11The CG-SDT circuitry 1122 and communication and processing circuitry 1120 shown and described can provide a CG-SDT configuration for transmitting downlink signal quality information that meets configured thresholds. In some examples, the configured thresholds include one or more thresholds for received power (RSRP) measurements or changes in RSRP measurements. In some examples, the TA verification criteria are further based on one or more of the following: at least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index of each of the at least one downlink reference signal, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset of each of the at least one downlink reference signal, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes in the detection of the serving cell or transmit and receive point (TRP), and TA timer configuration.

[0149] In some examples, the UE RRC state includes one of an inactive state, an idle state, and a connected state. For either the inactive or idle state, the CG-SDT transmission configuration includes transmitting the CG-SDT together with one of the periodic scheduling and wake-up signal (WUS), paging signal, or discontinuous receive-on (DRX-ON) signal. The CG-SDT configuration includes a measurement gap configuration that at least partially overlaps with the WUS, paging signal, or DRX-ON time period. The periodic scheduling includes a DRX cycle configured in conjunction with the CG-SDT transmission period. The CG-SDT configuration includes a search space configuration and a PDCCH configuration that at least partially overlap with the WUS, paging signal, or DRX-ON time period. In some examples, the UE uplink coverage enhancement range includes multiple PUSCH repetition levels or multiple aggregated PUSCH time slots.

[0150] In some examples, the CG-SDT configuration includes: CG-SDT configuration parameters for the UE, a downlink reference signal or channel used by the UE for TA authentication, and TA authentication criteria for the UE, wherein the time gap between the downlink reference signal or channel used by the UE for TA authentication and the CG-SDT transmission from the UE is less than a configured time threshold (e.g., the time gap threshold between the DL channel / signal used for TA authentication and the CG-SDT UL data transmission).

[0151] In some examples, CG-SDT configuration can be sent as public CG-SDT configuration information to multiple user equipments (UEs), and sending CG-SDT configuration includes: sending public CG-SDT configuration information on shared radio resources in the time or frequency domain using one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams.

[0152] Figure 15 This is a flowchart illustrating an exemplary process 1500 for a UE to implement a CG-SDT process with enhanced TA verification, according to some aspects. As described below, some or all of the features shown may be omitted in specific implementations within the scope of this disclosure, and some of the shown features may not be necessary for all examples. In some examples, process 1500 may be implemented by a scheduled entity (e.g., 1000). In some examples, process 1500 may be implemented by any suitable means or unit for implementing the functions or algorithms described below.

[0153] In block 1502, the UE transmits signal quality measurements for the configured downlink beam. For example, combined with Figure 10 The communication and processing circuitry 1020 and CG-SDT circuitry 1022 shown and described are units that can provide signal quality information for transmitting downlink beams configured. In some examples, signal quality measurements include received power (RSRP) measurements or variations in RSRP measurements. In some examples, signal quality measurements may include additional information for use in TA verification criteria, including at least one of the following: a downlink signal quality measurement configuration including one or more downlink reference signals, at least one downlink signal quality measurement configuration, a beam index of a downlink reference signal, location information obtained from the serving cell or neighboring cells, a transmit power offset of the downlink reference signal and UE capabilities, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes in the detection of the serving cell or transmit and receive point (TRP), TA timer configuration, and location information.

[0154] In block 1504, the UE sends a Configured Allowed Small Data Transmission (CG-SDT) request. For example, in conjunction with Figure 10 The communication and processing circuit 1020 shown and described can provide a unit for sending CG-SDT requests.

[0155] In block 1506, the UE receives a CG-SDT configuration including a timing advance (TA) verification criterion based on signal quality measurements satisfying a configured threshold. For example, combined with Figure 10The communication and processing circuitry 1020 shown and described can provide a unit for receiving CG-SDT configuration.

[0156] In some examples, the configured thresholds include one or more thresholds for received power (RSRP) measurements or changes in RSRP measurements, and the TA verification criteria may also include at least one of the following: downlink signal quality measurement configurations for one or more downlink reference signals, at least one downlink signal quality measurement configuration, beam index of the downlink reference signal, location information obtained from the serving cell or neighboring cells, transmit power offset of the downlink reference signal and UE capabilities, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes in the detection of the serving cell or transmit and receive point (TRP), TA timer configuration, and location information.

[0157] In some examples, CG-SDT configuration and TA authentication are received via downlink signaling, and the time gap between CG-SDT and TA authentication is less than a configured threshold. In some examples, CG-SDT configuration is received as public CG-SDT configuration information on shared radio resources in the time or frequency domain using one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams.

[0158] In block 1508, the UE verifies the CG-SDT configuration according to one or more TA authentication criteria in the TA authentication criteria. In block 1510, the UE performs CG-SDT configuration for small data communication with the wireless network. For example, combined with Figure 10 The CG-SDT circuit 1022 shown and described can provide a unit for verifying and executing the CG-SDT configuration.

[0159] The following provides an overview of examples of the contents of this disclosure.

[0160] Example 1: A scheduling entity within a wireless communication network includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform the following operations: receive a Configuration-Allowed Small Data Transmission (CG-SDT) configuration request from a user equipment (UE); and in response to receiving the CG-SDT configuration request, send a CG-SDT configuration to the UE, the CG-SDT configuration including a timing advance (TA) verification criterion based on downlink signal quality measurements satisfying a configured threshold.

[0161] Example 2: The scheduling entity described in Example 1, wherein the configured thresholds include one or more thresholds for changes in received power (RSRP) measurements or RSRP measurements.

[0162] Example 3: The scheduling entity described in Example 1 and / or 2, wherein the TA verification criteria are based on one or more of the following: at least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index of each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the downlink signal quality measurement of each of the at least one downlink reference signals, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes in the detection of the serving cell or transmit and receive point (TRP), or TA timer configuration.

[0163] Example 4: The scheduling entity described in any one of Examples 1 through 3, wherein the UE RRC state includes one of an inactive state, an idle state, and a connected state.

[0164] Example 5: The scheduling entity of any one of Examples 1 through 4, wherein, for one of the inactive state or the idle state, the processor and the memory are configured to perform the following operations: transmit the CG-SDT configuration via one of Radio Resource Control (RRC) signaling or Media Access Control (MAC) control element (MAC CE), and transmit one or more downlink reference signals for TA verification of the CG-SDT together with one of the wake-up signal (WUS) or paging signal during a discontinuous reception (DRX) period according to periodic scheduling.

[0165] Example 6: The scheduling entity of any one of Examples 1 through 5, wherein the processor and the memory are configured to transmit the one or more downlink reference signals within a measurement gap that at least partially overlaps with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

[0166] Example 7: The scheduling entity of any one of Examples 1 through 6, wherein the periodic scheduling for CG-SDT transmission is configured in conjunction with a DRX cycle, and the period of the CG-SDT transmission is configured to be proportional to the period of the DRX cycle.

[0167] Example 8: The scheduling entity of any one of Examples 1 through 7, wherein the processor and the memory are configured to transmit the CG-SDT configuration by transmitting a search space configuration and a PDCCH configuration that at least partially overlap with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

[0168] Example 9: The scheduling entity of any one of Examples 1 through 8, wherein the UE uplink coverage enhancement includes: multiple PUSCH repetition levels, multiple aggregated PUSCH slots, or a PUSCH repetition mode including at least frequency hopping, redundant version cycling, and DMRS configuration.

[0169] Example 10: The scheduling entity of any one of Examples 1 through 9, wherein the processor and the memory are configured to send the CG-SDT configuration to the UE by sending CG-SDT configuration parameters for the UE, a downlink reference signal or channel used by the UE for TA authentication, and the TA authentication criteria for the UE, and wherein the time gap between the downlink reference signal or channel used by the UE for TA authentication and the CG-SDT transmission from the UE is not less than a configured time threshold.

[0170] Example 11: The scheduling entity of any one of Examples 1 through 10, wherein the processor and the memory are configured to transmit the CG-SDT configuration by sending common or individual CG-SDT configuration information to a plurality of user equipments (UEs), and wherein the processor and the memory are configured to transmit the CG-SDT configuration information by sending the common or individual CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domain using one or more beams having a quasi-co-location (QCL) relationship with other DL broadcast beams.

[0171] Example 12: A wireless communication method for a scheduling entity in a wireless communication network, comprising: receiving a Configuration Allowed Small Data Transmission (CG-SDT) configuration request from a user equipment (UE); and in response to receiving the CG-SDT configuration request, sending a CG-SDT configuration to the UE including the TA verification criteria, the CG-SDT configuration including a timing advance (TA) verification criterion based on one or more downlink signal quality measurements satisfying a configured threshold.

[0172] Example 13: The method described in Example 12, wherein the downlink signal quality measurement includes a reference signal received power (RSRP) measurement or a change in the RSRP measurement.

[0173] Example 14: The method described in Examples 12 and / or 13, wherein the TA verification criteria are based on one or more of the following: at least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index of each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the downlink signal quality measurement of each of the at least one downlink reference signals, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes in the detection of the serving cell or transmit and receive point (TRP), or TA timer configuration.

[0174] Example 15: The method of any one of Examples 12 to 14, wherein the UE RRC state includes one of an inactive state, an idle state, and a connected state.

[0175] Example 16: The method of any one of Examples 12 to 15, wherein, for one of the inactive state or the idle state, transmitting the CG-SDT configuration includes: transmitting the CG-SDT configuration via one of Radio Resource Control (RRC) signaling or MAC Control Element (MAC CE), and transmitting a downlink reference signal for TA verification of the CG-SDT together with one of a Wake-up Signal (WUS) or a Paging Signal during a periodicly scheduled discontinuous reception (DRX) period.

[0176] Example 17: The method of any one of Examples 12 to 16, wherein transmitting the CG-SDT configuration further includes transmitting the downlink reference signal within a measurement gap configuration that at least partially overlaps with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

[0177] Example 18: The method of any one of Examples 12 to 17, wherein the periodic scheduling is configured in conjunction with the DRX cycle, and the period of the CG-SDT configuration transmission is configured to be proportional to the period of the DRX cycle.

[0178] Example 19: The method of any one of Examples 12 to 18, wherein sending the CG-SDT configuration further includes sending a search space configuration and a PDCCH configuration that at least partially overlap with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

[0179] Example 20: The method of any one of Examples 12 to 19, wherein the scope of the UE uplink coverage enhancement includes: multiple PUSCH repetition levels or multiple aggregated PUSCH slots or a PUSCH repetition mode including at least frequency hopping, redundant version cycling and DMRS configuration.

[0180] Example 21: The method of any one of Examples 12 to 20, wherein sending the CG-SDT configuration to the UE includes sending CG-SDT configuration parameters for the UE, a downlink reference signal or channel used by the UE for TA authentication, and the TA authentication criteria for the UE, and wherein the time gap between the downlink reference signal or channel used by the UE for TA authentication and the CG-SDT transmission from the UE is less than a configured time threshold.

[0181] Example 22: The method of any one of Examples 12 to 21, wherein transmitting the CG-SDT configuration includes: transmitting common or individual CG-SDT configuration information to a plurality of user equipments (UEs), and wherein transmitting the CG-SDT configuration includes: transmitting the common or individual CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domain using one or more beams having a quasi-co-location (QCL) relationship with other DL broadcast beams.

[0182] Example 23: A user equipment (UE) within a wireless communication network includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to perform the following operations: transmit signal quality information configured for downlink beams; transmit a configured permitted small data transmission (CG-SDT) request; receive a CG-SDT configuration including a timing advance (TA) verification criterion based on the signal quality measurement satisfying a configured threshold; verify the TA for CG-SDT transmission according to the TA verification criterion; and perform the CG-SDT configuration for communication with the wireless communication network.

[0183] Example 24: The UE described in Example 23, wherein the signal quality measurement includes a Reference Signal Received Power (RSRP) measurement or a change in the RSRP measurement, and wherein the TA verification criterion is based on at least one of the following: at least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index of each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the signal quality measurement of each of the at least one downlink reference signals, UE capability, UE Radio Resource Control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, a change in the detection of the serving cell or Transmit and Receive Point (TRP), or a TA timer configuration.

[0184] Example 25: The UE described in Examples 23 and / or 24, wherein the processor and the memory are configured to perform the TA verification based on the TA verification criteria configured for CG-SDT transmission, and to perform the CG-SDT configuration based on the result of the TA verification, and wherein the time gap between the CG-SDT transmission and the TA verification is not less than a configured threshold.

[0185] Example 26: UE of any one of Examples 23 to 25, wherein the processor and the memory are configured to receive the CG-SDT configuration by receiving public or separate CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domain using one or more beams having a quasi-co-location (QCL) relationship with other DL broadcast beams.

[0186] Example 27: A wireless communication method for a user equipment (UE) in a wireless communication network, the method comprising: transmitting a signal quality measurement of a configured downlink beam; transmitting a configured permitted small data transmission (CG-SDT) request; receiving a CG-SDT configuration including a timing advance (TA) verification criterion based on the signal quality measurement satisfying a configured threshold; verifying the TA for the CG-SDT configuration according to one or more of the TA verification criteria; and performing the CG-SDT configuration for communication with the wireless communication network.

[0187] Example 28: The method of Example 27, wherein the signal quality measurement includes a Reference Signal Received Power (RSRP) measurement or a change in the RSRP measurement, and wherein the TA verification criterion is based on at least one of the following: at least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index of each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the signal quality measurement of each of the at least one downlink reference signals, UE capability, UE Radio Resource Control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, a change in the detection of the serving cell or Transmit and Receive Point (TRP), or a TA timer configuration.

[0188] Example 29: The method described in Examples 27 and / or 28, wherein the TA verification is based on the TA verification criteria configured for the CG-SDT configuration transmission, and the CG-SDT configuration is performed based on the result of the TA verification, and wherein the time interval between the CG-SDT transmission and the TA verification is not less than or equal to a configured threshold.

[0189] Example 30: The method of any one of Examples 27 to 29, wherein receiving the CG-SDT configuration comprises: receiving public or individual CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domain using one or more beams having a quasi-co-location (QCL) relationship with other DL broadcast beams.

[0190] Several aspects of wireless communication networks have been given with reference to exemplary implementations. Those skilled in the art will recognize that the various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards.

[0191] As examples, various aspects can be implemented within other systems defined by 3GPP, such as LTE, Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2 (such as CDMA2000 and / or Evolved Data Optimized (EV-DO)). Other examples can be implemented within systems using IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards used will depend on the specific application and the overall design constraints imposed on the system.

[0192] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or more advantageous than other aspects of this disclosure. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to direct or indirect coupling between two objects. For example, if object A is physically in contact with object B, and object B is in contact with object C, then objects A and C can still be considered coupled to each other—even if they are not physically in direct contact with each other. For example, even if the first object never physically contacts the second object, the first object can be coupled to the second object. The terms “circuit” and “circuitry” are used broadly and are intended to include both the hardware implementation of electrical devices and conductors that enable the performance of the functions described in this disclosure when connected and configured (without limitation on the type of electronic circuit) and the software implementation of information and instructions that enable the performance of the functions described in this disclosure when executed by a processor.

[0193] Figure 1-15 One or more of the components, steps, features, and / or functions shown herein may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2The apparatuses, devices, and / or components shown in 4, 7, 9, 10, and 11 can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0194] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of the exemplary process. It should be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design conventions. The appended method claims provide elements of various steps in the order specified in the examples, and are not limited to the given specific order or hierarchy unless specifically detailed therein.

[0195] The preceding description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but will conform to the full scope consistent with the language of the claims, wherein, unless specifically indicated otherwise, references to elements in the singular are not intended to mean “one and only one,” but rather “one or more.” Unless specifically indicated otherwise, the term “some” means one or more. The phrase “at least one of” referring to a list of items means any combination of those items including a single member. As an example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known to those skilled in the art or will become known later are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, nothing disclosed herein is intended to be exclusive of disclosure, whether or not such disclosure is expressly detailed in the claims.

Claims

1. A scheduling entity within a wireless communication network, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, wherein the one or more processors are configured to perform the following operations: Send a Configurable Allowed Small Data Transmission (CG-SDT) configuration to the User Equipment (UE), the CG-SDT configuration including a timing advance (TA) verification criterion, the TA verification criterion indicating that TA verification prior to CG-SDT transmission is based on at least one downlink signal quality measurement satisfying at least one threshold; According to periodic scheduling, during discontinuous reception (DRX) periods, one or more downlink reference signals for TA authentication are transmitted together with either a wake-up signal (WUS) or a paging signal; and Communication is received from the UE based on the CG-SDT configuration.

2. The scheduling entity according to claim 1, wherein, The downlink signal quality measurement includes a reference signal received power (RSRP) measurement or a change in the RSRP measurement.

3. The scheduling entity according to claim 1, wherein, The TA verification criteria also indicate one or more of the following: At least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index for each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the downlink signal quality measurement of each of the at least one downlink reference signals, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes to the detection of the serving cell or transmit and receive point (TRP), or TA timer configuration.

4. The scheduling entity according to claim 3, wherein, The UE RRC state includes one of the following: inactive state, idle state, and connected state.

5. The scheduling entity according to claim 4, wherein, For either the inactive state or the idle state, the one or more processors are configured to perform the following operations: The CG-SDT configuration is transmitted via either Radio Resource Control (RRC) signaling or Media Access Control (MAC) control element (MAC CE).

6. The scheduling entity according to claim 1, wherein, The one or more processors are configured to transmit the one or more downlink reference signals during measurement gaps that at least partially overlap with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

7. The scheduling entity according to claim 1, wherein, The periodic scheduling used for CG-SDT transmissions is configured in conjunction with the DRX cycle, and the period of the CG-SDT transmissions is configured to be proportional to the period of the DRX cycle.

8. The scheduling entity according to claim 1, wherein, The one or more processors are configured to transmit the CG-SDT configuration by transmitting a search space configuration and a PDCCH configuration that at least partially overlap with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

9. The scheduling entity according to claim 3, wherein, The UE uplink coverage enhancement includes: multiple PUSCH repetition levels, multiple aggregated PUSCH slots, or a PUSCH repetition mode including at least frequency hopping, redundant version cycling, and DMRS configuration.

10. The scheduling entity according to claim 1, wherein, The one or more processors are configured to send the CG-SDT configuration to the UE by sending CG-SDT configuration parameters for the UE, a downlink reference signal or channel used by the UE for TA authentication, and the TA authentication criteria for the UE, wherein the time gap between the downlink reference signal or channel used by the UE for TA authentication and the CG-SDT transmission from the UE is not less than a configured time threshold.

11. The scheduling entity according to claim 1, wherein, The one or more processors are configured to transmit the CG-SDT configuration by sending a common or individual CG-SDT configuration to multiple user equipments (UEs), wherein the one or more processors are configured to transmit the CG-SDT configuration by sending the common or individual CG-SDT configuration on shared or partially overlapping radio resources in the time or frequency domain using one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams.

12. A wireless communication method for a scheduling entity in a wireless communication network, the method comprising: Send a Configurable Allowed Small Data Transmission (CG-SDT) configuration to the User Equipment (UE), the CG-SDT configuration including a timing advance (TA) verification criterion, the TA verification criterion indicating that TA verification prior to CG-SDT transmission is based on at least one downlink signal quality measurement satisfying at least one threshold; According to periodic scheduling, during discontinuous reception (DRX) periods, one or more downlink reference signals for TA verification are transmitted together with either a wake-up signal (WUS) or a paging signal. as well as Communication is received from the UE based on the CG-SDT configuration.

13. The method according to claim 12, wherein, The downlink signal quality measurement includes a reference signal received power (RSRP) measurement or a change in the RSRP measurement.

14. The method according to claim 12, wherein, The TA verification criteria also indicate one or more of the following: At least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index for each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the downlink signal quality measurement of each of the at least one downlink reference signals, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes to the detection of the serving cell or transmit and receive point (TRP), or TA timer configuration.

15. The method according to claim 14, wherein, The UE RRC state includes one of the following: inactive state, idle state, and connected state.

16. The method according to claim 15, wherein, For either the inactive state or the idle state, sending the CG-SDT configuration includes sending the CG-SDT configuration via either Radio Resource Control (RRC) signaling or MAC Control Element (MAC CE).

17. The method according to claim 12, wherein, Sending the CG-SDT configuration further includes sending the downlink reference signal within a measurement gap configuration that at least partially overlaps with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

18. The method according to claim 12, wherein, The periodic scheduling is configured in conjunction with the DRX cycle, and the period of CG-SDT configuration transmission is configured to be proportional to the period of the DRX cycle.

19. The method according to claim 12, wherein, Sending the CG-SDT configuration further includes sending a search space configuration and a PDCCH configuration that at least partially overlap with the WUS timing, paging timing, or DRX-ON time period of the UE configured to have CG-SDT resources.

20. The method of claim 14, wherein, The scope of the UE uplink coverage enhancement includes: multiple PUSCH repetition levels, or multiple aggregated PUSCH slots, or a PUSCH repetition mode including at least frequency hopping, redundant version cycling, and DMRS configuration.

21. The method according to claim 12, wherein, Sending the CG-SDT configuration to the UE includes: sending CG-SDT configuration parameters for the UE, a downlink reference signal or channel used by the UE for TA authentication, and the TA authentication criteria for the UE, wherein the time gap between the downlink reference signal or channel used by the UE for TA authentication and the CG-SDT transmission from the UE is not less than a configured time threshold.

22. The method according to claim 12, wherein, Sending the CG-SDT configuration includes sending common or individual CG-SDT configuration information to multiple user equipments (UEs), wherein sending the CG-SDT configuration includes sending the common or individual CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domain using one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams.

23. A user equipment (UE) within a wireless communication network, comprising: One or more memory units; as well as One or more processors coupled to the one or more memories, wherein the one or more processors are configured to perform the following operations: Send signal quality measurements for the configured downlink beam; Receive configured permitted small data transmission (CG-SDT) configuration, the CG-SDT configuration including timing advance (TA) verification criteria, the TA verification criteria indicating that TA verification prior to CG-SDT transmission is based on the signal quality measurement meeting at least one threshold; According to periodic scheduling, during discontinuous reception (DRX) periods, one or more downlink reference signals for TA verification are received together with either a wake-up signal (WUS) or a paging signal; Based on the one or more downlink reference signals, the TA used for CG-SDT transmission is verified according to the TA verification criteria; and The CG-SDT configuration is performed for communication with the wireless communication network.

24. The UE according to claim 23, wherein, The signal quality measurement includes a reference signal received power (RSRP) measurement or a change in the RSRP measurement, and wherein the TA verification criterion further indicates at least one of the following: At least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index for each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the signal quality measurement of each of the at least one downlink reference signals, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes to the detection of the serving cell or transmit and receive point (TRP), or TA timer configuration.

25. The UE according to claim 23, wherein, The one or more processors are configured to: perform the TA verification based on the TA verification criteria configured for CG-SDT transmission, and perform the CG-SDT configuration based on the result of the TA verification, wherein the time interval between the CG-SDT transmission and the TA verification is not less than a configured threshold.

26. The UE according to claim 23, wherein, The one or more processors are configured to receive the CG-SDT configuration by receiving public or individual CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domains of one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams.

27. A wireless communication method for a user equipment (UE) in a wireless communication network, the method comprising: Send signal quality measurements for the configured downlink beam; Receive configured permitted small data transmission (CG-SDT) configuration, the CG-SDT configuration including timing advance (TA) verification criteria, the TA verification criteria indicating that TA verification prior to CG-SDT transmission is based on the signal quality measurement meeting at least one threshold; According to periodic scheduling, during discontinuous reception (DRX) periods, one or more downlink reference signals for TA verification are received together with either a wake-up signal (WUS) or a paging signal; Based on the one or more downlink reference signals, the TA used for CG-SDT configuration is verified according to one or more TA verification criteria in the TA verification criteria. as well as The CG-SDT configuration is performed for communication with the wireless communication network.

28. The method according to claim 27, wherein, The signal quality measurement includes a reference signal received power (RSRP) measurement or a change in the RSRP measurement, and wherein the TA verification criterion further indicates at least one of the following: At least one downlink signal quality measurement configuration, at least one downlink reference signal, a corresponding beam index for each of the at least one downlink reference signals, location information obtained from at least one of the serving cell or one or more neighboring cells, a corresponding transmit power offset to be applied to the signal quality measurement of each of the at least one downlink reference signals, UE capability, UE radio resource control (RRC) status, UE uplink coverage enhancement for CG-SDT transmission, changes to the detection of the serving cell or transmit and receive point (TRP), or TA timer configuration.

29. The method according to claim 27, wherein, The TA verification is based on the TA verification criteria configured for the CG-SDT configuration transmission, and the execution of the CG-SDT configuration is based on the result of the TA verification, wherein the time gap between the CG-SDT transmission and the TA verification is not less than or equal to a configured threshold.

30. The method according to claim 27, wherein, Receiving the CG-SDT configuration includes: receiving public or individual CG-SDT configuration information on shared or partially overlapping radio resources in the time or frequency domain using one or more beams that have a quasi-co-location (QCL) relationship with other DL broadcast beams.

Images