Mobile incoming call small data transmission

Abstract

According to some embodiments of this disclosure, a solution for mobile incoming small data transmission (MT-SDT) is provided. In this solution, an RRC entity notifies a MAC entity of first information associated with an MT-SDT procedure and second information. Based on the second information, the MAC entity checks one or more conditions related to the initialization of the MT-SDT procedure. The MAC entity notifies the RRC entity of the second information, which is associated with the result of the condition check. Based on the second information, the RRC entity can decide whether or not to initiate the MT-SDT procedure.

Description

Technical Field

[0001] Various embodiments of the present disclosure generally relate to the field of telecommunications, and in particular, to methods, apparatuses, and computer-readable storage media for Mobile Terminated-Small Data Transmission (MT-SDT).

Background Art

[0002] With the development of communication systems, new technologies have been proposed. For example, Small Data Transmission (SDT) has been proposed. Specifically, SDT is the transmission of short data bursts in a connectionless state where a terminal device (e.g., a user equipment, UE) does not need to establish and disconnect a connection when it is necessary to transmit a small amount of data. In addition to Mobile Originated SDT (MO-SDT), MT-SDT has also been proposed. Therefore, it is valuable to study MT-SDT.

Summary of the Invention

[0003] In a first aspect of the present disclosure, an apparatus is provided. The apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least: the radio resource control (RRC) entity of the apparatus notifies the media access control (MAC) entity of the apparatus of first information associated with an MT-SDT procedure; the MAC entity determines whether one or more conditions related to the start of the MT-SDT procedure are satisfied based on the first information; the MAC entity notifies the RRC entity of second information based on the determination; and the RRC entity determines whether to start the MT-SDT procedure based on the second information.

[0004] A second aspect of this disclosure provides a method, which includes: an RRC entity of a terminal device notifying a MAC entity of the terminal device of first information associated with an MT-SDT procedure; the MAC entity determining, based on the first information, whether one or more conditions related to the initiation of an MT-SDT procedure are met; the MAC entity notifying the RRC entity of second information based on the determination; and the RRC entity determining, based on the second information, whether to initiate an MT-SDT procedure.

[0005] In a third aspect of the present disclosure, an apparatus is provided. The apparatus comprises means for the RRC entity of the apparatus to notify the MAC entity of the apparatus of first information associated with an MT-SDT procedure; means for the MAC entity to determine whether one or more conditions related to the initiation of an MT-SDT procedure are met based on the first information; means for the MAC entity to notify the RRC entity of second information based on the determination; and means for the RRC entity to determine whether to initiate an MT-SDT procedure based on the second information.

[0006] A fourth aspect of this disclosure provides a computer-readable medium, which includes instructions stored on the medium to cause a device to perform at least the method according to the second aspect.

[0007] It should be understood that the summary does not identify any important or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will be readily apparent through the following description. [Brief explanation of the drawing]

[0008] Several embodiments will be described with reference to the attached drawings. [Figure 1] Figure 1 shows an example of a communication environment in which the embodiments of this disclosure can be implemented. [Figure 2A]Figure 2A shows an example of a signaling chart for SDT. [Figure 2B] Figure 2B shows an example of a signaling chart for SDT. [Figure 2C] Figure 2C shows an example of a signaling chart for SDT. [Figure 3] Figure 3 shows a signaling chart for communication according to some embodiments of the present disclosure. [Figure 4] Figure 4 shows a flowchart of a method implemented in a terminal device according to some embodiments of the present disclosure. [Figure 5] Figure 5 shows a simplified block diagram of an apparatus suitable for carrying out an embodiment of the present disclosure. [Figure 6] Figure 6 is a block diagram showing an example of a computer-readable medium according to some embodiments of the present disclosure. Throughout the drawings, the same or similar reference numerals indicate the same or similar components. [Modes for carrying out the invention]

[0009] The principles of this specification will be explained with reference to several examples. These examples are not intended to limit the scope of this specification, but are provided solely for illustrative purposes to help those skilled in the art understand and implement this specification. The examples described herein can be implemented in various ways other than those described below.

[0010] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by an ordinary person skilled in the art to which this specification belongs.

[0011] In this specification, descriptions such as “one embodiment,” “embodiment,” and “exemplary embodiment” indicate that the described embodiment may include a particular function, structure, or feature, but not all embodiments are required to include such a particular function, structure, or feature. Furthermore, these expressions do not necessarily refer to the same embodiment. Also, if a particular function, structure, or characteristic is described in relation to an embodiment, it is assumed that the influence of that function, structure, or characteristic on other embodiments, whether explicitly stated or not, is within the knowledge of those skilled in the art.

[0012] While terms such as "first" and "second" may be used before nouns to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish elements and do not limit the order of nouns. For example, referring to the first element as the second element, or similarly referring to the second element as the first element, does not deviate from the scope of the examples. In this specification, the term "and / or" encompasses any combination of one or more of the terms described.

[0013] In this specification, where the phrases "at least one of the following: <list of two or more elements>" and "list of at least one or more elements," and similar expressions, lists of two or more elements connected by "and" or "or," these mean at least one of any two elements, at least two or more elements, or at least all of the elements.

[0014] In this specification, unless expressly stated otherwise, performing a step "in response to A" does not indicate that the step is performed immediately after the occurrence of "A," and that one or more steps may be included in between.

[0015] The terms used herein are intended solely to describe specific embodiments and are not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are intended to include the plural forms as well. Furthermore, the terms “equip,” “equip,” “have,” “possess,” “include,” and / or “include” herein identify the presence of the described features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0016] In this application, the term "circuit" is defined as follows: (a) Hardware-only circuit implementation (such as implementation using only analog and / or digital circuits), (b) A combination of hardware circuitry and software, for example (where applicable), (i) A combination of analog and / or digital hardware circuits and software / firmware, (ii) A combination of a part of a hardware processor, software (including a digital signal processor), software, and memory, which work together to enable devices such as mobile phones and servers to perform various functions. (c) Hardware circuits and / or processors (e.g., microprocessors or parts of microprocessors) that require software (e.g., firmware) for operation, but may not have software if it is not necessary for operation. This may refer to one or more of these, or all of them.

[0017] This definition of "circuit" applies to all uses of this term in this application, i.e., to all claims. For further examples, the term "circuit" as used in this application includes not only a hardware circuit or processor (or multiple processors), but also a part of a hardware circuit or processor and its associated software and / or firmware implementation. The term "circuit" also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device, where applicable to a particular claim element.

[0018] In this specification, the term “communication network” refers to a network that conforms to an appropriate communication standard, such as New Radio (NR), Long-Term Evolution (LTE), LTE Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA®), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communication between terminal devices and network devices within a communication network includes, but is not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), and sixth-generation (6G) communication protocols, and / or other protocols currently known or to be developed in the future. Embodiments of this disclosure are applicable to a variety of communication systems. Given the rapid development of communication technology, there will naturally be future communication technologies and systems to which this disclosure will be embodied. The scope of this disclosure is not limited to the aforementioned systems.

[0019] As used herein, the term "network device" refers to a node on a communication network through which a terminal device accesses the network and receives services therefrom. The network device may refer to, for example, a base station (BS), an access point (AP), a Node B (NodeB, or NB), an evolved Node B (eNodeB, or eNB), an NR Node B (also called a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an integrated access backhaul (IAB) node, a low-power node such as a femto or pico, a satellite network device, a non-terrestrial network (NTN) or non-terrestrial network device such as a low Earth orbit (LEO) satellite or a geostationary orbit (GEO) satellite, an aircraft network device, etc. This may vary depending on the terms and technologies applied. In some embodiments, a radio access network (RAN) split architecture includes a central unit (CU) and a distributed unit (DU) at an IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves like a UE with respect to the parent node and a DU portion that behaves like a base station with respect to the next IAB node.

[0020] The term "terminal device" refers to any end device capable of wireless communication. While these are merely examples, terminal devices may also be called communication devices, user equipment (UE), subscriber stations (SS), mobile subscriber stations, mobile stations (MS), and access terminals (AT). Terminal devices include mobile phones, mobile phone terminals, smartphones, VoIP phones, wireless local loop phones, tablet devices, wearable devices, PDAs, portable computers, desktop computers, digital cameras and other image capture devices, game terminals, music storage and playback devices, in-vehicle wireless terminals, wireless endpoints, mobile stations, laptop computers (LEE), laptop computers (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches and other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics, and devices operating on commercial and / or industrial wireless networks. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (such as a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user device," and "UE" may be used interchangeably.

[0021] In this specification, the terms "resource", "transmission resource", "resource block", "physical resource block (PRB)", "uplink resource", and "downlink resource" refer to any resource for communication. For example, in the communication between a terminal device and a network device, resources in the time domain, frequency domain, spatial domain, code domain, or any combination of resources in the time domain, frequency domain, spatial domain, and code domain that enable communication are applicable. Hereinafter, unless otherwise specified, resources in both the frequency domain and the time domain are used as examples of transmission resources to describe some embodiments of this specification. It should be noted that the embodiments of this specification are equally applicable to resources in other domains.

[0022] In this specification, the term "SDT" may refer to a procedure that enables data and / or signaling transmission while maintaining the RRC_INACTIVE (i.e., not transitioning to the RRC_CONNECTED state) state. Specifically, SDT is the transmission of short data bursts in a connectionless state where the device does not need to establish and disconnect a connection when it is necessary to transmit a small amount of data.

[0023] In this specification, the term "common random access (RA)" may refer to a random access that is not dedicated to SDT. Similarly, the terms "common random access channel (RACH)" or "common RA resource" may refer to an RACH or RA resource that is not dedicated to SDT, respectively.

[0024] FIG. 1 shows an example of a communication environment 100 in which embodiments of the present disclosure can be implemented. The communication environment 100 includes a terminal device 110. Hereinafter, the terminal device 110 is also referred to as a UE.

[0025] The terminal device 110 includes or implements entities for different layers. As shown in Figure 1, the terminal device 110 includes an RRC entity 130 and a media access control (MAC) entity 140. The RRC entity 130 and the MAC entity 140 may interact with each other. Furthermore, one or more RRC entities may reside in the RRC layer, and one or more MAC entities may reside in the MAC layer. In the following description, unless otherwise defined, "RRC entity" and "RRC layer" are interchangeable, and "MAC entity" and "MAC layer" are also interchangeable.

[0026] The communication environment 100 may also include a network device 120. Hereinafter, the network device 120 may also be called a gNB. The network device 120 can communicate with the terminal device 110.

[0027] The number of network devices, terminal devices, and entities shown in Figure 1 is for illustrative purposes only and does not imply any limitation. The communication environment 100 may include any appropriate number of network devices, terminal devices, and entities.

[0028] In some embodiments, the link from network device 120 to terminal device 110 is called a downlink (DL), and the link from terminal device 110 to network device 120 is called an uplink (UL). In a DL, network device 120 is a transmitting device (TX device), and terminal device 110 is a receiving device (RX device). In a UL, terminal device 110 is a transmitting device (TX device), and network device 120 is a receiving device (RX device).

[0029] Communication in communication environment 100 is implemented according to an appropriate communication protocol, which includes, but is not limited to, cellular communication protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), and sixth generation (6G), wireless local network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols currently known or to be developed in the future. Furthermore, communication may optionally utilize appropriate wireless communication technologies, which include, but is not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and other technologies currently known or to be developed in the future.

[0030] SDT can be applied to communication environment 100. For example, MT-SDT and MO-SDT are applicable to communication environment 100. MO-SDT is enabled on a per-wireless bearer basis and is initiated by the terminal device only when the amount of UL data waiting to transmit is less than a set value in all wireless bearers where SDT is enabled, the DL reference signal received power (RSRP) exceeds a set threshold, and valid SDT resources are available. Figures 2A to 2C show example signaling charts for SDT applicable to communication environment 100.

[0031] Figure 2A is a signaling chart 200A illustrating the operation of SDT based on a 4-step random access channel (RACH) (i.e., 4-step RA-SDT). As shown in Figure 2A, terminal device 110 can send message 1 (MSG1) to network device 120 (2010) when the radio resource control (RRC) is inactive. MSG1 includes a preamble for RACH. Network device 120 can send message 2 (MSG2) to terminal device 110 (2020). MSG2 includes a random access response. Terminal device 110 can send message 3 (MSG3) to network device 120 (2030). MSG3 includes an RRC connection resumption request. A small payload (i.e., small data) can be sent in MSG3. For example, the small payload can be multiplexed with the RRC connection resumption request. Network device 120 can send an RRC release message (2040). Figure 2B shows a signaling chart 200B illustrating the operation of a two-step RACH-based SDT (i.e., two-step RA-SDT). As shown in Figure 2B, when terminal device 110 is in an RRC inactive state, terminal device 110 can send message A (MSG A) to network device 120 (2110). MSG A may include a preamble for RACH. Small data is sent with MSG A. In particular, small data is sent over a physical uplink shared channel (PUSCH) resource that is pre-configured by network device 120 and broadcast in system information along with relevant physical transmission parameters. Network device 120 sends message B (MSG B) to terminal device 110 (2120). MSG B includes a random access response. Figure 2C shows a signaling chart 200C illustrating the operation of a configuration grant-based SDT (CG-SDT). When terminal device 110 is in an RRC connection state, terminal device 110 can receive (2210) a CG type 1 setting indicating a specific pre-configured PUSCH resource used for UL data transmission in an RRC inactive state, as long as timing adjustment is enabled.The network device 120 can send an RRC release message (2220).

[0032] MO-SDT for New Radio (NR) is defined. SDT is a procedure that enables data and / or signaling transmission while maintaining the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state). SDT is enabled on a per-radio bearer basis and is initiated by the UE only when, in all radio bearers with SDT enabled, there is UL data below a set value waiting to be transmitted, the DL RSRP exceeds a set threshold, and a valid SDT resource is available.

[0033] The SDT procedure is initiated by transmission via RACH (configured in system information) or a Type 1 CG resource (configured in RRCRelease or other RRC messages, dedicated signaling in information elements (IE)). SDT resources can be configured in the initial bandwidth portion (BWP) for both RACH and CG. RACH and CG resources for SDT can be configured on either a non-supplementary uplink (NUL) carrier, a supplementary uplink (SUL) carrier, or both. CG resources for SDT are only valid within the primary cell (PCell) of a UE that receives an RRC release with a suspend instruction. A CG resource is associated with one or more SSBs. For RACH, the network can configure 2-step and / or 4-step RA resources for SDT. If both 2-step and 4-step RA resources are configured for SDT, the UE selects the RA type. Contention-free random access (CFRA) is not supported for SDT over RACH.

[0034] Once initiated, the SDT procedure is performed. The UE completes successfully after being notified to transition to the RRC_IDLE state (via RRCRelease), or after being notified to continue in the RRC_INACTIVE state (via RRCRelease or RRCReject), or after being notified to transition to the RRC_CONNECTED state (via RRCResume or RRCSetup), or The SDT procedure fails when a cell is reselected, when the SDT failure detection timer expires, when a MAC entity reaches the configured maximum PRACH preamble transmission threshold, when an RLC entity reaches the configured maximum retransmission threshold, or when the SDT procedure is in progress on the CG and the SDT-specific timing adjustment timer expires while the UE has not received a response from the network after the initial PUSCH transmission. It will be one of the following.

[0035] If the SDT procedure does not complete successfully, the UE transitions to the RRC_IDLE state.

[0036] The initial PUSCH transmission during the SDT procedure includes at least a Common Control Channel (CCCH) message. If CG resources are used for the initial SDT transmission, the UE may autonomously retransmit the initial transmission if it does not receive confirmation from the network (dynamic UL grant or DL ​​assignment) before the configured timer expires. After the initial PUSCH transmission, subsequent transmissions are handled differently depending on the type of resource used to initiate the SDT procedure. When using CG resources, the network schedules subsequent UL transmissions using dynamic grants or transmissions occur on the next available CG resource opportunity. DL transmissions are scheduled using dynamic assignments. A UE can only initiate a subsequent UL transmission after receiving confirmation (dynamic UL grant or DL ​​assignment) for the initial PUSCH transmission from the network. In subsequent UL transmissions, the UE cannot initiate retransmissions via CG resources. When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic UL grants and DL assignments, respectively, after the RA procedure is complete.

[0037] If data is generated in the buffer of a non-SDT-enabled wireless bearer during the execution of the SDT procedure, the UE will send a notification of non-SDT data arrival to the network using a UEAssistanceInformation message, including the reason for resumption if possible.

[0038] The SDT procedure on the CG resource can only be initiated if there is valid UL timing adjustment. UL timing adjustment is maintained by the UE based on SDT-specific timing adjustment timers configured by the network using dedicated signaling. Additionally, during the initial CG-SDT transmission, it is maintained by a configured number of DL RSRPs from the highest-ranked SSBs that exceed the configured RSRP threshold. Once the SDT-specific timing adjustment timers expire, the CG resource is released while maintaining its configuration.

[0039] Logical channel restrictions set by the network in the RRC_CONNECTED state, and / or RRCRelease messages (if any) from radio bearers enabled for SDT, are applied by the UE during the SDT procedure.

[0040] The network may configure the UE to apply Robust Header Compression (ROHC) continuity to SDT when the UE initiates SDT at its PCell upon receiving an RRCRelease with a suspend instruction, or when the UE initiates SDT at a cell within its own Radio Notice Area (RNA).

[0041] The above description relates to MO-SDT. Currently, research is underway on MT-SDT for NR. For example, Release (Rel)-17 specified MO-SDT, which enables the transmission of small packets in the UL direction. In DL, MT-SDT (i.e., DL-triggered small data) offers similar advantages. Specifically, it reduces signaling overhead and UE power consumption by avoiding transitions to the RRC_CONNECTED state, and reduces latency by enabling high-speed transmission of packets (small capacity and infrequent) such as location information.

[0042] The goal is to specify support for paging-triggered SDT (i.e., MT-SDT). This includes an MT-SDT trigger mechanism for UEs in the RRC_INACTIVE state, support for RA-SDT and CG-SDT as UL responses, and an MT-SDT procedure for initial DL data reception and subsequent UL / DL data transmission in the RRC_INACTIVE state.

[0043] Regarding MT-SDT, some agreement has been reached. In RAN paging, an MT-SDT notification (at least 1 bit) is explicitly included for each UE via the paging message. In some exemplary embodiments, in Rel-18 MT-SDT after MT-SDT paging trigger detection, the RA-SDT and CG SDT solutions / procedures specified in Rel-17 are reused as a baseline. UEs can utilize non-SDT random access resources for network access for MT-SDT forwarding. Configuration grant resources and MO-RA resources can also be utilized. The network must be able to identify why the uplink access was triggered (i.e., implicit or explicit notification by the UE). MT-SDT is data belonging to bearers configured for SDT. Configuration will be MO-SDT or MT-SDT specific. The network can only trigger MT-SDT if the data belongs to those bearers. The network can configure MT-SDT only without MO-SDT RA resources or CG-SDT. Subsequent UL / DL data belonging to an SDT bearer is permitted even in an INACTIVE state, similar to the MT-SDT procedure. A single code point MT-SDT notification may be introduced as a new resumption cause in RRC resumption.

[0044] Furthermore, a 1-bit notification that triggers MT-SDT can be included in the paging. It is guaranteed that the Common Control Channel (CCCH) message can be transmitted via the CG. The notification is made on a per-UE basis. If the MT-SDT trigger condition by paging is not met, the UE initiates the RRC restart procedure.

[0045] When a UE restarts MT-SDT, it restarts all radio bearings (RBs) configured for SDT. RBs configured for SDT are common to both MO-SDT and MT-SDT. If a valid CG-SDT resource exists, the UE should use CG-SDT to transmit responses. If SDT is initiated by MT-SDT, the UE can exchange subsequent DL / UL SDT data over the restarted RBs.

[0046] A RRC restart procedure must be defined for initiating MT-SDT without verifying the availability of UL data (i.e., if MT-SDT is initiated first, the restart cause is set to MT-SDT). The UE may be permitted to initiate either an MT-SDT-based restart or a non-SDT-based restart using separate procedures at any time before initiating an MT-SDT RRCResumeRequest. Once the MT-SDT procedure is initiated, for subsequent RACHs during data transfer (i.e., RACHs triggered by scheduling requests), the UE can only utilize non-SDTRACH resources (i.e., as in the conventional method).

[0047] Based on the above, the UE does not check the availability of UL data at the start of MT-SDT, so the MO-SDT-RA resource may not be used for MT-SDT. However, the UE can trigger MO-SDT if there is UL data in the buffer, and in that case, the MO-SDT-RA resource will naturally be used as well. Therefore, RACH-based MT-SDT uses a common RACH that is not dedicated to SDT.

[0048] In the case of MO-SDT, the MAC layer simply notifies that the SDT procedure can be initiated from the MAC's perspective, but does not provide any information about the SDT resources available to the SDT. This principle does not apply to MT-SDT if the MT-SDT procedure does not utilize MO-SDT RACH resources. Some solutions do not take into account that MT-SDT cannot utilize RA-SDT or the nature of MT-SDT that a common RACH is used for MT-SDT.

[0049] According to one embodiment of the present disclosure, a solution for MT-SDT is provided. In this solution, an RRC entity notifies a MAC entity of first information associated with an MT-SDT procedure. Based on the first information, the MAC entity checks one or more conditions related to the initialization of the MT-SDT procedure. The MAC entity notifies the RRC entity of second information, which is associated with the result of the condition check. Based on the second information, the RRC entity can determine whether or not to start the MT-SDT procedure. In this way, the interaction between the RRC layer and the MAC layer is defined and supports MT-SDT.

[0050] The embodiments described herein will be explained in detail with reference to the accompanying drawings.

[0051] Referring to Figure 3, Figure 3 shows a signaling chart 300 for communication according to some embodiments of the present disclosure. As shown in Figure 3, the signaling chart 300 includes a terminal device 110 and a network device 120. For convenience of explanation, the signaling chart 300 will be described with reference to Figure 1.

[0052] In some embodiments, terminal device 110 may receive SDT settings from network device 120 (305). For example, SDT settings may include RACH settings, CG settings (e.g., via IEcg-SDT-config), settings for service radio bearers (SRBs) / data radio bearers (DRBs) used for SDT, and DRB lists. SDT settings may be received via any appropriate signaling, such as information elements (IEs) sdt-Config, IEsdt-ConfigCommon, and / or other RRCIEs or messages.

[0053] In some embodiments, terminal device 110 receives a paging message from network device 120. The paging message notifies terminal device 110 to start the MT-SDT procedure. That is, the paging message is used to trigger the MT-SDT procedure. For example, the paging message may be the message PagingRecord.

[0054] When the MT-SDT procedure is triggered, for example, in response to the receipt of a paging message, the RRC entity 130 of the terminal device 110 notifies the MAC entity 140 of the terminal device 110 of the first information associated with the MT-SDT procedure (310).

[0055] Based on the first information, MAC entity 140 checks one or more conditions (also called initiation conditions) related to the initiation of the MT-SDT procedure (315). In other words, the MAC entity determines whether one or more initiation conditions are met. The first information triggers the condition check in MAC entity 140.

[0056] The first information may include any appropriate notifications. In some embodiments, the first information may include general notifications that check one or more initiation conditions. For example, RRC entity 130 may notify MAC entity 140 to check whether the MT-SDT procedure can be started. In this case, MAC entity 140 may check different conditions or sets of conditions than those for MO-SDT. For example, the Data Volume Threshold (DVT) may not be checked.

[0057] Alternatively, the first information may notify the MAC entity 140 to check for a specific condition among one or more initiation conditions. In some embodiments, the first information notifies the MAC entity 140 to check for the conditions for initiating an SDT procedure via a CG-SDT procedure (also called a CG-SDT resource). For example, the RRC entity 130 may notify the MAC entity 140 to check only whether the conditions for initiating an SDT procedure via a CG-SDT resource are met if there is no UL SDT data available to send when the MT-SDT procedure is initiated.

[0058] Any appropriate conditions related to initiating the MT-SDT procedure are checked by MAC entity 140. In some embodiments, an RSRP threshold condition may be checked. For example, the RSRP threshold condition may include that the RSRP of the downlink path loss reference is greater than the SDT RSRP threshold (e.g., sdt-RSRP-Threshold). If the SDT RSRP threshold is not set, the RSRP threshold condition may be omitted. In some embodiments, if the RSRP threshold condition is omitted, the condition for initiating MT-SDT is always true, and MAC entity 140 checks only the resources being utilized.

[0059] Alternatively or additionally, in some embodiments, conditions for initiating an SDT procedure via a CG-SDT resource may be checked. For example, conditions for initiating an SDT procedure via a CG-SDT resource include, but are not limited to, that the serving cell is configured with an auxiliary uplink, that the CG-SDT is configured on a selected UL carrier and that the CG-SDT's TA is enabled, and that at least one SSB configured for the CG-SDT with an SS-RSRP exceeding the cg-SDT-RSRP-ThresholdSSB is available.

[0060] Alternatively, or additionally, in some embodiments, conditions for initiating an SDT procedure via resources for an RA-SDT procedure (also called an RA-SDT resource) may be checked. For example, conditions for initiating an SDT procedure may include, but are not limited to, that a set of RA resources for running RA-SDT on a selected UL carrier have been selected.

[0061] Alternatively, or additionally, in some embodiments, conditions for initiating the MT-SDT procedure may be checked. Alternatively, or additionally, in some embodiments, conditions for initiating the MO-SDT procedure may be checked.

[0062] By checking one or more initiation conditions, the terminal device 110 can determine whether or not it can start the MT-SDT procedure, and if it can start the MT-SDT procedure, which resources are available.

[0063] Continuing to refer to the signaling chart 300, based on the result of the condition check, MAC entity 140 notifies RRC entity 130 of second information (320). The second information is related to the result of the condition check.

[0064] In some embodiments, MAC entity 140 notifies RRC entity 130 that the conditions for initiating the MT-SDT procedure are met or that the MT-SDT procedure can be initiated; this is also called a general notification. Such a general notification may not include information about which resources are available. In some embodiments, MAC entity 140 may further notify RRC entity 130 of the resources available for the MT-SDT procedure; this is also called a specific notification. For example, MAC entity 140 may notify RRC entity 130 that the conditions for initiating the SDT procedure via CG-SDT resources are met. In some embodiments, MAC entity 140 may notify RRC entity 130 that some or all of the conditions for initiating the MT-SDT procedure are not met.

[0065] Subsequently, the RRC entity 130 decides whether or not to initiate the MT-SDT procedure based on the second information (325). In some embodiments, the MT-SDT procedure is initiated using, for example, a CG-SDT resource or a common RA resource. In other embodiments, the MT-SDT procedure is not initiated. Instead, a non-SDT restart procedure or an MO-SDT procedure may be initiated. Subsequently, a transmission to the network device 120 occurs (330). Alternatively, the terminal device 110 may not initiate any procedure to respond to paging messages from the network device 120.

[0066] In some embodiments, when MAC entity 140 notifies RRC entity 130 that the conditions for initiating the MT-SDT procedure are met or that it is possible to initiate the MT-SDT procedure, RRC entity 130 may simply initiate the MT-SDT procedure. RRC entity 130 notifies MAC entity 140 to initiate the MT-SDT procedure, and MAC entity 140 determines which resources to use based on the results of the condition check. For example, if the conditions for initiating the SDT procedure via the CG-SDT resource are met, MAC entity 140 decides to use the CG-SDT resource. As another example, if the conditions for initiating the SDT procedure via the CG-SDT resource are not met, but the RSRP threshold condition is met, MAC entity 140 decides to use the common RA resource.

[0067] In some embodiments, the RRC entity 130 determines the resources to be used for the MT-SDT procedure. For example, based on second information from the MAC entity 140, the RRC entity 130 initiates an MT-SDT procedure that utilizes CG-SDT resources. In other examples, based on second information from the MAC entity 140, the RRC entity 130 initiates an MT-SDT procedure that utilizes common RA resources. For example, the RRC entity 130 notifies the MAC entity 140 to initiate an RA procedure.

[0068] An example of the interaction process between MAC entity 140 and RRC entity 130 was described above. Further examples of condition checks and interactions are described below.

[0069] In some embodiments, the RSRP threshold conditions and / or the conditions for initiating an SDT procedure via a CG-SDT resource are checked by MAC entity 140. For example, if RRC entity 130 notifies MAC entity 140 to check whether an MT-SDT procedure can be initiated, MAC entity 140 will only check whether the RSRP threshold conditions and / or the conditions for initiating an SDT procedure via a CG-SDT resource are met.

[0070] In some embodiments, if the conditions for initiating an SDT procedure via a CG-SDT resource are met, the terminal device 110 may initiate an MT-SDT procedure that utilizes the CG-SDT resource. For example, if MAC entity 140 determines that the conditions for initiating an SDT procedure via a CG-SDT resource are met, MAC entity 140 may notify RRC entity 130 that the conditions for initiating an SDT procedure via a CG-SDT resource are met. Based on this notification, RRC entity 130 determines that it can initiate an MT-SDT procedure and utilize the CG-SDT resource. Alternatively, MAC entity 140 may simply notify RRC entity 130 that the conditions for initiating an MT-SDT procedure are met, or that it can initiate an MT-SDT procedure. Therefore, RRC entity 130 may simply initiate an MT-SDT procedure, and then MAC entity 140 may decide to utilize the CG-SDT resource for MT-SDT.

[0071] In some embodiments, if the conditions for starting an SDT procedure via the CG-SDT resource are not met, and the RSRP threshold condition is met, the terminal device 110 starts an MT-SDT procedure using the common RA resource. For example, if MAC entity 140 determines that the conditions for starting an SDT procedure via the CG-SDT resource are not met, and the RSRP threshold condition is met, MAC entity 140 may notify RRC entity 130 that at least one of the following is not met: the conditions for starting an SDT procedure via the CG-SDT resource are not met, the RSRP threshold condition is met, the conditions for starting an MT-SDT procedure are met, or the conditions for starting an SDT procedure are met. Based on this notification, RRC entity 130 may determine that it can start an MT-SDT procedure and utilize the common RA resource. Alternatively, MAC entity 140 may simply notify RRC entity 130 that the conditions for starting an MT-SDT procedure are met, or that it is possible to start an MT-SDT procedure. Therefore, RRC entity 130 may simply initiate the MT-SDT procedure, and then MAC entity 140 may decide to utilize common RA resources for MT-SDT.

[0072] In some embodiments, if the conditions for initiating an SDT procedure via a CG-SDT resource are not met and the RSRP threshold conditions are not met, the terminal device 110 may initiate a non-SDT-RRC restart procedure. For example, if MAC entity 140 determines that the conditions for initiating an SDT procedure via a CG-SDT resource are not met and the RSRP threshold conditions are not met, MAC entity 140 may notify RRC entity 130 that at least one of the conditions for initiating an MT-SDT procedure is not met, or the conditions for initiating an SDT procedure are not met. Based on this notification, RRC entity 130 may determine that it cannot initiate an MT-SDT procedure and instead initiate a non-SDT-RRC restart procedure.

[0073] In the embodiments described above, conditions for initiating the SDT procedure via CG-SDT resources and / or RSRP threshold conditions are checked. An example implementation of the technical specification (e.g., TS38.221) is shown below, but is not limited to this example. MAC entities are set up in SDT by RRC, and the SDT procedure is initiated by the RRC layer. The SDT procedure is executed by either a 2-step RA type or 4-step RA type (i.e., RA-SDT) random access procedure, or a set grant type 1 (i.e., CG-SDT). RRC sets the following parameters for the SDT procedure. sdt-DataVolumeThreshold: A data volume threshold used by the UE to determine whether or not to perform the SDT procedure. sdt-RSRP-Threshold: RSRP threshold for determining whether or not the UE will perform the SDT procedure. cg-SDT-RSRP-ThresholdSSB: The RSRP threshold set for SSB selection in CG-SDT. When an SDT procedure is initiated from a higher layer, the MAC entity performs the following actions: 1> If the amount of pending UL data across all RBs configured for SDT is less than or equal to sdt-DataVolumeThreshold, or if the SDT procedure is initiated for MT-SDT, and, Note: In the case of the SDT procedure, MAC entities also consider stopped RBs with SDT configured in their data volume calculations. The method for calculating the data volume of stopped RBs is left to the UE implementation. CCCH message sizes are excluded from data volume calculations. 1> If the RSRP referenced for downlink path loss is higher than sdt-RSRP-Threshold, or, 1>If sdt-RSRP-Threshold is not set, 2> If the serving cell is configured with an auxiliary uplink as defined in TS38.331[5], 2> If the RSRP based on downlink path loss is less than rsrp-ThresholdSSB-SUL, 3> Select the SUL carrier. 2>Otherwise, 3> Select NUL carrier. 2>If CG-SDT is configured on the selected UL carrier, and the TA of CG-SDT is enabled in accordance with Clause 5.27.2 and the first available CG opportunity using a CCCH message under Clause 5.8.2, and, 2> For each RB with data that can be transmitted, if configured, configureGrantType1Allowed is set to true for the corresponding logical channel, and, 2> If at least one SSB is configured for CG-SDT with SS-RSRP exceeding cg-SDT-RSRP-ThresholdSSB, 3>When the SDT procedure for MT-SDT is initiated by the upper layer, 4> Notify the higher layer that the conditions for initiating the CG-SDT procedure have been met. 3> In other cases, 4> Notify the upper layers that the conditions for initiating the SDT procedure have been met. Perform the CG-SDT procedure on the selected UL carrier in accordance with Section 3>5.8.2. 2> If the SDT procedure for MT-SDT is initiated by the upper layer, 3> Notify the upper layer that the conditions for initiating the CG-SDT procedure have not been met. Or (alternatively) Notify the upper layer that the conditions for initiating the SDT procedure have been met. Or (alternatively) Notify the upper layer that the RSRP for the downlink path loss criterion is greater than sdt-RSRP-Threshold. 2> Otherwise, if the SDT procedure for MT-SDT has not been initiated by the upper layer, 2>If a group of random access resources for RA-SDT execution is selected on the selected UL carrier in accordance with Section 5.1.1b, 3>If cg-SDT-TimeAlignmentTimer is running, it will be deemed that cg-SDT-TimeAlignmentTimer has expired, and the corrective measures specified in Clause 5.2 will be implemented. 3> Notify the higher layers that the conditions for initiating the SDT procedure have been met. 2>Otherwise, 3> Notify the higher layers that the conditions for initiating the SDT procedure have not been met. 1>Otherwise, 2> Notify the higher layers that the conditions for initiating the SDT procedure have not been met.

[0074] Another implementation example of the technical specification (e.g., TS38.331) regarding the conditions for initiating MT-SDT can be described as follows: A UE in the RRC_INACTIVE state will initiate the MT-SDT restart procedure if all of the following conditions are met. 1> The paging record includes a notification that MT-SDT has started, and, 1> SIB1 contains sdt-ConfigCommon, and, 1> sdt-Config is configured. 1> At startup, the lower layer notifies that the conditions for starting MT-SDT as defined in TS38.321[3] have been met.

[0075] Further implementation examples of the technical specifications regarding initiation (e.g., TS38.331) can be as follows: At the start of the procedure, the UE performs the following: 1>If sdt-MAC-PHY-CG-Config is configured, 2> If the restart procedure is initiated, the UE will be in a different cell from the PCell that received the saved sdt-MAC-PHY-CG-Config. 3> Release the saved sdt-MAC-PHY-CG-Config. 3> Notify the MAC entity to stop cg-SDT-TimeAlignmentTimer if it is currently running. 1> If the conditions for initiating an MO-SDT under section 5.3.13.1b of TS38.331 are met, or 1> If the conditions for initiating SDT for MT-SDT based on section 5.3.13.1c of TS38.331 are met, 2> The SDT restart procedure is considered to have started. 2> If the lower layer notifies that the conditions for initiating the CG-SDT procedure are not met, or (alternatively) if the lower layer notifies that the conditions for initiating the SDT procedure are met, or (alternatively) if the lower layer notifies that the RSRP based on downlink path loss is higher than sdt-RSRP-Threshold: 3> Notify the lower layers to initiate the random access procedure specified in TS38.321[3]. 2> Timer T319a is started when the lower layer first sends the CCCH message. 2> Assume the SDT procedure is in progress. 1>Otherwise, 2> Start timer T319. 2> Notify the MAC entity to stop cg-SDT-TimeAlignmentTimer if it is currently running. 1>If ta-Report is enabled and the UE supports TA reporting, 2> Notify lower-level tiers that the TA report has started. 1> Set the variable pendingRNA-Update to false. 1> If saved, release successHO-Config from the UE inactive AS context. 1> In accordance with section 5.3.13.3 of TS38.331, begin sending an RRCResumeRequest message or RRCResumeRequest1.

[0076] In addition to the conditions for initiating an SDT procedure via CG-SDT resources and / or RSRP threshold conditions, other conditions may be checked, or alternatively.

[0077] In some embodiments, conditions for initiating an SDT procedure via a CG-SDT resource, conditions for initiating an SDT procedure via an RA-SDT resource, and / or UL SDT data may be checked. For example, if RRC entity 130 notifies MAC entity 140 of the possibility of initiating an MT-SDT procedure, MAC entity 140 checks these conditions.

[0078] In some embodiments, if the conditions for initiating an SDT procedure via a CG-SDT resource are not met, but UL SDT data is available and the conditions for initiating an SDT procedure via an RA-SDT resource are met, the terminal device 110 initiates either an MO-SDT procedure or a non-SDT-RRC restart procedure. For example, if available UL SDT data is associated with a radio bearer configured in SDT, the MO-SDT procedure is initiated. Otherwise, the non-SDT-RRC restart procedure is initiated.

[0079] For example, RRC entity 130 may notify MAC entity 140 to check if MT-SDT can be started. Based on this notification, MAC entity 140 may check whether the conditions for starting the SDT procedure via the CG-SDT resource are met. If the conditions for starting the SDT procedure via the CG-SDT resource are not met, MAC entity 140 determines whether there is any UL SDT data that can be sent. If there is any UL SDT data that can be sent, MAC entity 140 checks whether the conditions for starting the SDT procedure via the RA-SDT resource are met. If the conditions for starting the SDT procedure via the RA-SDT resource are met, MAC entity 140 may notify RRC entity 130 that the conditions for starting the SDT procedure via the RA-SDT resource are met, or that the conditions for starting the MO-SDT procedure are met.

[0080] Based on this notification from MAC entity 140, RRC entity 130 may determine that it cannot initiate the MT-SDT procedure but can initiate the MO-SDT procedure. RRC entity 130 may initiate either the MO-SDT procedure or the non-SDT-RRC restart procedure.

[0081] In such embodiments, if UL SDT data is available, MO-SDT may be triggered instead of MT-SDT.

[0082] In some embodiments, specific conditions may be checked. For example, only the conditions for starting an SDT procedure via a CG-SDT resource may be checked. For example, if there is no UL SDT data that can be sent when starting an MT-SDT procedure, RRC entity 130 may notify MAC entity 140 to check whether only the conditions for starting an SDT procedure via a CG-SDT resource are met. If the conditions for starting an SDT procedure via a CG-SDT resource are met, terminal device 110 starts an MT-SDT procedure that utilizes the CG-SDT resource. For example, MAC entity 140 notifies RRC entity 130 that the conditions for starting an SDT procedure via a CG-SDT resource are met, or that the conditions for starting an MT-SDT procedure are met. Therefore, RRC entity 130 starts an MT-SDT procedure and the CG-SDT resource is used.

[0083] In some embodiments, if the conditions for initiating an SDT procedure via a CG-SDT resource are not met, the terminal device 110 initiates a non-SDT-RRC restart procedure. For example, MAC entity 140 notifies RRC entity 130 that the conditions for initiating an SDT procedure via a CG-SDT resource are not met, or that the conditions for initiating an MT-SDT procedure are not met. Therefore, RRC entity 130 may determine that it cannot initiate an MT-SDT procedure and instead initiate a non-SDT-RRC restart procedure.

[0084] Alternatively, in some embodiments, even if the RRC entity 130 notifies the MAC entity 140 to check a specific condition, the MAC entity 140 may also check one or more other conditions. Based on the results of the condition checks, the MAC entity 140 notifies the RRC entity 130 whether the specific condition is met, or whether one or more other conditions are met, or whether the conditions for initiating the MT-SDT procedure are met. Based on this notification from the MAC entity 140, the RRC entity 130 decides whether or not to initiate the MT-SDT procedure.

[0085] For example, RRC entity 130 may notify MAC entity 140 to check the conditions for initiating an SDT procedure via a CG-SDT resource. MAC entity 140 may also check other conditions, such as RSRP threshold conditions. Based on the results of the condition check, MAC entity 140 then notifies RRC entity 130 whether the conditions for initiating an SDT procedure via a CG-SDT resource are met, whether the RSRP threshold conditions are met, or whether the conditions for initiating an MT-SDT procedure are met.

[0086] The MT-SDT procedure can be successfully initiated through condition checks and the interaction between the RRC and MAC layers. Furthermore, it should be noted that the various condition combinations described above are presented as non-limiting examples.

[0087] Although Figure 3 shows only one RRC entity 130 and one MAC entity 140, the terminal device 110 may contain multiple RRC entities and / or MAC entities.

[0088] Figure 4 shows a flowchart of Method 400 as implemented in a terminal device according to some embodiments of the present disclosure. For convenience of explanation, Method 400 will be described in terms of the terminal device 110 in Figure 1.

[0089] In block 410, the RRC entity of the terminal device notifies the MAC entity of the terminal device of the first information associated with the MT-SDT procedure.

[0090] In block 420, the MAC entity determines, based on the first information, whether one or more conditions related to the initiation of the MT-SDT procedure are met.

[0091] In block 430, the MAC entity notifies the RRC entity of the second information based on its determination.

[0092] In block 440, the RRC entity decides whether or not to initiate the MT-SDT procedure based on the second piece of information.

[0093] In some embodiments, one or more conditions include at least one of the following: reference signal received power (RSRP threshold condition), conditions for initiating an MT-SDT procedure, conditions for initiating a Small Data Transmission via Resource for a Config Grant Small Data Transmission (SDT procedure), a CG-SDT procedure, conditions for initiating an SDT procedure via Resource for a Random Access Small Data Transmission, an RA-SDT procedure, or conditions for initiating a Mobile Outgoing Small Data Transmission (MO-SDT procedure).

[0094] In some embodiments, the terminal device can initiate an MT-SDT procedure that utilizes the resources for the CG-SDT procedure when the conditions for initiating an SDT procedure via the resources for the CG-SDT procedure are met.

[0095] In some embodiments, the second information indicates that the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure have been met.

[0096] In some embodiments, if the conditions for initiating an SDT procedure via resources for a CG-SDT procedure are not met, and the RSRP threshold condition is met, the terminal device may initiate an MT-SDT procedure using resources for a Common Random Access (RA) procedure.

[0097] In some embodiments, the second information indicates at least one of the following: that the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met; that the RSRP threshold conditions are met; that the conditions for initiating the MT-SDT procedure are met; or that the conditions for initiating the SDT procedure are met.

[0098] In some embodiments, the terminal device can initiate a non-SDT-RRC restart procedure if the conditions for initiating an SDT procedure via resources for the CG-SDT procedure are not met, and the RSRP threshold conditions are not met.

[0099] In some embodiments, the second information indicates that the conditions for initiating the MT-SDT procedure are not met, or at least one of the conditions for initiating the SDT procedure are not met.

[0100] In some embodiments, the terminal device initiates the MO-SDT procedure or the non-SDT-RRC restart procedure when the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met, uplink small data transmission data is available, and the conditions for initiating the SDT procedure via the resources for the RA-SDT procedure are met.

[0101] In some embodiments, the second information indicates that the conditions for initiating an SDT procedure via a resource for an RA-SDT procedure are met, or that the conditions for initiating an MO-SDT procedure are met, or at least one of these.

[0102] In some embodiments, the first information notifies that if no uplink SDT data is available for sending the MT-SDT procedure, only the conditions for initiating the SDT procedure via the CG-SDT procedure resources should be checked.

[0103] In some embodiments, an apparatus capable of performing any of the methods 400 (e.g., the terminal device 110 in Figure 1) may include means for performing each operation of the methods 400. These means can be implemented in any suitable form. For example, the means may be implemented as a circuit configuration or a software module. The apparatus is implemented as or as part of the terminal device 110 in Figure 1.

[0104] In some embodiments, the device includes means for a radio resource control (RRC) entity to notify a media access control (MAC) entity of the device of first information associated with a mobile incoming small data transmission (MT-SDT) procedure; means for the MAC entity to notify the RRC entity of second information based on a determination; and means for the RRC entity to determine whether or not to initiate the MT-SDT procedure based on the second information.

[0105] In some embodiments, one or more conditions include at least one of the following: a reference signal received power (RSRP) threshold condition, a condition for initiating an MT-SDT procedure, a condition for initiating a Small Data Transmit (SDT) procedure via resources for a Config-Grant Small Data Transmit (CG-SDT) procedure, a condition for initiating an SDT procedure via resources for a Random Access Small Data Transmit (RA-SDT) procedure, or a condition for initiating a Mobile Outgoing Small Data Transmit (MO-SDT) procedure.

[0106] In some embodiments, the apparatus includes means for initiating an MT-SDT procedure that utilizes resources for a CG-SDT procedure when the conditions for initiating an SDT procedure via resources for a CG-SDT procedure are met.

[0107] In some embodiments, the second piece of information indicates that the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure have been met.

[0108] In some embodiments, the apparatus includes means for initiating an MT-SDT procedure that utilizes resources for a Common Random Access (RA) procedure when the conditions for initiating an SDT procedure via resources for a CG-SDT procedure are not met and the RSRP threshold condition is met.

[0109] In some embodiments, the second information indicates at least one of the following: that the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met; that the RSRP threshold conditions are met; that the conditions for initiating the MT-SDT procedure are met; or that the conditions for initiating the SDT procedure are met.

[0110] In some embodiments, the apparatus includes means for initiating a non-SDT-RRC restart procedure if the conditions for initiating an SDT procedure via resources for a CG-SDT procedure are not met and the RSRP threshold conditions are not met.

[0111] In some embodiments, the second information indicates that the conditions for initiating the MT-SDT procedure are not met, or that the conditions for initiating the SDT procedure are not met, or at least one of these.

[0112] In some embodiments, the device includes means for initiating an MO-SDT procedure or a non-SDT-RRC restart procedure when the conditions for initiating an SDT procedure via resources for a CG-SDT procedure are not met, uplink small data transmission data is available, and the conditions for initiating an SDT procedure via resources for an RA-SDT procedure are met.

[0113] In some embodiments, the second information indicates that the conditions for initiating an SDT procedure via a resource for an RA-SDT procedure are met, or that the conditions for initiating an MO-SDT procedure are met, or at least one of these.

[0114] In some embodiments, the first information notifies that if uplink SDT data is unavailable for sending the MT-SDT procedure, only the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure should be checked.

[0115] In some embodiments, the apparatus further comprises means for performing other operations in some embodiments of Method 400 or Terminal Device 110. In some embodiments, the means comprises at least one processor and at least one memory which, when executed by the at least one processor, stores instructions that cause the apparatus to perform operations.

[0116] Figure 5 is a simplified block diagram of a device 500 suitable for implementing an embodiment of the present disclosure. The device 500 is provided for implementing, for example, a communication device such as the terminal device 110 or the network device 120 shown in Figure 1. As shown in the figure, the device 500 comprises one or more processors 510, one or more memories 520 connected to the processors 510, and one or more communication modules 540 connected to the processors 510.

[0117] The communication module 540 is for bidirectional communication. The communication module 540 has one or more communication interfaces to facilitate communication with other modules or devices. The communication interfaces can represent any interfaces necessary for communication with other network elements. In some embodiments, the communication module 540 may include at least one antenna.

[0118] The processor 510 is any type suitable for a local technology network and, in non-limiting examples, may include general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. The device 500 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock that synchronizes the main processor.

[0119] The memory 520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically rewritable read-only memory (EPROM), flash® memory, hard disks, compact discs (CDs), digital video discs (DVDs), optical discs, laser discs, and other magnetic and / or optical storage devices. Examples of volatile memories include random-access memory (RAM) 522 and other volatile memories that cannot retain data during power outages.

[0120] The computer program 530 includes computer-executable instructions that are executed by the associated processor 510. The instructions in program 530 may include instructions for performing actions / operations in some embodiments of this disclosure. Program 530 may be stored in memory, for example, ROM 524. The processor 510 can perform any appropriate actions and operations by loading program 530 into RAM 522.

[0121] Exemplary embodiments of the present disclosure may be implemented by program 530, thereby enabling the device 500 to perform any of the operations of the present disclosure described with reference to Figures 2A to 4. Exemplary embodiments of the present disclosure may also be implemented by hardware, or by a combination of software and hardware.

[0122] In some embodiments, the program 530 may be tangibly stored in a computer-readable medium built into the device 500 (e.g., in memory 520) or in another storage device accessible to the device 500. The device 500 can load the program 530 from the computer-readable medium into RAM 522 and execute it. In some embodiments, the computer-readable medium may include any type of non-temporary storage medium, such as ROM, EPROM, flash® memory, hard disk, CD, DVD, etc. The term “non-temporary” here refers to the medium itself (i.e., a tangible medium rather than a signal) and not to the persistence of data storage (e.g., RAM vs. ROM).

[0123] Figure 6 shows an example of a computer-readable medium 600 that can take the form of a CD, DVD, or other optical storage disc. The computer-readable medium 600 stores a program 530.

[0124] In general, various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some features may be implemented in hardware, while others may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Various aspects of the embodiments described herein are illustrated using block diagrams, flowcharts, or other graphic representations, but it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, other computing devices, or any combination thereof.

[0125] Some embodiments of this disclosure also provide at least one computer program product physically recorded on a computer-readable medium, such as a non-temporary computer-readable medium. This computer program product includes computer-executable instructions, such as those contained in a program module, and runs on a device on a target physical or virtual processor, performing one of the methods described above. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functionality of program modules may be combined or divided among program modules as needed in various embodiments. The machine-executable instructions for a program module may run on a local or distributed device. On a distributed device, the program module may reside on both local and remote storage media.

[0126] Program code for carrying out the methods of this disclosure is written in any combination of one or more programming languages. The program code is provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and is executed by the processor or controller to implement the functions / operations specified in the flowchart and / or block diagrams. The program code may run entirely on the machine, partially on the machine, run as a standalone software package, partially on the machine and partially on a remote machine, or run entirely on a remote machine or server.

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

[0128] Computer-readable media may be computer-readable signal media or computer-readable storage media. Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, and semiconductor systems, apparatus, devices, or appropriate combinations thereof. More specific examples of computer-readable storage media include electrical connections with one or more wires, portable computer floppy disks, 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), optical storage devices, magnetic storage devices, or appropriate combinations thereof.

[0129] Furthermore, while the operations are shown in a specific order, this does not mean that the operations must be performed in a specific or sequential order shown to obtain the desired results, or that all illustrated operations must be performed. In certain situations, multitasking or parallel processing may be advantageous. Similarly, the above description includes some specific implementation details, which should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Unless expressly stated, certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless expressly stated, various features described in the context of a single embodiment may also be implemented individually or in any suitable partial combination in multiple embodiments.

[0130] While this disclosure is written in a language specific to structural features and / or methodological actions, the content of this disclosure as defined in the attached claims is not necessarily limited to the specific functions and actions described above. Rather, the specific functions and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. It is a device, At least one processor, When executed by the at least one processor, the device has at least, The Radio Resource Control (RRC) entity of the device notifies the Media Access Control (MAC) entity of the device of first information associated with the Mobile Incoming Small Data Transmission (MT-SDT) procedure, The MAC entity determines, based on the first information, whether one or more conditions related to the initiation of the MT-SDT procedure are met, The MAC entity notifies the RRC entity of the second information based on the determination, The RRC entity decides whether or not to initiate the MT-SDT procedure based on the second information, At least one memory to store instructions to execute, A device equipped with the following features.

2. The one or more of the above conditions are, Reference signal received power (RSRP) threshold condition, Conditions for initiating the aforementioned MT-SDT procedure, Conditions for initiating a Small Data Sending (SDT) procedure via resources for the configured Grant Small Data Sending (CG-SDT) procedure, Conditions for initiating the SDT procedure via resources for Random Access Small Data Transmission (RA-SDT), or Conditions for initiating the Mobile Outgoing Small Data Transmission (MO-SDT) procedure, The apparatus according to claim 1, comprising at least one of the following.

3. The at least one memory, when executed by the at least one processor, provides the device with If the conditions for starting the SDT procedure via the resources for the CG-SDT procedure are met, the MT-SDT procedure using the resources for the CG-SDT procedure is started. The apparatus according to claim 2, which stores an instruction to execute.

4. The apparatus according to claim 3, wherein the second information indicates that the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure have been met.

5. The at least one memory, when executed by the at least one processor, provides the device with If the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met, and the RSRP threshold condition is met, then the MT-SDT procedure using the resources for the Common Random Access (RA) procedure is initiated. The apparatus according to claim 2, which stores an instruction to execute.

6. The second set of information includes, at a minimum, The conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met. The RSRP threshold conditions mentioned above are met. The conditions for initiating the MT-SDT procedure are met, or The conditions for initiating the SDT procedure are met. The apparatus according to claim 5, which notifies one of the following.

7. The at least one memory, when executed by the at least one processor, provides the device with If the conditions for initiating the SDT procedure via the resources of the CG-SDT procedure are not met, and the RSRP threshold conditions are not met, then the non-SDT-RRC restart procedure is initiated. The apparatus according to claim 2, which stores an instruction to execute.

8. The second set of information includes, at a minimum, The conditions for initiating the MT-SDT procedure are not met, or The conditions for initiating the aforementioned SDT procedure are not met. The apparatus according to claim 7, which notifies one of the following.

9. The at least one memory, when executed by the at least one processor, provides the device with If the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met, If uplink small data transmission data is available, and, If the conditions for initiating the SDT procedure via the resources for the RA-SDT procedure are met, The apparatus according to claim 2, wherein it stores an instruction to initiate the MO-SDT procedure or the non-SDT-RRC restart procedure.

10. The second set of information includes, at a minimum, The conditions for initiating the SDT procedure via the resources for the RA-SDT procedure are met, or The conditions for initiating the MO-SDT procedure are met. The apparatus according to claim 9, which notifies one of the following.

11. The apparatus according to claim 1, wherein the first information notifies the user to check only the conditions for initiating an SDT procedure via a resource for a CG-SDT procedure if no uplink SDT data is available for transmitting the MT-SDT procedure.

12. The Radio Resource Control (RRC) entity of the terminal device notifies the Media Access Control (MAC) entity of the terminal device of first information associated with the Mobile Incoming Small Data Transmission (MT-SDT) procedure, The MAC entity determines, based on the first information, whether one or more conditions related to the initiation of the MT-SDT procedure are met, The MAC entity notifies the RRC entity of the second information based on the determination, The RRC entity determines whether or not to initiate the MT-SDT procedure based on the second information, Methods that include...

13. The one or more of the above conditions are, Reference signal received power (RSRP) threshold condition, Conditions for initiating the aforementioned MT-SDT procedure, Conditions for initiating a Small Data Sending (SDT) procedure via resources for the configured Grant Small Data Sending (CG-SDT) procedure, Conditions for initiating the Random Access Small Data Transmission (RA-SDT) procedure via resources for the SDT procedure, or Conditions for initiating the Mobile Outgoing Small Data Transmission (MO-SDT) procedure, The method according to claim 12, comprising at least one of the following.

14. When the conditions for starting the SDT procedure via the resources for the CG-SDT procedure are met, the MT-SDT procedure using the resources for the CG-SDT procedure is started. The method according to claim 13, further comprising:

15. The method according to claim 14, wherein the second information indicates that the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure have been met.

16. The method according to claim 13, further comprising initiating the MT-SDT procedure using resources for a Common Random Access (RA) procedure when the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met and the RSRP threshold condition is met.

17. The second information mentioned above is, The conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met. The RSRP threshold conditions mentioned above are met. The conditions for initiating the MT-SDT procedure are met, or The conditions for initiating the SDT procedure are met. The method according to claim 16, which provides notification of at least one of the following.

18. If the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met, and the RSRP threshold conditions are not met, then the non-SDT-RRC restart procedure is initiated. The method according to claim 13, further comprising:

19. The second set of information includes, at a minimum, The conditions for initiating the MT-SDT procedure are not met, or The conditions for initiating the aforementioned SDT procedure are not met. The method according to claim 18, wherein one of the following is notified.

20. If the conditions for initiating the SDT procedure via the resources for the CG-SDT procedure are not met, Uplink small data transmission data is available, and The conditions for initiating the SDT procedure via the resources for the RA-SDT procedure are met. In that case, the MO-SDT procedure or the non-SDT RRC restart procedure is initiated. The method according to claim 13, further comprising:

21. The second set of information includes, at a minimum, The conditions for initiating the SDT procedure via the resources for the RA-SDT procedure are met, or The conditions for initiating the MO-SDT procedure are met. The method according to claim 20, wherein one of the following is notified.

22. The method according to claim 12, wherein the first information notifies that if no uplink SDT data is available for transmission of the MT-SDT procedure, only the conditions for initiating an SDT procedure via resources for a CG-SDT procedure should be checked.

23. It is a device, The Radio Resource Control (RRC) entity of the device provides means for notifying the Media Access Control (MAC) entity of the device of first information associated with a Mobile Incoming Small Data Transmission (MT-SDT) procedure, The MAC entity includes means for determining, based on the first information, whether one or more conditions related to the initiation of the MT-SDT procedure are met, The MAC entity provides means for notifying the RRC entity of the second information based on the determination, The RRC entity has means for determining whether or not to initiate the MT-SDT procedure based on the second information, A device equipped with the following features.

24. A computer-readable medium containing instructions stored in the device for causing it to perform at least one of the methods described in claims 12 to 22.

Images