Control of non-SDT data transmission

Abstract

The present invention provides a novel device, method, apparatus, and computer-readable storage medium for controlling DCCH-based non-small data transmission (SDT) data arrival. [Solution] In some exemplary embodiments, a terminal device sends an indication of the availability of non-small data transmission (SDT) data to a network device during the SDT procedure. The terminal device monitors for responses to the indication and takes action in response to no response to the non-SDT data indication. Actions include entering an idle or inactive state and / or initiating a connection setup or restart request to the network device.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to devices, methods, apparatuses, and computer-readable storage media for controlling non-small data transmission.

Background Art

[0002] With the development of communication technologies, small data transmission (SDT) has been introduced to avoid signaling overhead and latency caused by the transition from the non-active mode to the connected mode. In the SDT procedure, a terminal device in the non-active mode can transmit small data packets to a network device over an uplink channel without transitioning to the connected mode. Depending on the situation, data may become available on a radio bearer that is not configured to allow SDT during the SDT procedure. Such data may be referred to as non-SDT data. Conventionally, non-SDT data cannot be transmitted to a network device using resources configured for SDT.

Summary of the Invention

[0003] Generally, exemplary embodiments of the present disclosure provide a device, a method, an apparatus, and a computer-readable storage medium for controlling non-SDT data transmission.

[0004] In a first embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code are configured, using at least one processor, to cause the terminal device to send an indication of the availability of non-small data transmission (SDT) data to a network device during an SDT procedure. Furthermore, the terminal device monitors for responses to the indication and takes action in response to no response to the indication. Actions include entering an idle or inactive state and / or sending a connection setup or restart request to a network device.

[0005] A second embodiment provides a method implemented by a terminal device, in which the terminal device sends an indication of the availability of non-small data transmission (SDT) data to a network device during the SDT procedure. The terminal device monitors for responses to the indication and takes action in response to no response to the indication. Actions include entering an idle or inactive state and / or initiating a connection setup or restart request to the network device.

[0006] In a third embodiment, an apparatus is provided that includes means for carrying out the method according to the second embodiment.

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

[0008] Other features of this disclosure will be readily apparent through the following description.

[0009] The above and other purposes, features, and advantages of this disclosure will become more apparent through a more detailed description of some exemplary embodiments of this disclosure shown in the attached drawings. [Brief explanation of the drawing]

[0010] [Figure 1] This document describes exemplary environments in which exemplary embodiments of this disclosure can be implemented. [Figure 2] This disclosure describes a process for controlling non-SDT data transmission according to some embodiments of this disclosure. [Figure 3] A flowchart of an exemplary process performed on a terminal device according to some embodiments of this disclosure is shown. [Figure 4] This is a simplified block diagram of a device suitable for implementing an embodiment of the present disclosure. [Modes for carrying out the invention]

[0011] Throughout the drawing, identical or similar reference figures represent identical or similar elements.

[0012] Next, the principles of this disclosure will be described with reference to some exemplary embodiments. Naturally, these embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, but do not imply any limitation on the scope of this disclosure. The disclosures described herein can be implemented in various ways other than those described below.

[0013] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those broadly understood by those skilled in the art to which this disclosure belongs.

[0014] As used herein, the term “network device” refers to a device that can provide or host a cell or coverage on which further devices, such as terminal devices, can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), Evolved Node B (eNodeB or eNB), Next Generation eNB (ng-eNB), ng-eNB Central Unit (ng-eNB-CU), ng-eNB Distributed Unit (ng-eNB-DU), Next Generation Node B (gNB), gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), Integrated Access and Backhaul (IAB) Node, and low-power nodes such as femtonodes or piconodes.

[0015] As used herein, the term “terminal device” refers to any device having 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, on-vehicle devices for V2X communication (where X means pedestrian, vehicle, or infrastructure / network), integrated access and backhaul (IAB) devices, or image capture devices such as digital cameras, game devices, music storage and playback devices, or internet equipment that enables wireless or wired internet access and browsing, etc. In this specification, the term “terminal device” may be used interchangeably with UE.

[0016] As used herein, the term “circuit” may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As an additional example, a circuit may be any part of a hardware processor, software, and memory(s) that uses software including digital signal processors(s) that work together to cause a device such as a terminal device or network device to perform various functions. As a further additional example, a circuit may be a hardware circuit and / or a processor such as a microprocessor or a part of a microprocessor that requires software / firmware to operate, but may not be present if the software is not required for operation. As used herein, the term “circuit” also includes embodiments of a mere hardware circuit, or a processor(s), or a part of a hardware circuit or processor(s), and the software and / or firmware associated with it (or them).

[0017] Where used herein, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context makes this clear. The term “including” and its variations should be interpreted as an open term meaning “including, but not limited to.” The term “based on” should be interpreted as “at least partially based on.” The terms “one embodiment” and “embodiment” should be interpreted as “at least one embodiment.” The term “another embodiment” should be interpreted as “at least one other embodiment.” Terms such as “first,” “second,” etc., may refer to different objects or the same object.

[0018] As described above, non-SDT data that can be sent from the terminal device to the network device may become available during the SDT procedure. Two approaches are possible for the terminal device to indicate the availability of non-SDT data to the network device: one based on Common Control Channel (CCCH) indication and the other on Dedicated Control Channel (DCCH) indication. In the CCCH-based approach, when non-SDT data arrives in the buffer of a radio bearer that is not configured to enable SDT, the terminal device terminates the SDT procedure and triggers a Radio Resource Control (RRC) restart or establishment procedure to set up an RRC connection to the network device. In the DCCH-based approach, when non-SDT data arrives in the buffer of a radio bearer that is not configured to enable SDT, the SDT procedure is maintained, and the terminal device can send an indication of the availability of non-SDT data to the network device (for example, using an RRC message). Upon receiving the indication of non-SDT data, the network device can instruct the terminal device to switch from inactive mode to connected mode in order to send the non-SDT data. The CCCH-based approach is so named because the indication is transmitted on the CCCH channel (on Signaling Radio Bearer 0 (SRB0)) by an RRCResumeRequest. The DCCH-based approach is so named because the indication is transmitted on the DCCH channel (on SRB1, SRB2, or SRB3) by a new or existing RRC message (such as UEAssistanceInformation).

[0019] However, depending on the circumstances, for example, if the radio signal is poor, the network device may not be able to receive or decode the indication for non-SDT data, or the terminal device may not be able to receive or decode the command sent by the network device in response to the indication. Furthermore, the network device may fail to send the command for other reasons, such as resource congestion. Therefore, without a command from the network device, the terminal device may not enter connected mode in time. In the case of high-priority non-SDT data, this can result in undesirable delays.

[0020] Furthermore, an SDT failure timer is defined to monitor for SDT procedure failures. However, since the time required for an SDT procedure cannot be predicted in advance, the SDT failure timer is long (e.g., 10 seconds). In addition, since SDT data is generally not of high priority, long delays in failure determination are not problematic, unlike in the case of high-priority data arrival or emergency calls. Therefore, undesirable delays can occur even with non-SDT data.

[0021] Exemplary embodiments of the present disclosure provide a scheme for controlling non-SDT data transmission. In this scheme, when non-SDT data to be transmitted to a network device becomes available during an SDT procedure, the terminal device transmits an indication of the non-SDT data to the network device. Next, the terminal device monitors for a response from the network device to the indication. When the terminal device detects a response such as an RRCResume message, the terminal device can transition from the non-active mode to the connected mode and 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 ends the SDT procedure, enters the non-active or idle mode, and / or triggers the transmission of a connection setup or resume request to the network device. For example, the terminal device can transmit an RRCSetupRequest or an RRCResumeRequest to the network device to start or resume a radio resource control (RRC) connection with the network device in order to transmit the non-SDT data.

[0022] In this way, the transmission of non-SDT data can be made timely, and the transmission delay can be reduced.

[0023] FIG. 1 shows an exemplary environment 100 in which exemplary embodiments of the present disclosure can be implemented.

[0024] The environment 100 may be part of a communication network and includes a terminal device 110 and a network device 120.

[0025] Of course, the number of terminal devices and network devices is shown in the environment 100 for illustrative purposes only and does not imply any limitation to the scope of the present disclosure. In some embodiments, the environment 100 may include additional terminal devices and / or additional network devices.

[0026] The terminal device 110 can communicate directly with the network device 120 or a further terminal device (not shown) or via the network device 120. Communication in the environment 100 may conform to any suitable communication standard or protocol that already exists or will be developed in the future, such as the Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), 5th Generation (5G) New Radio (NR), Wireless Fidelity (Wi-Fi), and Worldwide Interoperability for Microwave Access (WiMAX) standards. For example, it may employ any suitable communication technology such as 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 Unlicensed New Radio (NR-U) technology.

[0027] The terminal device 110 can access the cell provided by the network device 120 and can transmit small data packets to the network device 120 during the SDT procedure when the terminal device 110 is in the inactive mode. In the SDT procedure, the data available on the radio bearer configured for SDT can be transmitted to the network device 120 in small data packets. However, the data available on a radio bearer that is not configured to allow SDT cannot be transmitted in the SDT procedure.

[0028] FIG. 2 shows a process 200 for controlling non-SDT data transmission according to some embodiments of the present disclosure. For illustrative purposes, flowchart 200 will be described with reference to FIG. 1.

[0029] In process 200, during the SDT procedure between terminal device 110 and network device 120, after non-SDT data to be sent to network device 120 becomes available, terminal device 110 sends an indication of the availability of non-SDT data to network device 120 (210). Non-SDT data includes available data on wireless bearers that are not configured (or are not configured) for SDT. Terminal device 110 may send the indication of non-SDT data to network device 120 in any way.

[0030] In some embodiments, the terminal device 110 may transmit an indication of non-SDT data availability in an RRC message. In some embodiments, the terminal device 110 may transmit the indication in media access control (MAC) signaling or physical layer (PHY) signaling. In some embodiments, the terminal device 110 may transmit the indication in an existing message; for example, the terminal device 110 may transmit an indication of non-SDT data in user equipment (UE) assistance information. In some embodiments, the terminal device 110 may reuse other existing signaling or messages to transmit the indication. In some embodiments, the terminal device 110 may transmit an indication of non-SDT data in another uplink RRC message that may be defined for that purpose.

[0031] Next, the terminal device 110 monitors for responses to the indication (220). For example, the network device 120 may send a response to the indication to the 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 with suspendConfig message, or an RRCReject message. In some embodiments, the response may include any other messages, signaling, or system information sent by the network device 120 for indication of non-SDT data. Based on the response received from the network device 120, the terminal device 110 may take a corresponding action to send the non-SDT data to the network.

[0032] Depending on the circumstances, such as poor radio wave conditions, the terminal device 110 may not receive a response from the network device 120 for an indication of non-SDT data. In this case, the terminal device 110 may determine that there is no response for the indication of non-SDT data.

[0033] In some embodiments, the terminal device may employ a timer to monitor responses in order to determine if there is no response to an indication of non-SDT data. When the monitoring timer expires, the terminal device 110 may determine that there is no response to an indication of non-SDT data.

[0034] In some embodiments, a timer can be defined or set specifically for sending non-SDT data indications.

[0035] In addition to this, or instead, an existing timer may be reused as a monitoring timer. For example, the T319 timer may be reused as a monitoring timer. In some embodiments, as described above, the terminal device 110 can send an indication of non-SDT data in the UE Assistant information, and therefore the UE Assistant information prohibition timer can be reused as a monitoring timer. In this case, when the UE Assistant information prohibition timer has finished, the terminal device 110 may determine that there has been no response to the indication of non-SDT data. In some embodiments, any other existing timer can be reused as a monitoring timer.

[0036] A monitoring timer may be started when an indication of non-SDT data is transmitted. Alternatively, or additionally, the monitoring timer may be stopped when a cell reselection is initiated by the terminal device 110, or when a response to an indication of non-SDT data is received. 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 with suspendConfig message, or an RRCReject message. In some embodiments, the response may include any other messages, signaling, or system information sent by the network device 120 for the indication of non-SDT data. In some embodiments, the response may include an RRCReject message that indicates an action to be taken by the terminal device 110. For example, an RRCReject message may indicate that the terminal device 110 is transitioning to idle mode or inactive mode, and / or that it is initiating a connection setup or restart request to the network device 120. In some embodiments, if terminal device 110 receives an RRCReject message, terminal device 110 can maintain the SDT procedure. In some embodiments, if terminal device 110 receives an RRCReject message, terminal device 110 can terminate the SDT procedure.

[0037] In some embodiments, the SDT failure timer may also be reused as a monitoring timer. In some embodiments, the terminal device may determine that there is no response to an indication of non-SDT data when the SDT failure timer has finished. In some embodiments, a timer dedicated to sending indications of non-SDT data may be defined or set, and the terminal device 110 may determine that there is no response to an indication of non-SDT data based on both the timer dedicated to sending indications of non-SDT data and the SDT failure timer. For example, when either of these two timers finishes, the terminal device 110 may determine that there is no response to an indication of non-SDT data. In some embodiments, the SDT failure timer may be stopped when the timer dedicated to sending indications of non-SDT data is started or when an indication of non-SDT data is sent. For example, if an indication of non-SDT data is sent very close to the end of the SDT failure timer (e.g., only a few milliseconds until the SDT failure timer ends), stopping the SDT failure timer when the indication of non-SDT data is sent, or when a timer dedicated to sending indications of non-SDT data is started, allows sufficient time for the network device 120 to respond to the indication. Therefore, stopping the SDT failure timer ensures that the network has time to respond to the non-SDT data, which would otherwise cause the timer to end immediately.

[0038] In addition to or instead of a monitoring timer, the terminal device 110 may employ other methods to determine that there is no response to an indication of non-SDT data. In some embodiments, the terminal device 110 may employ a counter to count the number of times an indication of non-SDT data is sent or retransmitted in order to determine that there is no response to an indication of non-SDT data. In this case, a "max_amount_of_times" for the number of times the indication is sent or retransmitted can be predetermined. When the number of times the indication is sent or retransmitted reaches "max_amount_of_times", the terminal device 110 may determine that there is no response to an indication of non-SDT data. In some embodiments, the sending or retransmission of the indication is triggered based on a timer or the Non-Access Layer (NAS). For example, the terminal device 110 may periodically send an indication of non-SDT data based on a timer, or send an indication based on an indication in the NAS. In some embodiments, the number of times the indication is sent or retransmitted may be performed and maintained by the Radio Link Control (RLC) layer. For example, when the maximum number of RLC retransmissions is reached, the terminal device 110 may determine that there is no response to the indication of non-SDT data.

[0039] In some embodiments, different end times for the "max_amount_of_times" of timers and counters for monitoring may be predetermined based on different services, signaling or data radio bearers (SRB or DRB), trigger types, and establishment causes, or they may be changed dynamically on demand.

[0040] If terminal device 110 determines that there is no response to the indication of non-SDT data, terminal device 110 takes actions including entering an idle or inactive state and / or sending a connection setup or restart request to network device 120 (240) (230).

[0041] In some embodiments, the terminal device 110 may terminate the SDT procedure and enter an idle or inactive state. In some embodiments, the terminal device may initiate a connection setup or restart request to the network device 120 by sending an RRCSetupRequest or an RRCResumeRequest.

[0042] In this way, non-SDT data can be transmitted in a timely manner, and transmission delays can be reduced.

[0043] Figure 3 shows a flowchart of an exemplary method 300 implemented on a terminal device according to some embodiments of the present disclosure.

[0044] Method 300 can be performed on the terminal device 110 shown in Figure 1. For illustrative purposes, Method 300 will be described with reference to Figure 1. Naturally, Method 300 may include additional operations not shown and / or some of the operations shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0045] At 310, the terminal device 110 sends an indication of the availability of non-small data transmission (SDT) data to the network device 120 during the SDT procedure.

[0046] At 320, terminal device 110 monitors the response to the indication.

[0047] At 330, the terminal device 110 takes action in response to the lack of response to the indication. The action includes entering an idle or inactive state and / or initiating a connection setup or restart request to the network device 120.

[0048] In some embodiments, non-SDT data includes data available on wireless bearers that are not configured to enable SDT.

[0049] In some embodiments, monitoring the response to an indication includes monitoring the response to an indication until a monitoring timer expires or until a predetermined number of non-SDT data indications have been transmitted.

[0050] In some embodiments, the monitoring timer includes at least one of the following: an SDT failure timer, a timer dedicated to transmitting non-SDT data indications, a T319 timer, and a user equipment (UE) assistance information prohibition timer.

[0051] In some embodiments, method 300 further includes retransmitting the indicator at the end of the timer, or retransmitting the indicator based on an indicator from the Non-Access Layer (NAS).

[0052] In some embodiments, a monitoring timer is started when an indication is sent, and / or the monitoring timer is stopped at least one of the following: when a cell reselection is initiated by the terminal device, or when a response to the indication is received.

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

[0054] In some embodiments, non-SDT data indication is transmitted in at least one of RRC messages, MAC signaling, PHY signaling, and UE assistant information.

[0055] Figure 4 is a simplified block diagram of a device 400 suitable for carrying out exemplary embodiments of the present disclosure. The device 400 can be implemented in the terminal device 110 shown in Figure 1.

[0056] As shown in the figure, device 400 comprises 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 for bidirectional communication, for example, via multiple antennas or cables. The communication interface may represent any interface necessary for communication.

[0057] Program 440 is assumed to include program instructions, which, when executed by the associated processor 410, enable the device 400 to operate according to exemplary embodiments of the disclosure, as described herein with reference to Figures 1 and 2. These exemplary embodiments may be implemented by computer software, hardware, or a combination of software and hardware, executable by the processor 410 of the device 400. The processor 410 may be configured to implement various exemplary embodiments of the disclosure.

[0058] Memory 420 may be of any type suitable for a local technical network and may be implemented using any suitable data storage technology, such as non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. Although only one memory 420 is shown for device 400, device 400 may contain several physically separate memory modules. Processor 410 may be of any type suitable for a local technical network and may include, as non-limiting examples, one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 400 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock that synchronizes the main processor.

[0059] When device 400 functions as terminal device 110, processor 410 can perform the operations or actions of the first device 110 as described above, with reference to Figures 2 and 3. For simplicity, details are omitted.

[0060] Generally, the various exemplary embodiments of this disclosure may be implemented in hardware, dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various embodiments of the exemplary embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or some other graphical representations, the blocks, apparatus, systems, techniques, or methods described herein may, in non-limiting examples, be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, or other computing devices, or some combination thereof.

[0061] This disclosure also provides at least one computer program product tangibly stored in a non-temporary computer-readable storage medium. This computer program product includes computer-executable instructions, such as those contained in a program module and executed on a device on a target real or virtual processor, to perform the operations and actions described above with reference to Figures 1 to 3. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, or similar entities that perform a specific task or implement a specific abstract data type. The functions of program modules may be combined or divided among program modules as needed in various exemplary embodiments. The machine-executable instructions of a program module may be executed in a local device or in a distributed device. In a distributed device, the program module may reside on both local and remote storage media.

[0062] Program code for performing the methods disclosed 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, a dedicated computer, or other programmable data processing device, and when the program code is executed by the processor or controller, the functions or operations defined in the flowchart and / or block diagrams are performed. The program code may run entirely on a machine, partially on a machine as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0064] Computer-readable media may be computer-readable signal media or computer-readable storage media. Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media may include electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), digital multipurpose disks (DVDs), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0065] Furthermore, although the operations are shown in a specific order, this should not be understood as requiring that such operations be performed in a specific order shown, or sequentially, or that all illustrated operations be performed in order to obtain the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although details of several specific embodiments are included in the foregoing description, these should not be construed as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to particular exemplary embodiments. Certain features described in the context of separate exemplary embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple exemplary embodiments or in any suitable subcombination.

[0066] While this disclosure uses language specific to structural features and / or methodological actions, the disclosure as defined in the attached claims is not necessarily limited to the specific features or actions described herein. Rather, the specific features and actions described above are disclosed as exemplary forms for carrying out the claims.

[0067] Various exemplary embodiments of this technology are described. In addition to or as an alternative to the above, the following examples are provided. Features described in any of the following examples can be used in conjunction with any of the other examples described herein.

[0068] In some embodiments, the terminal device comprises at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured to cause the terminal device to use at least one processor to send an indication of the availability of non-small data transmission (SDT) data to a network device during an SDT procedure, monitor for a response to the indication, and, in response to no response to the indication, perform actions including entering an idle or inactive state and / or initiating a connection setup or restart request to the network device.

[0069] In some exemplary embodiments, non-SDT data includes available data on a wireless bearer that is not configured to enable SDT.

[0070] In some exemplary embodiments, the terminal device is made to monitor the response to the indication by monitoring the response to the indication until a monitoring timer expires or until a predetermined number of non-SDT data indications have been sent.

[0071] In some exemplary embodiments, the monitoring timers include at least one of the following: an SDT failure timer, a timer dedicated to transmitting non-SDT data indications, a T319 timer, and a user equipment (UE) assistance information prohibition timer.

[0072] In some exemplary embodiments, the terminal device is further instructed to retransmit the indication when the timer ends, or to retransmit the indication based on an indication from the Non-Access Layer (NAS).

[0073] In some exemplary embodiments, a monitoring timer is started when an indication is sent, and / or the monitoring timer is stopped at least one of the following: when a cell reselection is initiated by the terminal device, or when a response to the indication is received.

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

[0075] In some exemplary embodiments, the indication is transmitted in at least one of the following: RRC messages, MAC signaling, PHY signaling, and UE assistant information.

[0076] In some embodiments, the device implemented in the terminal device includes means for sending an indication of the availability of non-small data transmission (SDT) data to a network device during the SDT procedure; means for monitoring a response to the indication; and means for performing actions in response to no response to the indication, including entering an idle or inactive state and / or initiating a connection setup or restart request to the network device.

[0077] In some exemplary embodiments, non-SDT data includes available data on a wireless bearer that is not configured to enable SDT.

[0078] In some exemplary embodiments, means for monitoring responses to indications include means for monitoring responses to indications until a monitoring timer expires or until a predetermined number of non-SDT data indications have been transmitted.

[0079] In some exemplary embodiments, the monitoring timers include at least one of the following: an SDT failure timer, a timer dedicated to transmitting non-SDT data indications, a T319 timer, and a user equipment (UE) assistance information prohibition timer.

[0080] In some exemplary embodiments, the device further includes means for retransmitting an indication when a timer has finished, or means for retransmitting an indication based on an indication from the Non-Access Layer (NAS).

[0081] In some exemplary embodiments, a monitoring timer is started when an indication is sent, and / or the monitoring timer is stopped at least one of the following: when a cell reselection is initiated by the terminal device, or when a response to the indication is received.

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

[0083] In some exemplary embodiments, the indication is transmitted in at least one of the following: RRC messages, MAC signaling, PHY signaling, and UE assistant information.

[0084] In some embodiments, a computer-readable storage medium having instructions, when executed on at least one processor, causes at least one processor to perform the steps of the above embodiments.

Claims

1. Terminal device, At least one processor, At least one memory containing computer program code and Equipped with, The at least one memory and the computer program code are used by the at least one processor to connect to the terminal device. Sending an indication of the availability of non-small data transmission (SDT) data to a network device during the SDT procedure, To monitor the response to the aforementioned indication, The system is configured to perform an action in response to the absence of the aforementioned response to the indication of the non-SDT data, and the action is: Entering an idle or inactive state, and / or Sending a connection setup or restart request to the network device. The terminal device including the terminal device.

2. The terminal device according to claim 1, wherein the non-SDT data includes available data on a wireless bearer that is not configured to enable SDT.

3. The terminal device receives the response to the indication, By monitoring the response to the indication until the monitoring timer expires or until a predetermined number of transmissions of the non-SDT data indication has been made, A terminal device according to claim 1, which is used for monitoring.

4. The timer for monitoring, SDT failure timer, The non-SDT data is transmitted by the dedicated timer of the indication. T319 timer, and, User Equipment (UE) Assistance Information Prohibition Timer The terminal device according to claim 3, comprising at least one of the following.

5. The aforementioned terminal device further includes, The indicator is retransmitted when the timer ends, or Retransmitting the indication based on the indication from the Non-Access Layer (NAS). A terminal device according to claim 3, which enables the following:

6. The timer for monitoring is started when the indication is transmitted, and / or The timer for monitoring is stopped at least one of the following: when cell reselection is initiated by the terminal device, or when the response to the indication is received. The terminal device according to claim 3.

7. The aforementioned response is, RRCResume message, RRCSetup message, RRCRelease message, RRCRelease with the suspendedConfig message, or RRCReject message The terminal device according to claim 6, comprising at least one of the following.

8. The aforementioned indication is RRC message, MAC Signaling, PHY signaling, and, UE Assistant Information The terminal device according to claim 1, which transmits using at least one of the following methods.

9. A method performed on a terminal device, Sending an indication of the availability of non-small data transmission (SDT) data to a network device during the SDT procedure, To monitor the response to the aforementioned indication, In response to the absence of the aforementioned response to the aforementioned indication, Entering an idle or inactive state, and / or, Initiating a connection setup or resumption request to the aforementioned network device. Performing an action that includes The method, including the method described above.

10. The method according to claim 9, wherein the non-SDT data includes data available on a wireless bearer that is not configured to enable SDT.

11. Monitoring the response to the indication is The monitoring timer is terminated, or the number of transmissions of the non-SDT data indication is limited to the number of times the non-SDT data indication is transmitted, until the response from the network device to the non-SDT data indication is monitored. The method according to claim 9, including the method described in claim 9.

12. The aforementioned monitoring timer, SDT failure timer, The non-SDT data is transmitted by the dedicated timer of the indication. T319 timer, and, User Equipment (UE) Assistance Information Prohibition Timer The method according to claim 11, comprising at least one of the following.

13. The indicator is retransmitted when the timer ends, or The method according to claim 11, further comprising retransmitting the indication based on an indication from the Non-Access Layer (NAS).

14. The monitoring timer is started when the indication is transmitted, and / or The monitoring timer is stopped at least one of the following: when cell reselection is initiated by the terminal device, or when the response to the indication is received. The method according to claim 11.

15. The above response is, RRCResume message, RRCSetup message, RRCRelease message, RRCRelease with the suspendedConfig message, or RRCReject message The method according to claim 14, comprising at least one of the following.

16. The aforementioned indication is RRC message, MAC Signaling, PHY signaling, and, UE Assistant Information The method according to claim 9, transmitted by at least one of the following.

17. A device that is implemented on a terminal device, Means for sending an indication of the availability of non-small data transmission (SDT) data to a network device during the SDT procedure, Means for monitoring the response to the indication, In response to the absence of the aforementioned response to the aforementioned indication, Entering an idle or inactive state, and / or, Initiating a connection setup or resumption request to the aforementioned network device. Means for performing actions including The apparatus, including the above.

18. A computer-readable storage medium in which instructions are stored, wherein, when the instructions are executed on at least one processor, the computer-readable storage medium causes the at least one processor to perform the method according to any one of claims 9 to 16.

Images