Mechanism for transmission through configured concession

ES3078606T3Undetermined Publication Date: 2026-09-15NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
ES2021933674T
Authority / Receiving Office
ES · ES
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-30
Publication Date
2026-09-15
Estimated Expiration
2041-03-30

Smart Images

  • Figure 00000016_0000
    Figure 00000016_0000
  • Figure 00000016_0001
    Figure 00000016_0001
  • Figure 00000017_0000
    Figure 00000017_0000
Patent Text Reader

Abstract

A mechanism is provided for transmitting data with configured permissions. If a small data transmission is required, a first device determines whether a timestamp is valid on a subsequent occasion with permissions configured for that transmission. The first device also determines whether a validity condition assessment is applicable on a subsequent occasion with permissions configured for the small data transmission. If the timestamp is valid and the assessment is applicable, the first device performs the small data transmission on the subsequent occasion with configured permissions. In this way, the first device can perform the validity condition assessment in advance, thus reducing delays and preventing failures.
Need to check novelty before this filing date? Find Prior Art

Description

Mechanism for transmission through configured concession Field Realizations in the present description generally refer to communication techniques and, more particularly, to computer-readable methods, devices, and media for configured concession transmissions. Background With the development of communication systems, new technologies have been proposed. For example, to increase the utilization rate of periodically allocated resources, the communication system can allow multiple devices to share these resources using a configured lease (CG) mechanism. The base station allocates the configured lease resources to multiple terminal devices, and the terminal devices use the resources randomly when they have data to transmit. By allocating configured lease resources, the communication system eliminates packet transmission delays caused by scheduling requests. Summary In general, embodiments of the present description relate to a method for lease-based transmissions configured with the corresponding devices. A first device, a method, a system, and a computer-readable storage medium are provided, as defined in the separate claims. Brief description of the drawings Some illustrative embodiments will now be described with reference to the accompanying drawings, where: Figures 1A-1C illustrate schematic diagrams of Small Volume Data Transmission (SDT) solutions, respectively; Figure 2 illustrates a schematic diagram of a communication system according to the embodiments described herein; Figure 3 illustrates a schematic diagram of interactions between devices according to the embodiments described herein; Figure 4 illustrates a schematic diagram of a concession configuration configured according to realizations of the present description; Figure 5 illustrates a flowchart of a method according to realizations of the present description; Figure 6 illustrates a flowchart of a method according to realizations of the present description; Figure 7 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present description; and Figure 8 illustrates a block diagram of an illustrative computer-readable medium according to some illustrative realizations of the present description. Throughout the drawings, the same numbers or similar reference numbers represent the same or a similar item. Detailed description The principle of this description will now be detailed with reference to some illustrative embodiments. It should be understood that these embodiments are described for illustrative purposes only and will assist those skilled in the art in understanding and implementing this description, without implying any limitation as to its scope. The description set forth herein may be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms employed herein have the same meaning as they are commonly understood by a person skilled in the art to which this description pertains. References in this specification to "an embodiment," "the embodiment," "an illustrative embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Furthermore, such expressions do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in relation to an illustrative embodiment, it is understood that it is within the knowledge of a person skilled in the art to affect that feature, structure, or characteristic in relation to other embodiments, whether explicitly described or not. It is understood that, although the terms "first" and "second," etc., may be used in this specification to describe various elements, these elements shall not be limited by these terms. These terms are used only to distinguish one element from another.For example, a first element could be called a second element, and similarly, a second element could be called a first element, without departing from the scope of the illustrative realizations. As used herein, the term "and / or" includes any and all combinations of one or more of the terms indicated. The terminology used in this report is solely for the purpose of describing particular realizations and is not intended to limit illustrative realizations. As used herein, the singular forms "a," "one," "the," and "a" are intended to include the plural forms, unless the context clearly indicates otherwise. It is further understood that the terms "comprises," "comprising," "has," "having," "includes," and / or "including," when used herein, specify the presence of mentioned features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used in this application, the term "circuitry" may refer to one, more, or all of the following concepts: (a) Hardware-only circuit implementations (such as implementations in exclusively analog and / or exclusively digital circuitry) and (b) combinations of physical circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of the hardware processor(s) with software (including digital signal processors, software and memories that work together to make a device, such as a mobile phone or server, perform various functions) and (c) hardware circuit(s) and / or processor(s), such as microprocessor(s) or part of microprocessor(s), which requires software (e.g., firmware) for operation, but the software may not be present when it is not required for operation. This definition of circuitry applies to all uses of this term in this application, including any claims. By way of further example, as used in this application, the term circuitry also covers an implementation of just a hardware circuit or a processor (or multiple processors) or a portion of a hardware circuit or a processor and its accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile phone or a similar integrated circuit in a server, cellular network device, or other computing or networking device. As used herein, the term "communication network" refers to a network that adheres to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Broadband Internet of Things (NB-IoT), New Radio (NR), and so forth. Furthermore, communication between a terminal device and a network device within the communication network may be conducted using any suitable generation communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and / or any other protocol currently known or that may be developed in the future.The realizations described here can be applied to various communication systems. Given the rapid development of communications, there will, of course, be future communication technologies and systems with which this description can be implemented. The scope of this description should not be limited to the system mentioned above. As used in this document, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from it. The network device may refer to a base station (BS) or an access point (AP), for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a remote radio NB (also called a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node such as a femto, a pico, and so on, depending on the terminology and technology used. The term "terminal device" refers to any end device capable of wireless communication. For illustrative purposes, rather than as a limitation, a terminal device may also be called a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cell phones, smartphones, Voice over IP (VoIP) phones, cordless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), laptops, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, and mobile stations.Laptop-integrated equipment (LEE), laptop-mounted equipment (LME), USB backpacks, smart devices, wireless customer premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial environment and / or automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably. As mentioned previously, configured concession (CG)-based uplink transmission has been proposed. According to some technologies, small-volume data transmission can be supported. Figure 1A shows a schematic interaction diagram for SDT based on a 4-stage random access channel (RACH) (i.e., 4-stage RA-SDT). As shown in Figure 1A, a terminal device 110 can transmit message 1 (MSG 1) to a network device 120 when terminal device 110 is in a radio resource control (RRC) idle state. MSG 1 comprises a preamble to the RACH. Network device 120 can then transmit message 2 (MSG 2) to terminal device 110. MSG 2 comprises a random access response. Terminal device 110 can transmit a message 3 (MSG 3) to network device 120. MSG 3 comprises a request to resume RRC connection.A small payload (i.e., small volume data) can be transmitted on MSG 3. For example, the small payload can be multiplexed with the RRC connection resumption request. Network device 120 can transmit an RRC release message. Figure 1B shows a schematic interaction diagram for a 2-stage RACH-based SDT (i.e., a 2-stage RA-SDT). As shown in Figure 1B, when terminal device 110 is in the RRC idle state, terminal device 110 transmits message A (MSG A) to network device 120. MSG A may contain a preamble for the RACH. Small volume data can be transmitted with MSG A. In particular, small volume data can be transmitted over the uplink shared physical channel (PUSH) resources that are preconfigured by network device 120 and transmitted in the system information with the associated physical transmission parameters. Network device 120 then transmits message B (MSG B) to terminal device 110. MSG B contains a random access response. Figure 1C shows a schematic interaction diagram for the configured concession-based SDT (i.e., CG-SDT). When terminal device 110 is in an RRC-connected state, terminal device 110 can receive a CG configuration of type 1 (1210) indicating specific preconfigured PUSCH resources to be used for UL data transmission in an idle RRC, provided the timing alignment is valid. Network device 120 can then transmit an RRC release message (1220). In wireless systems, it is necessary to adjust the timing of an uplink frame to align with a downlink frame in the time domain. According to some conventional technologies, the timing lead (TA) value corresponds to the time it takes for a signal to travel from the terminal device to the network device. Timing lead adjustment can occur either during the RACH procedure (for example, using the timing lead command) or during normal terminal device operation in the RRC connected state. The term "timing lead command (TAC)" used herein may refer to a command sent by a network device to a terminal device to adjust its current timing lead and apply it to an uplink transmission.This means that the terminal device transmits a certain number of UL symbols to the network associated with a specific UL frame, ahead of the corresponding DL frame, according to the received command. This applies, for example, to PUSCH transmissions, the physical uplink control channel (PUCCH), and the sound reference signal (SRS). Essentially, the TAC can inform the terminal device of the amount of time it needs to advance the UL transmissions. According to some conventional technologies, CG-SDT selection is prioritized over random access-based SDT (i.e., RA-SDT). However, the terminal device is required to perform several (sequential) evaluations before it can select the transmission type using CG-SDT and a CG-SDT resource to perform a UL data transmission when in the RRC idle state. In some implementations, the terminal device is likely to initiate an evaluation procedure shortly after data arrives in its buffer to minimize the delay in selecting the transmission type (e.g., selecting between CG-SDT and RA-SDT). This is beneficial, for example, because evaluations based on the received reference signal power (RSRP) included in the procedure may require new RSRP measurements to be taken on subsequent available SSB transmission opportunities. Furthermore, if the CG-SDT selection result is unsatisfactory, the evaluation may need to continue to determine whether a 2-stage or 4-stage RA-SDT could be selected instead, which would take more time. However, if the terminal device performs the evaluation procedure shortly after the data arrives, but the CG periodicity value, configured for the CG resource selected for CG-SDT transmission, is large (e.g., 160-640 ms), this implies that there may be a certain delay (e.g., up to 640 ms) between the time the next occurrence of the selected CG resource is available and the time the UE made the CG resource selection. To address at least some of the aforementioned problems and other potential issues, solutions for configured-lease transmissions are proposed. According to embodiments of this description, if a small-volume data transmission is required, a first device determines whether a timing advance is valid in a subsequent configured-lease (CG) event for the small-volume data transmission. The first device also determines whether a validity condition assessment is applicable in the next CG event for the small-volume data transmission. If the timing advance is valid and the assessment is applicable, the first device performs the small-volume data transmission in the next CG event. In this way, the first device can perform the validity condition assessment in advance, thereby reducing delays and preventing failures. Figure 2 illustrates a schematic diagram of a communication system in which embodiments of the present description may be implemented. The communication system 200, which is part of a communication network, comprises a first device 210-1, a first device 210-2, and a first device 210-3, ..., a first device 210-N, which may be collectively referred to as the "first devices 210". The communication system 200 further comprises a second device 220. It should be understood that the number of devices shown in Figure 2 is for illustrative purposes only and does not imply any limitation. The communication system 200 may comprise any suitable number of devices and cells. In the communication system 200, the first device 210 and the second device 220 may communicate data and control information with each other.If the first device 210 is a terminal device and the second device 220 is the network device, a link from the second device 220 to the first device 210 is called a downlink (DL), while a link from the first device 210 to the second device 220 is called an uplink (UL). The number of devices shown in Figure 2 is provided for illustrative purposes only and does not imply any limitation. Communications in the 200 communication system can be implemented according to any suitable communication protocols, and include, but are not limited to, first generation (1G), second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G) cellular communication protocols and the like, wireless local area network communication protocols such as the Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocol currently known or that may be developed in the future.Furthermore, communication may utilize any suitable wireless communication technology, and includes, but is not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDMA), and / or any other technology currently known or that may be developed in the future. Illustrative embodiments of the present description will be described in detail below with reference to the accompanying drawings. Reference is made to Figure 2 below, which shows a signaling flow 200 according to some illustrative embodiments of the present description. For illustrative purposes only, the signaling flow 200 involves the first device 210-1 and the second device 220. The second device 220 transmits a configured lease (CG) transmission resource configuration to the first device 210-1. The term "configured lease transmission" used herein may refer to a transmission without a dynamic lease. For example, there may be two types of dynamic lease-free transmission: configured lease type 1 and configured lease type 2. For configured lease type 1, RRC signaling may provide an uplink lease and store it as a configured uplink lease. For configured lease type 2, an uplink lease may be provided, for example, by a PDCCH and stored or deleted as a configured uplink lease based on a physical layer signal (for example, a PDCCH DCI) indicating configured enable or disablement.In some implementations, the resource configuration can be transmitted using RRC signaling. Alternatively, the resource configuration can be transmitted using PDCCH signaling. Both Type 1 and Type 2 leases can be configured per service cell and per bandwidth portion (BWP). For Type 2 leases, activation and deactivation can be independent across service cells. When using a Type 1 configured lease, the resource configuration can include one or more of the following parameters: a Configured Schedule Radio Network Time Identifier (CS-RNTI) for retransmission; the periodicity of the Type 1 configured lease; a time-domain offset of a resource from a system frame number; time-domain parameters including a start symbol and the length of an allocation; and the number of Hybrid Automatic Repeat Request (HARQ) processes.Alternatively, when using configured lease type 2, the resource configuration can include one or more of the following parameters: a CS-RNTI for activation, deactivation, and retransmission; the periodicity of the configured lease type 2; and the number of HARQ processes. Figure 4 shows an example for configuring transmission using CG. As shown in Figure 4, there are multiple CG instances: 410-1, 410-2, 410-3, and 410-4. Note that the number of CG instances shown in Figure 4 is merely an example, not a limitation. Data can be transmitted during the CG instances. In some embodiments, the first 210-1 device can compare the data volume of the generated data with a data volume threshold. For example, if the data volume of the data generated at time 420 exceeds the data volume threshold, the first 210-1 device can determine that small-volume data transmission is not applicable to the data generated at time 420. Alternatively, if the data volume of the data generated at time 420 is below the data volume threshold, the first 210-1 device can determine that small-volume data transmission is applicable to the data generated at time 420. The data volume threshold can be configured by the second 220 device. Alternatively, the data volume threshold can be preconfigured. Additionally, the first 210-1 device can determine whether a data radio carrier from the SDT is valid. Returning to Figure 3, the first device 210-1 determines whether a timing advance is valid in the next CG event for a small-volume data transmission based on a first timer and the resource configuration. This allows it to avoid a fault recovery procedure or delay the start of RA-SDT. For example, as shown in Figure 4, the data for the small-volume data transmission can be generated by the first device 210-1 at time 420. In this situation, CG event 410-2 can be considered the next CG event. The first timer can be associated with the timing advance. In some embodiments, the first timer can be a timing advance timer (TAT). For example, the timing advance is still valid when the first timer is running. The timing advance may no longer be valid after the first timer has expired. The duration / value of the first timer can be set by the second device 220. As an example shown in Figure 4, the first device 210-1 can determine whether the first timer continues running until the event of CG 410-2. If the first timer continues running until the event of CG 410-2, the first device 210-1 can determine that the timing advance is valid at the event of CG 410-2.Alternatively, if the first timer expires before the CG 410-2 event, the first 210-1 device can determine that the timing advance is not valid on the CG 410-2 event. In some embodiments, if the SDT procedure is initiated for data generated at time 420, the first device 210-1 can select the SDT type for the data. For example, the first device 210-1 can select either a CG-based or RA-based SDT for the data. In this situation, the first device 210-1 can determine whether the timing advance is valid on the next CG occurrence during the SDT type selection. If the timing advance is valid on the next CG occurrence, the first device 210-1 can select a CG-based SDT. Alternatively, if the timing advance is not valid on the next CG occurrence, the first device 210-1 can select an RA-based SDT. Alternatively, the first device 210-1 can determine whether the first timer continues running until the next CG event plus a configured retransmission timer. The retransmission timer can be configured by the second device 220. In this situation, if the first timer continues running until the next CG event plus the configured retransmission timer, the second device 220 can determine that the timing advance is valid. Alternatively, if the first timer expires before the next CG event plus the configured retransmission timer, the second device 220 can determine that the timing advance is invalid. The first device, 210-1, performs a validity condition assessment. If the validity condition is met, the CG-based SDT can be selected. For example, the first device, 210-1, can measure the current cell's received reference signal power (RSRP) from the second device, 220. In this case, the first device, 210-1, can compare the measured RSRP to an RSRP threshold. If the measured RSRP exceeds the RSRP threshold, the validation condition is met. In other words, in this case, the assessment indicates that the validation condition is met. If the measured RSRP is below the RSRP threshold, the validation condition is not met. In this situation, the assessment indicates that the validation condition is not met. Alternatively or additionally, the first 210-1 device can determine whether a service beam is valid. For example, the first 210-1 device can measure the RSRP of the synchronization (SS) signal in the service beam. In this case, the first 210-1 device can compare the measured SS-RSRP with an SS-RSRP threshold. If the measured SS-RSRP exceeds the SS-RSRP threshold, the validation condition is met. In other words, in this case, the evaluation indicates that the validation condition is met. If the measured SS-RSRP is below the SS-RSRP threshold, the validation condition is not met. In this situation, the evaluation indicates that the validation condition is not met. The validity condition comprises a TA validity condition based on RSRP. For example, the first 210-1 device can determine a change in the SS RSRP. In this case, the first 210-1 device can compare the SS-RSRP change with a change threshold. The change threshold can comprise an increase threshold or a decrease threshold. The validity condition assessment can be performed at any suitable time. In some embodiments, the first device 210-1 can optimize the timing of the validity condition assessment based on a second timer (i.e., the validity timer) and the timing of the next CG event. For example, the first device 210-1 can perform the validity condition assessment before the next CG event by means of a time offset. As shown in Figure 4, the first device 210-1 can perform the assessment at time 440, which is prior to the CG event 410-2, by means of the time offset 430. In some embodiments, the time offset can be the minimum time requirement for performing the validity condition assessment. It should be noted that the time offset can be any suitable value. The embodiment described herein is not limited to this aspect.The first device 210-1 determines whether a validity condition assessment is applicable to the next CG occasion based on a second timer and resource settings. The first device 210-1 can apply the second timer to the validity condition assessment applicable to the CG-SDT. In other words, the assessment (i.e., the validity condition met / not met) can remain valid for a certain period after the assessment is performed according to the second timer. For example, as shown in Figure 4, the first device 210-1 can perform the assessment before occasion 410-2, and the first device 210-1 can determine whether the validity condition assessment remains applicable to CG occasion 410-2. In some embodiments, the second timer can be applied to any RSRP-based validity condition. For example, the second timer can be applied to an RSRP-based beam validity condition. The second timer can be configured by the second 220 device. For example, the second 220 device can transmit a second timer configuration that specifies the duration of the second timer. Alternatively, the second timer can be preconfigured. For example, the second timer can be a default timer that is pre-configured. In other embodiments, the first 210-1 device may not apply the second timer. Alternatively, the second timer can be determined based on a subcarrier spacing (SCS) used for a base waveform (BWP) in which the CG resources are configured. In some implementations, considering the RSRP-based condition for TA validation, this is based on the lack of a significant change in RSRP values. The TA may remain valid during the second timer as long as the first 210-1 device does not move beyond a threshold distance. In this case, the threshold distance can be relative to the SCS. For example, if an SCS is 120 kHz, the threshold distance might be 9 m, which corresponds to the spatial TA tuning granularity of the 120 kHz SCS (as shown in Table 1 below), where Tc and µ are, respectively, the basic time unit for new radio (NR) and the subcarrier spacing setting. Table 1 If the first 210-1 device is moving at 50 km / h (i.e., 13.8 m / s), it can travel approximately 9 m in approximately 640 ms. Thus, the second timer, which is up to 640 ms, can be used for low / medium mobile UEs, disregarding the portion of the TA's spatial granularity that may have already been consumed. In some illustrative embodiments, the second timer can depend on the difference between the observed RSRP change and the calculated change threshold at the time of RSRP-based validation. In one example, the second timer can be scaled based on the difference between the observed RSRP change and the calculated change threshold at the time of RSRP-based validation.Just as an example, assuming the second timer is 640 ms, the change in RSRP is 2 dB, an allowable change window of 5 dB (equivalent to the increase threshold plus the decrease threshold), and a remaining allowable change window of 3 dB (equivalent to the allowable change window minus the change in RSRP), the second scaled timer can be based on the second timer, the allowable change window, and the remaining allowable change window. In this case, the second scaled timer could be 640 ms * (3 dB / 5 dB), which is equivalent to 384 ms. Alternatively, the second timer can be configured if a high SCS is used for the BWP where the CG resources are configured, and no timer is configured if a low SCS is used. For example, if the SCS is above 60 kHz, the second timer can be configured. Conversely, if the SCS is below 60 kHz, the second timer may not be configured. In some embodiments, the first 210-1 device can perform a re-evaluation of the validity condition after the second timer expires. In this case, if the re-evaluation indicates that the validity condition is not met, the first 210-1 device can initiate the RA-based SDT. Alternatively, if the re-evaluation indicates that the validity condition is met, the first 210-1 device can initiate the second timer. The first device 210-1 performs the small-volume data transmission based on whether the timing advance is valid at the next CG event. In some embodiments, if the timing advance is valid, the first device 210-1 can perform the small-volume data transmission at the next CG event. For example, if the timing advance is valid at the next CG event and the validity condition is met at the next CG event, the first device 210-1 can initiate the CG-SDT at the next CG event. Alternatively, if the timing advance is not valid at the next CG event, the first device 210-1 can perform the small-volume data transmission in a random access (RA) procedure. For example, if the condition for RA-SDT is met, the small-volume data transmission can be performed in the RA procedure.In other embodiments, if the timing advance is invalid, the first 210-1 device can perform 3030 conventional volume data transmissions. For example, if the RA-SDT condition is not met, conventional volume data transmission can be performed. In some embodiments, small volume data transmission can be performed based on a data volume. Alternatively, small volume data transmission can be performed based on the received power of a reference signal. Implementations described herein allow the UE to perform the evaluation of the validity condition in advance. In this way, it can reduce delays and avoid failure scenarios. Figure 5 illustrates a flowchart of Method 500 according to the embodiments described herein. Method 500 can be implemented on any suitable device. For example, the method can be implemented on the first device, 210-1. In block 510, the first device 210-1 receives a transmit resource configuration via CG from the second device 220. For example, there can be two types of dynamic leaseless transmission: Configured Concession Type 1 and Configured Concession Type 2. For Configured Concession Type 1, RRC signaling can provide an uplink concession, which is then stored as a configured uplink concession. For Configured Concession Type 2, the PDCCH can provide an uplink concession and store or delete it as a configured uplink concession based on the physical layer signal indicating configured activation or deactivation. In some implementations, the resource configuration can be transmitted via RRC signaling. Alternatively, the resource configuration can be transmitted on the PDCCH signaling. In some embodiments, the first 210-1 device can compare the data volume of the generated data with a data volume threshold. For example, if the data volume of the generated data exceeds the data volume threshold, the first 210-1 device can determine that small-volume data transmission is not applicable to the generated data. Alternatively, if the data volume of the generated data is below the data volume threshold, the first 210-1 device can determine that small-volume data transmission is applicable to the generated data. The data volume threshold can be configured by the second 220 device. Alternatively, the data volume threshold can be preconfigured. Additionally, the first 210-1 device can determine whether a data radio carrier from the SDT is valid. In block 520, the first device 210-1 determines whether a timing advance is valid for a subsequent CG instance for small-volume data transmission based on a first timer and resource configuration. This allows it to avoid a fault recovery procedure or delay the start of RA-SDT. The first timer can be associated with the timing advance. For example, the timing advance is still valid when the first timer is running. The timing advance may no longer be valid after the first timer has expired. The duration / value of the first timer can be configured using the second device 220. Alternatively, the first device 210-1 can determine whether the first timer continues running until the next CG event plus a configured retransmission timer. The retransmission timer can be configured by the second device 220. In this situation, if the first timer continues running until the next CG event plus the configured retransmission timer, the second device 220 can determine that the timing advance is valid. Alternatively, if the first timer expires before the next CG event plus the configured retransmission timer, the second device 220 can determine that the timing advance is invalid. The first device, 210-1, performs a validity condition assessment. If the validity condition is met, the CG-based SDT can be selected. For example, the first device, 210-1, can measure the current cell's received reference signal power (RSRP) from the second device, 220. In this case, the first device, 210-1, can compare the measured RSRP to an RSRP threshold. If the measured RSRP exceeds the RSRP threshold, the validation condition is met. In other words, in this case, the assessment indicates that the validation condition is met. If the measured RSRP is below the RSRP threshold, the validation condition is not met. In this situation, the assessment indicates that the validation condition is not met. Alternatively or additionally, the first 210-1 device can determine whether a service beam is valid. For example, the first 210-1 device can measure the RSRP of the synchronization signal (SS) in the service beam. In this case, the first 210-1 device can compare the measured SS-RSRP with an SS-RSRP threshold. If the measured SS-RSRP exceeds the SS-RSRP threshold, the validation condition is met. In other words, in this case, the evaluation indicates that the validation condition is met. If the measured SS-RSRP is below the SS-RSRP threshold, the validation condition is not met. In this situation, the evaluation indicates that the validation condition is not met. The validity condition comprises a TA validity condition based on RSRP. For example, the first 210-1 device can determine a change in the SS RSRP. In this case, the first 210-1 device can compare the change in the SS-RSRP with a change threshold.The threshold of change can comprise an increase threshold or a decrease threshold. The validity condition assessment can be performed at any suitable time. In some embodiments, the first 210-1 device can optimize the timing of the validity condition assessment based on a second timer (i.e., the validity timer) and the timing of the next CG event. For example, the first 210-1 device can perform the validity condition assessment before the next CG event by means of a time lag. In some embodiments, the time lag may be the minimum time requirement for performing the validity condition assessment. It should be noted that the time lag may be of any suitable value. The embodiment described herein is not limited to this aspect.In block 530, the first 210-1 device determines whether a validity condition assessment is applicable to the next CG occurrence based on a second timer and resource configuration. The first 210-1 device can apply the second timer to the validity condition assessment applicable to the CG-SDT. In other words, the assessment (i.e., the validity condition met / not met) can remain valid for a certain period after the assessment is performed according to the second timer. In some embodiments, the second timer can be applied to any RSRP-based validity condition. For example, the second timer can be applied to an RSRP-based beam validity condition or an RSRP-based TA validity condition. The second timer can be configured by the second 220 device. For example, the second 220 device can transmit a second timer setting that specifies the duration of the second timer. Alternatively, the second timer can be preconfigured. For example, the second timer can be a pre-set default timer. In other embodiments, the first 210-1 device may not apply the second timer. Alternatively, the second timer can be determined based on a subcarrier spacing (SCS) used for a BWP in which the CG resources are configured. In some implementations, considering the RSRP-based condition for TA validation, this is based on the lack of a significant change in RSRP values. The TA may remain valid during the second timer as long as the first 210-1 device does not move beyond a threshold distance. In this case, the threshold distance may be relative to the SCS. Alternatively, the second timer may be set if a high SCS is used for the BWP in which the CG resources are configured, and no timer is set if a low SCS is used. In some implementations, the first 210-1 device may perform a re-evaluation of the validity condition after the second timer expires.In this case, if the re-evaluation indicates that the validity condition is not met, the first 210-1 device can initiate the RA-based SDT. Alternatively, if the re-evaluation indicates that the validity condition is met, the first 210-1 device can initiate the second timer. The first device 210-1 performs the small-volume data transmission based on whether the timing advance is valid at the next CG event. In some embodiments, if the timing advance is valid, the first device 210-1 can, in block 540, perform the small-volume data transmission at the next CG event. For example, if the timing advance is valid at the next CG event and the validity condition evaluation is applicable at the next CG event, the first device 210-1 can initiate the CG-SDT at the next CG event. Alternatively, if the timing advance is not valid at the next CG event and the evaluation indicating that the validity condition is met is applicable at the next CG event, in block 550, the first device 210-1 can perform the small-volume data transmission in a random access procedure.In other embodiments, if the timing advance is invalid and the evaluation is not applicable on the next CG occasion, the first 210-1 device can perform a conventional volume data transmission in block 560. Figure 6 illustrates a flowchart of Method 600 according to the embodiments described herein. Method 600 can be implemented on any suitable devices. For example, the method can be implemented on the second device, 220. In block 610, the second device 220 transmits a configured lease (CG) transmission resource configuration to the first device 210-1. The term "configured lease transmission" used herein may refer to a transmission without a dynamic lease. For example, there may be two types of dynamic lease-free transmission: configured lease type 1 and configured lease type 2. For configured lease type 1, RRC signaling may provide an uplink lease and store it as a configured uplink lease. For configured lease type 2, the PDCCH may provide an uplink lease and store or delete it as a configured uplink lease based on the physical layer signal indicating configured enable or disablement.In some implementations, the resource configuration can be transmitted using RRC signaling. Alternatively, the resource configuration can be transmitted using PDCCH signaling. In block 620, if the timing advance is valid on the next CG occasion for a small-volume data transmission, the second device 220 receives the small-volume data transmission on the next CG occasion. In some embodiments, the second device 220 can transmit to the first device 210-1 a setting that indicates the duration of a timer to determine whether an evaluation of a validity condition for the small-volume data transmission is applicable on the next CG occasion. Alternatively, if the timing advance is invalid and the evaluation is applicable, the second device 220 can receive the small-volume data transmission in a random access procedure. In other embodiments, if the timing advance is invalid and the evaluation is not applicable, the second device 220 can receive a conventional volume data transmission from the first device. In some implementations, after initiating the CG-SDT procedure, the first 210-1 device can also perform CG resource validation during the CG-SDT procedure. If the CG for SDT becomes invalid due to, for example, the expiration of the CG-SDT TAT, the CG-SDT beams becoming invalid, or the RSRP falling below or changing beyond the configured threshold, etc., the first 210-1 device performs the contingency procedure. The contingency procedure can be, for example, an RA-SDT procedure, an RRC resumption procedure, a normal RA procedure to request a UL resource, or actions that go to the RRC configuration request or IDLE procedure. In some cases, only the TAT expiration is checked during the CG-SDT procedure, and the beam / RSRP criteria are checked only when initiating the SDT procedure. In some implementations, different procedures could be performed depending on when the CG resource becomes invalid in the SDT procedure, for example, before or after receiving the response from the second 220 device. For instance, if the CG becomes invalid before receiving the response from the second 220 device to a CG transmission, the RA-SDT is performed if a valid RA-SDT resource is available; otherwise, the normal RRC resumption procedure is carried out, or the first 210-1 device can perform actions that lead to IDLE. In one example, data sent via CG can be preserved and retransmitted. Alternatively, the first 210-1 device can decode the entire NW receive window regardless of whether the CG becomes invalid before the window expires.If the CG becomes invalid after the first 210-1 device has received a response from the second 220 device, one of the following actions is performed: The SDT procedure continues with the normal RA procedure performed to request resources (and acquire the UL timing in case the TAT has expired), or RA-SDT is performed if a valid RA-SDT resource is available, or the SDT procedure is stopped and the normal resume procedure is performed. In some cases, different procedures may be performed depending on the reason the CG becomes invalid. For example, RA-SDT is performed if the CG resource becomes invalid due to TAT expiration, but the RSRP is still above the threshold for SDT. RA-SDT or the normal resume procedure is performed depending on whether the RSRP is above the threshold. If the CG resource becomes invalid because the RSRP is below the threshold or because the configured beams become invalid, RA-SDT is performed. In some implementations, the CG configuration for SDT is released or suspended after receiving the response from the second 220 device, and subsequent UL transmission(s) are based on dynamic scheduling. This can be reconfigured or resumed with the RRC release message when the SDT procedure is complete.In some implementations, the CG configuration for SDT is suspended, suspended for a specified period, or released if the CG resource becomes invalid during the SDT procedure. In some implementations, the CG configuration for SDT is suspended if it becomes invalid due to criteria other than TAT expiration, e.g., RSRP / beam criteria, and released if it becomes invalid due to TAT expiration. In some embodiments, an apparatus for carrying out method 500 (for example, the first device 210) may comprise respective means for carrying out the corresponding steps in method 500. These means may be implemented in any suitable manner. For example, they may be implemented by means of circuitry or software modules. In some embodiments, the apparatus comprises means for receiving, in a first device, a configured lease transmission resource configuration, CG, from a second device; means for determining whether a timing advance is valid in a subsequent CG instance for a small-volume data transmission based on a first timer and the resource configuration; and means for performing the small-volume data transmission in the subsequent CG instance based on the determination. In some embodiments, the means for determining whether the timing advance is valid comprise: means for determining whether the first timer remains running until the next CG occasion; and means for, based on a determination that the first timer remains running until the next CG occasion, determining that the timing advance is valid. In some examples, the means for determining whether the timing advance is valid comprise: means for, based on the determination that the small-volume data transmission has begun, determining whether the timing advance is valid during the selection of a transmission type for the small-volume data transmission, the transmission type comprising transmission by CG or a random access (RA) transmission. In some embodiments, the apparatus comprises means for selecting the type of transmission for small volume data transmission on the next CG occasion, before the next CG occasion, or when the data for small volume data transmission arrives. In some embodiments, the means for determining whether the timing advance is valid comprise: means for determining whether the first timer remains running until the next CG occasion plus a configured retransmission timer. In some embodiments, the apparatus further comprises means for determining whether an assessment of a validity condition for small volume data transmission is applicable on the next CG occasion based on a second timer and resource configuration. In some embodiments, the validation condition comprises a received power threshold of the reference signal, RSRP, and the apparatus further comprises means for measuring an RSRP on a reference signal received from the second device; and means for, based on a determination that a change in the RSRP exceeds an RSRP change threshold, determining that the validation condition is met. In some embodiments, the means for determining the evaluation of the validation condition for configured concession transmission that are applicable comprise: means for performing the evaluation of the validation condition; and means for, based on the determination that the second timer is running until the next CG occasion, determining that the evaluation of the validation condition is applicable. In some embodiments, the apparatus further comprises means for performing the evaluation of the validation condition before the next CG occasion by means of a time lag. In some embodiments, the time lag is a minimum time period for the processing requirement for the first device to perform the evaluation. In some embodiments, the apparatus further comprises means for determining a duration of the second timer based on at least one of: a configuration of the second timer received from the second device, or a spacing of subcarriers used for CG resources. In some embodiments, the apparatus further comprises means for, based on the determination that the second timer has expired, to perform a re-evaluation of the validity condition. In some embodiments, the apparatus further comprises means for, upon determining that the timing advance is invalid, performing the transmission of small volume data in a random access procedure. In some embodiments, the apparatus further comprises means for, upon determining that the timing advance is invalid, initiating a conventional volume data transmission procedure. In some embodiments, the means for performing small volume data transmission comprise: means for, according to a determination that the timing advance is valid and the evaluation of the validity condition for small volume data transmission is applicable at the next CG occasion, performing small volume data transmission at the next CG occasion. In some examples, the means for performing small volume data transmission comprise means for performing small volume data transmission on the next configured lease occasion based on the determination of at least one of: a small volume data transmission data volume or a power received from an RSRP reference signal. In embodiments, an apparatus for carrying out method 600 (for example, the second device 220) may comprise respective means for carrying out the corresponding steps in method 600. These means may be implemented in any suitable manner. For example, they may be implemented by means of circuitry or software modules. In some embodiments, the apparatus comprises means for transmitting, in a second device, a configured lease transmission resource configuration (CG) to a second device; and means for, based on a determination that a timing advance is valid on a subsequent CG instance for a small-volume data transmission, receiving the small-volume data transmission on the next CG instance. In some embodiments, the apparatus comprises means for transmitting to the first device a configuration indicating the duration of a timer to determine whether the evaluation of a validity condition for the small-volume data transmission is applicable on the next CG instance. In some embodiments, the apparatus comprises means for, according to a determination that the timing advance is invalid and the evaluation is applicable, receiving the small volume data transmission in a random access procedure. In some embodiments, the apparatus comprises means for, upon a determination that the timing advance is invalid and the evaluation is not applicable, receiving a conventional volume data transmission from the first device. Figure 7 is a simplified block diagram of a 700 device suitable for implementing the embodiments described herein. The 700 device can be provided to implement a communication device, for example, the 210 terminal device and the 220 network device, as shown in Figure 2. As shown, the 700 device includes one or more 710 processors, one or more 720 memories coupled to the 710 processor, and one or more 740 communication modules coupled to the 710 processor. The 740 communication module is for bidirectional communication. The 740 communication module has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements. The 710 processor can be of any type suitable for the local technical network and may include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on a multi-core processor architecture, as non-limiting examples. The 700 device may have multiple processors, such as an application-specific integrated circuit chip that is time-dependent to a clock that synchronizes the main processor. The 720 memory may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, a 724 read-only memory (ROM), an electrically programmable read-only memory (EPROM), flash memory, a hard disk, a compact disc (CD), a digital video disc (DVD), and other magnetic and / or optical storage.Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories whose contents are not retained during periods of power disconnection. A computer program 730 includes computer-executable instructions that are executed by the associated processor 710. The program 730 can be stored in ROM 724. The processor 710 can perform any appropriate action and processing by loading the program 730 into RAM 722. The realizations of the present description can be implemented by means of program 720 so that device 700 can perform any process of the description as described with reference to figures 3 and 6. The realizations of the present description can also be implemented through hardware or through a combination of software and hardware. In some illustrative embodiments, program 730 may be tangibly contained on a computer-readable medium that may be included in device 700 (such as memory 720) or other storage devices accessible by device 700. Device 700 can load program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, a hard disk, CD, DVD, and the like. Figure 8 shows an example of computer-readable medium 800 in the form of a CD or DVD. The computer-readable medium has program 730 stored on it. In general, various embodiments of the description can be implemented in hardware or circuits, software, specialized logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, a microprocessor, or another computing device. Although several aspects of the embodiments in this description are illustrated and described using block diagrams, flowcharts, or some other graphical representation, it should be understood that the block, device, system, technique, or method described herein can be implemented, by way of non-limiting example, in hardware, software, firmware, special-purpose circuits or logic, general-purpose hardware or controllers, or other computing devices, or some combination thereof. This description also provides at least one computer program product tangibly stored on a non-transient, machine-readable storage medium. The computer program product includes machine-executable instructions, such as those contained in program modules, that execute on a device in a real or virtual target processor to carry out the methods described above with reference to Figures 3-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or apply particular abstract data types. The functionality of program modules can be combined in, or divided among, program modules as desired in various implementations. Machine-executable instructions for program modules can be executed within a local or distributed device.In a distributed device, program modules can be located on both local storage media and remote storage media. Program code for carrying out the methods described herein may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, specialized computer, or other programmable data processing device, such that the program code, when executed by the processor or controller, causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on one machine, partially on the machine as a standalone software package, partially on the machine and partially on a remote machine, or entirely on the remote machine or on a server. In the context of this description, computer program code or related data may be carried by any suitable medium to enable the device, apparatus, or processor to perform various processes and operations such as those described above. Examples of such media include a signal, computer-readable medium, and the like. A computer-readable medium can be either a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a laptop floppy disk, a hard disk drive, random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disc (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. Furthermore, although the operations are depicted in a particular order, it should not be understood that these operations are required to be performed in the specific order shown or sequentially, or that all the illustrated operations must be performed, to achieve the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although the preceding explanations contain several implementation-specific details, these should not be interpreted as limitations on the scope of this description, but rather as descriptions of features that may be specific to particular implementations. Certain features described in the context of separate implementations may also be implemented in combination in a single implementation.Conversely, various features described in the context of a single embodiment may also be implemented in multiple separate embodiments or in any suitable subcombination. Although the present description has been written in languages ​​specific to structural features and / or methodological acts, it should be understood that the present description defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are described as illustrative ways of implementing the claims.

Claims

1. A first device (210-1), comprising: at least one processor (710); and at least one memory (720) including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, enable the first device to: receive a configured lease transmission resource configuration (410-1) from a second device (220); determine whether a timing advance is valid on a subsequent configured lease occasion (410-2, 410-3, 410-4) for a small-volume data transmission based on a first timer and resource configuration; and perform an evaluation of a validity condition for a small-volume data transmission.wherein the validity condition is a timing advance validity condition based on the received power of the RSRP reference signal; determining whether the evaluation of the validity condition for small-volume data transmission is applicable at the next configured grant occasion based on a second timer and resource configuration, wherein the evaluation of the validity condition remains valid for a period determined by the second timer after the evaluation is performed; and initiating small-volume data transmission at the next configured grant occasion if the timing advance is valid and the evaluation of the validity condition for small-volume data transmission is applicable at the next configured grant occasion.

2. The first device of claim 1, wherein at least one memory and computer program code are configured to,together with at least one processor, the first device determines whether the timing advance is valid by: determining whether the first timer remains operational until the next configured grant occasion; and based on the determination that the first timer remains operational until the next configured grant occasion, determining that the timing advance is valid.

3. The first device of claim 1 or claim 2, wherein at least one memory and the computer program code are configured to, together with at least one processor, cause the first device to determine whether the timing advance is valid by: based on the determination that the small-volume data transmission has started, determining whether the timing advance is valid during the selection of a transmission type for the small-volume data transmission,The transmission type comprises configured concession transmission or random access transmission.

4. The first device of any one of claims 1-3, wherein at least one memory and the computer program code are configured, together with at least one processor, to enable the first device to: upon determination that the timing advance is invalid, perform small-volume data transmission in a random access procedure or initiate a conventional large-volume data transmission procedure.

5. The first device of any one of claims 1-4, wherein the at least one memory and the computer program code are configured, together with the at least one processor,further causing the first device to initiate small-volume data transmission on the next configured lease occasion based on the determination of at least one of: a small-volume data transmission volume, or a received reference signal power.

6. The first device of any one of claims 1 to 5, wherein the first device comprises a terminal device and the second device comprises a network device.

7. The first device of any one of claims 1 to 6, wherein the second timer is up to 640 ms.

8. A system (200) comprising a network device (210-1, 210-2, 210-3, ..., 210-N) and a terminal device (220), wherein the network device comprises: at least one processor (710); and at least one memory (720) including computer program code, wherein the at least one memory and the computer program code are configured to,with at least one processor, enabling the device to: transmit a resource configuration of a configured lease-based transmission (410-1) to the terminal device; and receive a small-volume data transmission from the terminal device on the next configured lease occasion (410-2, 410-3, 410-4), and wherein the terminal device comprises: at least one processor (710); and at least one memory (720) including computer program code, wherein the at least one memory and the computer program code are configured to: determine whether a timing advance is valid on the next configured lease occasion for a small-volume data transmission based on a first timer and the resource configuration; and perform an evaluation of a validity condition for a small-volume data transmission.wherein the validity condition is a timing advance validity condition based on the received power of the reference signal, RSRP, and determining whether the validity condition evaluation for small-volume data transmission is applicable at the next configured lease occasion based on a second timer and resource configuration, wherein the validity condition evaluation remains valid for a period determined by the second timer after the evaluation is performed; and initiating small-volume data transmission at the next configured lease occasion if the timing advance is valid and the validity condition evaluation for small-volume data transmission is applicable at the next configured lease occasion.

9. A method (300), comprising: receiving, in a first device (210-1),a configured lease-based transmission resource configuration (410-1) from a second device (220); determine (3010, 3015), on the first device, whether a timing advance is valid on the next configured lease occasion (410-2, 410-3, 410-4) for a small-volume data transmission based on a first timer and resource configuration; perform an evaluation of a validity condition for a small-volume data transmission,wherein the validity condition is a timing advance validity condition based on the received reference signal power (RSRP); determining whether the validity condition evaluation for small-volume data transmission is applicable at the next configured grant occasion based on a second timer and resource configuration, wherein the validity condition evaluation remains valid for a certain period according to the second timer after the evaluation is performed; and initiating (3030), by means of the first device, small-volume data transmission at the next configured grant occasion if the timing advance is valid and the validity condition evaluation for small-volume data transmission is applicable at the next configured grant occasion.

10. The method of claim 9,wherein determining whether the timing advance is valid comprises: determining whether the first timer remains operational until the next configured lease occasion; and based on the determination that the first timer remains operational until the next configured lease occasion, determining that the timing advance is valid.

11. The method of claim 9 or claim 10, wherein determining whether the timing advance is valid comprises: based on the determination that the small-volume data transmission has commenced, determining whether the timing advance is valid during the selection of a transmission type for the small-volume data transmission, the transmission type comprising transmission by configured lease or a random access transmission.

12. The method of any one of claims 9-11,further comprising: upon determining that the timing advance is invalid, performing, by means of the first device, the transmission of small-volume data in a random access process or initiating a transmission procedure using conventional volume data.

13. The method of any one of claims 9-12, wherein performing the transmission of small-volume data at the next configured lease occasion comprises: initiating, by means of the first device, the transmission of small-volume data at the next configured lease occasion based on the determination of at least one of: a data volume of the small-volume data transmission, or a received reference signal power.

14. The method of any one of claims 9-13,wherein the first device comprises a terminal device and the second device comprises a network device.

15. The method of claim 14 further comprising: transmitting, in the network device, the configured lease-based transmission resource configuration to the terminal device; and transmitting, in the terminal device, the small-volume data transmission on the next configured lease-based determination.

16. A computer-readable storage medium (800) comprising program instructions stored therein, the instructions, when executed by an apparatus, causing the apparatus to perform the method of any one of claims 9-15.