Processing of mobile terminated small data transmission bearers

Abstract

Embodiments of the present disclosure relate to a device, method, apparatus, and computer-readable storage medium for bearer processing in Mobile Terminated Small Data Transmission (MT-SDT), including determining that data not belonging to an MT-SDT bearer is available during an MT-SDT procedure or that data belonging to an MT-SDT bearer is available during a Mobile Originated Small Data Transmission (MO-SDT) procedure, and, based on the determination, performing at least one of sending a notification indicating the presence of the data to a network device, resuming a non-MT-SDT bearer during the MT-SDT procedure, resuming an MT-SDT bearer during the MO-SDT procedure, transmitting data not belonging to an MT-SDT bearer after the MT-SDT procedure is completed, or transmitting data belonging to an MT-SDT bearer after the MO-SDT procedure is completed.

Description

[Technical Field]

[0001] FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to a device, method, apparatus, and computer-readable storage medium for processing Mobile Terminated Small Data Transmission (MT-SDT) bearers. [Background technology]

[0002] Small Data Transmission (SDT) is a procedure that enables data and / or signaling transmission while remaining in a Radio Resource Control (RRC) non-connected state, i.e., an RRC_INACTIVE state, without transitioning to an RRC connected state (i.e., an RRC_CONNECTED state). Summary of the Invention

[0003] Generally, embodiments of the present disclosure provide a solution for handling MT-SDT bearers.

[0004] In a first aspect, an apparatus is provided comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: determine that data not belonging to a Mobile Terminated Small Data Transmission (MT-SDT) bearer is available during a Mobile Oriented Small Data Transmission (MO-SDT) procedure or that data belonging to a MT-SDT bearer is available during a Mobile Oriented Small Data Transmission (MO-SDT) procedure, and based on the determining, send a notification to a network device indicating the presence of the data, or resume a non-MT-SDT bearer during the MT-SDT procedure, or resume an MT-SDT bearer during the MO-SDT procedure, or transmit data not belonging to a MT-SDT bearer after the MT-SDT procedure is completed, or transmit data belonging to a MT-SDT bearer after the MO-SDT procedure is completed.

[0005] In a second aspect, an apparatus is provided comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to receive at least one of: a notification indicating the presence of data not belonging to an MT-SDT bearer available during an MT-SDT procedure, a notification indicating the presence of data belonging to an MT-SDT bearer available during an MO-SDT procedure, or data not belonging to an MT-SDT bearer after an MT-SDT procedure is completed, or data belonging to an MT-SDT bearer after an MO-SDT procedure is completed.

[0006] In a third aspect, a method is provided, the method including: determining, in a terminal device, that data not belonging to an MT-SDT bearer is available during an MT-SDT procedure or that data belonging to an MT-SDT bearer is available during an MO-SDT procedure, and based on the determining, performing at least one of: sending a notification of the presence of the data to a network device, or resuming the non-MT-SDT bearer during the MT-SDT procedure, or resuming the MT-SDT bearer during the MO-SDT procedure, or transmitting the data not belonging to the MT-SDT bearer after the MT-SDT procedure is completed, or transmitting the data belonging to the MT-SDT bearer after the MO-SDT procedure is completed.

[0007] In a fourth aspect, there is provided a method, the method including receiving, in a network device, from a terminal device at least one of a notification indicating the presence of data not belonging to an MT-SDT bearer during an MT-SDT procedure, a notification indicating the presence of data belonging to an MT-SDT bearer during an MO-SDT procedure, or data not belonging to an MT-SDT bearer after an MT-SDT procedure is completed, or data belonging to an MT-SDT bearer after an MO-SDT procedure is completed.

[0008] In a fifth aspect, there is provided an apparatus including: means for determining that data not belonging to an MT-SDT bearer is available during an MT-SDT procedure, or that data belonging to an MT-SDT bearer is available during an MO-SDT procedure; and based on the determination, performing at least one of: sending a notification to a network device indicating the presence of data; or resuming a non-MT-SDT bearer during the MT-SDT procedure; or resuming an MT-SDT bearer during the MO-SDT procedure; or transmitting data not belonging to an MT-SDT bearer after the MT-SDT procedure is completed; or transmitting data belonging to an MT-SDT bearer after the MO-SDT procedure is completed.

[0009] In a sixth aspect, there is provided an apparatus comprising: means for receiving from a terminal device at least one of: an indication of the presence of data not belonging to an MT-SDT bearer available during an MT-SDT procedure; or an indication indicating the presence of data belonging to an MT-SDT bearer available during an MO-SDT procedure; or data not belonging to an MT-SDT bearer after an MT-SDT procedure has been completed;

[0010] In a seventh aspect, there is provided a computer readable medium having recorded thereon a computer program which, when executed by at least one processor of an apparatus, causes the apparatus to perform a method according to the third or fourth aspect.

[0011] Other features and advantages of the disclosed embodiments will become apparent from the following description of specific embodiments, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the disclosed embodiments. [Brief explanation of the drawings]

[0012] The embodiments herein are given by way of example, the advantages of which will be explained in more detail below with reference to the accompanying drawings. [Figure 1] FIG. 1 illustrates an example environment in which embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 is a signaling chart illustrating an example process according to some embodiments of the present disclosure. [Figure 3] FIG. 3 is a flowchart illustrating an example method for processing MT-SDT bearers according to some embodiments of the present disclosure. [Figure 4] FIG. 4 is a flowchart illustrating an example method for processing MT-SDT bearers according to some embodiments of the present disclosure. [Figure 5] FIG. 5 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure. [Figure 6]6 is a block diagram illustrating an example of a computer-readable medium according to an embodiment of the present disclosure.Throughout the drawings, the same or similar reference numbers may refer to the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0013] The principles of the present invention will now be described with reference to several examples. These examples are not intended to limit the scope of the present invention, but are provided for illustrative purposes only to aid those skilled in the art in understanding and practicing the present invention. The examples described herein may be implemented in a variety of ways other than those described below.

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

[0015] References herein to "one embodiment," "embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one skilled in the art to affect that feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0016] Although terms such as "first" and "second" may be used to describe various elements, these elements are not limited by these terms. These terms are merely used to distinguish between elements. For example, calling a first element a second element, and similarly calling a second element a first element, would not depart from the scope of the embodiments. As used herein, the term "and / or" encompasses any combination of one or more of the listed terms.

[0017] As used herein, "at least one of: " and "a list of at least one or more elements" and similar expressions, when a list of two or more elements is connected by "and" or "or," means at least any one element, at least two or more elements, or at least all elements.

[0018] In this specification, unless expressly stated otherwise, performing a step "in response to A" does not necessarily indicate that the step is performed immediately after the occurrence of "A," but may include one or more steps therebetween.

[0019] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Furthermore, as used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0020] In this application, the term "circuit" means (a) hardware-only circuit implementation (e.g., implementation using only analog and / or digital circuitry); (b) A combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) A combination of a portion of a hardware processor and software (including a digital signal processor), software, and memory that work together to cause a device, such as a mobile phone or server, to perform various functions; (c) hardware circuitry and / or processors (e.g., microprocessors or portions of microprocessors) that require software (e.g., firmware) to operate, provided that the software may be absent if not necessary for operation; It may refer to any one or more, or all of the above.

[0021] This definition of circuit applies to all uses of the term in this application, i.e., in all claims. By way of further example, the term circuit as used herein encompasses a simple hardware circuit or processor (or processors), or a portion of a hardware circuit or processor and its associated software and / or firmware implementation. The term circuit also encompasses, for example, baseband or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular networks, and other computing systems, where applicable to particular claim elements.

[0022] As used herein, the term "communication network" refers to a network conforming to any appropriate communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), or Enhanced Machine Type Communications (eMTC). Furthermore, communications between terminal devices and network devices within the communication network may be performed using, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, as well as other protocols currently known or developed in the future. Embodiments of the present disclosure are applicable to various communication systems. Given the rapid development of communication technologies, future communication technologies and systems may also embody the present disclosure. The scope of the present disclosure is not limited to the aforementioned systems.

[0023] As used herein, the terms "network device," "radio network device," and / or "radio access network device" refer to a node in a communication network through which a terminal device accesses the network and receives services therefrom. A network device may refer to, for example, a base station (BS) or access point (AP), a Node B (Node B or NB), an evolved Node B (eNodeB or eNB), a NR Node B (also known as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a repeater, an integrated access backhaul (IAB) node, a low-power node such as a femto or pico node, a non-terrestrial network (NTN) or non-terrestrial network device such as a satellite network device, a low Earth orbit (LEO) satellite, a geostationary Earth orbit (GEO) satellite, or an airborne network device. This varies depending on the terminology and technology applied. In some embodiments, a low Earth orbit radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU). In other embodiments, part or all of the radio access network may be mounted on an airborne or spaceborne non-terrestrial network (NTN) vehicle.

[0024] The term "terminal equipment" refers to any end device capable of wireless communication. By way of example only, terminal equipment may also be referred to as communications equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal equipment includes mobile phones, mobile phone terminals, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminals, PDAs, portable computers, desktop computers, digital cameras and other imaging terminals, gaming terminals, music storage and playback devices, in-vehicle wireless terminals, 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 and other wearables, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. A terminal device may correspond to a mobile terminal (MT) 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.

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

[0026] 1 illustrates an example of a communication network 100 in which an embodiment of the present disclosure may be implemented. As shown in FIG. 1, the communication network 100 may include a terminal device 110. Hereinafter, the terminal device 110 may also be referred to as a UE.

[0027] The communication network 100 may further include a network device 120. Hereinafter, the network device 120 may also be referred to as a gNB or an eNB. The terminal device 110 may communicate with the network device 120.

[0028] 1 is for illustrative purposes only and is not intended to be limiting in any way. Communications network 100 may include any suitable number of network devices and terminal devices.

[0029] In some embodiments, the link from network device 120 to terminal device 110 may be referred to as the downlink (DL), and the link from terminal device 110 to network device 120 may be referred to as the uplink (UL). In the DL, network device 120 is the transmit (TX) device (or transmitter) and terminal device 110 is the receive (RX) device (or receiver). In the UL, terminal device 110 is the TX device (or transmitter) and network device 120 is the RX device (or receiver).

[0030] Communications in the communication environment 100 may be implemented according to 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 Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols now known or developed in the future. Furthermore, communications may utilize any suitable wireless communication technology, including, but not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and other technologies now known or developed in the future.

[0031] As mentioned above, the SDT procedure can perform data and / or signaling transmissions while remaining in the RRC_INACTIVE state.

[0032] SDT is enabled per radio bearer and initiated only by the terminal device. The conditions for SDT are that all SDT-enabled radio bearers have uplink (UL) data waiting for transmission below a configured value, downlink (DL) reference signal received power (RSRP) above a configured threshold, and valid SDT resources are available. The maximum duration of the SDT procedure may depend on the SDT failure detection timer configured by the network.

[0033] The SDT procedure is initiated either by transmission over the Random Access Channel (RACH) (configured in the system information) or via Type 1 Configuration Grant (CG) resources (configured in dedicated signaling of RRCRelease).

[0034] If data appears in the buffer of a radio bearer for which SDT is not enabled while an SDT procedure is in progress, the terminal device shall send a non-SDT data arrival notification to the network using a UEAssistanceInformation message and may include a resume cause, if available.

[0035] The SDT procedure over CG resources can only be initiated if there is valid UL timing adjustment. The UL timing adjustment is maintained by the terminal based on the SDT-specific timing adjustment timer configured by the network through dedicated signaling, and also by the DL RSRP of the configured number of highest-ranked synchronization signal blocks (SSBs) that exceed the configured RSRP threshold for the initial CG-SDT transmission.

[0036] Additionally, a work item on MT-SDT was discussed and developed. MT-SDT is data belonging to bearers configured for SDT. The network can trigger MT-SDT only if the data belongs to those bearers.

[0037] It is beneficial to allow the establishment of different radio bearers for Mobile Originated SDT (MO-SDT) and MT-SDT, since different resources may be used for MO-SDT and MT-SDT. In addition, MO-SDT and MT-SDT data may have different QoS requirements. In general, the network may not want to allow a terminal device to initiate MO-SDT for a particular Data Radio Bearer (DRB) that has been configured for MT-SDT. Similarly, the network may not want to allow a terminal device to initiate data transmission on a particular MO-SDT bearer while an MT-SDT procedure is running, as this situation may cause excessive load on the SDT procedure.

[0038] However, if the network equipment configures different radio bearers for MO-SDT and MT-SDT, further consideration is required regarding the behavior of the terminal device when uplink data belonging to an MO-SDT bearer becomes available for transmission while an MT-SDT procedure is in progress.

[0039] The solution of the present disclosure proposes a mechanism for bearer processing. In this solution, the terminal device 110 can notify that data not belonging to an MT-SDT bearer is available during an MT-SDT procedure, or that data belonging to an MT-SDT bearer is available during an MO-SDT procedure. Alternatively, the terminal device 110 may resume a non-MT-SDT bearer while an MT-SDT procedure is running, or resume an MO-SDT bearer while an MT-SDT procedure is running.

[0040] In this way, the behavior of the terminal device with regard to the handling of uplink data that does not belong to an MT-SDT bearer (e.g., an MO-SDT bearer) that is made available for transmission during the MT-SDT procedure can be defined.

[0041] The embodiments of the present specification will be described in detail with reference to the accompanying drawings.

[0042] Referring to Figure 2, Figure 2 illustrates a signaling chart 200 for communication in accordance with some embodiments of the present disclosure. As shown in Figure 2, signaling chart 200 includes terminal device 110 and network device 120. For purposes of explanation, signaling chart 200 will be described with reference to Figure 1.

[0043] During an MT-SDT procedure, the terminal device 110 may have data that does not belong to an MT-SDT bearer available for transmission. Similarly, during an MO-SDT procedure, the terminal device 110 may have data that belongs to an MT-SDT bearer available for transmission.

[0044] The embodiments herein will be described below using a scenario in which data not belonging to an MT-SDT bearer is available for transmission while an MT-SDT procedure is in progress, it being understood that similar mechanisms and solutions are applicable to scenarios in which data belonging to an MT-SDT bearer is available for transmission while an MO-SDT procedure is in progress.

[0045] If, during an MT-SDT procedure, data not belonging to an MT-SDT bearer is available for transmission, the terminal device 110 notifies the network device 120 that data not belonging to an MT-SDT bearer is available for transmission (204). It should be understood that non-MT-SDT bearers in this context include MO-SDT bearers.

[0046] If data belonging to the MT-SDT bearer becomes available for transmission during the period in which the MO-SDT procedure is being performed, the terminal device 110 notifies the network device 120 that data belonging to the MT-SDT bearer is available for transmission (204).

[0047] Alternatively, the terminal device 110 may notify the network device 120 that data not belonging to an MT-SDT bearer has resumed. Optionally, the terminal device 110 may also notify the network device 120 that data not belonging to an MT-SDT bearer has resumed together with the notification that data not belonging to an MT-SDT bearer is available for transmission. As another option, the terminal device 110 may notify the network device 120 that data not belonging to an MT-SDT bearer has resumed and that data not belonging to an MT-SDT bearer is available for transmission in separate notifications.

[0048] In some embodiments, the indication of the resumption of data not belonging to an MT-SDT bearer and / or the indication of data not belonging to an MT-SDT bearer available for transmission can be included in a Buffer Status Report (BSR). In other embodiments, the indication of the resumption of data not belonging to an MT-SDT bearer and / or the indication of data not belonging to an MT-SDT bearer available for transmission can also be included in RRC signaling, for example in an assistance information message, i.e., a "UEAssistanceInformation" message.

[0049] The Assistance Information message may contain a new restart cause for the arrival of non-MT-SDT or MO-SDT data or MT-SDT. Another option is to introduce a new indication in the Assistance Information message indicating non-MT-SDT or MO-SDT data or MT-SDT.

[0050] Furthermore, if data not belonging to an MT-SDT bearer becomes available for transmission while the MT-SDT procedure is in progress, the terminal device 110 resumes (206) the availability of data not belonging to an MT-SDT bearer for transmission. Specifically, the terminal device 110 can resume a non-MT-SDT bearer or an MO-SDT bearer through which uplink data is available for transmission.

[0051] Furthermore, if data belonging to an MT-SDT bearer becomes available for transmission while the MO-SDT procedure is in progress, the terminal device 110 resumes the availability of data belonging to the MT-SDT bearer for transmission (206). Specifically, the terminal device 110 may resume the MT-SDT bearer for which uplink data is available for transmission.

[0052] In this case, it should be understood that after a non-MT-SDT or MO-SDT bearer is resumed by the terminal device 120, a notification indicating the resumption of data not belonging to the MT-SDT bearer is sent from the terminal device 110 to the network device 120 (208), as described above.

[0053] In this case, it should be understood that after the terminal device 120 resumes the MT-SDT bearer, a notification is sent from the terminal device 110 to the network device 120 that the data belonging to the MT-SDT bearer has resumed (208), as described above.

[0054] In some embodiments, the terminal device 110 may transmit 210 data that does not belong to an MT-SDT or MO-SDT bearer to the network device 120 even when an MT-SDT procedure is running.

[0055] In some embodiments, the terminal device 110 may transmit 210 data belonging to an MT-SDT bearer from the network device 120 even while an MO-SDT procedure is running.

[0056] Another option is for the terminal device 110 to transmit (210) data that does not belong to the MT-SDT or MO-SDT bearer to the network device 120 after the MT-SDT procedure is completed. For example, whether an MT-SDT procedure is running may depend on an MT-SDT timer (e.g., t319a timer). That is, the MT-SDT procedure is completed when the MT-SDT timer expires.

[0057] Another option is for the terminal device 110 to transmit (210) data belonging to the MT-SDT bearer from the network device 120 after the MO-SDT procedure has been completed.

[0058] In some embodiments, the network device 120 allows or configures the terminal device 110 to send a notification indicating that data belonging to an MO-SDT bearer or a non-MT-SDT bearer is available for transmission.

[0059] Furthermore, the network device 120 may allow or configure the terminal device 110 to resume or transmit data that does not belong to an MT-SDT or MO-SDT bearer during the MT-SDT procedure.

[0060] Furthermore, the network device 120 allows or configures the terminal device 110 to resume or transmit data belonging to the MT-SDT bearer during the MO-SDT procedure.

[0061] The terminal device 110 sends a notification indicating that data not belonging to an MT-SDT bearer is available for transmission, or a configuration to resume or transmit data not belonging to an MT-SDT or MO-SDT bearer during an MT-SDT procedure is sent (202) from the network device 120 to the terminal device 110, for example, before or during the MT-SDT procedure.

[0062] The configuration for the terminal device 110 to send a notification indicating that data belonging to an MT-SDT bearer is available for transmission, or to resume or transmit data belonging to an MT-SDT bearer during an MO-SDT procedure, may be transmitted (202) from the network device 120 to the terminal device 110, for example, before or during the MO-SDT procedure.

[0063] It should be understood that the configuration for the terminal device 110 to resume or transmit data not belonging to an MT-SDT bearer or data belonging to an MO-SDT bearer during an MT-SDT procedure may be transmitted from the network device 120 to the terminal device 110 after the network device 120 receives a notification from the terminal device 110 indicating that data belonging to an MO-SDT bearer is available for transmission.

[0064] It should be understood that the configuration for the terminal device 110 to resume or transmit data belonging to the MT-SDT bearer during the MO-SDT procedure may be transmitted from the network device 120 to the terminal device 110 after the network device 120 receives a notification from the terminal device 110 indicating that data belonging to the MT-SDT bearer is available for transmission.

[0065] For example, this configuration may be sent from network device 120 to terminal device 110 via a paging message or RRC signaling.

[0066] As another option, the configuration may be sent from the network device 120 to the terminal device 110 via a Medium Access Control (MAC) Control Element (CE).

[0067] If the configuration is sent via the MAC CE, the MAC CE may include a header indicating that one or more configured non-MT-SDT, MO-SDT, or MT-SDT bearers are to be resumed. Optionally, the MAC CE may indicate the respective bearers corresponding to one or more logical channel identifiers to be resumed. That is, there is a mapping between each bearer and one or more logical channels. Furthermore, the MAC layer may notify the RRC layer to resume at least one of the non-MT-SDT / MO-SDT / MT-SDT bearers.

[0068] In this solution, bearers configured for non-MT-SDT, MO-SDT and / or MT-SDT may be referred to as Signaling Radio Bearers (SRBs) and / or DRBs.

[0069] In this way, the behavior of the terminal device for processing uplink data that does not belong to an MT-SDT bearer (eg an MO-SDT bearer) that is made available for transmission during an MT-SDT procedure can be defined.

[0070] 3 illustrates a flowchart of an example method 300 of MT-SDT bearer processing according to some embodiments of the present disclosure. Method 300 may be performed in terminal device 110 shown in FIG. 1. For illustrative purposes, method 300 will be described with reference to FIG. 1.

[0071] In step 310, the terminal device 110 determines whether data not belonging to an MT-SDT bearer is available for transmission during the MT-SDT bearer period, or whether data belonging to an MT-SDT bearer is available for transmission during the MO-SDT procedure ().

[0072] In step 320, based on the above determination, the terminal device 110 performs at least one of the following: sending a notification to the network device that data not belonging to the MT-SDT bearer is available for transmission during the MT-SDT bearer period, or sending a notification that data belonging to the MT-SDT bearer is available for transmission during the MO-SDT procedure; resuming the non-MT-SDT bearer during the MT-SDT procedure, or resuming the MT-SDT bearer during the MO-SDT procedure; sending data not belonging to the MT-SDT bearer after the MT-SDT procedure is completed, or sending data belonging to the MT-SDT bearer after the MO-SDT procedure is completed.

[0073] In some embodiments, the data not belonging to an MT-SDT bearer further includes data belonging to an MO-SDT bearer.

[0074] In some embodiments, the terminal device may also receive notification or resumption related settings from the network device.

[0075] In some embodiments, the configuration indicates at least one of: that the device is permitted to send notifications; that an MO-SDT configured bearer is permitted to be resumed during an MT-SDT procedure; that an MT-SDT configured bearer is permitted to be resumed during an MO-SDT procedure; that the device is permitted to resume an MO-SDT bearer during an MT-SDT procedure or to send data not belonging to MT-SDT or an MO-SDT bearer; that the device is permitted to resume an MT-SDT bearer during an MO-SDT procedure or to send data belonging to MT-SDT.

[0076] In some embodiments, the configuration is received via at least one of a paging message, a MAC CE, or RRC signaling.

[0077] In some embodiments, the configuration is signaled by at least one of including a header indicating that the MAC CE will resume one or more configured MO-SDT or MT-SDT bearers and the MAC CE indicating the respective bearers corresponding to one or more logical channel identifiers to be resumed.

[0078] In some embodiments, the terminal device may notify the RRC layer from the MAC layer to resume at least one of the MO-SDT or MT-SDT bearers.

[0079] In some embodiments, the notification further indicates that the MO-SDT bearer or the MT-SDT bearer is resumed.

[0080] In some embodiments, this notification is included in BSR or RRC signaling, for example in an assistance information message.

[0081] In some embodiments, this notification is included in an aiding information message containing a new cause for resumption of MO-SDT or MT-SDT data arrival or a new notification of MO-SDT or MT-SDT data.

[0082] 4 illustrates a flowchart of an example method 400 of MT-SDT bearer processing according to some embodiments of the present disclosure. Method 400 may be implemented in network device 120 shown in FIG. 1. For illustrative purposes, method 400 will be described with reference to FIG. 1.

[0083] In step 410, the network device 120 receives from the terminal device 110 at least one of a notification that data not belonging to an MT-SDT bearer is available for transmission during the MT-SDT procedure, or a notification that data belonging to an MT-SDT bearer is available for transmission during the MO-SDT procedure, or data not belonging to an MT-SDT bearer after the MT-SDT procedure is completed, or data belonging to an MT-SDT bearer after the MO-SDT procedure is completed.

[0084] In some embodiments, the data not belonging to an MT-SDT bearer further includes data belonging to an MO-SDT bearer.

[0085] In some embodiments, the network device may also send notification or resumption related settings to the end device.

[0086] In some embodiments, the configuration indicates at least one of: that the device is permitted to send notifications; that an MO-SDT configured bearer is permitted to be resumed during an MT-SDT procedure; that an MT-SDT configured bearer is permitted to be resumed during an MO-SDT procedure; that the device is permitted to resume an MO-SDT bearer during an MT-SDT procedure or to send data not belonging to MT-SDT or an MO-SDT bearer; that the device is permitted to resume an MT-SDT bearer during an MO-SDT procedure or to send data belonging to MT-SDT.

[0087] In some embodiments, the configuration is received via a paging message, a MAC CE, or RRC signaling.

[0088] In some embodiments, the configuration is signaled by at least one of: the MAC CE including a header indicating that one or more configured MO-SDT, MT-SDT bearers are to be resumed; and the MAC CE indicating the respective bearers corresponding to one or more logical channel identifiers to be resumed.

[0089] In some embodiments, the notification further indicates that the MO-SDT bearer or the MT-SDT bearer is resumed.

[0090] In some embodiments, this notification is included in BSR or RRC signaling, for example in an assistance information message.

[0091] In some embodiments, this notification is included in an aiding information message that contains a new cause for resumption of MO-SDT or MT-SDT data arrival or a new notification of MO-SDT or MT-SDT data.

[0092] In some embodiments, an apparatus capable of executing method 300 (e.g., implemented in terminal device 110) may comprise means for performing the steps of method 300. The means may be implemented in any suitable form, for example, as a circuit or a software module.

[0093] In some embodiments, the apparatus includes means for determining that data not belonging to an MT-SDT bearer is available during an MT-SDT procedure or that data belonging to an MT-SDT bearer is available during an MO-SDT procedure, and, based on the determination, performing at least one of: sending a notification to the network device indicating the presence of data; resuming the non-MT-SDT bearer during the MT-SDT procedure or resuming the MT-SDT bearer during the MO-SDT procedure; transmitting the data not belonging to the MT-SDT bearer after the MT-SDT procedure is completed; or transmitting the data belonging to the MT-SDT bearer after the MO-SDT procedure is completed.

[0094] In some embodiments, the data not belonging to an MT-SDT bearer further includes data belonging to an MO-SDT bearer.

[0095] In some embodiments, the device may also include means for receiving a notification or resumption related configuration from the network device.

[0096] In some embodiments, the configuration indicates at least one of: that the device is permitted to send notifications; that MO-SDT configured bearers are permitted to be resumed during an MT-SDT procedure; that MT-SDT configured bearers are permitted to be resumed during an MO-SDT procedure; that the device is permitted to resume MO-SDT bearers during an MT-SDT procedure or to send data not belonging to MT-SDT or MO-SDT bearers; that the device is permitted to resume MT-SDT bearers during an MO-SDT procedure or to send data belonging to MT-SDT.

[0097] In some embodiments, the configuration is received via a paging message, a MAC CE, or RRC signaling.

[0098] In some embodiments, the configuration is signaled by the MAC CE including a header indicating that one or more configured non-MT SDT, MO-SDT or MT-SDT bearers are to be resumed, and / or the MAC CE indicating the respective bearers corresponding to one or more logical channel identifiers to be resumed.

[0099] In some embodiments, the apparatus may also include means for notifying the RRC layer from the MAC layer to resume at least one of the MO-SDT or MT-SDT bearers.

[0100] In some embodiments, the notification further indicates that the MO-SDT bearer or the MT-SDT bearer is resumed.

[0101] In some embodiments, this notification is included in BSR or RRC signaling, for example, in an Assistance Information message.

[0102] In some embodiments, this notification is included in an aiding information message that contains a new cause for resumption of MO-SDT or MT-SDT data arrival or a new notification of MO-SDT or MT-SDT data.

[0103] In some embodiments, an apparatus capable of performing method 400 (e.g., implemented in network device 120) may include means for performing each step of method 400. The means may be implemented in any suitable form. For example, the means may be implemented as a circuit or a software module.

[0104] In some embodiments, the apparatus comprises means for receiving from the terminal device at least one of a notification indicating the presence of data not belonging to an MT-SDT bearer available during an MT-SDT procedure, or a notification indicating the presence of data belonging to an MT-SDT bearer available during an MO-SDT procedure, or data not belonging to an MT-SDT bearer after an MT-SDT procedure has been completed, or data belonging to an MT-SDT bearer after an MO-SDT procedure has been completed.

[0105] In some embodiments, the data not belonging to an MT-SDT bearer further includes data belonging to an MO-SDT bearer.

[0106] In some embodiments, the device may also comprise means for sending a notification or resumption related configuration to the terminal device.

[0107] In some embodiments, the configuration indicates at least one of: that the device is permitted to send notifications; that an MO-SDT configured bearer is permitted to be resumed during an MT-SDT procedure; that an MT-SDT configured bearer is permitted to be resumed during an MO-SDT procedure; that the device is permitted to resume an MO-SDT bearer during an MT-SDT procedure or to send data not belonging to MT-SDT or an MO-SDT bearer; that the device is permitted to resume an MT-SDT bearer during an MO-SDT procedure or to send data belonging to MT-SDT.

[0108] In some embodiments, the configuration is received via a paging message, a MAC CE, or RRC signaling.

[0109] In some embodiments, the configuration is signaled by the MAC CE including a header indicating that one or more configured non-MT-SDT, MO-SDT or MT-SDT bearers are to be resumed, and / or the MAC CE indicating the respective bearers corresponding to one or more logical channel identifiers to be resumed.

[0110] In some embodiments, the notification further indicates that the MO-SDT bearer or the MT-SDT bearer is resumed.

[0111] In some embodiments, this notification is included in BSR or RRC signaling, for example in an assistance information message.

[0112] In some embodiments, this notification is included in an aiding information message that contains a new cause for resumption of MO-SDT or MT-SDT data arrival or a new notification of MO-SDT or MT-SDT data.

[0113] 5 is a simplified block diagram of an apparatus 500 suitable for implementing embodiments of the present disclosure. The apparatus 500 may be used to implement a communications device such as the first terminal device 110 or the second terminal device 120 shown in FIG. 1. As shown, the apparatus 500 includes one or more processors 510, one or more memories 520 coupled to the processors 510, and one or more communications modules 540 coupled to the processors 510.

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

[0115] Processor 510 may be of any type suitable for a local technology network, including, for example, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a processor based on a multi-core processor architecture, etc. Device 500 may have multiple processors, such as application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

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

[0117] The computer program 530 includes computer-executable instructions that are executed by the associated processor 510. The instructions in the program 530 may include instructions for performing operations / acts in some embodiments of the present disclosure. The program 530 may be stored in a memory, such as the ROM 524. The processor 510 can load the program 530 into the RAM 522 to perform any appropriate operations and processes.

[0118] An exemplary embodiment of the present disclosure may be implemented by a program 530, which enables the device 500 to perform any of the processes of the present disclosure described with reference to Figures 2 to 4. An exemplary embodiment of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0119] In some embodiments, the program 530 may be tangibly stored on a computer-readable medium included in the device 500 (e.g., in memory 520) or on another storage device accessible to the device 500. The device 500 may load the program 530 from the computer-readable medium into RAM 522 and execute it. In some embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" here does not limit the permanence of the data storage (e.g., RAM vs. ROM), but rather the medium itself (i.e., a tangible medium rather than a signal).

[0120] 6 shows an example of a computer readable medium 600, which may take the form of a CD, DVD, or other optical storage device. The computer readable medium 600 has the program 530 stored thereon.

[0121] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some features may be implemented in hardware, while other features may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of the embodiments herein are described using block diagrams, flowcharts, or other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented by, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or combinations thereof.

[0122] Some embodiments of the present disclosure also provide at least one computer program product tangibly embodied on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, that execute on a target physical or virtual processor device to perform any of the methods described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. The machine-executable instructions for the program modules may be executed in local or distributed devices. In a distributed device, the program modules may be located in both local and remote storage media.

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

[0124] In the context of the present disclosure, computer program code or associated data may be transmitted by any suitable medium to enable a device, apparatus, or processor to perform the various processes and operations as described above. Examples of media include signals, computer-readable media, etc.

[0125] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media 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 an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0126] Furthermore, although operations are shown in a particular order, this does not imply that the operations must be performed in the particular order shown, or in a sequential order, or that all of the operations shown must be performed to achieve desirable results. In certain situations, multitasking or parallel processing may be advantageous. Similarly, while the above description includes some specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of functionality specific to particular embodiments. Unless expressly stated otherwise, certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, unless expressly stated otherwise, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

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

Claims

1. 1. An apparatus comprising: at least one processor; When executed by the at least one processor, the device includes at least: determining whether data not belonging to a Mobile Terminated Small Data Transmission (MT-SDT) bearer is available during an MT-SDT procedure or whether data belonging to an MT-SDT bearer is available during a Mobile Originated Small Data Transmission (MO-SDT) procedure; Based on the determination, sending a notification to a network device indicating the presence of said data; or resuming the non-MT-SDT bearer during the MT-SDT procedure, or resuming the MT-SDT bearer during the MO-SDT procedure, or transmitting data not belonging to an MT-SDT bearer after the MT-SDT procedure is completed, or transmitting data belonging to an MT-SDT bearer after the MO-SDT procedure is completed; and performing at least one of the following: at least one memory storing instructions for executing the To prepare, equipment.

2. The apparatus of claim 1 , wherein the data not belonging to the MT-SDT bearer further includes data belonging to MO-SDT.

3. The apparatus further comprises: receiving a setting regarding the notification or the resumption from the network device; The device according to claim 1 .

4. The setting is: the device is authorized to send the notification; the MO-SDT established bearer is allowed to be resumed during the MT-SDT procedure; the MT-SDT established bearer is allowed to be resumed during the MO-SDT procedure; the device is allowed to resume the MO-SDT bearer or transmit data not belonging to the MT-SDT or MO-SDT bearer during the MT-SDT procedure; the device is allowed to resume an MT-SDT bearer or transmit data belonging to the MT-SDT during the MO-SDT procedure; The device according to claim 3 , wherein the device notifies at least one of:

5. The setting is: Paging messages, a Medium Access Control (MAC) Control Element (CE), or Radio resource control signaling, 5. The apparatus according to claim 3, wherein the signal is received via at least one of:

6. The setting is: The MAC CE includes a header indicating that one or more configured MO-SDT or MT-SDT bearers are resumed; or the MAC CE indicating that each bearer corresponding to one or more logical channel identifiers is resumed; 6. The device according to claim 3, wherein the notification is made by at least one of the following:

7. The apparatus further comprises: notifying a radio resource control (RRC) layer of the device from a medium access control (MAC) layer of the device to resume the at least one of the MO-SDT or MT-SDT bearers; The device according to claim 1 .

8. The notice may further include: the MO-SDT bearer or MT-SDT bearer is resumed; 8. The device according to claim 2, wherein the device notifies

9. The notice shall: Buffer status reporting, or Support information messages, 9. The device according to claim 1, wherein the device is comprised of:

10. The notice shall: A new restart triggered by the arrival of MO-SDT or MT-SDT data, or New notifications of MO-SDT or MT-SDT data, The apparatus of claim 9, wherein the assistance information message includes:

11. 1. An apparatus comprising: at least one processor; When executed by at least one processor, the apparatus includes at least: From the terminal device, an indication of the presence of data not belonging to an MT-SDT bearer available during a Mobile Terminated Small Data Transmission (MT-SDT) procedure, or an indication of the presence of data belonging to an MT-SDT bearer available during a Mobile Originated Small Data Transmission (MO-SDT) procedure, or data that does not belong to an MT-SDT bearer after the MT-SDT procedure is completed, or data that belongs to an MT-SDT bearer after the MO-SDT procedure is completed; at least one memory storing instructions for receiving at least one of: An apparatus comprising:

12. The apparatus of claim 11, wherein the data not belonging to the MT-SDT bearer further includes data belonging to MO-SDT.

13. The apparatus further comprises: transmitting a setting related to the notification or the resumption to the terminal device; The device according to claim 11 .

14. The setting is: the device is authorized to send the notification; the MO-SDT established bearer is allowed to be resumed during the MT-SDT procedure; the MT-SDT established bearer is allowed to be resumed during the MO-SDT procedure; the device is allowed to resume or transmit data not belonging to the MT-SDT or the MO-SDT during the MT-SDT procedure, or the device is allowed to resume or transmit data belonging to the MT-SDT during the MO-SDT procedure; The device according to claim 13, wherein the device notifies at least one of

15. The setting is: Paging messages, a Medium Access Control (MAC) Control Element (CE), or Radio resource control signaling, 15. The device according to claim 13 or 14, wherein the device is transmitted via at least one of:

16. The setting is: the MAC CE includes a header indicating that one or more configured MO-SDT or MT-SDT bearers are resumed; the MAC CE indicating each bearer corresponding to one or more logical channel identifiers to be resumed; 16. The device of claim 15, wherein the notification is provided by at least one of:

17. The notice may further include: the MO-SDT bearer or MT-SDT bearer is resumed; 17. The device according to claim 11, wherein the device notifies

18. The notice shall: Buffer status reporting, or Support information messages, 18. The apparatus of claim 17,

19. The notice shall: A new restart cause of MO-SDT or MT-SDT data arrival, or New notifications of MO-SDT or MT-SDT data, 20. The apparatus of claim 18, wherein the assistance information message includes:

20. determining, at the terminal device, that data not belonging to a Mobile Terminated Small Data Transmission (MT-SDT) bearer is available during an MT-SDT procedure or that data belonging to an MT-SDT bearer is available during a Mobile Originated Small Data Transmission (MO-SDT) procedure; Based on the determination, sending a notification to a network device indicating the presence of said data; or resuming the non-MT-SDT bearer during the MT-SDT procedure, or resuming the MT-SDT bearer during the MO-SDT procedure, or transmitting data not belonging to an MT-SDT bearer after the MT-SDT procedure is completed, or transmitting data belonging to an MT-SDT bearer after the MO-SDT procedure is completed; and performing at least one of the following: A method comprising:

21. In the network device, from the terminal device, an indication of the presence of data not belonging to an MT-SDT bearer available during a Mobile Terminated Small Data Transmission (MT-SDT) procedure, or an indication of the presence of data belonging to an MT-SDT bearer available during a Mobile Originated Small Data Transmission (MO-SDT) procedure, or data that does not belong to an MT-SDT bearer after the MT-SDT procedure is completed, or data that belongs to an MT-SDT bearer after the MO-SDT procedure is completed; receiving at least one of:

22. 1. An apparatus comprising: means for determining whether data not belonging to a Mobile Terminated Small Data Transmission (MT-SDT) bearer is available during an MT-SDT procedure or whether data belonging to an MT-SDT bearer is available during a Mobile Originated Small Data Transmission (MO-SDT) procedure; Based on the above determination, sending a notification to a network device indicating the presence of said data; or resuming the non-MT-SDT bearer during the MT-SDT procedure, or resuming the MT-SDT bearer during the MO-SDT procedure, or transmitting data not belonging to an MT-SDT bearer after the MT-SDT procedure is completed, or transmitting data belonging to an MT-SDT bearer after the MO-SDT procedure is completed; and means for performing at least one of the following: An apparatus comprising:

23. 1. An apparatus comprising: From the terminal device, an indication of the presence of data not belonging to an MT-SDT bearer that is available during a Mobile Terminated Small Data Transmission (MT-SDT) procedure, or an indication of the presence of data belonging to an MT-SDT bearer that is available during a Mobile Originated Small Data Transmission (MO-SDT) procedure, or data that does not belong to an MT-SDT bearer after the MT-SDT procedure is completed, or data that belongs to an MT-SDT bearer after the MO-SDT procedure is completed; means for receiving at least one of An apparatus comprising:

24. A computer readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform at least the method of claim 20 or the method of claim 21.

Images