Data transmission processing

Abstract

To provide a system, a method, an apparatus, and a computer program product for processing data transmission, such as a non-small data transmission (SDT), in combination with an SDT.SOLUTION: In a mobile or wireless telecommunications system, a method performed by a network entity or node includes determining availability of non-small data transmission (non-SDT) data. The method also includes indicating a result of the determination to a network element.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 089,312, filed on October 8, 2020. The entire contents of this prior application are hereby incorporated by reference in their entirety.

[0002] Some exemplary embodiments may generally relate to mobile or wireless telecommunication systems such as Long - Term Evolution (LTE) or Fifth Generation (5G) radio access technology or New Radio (NR) access technology, or other communication systems. For example, certain exemplary embodiments may relate to apparatuses, systems, and / or methods for processing data transmission, such as non - small data transmission (SDT), in combination with SDT.

Background Art

[0003] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunication System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE Advanced (LTE-A), MulteFire, LTE-A Pro, and / or 5th Generation (5G) radio access technology or New Radio (NR) access technology. The 5th Generation (5G) wireless system refers to the next generation (NG) of wireless systems and network architectures. 5G is mainly built on New Radio (NR), but 5G (or NG) networks can also be built on E-UTRAN radio. NR is estimated to provide bitrates of approximately 10 - 20 Gbit / s and above, supporting at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC), as well as massive machine type communication (mMTC). NR is expected to provide a very wideband and ultra-robust low-latency connectivity and large-scale network to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more prevalent, the need for networks that meet the requirements of low power, high data rate, and long battery life will increase. Note that in 5G, a node that can provide wireless access functionality to user equipment (i.e., similar to NodeB in UTRAN or eNB in LTE) is called a gNB if it is built on NR radio and an NG-eNB if it is built on E-UTRAN radio.

SUMMARY OF THE INVENTION

[0004] Some exemplary embodiments are directed to a method. The method can include determining the availability of non-small data transmission (non-SDT) data. The method can also include indicating the result of this determination to a network element.

[0005] Other exemplary embodiments may be directed to an apparatus that can include at least one processor and at least one memory having computer program code. The at least one memory and the computer program code are configured to cause the apparatus, using the at least one processor, to at least determine the availability of non-small data transmission (non-SDT) data. The apparatus may also indicate the result of this determination to a network element.

[0006] Other exemplary embodiments may be directed to an apparatus that can include means for determining the availability of non-small data transmission (non-SDT) data. The apparatus may also include means for indicating the result of this determination to a network element.

[0007] According to other exemplary embodiments, a non-transitory computer-readable medium can be encoded with instructions that, when executed in hardware, can execute a method. The method can include determining the availability of non-small data transmission (non-SDT) data. The method can also include indicating the result of this determination to a network element.

[0008] Other exemplary embodiments may be directed to a computer program product that executes a method. The method can include determining the availability of non-small data transmission (non-SDT) data. The method can also include indicating the result of this determination to a network element.

[0009] Other exemplary embodiments may be directed to an apparatus that can include a circuit configured to determine the availability of non-small data transmission (non-SDT) data. The apparatus may also include a circuit configured to indicate the result of this determination to a network element.

[0010] Certain exemplary embodiments can be directed to a method. The method can include configuring a user equipment to trigger a small data transmission (SDT) of SDT data and indicate the presence of non-SDT data. The method can also include receiving an SDT data transmission that includes the SDT data. Further, the method can include receiving, from the user equipment, an indication that indicates the presence of the non-SDT data.

[0011] Other exemplary embodiments can be directed to an apparatus. The apparatus can include at least one processor and at least one memory having computer program code. The at least one memory and the computer program code can be configured to cause the at least one processor to configure a user equipment to at least trigger an SDT of small data transmission (SDT) data and indicate the presence of non-SDT data. The apparatus can also be adapted to receive an SDT data transmission that includes the SDT data. Further, the apparatus can be adapted to receive, from the user equipment, an indication that indicates the presence of the non-SDT data.

[0012] Other exemplary embodiments can be directed to an apparatus. The apparatus can include means for configuring a user equipment to trigger an SDT of small data transmission (SDT) data and indicate the presence of non-SDT data. The apparatus can also include means for receiving an SDT data transmission that has the SDT data. Further, the apparatus can include means for receiving, from the user equipment, an indication that indicates the presence of the non-SDT data.

[0013] According to another exemplary embodiment, a non-transitory computer-readable medium can be encoded with instructions that, when executed in hardware, can execute a method. The method can include triggering an SDT of small data transmission (SDT) data and configuring a user device to indicate the presence of non-SDT data. The method can also include receiving an SDT data transmission including the SDT data. Further, the method can include receiving, from the user device, an indication indicating the presence of non-SDT data.

[0014] Another exemplary embodiment can be directed to a computer program product that executes a method. The method can include triggering an SDT of small data transmission (SDT) data and configuring a user device to indicate the presence of non-SDT data. The method can also include receiving an SDT data transmission including the SDT data. Further, the method can include receiving, from the user device, an indication indicating the presence of non-SDT data.

[0015] Another exemplary embodiment can be directed to an apparatus that can include a circuit configured to trigger an SDT of small data transmission (SDT) data and configure a user device to indicate the presence of non-SDT data. The apparatus can also include a circuit configured to receive an SDT data transmission including the SDT data. Further, the apparatus can include a circuit configured to receive, from the user device, an indication indicating the presence of non-SDT data.

[0016] For a proper understanding of the exemplary embodiments, please refer to the accompanying drawings.

Brief Description of the Drawings

[0017]

Figure 1(a)

Figure 1(b)

Figure 1(c)

Figure 2

Figure 3

Figure 4

Figure 5(a)

Figure 5(b)

Figure 6(a)

Figure 6(b)

Figure 7

Figure 8

Figure 9(a)

Figure 9(b)

Best Mode for Carrying Out the Invention

[0018] It will be readily understood that the components of the specific exemplary embodiments generally described herein and shown in the figures can be arranged and designed in a wide variety of different configurations. The following is a detailed description of some exemplary embodiments of a system, method, apparatus, and computer program product for processing data transmission such as non-small data transmission (SDT) in combination with SDT.

[0019] The features, structures, or characteristics of the exemplary embodiments described throughout this specification can be incorporated in any suitable manner into one or more of the exemplary embodiments. For example, the use throughout this specification of phrases such as "specific embodiments", "exemplary embodiments", "some embodiments", or other similar language refers to the fact that the specific features, structures, or characteristics described in connection with the embodiments can be included in at least one embodiment. Thus, the appearance throughout this specification of phrases such as "in a specific embodiment", "in an exemplary embodiment", "in some embodiments", "in other embodiments", or other similar language does not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics can be incorporated in any suitable manner into one or more of the exemplary embodiments.

[0020] Furthermore, if necessary, the different functions or procedures discussed below may be executed in a different order and / or in parallel with each other. Additionally, if necessary, one or more of the described functions or procedures may be optional or may be combined. Thus, the following description should be regarded as merely illustrative of the principles and teachings of the specific exemplary embodiments and not as limiting the specific exemplary embodiments.

[0021] Figure 1(a) shows an example of a 4-step based Small Data Transmission (SDT) signaling diagram. Further, Figure 1(b) shows an example of a 2-step based SDT signaling diagram. Figure 1(c) shows an example of a Configured Grant (CG) based SDT signaling diagram. The 3rd Generation Partnership Project (3GPP) describes various solutions for enabling SDT of uplink (UL) user plane (UP) data in the radio resource control (RRC) inactive state of the 5G New Radio (NR) system. As shown in Figure 1(a), 3GPP describes a 4-step random access channel (RACH) based SDT. Here, the UP data may be transmitted in Msg3 of the 4-step RACH procedure. For example, the small data payload can be multiplexed with the RRC connection resume request message of Msg3, such as a media access control (MAC) protocol data unit (PDU).

[0022] As shown in Figure 1(b), 3GPP describes a 2-step RACH based SDT. In this procedure, the UP data transmission can occur in MsgA of the 2-step RACH procedure, specifically on a physical uplink shared channel (PUSCH) resource. The PUSCH resource can be preconfigured by the gNB and broadcast in the system information along with the associated physical transmission parameters.

[0023] Furthermore, as shown in Figure 1(c), 3GPP describes a CG based SDT. Here, a UE in the RRC_connected state can receive a CG type 1 configuration. According to a particular exemplary embodiment, this configuration can indicate a preconfigured PUSCH resource dedicated for UL data transmission in the RRC_inactive state as long as the timing adjustment is effective.

[0024] In certain cases, an RRC-based approach as shown in FIGS. 1(a) to 1(c) may be assumed. For example, the UE may transmit an RRC message containing information regarding the UE identifier and its authentication token (i.e., MAC-I). In FIGS. 1(a) to 1(c), it can be assumed that an RRC resume request message is used for this purpose, and FIG. 2 shows an example of the content corresponding to the UL MAC PDU. In an approach without RRC, it may be assumed that the RRC layer does not need to be involved in the SDT operation, and the necessary information such as the user equipment (UE) identifier and the UE authentication token may be provided by the UE in the MAC header or as a MAC control element (CE). Further, a data volume threshold may be used to determine whether the UE needs to execute the SDT or resume procedure.

[0025] According to 3GPP, the SDT may be configured by the network in units of data radio bearers (DRBs). The minimum number of DRBs that a UE can support can be 16 without duplication and 8 per MAC entity with duplication. However, up to 29 DRBs can be added to the DRB-toAddModList, and each DRB can be identified by its DRB identifier. Further, the configured DRBs may be suspended by the UE when receiving an RRC release message by SuspendConfig. Further, a buffer status report (BSR) transmitted from the UE to the gNB via a MAC CE can indicate the amount of pending data in the UL buffer permitted by an explicit buffer size bitfield for each NR logical channel group (LCG). Further, with a dedicated MAC CE format, it may be possible to transmit a short (truncated) BSR and a long (truncated) BSR indicating a buffer size index corresponding to the actual buffer size level (in bytes) of one or more logical channel groups (LCGs). Then, the network (gNB) can schedule UL resources for each UE according to the BSR, based on the quality of service (QoS) characteristics of the corresponding DRB.

[0026] In some cases, a logical channel group (LCG) can be used to construct an integrated report of buffer status for signaling overhead efficiency. For example, the buffer status can be reported by aggregating data across a group of logical channels (LCHs) assigned to the same LCG. Conversely, resource allocation may be performed according to logical channels. The mapping of radio bearers and logical channels to LCGs can be performed by the gNB at radio bearer setup time via RRC signaling and can be based on the corresponding QoS attributes of the radio bearers. Current BSR triggers include situations where new data arrives in a previously empty buffer, situations where higher-priority data arrives after the UE has already sent a BSR and is waiting for a grant, situations where the UE needs to update the gNB about the status of the buffer (e.g., periodically according to the periodicBSR-timer), and situations where a BSR retransmission can be sent according to the retxBSR-timer to provide BSR robustness.

[0027] Furthermore, 3GPP describes that the UE AS context can be stored in the UE while it is in the RRC_inactive state and in the last serving gNB (e.g., the anchor gNB or the old NG-RAN node). The UE AS context can include the current RRC context, which has the suspended RRC configuration and the UE radio capabilities. The UE AS context can also include the current AS security context, which has the UE security capabilities and security information. Furthermore, the UE AS context can include the current configuration of the suspended DRBs, which have the packet data convergence protocol (PDCP) state with the robust header compression (ROHC) state, the service data application protocol (SDAP) configuration, and the radio link control (RLC) configuration. Furthermore, the UE AS context can include the cell radio network temporary identifier (C-RNTI) used in the source Pcell, the cell identifier, and the physical cell identifier (PCI) of the source Pcell.

[0028] In certain cases, when receiving an RRC release in SuspendConfiguration, the UE may be triggered to transition from the RRC connected state to the RRC inactive state and suspend the currently configured DRBs. According to Radio Access Network 2 (RAN2), the SDT feature can be configured on a per-DRB basis. This may imply that the presence of traffic belonging to the DRB(s) configured with SDT can trigger the SDT. These DRBs may be referred to as SDT-DRBs. In this case, the SDT can be selected if the SDT selection condition(s) are met. Further, at least the selection condition based on the data volume may be defined, for example, as the total data volume of the SDT-DRBs being below the maximum data volume threshold defined by the network for SDT in order to select the SDT. Conversely, any other suspended DRB not configured with SDT (referred to as non-SDT DRB) may need to initiate a resume procedure to enable data transfer. This scenario is shown in Figure 3, which depicts an exemplary resume procedure for enabling data transfer.

[0029] Figure 4 indicates an example when SDT data and non-SDT data coexist in the buffer and the user equipment has started the triggered SDT and resume procedures. When only a given type of traffic (SDT or non-SDT) exists in the UE's buffer, SDT-DRB and non-SDT DRB operations may be easy, but problems may occur when data of both SDT-DRB and non-SDT DRB exist in the buffer. As shown in Figure 4, when new data arrives at the UE buffer from SDT-DRB and non-SDT DRB almost simultaneously, the current SDT signaling (see Figure 1) may be able to carry only the UL data of SDT-DRB and / or related information (e.g., BSR of SDT-DRB / LCG). Conversely, it is clear how such signaling can provide an indication of the existence of other traffic not intended to be provided via SDT. Therefore, certain exemplary embodiments provide signaling extensions for handling cases where SDT data and non-SDT data coexist. Without such extensions, as shown in Figure 4, every time data is generated in combination with SDT-DRB data, extra delays may occur in the transfer of non-SDT DRB data.

[0030] Certain exemplary embodiments may enable a UE in the RRC_inactive state to handle the case where SDT and non-SDT data may coexist in the UE's buffer at the time of starting SDT. For example, in certain exemplary embodiments, when the SDT procedure is triggered by the UE and data becomes available in the non-SDT DRB, the UE may be able to indicate the existence of the non-SDT DRB. The indication by the UE can be achieved by various means or options.

[0031] For example, in certain exemplary embodiments, a new BSR trigger that does not consider the priority of LCH may be defined, but the BSR may be triggered based on data becoming available on a non-SDT DRB when the SDT procedure is in progress. In this situation, the existing BSR format can be used for reporting. For example, the network (NW) can deduce that there is data on the non-SDT DRB by using the LCG with the data information. Alternatively, a new indication (or new format) in the BSR that indicates data availability on the non-SDT DRB may be defined.

[0032] According to other exemplary embodiments, a new MAC CE can be defined to indicate data availability on the non-SDT DRB. Here, the MAC CE can indicate, for example, the DRB ID / Logical Channel ID (LCID) of the LCH, the data volume, the LCG of the LCH, etc. In certain exemplary embodiments, another option can include the SDAP / PDCP / RLC control PDU of the non-SDT DRB multiplexed with the SDT data to indicate that there is data on the non-SDT DRB.

[0033] In other exemplary embodiments, another option can include triggering a new RRC message that indicates that data has also become available in the non-SDT DRB buffer(s). Such an RRC message can be a common control channel (CCCH) (SRB0) message, may be multiplexed by the RRC message used in the SDT procedure (e.g., RRC Resume), or may be transmitted via a UL grant addressed to the C-RNTI after the C-RNTI is assigned during the SDT procedure. Further, the RRC message can indicate, for example, the DRB ID / LCID of the LCH, the data volume, the LCG of the LCH, etc.

[0034] According to certain exemplary embodiments, the option can include triggering the RRC Resume message to be retransmitted with a resume cause that the NW can deduce if data exists in the non-SDT DRB. For example, the resume cause can be mobile-originated data (MO-data) (i.e., uplink data), or a new resume cause defined for the purpose.

[0035] According to other exemplary embodiments, the option can include indication of the existence of non-SDT DRB data in the UE buffer that is triggered when the data has a higher priority than the SDT-DRB data. This can be based on, for example, the LCH priority of the MAC layer. As described herein, "SDT is triggered" can mean that the UE (e.g., the RRC / MAC layer of the UE) has selected the SDT based on the detection of the existence of SDT data and the SDT selection conditions (e.g., data threshold), but has not yet started the actual SDT (such as MsgA / Msg3 of CG transmission). However, in the case of a multi-shot SDT where one single SDT transaction can include more than one actual data transmission (without transitioning the UE to the RRC_connected state), the same manner as above can be applied during the SDT procedure (i.e., the UE has already performed the first actual data transmission).

[0036] In certain exemplary embodiments, when the SDT procedure is triggered by the UE and data becomes available in the non-SDT DRB, the UE can abort the SDT procedure and trigger the RRC resume procedure. Alternatively, or additionally, this can depend on the priority of the SDT-DRB for the data compared to the non-SDT DRB for the data. For example, if the data of the SDT-DRB has a higher priority, the SDT procedure can be completed by the UE. However, if the data of the non-SDT DRB has a higher priority, the SDT procedure may be aborted.

[0037] In other exemplary embodiments, when the SDT procedure is triggered by the UE and data becomes available on a non-SDT DRB, whether the SDT procedure is aborted or completed by the UE may depend on whether the SDT data has already been transmitted by the UE. For example, if the data of the SDT-DRB has been transmitted, the SDT procedure can be completed by the UE. On the other hand, if the data of the SDT-DRB has not been transmitted, the SDT procedure can be aborted.

[0038] According to a particular exemplary embodiment, when the SDT procedure is triggered by the UE and data becomes available on a non-SDT DRB, the UE can buffer the data on the non-SDT DRB until the SDT procedure is completed (i.e., after receiving RRCResume or RRCRelease from the NW by supsendConfig). After receiving RRCRelease by supsendConfig, the UE can trigger the connection resumption procedure for non-SDT DRB data transmission.

[0039] According to other exemplary embodiments, when the UE is in the RRC_inactive state, configured with SDT, and UL data becomes available (or is available) for transmission on both the SDT-DRB and the non-SDT DRB, the UE can trigger the normal RRC resume procedure instead of the SDT transmission. In a particular exemplary embodiment, this may be common when the RRC resume procedure is started when data arrives on the non-SDT DRB and data becomes available on the SDT-DRB.

[0040] In certain exemplary embodiments, the UE implementation can determine whether to resume a new RRC procedure for RRC resume or continue the SDT procedure when data arrives at a non-SDT DRB while the SDT procedure has already been triggered. In other exemplary embodiments, the network can control UE behavior, which may include new signaling. For example, the signaling can be for configuring the UE as to which indication related to the presence of non-SDT data the network should report and when / how to trigger such a report. The signaling can also be for the UE to start SDT to indicate the presence of data belonging to a non-SDT DRB to the network according to network configuration or to transmit permitted UL data belonging to an SDT-DRB. According to certain exemplary embodiments, if the SDT-DRB(s) are not configured by the network, the UE can determine that all configured DRB(s) are SDT-DRBs, that SDT is not permitted, or that only default bearers are permitted for SDT.

[0041] Figure 5(a) shows a signaling diagram of non-SDT data indication via BSR in addition to SDT according to a specific exemplary embodiment. As shown in Figure 5(a), at 500, the UE may be in the RRC_connected state. At 505, the gNB may send a message with an RRC release by SuspendConfig, which may include an SDT configuration. Further, the SDT configuration may include the first SDT-DRB and optional BSR information for the second non-SDT DRB. According to a specific exemplary embodiment, a 4-step RACH-based SDT procedure may be assumed. However, in other exemplary embodiments, the SDT procedure may use a 2-step RACH-based SDT or a configured grant-based SDT. At 510, the UE can change to the RRC_inactive state, and at 515, the UE can have a new payload in the UE's buffer for the first DRB and the second DRB. Further, at 520, the UE can send a physical random access channel (PRACH) preamble to the gNB via Msg1. At 525, the gNB can respond by sending a random access response (RAR) to the UE via Msg2. At 530, the UE can send SDT via Msg3 with a UL payload that includes the first DRB (the first SDT-DRB mapped to the first SDT-LCG) in addition to the BSR (the second non-SDT DRB mapped to the second non-SDT LCG). At 535, the gNB can send an RRC resume indication via Msg4, and at 540, the UE can revert to the RRC_connected state.

[0042] Figure 5(b) shows a signaling diagram of the resume procedure after SDT abort due to the presence of SDT data and non-SDT data according to a specific exemplary embodiment. As shown in Figure 5(b), at 545, the UE can be in the RRC_connected state. At 550, the gNB can send a message with an RRC release to the UE by means of SuspendConfig. This message can include an SDT configuration that may have first SDT-DRB data. According to a specific exemplary embodiment, the SDT configuration can also include configuration / information for aborting the SDT procedure when both SDT data and non-SDT data are present. Alternatively, in other exemplary embodiments, the configuration / information for aborting the SDT procedure when both SDT data and non-SDT data are present can be written into the specification. Further, in some exemplary embodiments, the configuration regarding whether to abort SDT can depend on the type of SDT procedure. For example, aborting SDT can depend on whether the SDT procedure is a 4-step, 2-step, or CG-SDT procedure. For example, the abort may be applicable to an RACH-based SDT procedure and not applicable to a CG-based SDT. At 555, the UE can change to the RRC_inactive state. Further, at 560, a new payload can appear in the UE's buffer for the first DRB, and the SDT procedure can be triggered. At 565, a new payload can appear in the UE's buffer for the second DRB, and at that point, the UE can abort the SDT procedure and trigger the RRC resume procedure. At 570, the UE can send a PRACH preamble to the gNB via Msg1. In response, at 575, the gNB can send an RAR to the UE via Msg2. At 580, the UE can send an RRC message (e.g., an RRC resume request) indicating SDT data and non-SDT data to the gNB via Msg3.At 585, the gNB can send an RRC resume message to the UE via Msg4, and then at 590, the UE can revert to the RRC_connected state.

[0043] Figure 6(a) shows a signaling diagram of non-SDT data buffering according to a particular exemplary embodiment. At 600, the UE may be in the RRC_connected state. At 602, the gNB can send a message with an RRC release accompanied by a SuspendConfig to the UE. The message can include an SDT configuration with a first SDT-DRB. At 604, the UE can change to the RRC_inactive state. At 606, a new payload can appear in the UE's buffer for the first DRB, and the SDT procedure can be triggered. At 608, the UE can send a PRACH preamble to the gNB via Msg1. In response, at 610, the gNB can send an RAR to the UE via Msg2. Further, at 612, the UE can send the SDT (first SDT-DRB) to the gNB via Msg3 with a UL payload. At 614, the gNB can send an RRC release with a SuspendConfig to the UE via Msg4. As shown in Figure 6(a), between Msg2 and Msg4, a new payload can appear in the UE's buffer for a second non-SDT DRB while the SDT transaction is in progress. The second non-SDT DRB data can be buffered while the SDT transaction is in progress.

[0044] At 616, the UE can be in the RRC_inactive state. Further at 608, the UE can send a PRACH preamble to the gNB via Msg1. In response, at 620, the gNB can send an RAR to the UE via Msg2. Between 618 and 624, after the completion of the SDT transaction, an RRC resume procedure associated with the second non-SDT DRB data can be triggered. At 622, the UE can send an RRC resume request to the gNB via Msg3. In response, at 624, the gNB can send an RRC resume response to the UE via Msg4.

[0045] Figure 6(b) shows another signaling diagram of non-SDT data buffering according to a specific exemplary embodiment. As shown in Figure 6(b), at 626, the UE can be in the RRC_connected state. At 628, the gNB can send an RRC release to the UE by SuspendConfig. This message can include an SDT configuration having a first SDT-DRB. Further, at 630, the UE can be in the RRC_inactive state. At 632, a new payload can appear in the UE's buffer for the first DRB and the second DRB, and SDT can be started while non-SDT is being buffered. At 634, the UE can send a PRACH preamble to the gNB via Msg1. In response, at 636, the gNB can send an RAR to the UE via Msg2. At 638, the UE can send a UL payload (first SDT-DRB) to the gNB via Msg3. At 640, the gNB can send an RRC release by SuspendConfig to the UE via Msg4. Further, at 642, the UE can be in the RRC_inactive state. At 644, after the completion of the SDT transaction, an RRC resume procedure associated with the second non-SDT DRB data can be triggered.

[0046] According to certain exemplary embodiments, the network can be configured to determine whether the UE is permitted to use SDT for a DRB / LCG, and whether the UE can send an indication together with the SDT that the data existing for the DRB / LCG is not permitted to use SDT. In some exemplary embodiments, the UE can be configured not to send an indication for non-permitted DRB(s) / LCG(s). For example, an LCG including any LCH may not be mapped to an SDT-DRB. In other exemplary embodiments, the UE can be configured to send an indication of a subset of non-SDT DRB / LCG ID(s). In further exemplary embodiments, the UE can be configured to determine whether to cancel / defer an ongoing trigger to resume an RRC connection whenever a trigger to start SDT is satisfied. According to certain exemplary embodiments, the UE may be composed of DRB / LCG permitted for SDT, and there may be no separate configuration regardless of whether the indication is permitted. For example, the UE may be able to send an indication.

[0047] In certain exemplary embodiments, the UE can be configured (or operate as specified) to indicate the presence of data belonging to non-SDT-LCG via the BSR. Further, when starting SDT, the UE can multiplex and transmit such a BSR with UL data. For example, in some exemplary embodiments, a new BSR format can be used, which can be constructed to distinguish between SDT-LCG and non-SDT-LCG. According to certain exemplary embodiments, this distinction can be beneficial as it enables the BSR indication to be accurately and timely interpreted by a new cell / gNB (different from the last serving gNB). Without this feature, the new cell / gNB would not inherently know whether a particular LCG is permitted to use SDT unless / until it requests and receives the UE context from the anchor gNB (the last serving gNB). According to further exemplary embodiments, the target gNB can determine different actions based on whether the BSR report is for an SDT-LCG. In the former case (i.e., the BSR indicating SDT data), the network can determine to provide data without transitioning the UE to the RRC_connected state (i.e., using subsequent packets during multi-shot SDT). For this purpose, while performing context acquisition, the network can start scheduling the UE and buffer multiple packets. According to certain exemplary embodiments, the network may be able to process the buffered packets when it receives the UE context. When the BSR indicates non-SDT data, the network can determine to immediately transition the UE to the RRC_connected state during the execution of the anchor relocation procedure.

[0048] According to certain exemplary embodiments, when the UE performs SDT for a cell different from the last serving cell, a new BSR format may be used. However, if the cells are the same, the UE can use the normal BSR format. According to further exemplary embodiments, a dedicated BSR index (e.g., value 0) may be assigned to indicate that a particular reported LCG(s) is non-SDT (i.e., partitioning of the LCG ID space). In certain exemplary embodiments, a new indication (e.g., a flag) can be added for each LCG to indicate whether the LCG is permitted for SDT. In other exemplary embodiments, the total buffer size of the targeted non-SDT LCGs can be reported, indicating that it is non-SDT data, but the corresponding LCG ID(s) can be omitted from the report. In some exemplary embodiments, this omission may be done when the UE performs SDT for a cell different from the last serving cell. According to certain exemplary embodiments, a short BSR format can be used to carry the buffer size index and the non-SDT LCG ID. Further, in other exemplary embodiments, the BSR format can be used to carry at least two buffer size indexes corresponding to at least one non-SDT LCG ID.

[0049] According to certain exemplary embodiments, the UE can be configured (or function as specified) to indicate the presence of data belonging to non-SDT-LCG via a (new) RRC message and multiplex and transmit such an RRC message with UL data when starting SDT. According to other exemplary embodiments, the (new) RRC message can extend the RRC resume request message and include additional indications such as the transmission cause being "MO-SDT + presence of non-SDT data" or similarly "MO-SDT + resume request". According to further exemplary embodiments, the RRC message can include the UL data amount of the UE for non-SDT DRB and / or SDT DRB.

[0050] Figure 7 shows a flow diagram of a method according to a particular exemplary embodiment. In a particular exemplary embodiment, the flow diagram of FIG. 7 can be executed by a network entity or network node within a 3GPP system such as LTE or 5G-NR. For example, in an exemplary embodiment, the method of FIG. 7 can be executed by a UE, similar to the apparatuses 10 or 20 shown in FIGS. 9(a) and 9(b) for example.

[0051] According to a particular exemplary embodiment, the method of FIG. 7 may include, at 700, determining the availability of non-small data transmission (non-SDT) data. The method may also include, at 705, indicating the result of this determination to a network element.

[0052] According to a particular exemplary embodiment, the method may also include determining the availability of small data transmission (SDT) data and triggering an SDT procedure when it is determined that the SDT data is available. According to some exemplary embodiments, determining the availability of non-SDT data may be performed while the SDT procedure is in progress or at the start of the SDT procedure. According to other exemplary embodiments, the method may further include triggering a connection resumption procedure when it is determined that the non-SDT data is available. According to further exemplary embodiments, the method may also include performing SDT on a network element using the SDT data.

[0053] In certain exemplary embodiments, determining whether non-SDT data is available while the SDT procedure is in progress may include determining that the non-SDT data is available. In other exemplary embodiments, indicating the result of this determination to a network element may include indicating the presence of non-SDT data. In some exemplary embodiments, the presence of non-SDT data may be indicated during the SDT procedure. In further exemplary embodiments, indicating the result of this determination to a network element may be performed via one of a buffer status report (BSR), a new media access control control element, a service data adaptation protocol control protocol data unit, a packet data convergence protocol control protocol data unit, a radio link control control protocol data unit, or a connection resume message. In some exemplary embodiments, the indication via the BSR may be transmitted in the SDT procedure.

[0054] According to certain exemplary embodiments, indicating the result of this determination to a network element may be performed by transmitting a new radio resource control (RRC) message. According to some exemplary embodiments, when the SDT procedure is triggered, the new RRC message may be multiplexed with the SDT data. According to other exemplary embodiments, indicating the result of this determination to a network element may include indicating the presence of SDT data and non-SDT data. According to further exemplary embodiments, the presence of SDT data and non-SDT data may be indicated in the BSR information.

[0055] In certain exemplary embodiments, the method can further include buffering SDT data and non-SDT data. In some exemplary embodiments, if non-SDT data is available, the method can further include aborting the SDT procedure and triggering a connection resumption procedure. In other exemplary embodiments, the abort can be based on the priority of the SDT data or whether the SDT data has already been transmitted. In further exemplary embodiments where non-SDT data is available, the method can also include buffering non-SDT data while the SDT procedure is in progress.

[0056] According to certain exemplary embodiments, after the SDT procedure is completed, the method can further include triggering a connection resumption procedure for non-SDT data transmission. According to some exemplary embodiments, the method can also include buffering SDT data and non-SDT data and starting the SDT procedure while non-SDT data is being buffered. According to other exemplary embodiments, the method can further include transmitting the SDT data to a network element while non-SDT data is being buffered.

[0057] FIG. 8 shows a flow diagram of another method according to certain exemplary embodiments. In certain exemplary embodiments, the flow diagram of FIG. 8 can be executed by a telecommunications network, a network entity or a network node in a 3GPP system such as LTE or 5G-NR. For example, in an exemplary embodiment, the method of FIG. 8 can be executed by a gNB, similar to the apparatuses 10 or 20 shown in FIGS. 9(a) and 9(b) for example.

[0058] According to certain exemplary embodiments, the method of FIG. 8 may include, at 800, configuring a user equipment to trigger SDT of small data transmission (SDT) data and indicate the presence of non-SDT data. The method may further include, at 805, receiving an SDT data transmission including the SDT data. Additionally, the method may include, at 810, receiving an indication from the user equipment indicating the presence of non-SDT data.

[0059] According to certain exemplary embodiments, the configuration of the user equipment may be performed via a radio resource control (RRC) message. According to some exemplary embodiments, the RRC message may trigger the user equipment to transition from the RRC connected state to the RRC inactive state. According to other exemplary embodiments, the indication of the presence of non-SDT data may be received via one of a buffer status report (BSR), a new media access control control element, a service data adaptation protocol control protocol data unit, a packet data convergence protocol control protocol data unit, a radio link control control protocol data unit, or a connection resume message. According to further exemplary embodiments, the indication via the BSR may be received during an SDT procedure.

[0060] In certain exemplary embodiments, configuring the user equipment can include configuring the user equipment as to which indication related to the presence of non-SDT data should be reported, and when to trigger such a report, or whether to trigger such a report. In some exemplary embodiments, the method can further include configuring the user equipment to initiate SDT to transmit permitted uplink SDT data. In other exemplary embodiments, configuring the user equipment includes configuring the user equipment not to transmit an indication about non-SDT data, configuring the user equipment to transmit an indication about a subset of non-SDT data, configuring the user equipment to cancel or defer an ongoing trigger to resume an RRC connection each time a trigger to initiate SDT is satisfied, configuring the user equipment with SDT data permitted for SDT, or configuring the user equipment to abort SDT if both SDT data and non-SDT data are present, including one or more of the above.

[0061] Figure 9(a) shows an apparatus 10 according to certain exemplary embodiments. In certain exemplary embodiments, the apparatus 10 can be a node or element within or associated with a communication network, such as a UE, a mobile device (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. In other exemplary embodiments, the apparatus 10 can be a network element, node, host, server within or providing such a communication network. It should be noted that those skilled in the art will understand that the apparatus 10 can include components or features not shown in Figure 9(a).

[0062] In some exemplary embodiments, device 10 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more wireless access components (e.g., modem, transceiver, etc.), and / or a user interface. In some exemplary embodiments, device 10 may be configured to operate using one or more wireless access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other wireless access technology. It should be noted that those skilled in the art will understand that device 10 may include components or features not shown in FIG. 9(a).

[0063] As shown in the example of FIG. 9(a), device 10 may include or be coupled to a processor 12 for processing information and executing instructions or operations. Processor 12 can be any type of general-purpose or dedicated processor. In practice, processor 12 can include, by way of example, one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although a single processor 12 is shown in FIG. 9(a), multiple processors according to other exemplary embodiments can be utilized. For example, in certain exemplary embodiments, it should be understood that device 10 may include two or more processors that can form a multi-processor system (e.g., in this case, processor 12 can represent a multi-processor) that can support multi-processing. According to certain exemplary embodiments, the multi-processor system may be tightly coupled (e.g., to form a computer cluster) or loosely coupled.

[0064] Processor 12 can perform functions related to the operation of device 10, including, by way of example, pre-coding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10 having the processes shown in FIGS. 1-7.

[0065] Device 10 may further include or be coupled to memory 14 (internal or external) for storing information and instructions executable by processor 12. Memory 14 can be one or more memories suitable for a local application environment and of any type, and can be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 14 can be composed of any combination of random access memory (RAM), read only memory (ROM), static storage such as magnetic disk or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer-readable medium. Instructions stored in memory 14 can include program instructions or computer program code, and when executed by processor 12, these program instructions or computer program code enable device 10 to perform the tasks described herein.

[0066] In certain exemplary embodiments, device 10 may further include or be coupled to a (internal or external) drive or port configured to receive and read an external computer-readable storage medium, such as an optical disk, USB drive, flash drive, or any other storage medium. For example, the external computer-readable storage medium can store a computer program or software executable by processor 12 and / or device 10 to perform any of the methods shown in FIGS. 1-7.

[0067] In some exemplary embodiments, the apparatus 10 may include or be coupled to one or more antennas 15 for receiving downlink signals and transmitting them via an uplink from the apparatus 10. The apparatus 10 may further include a transceiver 18 configured to transmit and receive information. The transceiver 18 may also include a wireless interface (e.g., a modem) coupled to the antenna 15. The wireless interface may be capable of supporting multiple radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The wireless interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., and may be capable of processing symbols such as OFDMA symbols carried by the downlink or uplink.

[0068] For example, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other exemplary embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some exemplary embodiments, the apparatus 10 may include input and / or output devices (I / O devices). In certain exemplary embodiments, the apparatus 10 may further include a user interface such as a graphical user interface or a touch screen.

[0069] In certain exemplary embodiments, memory 14 stores software modules that, when executed by processor 12, provide functionality. The modules can include, for example, an operating system that provides operating system functionality to device 10. The memory can also store one or more functional modules, such as applications or programs, to provide additional functionality to device 10. The components of device 10 can be implemented in hardware, or as any suitable combination of hardware and software. According to certain exemplary embodiments, device 10 can optionally be configured to communicate with device 20 via a wireless or wired communication link 70 according to any wireless access technology, such as NR.

[0070] According to certain exemplary embodiments, processor 12 and memory 14 may be included in, or form part of, a processing circuit or a control circuit. Further, in some exemplary embodiments, transceiver 18 may be included in, or form part of, a transmit-receive circuit.

[0071] As described above, according to certain exemplary embodiments, device 10 may be, for example, a UE. According to certain exemplary embodiments, device 10 may be controlled by memory 14 and processor 12 to perform functions related to the exemplary embodiments described herein. For example, in certain exemplary embodiments, device 10 may be controlled by memory 14 and processor 12 to determine the availability of non-small data transmission (non-SDT) data. Also, device 10 may be controlled by memory 14 and processor 12 to indicate the result of this determination to a network element.

[0072] Figure 9(b) shows apparatus 20 according to a particular exemplary embodiment. In a particular exemplary embodiment, apparatus 20 may be a node or element within a communication network, such as a base station, NodeB, evolved NodeB (eNB), 5G NodeB or access point, next generation NodeB (NG-NB or gNB), and / or a WLAN access point, associated with a radio access network (RAN) such as an LTE network, 5G or NR, or may be a node or element associated with such a network. It should be noted that those skilled in the art will understand that apparatus 20 may include components or features not shown in Figure 9(b).

[0073] As shown in the example of Figure 9(b), apparatus 20 may include a processor 22 for processing information and executing instructions or operations. Processor 22 can be any type of general-purpose or dedicated processor. For example, processor 22 can include, by way of example, one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although a single processor 22 is shown in Figure 9(b), multiple processors can be utilized according to other exemplary embodiments. For example, in a particular exemplary embodiment, it should be understood that apparatus 20 may include two or more processors that can form a multi-processor system (e.g., in this case, processor 22 can represent a multi-processor) that can support multi-processing. In a particular exemplary embodiment, the multi-processor system may be tightly coupled (e.g., to form a computer cluster) or loosely coupled.

[0074] According to certain exemplary embodiments, processor 22 can perform functions related to the operation of device 20, and these functions can include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 20 having the processes shown in FIGS. 1-6 and FIG. 8.

[0075] Device 20 may further include or be coupled to a memory 24 (internal or external) that can be coupled to processor 22 for storing information and instructions executable by processor 22. Memory 24 can be one or more memories suitable for a local application environment and of any type, and can be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 24 can be composed of any combination of random access memory (RAM), read-only memory (ROM), static storage such as magnetic disks or optical disks, hard disk drives (HDDs), or any other type of non-transitory machine or computer-readable medium. Instructions stored in memory 24 can include program instructions or computer program code, and when executed by processor 22, these program instructions or computer program code enable device 20 to perform the tasks described herein.

[0076] In certain exemplary embodiments, device 20 may further include or be coupled to a (internal or external) drive or port configured to receive and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software to be executed by processor 22 and / or device 20, and execute the methods shown in FIGS. 1-6 and 8.

[0077] In certain exemplary embodiments, device 20 may include or be coupled to one or more antennas 25 for transmitting and receiving signals and / or data between device 20. Device 20 may further include or be coupled to a transceiver 28 configured to transmit and receive information. The transceiver 28 may include, for example, a plurality of wireless interfaces that may be coupled to the antenna(s) 25. The wireless interface may be capable of corresponding to a plurality of wireless access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultra-wideband wireless communication (UWB), MulteFire, etc. The wireless interface may include components such as filters, converters (such as digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., which may generate symbols for transmission via one or more downlinks and receive symbols (e.g., via an uplink).

[0078] As such, the transceiver 28 can be configured to modulate information into a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of the apparatus 20. In other exemplary embodiments, the transceiver 18 can directly transmit and receive signals or data. Additionally or alternatively, in some exemplary embodiments, the apparatus 20 can include input and / or output devices (I / O devices).

[0079] In certain exemplary embodiments, the memory 24 can store software modules that, when executed by the processor 22, provide functionality. The modules can include, for example, an operating system that provides operating system functionality to the apparatus 20. The memory can also store one or more functional modules, such as applications or programs, to provide additional functionality to the apparatus 20. The components of the apparatus 20 can be implemented in hardware or as any suitable combination of hardware and software.

[0080] According to some exemplary embodiments, the processor 22 and the memory 24 may be included in or form part of a processing circuit or a control circuit. Further, in some exemplary embodiments, the transceiver 28 may be included in or form part of a transceiver circuit.

[0081] As used herein, the term "circuit" may refer to a hardware-only circuit implementation (e.g., analog and / or digital circuits) that uses software for operation but may not have software if not required for operation, a combination of a hardware circuit and software, a combination of an analog and / or digital hardware circuit and software / firmware, any portion of a hardware processor(s) (including a digital signal processor) having software that cooperates to perform various functions in a device (e.g., devices 10 and 20), and / or a hardware circuit(s) and / or processor(s) or a portion thereof. As a further example, as used herein, the term "circuit" may also include an embodiment of a single hardware circuit or processor (or multiple processors), or an embodiment of a portion of a hardware circuit or processor, along with the accompanying software and / or firmware. The term "circuit" may also include, for example, a baseband integrated circuit within a server, a cellular network node or device, or other computing or network device.

[0082] As noted above, in certain embodiments, device 20 may be a network element, node, host, or server within a communication network or providing such a network. For example, device 20 may be a satellite, base station, NodeB, evolved NodeB (eNB), 5G NodeB or access point, next generation NodeB (NG-NB or gNB), and / or a WLAN access point associated with a radio access network (RAN) such as an LTE network, 5G or NR. According to certain embodiments, device 20 may be controlled by memory 24 and processor 22 to perform functions related to any of the embodiments described herein.

[0083] As described above, according to certain exemplary embodiments, apparatus 20 may be, for example, a communication network. According to certain embodiments, apparatus 20 may be controlled by memory 14 and processor 12 to perform functions related to the exemplary embodiments described herein. For example, in certain exemplary embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to configure a user equipment to trigger a small data transmission (SDT) of SDT data to indicate the presence of non-SDT data. Also, apparatus 20 may be controlled by memory 24 and processor 22 to receive an SDT data transmission including SDT data. Further, apparatus 20 may be controlled by memory 24 and processor 22 to receive an indication from the user equipment indicating the presence of non-SDT data.

[0084] Further exemplary embodiments can provide means for performing any of the functions or procedures described herein. For example, certain exemplary embodiments can be directed to an apparatus including means for determining the availability of non-small data transmission (non-SDT) data. Also, the apparatus can include means for indicating the result of this determination to a network element.

[0085] Other exemplary embodiments can be directed to a further apparatus including means for configuring a user equipment to trigger an SDT of small data transmission (SDT) data to indicate the presence of non-SDT data. Also, the apparatus can include means for receiving an SDT data transmission having SDT data. Further, the apparatus can include means for receiving an indication from the user equipment indicating the presence of non-SDT data.

[0086] The specific exemplary embodiments described herein provide several technical improvements, enhancements, and / or advantages. In some exemplary embodiments, it may be possible to provide signaling extensions to handle cases where SDT data and non-SDT data coexist. Also, it may be possible to prevent extra delays from occurring whenever data is generated in combination with SDT-DRB data. Specific exemplary embodiments may provide means for a UE in the RRC_inactive state to handle cases where SDT and non-SDT data may coexist in the UE's buffer at the time SDT is initiated. In some examples, this processing can take into account the priority and type of data (e.g., depending on the type of application that generated the data, including not only non-smartphone applications such as sensors and smart meters but also smartphone applications).

[0087] A computer program product may include one or more computer-executable components configured to perform some exemplary embodiments when the program is executed. The one or more computer-executable components may be at least one software code or a portion thereof. Changes and configurations necessary to implement the functions of the exemplary embodiments may be implemented as added or updated software routines that may be executed as routines. The software routines may be downloaded to the device.

[0088] As an example, software or computer program code or a part thereof may be in source code form, object code form, or some intermediate form, and may be stored in some kind of carrier, distribution medium, or computer-readable medium, which can be any entity or device capable of carrying the program. Such carriers may include, for example, recording media, computer memories, read-only memories, optoelectronic and / or electrical carrier signals, electrical communication signals, and software distribution packages. Depending on the required processing power, the computer program may be executed on a single electronic digital computer or may be distributed among multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0089] In other exemplary embodiments, the functionality may be implemented by hardware or circuitry included in a device (e.g., device 10 or device 20) through the use of, for example, application-specific integrated circuits (ASICs), programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), or any other combination of hardware and software. In yet another exemplary embodiment, the functionality may be implemented as a signal, i.e., as a non-tangible means carried by an electromagnetic signal downloaded from the Internet or other network.

[0090] According to an exemplary embodiment, a device such as a node, device, or corresponding component may be configured as a circuit, computer, or microprocessor, such as a single-chip computer element, or as a chipset including a memory providing at least the storage capacity used for arithmetic operations and an arithmetic operation processor for executing arithmetic operations.

[0091] One skilled in the art can easily understand that the present invention described above can be implemented by procedures in different orders and / or by hardware elements having configurations different from the disclosed configurations. Therefore, although the present invention is described based on these exemplary embodiments, it is clear to those skilled in the art that specific modifications, variations, and alternative structures are obvious and, at the same time, remain within the scope of the exemplary embodiments. Although the above embodiments refer to 5G NR and LTE technologies, the above embodiments can also be applied to any other current or future 3GPP technologies, such as LTE-Advanced and / or Fourth Generation (4G) technologies.

[0092] Partial Glossary 5GS 5G System AMF Access and Mobility Management Function BSR Buffer Status Report CG Configured Grant CP Control Plane DRB Data Radio Bearer eNB Enhanced NodeB gNB 5G or Next Generation NodeB I-RNTI Inactive Radio Network Temporary Identifier LCG Logical Channel Group LCH Logical Channel LTE Long Term Evolution NCC nextHopChainingCount NG-RAN Next Generation - Radio Access Network NR New Radio NW Network PDU Protocol Data Unit PRACH Physical Random Access Channel RACH Random Access Channel RAN Radio Access Network RB Radio Bearer RNA RAN Notification Area RNAU RAN Notification Area Update RRC Radio Resource Control SDT Small Data Transmission UE User Equipment UP User Plane Xn Xn Network Interface

Claims

1. determining availability of non-small data transmission (non-SDT) data; indicating a result of said determining to a network element; and A method comprising:

2. Determining availability of small data transmission (SDT) data; triggering an SDT procedure when the SDT data is determined to be available; The method of claim 1 further comprising:

3. The method of claim 2 , wherein the determining the availability of the non-SDT data is performed while the SDT procedure is in progress or at the start of the SDT procedure.

4. The method according to any one of claims 1 to 3, further comprising triggering a connection resumption procedure when the non-SDT data is determined to be available.

5. The method of any of claims 1 to 4, further comprising: performing SDT on said network elements using said SDT data.

6. determining whether the non-SDT data is available while the SDT procedure is in progress includes determining that the non-SDT data is available; and indicating the result of the determining to the network element includes indicating the presence of the non-SDT data. The method according to any of claims 2 to 5, wherein the presence of said non-SDT data is indicated during said SDT procedure.

7. The indicating to the network element the result of the determining is performed via one of a Buffer Status Report (BSR), a new Medium Access Control control element, a Service Data Adaptation Protocol control protocol data unit, a Packet Data Convergence Protocol control protocol data unit, a Radio Link Control control protocol data unit, or a Connection Resume message; The method according to any one of claims 2 to 6, wherein the indication via the BSR is transmitted in the SDT procedure.

8. The indicating to the network element of the result of the determining is performed by transmitting a new Radio Resource Control (RRC) message; The method according to any of claims 2 to 6, wherein when the SDT procedure is triggered, the new RRC message is multiplexed with the SDT data.

9. and indicating the result of the determining to the network element includes indicating the presence of the SDT data and the non-SDT data. The method according to any of claims 2 to 8, wherein the presence of the SDT data and the non-SDT data is indicated in BSR information.

10. The method of any of claims 2 to 9, further comprising buffering the SDT data and the non-SDT data.

11. If the non-SDT data is available, the method further comprises: The method according to any of claims 2 to 10, further comprising aborting the SDT procedure and triggering the connection resumption procedure.

12. The method of claim 11 , wherein the aborting is based on a priority of the SDT data or whether the SDT data has already been transmitted.

13. If the non-SDT data is available, the method further comprises: The method of any of claims 2 to 12, further comprising buffering the non-SDT data while the SDT procedure is in progress.

14. After the SDT procedure is completed, the method further comprises: The method of claim 13 , further comprising triggering a connection resumption procedure for the non-SDT data transmission.

15. buffering the SDT data and the non-SDT data; initiating the SDT procedure while the non-SDT data is buffered; The method of any one of claims 2 to 14, further comprising:

16. 16. The method of claim 15, further comprising transmitting the SDT data to the network element while the non-SDT data is buffered.

17. configuring a user equipment to trigger a small data transmission (SDT) for SDT data and to indicate the presence of non-SDT data; receiving an SDT data transmission including the SDT data; receiving an indication from the user equipment indicating the presence of the non-SDT data; A method comprising:

18. 20. The method of claim 17, wherein the configuration of the user equipment is performed via a Radio Resource Control (RRC) message.

19. 20. The method of claim 18, wherein the RRC message triggers the user equipment to transition from an RRC connected state to an RRC inactive state.

20. The indication of the presence of the non-SDT data may further comprise: Buffer Status Report (BSR), New medium access control control elements, Service Data Adaptation Protocol Control Protocol Data Unit, Packet Data Convergence Protocol Control Protocol Data Unit, a radio link control control protocol data unit, or Connection resumed message, , The method according to any of claims 17 to 19, wherein the indication via the BSR is received in an SDT procedure.

21. A method according to any of claims 17 to 20, wherein configuring the user equipment comprises configuring the user equipment as to which indications relating to the presence of the non-SDT data to report and when or whether to trigger such reporting.

22. The method according to any of claims 17 to 21, further comprising configuring the user equipment to initiate an SDT to transmit allowed uplink SDT data.

23. Configuring the user equipment includes: configuring the user equipment not to transmit the indication of the non-SDT data; configuring the user equipment to transmit an indication of the subset of non-SDT data; configuring the user equipment to cancel or postpone an ongoing trigger to resume an RRC connection whenever a trigger to initiate SDT is met; configuring said user equipment with SDT data authorized for SDT; or configuring the user equipment to abort the SDT if both the SDT data and the non-SDT data are present; The method according to any one of claims 17 to 22, comprising one or more of the following:

24. At least one processor; at least one memory having computer program code; An apparatus comprising: The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: determining availability of non-small data transmission (non-SDT) data; indicating a result of said determining to a network element; and The apparatus is configured to cause

25. The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: Determining availability of small data transmission (SDT) data; triggering an SDT procedure when the SDT data is determined to be available; 25. The apparatus of claim 24, further configured to:

26. 26. The apparatus of claim 25, wherein the determining the availability of the non-SDT data is performed while the SDT procedure is in progress or at the start of the SDT procedure.

27. The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: The apparatus according to any of claims 24 to 26, further configured to trigger a connection resumption procedure when the non-SDT data is determined to be available.

28. The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: An apparatus according to any of claims 24 to 27, further configured to cause the network element to perform SDT using the SDT data.

29. When determining whether non-SDT data is available while the SDT procedure is in progress, the at least one memory and the computer program code are further configured to cause the device, using the at least one processor, to at least determine that the non-SDT data is available; When indicating the result of the determination to the network element, the at least one memory and the computer program code are further configured to cause the device, using the at least one processor, to at least indicate the presence of the non-SDT data; An apparatus according to any of claims 25 to 26, wherein the presence of said non-SDT data is indicated during said SDT procedure.

30. The indicating of the result of the determination to the network element is performed via one of a Buffer Status Report (BSR), a new Medium Access Control control element, a Service Data Adaptation Protocol control protocol data unit, a Packet Data Convergence Protocol control protocol data unit, a Radio Link Control control protocol data unit, or a Connection Resume message; The device according to any one of claims 25 to 29, wherein the indication via the BSR is transmitted in the SDT procedure.

31. Indicating the result of the determination to the network element is performed by transmitting a new Radio Resource Control (RRC) message; The apparatus according to any one of claims 25 to 29, wherein when the SDT procedure is triggered, the new RRC message is multiplexed with the SDT data.

32. When indicating the result of the determination to the network element, the at least one memory and the computer program code are further configured to cause the device, using the at least one processor, to at least indicate the presence of the SDT data and the non-SDT data; The apparatus according to any of claims 25 to 31, wherein the presence of the SDT data and the non-SDT data is indicated in BSR information.

33. The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: An apparatus according to any of claims 25 to 32, further configured to cause buffering of the SDT data and the non-SDT data.

34. If the non-SDT data is available, the at least one memory and the computer program code, using the at least one processor, cause the device to at least: The apparatus of any of claims 25 to 33, further configured to abort the SDT procedure and to trigger the connection resumption procedure.

35. 35. The apparatus of claim 34, wherein the aborting is based on a priority of the SDT data or whether the SDT data has already been transmitted.

36. If the non-SDT data is available, the at least one memory and the computer program code, using the at least one processor, cause the device to at least: An apparatus according to any of claims 25 to 35, further configured to cause buffering of said non-SDT data whilst said SDT procedure is in progress.

37. After the SDT procedure is completed, the at least one memory and the computer program code, using the at least one processor, cause the device to at least:

37. The apparatus of claim 36, further configured to trigger a connection resumption procedure for the non-SDT data transmission.

38. The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: buffering the SDT data and the non-SDT data; initiating the SDT procedure while the non-SDT data is buffered; The apparatus of any of claims 25 to 37, further configured to:

39. 40. The apparatus of claim 38, wherein the at least one memory and the computer program code are further configured to, using the at least one processor, cause the apparatus to at least transmit the SDT data to the network element while the non-SDT data is buffered.

40. At least one processor; at least one memory having computer program code; An apparatus comprising: The at least one memory and the computer program code are configured to cause the device, using the at least one processor, to at least: configuring a user equipment to trigger a small data transmission (SDT) for SDT data and to indicate the presence of non-SDT data; receiving an SDT data transmission including the SDT data; receiving an indication from the user equipment indicating the presence of the non-SDT data; The apparatus is configured to cause

41. 41. The apparatus of claim 40, wherein the configuration of the user equipment is performed via a radio resource control (RRC) message.

42. 42. The apparatus of claim 41, wherein the RRC message triggers the user equipment to transition from an RRC connected state to an RRC inactive state.

43. The indication of the presence of the non-SDT data comprises: Buffer Status Report (BSR), New medium access control control elements, Service Data Adaptation Protocol Control Protocol Data Unit, Packet Data Convergence Protocol Control Protocol Data Unit, a radio link control control protocol data unit, or Connection resumed message, , The apparatus according to any one of claims 40 to 42, wherein the indication via the BSR is received in an SDT procedure.

44. An apparatus as described in any one of claims 40 to 43, wherein when configuring the user equipment, the at least one memory and the computer program code are further configured to cause the apparatus, using the at least one processor, to configure the user equipment at least as to which indications related to the presence of the non-SDT data to report and when or whether to trigger such reporting.

45. The apparatus of any one of claims 40 to 44, wherein the at least one memory and the computer program code are further configured to cause the apparatus, using the at least one processor, to at least configure the user equipment to initiate an SDT to transmit authorized uplink SDT data.

46. The configuration of the user equipment comprises: configuring the user equipment not to transmit the indication of the non-SDT data; configuring the user equipment to transmit the indication of the subset of non-SDT data; configuring the user equipment to cancel or postpone an ongoing trigger to resume an RRC connection whenever a trigger to initiate SDT is met; configuring said user equipment with SDT data authorized for SDT; or configuring the user equipment to abort the SDT if both the SDT data and the non-SDT data are present; 46. ​​Apparatus according to any one of claims 40 to 45, comprising one or more of:

47. means for determining availability of non-small data transmission (non-SDT) data; means for indicating a result of said determining to a network element; 13. An apparatus comprising:

48. means for determining availability of small data transmission (SDT) data; means for triggering an SDT procedure when the SDT data is determined to be available; 48. The apparatus of claim 47, further comprising:

49. 49. The apparatus of claim 48, wherein the determining the availability of the non-SDT data is performed while the SDT procedure is in progress or at the start of the SDT procedure.

50. The apparatus according to any of claims 47 to 49, further comprising means for triggering a connection resumption procedure when said non-SDT data is determined to be available.

51. An apparatus according to any of claims 47 to 50, further comprising means for performing SDT on said network element using said SDT data.

52. said means for determining whether said non-SDT data is available while said SDT procedure is in progress comprises means for determining that said non-SDT data is available; the means for indicating the result of the determining to the network element includes means for indicating the presence of the non-SDT data; Apparatus according to any of claims 48 to 51, wherein the presence of said non-SDT data is indicated during said SDT procedure.

53. The indicating to the network element the result of the determining is performed via one of a Buffer Status Report (BSR), a new Medium Access Control control element, a Service Data Adaptation Protocol control protocol data unit, a Packet Data Convergence Protocol control protocol data unit, a Radio Link Control control protocol data unit, or a Connection Resume message; The device according to any one of claims 48 to 52, wherein the indication via the BSR is transmitted in the SDT procedure.

54. The indicating to the network element of the result of the determining is performed by transmitting a new Radio Resource Control (RRC) message; The apparatus according to any of claims 48 to 52, wherein when the SDT procedure is triggered, the new RRC message is multiplexed with the SDT data.

55. the means for indicating the result of the determining to the network element includes means for indicating the presence of the SDT data and the non-SDT data; An apparatus according to any of claims 48 to 54, wherein the presence of the SDT data and the non-SDT data is indicated in BSR information.

56. Apparatus according to any of claims 48 to 55, further comprising means for buffering said SDT data and said non-SDT data.

57. If the non-SDT data is available, the device: The apparatus according to any of claims 48 to 56, further comprising: means for aborting said SDT procedure; and means for triggering said connection resumption procedure.

58. 58. The apparatus of claim 57, wherein the aborting is based on a priority of the SDT data or whether the SDT data has already been transmitted.

59. If the non-SDT data is available, the device: Apparatus according to any of claims 48 to 58, further comprising means for buffering said non-SDT data whilst said SDT procedure is in progress.

60. After the SDT procedure is completed, the device:

60. The apparatus of claim 59, further comprising: means for triggering a connection resumption procedure for the non-SDT data transmission.

61. means for buffering the SDT data and the non-SDT data; means for initiating the SDT procedure while the non-SDT data is buffered; 61. The apparatus of any of claims 48 to 60, further comprising:

62. 62. The apparatus of claim 61, further comprising: means for transmitting the SDT data to the network element while the non-SDT data is buffered.

63. means for configuring a user equipment to trigger small data transmission (SDT) data and to indicate the presence of non-SDT data; means for receiving an SDT data transmission including the SDT data; means for receiving an indication from the user equipment indicating the presence of the non-SDT data; 13. An apparatus comprising:

64. 64. The apparatus of claim 63, wherein the configuration of the user equipment is performed via a radio resource control (RRC) message.

65. 65. The apparatus of claim 64, wherein the RRC message triggers the user equipment to transition from an RRC connected state to an RRC inactive state.

66. The indication of the presence of the non-SDT data comprises: Buffer Status Report (BSR), New medium access control control elements, Service Data Adaptation Protocol Control Protocol Data Unit, Packet Data Convergence Protocol Control Protocol Data Unit, a radio link control control protocol data unit, or Connection resumed message, , The apparatus according to any one of claims 63 to 65, wherein the indication via the BSR is received in an SDT procedure.

67. An apparatus as claimed in any of claims 63 to 66, wherein the means for configuring the user equipment comprises means for configuring the user equipment as to which indications relating to the presence of the non-SDT data to report and when or whether to trigger such reporting.

68. An apparatus according to any of claims 63 to 67, further comprising means for configuring the user equipment to initiate an SDT to transmit permitted uplink SDT data.

69. The means for configuring the user equipment further comprises: means for configuring the user equipment not to transmit the indication of the non-SDT data; means for configuring the user equipment to transmit an indication of the subset of non-SDT data; means for configuring said user equipment to cancel or postpone an ongoing trigger to resume an RRC connection whenever a trigger to initiate SDT is met; means for configuring said user equipment with SDT data authorized for SDT; or means for configuring said user equipment to abort said SDT if both said SDT data and said non-SDT data are present; 69. Apparatus according to any of claims 63 to 68, comprising one or more of:

70. A non-transitory computer readable medium comprising program instructions stored thereon for carrying out the method of any of claims 1 to 23.

71. Apparatus comprising circuitry configured to cause said apparatus to carry out a process according to any preceding claim.

Images