Apparatus and method of communication

Abstract

Aspects of the disclosure relate to a communication device and method. The base station transmits, to the UE, a configuration including information for resource management of the SDT. Based on the information, the UE performs SDT resource management. Thus, the SDT communication performance can be enhanced, and the resource utilization rate can be improved.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to communication devices and methods for small data transmission (SDT). Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). In addition, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] Currently, inactive or idle SDTs have been approved to save signaling overhead. Furthermore, support for Mobile Initiation SDT (MO-SDT) and Mobile Termination SDT (MT-SDT) procedures has been agreed upon. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems for supporting resource management for SDT. By receiving a configuration including information for SDT resource management, a communication device can perform SDT resource management based on that information. This enhances SDT communication performance and improves resource utilization.

[0005] In one aspect, some implementations of the methods and apparatus described herein may include: receiving configuration from a base station, the configuration including information for resource management of small data transmission; and performing resource management for small data transmission based on the information.

[0006] In some implementations of the methods and apparatus described herein, the information may include at least one of the following: the resource used for SDT is a valid resource; or rules for selecting the resource or process used for SDT.

[0007] In some implementations of the methods and apparatus described herein, performing resource management may include at least one of the following: selecting a configuration authorization resource configured for small data transmission based on the determination that the configuration authorization resource configured for small data transmission is valid; selecting a random access resource configured for small data transmission based on the determination that the configuration authorization resource configured for small data transmission is invalid; selecting a random access resource configured for small data transmission based on the determination that the configuration authorization resource configured for small data transmission is invalid and the random access resource configured for small data transmission is valid; selecting a random access resource configured for a user equipment based on the determination that the configuration authorization resource configured for small data transmission is invalid and the random access resource configured for small data transmission is invalid; or selecting a random access resource configured for a user equipment based on the determination that the configuration authorization resource configured for small data transmission is invalid.

[0008] In some implementations of the methods and apparatus described herein, performing resource management may include at least one of the following: if a configuration-authorized resource is determined to be invalid, keeping the configuration-authorized resource available for subsequent resource selection; or if a configuration-authorized resource is determined to be invalid a first predetermined number of times, releasing the configuration-authorized resource.

[0009] In some implementations of the methods and apparatus described herein, keeping the configuration licensed resource available for subsequent resource selection may include: keeping the time alignment timer used to configure the licensed resource running.

[0010] In some implementations of the methods and apparatus described herein, releasing a configuration license resource may include: incrementing a counter based on determining that the configuration license resource is invalid; and releasing the configuration license resource based on determining that the value of the counter equals a first predetermined number of times.

[0011] Some implementations of the methods and apparatus described herein may also include at least one of the following: resetting a counter based on determining that the configured authorized resource has been continuously valid for a second predetermined number of times; or decrementing a counter based on determining that the configured authorized resource is valid.

[0012] In some implementations of the methods and apparatus described herein, performing resource management may include sending an indication via a transceiver to a base station of the reason for selecting random access resources configured for small data transmission or for user equipment.

[0013] In some implementations of the methods and apparatus described herein, an indication may indicate at least one of the following: whether the configuration authorization resource configured for small data transmission is invalid; whether the change in channel quality is greater than a threshold change; whether timing advance is effective; or whether neither the synchronization signal nor the physical broadcast channel block has signal quality greater than a threshold quality.

[0014] In some implementations of the methods and apparatus described herein, performing resource management may include: receiving configuration from a base station via a transceiver, the configuration indicating a report of an event in which the resource is invalid for small data transmission; determining, based on the determination that the resource is invalid for small data transmission, that an entry condition for the event is met; and, based on the configuration, sending a report to the base station via the transceiver.

[0015] In some implementations of the methods and apparatus described herein, the report may indicate at least one of the following: signal quality of the synchronization signal and the physical broadcast channel block set; timing advance invalidation; channel quality variation exceeding a threshold; or resource invalidation.

[0016] On the other hand, some implementations of the methods and apparatus described herein may include sending a configuration, including information for resource management for small data transmission, to a user equipment.

[0017] In some implementations of the methods and apparatus described herein, the information may include at least one of the following: the resource used for small data transmission is a valid resource; or rules for selecting the resource or process used for small data transmission.

[0018] Some implementations of the methods and apparatus described herein may further include: receiving from a user equipment an indication of the reason for selecting a random access resource configured for small data transmission or for a random access resource configured for the user equipment.

[0019] In some implementations of the methods and apparatus described herein, an indication may indicate at least one of the following: whether the configuration authorization resource configured for small data transmission is invalid; whether the change in channel quality is greater than a threshold change; whether timing advance is effective; or whether neither the synchronization signal nor the physical broadcast channel block has signal quality greater than a threshold quality.

[0020] Some implementations of the methods and apparatus described herein may also include: sending a configuration to a user equipment via a transceiver, the configuration indicating a report of an event that the resource is invalid for small data transmission; and receiving the report from the user equipment via the transceiver based on the configuration.

[0021] In some implementations of the methods and apparatus described herein, the report may indicate at least one of the following: signal quality of the synchronization signal and the physical broadcast channel block set; timing advance invalidation; channel quality variation exceeding a threshold; or resource invalidation. Attached Figure Description

[0022] Figure 1 An example of a wireless communication system supporting the management of resources for SDT according to various aspects of this disclosure is illustrated.

[0023] Figure 2 An example of a process for managing resources for SDT, supported by various aspects of this disclosure, is illustrated.

[0024] Figure 3 An example of a device supporting the management of resources for SDT according to various aspects of this disclosure is illustrated.

[0025] Figure 4 An example of another device supporting the management of resources for SDT according to various aspects of this disclosure is illustrated.

[0026] Figure 5 An example of a processor that supports resource management for SDT according to various aspects of this disclosure is illustrated.

[0027] Figure 6 The diagram illustrates a flowchart of a method for managing resources for SDT in accordance with various aspects of this disclosure.

[0028] Figure 7 The diagram illustrates a flowchart of another method for managing resources for SDT, in accordance with various aspects of this disclosure. Detailed Implementation

[0029] As is known, the SDT procedure can be performed via a random access (RA) procedure with a 2-step RA type or a 4-step RA type (i.e., RA-SDT) or via a configured authorization (CG) type 1 (i.e., CG-SDT). For convenience, the CG resources configured for SDT can also be referred to as CG-SDT resources, and the RA resources configured for SDT can also be referred to as RA-SDT resources. RA resources configured for the UE (i.e., non-SDT RA resources) can also be used in the SDT procedure.

[0030] Normally, during SDT transmission, if CG-SDT resources are available for SDT, then CG-SDT resources can be used for SDT. If no CG-SDT resources are available for SDT, then RA-SDT resources can be used for SDT. If no RA-SDT resources are available for SDT, then non-SDT RA resources can be used for SDT.

[0031] Recently, it has been agreed that for both MO-SDT and MT-SDT, if the next CG-SDT resource is too far away, the RA resource can be selected first. In the context of this disclosure, the term "too far away" can mean that the available resource is far from the arriving data and the arriving data cannot be sent in a timely manner, or that the parameters of the CG-SDT resource (e.g., subcarrier spacing (SCS), physical uplink shared channel (PUSCH) duration, etc.) are unsuitable for data transmission. The arriving data can be uplink (UL) data or downlink (DL) data. In the context of this disclosure, if a resource is too far away, the resource is considered invalid. Otherwise, the resource is considered valid.

[0032] However, it remains unclear how to consider resource effectiveness when selecting resources for SDT. It is also unclear how to handle resources that are not selected for SDT.

[0033] In view of this, embodiments of the present disclosure provide a solution for managing resources for SDT. In this solution, the base station sends a configuration including information for resource management for SDT to the UE. Based on this information, the UE performs resource management for SDT.

[0034] In this way, SDT communication performance can be enhanced, and resource utilization can be improved.

[0035] All aspects of this disclosure are described in the context of wireless communication systems.

[0036] Figure 1 An example of a wireless communication system 100 supporting the evaluation of resources for SDT according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0037] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0038] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0039] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine-Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0040] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 The diagram illustrates some examples of UE104. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Figure 1 As shown in the diagram. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104 that may act as relays in the wireless communication system 100.

[0041] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0042] Network entity 102 may support communication with core network 106, or with another network entity 102, or with both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0043] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) system, or any combination thereof.

[0044] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0045] The functional splitting among CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional splitting can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0046] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack, and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within a protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer can be performed by another of the CU, DU, or RU).

[0047] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the mid-range or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the respective network entity 102 communicating via such communication links.

[0048] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and user plane entities that route packets or interconnects to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0049] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0050] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (such as symbols, time slots, subframes, frames, etc.) or frequency resources (such as subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single-frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0051] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. The first digital technology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15kHz) may utilize one time slot per subframe. A second digital technology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third digital technology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0052] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, such as 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, such as 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0053] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include multiple (e.g., a number of) time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth digital technologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include multiple (e.g., a number of) symbols (e.g., OFDM symbols). In some implementations, the number (e.g., a number of) time slots in a subframe may depend on the digital technology. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier interval), a time slot may include 12 symbols. For both ordinary cyclic prefixes and extended cyclic prefixes, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame can depend on the digital technique. It should be understood that references to the first digital technique (e.g., μ=0) associated with the first subcarrier interval (e.g., 15 kHz) can be used interchangeably between subframes and slots.

[0054] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into multiple categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0055] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with: a first digital technology (e.g., μ=0) comprising a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ=1) comprising a subcarrier spacing of 30 kHz; and a third digital technology (e.g., μ=2) comprising a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with: a third digital technology (e.g., μ=2) comprising a subcarrier spacing of 60 kHz; and a fourth digital technology (e.g., μ=3) comprising a subcarrier spacing of 120 kHz.

[0056] In the context of this disclosure, the term “connected state” may be used interchangeably with “RRC_CONNECTED state”, the term “idle state” may be used interchangeably with “RRC_IDLE state”, and the term “inactive state” may be used interchangeably with “RRC_INACTIVE state”.

[0057] In some scenarios, UE 104 may enter an inactive or idle state. In some embodiments where UE 104 is in an inactive or idle state, small and low-frequency uplink (UL) data may reach UE 104. UE 104 may perform an SDT procedure to send UL data to network entity 102. This procedure is an MO-SDT procedure.

[0058] In some embodiments where UE 104 is inactive or idle, network entity 102 may send a paging message to UE 104. The paging message may be associated with an SDT (Software-Defined Timeout). In other words, the paging message may indicate an SDT. Upon receiving a paging message, UE 104 may send a response to the paging message to network entity 102. Network entity 102 may then send DL (Data Streaming) data to UE 104. This process is an MT-SDT (Multi-Level Designation) procedure.

[0059] Embodiments of this disclosure provide a solution for managing resources used in SDT. This solution can be applied to both MO-SDT and MT-SDT processes. The following will combine... Figure 2 Describe the solution.

[0060] Figure 2 An example of a process 200 for evaluating resources used in SDT in accordance with various aspects of this disclosure is illustrated. For purposes of discussion, reference will be made to... Figure 1 Describe process 200. Process 200 may involve, for example, Figure 1 The UE 104 and network entity 102 are shown in the diagram. It should be understood that... Figure 2The steps and their order are for illustrative purposes only and are not intended to be limiting.

[0061] like Figure 2 As shown, network entity 102 can send 210 a configuration including information for resource management for SDT to UE 104. This information can indicate rules for resource management for SDT. This configuration can be sent in any suitable manner, and this disclosure is not limiting in this respect.

[0062] In some embodiments, the SDT may include an initial transmission of the SDT. In some embodiments, the SDT may include an initial transmission of the SDT and one or more subsequent transmissions. That is, embodiments of this disclosure can be applied to the initial new transmission and / or subsequent new transmissions of the SDT.

[0063] In some embodiments, the information for resource management in SDT may include whether the resources used in SDT are valid resources. In other words, resource validity should be considered in resource selection for SDT, and only valid resources can be used in SDT. In some embodiments, the information for resource management in SDT may indicate that validity assessment is applied only to CG-SDT resources. In some embodiments, the information for resource management in SDT may indicate that validity assessment is applied only to RA-SDT resources. In some embodiments, the information for resource management in SDT may indicate that validity assessment is applied to both CG-SDT resources and RA-SDT resources.

[0064] In some embodiments, the information for resource management of SDT may include rules for selecting SDT resources or processes, i.e., a sequence for selecting SDT resources or processes. In some embodiments, the information for resource management of SDT may indicate that CG-SDT resources or processes precede RA-SDT resources or processes, and that RA-SDT resources or processes precede non-SDT RA resources or processes. In some embodiments, if a CG-SDT resource or process is invalid for SDT (i.e., not satisfied), the information for resource management of SDT may indicate or define whether a RA-SDT resource or process is ignored.

[0065] It should be understood that the information used for resource management in SDT may include any combination of the above-mentioned information or any other appropriate information. In some alternative embodiments, the information used for resource management in SDT may be predefined.

[0066] Continue to refer to Figure 2 UE 104 can perform 220 SDT resource management based on information used for SDT resource management. (Reference) Figure 2 In some embodiments, UE 104 may select 221SDT resources based on this information.

[0067] In some embodiments, if the CG-SDT resource or procedure is valid or available (i.e., not too far away), UE 104 may select the CG-SDT resource or procedure for the SDT. In some embodiments, if the CG-SDT resource or procedure is invalid (i.e., too far away), UE 104 may select the RA-SDT resource or procedure for the SDT. In other words, UE 104 may select the RA-SDT resource or procedure even if other conditions for the CG-SDT resource are met but the CG-SDT resource is too far away.

[0068] In some embodiments, if the CG-SDT resource or procedure is invalid and the RA-SDT resource or procedure is valid, UE104 can select the RA-SDT resource or procedure for the SDT. In other words, if the conditions for the RA-SDT resource are met (e.g., the RA-SDT resource is not too far away), UE104 will select the RA-SDT resource or procedure even if other conditions for the CG-SDT resource are met but the CG-SDT resource is too far away.

[0069] In some embodiments where CG-SDT or RA-SDT resources are selected for SDT, the lower layer of UE 104 may indicate to the upper layer of UE 104 that the conditions for initiating the SDT procedure have been met.

[0070] In some embodiments, if both the CG-SDT resource or procedure and the RA-SDT resource or procedure are invalid, UE 104 may select a non-SDT RA resource or procedure for transmission (e.g., SDT). In other words, even if other conditions for the CG-SDT and RA-SDT resources are met, UE 104 may select a non-SDT RA resource if the CG-SDT and RA-SDT resources are too far apart.

[0071] In some embodiments, if no CG-SDT resource is configured or selected, and other conditions for RA-SDT resources are met, but the RA-SDT resource is too far away, UE 104 may select a non-SDT RA resource.

[0072] In some embodiments, if the CG-SDT resource or procedure is invalid, the UE 104 can select a non-SDT RA resource or procedure for transmission (e.g., SDT). In other words, if other conditions for the CG-SDT resource are met but the CG-SDT resource is too far away, the UE 104 can select a non-SDT RA resource or procedure.

[0073] In some embodiments where non-SDT RA resources are selected for transport (e.g., SDT), the lower layer of UE 104 may indicate to the upper layer of UE 104 that the conditions for initiating the SDT procedure are not met.

[0074] It should be understood that the effectiveness of resources can be assessed in any suitable way, whether existing or to be developed, and this disclosure does not limit that aspect.

[0075] Thus, taking into account the availability of resources, a sequence for selecting SDT resources can be provided.

[0076] Continue to refer to Figure 2 In some embodiments, UE 104 can process resources 222 that were not selected for SDT. In some embodiments where CG-SDT resources are not selected for SDT, if the CG-SDT resource is invalid, UE 104 can keep the CG-SDT resource available for subsequent resource selection. In some embodiments, UE 104 can keep the CG-SDT resource available for subsequent resource selection, for example, by keeping a time alignment timer for the CG-SDT resource running.

[0077] In some embodiments, if the CG-SDT resource becomes invalid a predetermined number of times (for convenience, also referred to herein as the first predetermined number of times), the UE 104 may release the CG-SDT resource. In some embodiments, the time alignment timer used for the CG-SDT resource may be considered to have expired. In some embodiments, the UE 104 may clear any configured UL authorization.

[0078] In some embodiments, if the CG-SDT resource is invalid, UE 104 may increment a counter. If the counter value equals a first predetermined number of times, UE 104 may release the CG-SDT resource. In some embodiments, the first predetermined number of times may be configured. In some embodiments, the first predetermined number of times may be predefined.

[0079] In some embodiments, if the CG-SDT resource is continuously active for a predetermined number of times (also referred to herein as the second predetermined number of times for convenience), the UE 104 may reset the counter to, for example, 0 or any other suitable value. In some embodiments, if the CG-SDT resource is continuously active for the second predetermined number of times before a configured timer or time window expires, the UE 104 may reset the counter to, for example, 0 or any other suitable value. In some embodiments, the second predetermined number of times can be configured. In some embodiments, the second predetermined number of times can be predefined. In some embodiments, if the CG-SDT resource is active, the UE 104 may decrement the counter. The minimum value of the counter can be 0.

[0080] This allows for the more appropriate management of resources that were not selected for SDT.

[0081] Continue to refer to Figure 2In some embodiments, UE 104 may send 223 information to network entity 102 indicating that the resource was not selected for SDT and is invalid.

[0082] In some embodiments, UE 104 may send an indication of the reason for selecting RA-SDT resources or non-SDT RA resources. In some embodiments, this indication may be sent via a Media Access Control (MAC) control element (CE). In some embodiments, this indication may be sent via a Radio Resource Control (RRC) message. In some embodiments, this indication may be sent via UE assistance information. In some embodiments, this indication may be sent via a new reason value.

[0083] In some embodiments, the indication may indicate whether CG-SDT resources are unsuitable, such as whether CG-SDT resources are invalid (i.e., too far away). In some embodiments, the indication may indicate whether the channel quality variation is higher than (i.e., higher than or equal to) a threshold variation. In some embodiments, the indication may indicate whether there is no synchronization signal and the physical broadcast channel block (SSB) has a signal quality exceeding (i.e., higher than or equal to) a threshold quality. In some embodiments, the indication may indicate whether timing advance (TA) is effective.

[0084] In some embodiments, UE 104 may receive configuration from network entity 102 indicating a report of an event where the resource is invalid for the SDT. If the resource is invalid for the SDT, UE 104 may determine that the entry condition for the event is met. Based on this configuration, UE 104 may send a report to network entity 102. In some embodiments, the report may be sent during the SDT. In some embodiments, the report may be sent by UE 104 in a connected state (e.g., RRC_CONNECTED).

[0085] In some embodiments, the report may indicate the signal quality of a set of SSB blocks (i.e., one or more SSBs). In some embodiments, the report may indicate an invalid TA. In some embodiments, the report may indicate a channel quality change exceeding a threshold change. In some embodiments, the report may indicate an invalid resource. For example, the resource may be a CG-SDT resource or a RA-SDT resource. It should be understood that the report may include any combination of the above information or any other suitable information.

[0086] This concludes the description of resource management for SDT. By utilizing process 200 and considering resource availability, resource selection for SDT can be optimized, and the utilization rate of resources not selected for SDT can be improved.

[0087] Figure 3An example of device 300 supporting the management of resources for SDT according to various aspects of this disclosure is illustrated. Device 300 may be an example of UE 104 or network entity 102 as described herein. Device 300 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 300 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 302, memory 304, transceiver 306, and optionally I / O controller 308. These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0088] Processor 302, memory 304, transceiver 306, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of this disclosure as described herein. For example, processor 302, memory 304, transceiver 306, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0089] In some implementations, processor 302, memory 304, transceiver 306, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described herein. In some implementations, processor 302 and memory 304 coupled to processor 302 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 304 are executed by processor 302).

[0090] For example, according to the examples disclosed herein, processor 302 may support wireless communication at device 300. Processor 302 may be configured to operablely support components for receiving configuration from network entity 102 and performing resource management for SDT based on that information, the configuration including information for resource management for SDT.

[0091] Processor 302 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 302 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into processor 302. Processor 302 may be configured to execute computer-readable instructions stored in memory (e.g., memory 304) to cause device 300 to perform various functions of this disclosure.

[0092] Memory 304 may include random access memory (RAM) and read-only memory (ROM). Memory 304 may store computer-readable, computer-executable code including instructions that, when executed by processor 302, cause device 300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some implementations, the code may not be directly executed by processor 302, but may instead cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 304 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0093] I / O controller 308 can manage the input and output signals of device 300. I / O controller 308 can also manage peripheral devices not integrated into device 300. In some implementations, I / O controller 308 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 308 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 308 can be implemented as part of a processor (such as processor 306). In some implementations, a user can interact with device 300 via I / O controller 308 or via hardware components controlled by I / O controller 308.

[0094] In some implementations, device 300 may include a single antenna 310. However, in other implementations, device 300 may have more than one antenna 310 (e.g., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 306 may communicate bidirectionally via one or more antennas 310, wired or wireless links, as described herein. For example, transceiver 306 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 306 may also include a modem for modulating packets, providing modulated packets to one or more antennas 310 for transmission, and demodulating packets received from one or more antennas 310. Transceiver 306 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0095] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing it for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation techniques like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 310 for transmitting the amplified signal over the air or wireless medium.

[0096] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 310 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the processed demodulated signal to receive the transmitted data.

[0097] Figure 4An example of another device 400 supporting the management of resources for SDT according to various aspects of this disclosure is illustrated. Device 400 may be an example of network entity 102 as described herein. Device 400 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 400 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 402, memory 404, transceiver 406, and optionally I / O controller 408. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0098] Processor 402, memory 404, transceiver 406, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of this disclosure as described herein. For example, processor 402, memory 404, transceiver 406, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0099] In some implementations, processor 402, memory 404, transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described herein. In some implementations, processor 402 and memory 404 coupled to processor 402 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 404 are executed by processor 402).

[0100] For example, according to the examples disclosed herein, processor 402 may support wireless communication at device 400. Processor 402 may be configured to operablely support components for transmitting configurations to UE 104, including information for resource management for SDT.

[0101] Processor 402 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 402 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory (e.g., memory 404) to cause device 400 to perform various functions of this disclosure.

[0102] Memory 404 may include random access memory (RAM) and read-only memory (ROM). Memory 404 may store computer-readable, computer-executable code including instructions that, when executed by processor 402, cause device 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some implementations, the code may not be directly executed by processor 402, but may instead cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 404 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0103] I / O controller 408 can manage the input and output signals of device 400. I / O controller 408 can also manage peripheral devices not integrated into device 400. In some implementations, I / O controller 408 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 408 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 408 can be implemented as part of a processor (such as processor 402). In some implementations, a user can interact with device 400 via I / O controller 408 or via hardware components controlled by I / O controller 408.

[0104] In some implementations, device 400 may include a single antenna 410. However, in other implementations, device 400 may have more than one antenna 410 (e.g., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 406 may communicate bidirectionally via one or more antennas 410, wired or wireless links, as described herein. For example, transceiver 406 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 406 may also include a modem for modulating packets, providing modulated packets to one or more antennas 410 for transmission, and demodulating packets received from one or more antennas 410. Transceiver 406 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0105] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation techniques like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 410 for transmitting the amplified signal over the air or wireless medium.

[0106] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 410 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the processed demodulated signal to receive the transmitted data.

[0107] Figure 5An example of a processor 500 supporting SDT resource management according to various aspects of this disclosure is illustrated. Processor 500 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 500 may include a controller 502 configured to perform various operations according to the examples described herein. Processor 500 may optionally include at least one memory 504, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 500 may optionally include one or more arithmetic logic units (ALUs) 506. These components may be electronically communicated or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0108] Processor 500 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 500) or included in the processor chipset (e.g., processor 500)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0109] Controller 502 can be configured to manage and coordinate various operations of processor 500 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 500 to support various operations according to the examples described herein. For example, controller 502 can operate as a control unit of processor 500, generating control signals that manage the operation of various components of processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0110] Controller 502 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 504 and determine subsequent instructions to be executed to enable processor 500 to support various operations according to the examples described herein. Controller 502 may be configured to track the memory addresses of instructions associated with memory 504. Controller 502 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 502 may be configured to interpret instructions and determine control signals to be output to other components of processor 500 to enable processor 500 to support various operations according to the examples described herein. Additionally or alternatively, controller 502 may be configured to manage data flow within processor 500. Controller 502 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 500.

[0111] Memory 504 may include one or more caches (e.g., memory native to processor 500 or included in processor 500, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 504 may reside within or on the processor chipset (e.g., native to processor 500). In some other implementations, memory 504 may reside outside the processor chipset (e.g., remote processor 500).

[0112] Memory 504 may store computer-readable, computer-executable code including instructions that, when executed by processor 500, cause processor 500 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. Controller 502 and / or processor 500 may be configured to execute computer-readable instructions stored in memory 504 to cause processor 500 to perform various functions. For example, processor 500 and / or controller 502 may be coupled to or coupled to memory 504, and processor 500, controller 502, and memory 504 may be configured to perform the various functions described herein. In some examples, processor 500 may include multiple processors, and memory 504 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and the multiple memories may be configured individually or collectively to perform the various functions described herein.

[0113] One or more ALU 506s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 506s may reside within or on a processor chipset (e.g., processor 500). In some other implementations, one or more ALU 506s may reside outside the processor chipset (e.g., processor 500). One or more ALU 506s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 506s may receive input operands and opcodes, which determine the operation to be performed. One or more ALU 506s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively or additionally, one or more ALU 506s may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 506s to handle conditional operations, comparisons, and bitwise operations.

[0114] Processor 500 may support wireless communication according to the examples described herein. Processor 500 may be configured or operable to support: receiving configuration from network entity 102 including information for resource management for SDT and performing components for resource management for SDT based on that information.

[0115] Figure 6 A flowchart illustrating a method 600 for managing resources for SDT according to various aspects of this disclosure is shown. Operation of method 600 can be implemented by a device or its components as described herein. For example, operation of method 600 can be performed by a UE 104 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or optionally, the device can use dedicated hardware to perform aspects of the described functions.

[0116] In box 605, method 600 may include: receiving a configuration from network entity 102 including information for resource management for SDT. The operation of 605 can be performed according to the examples described herein. In some implementations, aspects of the operation of 605 may be provided by reference to [reference needed]. Figure 1 The device described is used to perform this action.

[0117] In some embodiments, the information may include at least one of the following: the resource used for SDT is a valid resource; or the rules for selecting the resource or process used for SDT.

[0118] In box 610, method 600 may include: performing resource management for SDT based on information. The operations of 610 can be performed according to the examples described herein. In some implementations, aspects of the operations of 610 may be derived from, as referenced... Figure 1 The device described is used to perform this action.

[0119] In some embodiments, performing resource management may include at least one of the following: selecting a configuration authorization resource configured for small data transmission based on the determination that the configuration authorization resource configured for small data transmission is valid; selecting a random access resource configured for small data transmission based on the determination that the configuration authorization resource configured for small data transmission is invalid; selecting a random access resource configured for small data transmission based on the determination that the configuration authorization resource configured for small data transmission is invalid and the random access resource configured for small data transmission is valid; selecting a random access resource configured for a user equipment based on the determination that the configuration authorization resource configured for small data transmission is invalid and the random access resource configured for small data transmission is invalid; or selecting a random access resource configured for a user equipment based on the determination that the configuration authorization resource configured for small data transmission is invalid.

[0120] In some embodiments, performing resource management may include at least one of the following: if the configuration authorization resource is determined to be invalid, keep the configuration authorization resource available for subsequent resource selection; or if the configuration authorization resource is determined to be invalid for a first predetermined number of times, release the configuration authorization resource.

[0121] In some embodiments, keeping the configuration licensed resource available for subsequent resource selection may include keeping the time alignment timer used to configure the licensed resource running.

[0122] In some embodiments, releasing a configuration license resource may include: incrementing a counter based on determining that the configuration license resource is invalid; and releasing the configuration license resource based on determining that the value of the counter equals a first predetermined number of times.

[0123] In some embodiments, method 600 may further include at least one of the following: resetting a counter based on determining that the configuration authorized resource has been continuously valid for a second predetermined number of times; or decrementing a counter based on determining that the configuration authorized resource is valid.

[0124] In some embodiments, performing resource management may include sending an indication to a base station via a transceiver of the reason for selecting random access resources configured for small data transmission or random access resources configured for user equipment.

[0125] In some embodiments, the indication may indicate at least one of the following: whether the configuration authorization resource configured for small data transmission is invalid; whether the change in channel quality is greater than the threshold change; whether the timing advance is effective; or whether the SSB does not have signal quality greater than the threshold quality.

[0126] In some embodiments, performing resource management may include: receiving configuration from network entity 102, the configuration indicating a report of an event in which the resource is invalid for small data transmission; determining, based on the determination that the resource is invalid for small data transmission, that the entry conditions for the event are met; and, based on the configuration, sending a report to a base station via a transceiver.

[0127] In some embodiments, the report may indicate at least one of the following: signal quality of the SSB set; timing advance invalidation; channel quality change exceeding a threshold change; or resource invalidation.

[0128] Figure 7 A flowchart illustrating another method 700 for managing resources for SDT according to various aspects of this disclosure is shown. Operation of method 700 can be implemented by a device or its components as described herein. For example, operation of method 700 can be performed by network entity 102 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or optionally, the device can use dedicated hardware to perform aspects of the described functions.

[0129] In box 705, method 700 may include sending a configuration to UE 104 including information for resource management for SDT. The operation of 705 can be performed according to the examples described herein. In some implementations, aspects of the operation of 705 may be provided by reference to [reference needed]. Figure 1 The device described is used to perform this action.

[0130] In some embodiments, the information may include at least one of the following: the resource used for small data transfer is a valid resource; or rules for selecting the resource or process used for small data transfer.

[0131] In some embodiments, method 700 may further include: receiving from UE 104 an indication of the reason for selecting a random access resource configured for small data transmission or a random access resource configured for a user equipment.

[0132] In some embodiments, the indication may indicate at least one of the following: whether the configuration authorization resource configured for small data transmission is invalid; whether the change in channel quality is greater than the threshold change; whether the timing advance is effective; or whether the SSB does not have signal quality greater than the threshold quality.

[0133] In some embodiments, method 700 may further include: sending a configuration to UE 104, the configuration indicating a report of an event where resources are invalid for small data transmission; and receiving a report from UE 104 based on the configuration.

[0134] In some embodiments, the report may indicate at least one of the following: signal quality of the SSB set; timing advance invalidation; channel quality change exceeding a threshold change; or resource invalidation.

[0135] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified; other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0136] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0137] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0138] Computer-readable media include non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. As examples, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store required program code in the form of instructions or data structures and is accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0139] As used herein, including in the claims, the article “a” preceding an element is non-limiting and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “a or both”) indicates an inclusive list, such that a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Additionally, as used herein, including in the claims, “set” can include one or more elements.

[0140] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment, comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver receives configuration from the base station, the configuration including information for resource management of small data transmissions; and Based on the information, resource management is performed for the small data transmission.

2. The user equipment according to claim 1, wherein the information includes at least one of the following: The resources used for the small data transmission are available resources; or Rules for selecting the resources or processes used for the small data transfer.

3. The user equipment of claim 1, wherein the processor is configured to perform the resource management by at least one of the following: Based on the determination that the configuration authorization resource configured for the small data transmission is valid, select the configuration authorization resource configured for the small data transmission; If the configuration authorization resource configured for the small data transmission is determined to be invalid, a random access resource configured for the small data transmission is selected. Based on the determination that the configuration authorization resource configured for the small data transmission is invalid and the random access resource configured for the small data transmission is valid, the random access resource configured for the small data transmission is selected. Based on the determination that the configured authorized resource for the small data transmission is invalid and the random access resource configured for the small data transmission is invalid, a random access resource configured for the user equipment is selected; or If the configuration authorization resource configured for the small data transmission is determined to be invalid, the random access resource configured for the user equipment is selected.

4. The user equipment of claim 1, wherein the processor is configured to perform the resource management by at least one of the following: If the configured authorized resource is determined to be invalid, the configured authorized resource remains available for subsequent resource selection; or If the configuration authorization resource is determined to be invalid a first predetermined number of times, the configuration authorization resource is released.

5. The user equipment of claim 4, wherein the processor is configured to maintain the configuration-authorized resources available for subsequent resource selection by: Keep the time alignment timer used for the configured authorized resources running.

6. The user equipment of claim 4, wherein the processor is configured to release the configuration authorization resources by: Based on the determination that the configured authorized resource is invalid, increment the counter; and The configuration authorization resources are released once the value of the counter is determined to be equal to the first predetermined number of times.

7. The user equipment of claim 6, wherein the processor is further configured to at least one of the following: The counter is reset based on the determination that the configured authorized resources have been continuously valid for a second predetermined number of times; or The counter is decremented once the configured authorized resources are determined to be valid.

8. The user equipment of claim 1, wherein the processor is configured to perform the resource management by: The transceiver sends an indication to the base station regarding the reason for selecting random access resources configured for the small data transmission or for the user equipment.

9. The user equipment of claim 8, wherein the indication specifies at least one of the following: Is the configuration authorization resource configured for the small data transmission invalid? Does the change in channel quality exceed the threshold change? Is setting a timer in advance effective? Neither the synchronization signal nor the physical broadcast channel block has signal quality above the threshold quality.

10. The user equipment of claim 1, wherein the processor is configured to perform the resource management by: The transceiver receives a configuration from the base station, the configuration indicating a report of an event where resources are invalid for the small data transmission; Based on the determination that the resource is invalid for the small data transmission, the entry condition of the event is determined to be met; as well as Based on the configuration, the report is sent to the base station via the transceiver.

11. The user equipment of claim 10, wherein the report indicates at least one of the following: Signal quality of synchronization signals and physical broadcast channel block sets; Pre-scheduling is ineffective; The change in channel quality is greater than the change in the threshold; or The resource is invalid.

12. A processor for wireless communication, comprising: At least one memory; as well as A controller, coupled to the at least one memory, and configured such that the controller: Obtain configuration, which includes information for resource management for small data transfers; and Based on the information, resource management is performed for the small data transmission.

13. The processor of claim 12, wherein the information includes at least one of the following: The resources used for the small data transmission are available resources; or Rules for selecting the resources or processes used for the small data transfer.

14. The processor of claim 12, wherein the processor is configured to perform the resource management by at least one of the following: Based on the determination that the configuration authorization resource configured for the small data transmission is valid, select the configuration authorization resource configured for the small data transmission; If the configuration authorization resource configured for the small data transmission is determined to be invalid, a random access resource configured for the small data transmission is selected. Based on the determination that the configuration authorization resource configured for the small data transmission is invalid and the random access resource configured for the small data transmission is valid, the random access resource configured for the small data transmission is selected. Based on the determination that the configured authorized resource for the small data transmission is invalid and the random access resource configured for the small data transmission is invalid, a random access resource configured for the user equipment is selected; or If the configuration authorization resource configured for the small data transmission is determined to be invalid, the random access resource configured for the user equipment is selected.

15. The processor of claim 12, wherein the processor is configured to perform the resource management by at least one of the following: If the configured authorized resource is determined to be invalid, the configured authorized resource remains available for subsequent resource selection; or If the configuration authorization resource is determined to be invalid a first predetermined number of times, the configuration authorization resource is released.

16. The processor of claim 15, wherein the processor is configured to maintain the configuration-authorized resources available for subsequent resource selection by: Keep the time alignment timer used for the configured authorized resources running.

17. The processor of claim 15, wherein the processor is configured to release the configuration-authorized resources by: Based on the determination that the configured authorized resource is invalid, increment the counter; and The configuration authorization resources are released once the value of the counter is determined to be equal to the first predetermined number of times.

18. The processor of claim 12, wherein the processor is configured to perform the resource management by: The transceiver sends an indication to the base station regarding the reason for selecting random access resources configured for the small data transmission or for the user equipment.

19. A base station, comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver sends a configuration to the user equipment, the configuration including information on resource management for small data transmissions.

20. A method performed by a user equipment, the method comprising: Receive configuration from the base station, the configuration including information for resource management for small data transmission; as well as Based on the information, resource management is performed for the small data transmission.

Images