Small-scale data transmission control

Abstract

An exemplary embodiment of the present disclosure relates to small data transmission control. A method comprising: a terminal device receiving small data transmission, SDT, configuration information from a network node; the terminal device determining, based on the SDT configuration information, whether the terminal device is permitted to use a mobile incoming, MT, SDT procedure and / or a mobile outgoing, MO, SDT procedure; and the terminal device initiating or applying at least one of the MT SDT procedure or MO SDT procedure based on the determination and / or the SDT configuration information.

Description

Technical Field

[0004] ,

[0001] Various exemplary embodiments of the present disclosure generally relate to the field of telecommunication, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for small data transmission control.

Background Art

[0002] In some communication systems, a terminal device can transition between an inactive state, an idle state, and a connected state. In the inactive state or the idle state, the terminal device may not establish a connection with a network node for communication. In order to avoid unnecessary signaling overhead and power consumption for establishing or re-establishing a connection, it is agreed that small data transmission (SDT) can be supported for terminal devices in the inactive state without the need for the terminal device to establish a connection with a network node.

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, which, when executed by the at least one processor, cause the apparatus to at least receive small data transmission, SDT, configuration information from a network node, determine whether the use of a mobile terminated, MT, SDT procedure and / or a mobile originated, MO, SDT procedure is permitted for the apparatus based on the SDT configuration information, and start or apply at least one of the MT SDT procedure or the MO SDT procedure based on the determination and / or the SDT configuration information.

[0004] A second aspect of the present disclosure provides an apparatus comprising at least one processor and at least one memory for storing instructions, the instructions, when executed by at least one processor, cause the apparatus to perform at least: transmit small data transmission, SDT, configuration information to a terminal device, the SDT configuration information being used by the terminal device to determine whether the use of mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures is permitted to the terminal device; and perform or apply at least one of the MT SDT procedure or MO SDT procedure with the terminal device based on the SDT configuration information.

[0005] A third aspect of this disclosure provides a method, which includes: a terminal device receiving small data transmission, SDT, configuration information from a network node; the terminal device determining, based on the SDT configuration information, whether the terminal device is permitted to use a mobile incoming, MT, SDT procedure and / or a mobile outgoing, MO, SDT procedure; and the terminal device initiating or applying at least one of the MT SDT procedure or MO SDT procedure based on the determination and / or the SDT configuration information.

[0006] A fourth aspect of this disclosure provides a method, which includes a network node transmitting Small Data Transmission, SDT, configuration information to a terminal device, the SDT configuration information being used by the terminal device to determine whether the terminal device is permitted to use a mobile incoming, MT, SDT procedure and / or mobile outgoing, MO, SDT procedure; and the network node performing or applying at least one of an MT SDT procedure or an MO SDT procedure to the terminal device based on the SDT configuration information.

[0007] A fifth aspect of this disclosure provides a device. This device includes means for receiving small data transmission, SDT, and configuration information from a network node; means for determining, based on the SDT configuration information, whether the device is permitted to use mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures; and means for initiating or applying at least one of the MT SDT procedures or MO SDT procedures based on the determination and / or the SDT configuration information.

[0008] A sixth aspect of this disclosure provides an apparatus. The apparatus comprises means for transmitting small data transmission, SDT, configuration information to a terminal device, the SDT configuration information being used by the terminal device to determine whether the terminal device is permitted to use mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures; and means for performing or applying at least one of MT SDT procedures or MO SDT procedures to and from the terminal device based on the SDT configuration information.

[0009] A seventh aspect of this disclosure provides a computer-readable medium which stores instructions for causing a device to perform at least the method according to the third aspect.

[0010] In an eighth aspect of this disclosure, a computer-readable medium is provided which stores instructions for causing a device to perform at least the method according to the fourth aspect.

[0011] It should be understood that the Summary of the Invention section is not intended to identify the main or important features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will be readily apparent through the following description.

[0012] Several exemplary embodiments will be described below with reference to the attached drawings. [Brief explanation of the drawing]

[0013] [Figure 1] This figure shows an exemplary communication environment in which exemplary embodiments of the present disclosure can be implemented. [Figure 2] This is a signaling chart for communications according to some exemplary embodiments of the present disclosure. [Figure 3] This is a flowchart of a method implemented on a terminal device according to some exemplary embodiments of the present disclosure. [Figure 4] This is a flowchart of a method implemented on a network node according to some exemplary embodiments of the present disclosure. [Figure 5] This is a simplified block diagram of a device suitable for carrying out exemplary embodiments of the present disclosure. [Figure 6] This is a block diagram of an exemplary computer-readable medium according to some exemplary embodiments of the present disclosure. [Modes for carrying out the invention]

[0014] Throughout the drawing, identical or similar reference numbers represent identical or similar elements.

[0015] The principles of this disclosure will be explained below with reference to several exemplary embodiments. These embodiments are described for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing this disclosure, without implying any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

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

[0017] References in this disclosure such as “one embodiment,” “one example embodiment,” or “one exemplary embodiment” indicate that the described embodiments may include certain features, structures, or characteristics, but not all embodiments are required to include such features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, if certain features, structures, or characteristics are described in relation to one embodiment, it is considered within the knowledge of those skilled in the art that such features, structures, or characteristics may be affected in relation to other embodiments, whether explicitly described or not.

[0018] In this specification, terms such as “first,” “second,” etc., may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, the first element may be called the second element, and similarly, the second element may be called the first element. As used herein, the term “and / or” includes any combination of one or more of the listed terms.

[0019] As used herein, “at least one of the following: <list of two or more elements>” and “at least one of the <list of two or more elements>,” as well as similar wording in which lists of two or more elements are joined by “and” or “or,” mean at least one of those elements, or at least two or more of those elements, or at least all of those elements.

[0020] As used herein, unless expressly stated otherwise, performing a step "in response to A" does not mean that the step is performed immediately after the occurrence of "A", and may include one or more intervening steps.

[0021] The terms used in this specification are for the purpose of describing particular embodiments only and are not intended to limit the exemplary embodiments. As used in this specification, the singular forms "a", "an", and "the" are to be construed to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "has", "having", "includes", and / or "including", when used in this specification, specify the presence of the stated features, elements, and / or components, etc., and do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0022] As used in this application, the term "circuit" can refer to one or more or all of the following. (a) Circuit implementation with only hardware (e.g., implementation with only analog and / or digital circuits) (b) Combination of a hardware circuit and software. For example, (where applicable): (i) Combination of analog and / or digital hardware circuits and software / firmware (ii) Any part of a hardware processor (including a digital signal processor), software, and memory that operate in cooperation to perform various functions in a device such as a mobile phone or a server (c) A hardware circuit and / or processor, such as a microprocessor or a part of a microprocessor, that requires software (e.g., firmware) for operation, but the software may not exist if not necessary for operation

[0023] The definition of this circuit applies to all uses of this term in this application, including any claims. As a further example, when used in this application, the term "circuit" covers implementations of only hardware circuits or processors (or a plurality of processors), or implementations of a part of a hardware circuit or processor and the software and / or firmware associated therewith (or therewith). The term "circuit" covers, for example, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit within a server, a cellular network device, or other computing or network device, if it corresponds to a particular claim element.

[0024] As used herein, the term "communication network" refers to a network compliant with any suitable communication standard, such as, for example, New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), and the like. Further, communication between terminal devices and network devices within a communication network may be carried out according to any suitable generation of communication protocol, including but not limited to 1st generation (1G), 2nd generation (2G), 2.5G, 2.75G, 3rd generation (3G), 4th generation (4G), 4.5G, 5th generation (5G) communication protocols, and / or any other communication protocols known currently or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Considering the rapid development of communication, it is natural that there will also be future types of communication technologies and systems in which the present disclosure can be implemented. This should not be regarded as limiting the scope of the present disclosure to only the aforementioned systems.

[0025] As used herein, the terms “network device” or “network node” refer to a node in a communications network from which a terminal device accesses and receives services. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or access point (AP), such as a node B (NodeB or NB), an evolved node B (eNodeB or eNB), an NR NB (also called a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node, such as a femto or pico node, a non-terrestrial network (NTN) or non-ground network device, such as a satellite network device, a low-earth orbit (LEO) satellite, a geosynchronous earth orbit (GEO) satellite, or an aircraft network device. In some exemplary embodiments, the radio access network (RAN) partitioning architecture consists of a centralized unit (CU) and a distributed unit (DU) in the IAB donor node. The IAB node consists of a mobile terminal (IAB-MT) portion that behaves like a UE to the parent node and a DU portion of the IAB node that behaves like a base station to the next hop's IAB node.

[0026] The term "terminal device" refers to any end device that may be capable of wireless communication. For example, rather than being limited, terminal devices may also be called communication devices, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), Internet of Things (IoT) devices, watches or 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 the context of industrial and / or automated processing chains), consumer electronic devices, and devices operating on commercial and / or industrial wireless networks. Terminal devices may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms “terminal device,” “communication device,” “terminal,” “user equipment,” and “UE” may be used interchangeably.

[0027] As used herein, the terms “resource,” “transmit resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing communication, such as communication between a terminal device and a network device, for example, a time-domain resource, a frequency-domain resource, a spatial-domain resource, a code-domain resource, or any other resource that enables communication. Hereinafter, unless expressly stated otherwise, both frequency-domain and time-domain resources are used as examples of transmit resources to illustrate some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0028] Figure 1 shows an exemplary communication environment 100 in which exemplary embodiments of the present disclosure can be implemented. In the communication environment 100, multiple communication devices, including terminal devices 110 and network nodes 120, can communicate with each other. Network nodes 120 are shown as network nodes that provide services to terminal devices 110. The service area of ​​network nodes 120 may be called a cell.

[0029] In the following, for illustrative purposes, several exemplary embodiments are described in which one device operates as a terminal device 110 and another device operates as a network node 120. However, in some exemplary embodiments, the operations described with respect to the terminal device may be performed by the network node or other devices, and vice versa.

[0030] In some exemplary embodiments, the link from network node 120 to terminal device 110 is called a downlink (DL), and the link from terminal device 110 to network node 120 is called an uplink (UL). In a DL, network node 120 is a transmit (TX) device (or transmitter), and terminal device 110 is a receive (RX) device (or receiver). In a UL, terminal device 110 is a TX device (or transmitter), and network node 120 is an RX device (or receiver).

[0031] Communication in communication environment 100 may be carried out in accordance with any suitable communication protocol, including but 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 IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication may utilize any suitable wireless communication technology, including but not limited to code division multiplexing access (CDMA), frequency division multiplexing access (FDMA), time division multiplexing 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 / or any other technologies currently known or to be developed in the future.

[0032] It should be understood that the number of devices and their connections shown in Figure 1 are for illustrative purposes only and do not imply any limitation. The communication environment 100 may include any appropriate number of devices configured to carry out the exemplary embodiments of this disclosure. It should be understood that one or more additional devices, not shown, may be present in the communication environment 100.

[0033] In communication environment 100, a communication device (e.g., a terminal device) can transition between an inactive state, an idle state, and a connected state. The inactive state may also be called an inactive mode, an RRC_INACTIVE state / mode, or an inactive state in an RRC_CONNECTED state / mode, and such terms are used interchangeably herein. The idle state may also be called an idle mode, an RRC_IDLE state / mode, and such terms are used interchangeably herein. The connected state may also be called a connected mode, an active state / mode, or an RRC_CONNECTED state / mode, and such terms are used interchangeably herein.

[0034] In the RRC inactive or idle state, the terminal device has not established a connection with the network node for sending and / or receiving data. In the connected state, a connection has been established between the terminal device and the network node, so the terminal device can perform normal data communication with the network node through this connection.

[0035] To conserve power and reduce signaling overhead, it has been proposed to support Small Data Transmissions (SDTs) for terminal devices in a non-RRC connected state. It is currently agreed that terminal devices in an RRC inactive state can perform SDTs without transitioning to a connected state. SDTs may also be supported for terminal devices in an RRC idle state. As used herein, the term "SDT" refers to a type of transmission triggered by a small amount of data, although other terms may be used. In some exemplary embodiments, an SDT procedure may be initiated through a random access (RA) procedure and / or a configured grant (CG).

[0036] SDT procedures may include mobile outbound (MO) SDT procedures to enable small packet transmission of packets in the UL direction. In the case of MO SDT procedures, a terminal device may initiate the SDT procedure when uplink data becomes available for transmission. Initiating the SDT procedure may be performed based on a specific SDT configuration.

[0037] Furthermore, it has been proposed to support a Mobile Incoming (MT) SDT procedure to enable small data transmissions for DL ​​triggers. MT SDT can achieve similar advantages, such as reduced signaling overhead and power consumption because the terminal device does not need to transition to an RRC connected state, and reduced latency by enabling high-speed transmission of small, infrequent packets for purposes such as positioning. In some exemplary embodiments, the MT SDT procedure may be initiated when the terminal device is paged by a network node, or when the terminal device is paged to explicitly initiate an SDT procedure. For example, MT SDT may be initiated when a terminal device in an RRC inactive state is paged using an Inactive-Radio Network Temporary Identity (I-RNTI).

[0038] In some exemplary embodiments, in the case of MO SDT, a terminal device may indicate the start of the SDT procedure by a dedicated RACH resource configured by the network node. If such a RACH resource is not configured (for example, if the SDT procedure is configured to use a common RACH resource), the network node may infer the need for SDT from the Buffer Status Report (BSR) indicated by the terminal device in message 3 (Msg3) of the RA procedure (if there is sufficient space in this message after a Common Control Channel (CCCH) Service Data Unit (SDU) and / or RRC restart request has been included), or after successful conflict resolution. On the other hand, this solution also affects conventional terminal devices or other terminal devices that do not perform the SDT procedure, because the network still needs to allocate resources to them, even though these terminal devices cannot send data until a connection is established.

[0039] In some cases, a network node may want to use only MT SDT, which is entirely under the network node's control when specific DL data becomes available, and control whether or not SDT is required. However, currently, if SDT is enabled within the network node's cell, terminal devices are permitted to initiate the MO SDT procedure when the relevant conditions are met.

[0040] According to some exemplary embodiments of this disclosure, a solution for controlling SDT procedures is provided. In this solution, a network node can control the transmission of SDT configuration information and / or such SDT configuration information from the network node to a terminal device to determine whether to allow the terminal device to use an MT SDT procedure and / or an MO SDT procedure. Based on the SDT configuration information, the terminal device determines whether to allow an MT SDT procedure and / or an MO SDT procedure, and based on the determination and / or the SDT configuration information, initiates or applies at least one of the MT SDT procedure or MO SDT procedure with the network node. This solution allows the network node to control which SDT procedures a terminal device can initiate and the configuration information used for the initiated SDT procedures. This increases the flexibility of control by the network node over terminal devices in a cell.

[0041] Exemplary embodiments of this disclosure will be described in detail below with reference to the attached drawings.

[0042] Referring now to Figure 2, a signaling chart 200 of communications according to some exemplary embodiments of the present disclosure is shown. For convenience of explanation, the signaling chart 200 will be described with reference to Figure 1. As shown in Figure 2, the signaling chart 200 involves terminal devices 110 and network nodes 120.

[0043] In the signaling chart 200, the network node 120 transmits SDT configuration information to the terminal device 110 (205). The terminal device 110 receives small data transmission, SDT, and configuration information from the network node 110 (210). Based on the received SDT configuration information, the terminal device 110 determines whether or not it is permitted to use the MT SDT procedure and / or the MO SDT procedure (215). In some exemplary embodiments, the network node 120 may control whether and / or how it permits the terminal device 110 to use the MT SDT procedure and / or the MO SDT procedure by controlling certain information contained in the SDT configuration information and / or the transmission of the SDT configuration information. The terminal device 110 may be able to determine whether or not to permit the MT SDT procedure and / or the MO SDT procedure based on at least the received SDT configuration information.

[0044] SDT procedures can include MT SDT procedures and MO SDT procedures. An MT SDT procedure refers to an SDT procedure triggered by a network node for data transmission in DL. An MO SDT procedure refers to an SDT procedure triggered by a terminal device for data transmission in UL.

[0045] In some exemplary embodiments, the MT SDT procedure also refers to the MO SDT procedure, which is triggered by a network node for data transmission in DL. In this case, paging for SDT triggers a terminal device to perform the MO SDT procedure, during which DL data can be transmitted.

[0046] SDT may be permitted for terminal devices in a non-RRC connected state. In some exemplary embodiments, terminal device 110 may initiate SDT with network node 120 when RRC is inactive. In some exemplary embodiments, terminal device 110 may initiate SDT with network node 120 when RRC is idle. In exemplary embodiments of this disclosure, terminal device 110 initiates or applies at least one of the MT SDT procedure or MO SDT procedure based on a determination of whether the MT SDT procedure and / or MO SDT procedure are permitted and / or based on received SDT configuration information (220). Network node 120 performs or applies at least one of the MT SDT procedure or MO SDT procedure with terminal device 110 based on the SDT configuration information (225).

[0047] In some exemplary embodiments, if the MO SDT procedure is not permitted, the terminal device 110 may be permitted to use the received SDT configuration information only for the MT SDT procedure. In this case, the terminal device 110 may apply the SDT configuration information only for the MT SDT procedure. The terminal device 110 may initiate or apply only the MT SDT procedure with the network node 120 based on the SDT configuration information.

[0048] In some exemplary embodiments, the network node 120 may signal whether the MO SDT procedure is permitted via dedicated signaling and / or broadcast signaling when SDT configuration information is set on the terminal device 110.

[0049] In some exemplary embodiments, the SDT configuration information may indicate whether the terminal device 110 is permitted to use the MT SDT procedure and / or the MO SDT procedure. Thus, the terminal device 110 can determine from the SDT configuration information whether the MT SDT procedure and / or the MO SDT procedure are permitted. In some exemplary embodiments, the SDT configuration information explicitly indicates whether the terminal device 110 is permitted to use the MT SDT procedure and / or the MO SDT procedure.

[0050] In some exemplary embodiments, the SDT configuration information from the network node 120 to the terminal device 110 may include at least one of the MO SDT configuration for the MO SDT procedure or the MT SDT configuration for the MT SDT procedure. That is, the MT SDT configuration may be defined as a configuration separate from the MO SDT configuration. If both the MT SDT configuration and the MO SDT configuration are transmitted from the network node 120, the MO SDT configuration may be separate from or different from the MT SDT configuration.

[0051] In some cases, if the network node 120 decides to configure the MT SDT setting on the terminal device 110 but not the MO SDT setting, the terminal device 110 may determine that the MT SDT procedure is permitted but the MO SDT procedure is not. In those cases, the terminal device 110 may initiate or apply only the MT SDT procedure for data communication between the terminal device 110 and the network node 120. The initiation or application of the MT SDT procedure may be based on SDT configuration information (for example, the MT SDT setting included in the SDT configuration information).

[0052] In some cases, if the network node 120 decides to configure MO SDT settings on the terminal device 110 but not MT SDT settings, the terminal device 110 may determine that MO SDT procedures are permitted but MT SDT procedures are not. In those cases, the terminal device 110 may initiate or apply only MO SDT procedures for data communication between the terminal device 110 and the network node 120. The initiation or application of MO SDT procedures may be based on SDT configuration information (for example, MO SDT settings included in the SDT configuration information).

[0053] Furthermore, if the network node 120 decides to configure both MT SDT and MO SDT settings on the terminal device 110, the terminal device 110 may determine that both MT SDT and MO SDT procedures are permitted. Based on the SDT configuration information (for example, the MT SDT settings and / or MO SDT settings in the SDT configuration information), the terminal device 110 may initiate or apply the MT SDT procedure and / or MO SDT procedure for data communication as needed.

[0054] In some exemplary embodiments, the SDT procedure settings (e.g., MO SDT settings for an MO SDT procedure or MT SDT settings for an MT SDT procedure) represent one or more configuration parameters related to the corresponding SDT procedure. In some exemplary embodiments, the MT SDT settings for an MT SDT procedure may represent resource settings specific to the MT SDT procedure. Resource settings may represent one or more resources used by the MT SDT procedure, e.g., RACH resources and / or CG. The RACH resources for an MT SDT procedure may include conventional SDT RACH resources, MT SDT RACH resources, and / or common RACH resources.

[0055] In some exemplary embodiments, the MO SDT setting for an MO SDT procedure may indicate resource settings specific to the MO SDT procedure. The resource settings may indicate one or more resources used in the MO SDT procedure, such as RACH resources and / or CG. The RACH resources for an MO SDT procedure may include conventional SDT RACH resources, MO SDT RACH resources, and / or common RACH resources. Alternatively or additionally, either the MT SDT setting or the MO SDT setting may indicate one or more relevant conditions for triggering the corresponding SDT procedure.

[0056] In the case of MO SDT, a terminal device may determine whether it can trigger the MO SDT procedure based on whether relevant conditions are met. In some examples, satisfaction of relevant conditions may be based on one or more of the following: UL data volume threshold, radio state, data belonging to a radio bearer configured for SDT, or timer values ​​(e.g., t319a timer value). The radio state may be measured based on the reference signal received power (RSRP) of the communication link between the terminal device 110 and the network node 120. The radio state may indicate that the SDT procedure can be initiated if the RSRP is the RSRP threshold set in the SDT configuration information. The RSRP threshold is used to evaluate whether the terminal device can initiate the RRC restart procedure even if the network node 120 indicates in a paging message that DL data is available. This is to ensure that the transmission of DL data is successful even if the channel state of the terminal device is worse than the state allowed by the RSRP threshold.

[0057] In the case of MO SDT, terminal device 110 may initiate the MO SDT procedure if the amount of UL data that can be transmitted exceeds the UL data volume threshold. For example, this may occur if the amount of pending UL data across all resource bearers (RBs) configured for SDT is less than or equal to the UL data volume threshold. In some cases, with respect to the SDT procedure, terminal device 110 may also consider suspended RBs on which SDT is configured for data volume calculation. Alternatively, in addition, terminal device 110 may initiate the MO SDT procedure if the RSRP of a reference signal (e.g., a DL path loss reference signal) is higher than the RSRP threshold.

[0058] It can be determined whether the MT SDT configuration is the same as or different from the MO SDT configuration. The definition of whether the resources and / or the relevant conditions for triggering the MT SDT and MO SDT procedures are the same or different may depend on network node 120.

[0059] In some examples, for MT SDT, even if network node 120 indicates in a paging message that DL SDT is available, the relevant RSRP threshold may be used to determine whether terminal device 110 can initiate the normal restart procedure. This is to ensure that DL data transmission is successful if the channel state of terminal device 110 is worse than the state allowed by the RSRP threshold.

[0060] On the other hand, in the case of MT-SDT, the terminal device 110 may or may not have UL SDT data to transmit. In this case, it is pointless to use SDT-specific RACH resources (if configured) when the terminal device 110 does not have SDT UL data to transmit, because the network node 120 is likely to allocate a larger amount of resources for transmission (e.g., Msg3 transmission) to accommodate at least a portion of the UL SDT data. In this case, it may be beneficial to allow the terminal device 110 with MT SDT access configured to initiate the SDT restart procedure with the network node using normal RACH resources, thereby avoiding the resource being wasted when there is no available UL SDT data. According to some embodiments of the present invention, resource utilization can be further improved by allowing the network node to configure resources for MT SDT procedures and MO SDT procedures separately.

[0061] In some exemplary embodiments, the SDT configuration information may include SDT configurations used as MO SDT configurations and MT SDT configurations, respectively. That is, the MT SDT configuration and the MO SDT configuration may be represented as the same SDT configuration. This SDT configuration may represent one or more configuration parameters related to the SDT procedure.

[0062] In some exemplary embodiments, if the same SDT configuration is included in the SDT configuration information, the network node 120 may explicitly indicate whether the SDT configuration can be used for the MT SDT procedure, the MO SDT procedure, or both. By receiving instructions from the network node 120 indicating whether the SDT configuration is used for the MT SDT procedure and / or the MO SDT procedure, the terminal device 110 may be able to determine, based on the received SDT configuration information, which of the MT SDT procedure and / or the MO SDT procedure the terminal device 110 is permitted to use.

[0063] In some exemplary embodiments, if the same SDT setting is included in the SDT configuration information, the terminal device 110 may be allowed by default to use the SDT setting for both the MT SDT procedure and the MO SDT procedure. Thus, the terminal device 110, which is in an RRC inactive or RRC idle state, may initiate or apply the MT SDT procedure and the MO SDT procedure, respectively, based on the SDT setting.

[0064] In some exemplary embodiments, network node 120 may transmit SDT configuration information via dedicated signaling. In some exemplary embodiments, dedicated signaling may be, for example, an RRC release message, but other signaling may also be applicable. In some exemplary embodiments, network node 120 may set the SDT start timer value (e.g., t319a timer value) and / or RSRP threshold used for MO SDT in cells that do not provide SDT configuration via system information (SI) to terminal device 110 via dedicated signaling. In some exemplary embodiments, alternatively or additionally, network node 120 may transmit SDT configuration information via common signaling.

[0065] In some exemplary embodiments, if network node 120 transmits SDT configuration information to terminal device 110 via dedicated signaling or a specific common signaling, terminal device 110 may determine, based on such receipt of SDT configuration information, that only MT SDT procedures are permitted. In some exemplary embodiments, if network node 120 transmits SDT configuration information to terminal device 110 via dedicated signaling, terminal device 110 may use the dedicatedly configured information regardless of SDT configurations being broadcast within the cell. For example, terminal device 110 may initiate or apply only MT SDT procedures based on the SDT configuration information, regardless of other SDT configuration information received via broadcast signaling.

[0066] In some exemplary embodiments, the SDT configuration information may include a specific UL data volume threshold for initiating or triggering an MO SDT procedure. In some exemplary embodiments, network node 120 may transmit this special UL data volume threshold to determine that an MO SDT procedure is not permitted. In some exemplary embodiments, network node 120 may transmit this special UL data volume threshold to determine that an MO SDT procedure is permitted. For example, a UL data volume threshold that can actually be used to initiate or trigger an MO SDT procedure may represent one or more non-zero bytes. The non-zero bytes of the UL data volume threshold may be one or more of, for example, 32 bytes, 100 bytes, 200 bytes, 400 bytes, 600 bytes, 800 bytes, 1000 bytes, 2000 bytes, 4000 bytes, 8000 bytes, 9000 bytes, 10000 bytes, 12000 bytes, 24000 bytes, 48000 bytes, or 96000 bytes. A new value, "zero bytes," may be introduced as a specific UL data volume threshold to indicate that the SDT configuration information is intended only for the MT SDT procedure and is not permitted for the MO SDT procedure. Currently, when SDT is configured on terminal device 110, the UL data volume threshold is required to be set to a minimum value of 32 bytes. Introducing the new value would allow the use of existing fields (e.g., sdt-DataVolumeThreshold) to indicate permission for both the MT SDT procedure and / or the MO SDT procedure.

[0067] In some exemplary embodiments, the SDT procedure may be triggered when the terminal device 110 becomes capable of transmitting UL data. Alternatively, the SDT procedure may be triggered when the network node 120 pages the terminal device 110. Alternatively, the SDT procedure may be triggered when the network node 120 pages the terminal device 110 to initiate the SDT procedure.

[0068] In some exemplary embodiments, to initiate an SDT procedure, the terminal device 110 may determine whether to initiate an RRC restart procedure or an MO SDT procedure when UL data can be transmitted. The terminal device 110 may further determine which resources (e.g., RACH resources) to use to initiate the SDT procedure. Based on the decision, the terminal device 110 may initiate the RRC restart procedure or the MO SDT procedure using the determined resources.

[0069] In some exemplary embodiments, terminal device 110 may initiate a non-SDT RRC restart procedure if the MO SDT procedure and / or MT SDT procedure are not permitted.

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

[0071] In block 310, the terminal device 110 receives SDT configuration information from the network node 120.

[0072] In block 320, the terminal device 110 determines, based on the SDT configuration information, whether or not the terminal device 110 is permitted to use the MT SDT procedure and / or the MO SDT procedure.

[0073] In block 330, the terminal device 110 initiates or applies at least one of the MT SDT procedure or the MO SDT procedure based on the determination and SDT configuration information. In some exemplary embodiments, the terminal device 110 is in the Radio Resource Control, RRC, Inactive state. In some exemplary embodiments, the terminal device 110 is in the Radio Resource Control, RRC, Idle state.

[0074] In some exemplary embodiments, the SDT configuration information indicates whether the terminal device 110 is permitted to use the MT SDT procedure and / or the MO SDT procedure.

[0075] In some exemplary embodiments, if the MO SDT procedure is not permitted, the terminal device 110 may apply the SDT configuration information only to the MT SDT procedure.

[0076] In some exemplary embodiments, the SDT configuration information includes at least one of the MO SDT configuration for an MO SDT procedure or the MT SDT configuration for an MT SDT procedure.

[0077] In some exemplary embodiments, the MO SDT setting is separate from or different from the MT SDT setting.

[0078] In some exemplary embodiments, if the terminal device 110 is configured with MT SDT settings but not with MO SDT settings, the terminal device 110 may initiate or apply only MT SDT procedures for data communication between the terminal device 110 and the network node 120.

[0079] In some exemplary embodiments, the SDT configuration information includes SDT configurations used as MO SDT configurations and MT SDT configurations, respectively.

[0080] In some exemplary embodiments, the terminal device 110 may further receive instructions from the network node 120 indicating whether the SDT configuration is to be used for the MT SDT procedure and / or the MO SDT procedure.

[0081] In some exemplary embodiments, the terminal device 110 may initiate or apply SDT settings for the MT SDT procedure and the MO SDT procedure, respectively.

[0082] In some exemplary embodiments, the terminal device 110 may further receive SDT configuration information from the network node 120 via dedicated signaling or common signaling.

[0083] In some exemplary embodiments, the terminal device 110 may initiate only the MT SDT procedure based on SDT configuration information, regardless of other SDT configuration information received via broadcast signaling.

[0084] In some exemplary embodiments, the SDT configuration information includes resource settings specific to the MT SDT procedure.

[0085] In some exemplary embodiments, the SDT configuration information includes a specific uplink data volume threshold for initiating or triggering an MO SDT procedure. In some exemplary embodiments, the terminal device 110 may further determine that an MO SDT procedure is not permitted based on the specific uplink data volume threshold.

[0086] In some exemplary embodiments, the SDT procedure is initiated when the terminal device 110 becomes capable of transmitting uplink data, when the network node 120 pages the terminal device 110, or when the network node 120 pages the terminal device 110 to initiate the SDT procedure.

[0087] In some exemplary embodiments, a non-SDT RRC restart procedure is initiated if the MO SDT procedure and / or MT SDT procedure are not permitted.

[0088] Figure 4 shows a flowchart of Method 400 as implemented on a network node according to some exemplary embodiments of the present disclosure. For convenience of explanation, Method 400 will be described in terms of network node 120 in Figure 1.

[0089] In block 410, the network node 120 transmits SDT configuration information to the terminal device 110. The SDT configuration information is used by the terminal device to determine whether it is permitted to use mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures.

[0090] In block 420, the network node 120 performs or applies at least one of the MT SDT procedure or MO SDT procedure with the terminal device based on the SDT configuration information. In some exemplary embodiments, the terminal device 110 is in the Radio Resource Control, RRC, inactive state. In some exemplary embodiments, the terminal device 110 is in the Radio Resource Control, RRC, idle state.

[0091] In some exemplary embodiments, the SDT configuration information indicates whether the terminal device is permitted to use the MT SDT procedure and / or the MO SDT procedure.

[0092] In some exemplary embodiments, the SDT configuration information includes at least one of the MO SDT configuration for an MO SDT procedure or the MT SDT configuration for an MT SDT procedure.

[0093] In some exemplary embodiments, the MO SDT setting is separate from or different from the MT SDT setting.

[0094] In some exemplary embodiments, the SDT configuration information includes SDT configurations used as MO SDT configurations and MT SDT configurations, respectively.

[0095] In some exemplary embodiments, the network node 120 may further send instructions to the terminal device 110 indicating whether the SDT configuration is to be used for the MT SDT procedure and / or the MO SDT procedure.

[0096] In some exemplary embodiments, the network node 120 may transmit SDT configuration information to terminal devices via dedicated signaling or common signaling, and the SDT configuration information is used solely for MT SDT procedures.

[0097] In some exemplary embodiments, the SDT configuration information includes resource settings specific to the MT SDT procedure.

[0098] In some exemplary embodiments, the SDT configuration information includes a specific uplink data volume threshold for initiating the MO SDT procedure, which is used to indicate to the terminal device 110 whether or not the MO SDT procedure is permitted.

[0099] In some exemplary embodiments, an apparatus capable of performing any of Method 300 (for example, the terminal device 110 in Figure 1) may include means for performing each operation of Method 300. These means can be implemented in any suitable form; for example, they may be implemented in a circuit or a software module. The apparatus may be implemented as the terminal device 110 in Figure 1, or may be included in the terminal device 110.

[0100] In some exemplary embodiments, the device includes means for receiving small data transmission, SDT, and configuration information from a network node; means for determining, based on the SDT configuration information, whether the device is permitted to use mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures; and means for initiating or applying at least one of the MT SDT procedures or MO SDT procedures based on the determination and / or the SDT configuration information.

[0101] In some exemplary embodiments, the device is in a Radio Resource Control (RRC) inactive state. In some exemplary embodiments, the device is in a Radio Resource Control (RRC) idle state.

[0102] In some exemplary embodiments, the SDT configuration information indicates whether the device is permitted to use the MT SDT procedure and / or the MO SDT procedure.

[0103] In some exemplary embodiments, the initiation means includes means for applying SDT configuration information only to the MT SDT procedure if the MO SDT procedure is not permitted.

[0104] In some exemplary embodiments, the SDT configuration information includes at least one of the MO SDT configuration for an MO SDT procedure or the MT SDT configuration for an MT SDT procedure.

[0105] In some exemplary embodiments, the MO SDT setting is separate from or different from the MT SDT setting.

[0106] In some exemplary embodiments, the initiation means includes means for initiating or applying only the MT SDT procedure for data communication between the device and the network node when the device has an MT SDT setting configured but no MO SDT setting configured.

[0107] In some exemplary embodiments, the SDT configuration information includes SDT configurations used as MO SDT configurations and MT SDT configurations, respectively.

[0108] In some exemplary embodiments, the device further includes means for receiving instructions from a network node indicating whether the SDT configuration is to be used for the MT SDT procedure and / or the MO SDT procedure.

[0109] In some exemplary embodiments, the initiation means includes means for initiating or applying the MT SDT procedure and the MO SDT procedure, respectively, based on the SDT settings.

[0110] In some exemplary embodiments, the device further comprises means for receiving SDT configuration information from network nodes via dedicated signaling or common signaling.

[0111] In some exemplary embodiments, the initiation means includes means for initiating or applying only the MT SDT procedure based on SDT configuration information, regardless of other SDT configuration information received via broadcast signaling.

[0112] In some exemplary embodiments, the SDT configuration information includes resource settings specific to the MT SDT procedure.

[0113] In some exemplary embodiments, the SDT configuration information includes a specific uplink data volume threshold for initiating or triggering an MO SDT procedure, and the device is configured to further perform means for determining whether or not an MO SDT procedure is permitted based on the specific uplink data volume threshold.

[0114] In some exemplary embodiments, the SDT procedure is initiated when the device becomes capable of transmitting uplink data, when a network node pages the device, or when a network node pages the device to initiate the SDT procedure.

[0115] In some exemplary embodiments, a non-SDT RRC restart procedure is initiated if the MO SDT procedure and / or MT SDT procedure are not permitted.

[0116] In some exemplary embodiments, the apparatus further comprises means for performing other operations in Method 300 or some exemplary embodiments of the terminal device 110. In some exemplary embodiments, the means comprises at least one processor and at least one memory for storing instructions that, when executed by the at least one processor, cause the apparatus to execute.

[0117] In some exemplary embodiments, an apparatus capable of performing any of the methods 400 (for example, network node 120 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, these means may be implemented in a circuit or a software module. The apparatus may be implemented as network node 120 in Figure 1, or may be included in network node 120.

[0118] In some exemplary embodiments, the apparatus comprises means for transmitting small data transmission, SDT, and configuration information to a terminal device, the SDT configuration information being used by the terminal device to determine whether the use of mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures is permitted to the terminal device, and means for performing or applying at least one of the MT SDT procedure or MO SDT procedure with the terminal device based on the SDT configuration information.

[0119] In some exemplary embodiments, the terminal device is in a Radio Resource Control (RRC) inactive state. In some exemplary embodiments, the terminal device is in a Radio Resource Control (RRC) idle state.

[0120] In some exemplary embodiments, the SDT configuration information indicates whether the terminal device is permitted to use the MT SDT procedure and / or the MO SDT procedure.

[0121] In some exemplary embodiments, the SDT configuration information includes at least one of the MO SDT configuration for an MO SDT procedure or the MT SDT configuration for an MT SDT procedure.

[0122] In some exemplary embodiments, the MO SDT setting is separate from or different from the MT SDT setting.

[0123] In some exemplary embodiments, the SDT configuration information includes SDT configurations used as MO SDT configurations and MT SDT configurations, respectively.

[0124] In some exemplary embodiments, the device further includes means for sending instructions to a terminal device indicating whether the SDT setting is used for the MT SDT procedure and / or the MO SDT procedure.

[0125] In some exemplary embodiments, the apparatus further comprises means for transmitting SDT configuration information to a terminal device via dedicated signaling or common signaling, wherein the SDT configuration information is used solely for MT SDT procedures.

[0126] In some exemplary embodiments, the SDT configuration information includes resource settings specific to the MT SDT procedure.

[0127] In some exemplary embodiments, the SDT configuration information includes a specific uplink data volume threshold for initiating the MO SDT procedure, which is used to indicate to the terminal device whether or not the MO SDT procedure is permitted.

[0128] In some exemplary embodiments, the device further comprises means for performing other operations in Method 400 or some exemplary embodiments of Network Node 120. In some exemplary embodiments, the means comprises at least one processor and at least one memory for storing instructions that, when executed by the at least one processor, cause the device to execute.

[0129] Figure 5 is a simplified block diagram of a device 500 suitable for carrying out exemplary embodiments of the present disclosure. The device 500 may be provided to carry out a communication device such as the terminal device 110 or network node 120 shown in Figure 1. As shown in the figure, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processors 510, and one or more communication modules 540 coupled to the processors 510.

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

[0131] The processor 510 can be any type suitable for a local technology network and, in non-limiting examples, may include one or more of general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore 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.

[0132] 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 programmable 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. Examples of volatile memories include, but are not limited to, random-access memory (RAM) 522 and other volatile memories that do not persist during power-off periods.

[0133] 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 / behaviors of some exemplary embodiments of this disclosure. Program 530 may be stored in memory, such as ROM 524. The processor 510 may perform any appropriate actions and processes by loading program 530 into RAM 522.

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

[0135] In some exemplary embodiments, the program 530 may be tangibly contained in a computer-readable medium that may be contained within device 500 (for example, in memory 520) or in other storage devices accessible by device 500. Device 500 may load the program 530 from the computer-readable medium into RAM 522 and execute it. In some exemplary 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,” as used herein, refers to the limitations of the medium itself (i.e., tangible rather than signal) rather than limitations on the persistence of data storage (e.g., RAM vs. ROM).

[0136] Figure 6 shows an example of a computer-readable medium 600, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 600 stores a program 530.

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

[0138] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored in a computer-readable medium, such as a non-temporary computer-readable medium. The computer program product includes computer-executable instructions, such as those contained in a program module, that are executed on a target physical or virtual processor in a device to perform any of the methods described above. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. The functionality of a program module may be combined or divided among program modules as needed in various embodiments. The machine-executable instructions of a program module may be executed in a local device or a distributed device. In a distributed device, a program module may reside in both local and remote storage media.

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

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

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

[0142] Furthermore, although the operations are shown in a specific order, this should not be understood as meaning that such operations must be performed in a specific illustrated order, sequentially, or all illustrated operations must be performed in order to obtain the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although the above description includes some specific implementation details, these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features that may be 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 separately in multiple embodiments or in any suitable subcombination.

[0143] While this disclosure uses language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the attached claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. At least one processor, At least one memory for storing instructions, A device comprising, where, when the instruction is executed by the at least one processor, the device has at least, Receiving small-scale data transmission, SDT, and configuration information from network nodes, Based on the SDT setting information, determine whether the device is permitted to use mobile incoming calls, MT, SDT procedures and / or mobile outgoing calls, MO, SDT procedures. Starting or applying at least one of the MT SDT procedure or the MO SDT procedure based on the determination and / or the SDT setting information, A device that performs an action.

2. The apparatus according to claim 1, wherein the apparatus is in a wireless resource control, RRC, and inactive state.

3. The apparatus according to claim 1, wherein the apparatus is in a wireless resource control, RRC, and idle state.

4. The apparatus according to any one of claims 1 to 3, wherein the SDT setting information indicates whether the apparatus is permitted to use the MT SDT procedure and / or the MO SDT procedure.

5. The aforementioned device is If the aforementioned MO SDT procedure is not permitted, the SDT setting information shall be applied only to the aforementioned MT SDT procedure. The apparatus according to any one of claims 1 to 4, which is configured to perform the following.

6. The apparatus according to any one of claims 1 to 5, wherein the SDT setting information includes at least one of the MO SDT setting for the MO SDT procedure or the MT SDT setting for the MT SDT procedure.

7. The apparatus according to claim 6, wherein the MO SDT setting is separate from or different from the MT SDT setting.

8. The aforementioned device is If the MT SDT setting is configured on the device but the MO SDT setting is not configured, then only the MT SDT procedure is initiated or applied for data communication between the device and the network node. The apparatus according to claim 6 or 7, which is configured to perform the following.

9. The apparatus according to claim 6, wherein the SDT setting information includes SDT settings used as the MO SDT setting and the MT SDT setting, respectively.

10. The aforementioned device is The network node receives instructions indicating which of the MT SDT procedure and / or MO SDT procedure the SDT setting will be used for. The apparatus according to claim 8, further configured to perform the following.

11. The aforementioned device is To initiate or apply the SDT settings for each of the aforementioned MT SDT procedures and MO SDT procedures. The apparatus according to claim 9, which is configured to perform the following.

12. The aforementioned device is Receiving the SDT configuration information from the network node via dedicated signaling or common signaling. The apparatus according to any one of claims 1 to 3, which is configured to perform the following.

13. The aforementioned device is Regardless of other SDT configuration information received via broadcast signaling, the SDT configuration information is to be initiated or applied only to the MT SDT procedure. The apparatus according to claim 12, which is configured to perform the following.

14. The apparatus according to any one of claims 1 to 4, wherein the SDT setting information includes resource settings specific to the MT SDT procedure.

15. The SDT configuration information includes a specific uplink data volume threshold for initiating or triggering the MO SDT procedure, and the device Based on the aforementioned specific uplink data volume threshold, it is determined whether or not the MO SDT procedure is permitted. The apparatus according to any one of claims 1 to 4, further configured to perform the following.

16. The MT SDT procedure or the MO SDT procedure, at least one of the above, When the device becomes capable of transmitting uplink data while RRC is inactive, If the network node pages the device in the RRC inactive state, or If the network node pages the RRC-inactive device in order to initiate the SDT procedure, The apparatus according to any one of claims 1 to 3, which is initiated in at least one of the following cases.

17. The apparatus according to any one of claims 1 to 3, wherein if the MO SDT procedure and / or the MT SDT procedure is not permitted, a non-SDT RRC restart procedure is initiated.

18. At least one processor, At least one memory for storing instructions, A device comprising, where, when the instruction is executed by the at least one processor, the device has at least, The transmission of small data, SDT, and configuration information to a terminal device, wherein the SDT configuration information is used by the terminal device to determine whether the use of mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, and SDT procedures is permitted to the terminal device. Based on the SDT configuration information, perform or apply at least one of the MT SDT procedure or the MO SDT procedure with the terminal device, A device that performs an action.

19. The apparatus according to claim 18, wherein the terminal device is in a wireless resource control, RRC, or inactive state.

20. The apparatus according to claim 18, wherein the terminal device is in a wireless resource control, RRC, or idle state.

21. The apparatus according to any one of claims 18 to 20, wherein the SDT setting information indicates whether the terminal device is permitted to use the MT SDT procedure and / or the MO SDT procedure.

22. The apparatus according to any one of claims 18 to 21, wherein the SDT setting information includes at least one of the MO SDT setting for the MO SDT procedure or the MT SDT setting for the MT SDT procedure.

23. The apparatus according to claim 22, wherein the MO SDT setting is separate from or different from the MT SDT setting.

24. The apparatus according to claim 22, wherein the SDT setting information includes SDT settings used as the MO SDT setting and the MT SDT setting, respectively.

25. The aforementioned device is To transmit an instruction to the terminal device indicating whether the SDT setting is used for the MT SDT procedure and / or the MO SDT procedure. The apparatus according to claim 24, further configured to perform the following.

26. The aforementioned device is Transmitting the SDT configuration information to the terminal device via dedicated signaling or common signaling, wherein the SDT configuration information is used only for the MT SDT procedure. The apparatus according to any one of claims 18 to 20, which is configured to perform the following.

27. The apparatus according to any one of claims 18 to 21, wherein the SDT setting information includes resource settings specific to the MT SDT procedure.

28. The apparatus according to any one of claims 18 to 21, wherein the SDT configuration information includes a specific uplink data volume threshold for initiating an MO SDT procedure, the specific threshold being used to indicate to the terminal device whether or not the MO SDT procedure is permitted.

29. Depending on the terminal device, it can receive small data transmissions, SDTs, and configuration information from network nodes. The terminal device determines, based on the SDT setting information, whether or not the use of mobile incoming calls, MT, SDT procedures and / or mobile outgoing calls, MO, SDT procedures is permitted for the terminal device. The terminal device initiates or applies at least one of the MT SDT procedure or the MO SDT procedure based on the determination and / or the SDT setting information, Methods that include...

30. The network node transmits small data transmission, SDT, and configuration information to a terminal device, the SDT configuration information being used by the terminal device to determine whether the terminal device is permitted to use mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures. The network node executes or applies at least one of the MT SDT procedure or the MO SDT procedure to the terminal device based on the SDT configuration information. Methods that include...

31. A means for receiving small-scale data transmission, SDT, and configuration information from network nodes. Means for determining whether the use of mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, SDT procedures is permitted for the device based on the SDT setting information, Means for initiating or applying at least one of the MT SDT procedure or the MO SDT procedure based on the determination and / or the SDT setting information, A device equipped with the following features.

32. Means for transmitting small data transmission, SDT, and configuration information to a terminal device, wherein the SDT configuration information is used by the terminal device to determine whether the use of mobile incoming, MT, SDT procedures and / or mobile outgoing, MO, and SDT procedures is permitted to the terminal device. Means for executing or applying at least one of the MT SDT procedure or the MO SDT procedure with the terminal device based on the SDT configuration information, A device equipped with the following features.

33. A computer-readable medium storing instructions for causing a device to perform at least the method according to claim 29 or the method according to claim 30.

Images