Apparatus and method of communication

Abstract

Aspects of the present disclosure relate to devices and methods of communication. The base station sends a configuration to the UE, the configuration comprising information for evaluating validity of resources for SDT. Based on the information, the UE determines validity of the resource. In this way, an effective resource may be determined for the SDT, and communication efficiency may be improved.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to devices and methods for communication 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 the evaluation of resources used in SDT. By receiving a configuration including information for evaluating the effectiveness of resources, a communication device can determine effective resources for SDT based on that information. This can improve communication efficiency.

[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 evaluating the effectiveness of resources for small data transmission; and determining the effectiveness of the resources based on the information.

[0006] In some implementations of the methods and apparatus described herein, the information includes at least one of the following: a set of radio bearers, operations associated with network power saving, a threshold for determining the effectiveness of resources, or a reference value for determining the effectiveness of resources.

[0007] In some implementations of the methods and apparatus described herein, the threshold is associated with at least one of the following: a radio bearer, a set of data radio bearers for small data transmission, a set of signaling radio bearers for small data transmission, a logical channel, or a group of logical channels.

[0008] In some implementations of the methods and apparatus described herein, determining the validity of a resource includes: determining the time interval between a first time point associated with the resource and a reference time point; determining the resource to be valid if the determined time interval is below a threshold; and determining the resource to be invalid if the determined time interval is above a threshold.

[0009] In some implementations of the methods and apparatus described herein, the reference time point is one of the following: the time point at which a paging message associated with small data transmission is received, the time point at which a response to the paging is initiated, the time point at which a recovery process is initiated for small data transmission, or the time point at which data associated with small data transmission arrives.

[0010] In some implementations of the methods and apparatus described in this paper, the threshold is the delay requirement of radio bearers in a set of radio bearers used for small data transmission.

[0011] In some implementations of the methods and apparatus described herein, the information includes a set of thresholds associated with a set of radio bearers. These implementations of the methods and apparatus described herein may further include: receiving a paging message, the paging message including: an indication of a radio bearer associated with small data transmission in the set of radio bearers; and determining a threshold associated with a radio bearer from the set of thresholds.

[0012] In some implementations of the methods and apparatus described in this paper, the threshold is a timer value or time window configured by the base station.

[0013] In some implementations of the methods and apparatus described in this paper, the first point in time is the preamble transmission timing associated with the resource.

[0014] In some implementations of the methods and apparatus described herein, the threshold is a second time point associated with the configuration authorization resource used for small data transfer, at which point the configuration authorization resource becomes invalid.

[0015] In some implementations of the methods and apparatus described herein, the first time point is determined based on the timing of uplink data transmission during the random access procedure.

[0016] In some implementations of the methods and apparatus described herein, the uplink data transmission timing is determined based on the preamble transmission timing and reference values ​​associated with the resource.

[0017] In some implementations of the methods and apparatus described herein, reference values ​​are determined based on at least one of the following: a random access response window, a round-trip time value, the duration from the reception of a downlink scheduling signal to the reception of an uplink grant, the duration from the transmission of a preamble to the reception of a downlink scheduling signal, or a processing delay.

[0018] In some implementations of the methods and apparatus described herein, determining the validity of a resource includes at least one of the following: determining that the resource is valid based on a determination that the duration of the period during which the base station does not perform transmission or reception does not overlap; or determining that the resource is invalid based on a determination that the duration of the period during which the base station does not perform transmission or reception overlaps.

[0019] In some implementations of the methods and apparatus described herein, determining the validity of a resource includes: determining the permissible uplink data transmission duration associated with a radio bearer in a set of radio bearers used for small data transmission; determining the resource to be valid based on a determination that the uplink data transmission duration associated with the resource is less than the permissible uplink data transmission duration associated with the radio bearer; and determining the resource to be invalid based on a determination that the uplink data transmission duration associated with the resource is greater than the permissible uplink data transmission duration associated with the radio bearer.

[0020] Some implementations of the methods and apparatus described herein may further include: selecting a first carrier for initiating small data transmission; and performing carrier reselection to the second carrier based on the determination that no resources are available on the first carrier and resources are available on the second carrier.

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

[0022] In some implementations of the methods and apparatus described herein, the information includes at least one of the following: a set of radio bearers, operations associated with network power saving, a threshold for determining the effectiveness of resources, or a reference value for determining the effectiveness of resources.

[0023] In some implementations of the methods and apparatus described herein, the threshold is associated with at least one of the following: a radio bearer, a set of data radio bearers for small data transmission, a set of signaling radio bearers for small data transmission, a logical channel, or a group of logical channels.

[0024] In some implementations of the methods and apparatus described in this paper, the threshold is a timer value or time window configured by the base station.

[0025] In some implementations of the methods and apparatus described herein, the information may include a set of thresholds associated with a set of radio bearers. Some implementations of the methods and apparatus described herein may also include sending a paging message to a user equipment, the paging message including an indication of a radio bearer associated with small data transmission within the set of radio bearers. Attached Figure Description

[0026] Figure 1 An example of a wireless communication system that supports the evaluation of resources applied to SDT according to various aspects of this disclosure is illustrated.

[0027] Figure 2 An example of the process for evaluating resources used in SDT in accordance with various aspects of this disclosure is illustrated.

[0028] Figure 3 An example of an apparatus supporting the evaluation of resources for SDT according to various aspects of this disclosure is illustrated.

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

[0030] Figure 5 An example of a processor supporting the evaluation of resources for SDT according to various aspects of this disclosure is illustrated.

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

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

[0033] 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. The RA resources configured for the UE can also be used in the SDT procedure.

[0034] 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 transmitted 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.

[0035] However, it remains unclear how to determine if CG-SDT resources are too far away. It also remains unclear how to determine if RA-SDT resources are too far away.

[0036] In view of this, embodiments of this disclosure provide a solution for evaluating the effectiveness of resources used for SDT. In this solution, the base station sends a configuration to the UE, the configuration including information for evaluating the effectiveness of resources used for SDT. Based on the information, the UE determines the effectiveness of the resources.

[0037] In this way, by determining the validity of resources for SDT based on information included in the configuration for evaluating resource validity, the communication device can identify valid resources for SDT, thereby improving communication efficiency.

[0038] The aspects of this disclosure are described in the context of wireless communication systems.

[0039] Figure 1An example of a wireless communication system 100 supporting the evaluation of resources for SDT according to various aspects of this disclosure is shown. 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).

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

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

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

[0043] 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 equipment, integrated access and backhaul (IAB) node, or another network device), such as 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.

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

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

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

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

[0048] The functional decomposition 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 decomposition 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), Service 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.

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

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

[0051] 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 interconnections 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.

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

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

[0054] 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., 15 kHz) and a normal cyclic prefix. The first digital technology (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) 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., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

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

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

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

[0058] 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) that includes a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ = 1) that includes a subcarrier spacing of 30 kHz; and a third digital technology (e.g., μ = 2) that includes 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) that includes a subcarrier spacing of 60 kHz; and a fourth digital technology (e.g., μ = 3) that includes a subcarrier spacing of 120 kHz.

[0059] 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”.

[0060] 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 infrequent 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.

[0061] In some embodiments where UE 104 is in an inactive or idle state, network entity 102 may send a paging message to UE 104. The paging message may be associated with an SDT (Software Directive). 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. When UE 104 remains in an inactive or idle state, network entity 102 may send DL (Data Streaming) data to UE 104. This process is an MT-SDT (Multi-Level Designation) procedure.

[0062] Embodiments of this disclosure provide a solution for evaluating the effectiveness of 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.

[0063] Figure 2 An example of a process 200 for evaluating resources for SDT is illustrated, supported by various aspects of this disclosure. 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 2 The steps and their order are for illustrative purposes only and not for limitation.

[0064] like Figure 2 As shown, network entity 102 can send configuration 210 to UE 104, which includes information for evaluating the effectiveness of resources used for SDT. In some embodiments, the configuration can be sent while UE 104 is in a connected state. In some embodiments, the configuration can be sent when UE 104 is released to an inactive or idle state. In some embodiments, the configuration can be updated when UE 104 is in an inactive or idle state.

[0065] In some embodiments, this information may be included in the RRCReconfiguration message. In some embodiments, this information may be included in the RRCRelease message, which includes suspendConfig. In some embodiments, this information may be included in the information element (IE) sdt-Config.

[0066] In some embodiments, this information may include a set of radio bearers (RBs), i.e., one or more RBs. In some embodiments, network entity 102 may configure the set of RBs for SDT to UE 104. That is, the set of RBs is associated with SDT. In some embodiments, the RBs in the set of RBs may be signal radio bearers (SRBs). In some embodiments, the RBs in the set of RBs may be data radio bearers (DRBs).

[0067] In some embodiments, the information may include operations associated with Network Energy Saving (NES). In some embodiments, network entity 102 may configure NES-related configurations to UE 104. In some embodiments, NES-related configurations may be Discontinuous Transmission (DTX) configurations. In some embodiments, NES-related configurations may be Discontinuous Reception (DRX) configurations. In some embodiments, the information may include the duration during which network entity 102 does not perform transmission or reception, such as the duration of cell DRX shutdown or cell DTX shutdown.

[0068] In some embodiments, the information may include a threshold for determining the validity of a resource. In some embodiments, the threshold may be associated with a Resource Block (RB). In other words, the threshold may be configured per RB. In some embodiments, the information may include a set of thresholds associated with a set of RBs.

[0069] In some embodiments, the threshold may be associated with a logical channel (LCH). In other words, the threshold can be configured per LCH. In some embodiments, this information may include a set of thresholds associated with a set of LCHs.

[0070] In some embodiments, the threshold may be associated with a logical channel group (LCG). In other words, the threshold can be configured per LCG. In some embodiments, this information may include a set of thresholds associated with a set of LCGs.

[0071] In some embodiments, the threshold may be associated with the DRB set used for SDT (also referred to herein as the SDT-DRB set). In other words, the threshold may be a common threshold for all SDT-DRBs used for SDT-DRB. In some embodiments, the threshold may be associated with the SRB set used for SDT (also referred to herein as the SDT-SRB set). In other words, the threshold may be a common threshold for all SDT-SRBs used for SDT-SRB. In some embodiments, the threshold may be associated with the RB set used for SDT (also referred to herein as the SDT-RB set).

[0072] In some embodiments, this information may include reference values ​​for determining the availability of resources. These reference values ​​may be used to determine the timing of uplink data transmissions (e.g., PUSCH) during the RA process.

[0073] It should be understood that the information used to assess the effectiveness of resources used for SDT may include any combination of the information described above. In some alternative embodiments, the information used to assess the effectiveness of resources used for SDT may be predefined.

[0074] Continue to refer to Figure 2 UE 104 can use this information to determine the validity of the resources 220 uses for SDT. (Reference) Figure 2 UE 104 can determine that 221 needs to perform SDT. In some embodiments, UL data associated with SDT can reach UE 104. In this case, UE 104 can trigger the MO-SDT procedure. In some embodiments, UE 104 can receive a paging message associated with SDT from network entity 102. That is, the MT-SDT procedure can be triggered.

[0075] In some embodiments, the SDT may include the initial transmission of the SDT. In some embodiments, the SDT may include subsequent transmissions of the SDT.

[0076] refer to Figure 2 When determining whether to perform SDT, UE 104 can select resource 222 for SDT. UE 104 can use this resource to send UL data during MO-SDT or to send a response to a paging message during MT-SDT.

[0077] In some embodiments, UE 104 may select CG-SDT resources for SDT. In some embodiments, UE 104 may select RA-SDT resources for SDT. In some embodiments, UE 104 may select non-SD TRA resources for SDT. It should be understood that selection may be made in any suitable manner, whether existing or developed in the future, and this disclosure is not limiting in this respect.

[0078] Continue to refer to Figure 2 UE 104 can determine whether the resource selected by 223 is valid, that is, evaluate the validity of the selected resource. If the selected resource is valid, UE 104 can use the selected resource for SDT.

[0079] In some embodiments for effectiveness assessment, UE 104 may determine the time interval between a point in time associated with the selected resource (also referred to herein as a first point in time for convenience) and a reference point in time. In some embodiments, the reference point in time may be the point in time when a paging message associated with the SDT is received. In some embodiments, the reference point in time may be the point in time when a response to the paging message is initiated. In some embodiments, the reference point in time may be the point in time when a recovery procedure for the SDT is initiated. In some embodiments, the reference point in time may be the point in time when data associated with the SDT arrives.

[0080] In some embodiments, if the time interval is below (i.e., less than or equal to) a threshold, UE 104 may determine that the selected resource is valid. In some embodiments, if the time interval is above (i.e., greater than or equal to) a threshold, UE 104 may determine that the selected resource is invalid. In other words, if the selected resource is further away than the sum of a reference time point and a threshold, UE 104 may determine that the selected resource is invalid.

[0081] In some embodiments, a threshold can be configured. In some embodiments, a threshold can be predefined.

[0082] In some embodiments where a set of thresholds associated with an RB set is configured or predefined, UE 104 may receive a paging message from network entity 102, the paging message including an indication of an RB in the RB set associated with an SDT. The paging message may be associated with or indicate an SDT. Based on the RB indication, UE 104 may determine a threshold associated with the indicated RB from the set of thresholds. In some embodiments, UE 104 may receive a paging message from network entity 102 including an indication of one or more values ​​or thresholds. The paging message may be associated with or indicate an SDT. Based on the indication of one or more values ​​or thresholds, UE 104 may select one of one or more values ​​or thresholds as the threshold associated with the indicated SDT.

[0083] In some embodiments, the threshold may be the latency requirement of an RB in the RB set used for SDT. In some embodiments, the threshold may be the most critical latency requirement of all RBs in the RB set. In some embodiments, the threshold may be the most critical latency requirement of all configured SDT DRBs in the configured SDT DRBs. In some embodiments, the threshold may be associated with the requirement of the RB with the highest priority in the RB set. In some embodiments, the threshold may be the latency requirement of the RB with the highest priority in the RB set. In some embodiments, the threshold may be the shortest remaining time in the pending, buffered, or arriving data that UE 104 will transmit. In some embodiments, the threshold may be the most critical latency requirement of the DL data that network entity 102 is to transmit.

[0084] In some embodiments, the threshold may be the latency requirement of an LCH in a set of LCHs used for SDT. In some embodiments, the threshold may be the most critical latency requirement among all configured SDT LCHs. In some embodiments, the threshold may be associated with the requirement of the LCH with the highest priority in the LCH set. In some embodiments, the threshold may be the latency requirement of the LCH with the highest priority in the LCH set. In some embodiments where a set of thresholds associated with an LCH set is configured or predefined, UE 104 may receive a paging message from network entity 102, the paging message including an indication of an LCH associated with SDT in the LCH set. Based on the LCH indication, UE 104 may determine a threshold associated with the indicated LCH from the set of thresholds.

[0085] In some embodiments, the threshold may be a duration configured by network entity 102. In some embodiments, network entity 102 may configure a timer as a duration. In some embodiments, network entity 102 may configure a time window as a duration. In some embodiments, the threshold may be a value of a timer configured by network entity 102. In some embodiments, if the timer expires before the selected resource, UE 104 may determine that the selected resource is invalid.

[0086] In some embodiments, if no NES-related configuration is configured for UE 104, UE 104 can determine that the selected resource is valid. In some embodiments, if the selected resource does not overlap with NES-related configurations, UE 104 can determine that the selected resource is valid. In some embodiments, if the selected resource does not overlap with a duration during which network entity 102 does not perform transmission or reception (e.g., cell DTX or DRX shutdown duration), UE 104 can determine that the selected resource is invalid. In some embodiments, if the selected resource does not overlap with a duration during which network entity 102 does not perform transmission or reception, UE 104 can determine that the selected resource is invalid.

[0087] In some embodiments, UE 104 may determine that the selected resource is invalid if the timer expires before the selected resource (e.g., before the start point of the selected resource in the time domain) and if the NES-related configuration has not been configured for UE 104. In some embodiments, UE 104 may determine that the selected resource is invalid if the selected resource overlaps with the NES-related configuration and the next available SDT resource does not overlap with the NES-related configuration, and if the next available SDT resource, which is the first resource that does not overlap with the NES-related configuration, is further away than the sum of the reference time point and the threshold.

[0088] In some embodiments, UE 104 may determine the allowed uplink data transmission duration (e.g., maxPUSCH duration) associated with an RB in the set of RBs used for SDT. If the uplink data transmission (e.g., PUSCH) duration associated with the selected resource is less than (i.e., less than or equal to) the allowed uplink data transmission duration associated with the RB, UE 104 may determine that the selected resource is valid. If the uplink data transmission duration associated with the selected resource is greater than (i.e., greater than or equal to) the allowed uplink data transmission duration associated with the RB, UE 104 may determine that the selected resource is invalid.

[0089] In some embodiments, if the maxPUSCH duration configured for the logical channel(s) where data arrives at the SDT and(s) logical channels(s) configured, or the maxPUSCH duration configured (if configured) for the highest priority logical channel among the logical channels where data arrives at the SDT and(s) logical channels(s) configured, is less than the PUSCH transmission duration associated with the UL grant, then UE 104 may determine that the selected resource is invalid.

[0090] In some embodiments, if the selected resource does not overlap with NES-related configurations, and if the maxPUSCH duration configured for the logical channel(s) where data arrives at the SDT and(s) logical channels(s) configured, or the maxPUSCH duration configured (if configured) for the highest priority logical channel(s) where data arrives at the SDT and(s) logical channels(s) configured, is less than the first PUSCH transmission duration associated with UL authorization, then UE 104 may determine that the selected resource is invalid.

[0091] In some embodiments, if the selected resource overlaps with the cell DTX or DRX off duration and the next resource does not overlap with the cell DTX or DRX off duration, and if the maxPUSCH duration configured for a logical channel where data arrives at SDT and(s) is configured, or the maxPUSCH duration configured for the highest priority logical channel among the logical channels where data arrives at SDT and(s) is configured (if configured), is less than the next PUSCH transmission duration associated with UL grant, then UE 104 may determine that the selected resource is invalid.

[0092] In some embodiments, UE 104 may determine that the selected resource is invalid if the selected resource is further away than the sum of a threshold and the time point at which paging is received for MT-SDT. In some embodiments, UE 104 may determine that the selected resource is invalid if the selected resource overlaps with an NES-related configuration and the next available SDT resource does not overlap with an NES-related configuration, and if the next available SDT resource (which is the first available resource that does not overlap with an NES-related configuration) is further away than the sum of a threshold and the time point at which paging is received for MT-SDT.

[0093] In some embodiments, UE 104 may determine that the selected resource is invalid if the selected resource is further away than the sum of a threshold and the arrival time of the UL small data, or if the lower layer receives an indication that the upper layer's UL small data has arrived. In some embodiments, UE 104 may determine that the selected resource is invalid if the selected resource overlaps with an NES-related configuration and the next available SDT resource that does not overlap with an NES-related configuration, and if the next available SDT resource (which is the first available resource that does not overlap with an NES-related configuration) is further away than the sum of a threshold and the time point for receiving a paging message for MT-SDT.

[0094] In some embodiments, UE 104 may select a carrier for initiating SDT (hereinafter also referred to as the first carrier for convenience). If no resources are available on the first carrier and resources are available on another carrier (hereinafter also referred to as the second carrier for convenience), UE 104 may perform carrier reselection to the second carrier. In this way, UE 104 can select available resources on the second carrier for SDT.

[0095] In some embodiments, the first carrier may be a normal uplink (NUL) carrier, and the second carrier may be a supplementary uplink (SUL) carrier. In some embodiments, the first carrier and the second carrier may be NUL carriers. In some embodiments, the first carrier and the second carrier may be SUL carriers. In some embodiments, the first carrier may be an SUL carrier, and the second carrier may be a NUL carrier.

[0096] In some embodiments where the selected resource is a RA-SDT resource, the validity of the RA-SDT resource can be determined based on the timing of preamble transmission (e.g., Physical Random Access Channel (PRACH)). In some embodiments, the first time point can be the preamble transmission timing associated with the selected resource. In some embodiments, the threshold can be a second time point associated with an invalid CG resource for the SDT (which is the next CG-SDT resource for the SDT).

[0097] In some embodiments where the selected resource is a RA-SDT resource, the validity of the RA-SDT resource can be based on the timing of uplink data transmissions (e.g., PUSCH) during the RA process. In some embodiments, a first time point can be determined based on the timing of uplink data transmissions during the RA process. In some embodiments, the uplink data transmission timing can be determined based on the timing of preamble transmissions (e.g., PRACH) associated with the selected resource and a reference value. In some embodiments, the reference value can be 0.

[0098] In some embodiments, a reference value may be determined based on a Random Access Response (RAR) window. In some embodiments, a reference value may be determined based on a Round-Trip Time (RTT) value. In some embodiments, a reference value may be determined based on the duration (e.g., k2) from the reception of a downlink scheduling signal to the reception of an uplink grant. In some embodiments, a reference value may be determined based on the duration from the transmission of a preamble to the reception of a downlink scheduling signal. In some embodiments, a reference value may be determined based on a processing delay (e.g., an increment of the processing delay). It should be understood that the reference value may be determined by any combination of the above information or by any other suitable means.

[0099] This concludes the description of the effectiveness assessment of resources used in SDT. Using procedure 200, effective resources can be identified for SDT, thereby improving communication efficiency.

[0100] Figure 3 An example of a device 300 supporting the evaluation of resources for SDT according to various aspects of this disclosure is shown. Device 300 may be an example of UE 104 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).

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

[0102] In some implementations, processor 302, memory 304, transceiver 306, or various combinations thereof, 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 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).

[0103] For example, according to the examples disclosed herein, processor 302 may support wireless communication at device 300. Processor 302 may be configured to operatively support components for receiving configuration from network entity 102, the configuration including: information for evaluating the availability of resources for small data transmission, and based on that information, determining the availability of the resources.

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

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

[0106] 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... Or another known operating system. In some implementations, the I / O controller 308 may be implemented as part of a processor (such as processor 306). In some implementations, a user can interact with device 300 via the I / O controller 308 or via hardware components controlled by the I / O controller 308.

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

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

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

[0110] Figure 4An example of a device 400 supporting the evaluation of resources for SDT according to various aspects of this disclosure is shown. 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., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

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

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

[0113] For example, according to the examples disclosed herein, processor 402 may support wireless communication at device 400. Processor 402 may be configured to operatively support components for transmitting configuration to UE 104, including: configuration of information for evaluating the effectiveness of resources for small data transmission.

[0114] 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 use a memory controller to operate a memory array. 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.

[0115] 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 another type 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) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0116] 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... Or another known operating system. In some implementations, the I / O controller 408 may be implemented as part of the processor (e.g., processor 406). In some implementations, the user can interact with the device 400 via the I / O controller 408 or via hardware components controlled by the I / O controller 408.

[0117] In some implementations, device 400 may include a single antenna 410. However, in other implementations, device 400 may have more than one antenna 410 (i.e., 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.

[0118] 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 410 for transmitting the amplified signal over the air or wireless medium.

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

[0120] Figure 5An example of a processor 500 supporting the evaluation of resources for SDT 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 optionally, processor 500 may optionally include one or more arithmetic logic units (ALUs) 506. These components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

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

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

[0123] 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, such that processor 500 supports 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.

[0124] 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., remotely to processor 500).

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

[0126] 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 can 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.

[0127] Processor 500 may support wireless communication according to the examples described herein. Processor 500 may be configured or operable to support components for acquiring configuration including: information for evaluating the effectiveness of resources for small data transmission, and determining the effectiveness of resources based on that information.

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

[0129] In box 605, method 600 may include: receiving configuration from network entity 102, the configuration including information for evaluating the effectiveness of resources used 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 derived from, as referenced... 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: a set of radio bearers, operations associated with network power saving, a threshold for determining the effectiveness of resources, or a reference value for determining the effectiveness of resources.

[0131] In some embodiments, the threshold may be associated with at least one of the following: radio bearers, a set of data radio bearers for small data transmission, a set of signaling radio bearers for small data transmission, a logical channel, or a group of logical channels.

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

[0133] In some embodiments, determining the validity of a resource may include: determining a time interval between a first time point associated with the resource and a reference time point; determining that the resource is valid if the determined time interval is below a threshold; and determining that the resource is invalid if the determined time interval is above a threshold.

[0134] In some embodiments, the reference time point may be one of the following: the time point at which a paging message associated with a small data transmission is received, the time point at which a response to the paging message is initiated, the time point at which a recovery process is initiated for the small data transmission, or the time point at which the data associated with the small data transmission arrives.

[0135] In some embodiments, the threshold may be the latency requirement of radio bearers in a set of radio bearers used for small data transmission.

[0136] In some embodiments, the information may include a set of thresholds associated with a set of radio bearers. In these embodiments, method 600 may further include: receiving a paging message from network entity 102, the paging message including: an indication of radio bearers in the set of radio bearers associated with small data transmission; and determining a threshold associated with a radio bearer from the set of thresholds.

[0137] In some embodiments, the threshold may be a timer value or a time window configured by the base station.

[0138] In some embodiments, the first time point may be the timing of a preamble transmission associated with a resource. In some embodiments, the threshold may be a second time point associated with a configuration-authorized resource for small data transfers, which is invalid.

[0139] In some embodiments, the first time point may be determined based on the uplink data transmission timing during the random access procedure. In some embodiments, the uplink data transmission timing is determined based on the preamble transmission timing associated with the resource and a reference value.

[0140] In some embodiments, the reference value may be determined based on at least one of the following: random access response window, round-trip time value, duration from the reception of downlink scheduling signal to the reception of uplink authorization, duration from the transmission of preamble to the reception of downlink scheduling signal, or processing delay.

[0141] In some embodiments, determining the validity of a resource may include at least one of the following: determining that the resource is valid based on a determination that the duration of the period during which the base station does not perform transmission or reception does not overlap; or determining that the resource is invalid based on a determination that the duration of the period during which the base station does not perform transmission or reception overlaps.

[0142] In some embodiments, determining the validity of a resource may include: the allowed uplink data transmission duration associated with a radio bearer in a set of radio bearers used for small data transmission; determining the resource to be valid based on a determination that the uplink data transmission duration associated with the resource is less than the allowed uplink data transmission duration associated with the radio bearer; and determining the resource to be invalid based on a determination that the uplink data transmission duration associated with the resource is greater than the allowed uplink data transmission duration associated with the radio bearer.

[0143] In some embodiments, method 600 may further include: selecting a first carrier for initiating small data transmission; and performing carrier reselection to the second carrier based on the determination that there are no valid resources on the first carrier and resources are valid on the second carrier.

[0144] Figure 7 A flowchart illustrating another method 700 for evaluating 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.

[0145] In box 705, method 700 may include: sending configuration to UE 104, the configuration including information for evaluating the effectiveness of resources for small data transmission. The operation of 705 can be performed according to the examples described herein. In some implementations, aspects of the operation of 705 may be derived from, as referenced... Figure 1 The device described is used to perform this action.

[0146] In some embodiments, the information may include at least one of the following: a set of radio bearers, operations associated with network power saving, a threshold for determining the effectiveness of resources, or a reference value for determining the effectiveness of resources.

[0147] In some embodiments, the threshold may be associated with at least one of the following: radio bearers, a set of data radio bearers for small data transmission, a set of signaling radio bearers for small data transmission, a logical channel, or a group of logical channels.

[0148] In some embodiments, the threshold may be a timer value or a time window configured by the base station.

[0149] In some embodiments, the information may include a set of thresholds associated with a set of radio bearers. In these embodiments, method 700 may further include sending a paging message to UE 104, the paging message including an indication of radio bearers in the set of radio bearers associated with small data transmission.

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

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

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

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

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

[0155] 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 evaluating the effectiveness of resources for small data transmission; as well as Based on the information, the validity of the resource is determined.

2. The user equipment according to claim 1, wherein the information includes at least one of the following: Radio bearer collection, Operations related to network energy saving, A threshold used to determine the validity of the resource, or Reference values ​​used to determine the validity of the resource.

3. The user equipment of claim 2, wherein the threshold is associated with at least one of the following: Radio bearer, The set of data radio bearers used for the small data transmission Set of signaling radio bearers used for the small data transmission Logical channel, or Logical channel group.

4. The user equipment of claim 1, wherein the processor is configured to determine the validity of the resource by: Determine the time interval between a first time point and a reference time point associated with the resource; The resource is determined to be valid based on the determination that the time interval is below a threshold; and The resource is determined to be invalid if the time interval is determined to be higher than the threshold.

5. The user equipment according to claim 4, wherein the reference time point is one of the following: The time point at which the paging message associated with the small data transmission is received. The time point at which a response to the paging message is initiated. The time point at which the recovery process is initiated for the small data transmission, or The time point at which the data arrives in connection with the small data transmission.

6. The user equipment of claim 4, wherein the threshold is a delay requirement for radio bearers in the set of radio bearers used for the small data transmission.

7. The user equipment of claim 4, wherein the information includes a set of thresholds associated with a set of radio bearers, and wherein the processor is further configured to: The paging message is received from the base station via the transceiver, and the paging message includes: An indication of the radio bearers associated with the small data transmission in the set of radio bearers; as well as Determine the threshold associated with the radio bearer from the set of thresholds.

8. The user equipment according to claim 4, wherein the threshold is a timer value or time window configured by the base station.

9. The user equipment of claim 4, wherein the first time point is the preamble transmission timing associated with the resource.

10. The user equipment of claim 9, wherein the threshold is a second time point associated with a configuration authorization resource for the small data transmission, the configuration authorization resource being invalid.

11. The user equipment of claim 4, wherein the first time point is determined based on the uplink data transmission timing during the random access procedure.

12. The user equipment of claim 11, wherein the uplink data transmission timing is determined based on the preamble transmission timing and reference value associated with the resource.

13. The user equipment of claim 12, wherein the reference value is determined based on at least one of the following: Random access response window, Round-trip time value, The duration from the reception of the downlink scheduling signal to the reception of the uplink grant. The duration from the transmission of the preamble to the reception of the downlink scheduling signal, or Addressing delays.

14. The user equipment of claim 1, wherein the processor is configured to determine the validity of the resource by at least one of the following: The resource is determined to be valid based on the determination that the duration of the period during which the resource and the base station do not perform transmission or reception does not overlap; or The resource is determined to be invalid based on the determination that the duration of the resource overlaps with the duration during which the base station does not perform transmission or reception.

15. The user equipment of claim 1, wherein the processor is configured to determine the validity of the resource by: Determine the permissible uplink data transmission duration associated with each radio bearer in the set of radio bearers used for the small data transmission; The resource is determined to be valid based on the determination that the uplink data transmission duration associated with the resource is less than the allowed uplink data transmission duration associated with the radio bearer; as well as The resource is determined to be invalid based on the determination that the duration of the uplink data transmission associated with the resource is higher than the allowed duration of the uplink data transmission associated with the radio bearer.

16. The user equipment of claim 1, wherein the processor is further configured to: Select a first carrier for initiating the small data transmission; and Based on the determination that there are no valid resources on the first carrier and resources are valid on the second carrier, carrier reselection is performed on the second carrier.

17. 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 processor: Obtain configuration, which includes information for evaluating the effectiveness of resources used for small data transfer; as well as Based on the information, the validity of the resource is determined.

18. 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 for evaluating the effectiveness of resources for small data transmission.

19. The base station of claim 18, wherein the information includes at least one of the following: Radio bearer collection, Operations related to network energy saving, A threshold used to determine the validity of the resource, or Reference values ​​used to determine the validity of the resource.

20. A method performed by a user equipment, the method comprising: Receive configuration from base station, the configuration including: information for evaluating the effectiveness of resources for small data transmission; and Based on the information, the validity of the resource is determined.

Images