Control of non-sdt data transmission

Abstract

Embodiments of the present disclosure relate to apparatuses, methods, devices, and computer-readable storage media for controlling DCCH-based non-small data transmission (SDT) data arrival. In some example embodiments, a terminal apparatus transmits an indication of availability of non-SDT data to a network apparatus during a small data transmission (SDT) procedure. The terminal apparatus monitors for a response to the indication and performs an action in response to an absence of the response to the indication of the non-SDT data. The action includes entering an idle or inactive state and / or initiating a connection establishment or resume request to the network apparatus.

Description

Technical Field

[0001] The embodiments disclosed herein relate generally to the telecommunications field, and in particular to apparatus, methods, devices, and computer-readable storage media for controlling the transmission of non-small data. Background Technology

[0002] With the development of communication technology, Small Data Transmission (SDT) has been introduced to avoid signaling overhead and latency caused by transitioning from inactive mode to connected mode. In SDT, a terminal device in inactive mode can transmit small data packets to a network device in the uplink channel without transitioning to connected mode. In some cases, data may be available on radio bearers not configured to allow SDT during SDT. This type of data is referred to as non-SDT data. Normally, non-SDT data cannot be transmitted to a network device using resources configured for SDT. Summary of the Invention

[0003] In general, exemplary embodiments of this disclosure provide an apparatus, method, device, and computer-readable storage medium for controlling non-SDT data transmission.

[0004] In a first aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory, the at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the terminal device to indicate the availability of transmitting non-SDT data to a network device during a Small Data Transfer (SDT) procedure. The terminal device is also caused to monitor responses to the indication and, in response to the absence of a response to the indication, to perform an action. The action includes entering an idle or inactive state and / or transmitting a connection establishment or recovery request to the network device.

[0005] In a second aspect, a method implemented in a terminal device is provided. In this method, the terminal device transmits an indication of the availability of non-SDT data to a network device during a Small Data Transfer (SDT) procedure. The terminal device monitors responses to the indication and performs an action in response to the absence of a response to the indication. The action includes: entering an idle or inactive state, and / or initiating a connection establishment or recovery request to the network device.

[0006] In a third aspect, an apparatus is provided, the apparatus comprising components for performing the method according to the second aspect.

[0007] In a fourth aspect, a computer-readable storage medium is provided, on which instructions are stored. When executed on at least one processor, the instructions cause the at least one processor to perform the method according to the second aspect.

[0008] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other objectives, features and advantages of this disclosure will become more apparent from the more detailed description of some exemplary embodiments thereof in the accompanying drawings, in which:

[0010] Figure 1 An example environment in which an example implementation of this disclosure may be carried out is shown;

[0011] Figure 2 The process for controlling non-SDT data transmission according to some embodiments of the present disclosure is illustrated;

[0012] Figure 3 Flowcharts of example processes implemented at a terminal device according to some embodiments of the present disclosure are shown; and

[0013] Figure 4 This is a simplified block diagram of an apparatus suitable for implementing the embodiments of this disclosure.

[0014] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0015] The principles of this disclosure will now be described with reference to some example embodiments. It will be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, and not to imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0017] As used herein, the term "network device" refers to a device capable of providing or hosting a cell or coverage area with which other devices (e.g., terminal devices) can communicate. Examples of network devices include, but are not limited to, NodeB (or NB), evolved NodeB (eNodeB or eNB), next-generation eNB (ng-eNB), ng-eNB-Central Unit (ng-eNB-CU), ng-eNB-Distributed Unit (ng-eNB-DU), next-generation NodeB (gNB), gNB-Central Unit (gNB-CU), gNB-Distributed Unit (gNB-DU), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Header (RRH), Integrated Access and Backhaul (IAB) nodes, low-power nodes (such as femtonodes or piconodes), etc.

[0018] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, vehicular devices for V2X communication (where X represents a pedestrian, vehicle, or infrastructure / network), integrated access and backhaul (IAB) devices, or image capture devices such as digital cameras, gaming devices, music storage and playback devices, or internet devices that support wireless or wired internet access and browsing. In this document, the term "terminal device" may be used interchangeably with UE.

[0019] As used herein, the term "circuit system" can refer to hardware circuitry and / or a combination of hardware circuitry and software. For example, a circuit system may be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit system may be any part of a hardware processor, including software (including digital signal processors), software, and memory, that works together to enable a device such as a terminal device or network device to perform various functions. In yet another example, a circuit system may be hardware circuitry and / or a processor, such as a microprocessor or part of a microprocessor, that requires software / firmware to operate, but the software may be absent when operation is not required. As used herein, the term circuit system also encompasses an implementation of hardware circuitry or a processor alone, or an implementation of hardware circuitry or a processor and a portion thereof with its accompanying software and / or firmware.

[0020] As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well. The term “comprising,” and variations thereof, will be interpreted as an open-ended term meaning “including, but not limited to.” The term “based on” will be interpreted as “at least partially based on.” The terms “one embodiment” and “implementation” will be interpreted as “at least one embodiment.” The term “another embodiment” will be interpreted as “at least one other embodiment.” The terms “first,” “second,” etc., may refer to different or the same objects.

[0021] As mentioned above, non-SDT data can become available for transmission from the terminal device to the network device while the SDT procedure is in progress. Two methods are considered: one based on Common Control Channel (CCCH) indication and the other on Dedicated Control Channel (DCCH) indication, for indicating the availability of non-SDT data from the terminal device to the network device. In the CCCH-based method, after non-SDT data arrives in a buffer of a radio bearer not configured to allow SDT, the terminal device terminates the SDT procedure and triggers a Radio Resource Control (RRC) recovery or establishment procedure to establish an RRC connection with the network device. In the DCCH-based method, when non-SDT data arrives in a buffer of a radio bearer not configured to allow SDT, the terminal device can transmit an indication of the availability of non-SDT data to the network device (e.g., using an RRC message) while maintaining the SDT procedure. Once the indication of non-SDT data is received, the network device can instruct the terminal device to transition from an inactive mode to a connected mode to transmit the non-SDT data. The CCCH-based method is named based on the transmission of the indication on the CCCH channel (on Signaling Radio Bearer 0 (SRB0)) using an RRC Resume Request. The DCCH-based approach is named for the transmission of indications on the DCCH channel (on SRB1, SRB2, or SRB3) using new or existing RRC messages (such as UEAssistanceInformation).

[0022] However, in some situations, such as poor radio conditions, the network device may be unable to receive or decode instructions for non-SDT data, or the terminal device may be unable to receive or decode instructions transmitted by the network device in response to the instructions. Additionally, the network device may also be unable to transmit instructions due to other reasons (e.g., resource congestion). Therefore, without instructions from the network device, the terminal device may not be able to enter connected mode in a timely manner. For high-priority non-SDT data, this may cause unintended delays.

[0023] Additionally, an SDT failure timer is defined to monitor for SDT procedure failures. However, the SDT failure timer will be quite long (e.g., 10 seconds) because the required time for the procedure cannot be assumed before the SDT procedure is performed. Furthermore, because SDT data is typically not high priority, long delays in failure determination are not a problem, unlike the case of higher priority data arrival or emergency calls. Therefore, non-SDT data may also experience unexpected delays.

[0024] An example embodiment of this disclosure provides a scheme for controlling non-SDT data transmission. In this scheme, if non-SDT data becomes available for transmission to a network device during an SDT procedure, the terminal device transmits an indication of the non-SDT data to the network device. The terminal device then monitors the network device's response to the indication. If the terminal device detects a response, such as an RRCResume message, the terminal device may transition from an inactive mode to a connected mode to transmit the non-SDT data to the network device. If the terminal device determines that there is no response from the network device, the terminal device terminates the SDT procedure and enters an inactive or idle mode and / or triggers the transmission of a connection establishment or restoration request to the network device. For example, the terminal device may transmit an RRCSetupRequest or RRCResumeRequest to the network device to initiate or restore a Radio Resource Control (RRC) connection with the network device for transmitting non-SDT data.

[0025] In this way, the transmission of non-SDT data can be timely and transmission latency can be reduced.

[0026] Figure 1 An example environment 100 in which an example implementation of the present disclosure may be carried out is shown.

[0027] Environment 100 may be part of a communication network, including terminal device 110 and network device 120.

[0028] It should be understood that the number of terminal devices and network devices shown in environment 100 is for illustrative purposes only and does not imply any limitation on the scope of this disclosure. In some embodiments, environment 100 may include additional terminal devices and / or additional network devices.

[0029] Terminal device 110 can communicate directly with network device 120 or via network device 120 with another terminal device (not shown). Communication in environment 100 can follow any suitable communication standards or protocols that are already in use or will be developed in the future, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), 5G New Radio (NR), Wi-Fi, and Global Microwave Access Interoperability (WiMAX) standards, and employ any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth, ZigBee and Machine Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Ultra Reliable Low Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), and New Radio Unlicensed (NR-U) technologies.

[0030] Terminal device 110 can access the cell provided by network device 120, and when terminal device 110 is in inactive mode, it can transmit small data packets to network device 120 during SDT procedures. During SDT procedures, data available on radio bearers configured for SDT can be transmitted to network device 120 in the form of small data packets. However, data available on radio bearers not configured to allow SDT cannot be transmitted during SDT procedures.

[0031] Figure 2 A process 200 for controlling non-SDT data transmission according to some embodiments of this disclosure is shown. For discussion purposes, reference will be made to... Figure 1 To describe flowchart 200.

[0032] In process 200, during the SDT procedure between terminal device 110 and network device 120, after non-SDT data becomes available for transmission to network device 120, terminal device 110 transmits (210) an indication of the availability of non-SDT data to network device 120. Non-SDT data includes data available on radio bearers that are not configured (or not configured) to allow SDT. Terminal device 110 may transmit the indication of non-SDT data to network device 120 in any manner.

[0033] In some implementations, terminal device 110 may transmit an indication of the availability of non-SDT data in an RRC message. In some implementations, terminal device 110 may transmit the indication in Media Access Control (MAC) signaling or Physical Layer (PHY) signaling. In some implementations, terminal device 110 may transmit the indication in an existing message; for example, terminal device 110 may transmit an indication of non-SDT data in User Equipment (UE) Assistance Information. In some implementations, terminal device 110 may reuse other existing signaling or messages to transmit the indication. In some implementations, terminal device 110 may transmit an indication of non-SDT data in another uplink RRC message defined for this purpose.

[0034] Then, terminal device 110 monitors (220) the response to the indication. For example, network device 120 may transmit a response to the indication to terminal device 110. In some embodiments, the response may include at least one of the following: an RRCResume message, an RRCSetup message, an RRCRelease message, an RRCRelease message with suspendConfig, or an RRCReject message. In some embodiments, the response may include any other messages, signaling, or system information transmitted by network device 120 for the indication of non-SDT data. Based on the response received from network device 120, terminal device 110 may perform a corresponding action to transmit the non-SDT data to the network.

[0035] In some situations, such as under poor radio conditions, terminal device 110 may not be able to receive a response from network device 120 for an indication of non-SDT data. In this case, terminal device 110 may determine that there is no response for an indication of non-SDT data.

[0036] In some implementations, the terminal device may employ a timer to monitor responses to determine if there is a response to an indication of non-SDT data. After the timer used for monitoring expires, the terminal device 110 may determine that there is no response to an indication of non-SDT data.

[0037] In some implementations, a timer may be defined or configured specifically for the transmission of indications of non-SDT data.

[0038] Alternatively or concurrently, existing timers can be reused for monitoring. For example, the T319 timer can be reused for monitoring. In some embodiments, as mentioned above, terminal device 110 may transmit indications of non-SDT data in UE assistance information; therefore, the UE assistance information prohibition timer can be reused for monitoring. In this case, after the UE assistance information prohibition timer expires, terminal device 110 can determine that there is no response to the indication of non-SDT data. In some embodiments, any other existing timers can be reused for monitoring.

[0039] The timer used for monitoring may be started after the transmission of an indication of non-SDT data. Alternatively or additionally, the timer used for monitoring may be stopped upon cell reselection initiated by terminal device 110 or upon receiving a response to an indication of non-SDT data. In some embodiments, a response to an indication of non-SDT data may include at least one of the following: an RRCResume message, an RRCSetup message, an RRCRelease message, an RRCRelease message with suspendConfig, or an RRCReject message. In some embodiments, the response may include any other message, signaling, or system information transmitted by network device 120 in response to an indication of non-SDT data. In some embodiments, the response may include an RRCReject message instructing terminal device 110 to take action. For example, an RRCReject message may instruct terminal device 110 to enter an idle or inactive mode; and / or instruct to initiate a connection establishment or recovery request to network device 120. In some embodiments, if terminal device 110 receives an RRCReject message, terminal device 110 may maintain the SDT procedure. In some implementations, if terminal device 110 receives an RRCReject message, terminal device 110 may terminate the SDT procedure.

[0040] In some implementations, the SDT failure timer can also be reused as a monitoring timer. In some implementations, the terminal device can determine that there is no response to an indication of non-SDT data after the SDT failure timer expires. In some implementations, a timer dedicated to the transmission of indications of non-SDT data can also be defined or configured, and the terminal device 110 can determine that there is no response to an indication of non-SDT data based on both the timer dedicated to the transmission of indications of non-SDT data and the SDT failure timer. For example, the terminal device 110 can determine that there is no response to an indication of non-SDT data after either of these timers expires. In some implementations, the SDT failure timer can be stopped when the timer dedicated to the transmission of indications of non-SDT data starts or when an indication of non-SDT data is transmitted. For example, if an indication of non-SDT data is transmitted very close to the expiration of the SDT failure timer (e.g., only a few milliseconds away from expiration), stopping the SDT failure timer when the indication of non-SDT data is transmitted or when the timer dedicated to the transmission of indications of non-SDT data starts allows the network device 120 sufficient time to respond to the indication. Therefore, stopping the SDT failure timer ensures that the network has time to respond to non-SDT data, in case the timer expires quickly if it is not stopped.

[0041] In addition to or alternatively using a timer for monitoring, terminal device 110 may employ other methods to determine that there is no response to the indication of non-SDT data. In some embodiments, terminal device 110 may employ a counter to count the number of transmissions or retransmissions of the indication of non-SDT data to determine that there is no response to the indication of non-SDT data. In this case, a "max_amount_of_times" of the number of transmissions or retransmissions of the indication may be predetermined. After the number of transmissions or retransmissions of the indication reaches "max_amount_of_times", terminal device 110 may determine that there is no response to the indication of non-SDT data. In some embodiments, the transmission or retransmission of the indication is triggered based on a timer or a Non-Access Stratum (NAS). For example, terminal device 110 may periodically transmit the indication of non-SDT data based on a timer, or transmit the indication based on an indication for NAS. In some embodiments, the number of transmissions or retransmissions of the indication may be performed and maintained by the Radio Link Control (RLC) layer. For example, after the maximum number of RLC retransmissions, terminal device 110 may determine that there is no response to the indication of non-SDT data.

[0042] In some implementations, the different expiration times of the timers used for monitoring and the "max_amount_of_times" used for the counter can be predetermined based on different services, signaling or data radio bearers (SRB or DRB), trigger types, establishment reasons, or can be dynamically changed as needed.

[0043] Once terminal device 110 determines that there is no response to the indication of non-SDT data, terminal device 110 performs (230) actions, including: entering an idle or inactive state; and / or transmitting (240) a connection establishment or resumption request to network device 120.

[0044] In some implementations, terminal device 110 may terminate the SDT procedure and enter an idle or inactive state. In some implementations, terminal device may initiate a connection establishment or resumption request to network device 120 by transmitting an RRCSetupRequest or RRCResumeRequest.

[0045] Therefore, the transmission of non-SDT data can be timely and transmission latency can be reduced.

[0046] Figure 3 A flowchart of an example method 300 implemented at a terminal device according to some embodiments of the present disclosure is shown.

[0047] Method 300 is available Figure 1 The terminal device 110 shown is implemented here. For discussion purposes, reference will be made to... Figure 1 Method 300 is described herein. It should be understood that method 300 may include additional actions not shown and / or some actions shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0048] At 310, terminal device 110 transmits an indication of the availability of non-SDT data to network device 120 during a Small Data Transmission (SDT) procedure.

[0049] At 320, terminal device 110 monitors the response to the instruction.

[0050] At 330, terminal device 110 performs an action in response to the absence of a response to the indication, including: entering an idle or inactive state; and / or initiating a connection establishment or restoration request to network device 120.

[0051] In some implementations, non-SDT data includes data available on radio bearers that are not configured to allow SDT.

[0052] In some implementations, monitoring the response to an indication includes monitoring the response to the indication until a timer used for monitoring expires or until a predetermined number of transmissions of the indication for non-SDT data are completed.

[0053] In some implementations, the timer used for monitoring includes at least one of the following: an SDT failure timer; a timer dedicated to the transmission of indications for non-SDT data; a T319 timer; and a User Equipment (UE) Auxiliary Information Prohibition Timer.

[0054] In some implementations, method 300 further includes: retransmitting the indication after the timer expires; or retransmitting the indication based on an indication from the non-access stratum (NAS).

[0055] In some implementations, a timer for monitoring is started after the indicated transmission; and / or the timer for monitoring is stopped after at least one of a cell reselection initiated by the terminal device or a response to the indication is received.

[0056] In some implementations, the response includes at least one of the following: an RRCResume message; an RRCSetup message; an RRCRelease message; an RRCRelease message with suspendConfig; or an RRCReject message.

[0057] In some implementations, an indication of non-SDT data is transmitted in at least one of the following: RRC messages; MAC signaling; PHY signaling; and UE auxiliary information.

[0058] Figure 4 This is a simplified block diagram of apparatus 400 suitable for implementing an example embodiment of the present disclosure. Apparatus 400 can be configured as follows: Figure 1 The terminal device 110 shown in the figure is implemented therein.

[0059] As shown in the figure, device 400 includes a processor 410, a memory 420 coupled to the processor 410, a communication module 430 coupled to the processor 410, and a communication interface (not shown) coupled to the communication module 430. The memory 420 stores at least a program 440. The communication module 430 is used for bidirectional communication, for example, via multiple antennas or via a cable. The communication interface can represent any interface necessary for communication.

[0060] Assume that program 440 includes program instructions that, when executed by the associated processor 410, enable device 400 to operate according to an example embodiment of this disclosure, as referenced herein. Figures 1 to 2The example embodiments discussed herein may be implemented by computer software capable of execution by the processor 410 of device 400, or by hardware, or by a combination of software and hardware. The processor 410 may be configured to implement various example embodiments of this disclosure.

[0061] Memory 420 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology. As a non-limiting example, the data storage technology includes non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 420 is shown in device 400, several physically different memory modules may exist in device 400. Processor 410 can be of any type suitable for a local technology network and may include one or more of the following: as a non-limiting example, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 400 may have multiple processors, such as application-specific integrated circuit chips whose time is controlled by a clock that synchronizes the main processor.

[0062] When device 400 acts as terminal device 110, processor 410 can implement the functions described in reference 2 above. Figure 3 The operation or action of the first device 110 described. For simplicity, details will be omitted.

[0063] In general, the various example embodiments of this disclosure can be implemented using hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while others can be implemented using firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of the example embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it will be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented as non-limiting examples using hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0064] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in a program module, which execute in a device on a target real or virtual processor to perform as referenced above. Figures 1 to 3The described operations and actions. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various example implementations, the functionality of program modules can be combined or split among program modules as needed. The machine-executable instructions used for a program module can be executed on a local device or a distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0065] Program code for performing the methods of this disclosure 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, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions or operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0066] In the context of this disclosure, computer program code or related data can be carried on any suitable carrier to enable an apparatus, device, or processor to perform the various processes and operations described above. Examples of carriers include signals and computer-readable media.

[0067] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0068] Furthermore, although operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in a sequential order, or requiring all shown operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of individual example embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple example embodiments.

[0069] Although this disclosure has been described using language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

[0070] Various example implementations of this technology have been described. In addition to or as an alternative to the above, the following examples are described. Features described in any of the following examples may be used in conjunction with any of the other examples described herein.

[0071] In some aspects, a terminal device includes: at least one processor; and at least one memory, the at least one memory including computer program code; and the at least one memory and the computer program code are configured together with the at least one processor to cause the terminal device to: indicate the availability of transmitting non-SDT data to a network device during a Small Data Transfer (SDT) procedure; monitor responses to the indication; and perform actions in response to the absence of a response to the indication, the actions including: entering an idle or inactive state; and / or initiating a connection establishment or recovery request to the network device.

[0072] In some example implementations, the non-SDT data includes data available on radio bearers that are not configured to allow SDT.

[0073] In some example implementations, the terminal device monitors the response to the indication in such a way that the response to the indication is monitored until a timer for monitoring expires or until a predetermined number of transmissions of the indication of the non-SDT data are completed.

[0074] In some example implementations, the timer used for the monitoring includes at least one of the following: an SDT failure timer; a timer dedicated to the transmission of the indicated non-SDT data; a T319 timer; and a User Equipment (UE) Assistance Information Prohibition timer.

[0075] In some example implementations, the terminal device is also caused to: retransmit the indication after a timer expires; or retransmit the indication based on an indication from a non-access stratum (NAS).

[0076] In some example implementations, the timer for monitoring is started after the transmission of the indication; and / or the timer for monitoring is stopped after at least one of the cell reselection initiated by the terminal device or the response to the indication is received.

[0077] In some example implementations, the response includes at least one of the following: an RRCResume message; an RRCSetup message; an RRCRelease message; an RRCRelease message with suspendConfig; or an RRCReject message.

[0078] In some example implementations, the indication is transmitted in at least one of the following: RRC message; MAC signaling; PHY signaling; and UE assistance information.

[0079] In some aspects, an apparatus implemented in a terminal device includes: a component for indicating the availability of transmitting non-SDT data to a network device during a Small Data Transmission (SDT) procedure; a component for monitoring a response to the indication; and a component for performing an action in response to the absence of a response to the indication, the action including: entering an idle or inactive state; and / or initiating a connection establishment or recovery request to the network device.

[0080] In some example implementations, the non-SDT data includes data available on radio bearers that are not configured to allow SDT.

[0081] In some example embodiments, the component for monitoring the response to the indication includes means for monitoring the response to the indication until a timer for monitoring expires or until a predetermined number of transmissions of the indication of the non-SDT data.

[0082] In some example implementations, the timer used for the monitoring includes at least one of the following: an SDT failure timer; a timer dedicated to the transmission of the indicated non-SDT data; a T319 timer; and a User Equipment (UE) Assistance Information Prohibition timer.

[0083] In some example implementations, the device further includes: a component for retransmitting the indication after a timer expires; or a component for retransmitting the indication based on an indication from a non-access stratum (NAS).

[0084] In some example implementations, the timer for monitoring is started after the transmission of the indication; and / or the timer for monitoring is stopped after at least one of the cell reselection initiated by the terminal device or the response to the indication is received.

[0085] In some example implementations, the response includes at least one of the following: an RRCResume message; an RRCSetup message; an RRCRelease message; an RRCRelease message with suspendConfig; or an RRCReject message.

[0086] In some example implementations, the indication is transmitted in at least one of the following: RRC message; MAC signaling; PHY signaling; and UE assistance information.

[0087] In some aspects, a computer-readable storage medium has instructions that, when executed on at least one processor, cause the at least one processor to perform the steps of the foregoing aspects.

Claims

1. A terminal device, the terminal device comprising: At least one processor; as well as At least one memory, said at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to: During Small Data Transmission (SDT) procedures, an indication of the availability of non-SDT data is transmitted to the network device in the UE auxiliary information; Monitor the response to the indication of the availability of the non-SDT data during the SDT procedure until the SDT failure timer expires; as well as If the SDT failure timer expires and the terminal device does not receive a response to the indication of the availability of the non-SDT data during the SDT procedure, an action is performed, the action including: Entering idle state; as well as Retransmit the instruction.

2. The terminal device of claim 1, wherein the non-SDT data includes data available on radio bearers not configured to allow SDT.

3. The terminal device as described in claim 1, wherein: The timer used for monitoring is stopped after at least one of the cell reselection initiated by the terminal device or after receiving the response to the indication.

4. The terminal device of claim 1, wherein the response includes at least one of the following: RRCResume message; RRCSetup message; RRCRelease message; RRCRelease message with suspendConfig; or RRCReject message.

5. A method implemented at a terminal device, the method comprising: During Small Data Transmission (SDT) procedures, an indication of the availability of non-SDT data is transmitted to the network device in the UE auxiliary information; Monitor the response to the indication of the availability of the non-SDT data during the SDT procedure until the SDT failure timer expires; as well as If the SDT failure timer expires and the terminal device does not receive a response to the indication of the availability of the non-SDT data during the SDT procedure, an action is performed, the action including: Entering idle state; as well as Retransmit the instruction.

6. The method of claim 5, wherein the non-SDT data includes data available on radio bearers that are not configured to allow SDT.

7. The method of claim 5, wherein: The timer used for monitoring is stopped after at least one of the cell reselection initiated by the terminal device or after receiving the response to the indication.

8. The method of claim 5, wherein the response comprises at least one of the following: RRCResume message; RRCSetup message; RRCRelease message; RRCRelease message with suspendConfig; or RRCReject message.

9. A device implemented in a terminal apparatus, the device comprising: A component for indicating the availability of transmitting non-SDT data to the network device in UE auxiliary information during Small Data Transmission (SDT) procedures; A component for monitoring the response to the indication of the availability of the non-SDT data during the SDT procedure until the SDT failure timer expires; as well as A component for performing an action when the SDT failure timer expires and the terminal device does not receive a response to the indication of the availability of the non-SDT data during the SDT procedure, the action comprising: Entering idle state; as well as Retransmit the instruction.

10. The device of claim 9, wherein the non-SDT data includes data available on radio bearers not configured to allow SDT.

11. The device as claimed in claim 9, wherein: The timer used for monitoring is stopped after at least one of the cell reselection initiated by the terminal device or after receiving the response to the indication.

12. The device of claim 9, wherein the response comprises at least one of the following: RRCResume message; RRCSetup message; RRCRelease message; RRCRelease message with suspendConfig; or RRCReject message.

13. A computer-readable storage medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the method as described in any one of claims 5 to 8.

Images