Terminal device and method for communication

Abstract

[0003] Embodiments of the present disclosure relate to a method, apparatus, and computer-readable medium for communications. The communications method implemented by a terminal device includes entering an inactive state in response to receiving a message from a network device at the terminal device indicating that the terminal device will enter an inactive state. The message includes a resource configuration for data transmission between the terminal device and the network device. The method further includes performing the data transmission based on the resource configuration.

Description

[Technical Field]

[0001] FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to a method, apparatus, and computer-readable medium for data communication during inactivity. [Background technology]

[0002] Typically, even a terminal device in an inactive state may have small and infrequent data traffic to transmit. Until 3GPP Release 16, data transmission in the inactive state could not be supported, and the terminal device must re-establish a connection for downlink and uplink data transmission. The establishment of a connection and its subsequent release to the inactive state occurs for every data transmission, even if the data packets are small and infrequent. This leads to unnecessary power consumption and signaling overhead.

[0003] In this regard, 3GPP Release 17 allows small and infrequent data traffic based on the random access channel (RACH) and pre-configured physical uplink shared channel (PUSCH) resources in the inactive state, which has led to a debate about how to transmit small and infrequent data traffic. Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, embodiments of the present disclosure provide a method, apparatus, and computer-readable medium for data communication during inactivity. [Means for solving the problem]

[0005] In a first aspect, a communication method is provided, the method including: entering an inactive state in response to receiving, at the terminal device, a message from a network device indicating that the terminal device is entering an inactive state, the message including a resource configuration for the data transmission between the terminal device and the network device, the method further including performing the data transmission based on the resource configuration.

[0006] In a second aspect, a communication method is provided, the method including: transmitting a message from a network device to a terminal device indicating that the terminal device will be in an inactive state; the message including a resource configuration for data transmission between the terminal device and the network device; and performing the data transmission based on the resource configuration.

[0007] In a third aspect, there is provided a terminal device, the terminal device comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform a method according to the first aspect of the present disclosure.

[0008] In a fourth aspect, there is provided a network device comprising a processor and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the network device to perform a method according to the second aspect of the present disclosure.

[0009] In a fifth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the first aspect of the present disclosure.

[0010] In a sixth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the second aspect of the present disclosure.

[0011] Other features of the present disclosure will become readily apparent from the following description.

[0012] The above and other objects, features and advantages of the present disclosure will become more apparent through more detailed descriptions of several embodiments of the present disclosure in the accompanying drawings. [Brief explanation of the drawings]

[0013] [Figure 1] 1 illustrates an exemplary communication network in which some embodiments of the present disclosure may be implemented. [Figure 2] 1 shows an example signaling chart illustrating an example process for data transmission in an inactive state, in accordance with some embodiments of the present disclosure. [Figure 3] 10 shows an example signaling chart illustrating an example process for data transmission in an inactive state according to another embodiment of the present disclosure. [Figure 4] 1 illustrates an exemplary communication method implemented in a terminal device, according to some embodiments of the present disclosure. [Figure 5] 1 illustrates an exemplary communication method implemented in a network device, according to some embodiments of the present disclosure. [Figure 6] FIG. 1 is a schematic block diagram of an apparatus suitable for practicing embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0014] Throughout the drawings, the same or similar reference numbers represent the same or similar elements.

[0015] The principles of the present disclosure will be described with reference to several embodiments. It should be understood that these embodiments are set forth for illustrative purposes only, to aid those skilled in the art in understanding and practicing the present disclosure, and are not intended to imply any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in a variety of ways other than those described below.

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

[0017] 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, mobile 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, vehicle-mounted devices for V2X communications (where X represents pedestrians, vehicles, or infrastructure / networks), imaging devices such as digital cameras, gaming devices, music storage and playback devices, and Internet devices enabling wireless / wired Internet access and browsing. The term "terminal device" can be used interchangeably with UE, mobile station, subscriber equipment, mobile terminal, user terminal, or wireless device. The term "network device" refers to a device capable of providing or hosting a cell or coverage area over which terminal devices can communicate. Examples of network devices include, but are not limited to, a Node B (NodeB or NB), an Evolved NodeB (eNodeB or eNB), a next generation NodeB (gNB), a transmit / receive point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a low power node such as a femto node, a pico node, and the like.

[0018] In one embodiment, a terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a master node, and the other may be a secondary node. The first network device and the second network device may use different RATs. In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, first information may be transmitted from the first network device to the terminal device, and second information may be transmitted from the second network device directly to the terminal device or via the first network device. In one embodiment, information related to a configuration of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information related to a reconfiguration of the terminal device set by the second network device may be transmitted from the second network device to the terminal device directly or via the first network device.

[0019] As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "comprises" and variations thereof are intended to be open-ended, meaning "including, but not limited to." The term "based on" is intended to mean "based at least in part on." The terms "one embodiment" and "one embodiment" are intended to mean "at least one embodiment." The term "another embodiment" is intended to mean "at least one other embodiment." Terms such as "first," "second," etc. may refer to different objects or the same object. The following content may include other definitions, both explicit and implicit.

[0020] In some instances, values, processes, or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It is understood that such descriptions are intended to indicate choices among multiple functional alternatives used, and that such choices are not necessarily better, smaller, higher, or more preferred than other choices.

[0021] 1 illustrates a schematic diagram of an exemplary communication network 100 in which embodiments of the present disclosure can be implemented. As shown in FIG. 1, communication network 100 includes a network device 110 and a terminal device 120 that is serviced by network device 110. Network device 110 and terminal device 120 may communicate over a channel, such as a wireless communication channel. For example, terminal device 120 may transmit uplink data to network device 110, and network device 110 may transmit a response to receiving the uplink data to terminal device 120.

[0022] 1 are shown for illustrative purposes only and are not intended to imply any limitations on the present disclosure. Communication network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing the present disclosure. Furthermore, communication network 100 may include any devices other than network devices and terminal devices, such as core network elements, which are omitted herein to avoid obscuring the present disclosure.

[0023] Communications in communication network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution (LTE-Evolution), LTE Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communications (MTC), etc. Furthermore, communications may be performed according to any currently known or future-developed generation of communication protocols. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols.

[0024] As mentioned above, even an inactive terminal device 120 may have small, infrequent data traffic to transmit. Such data transmissions are hereinafter also referred to as small data transmissions (SDT). In some embodiments, small, infrequent data traffic may include smartphone applications such as traffic from instant messaging (IM) services (e.g., WhatsApp, QQ, WeChat), heartbeat / keep-alive traffic from IM / email clients and other applications, and push notifications from various applications. In some embodiments, small, infrequent data traffic may also include non-smartphone applications such as traffic from wearables (e.g., periodic location information), sensors (e.g., industrial wireless sensor networks that transmit temperature and pressure measurements periodically or in an event-triggered manner), and smart meters and smart meter networks that transmit periodic meter measurements.

[0025] Currently, to perform SDT when a terminal device is inactive, a RACH-based method / communication on a pre-configured PUSCH is permitted. However, no further detailed solution has been proposed for the general procedure of SDT. The embodiments of the present disclosure provide a solution for SDT. SDT is realized by the solution according to the embodiments of the present disclosure. The principles and implementations of the present disclosure will be described in detail below with reference to the drawings.

[0026] 2 shows an example signaling diagram illustrating an example process 200 for data transmission in an inactive state according to some embodiments of the present disclosure. For purposes of discussion, process 200 will be described with reference to FIG. 1. Process 200 may involve terminal device 120 and network device 110 shown in FIG. 1.

[0027] When the terminal device 120 receives a message from the network device 110 (210), the terminal device 120 goes into an inactive state (220). The message indicates that the terminal device 120 is going into an inactive state. The message includes resource configuration for data transmission between the terminal device 120 and the network device 110.

[0028] In the inactive state, terminal device 120 performs data transmission based on the resource configuration. In some embodiments, upon entering the inactive state, terminal device 120 transmits uplink data to network device 110 based on the resource configuration (230). In some embodiments, upon entering the inactive state, terminal device 120 receives downlink data from network device 110 based on the resource configuration (240).

[0029] In an embodiment of the present disclosure, a general procedure for data transmission in an inactive state is provided.

[0030] In some embodiments, before receiving the message, terminal device 120 is in the connected state. In such embodiments, terminal device 120 transitions from the connected state to the inactive state upon receiving the message.

[0031] In some embodiments, the message may include a Radio Resource Control (RRC) Release message. Of course, other messages besides an RRC Release message may also be applied. The scope of the present disclosure is not limited thereto.

[0032] In some embodiments, the message may further include a suspend setting for inactivity.

[0033] In some embodiments, the suspend configuration may include at least one of the terminal device 120's complete inactive radio network temporary identifier (I-RNTI), the terminal device 120's short I-RNTI, a paging cycle, RAN-Notification Area Information, a periodic RNAU timer value, or a next hop chaining count.

[0034] Conventionally, when a UE receives a message containing a suspend configuration, it applies the received suspend configuration, deletes all entries in VarConditionalConfig (if any), resets the Medium Access Control (MAC) and releases the Default MAC cell group configuration (if any), re-establishes the Radio Link Control (RLC) entity for Signaling Radio Bearer 1 (SRB1), suspends all SRBs and Data Radio Bearers (DRBs) except SRB0, indicates to lower layers for all DRBs that the Packet Data Convergence Protocol (PDCP) is suspended, indicates to higher layers that the RRC connection is suspended, transitions to RRC_INACTIVE, and performs cell selection as specified in TS38.304.

[0035] However, when an RRC Release message with suspend setting is received, the MAC is reset and the Timing Advance (TA) is invalidated, which results in the inability to execute subsequent SDT. Therefore, if the RRC Release message with suspend setting includes resource settings for data transmission, a different procedure from the conventional one must be used.

[0036] In this regard, in some embodiments, upon receiving a message including a suspend configuration and a resource configuration for data transmission, terminal device 120 maintains the state of the MAC entity at terminal device 120. In other words, terminal device 120 does not reset the MAC entity.

[0037] In some embodiments, when the terminal device 120 receives a message including a suspend setting and a data transmission resource setting, the terminal device 120 maintains the DRB for data transmission. In other words, the terminal device 120 does not suspend the DRB for data transmission.

[0038] In some embodiments, upon receiving a message including a suspend configuration and a resource configuration for data transmission, terminal device 120 maintains the state of the PDCP entity at terminal device 120. In other words, terminal device 120 does not suspend the PDCP entity.

[0039] In some embodiments, upon receiving a message including a suspend configuration and a resource configuration for data transmission, terminal device 120 suspends all SRBs except SRB0.

[0040] In some embodiments, the message from network device 110 further includes the configuration of an active bandwidth portion (BWP) other than the initial BWP for terminal device 120. In such embodiments, terminal device 120 may perform data transmissions in an active BWP other than the initial BWP.

[0041] 3 shows an example signaling diagram illustrating an example process 300 for data transmission in an inactive state in accordance with another embodiment of the present disclosure. For purposes of discussion, the process 300 will be described with reference to FIG. 1. The process 300 may involve the terminal device 120 and the network device 110 shown in FIG. 1. The process 300 may relate to an SDT based on a RACH scheme and a subsequent SDT.

[0042] The terminal device 120 in an inactive state transmits a random access preamble to the network device 110 (310). Upon receiving the random access preamble, the network device 110 transmits a random access response to the terminal device 120 (320).

[0043] Terminal device 120 sends (330) a request to remain inactive to network device 110. In some embodiments, terminal device 120 sends the request to network device 110 along with the uplink data.

[0044] In some embodiments, the request may include an RRC Resume Request or an RRC Resume Request 1.

[0045] The network device 110 sends (340) a message to the terminal device 120. The message indicates that the terminal device 120 will be inactive. The message includes resource configuration for data transmission. Unlike the message sent at 210 in process 200, the message sent at 340 may be sent along with downlink data.

[0046] Similar to process 200, if terminal device 120 receives the message, terminal device 120 enters an inactive state (220). In the inactive state, terminal device 120 transmits uplink data to network device 110 based on the resource configuration (230). In some embodiments, once in the inactive state, terminal device 120 receives downlink data from network device 110 based on the resource configuration (240).

[0047] Although the process 300 is described in the context of a four-step random access procedure, it should be understood that the process 300 also applies to a two-step random access procedure.

[0048] Conventionally, radio link monitoring and radio link failure (RLF) detection are supported only for terminal devices in a connected state.

[0049] In the connected state, the terminal device performs radio link monitoring (RLM) in the active BWP based on the reference signal and signal quality threshold set by the network device. The reference signal may include at least one of a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS). SSB-based RLM is based on the SSB associated with the initial DL BWP and is configurable only for the initial DL BWP and DL BWPs containing the SSB associated with the initial DL BWP. For other DL BWPs, RLM can only be performed based on the CSI-RS. In the case of a DAPS handover, the terminal device continues RLM in the source cell until the random access procedure to the target cell is successfully completed.

[0050] The terminal device declares a Radio Link Failure (RLF) if one of the following criteria is met: expiry of a radio problem timer started after notification of a radio problem from the physical layer (if the radio problem recovers before the timer expires, the terminal device terminates the timer), expiry of a timer started when a measurement report for a measurement identity for which the timer was set is triggered while another radio problem timer is running, failure of the random access procedure, RLC failure, failure of the random access procedure, or after detection of a consistent uplink LBT (Listen Before Talk) failure for operation with shared spectrum channel access.

[0051] Conventionally, after RLF is declared, the terminal device may perform at least one of the following: maintain a connected state; select a suitable cell and then initiate RRC re-establishment; or enter an idle state if no suitable cell is found within a certain time after RLF is declared.

[0052] During SDT in the inactive state, there may be a gap between the coverage for cell reselection and the coverage for data transmission. This means that the radio signal is too weak to transmit data successfully, but cell reselection has not yet occurred. If the terminal device is still in SDT, significant delays will occur.

[0053] To solve the above problems, an RLF-related process is proposed for a terminal device that executes SDT in an inactive state.

[0054] In some embodiments, terminal device 120 detects RLF during data transmission in an inactive state.

[0055] In some embodiments, terminal device 120 detects and declares RLF if one of the following criteria is met: expiration of a radio problem timer started after notification of a radio problem from the physical layer (when T310 in PScel expires), an RLC failure (i.e., maximum number of retransmissions reached), a random access procedure failure, or a consistent LBT failure.

[0056] In some embodiments, the terminal device 120 detects radio problems by performing RLM in an active BWP based on a reference signal (such as SSB or CSI-RS) and signal quality thresholds set by the network device 110.

[0057] In some embodiments, upon detecting RLF, terminal device 120 mitigates RLF by initiating a connection resumption procedure to network device 110 .

[0058] In some embodiments, to initiate the connection resumption procedure, terminal device 120 sends a request to network device 110 to resume the first RRC connection between terminal device 120 and network device 110. In some embodiments, terminal device 120 sends the request to network device 110 without uplink data.

[0059] In some embodiments, upon detecting RLF, terminal device 120 mitigates RLF by resetting the MAC entity.

[0060] In some embodiments, upon detecting RLF, terminal device 120 mitigates RLF by suspending all DRBs.

[0061] In some embodiments, upon detecting RLF, terminal device 120 mitigates RLF by going into an idle state.

[0062] In some embodiments, terminal device 120 enters the idle state by releasing the resource configuration received from network device 110 .

[0063] According to some embodiments of the present disclosure, radio link monitoring and RLF detection during data transmission can detect radio link problems when performing SDT in an inactive state, and the terminal device can take steps to avoid service interruptions.

[0064] Currently, when a terminal device enters the RRC idle state, three types of release causes can be provided to the upper layer: "other", "RRC connection failure", and "RRC resume failure". However, these three release causes are not suitable for SDT failure.

[0065] In some embodiments, upon entering the idle state, terminal device 120 provides a notification to the non-access stratum (NAS). This notification indicates a failure of data transmission during the inactive state. This notification is also referred to hereinafter as a release cause. The failure of data transmission is also referred to as an SDT failure.

[0066] In some embodiments, if timer T319 expires or a consistency check failure indication is received from lower layers while timer T319 is running and an RRC resumption procedure is initiated for SDT, the terminal device 120 performs an action when entering idle state with a release cause indicating "SDT failure".

[0067] Table 1 shows the details of timer T319. [Table 1] Table 1

[0068] In some embodiments, if a cell reselection occurs while timer T319 or timer T302 is running and an RRC resumption procedure is initiated due to SDT, the terminal device 120 performs an action on going to idle state with a release cause indicating an SDT failure.

[0069] Table 2 shows the details of timer T302. [Table 2] Table 2

[0070] In some embodiments, if terminal device 120 detects an RLF during a subsequent SDT or a configured grant SDT, it performs an action upon going to idle state with a release cause indicating "SDT failure."

[0071] According to some embodiments of the present disclosure, when a release cause indicating "SDT failure" is provided to the NAS, the NAS layer may transition from a Connection Management (CM)-Connected state to a CM-Idle state due to the state transition reason.

[0072] 4 illustrates an exemplary communication method 400 implemented in a terminal device according to some embodiments of the present disclosure. For example, method 400 may be performed in terminal device 120 as shown in FIG. 1. For purposes of discussion, method 400 is described below with reference to FIG. 1. It should be understood that method 400 may include additional blocks not shown and / or omit some blocks shown, and that the scope of the present disclosure is not limited in this respect.

[0073] In block 410, terminal device 120 enters an inactive state when terminal device 120 receives a message from network device 110 indicating that terminal device 120 is entering an inactive state. The message includes resource configuration for data transmission between the terminal device and the network device.

[0074] In block 420, terminal device 120 performs data transmission based on the resource configuration.

[0075] In some embodiments, terminal device 120 is in a connected state before receiving the message. Becoming inactive includes transitioning from a connected state to an inactive state.

[0076] In some embodiments, the state of the media access control entity at the terminal device is maintained.

[0077] In some embodiments, a data radio bearer is maintained for data transmission.

[0078] In some embodiments, the state of a packet data convergence protocol entity at the terminal device is maintained.

[0079] In some embodiments, the message further includes setting an active band other than the initial band for the terminal device, and performing the data transmission includes performing the data transmission in the active band.

[0080] In some embodiments, the method 400 further includes detecting a radio link failure during data transmission in an inactive state.

[0081] In some embodiments, the method 400 further includes, in response to detecting the radio link failure, mitigating the radio link failure by initiating a connection resumption procedure to the network device.

[0082] In some embodiments, initiating the connection resumption procedure includes sending a request to the network device for resumption of the first radio resource control connection between the terminal device and the network device.

[0083] In some embodiments, transmitting the request includes transmitting the request without uplink data.

[0084] In some embodiments, the method 400 further includes, in response to detecting the radio link failure, mitigating the radio link failure by going into an idle state.

[0085] In some embodiments, the method 400 further includes entering the idle state in response to at least one of the following: expiration of timer T319, receiving a consistency check failure indication from a lower layer while timer T319 is running, or cell reselection occurring while timer T319 or timer T302 is running.

[0086] In some embodiments, becoming idle includes releasing a resource configuration.

[0087] In some embodiments, the method 400 further includes providing a notification to the non-access stratum indicating a failure of data transmission in the inactivity state.

[0088] 5 illustrates an exemplary communication method 500 implemented in a network device according to some embodiments of the present disclosure. For example, method 500 may be performed in network device 110 as shown in FIG. 1. For purposes of discussion, method 500 is described below with reference to FIG. 1. It should be understood that method 500 may include additional blocks not shown and / or omit some blocks shown, and that the scope of the present disclosure is not limited in this respect.

[0089] In block 510, network device 110 sends a message to terminal device 120 indicating that the terminal device will be inactive. The message includes resource configuration for data transmission between the terminal device and the network device.

[0090] At block 520, the network device 110 performs data transmission based on the resource configuration.

[0091] In some embodiments, the message further includes setting an active bandwidth portion other than the initial bandwidth portion for the terminal device, and performing the data transmission includes performing the data transmission in the active bandwidth portion.

[0092] In some embodiments, the method 500 further includes receiving a request from the terminal device for resumption of the first radio resource control connection between the terminal device and the network device in response to a radio link failure during data transmission in an inactive state.

[0093] In some embodiments, receiving the request includes receiving the request without the uplink data.

[0094] Figure 6 is a schematic block diagram of an apparatus 600 suitable for implementing embodiments of the present disclosure. Apparatus 600 may be considered another exemplary implementation of network apparatus 110 or terminal apparatus 120 shown in Figure 1. Thus, apparatus 600 may be implemented in, or at least as part of, network apparatus 110 or terminal apparatus 120.

[0095] As shown, the device 600 includes a processor 610, a memory 620 coupled to the processor 610, a suitable transmitter (TX) and receiver (RX) 640 coupled to the processor 610, and a communication interface coupled to the TX / RX 640. The memory 620 stores at least a portion of a program 630. The TX / RX 640 is for bidirectional communication. The TX / RX 640 has at least one antenna to facilitate communication, although in practice, the access nodes described herein may have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNBs / gNBs, an S1 / NG interface for communication between a mobility management entity (MME) / access and mobility management function (AMF) / SGW / UPF and an eNB / gNB, a Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.

[0096] The program 630 may be considered to include program instructions that, when executed by an associated processor 610, enable the device 600 to operate in accordance with embodiments of the present disclosure, as discussed herein with reference to FIGS. 1-5. The embodiments herein may be implemented by computer software, hardware, or a combination of software and hardware executable by the processor 610 of the device 600. The processor 610 may be configured to implement various embodiments of the present disclosure. Additionally, the combination of the processor 610 and the memory 620 may constitute a processing means 650 suitable for implementing embodiments of the present disclosure.

[0097] Memory 620 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology (e.g., but not limited to, computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed and removable memory, etc.). Although only one memory 620 is shown in device 600, device 600 may include multiple physically distinct memory modules. Processor 610 may be of any type suitable for a local technology network and may include, by way of example and not limitation, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration. Device 600 may have multiple processors, e.g., application-specific integrated circuit chips time-slaved to a clock synchronized with a master processor.

[0098] Generally, various embodiments of the present disclosure may be implemented by hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented by hardware, while other aspects may be implemented by firmware or software that may be executed by a controller, microprocessor, or other computing device. Although aspects of the embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or illustrated by some other pictorial representation, it will be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented by, for example, but not limited to, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or combinations thereof.

[0099] The present disclosure further provides at least one computer program product tangibly stored on a computer-readable, non-transitory storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules. The instructions execute on a target real or virtual processor device to perform, for example, the processes or methods described above with reference to FIGS. 2-5. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split among program modules as desired. The machine-readable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may reside on both local and remote readable media.

[0100] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, and when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are performed. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0101] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that contains or stores a program used by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Even more specific examples of machine-readable storage media include one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable-writeable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0102] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order or sequence shown, or performing all of the operations shown, is required to achieve desired results. In some situations, multitasking and parallel processing may be advantageous. Similarly, while the above discussion includes several specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented in multiple embodiments separately or in any suitable subcombination.

[0103] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, A means for receiving resource configuration information, including configuration information of a Bandwidth part (BWP) for small data transmission (SDT), by a Radio Resource Control (RRC) Release message; means for transmitting data to a base station in the SDT procedure based on the resource setting information while remaining in an inactive state; based on means for receiving a consistency check failure indication from a lower layer during the SDT procedure, means for detecting that a maximum number of Radio Link Control (RLC) retransmissions has been reached during the SDT procedure, or means for detecting a random access failure during the SDT procedure; transition means for transitioning from the inactive state to an idle state; A terminal device comprising:

2. the transition means transitions to the idle state upon a release cause indicating a failure; The terminal device according to claim 1 .

3. The release cause indicates a failure of an RRC resumption procedure. The terminal device according to claim 2 .

4. and transition means for transitioning from the inactive state to the idle state with a release cause indicating a failure when a cell reselection occurs during the SDT procedure.

4. The terminal device according to claim 1.

5. 1. A method for communication performed by a terminal device, comprising: Receiving resource configuration information, including configuration information of a Bandwidth part (BWP) for small data transmission (SDT), by a Radio Resource Control (RRC) Release message; Executing data transmission to the base station in the SDT procedure based on the resource setting information while remaining in an inactive state; based on receiving a consistency check failure indication from a lower layer during the SDT procedure, detecting that a maximum number of RLC retransmissions has been reached during the SDT procedure, or detecting a random access failure during the SDT procedure, transitioning from the inactive state to an idle state; A method for communication, comprising:

6. The terminal device transitions to the idle state with a release cause indicating a failure. The method of claim 5.

7. The release cause indicates a failure of an RRC resumption procedure. The method of claim 6.

8. transitioning from the inactive state to the idle state with a release cause indicating failure if a cell reselection occurs during the SDT procedure; 8. The method according to any one of claims 5 to 7.

Images