Method and apparatus for performing small data transmission and communication system

Abstract

Embodiments of the present application provide a method and apparatus for performing small data transmission, and a communication system. The apparatus for performing small data transmission is applied to a terminal device, and the apparatus comprises a first processing unit, wherein the first processing unit controls the terminal device and causes the terminal device to perform the following operations: initiating small data transmission (SDT); and when the next valid configured grant (CG) occasion satisfies a predetermined condition in the time domain, performing configured grant small data transmission (CG-SDT).

Description

Method, device and communication system for performing small data transmission Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] The Small Data Transmission (SDT) process allows the transmission of data and / or signaling in the Radio Resource Control Inactive (RRC_INACTIVE) state, wherein the RRC_INACTIVE state refers to not entering the Radio Resource Control Connected (RRC_CONNECTED) state.

[0003] In New Radio (NR), up to Release 16 (Rel-16), the RRC_INACTIVE state does not support data transmission. Therefore, the terminal device (e.g., UE) must first restore the connection, transitioning to the RRC_CONNECTED state, for both downlink / terminal (DL / MT) and uplink / terminal-oriented (UL / MO) data transmission. This means that even for infrequent small data transmissions, a connection must be established / restored and then released to the INACTIVE state, resulting in energy consumption and signaling overhead. Infrequent small data transmissions include services from instant messaging services (WhatsApp, QQ, WeChat, etc.), heartbeat services or keep-alive services from instant messaging or email (IM / e-mail) clients and other apps, push notifications from various applications, services from wearable devices (e.g., periodic location information), sensors (e.g., industrial wireless sensor networks sending temperature and pressure readings periodically or in an event-triggered manner), and smart meters (or networks) sending periodic meter readings.

[0004] The signaling overhead of small data packet transmission by inactive UEs is a major issue for more UEs in NR and will become a critical issue not only for network performance and efficiency, but also for UE battery performance. Basically, any device that has occasional small data packets in inactive state will benefit from small data transmission in inactive state.

[0005] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0006] Summary of the Invention

[0007] The inventors of the present application have discovered that, with respect to the prior art, how to perform small data transmission at a more reasonable time, thereby improving the reliability of small data transmission, is a problem that needs to be improved.

[0008] In response to at least one of the above problems or other similar problems, embodiments of the present application provide a method, apparatus, and communication system for performing small data transmission.

[0009] According to one aspect of an embodiment of the present application, a device for performing small data transmission is provided, which is applied to a terminal device. The device includes a first processing unit, which controls the terminal device so that the terminal device performs the following operations:

[0010] Initiate a small data transfer (SDT); and

[0011] When the next valid configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, configuration grant-based small data transmission (CG-SDT) is performed.

[0012] According to another aspect of an embodiment of the present application, a device for performing small data transmission is provided, which is applied to a terminal device. The device includes a second processing unit, which controls the terminal device so that the terminal device performs the following operations:

[0013] Initiate a small data transfer (SDT); and

[0014] When the next configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, a configuration grant-based small data transmission (CG-SDT) is performed.

[0015] Wherein, satisfying the predetermined condition in the time domain includes:

[0016] There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next configured grant opportunity (CG occasion), or the time interval between the next configured grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

[0017] One of the beneficial effects of the embodiments of the present application is that a more reasonable timing can be set for the execution of small data transmission, thereby improving the reliability of small data transmission.

[0018] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0019] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0020] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0022] FIG1 is a schematic diagram of a communication system of the present application;

[0023] FIG2 is a schematic diagram of a small data transmission process based on random access during RRC inactivity;

[0024] FIG3 is a schematic diagram of a process of transmitting small data based on RACH or performing a RACH process to enter an RRC connected state;

[0025] FIG4 is a schematic diagram of a small data transmission process based on a configured authorization during RRC inactivity;

[0026] Figure 5 is a schematic diagram of initiating SDT;

[0027] FIG6 is a schematic diagram of the interaction between terminal devices and the initiation evaluation of MT-SDT;

[0028] FIG7 is a schematic diagram of the time interval between the initiation of the SDT process and the next CG-SDT occasion in condition 2);

[0029] FIG8 is a schematic diagram of a method for performing small data transmission according to an embodiment of the first aspect;

[0030] FIG9 is another schematic diagram of the time interval between the initiation of the SDT process and the next CG-SDT occasion in condition 2);

[0031] FIG10 is a schematic diagram of a method for performing small data transmission according to an embodiment of the second aspect;

[0032] FIG11 is a schematic diagram of an apparatus for performing small data transmission in an embodiment of the third aspect;

[0033] FIG12 is a schematic diagram of an apparatus for performing small data transmission in an embodiment of the fourth aspect;

[0034] FIG13 is a schematic diagram of a method for performing small data transmission according to an embodiment of the fifth aspect;

[0035] FIG14 is a schematic diagram of an apparatus for performing small data transmission in an embodiment of the sixth aspect;

[0036] Figure 15 is a schematic diagram of an electronic device according to an embodiment of the seventh aspect. DETAILED DESCRIPTION

[0037] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0038] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0039] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0040] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0041] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0042] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. Network devices may include, but are not limited to, the following devices: an integrated access and backhaul node (IAB-node), a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and the like.

[0043] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0044] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0045] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0046] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0047] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as mentioned above.

[0048] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" are interchangeable to avoid confusion.

[0049] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" are interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH)" are interchangeable.

[0050] In addition, sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH, sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH, and sending or receiving PRACH can be understood as sending or receiving preamble carried by PRACH; uplink signals can include uplink data signals and / or uplink control signals, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or uplink channels. Sending uplink transmission on uplink resources can be understood as sending the uplink transmission using the uplink resources. Similarly, downlink data / signals / channels / information can be understood accordingly.

[0051] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0052] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0053] Figure 1 is a schematic diagram of the communication system of the present application, which schematically illustrates a situation taking a terminal device and a network device as an example. As shown in Figure 1, the communication system 100 may include a network device 101 and a terminal device 102 (for simplicity, Figure 1 only illustrates one terminal device as an example).

[0054] In the embodiment of the present application, existing services or future services can be carried out between the network device 101 and the terminal device 102. For example, these services include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0055] Among them, the terminal device 102 can send data to the network device 101, for example, using authorization (for example, a configured authorization, i.e., a configured grant) or an authorization-free transmission mode. In the authorization mode, the network device 101 can receive data sent by one or more terminal devices 102 in the authorization, and feedback information to the terminal device 102, such as confirmation ACK / non-confirmation NACK information, etc., or indicate a new authorization to the terminal device 102. The terminal device 102 can confirm the end of the transmission process based on the feedback information or the new authorization, or can also perform new data transmission, or can retransmit the data. For the authorization-free transmission mode, the terminal device can transmit new data on the configured authorization, or can retransmit.

[0056] The key elements of Small Data Transfer (SDT) in NR, namely the INACTIVE state, 2-step / 4-step random access, and configured grant type 1, have been defined as part of Rel-15 and Rel-16. Therefore, ensuring small data transfer in the INACTIVE state of NR can be based on these elements.

[0057] SDT is enabled on a radio bearer and can be initiated by the UE in the case of mobile-initiated SDT, i.e., mobile-oriented small data transmission (MO-SDT) and / or by the network equipment in the case of mobile-terminated SDT, i.e., mobile-terminated small data transmission (MT-SDT). The network equipment can enable MO-SDT and / or MT-SDT in a cell. MO-SDT is only initiated by the UE if the amount of UL data waiting to be transmitted on all radio bearers with activated SDT is less than the configured value, the DL RSRP is greater than the configured threshold, and valid SDT resources are available. When DL data is waiting for transmission on a radio bearer configured with SDT, MT-SDT is initiated by the network using an indication sent to the UE in a paging message; based on this indication, the UE only initiates MT-SDT if the DL RSRP is greater than the configured threshold.

[0058] The SDT procedure is initiated using transmissions on the Random Access Channel (RACH) or Type 1 Configuration Grant (Type 1 CG) resources. RACH can be configured using system information, and Type 1 CG resources can be configured using dedicated signaling in the Radio Resource Control Release (RRCRelease) request. For both RACH and CG, SDT resources can be configured on the initial bandwidth portion (BWP), non-supplimentary uplink (NUL) carriers, and / or supplementary uplink (SUL) carriers. CG resources for SDT are only valid in the UE's primary cell (PCell) upon receipt of an RRCRelease with a hold indication, and are associated with one or more Synchronization Signal Blocks (SSBs). SDT on RACH does not support contention-free random access (CFRA). If MT-SDT on RACH is initiated, the UE only uses RACHs that are not configured for SDT (i.e., RACHs configured for MO-SDT).

[0059] Figure 2 is a schematic diagram of a small data transmission process based on random access during RRC inactivity. As shown in Figure 2, the process includes the following operations:

[0060] Operation 1. The RRC-inactive UE sends an RRCResumeRequest message and sends UL SDT data and / or UL SDT signaling;

[0061] Operation 2. The gNB-DU (distributed unit) buffers the UL SDT data and / or UL SDT signaling.

[0062] Operation 3. The gNB-DU includes the RRCResumeRequest and SDT access indication in a non-UE-associated INITIAL UL RRC MESSAGE TRANSFER message and passes it to the gNB-CU-CP (control plane). The gNB-DU may also provide SDT assistance information.

[0063] Operations 4 and 5. The gNB-CU-CP sends a UE CONTEXT SETUP REQUEST message including the stored F1 UL TEIDs to create a UE context in the gNB-DU. The gNB-DU responds with a UE CONTEXT SETUP RESPONSE message including the allocated F1 DL TEIDs for DRBs (carrying user data). If there is any UL SDT data, it is transferred to the gNB-CU-UP (user plane). If there is any UL signaling, it is transferred to the gNB-CU-CP via a UL RRC MESSAGE TRANSFER message. Any uplink non-access stratum protocol data units (UL NAS PDUs) are sent to the AMF (Access and Mobility Management Function).

[0064] - NOTE 1: In the case where the full UE context is acquired from another gNB-CU-CP, the gNB-CU-CP first establishes the UE context via the bearer context establishment procedure in the gNB-CU-UP and obtains the F1-U UL TEIDs before operation 4. The BEARER CONTEXT SETUP REQUEST message may include an indication to initiate a non-SDT bearer. In this case, the BEARER CONTEXT MODIFICATION REQUEST message in operation 6 does not include an indication to resume SDT DRBs.

[0065] NOTE 2: In the case where only a partial UE context for SDT, including F1-U UL TEIDs, is obtained from another gNB-CU-CP, the gNB-CU-CP uses those F1-U UL TEIDs in steps 4-5 and does not perform subsequent operations 6-7. The F1-U DL TEIDs received from the gNB-DU in operation 5 should be passed to the other gNB-CU-CP for transfer of DL SDT data. In addition, if there is UL SDT data, it is passed from the gNB-DU to the gNB-CU-UP from which the partial context was obtained, and if there is UL signaling, it is passed from the gNB-CU-CP to the other gNB-CU-CP (the last serving gNB-CU-CP) via the XnAP RRC TRANSFER message.

[0066] - Note 3: If received before resuming the SDT bearer, other gNB-CU-UPs may need to buffer the UL SDT data;

[0067] Operation 6. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message including a resume indication for the SDT DRBs. The gNB-CU-CP also includes the F1-U DL TEIDs received from the gNB-DU in operation 5.

[0068] Operation 7. The gNB-CU-UP responds with the BEARER CONTEXT MODIFICATION RESPONSE message.

[0069] NOTE 4: When the SDT transfer is complete, the gNB-CU shall send a UE CONTEXT RELEASE COMMAND message to the gNB-DU. If CG-SDT is (re)configured, the gNB-CU may request the gNB-DU to retain the CG-SDT configuration and resources in the UE CONTEXT RELEASE COMMAND message.

[0070] In some cases, the UE has CG-SDT resource configuration but decides to perform RACH-based small data transmission with RRC inactive or perform a RACH procedure to enter the RRC connected state. Figure 3 is a schematic diagram of the process of performing RACH-based small data transmission or performing a RACH procedure to enter the RRC connected state. As shown in Figure 3, the process includes the following operations:

[0071] Operation 1. An RRC-inactive UE sends an RRCResumeRequest message. If the UE decides to perform a RACH-based SDT procedure, it also sends UL SDT data and / or UL SDT signaling.

[0072] Operation 2. The gNB-DU buffers the UL SDT data and / or UL SDT signaling.

[0073] Operation 3. The gNB-DU sends an INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU-CP, which includes the new gNB-DU UE F1AP ID. In the case of RACH-based SDT access, the gNB-DU provides an indication of SDT access and may also provide SDT assistance information.

[0074] Operation 4. The gNB-CU-CP sends a UE CONTEXT SETUP REQUEST message including the stored F1UL TEIDs. The new gNB-DU UE F1AP ID is received in operation 3.

[0075] In the case where the gNB-DU is the gNB-DU that sends the RRCRelease message carrying the CG-SDT resource configuration to the UE, the gNB-CU-CP also includes the old gNB-DU UE F1AP ID and the old gNB-CU UE F1AP ID in the Old CG-SDT Session Info IE of the UE CONTEXT SETUP REQUEST message;

[0076] If the gNB-CU-CP is the one that generates the RRCRelease message carrying the CG-SDT resource configuration, but the gNB-DU is not the old gNB-DU that sent the RRCRelease message to the UE, the gNB-CU-CP initiates the UE Context Release procedure by sending a UE CONTEXT RELEASE COMMAND message to the old gNB-DU.

[0077] In the case that the UE accesses a gNB other than the last served gNB, upon receiving the RETRIEVE UE CONTEXT REQUEST message from the receiving gNB-CU-CP, the last served gNB-CU-CP initiates the UE Context Release procedure by sending a UE CONTEXT RELEASE COMMAND message to the last served gNB-DU;

[0078] Operation 5. The gNB-DU sends a UE CONTEXT SETUP RESPONSE message carrying the new gNB-DU UE F1AP ID. If the old gNB-DU UE F1AP ID was received in the Old CG-SDT Session Info IE in operation 4, the gNB-DU retrieves the stored CG-SDT resource configuration and UE context based on the Old CG-SDT Session Info IE, if any, and associates it with the new gNB-DU UE F1AP ID.

[0079] Figure 4 is a schematic diagram of the small data transmission process based on the configured authorization during RRC inactivity. As shown in Figure 4, the process includes the following operations:

[0080] Operation 1. The gNB-CU decides to put the UE into the RRC_INACTIVE state.

[0081] Operation 2. The gNB-CU-CP decides to configure CG-SDT and sends a UE CONTEXT MODIFICATION REQUEST message, which includes a query indication for CG-SDT-related resource configuration associated with the SDT radio bearer information.

[0082] Operation 3. The gNB-DU sends a UE CONTEXT MODIFICATION RESPONSE message, which includes the CG-SDT-related resource configuration of the requested SDT radio bearer in the DU to CU RRC Information IE.

[0083] Operation 4. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message carrying a suspend indication to the gNB-CU-UP.

[0084] Operation 5. The gNB-CU-UP sends a BEARER CONTEXT MODIFICATION RESPONSE to the gNB-CU-CP.

[0085] Operation 6. The gNB-CU-CP sends a UE CONTEXT RELEASE COMMAND message to the gNB-DU, which includes an RRCRelease message to the UE, with the CG-SDT information included in the hold configuration. When the UE is entering the RRC_INACTIVE state with an explicit CG-SDT kept indicator, the gNB-CU notifies the gNB-DU to retain the SDT RLC configuration, F1-U tunnel, F1AP UE association, and store the CG resources for SDT.

[0086] Operation 7. The gNB-DU sends an RRCRelease message to the UE.

[0087] Operation 8. The gNB-DU sends a UE CONTEXT RELEASE COMPLETE message. When the UE enters RRC_INACTIVE, the gNB-DU retains the SDT RLC configuration, F1-U tunnel, F1AP UE association, and stores the CG resources for SDT. The gNB-DU also stores the C-RNTI, CS-RNTI, and which bearers are CG-SDT bearers.

[0088] After the UE is in RRC_INACTIVE state for a period of time

[0089] Operation 9. The UE decides to perform the CG-based SDT procedure and sends an RRCResumeRequest message together with UL SDT data / UL NAS PDU.

[0090] Operation 10. The gNB-DU sends an UL RRC MESSAGE TRANSFER message including an RRCResumeRequest message to indicate that the access is due to CG-SDT.

[0091] Operation 11 / 12. The gNB-CU-CP initiates the BEARER CONTEXT MODIFICATION procedure to recover SDT DRBs.

[0092] Action 13 – Action 13a. The gNB-DU sends the UL SDT number, if any, to the gNB-CU-UP and / or sends UL signaling via UL RRC MESSAGE TRANSFER message to the gNB-CU-CP, if any, where any UL NAS PDU is sent to the AMF.

[0093] Note: When the SDT transfer is complete, the gNB-CU will send a UE CONTEXT RELEASE COMMAND message to the gNB-DU. If CG-SDT is reconfigured, the gNB-CU can request the gNB-DU to retain the CG-SDT configuration and resources in the UE CONTEXT RELEASE COMMAND message.

[0094] Figure 5 is a schematic diagram of initiating an SDT. As shown in Figure 5, the process of initiating an SDT includes the following operations:

[0095] Operation 501: A terminal device in an RRC_inactive state detects an MT-SDT indication in a paging message.

[0096] Operation 502: Determine whether the conditions for MT-SDT are met. If so (i.e., the judgment is "yes"), proceed to operation 503; otherwise, proceed to operation 504;

[0097] Operation 503: The terminal device initiates the RRC resume procedure for SDT (UE initiates the resume procedure for SDT);

[0098] Operation 504: The terminal device initiates the RRC recovery process (UE initiates the legacy resume procedure), for example, enters the connected state. The RRC recovery process is performed according to the existing RRC recovery process.

[0099] Figure 6 is a schematic diagram of the interaction between terminal devices and the initiation and evaluation of MT-SDT. Figure 6 includes the following operations:

[0100] Operation 601: A terminal device in the RRC_inactive state detects an MT-SDT indication in a paging message.

[0101] Operation 602: Determine whether the RSRP of the DL PL reference is higher than the threshold or the threshold is not configured (RSRP of the DL PL reference is higher than the Threshold or the Threshold is not confiqured). If the judgment is "yes", proceed to operation 603; otherwise, proceed to operation 610;

[0102] Operation 603: Determine whether the CG-SDT condition is met (Are condition for CG-SDT fulfilled?). If the judgment is "yes", proceed to operation 604; otherwise, proceed to operation 607.

[0103] Operation 604: performing configuration-granted small data transfer (CG-SDT);

[0104] Operation 605: The conditions for initiating the SDT process are met;

[0105] Operation 606: Initiate an RRC resume procedure for SDT, where the cause is MT-SDT. In addition, deliver a common control channel message (CCCH message) to the media access control layer (MAC layer) to perform configuration grant-based small data transmission (CG-SDT), corresponding to operation 503 in Figure 5;

[0106] Operation 607: Consider the CG-SDT timing alignment timer (TAT) as timed out.

[0107] Operation 608: The conditions for initiating the SDT process are met;

[0108] Operation 609: Initiate an RRC resume procedure for SDT, where the cause is MT-SDT. In addition, deliver a common control channel message (CCCH message) to the media access control layer (MAC layer) to perform small data transmission based on random access (RA-SDT) (non-RA-SDT RACH), corresponding to operation 503 in FIG. 5 ;

[0109] Operation 610: The conditions for initiating the SDT process are not met;

[0110] Operation 611: Execute an RRC recovery procedure (the legacy resume procedure), where the cause is terminal terminated access (MT-access). In addition, a common control channel message (CCCH message) is sent to the media access control layer (MAC layer) to perform random access (legacy RA), that is, enter the connected state, corresponding to operation 504 in Figure 5. The RRC recovery procedure is performed according to the existing RRC recovery procedure, and the random access procedure is performed according to the existing random access procedure.

[0111] In operation 603 of FIG. 6 , the conditions of the CG-SDT may include:

[0112] 1) CG-SDT is configured on the selected UL carrier (e.g., type-1 CG) and the CG-SDT timing advance (TA) is valid in the first available CG occasion of the initial CG-SDT transmission carrying the CCCH message; or

[0113] 2) the time interval between the initiation of the SDT process (initial) and the next CG-SDT occasion (opportunity) is less than the offset value (offset), such as cg-SDT-MaxDurationToNext-CG-Occasion, if configured; or

[0114] 3) At least one SSB configured for CG-SDT whose synchronization signal reference signal received power (SS-RSRP) is greater than cg-SDT-RSRP-ThresholdSSB is available.

[0115] In each embodiment of the present application, SDT and SDT process have the same meaning; CG-SDT occasion and CG occasion have the same meaning.

[0116] Embodiments of the first aspect

[0117] In operation 603 of FIG. 6 , condition 2) of CG-SDT takes into account the time interval between the initiation of the SDT process and the next CG-SDT occasion to ensure that the terminal can respond to the network's paging in a timely manner.

[0118] FIG7 is a schematic diagram of the time interval between the initiation of the SDT process and the next CG-SDT occasion in condition 2), wherein CG-SDT occasion and CG occasion have the same meaning.

[0119] In case A of FIG7 , the time gap between the initiation of the SDT process and the next CG-SDT occasion is less than the offset value, where the offset value is, for example, cg-SDT-MaxDurationToNext-CG-Occasion, and therefore, CG-SDT can be performed.

[0120] In case B of FIG. 7 , the time gap between the initiation of the SDT process and the next CG-SDT occasion is greater than the offset value, where the offset value is, for example, cg-SDT-MaxDurationToNext-CG-Occasion. Therefore, CG-SDT is not performed.

[0121] In addition, the above condition 3) takes into account the SS-RSRP of the SSB of the CG-SDT to ensure the quality of the wireless link for initiating SDT.

[0122] The inventors of this application discovered that when conditions 2) and 3) are independent of each other, that is, the CG occasion that satisfies condition 2) is unrelated to the SSB that satisfies condition 3), which means that when CG-SDT is initiated, the CG occasion sent on the selected SSB may not be able to respond to the network's paging in a timely manner (for example, although the CG occasion satisfies condition 2) but does not satisfy condition 3)), resulting in the downlink data not being delivered in a timely manner.

[0123] In order to solve the above problems, an embodiment of the first aspect of the present application provides a method for performing small data transmission, which is applied to a terminal device, for example, the terminal device 102 in Figure 1.

[0124] FIG8 is a schematic diagram of a method for performing small data transmission according to an embodiment of the first aspect. As shown in FIG8 , the method for performing small data transmission includes:

[0125] Operation 801, initiating a small data transfer (SDT); and

[0126] Operation 802: When the next valid configuration grant opportunity (CG occasion) meets a predetermined condition in the time domain, perform configuration grant-based small data transmission (CG-SDT).

[0127] According to the method of the embodiment of the first aspect, the next configuration authorization opportunity (CG occasion) after initiating small data transmission (SDT) has both time domain requirements and validity requirements. Therefore, it can ensure that the CG occasion sent on the selected SSB can respond to the paging of the network device in a timely manner, thereby improving the reliability and efficiency of small data transmission.

[0128] In some embodiments, the operation of initiating a small data transmission in operation 801 may refer to related technologies. The operation of initiating a small data transmission (SDT) in operation 801 may be referred to as SDT initiation, and the initiation of SDT may include at least one of the following operations:

[0129] A medium access control (MAC) layer of the terminal device receives an indication from a radio resource control (RRC) layer to initiate a small data transmission (SDT);

[0130] The higher layer of the terminal device instructs to initiate a small data transmission (SDT), that is, to initiate an MT-SDT;

[0131] The media access control (MAC) layer of the terminal device evaluates or determines whether the conditions for initiating a small data transmission (SDT) are met;

[0132] The media access control (MAC) layer of the terminal device evaluates or determines whether the conditions for performing configuration-granted small data transmission (CG-SDT) are met.

[0133] In some embodiments, the active configuration grant opportunity (CG occasion) of operation 802 includes:

[0134] Configuration Grant (CG) resources configured for the Small Data Transfer (SDT); and / or

[0135] A synchronization signal block (SSB) associated with a configuration grant (CG) resource is available, wherein the association between the configuration grant (CG) resource and the synchronization signal block (SSB) can be configured by a network device (e.g., network device 101 of FIG. 1 ); and / or

[0136] The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than a configured first threshold, wherein the association between the configuration grant (CG) resource and the synchronization signal block (SSB) can be configured by a network device (for example, the network device 101 in Figure 1); the configured first threshold can be, for example, cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal-terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

[0137] In some embodiments, satisfying the predetermined condition in the time domain in operation 802 includes satisfying at least one of the following conditions 1 and 2:

[0138] Condition 1: The time interval between the initiation of the small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion) is less than the configured first offset. For example, the configured first offset includes cg-SDT-MaxDurationToNext-CG-Occasion, or the configured first offset includes a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0139] Condition 2: There is no available random access opportunity (RA occasion) between the initiation of the small data transmission (SDT) and the next valid configuration authorization opportunity (CG occasion) (that is, there is no available RA occasion until the next valid CG occasion), or the time interval between the next valid configuration authorization opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset (wherein, the RA occasion precedes the CG occasion, and in addition, the configured second offset includes cg-SDT-MaxDurationToNext-CG-Occasion, or the configured second offset includes a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0140] In some embodiments, in the above condition 2, if the available random access opportunity (RA occasion) is for two-step random access (2-step RA), then the available random access opportunity (RA occasion) may be:

[0141] A random access opportunity for sending a random access preamble (RA preamble), for example, the random access opportunity (RA occasion) is a random access opportunity (RA occasion) associated with a first synchronization signal block (SSB), and a synchronization signal reference signal received power (SS-RSRP) of the first SSB is higher than a configured second threshold; or

[0142] An available physical uplink shared channel opportunity (PUSCH occasion), for example, the available physical uplink shared channel opportunity (PUSCH occasion) is used to transmit MsgA, and the available physical uplink shared channel opportunity (PUSCH occasion) is associated with the available random access opportunity (RA occasion); or

[0143] The random access opportunity for sending the random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) that arrives later.

[0144] In some embodiments, in the above-mentioned condition 2, if the available random access opportunity (RA occasion) is for four-step random access (4-step RA), then the available random access opportunity (RA occasion) may be: a random access opportunity (RA occasion) associated with a second synchronization signal block (SSB), and the synchronization signal reference signal received power (SS-RSRP) of the second SSB is higher than a configured third threshold.

[0145] Through the above-mentioned condition 2, CG-SDT can be performed when the CG occasion occurs earlier than the RA occasion, so that the terminal device can respond to the paging of the network device in a timely manner.

[0146] In some embodiments, as shown in FIG8 , the method may further include:

[0147] Operation 803: If the predetermined condition in the time domain is not satisfied, perform random access-based small data transmission (RA-SDT) or perform random access.

[0148] In operation 803 , the predetermined condition in the time domain is not met, which may include: the above condition 1 is not met; or the above condition 2 is not met; or both the above condition 1 and the above condition 2 are not met.

[0149] In operation 803, a random access-based small data transmission (RA-SDT) is performed, including sending a resume request message, wherein a resume cause of the resume request message is a terminal terminated small data transmission (MT-SDT).

[0150] In operation 803, random access is performed, which may be legacy random access (legacy RA), for example, including sending a resume request message, wherein the resume cause of the resume request message is MT-access.

[0151] Embodiments of the second aspect

[0152] In operation 603 of FIG. 6 , condition 2) of the CG-SDT considers the time interval between the initiation of the SDT process and the next CG-SDT occasion.

[0153] FIG9 is another schematic diagram of the time interval between the initiation of the SDT process and the next CG-SDT occasion in condition 2). FIG9 also shows the RA occasion. CG-SDT occasion and CG occasion have the same meaning.

[0154] In case A1 of FIG9 , the time gap between the initiation of the SDT procedure and the next CG-SDT occasion is less than an offset value, such as cg-SDT-MaxDurationToNext-CG-Occasion. Therefore, according to condition 2), CG-SDT can be performed. The next RA occasion occurs after the CG-SDT occasion.

[0155] In case A2 of FIG9 , the time gap between the initiation of the SDT procedure and the next CG-SDT occasion is less than an offset value, such as cg-SDT-MaxDurationToNext-CG-Occasion. Therefore, according to condition 2), CG-SDT can be performed. The next RA occasion arrives before the CG-SDT occasion.

[0156] In case B1 of Figure 9 , the time gap between the initiation of the SDT procedure and the next CG-SDT occasion is greater than an offset value, such as cg-SDT-MaxDurationToNext-CG-Occasion. Therefore, according to condition 2), CG-SDT is not performed, and instead RA-SDT or legacy RA is performed using the next RA occasion, where the next RA occasion occurs after the CG-SDT occasion.

[0157] In case B2 of Figure 9 , the time gap between the initiation of the SDT procedure and the next CG-SDT occasion is greater than the offset value, where the offset value is, for example, cg-SDT-MaxDurationToNext-CG-Occasion. Therefore, according to condition 2), CG-SDT is not performed, and instead, RA-SDT or legacy RA is performed using the next RA occasion. The next RA occasion occurs before the CG-SDT occasion, that is, the next RA occasion occurs between the initiation of the SDT procedure and the next CG-SDT occasion.

[0158] The inventors of the present application discovered that, as shown in FIG9 , when CG-SDT is executed according to condition 2), there is a problem in that the terminal device cannot respond to the paging of the network device in a timely manner.

[0159] For example, in case A2 of FIG9 , although the RA occasion precedes the CG-SDT occasion, according to condition 2), the terminal device performs the CG-SDT; if the terminal device performs the RA-SDT using the RA occasion, it will be able to respond to the paging of the network device earlier.

[0160] For another example, in case B1 of Figure 9, although the CG-SDT occasion is before the RA occasion, according to condition 2), the terminal device does not perform CG-SDT, but performs RA-SDT or legacy RA; if the terminal device uses the CG-SDT occasion to perform CG-SDT, it will be able to respond to the paging of the network device earlier.

[0161] In order to solve the above problems, an embodiment of the second aspect of the present application provides a method for performing small data transmission, which is applied to a terminal device, for example, the terminal device 102 in Figure 1.

[0162] FIG10 is a schematic diagram of a method for performing small data transmission according to an embodiment of the second aspect. As shown in FIG10 , the method for performing small data transmission includes:

[0163] Operation 1001: Initiate a small data transfer (SDT); and

[0164] Operation 1002: When the next configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, perform small data transmission based on configuration authorization (CG-SDT), wherein the predetermined conditions in the time domain are met, including: there is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next configuration grant opportunity (CG occasion), or the time interval between the next configuration grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

[0165] According to the method of the embodiment of the second aspect, it is possible to respond to the paging of the network device earlier.

[0166] In some embodiments, the operation of initiating a small data transmission in operation 1001 may refer to related technologies. The operation of initiating a small data transmission (SDT) in operation 1001 may be referred to as SDT initiation, and the initiation of SDT may include at least one of the following operations:

[0167] A medium access control (MAC) layer of the terminal device receives an indication from a radio resource control (RRC) layer to initiate a small data transmission (SDT);

[0168] The higher layer of the terminal device instructs to initiate a small data transmission (SDT), that is, to initiate an MT-SDT;

[0169] The media access control (MAC) layer of the terminal device evaluates or determines whether the conditions for initiating a small data transmission (SDT) are met;

[0170] The media access control (MAC) layer of the terminal device evaluates or determines whether the conditions for performing configuration-granted small data transmission (CG-SDT) are met.

[0171] In some embodiments, satisfying the predetermined condition in the time domain in operation 1002 includes satisfying the following condition 2, or satisfying both the following conditions 1 and 2.

[0172] Condition 1: The time interval between the initiation of the small data transmission (SDT) and the next configuration grant opportunity (CG occasion) is less than the configured first offset. For example, the configured first offset includes cg-SDT-MaxDurationToNext-CG-Occasion, or the configured first offset includes a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0173] Condition 2: There is no available random access opportunity (RA occasion) between the initiation of the small data transmission (SDT) and the next configured authorization opportunity (CG occasion) (that is, there is no available RA occasion until the next CG occasion), or the time interval between the next configured authorization opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset (wherein the moment of the RA occasion is prior to the moment of the CG occasion), and in addition, the configured second offset includes cg-SDT-MaxDurationToNext-CG-Occasion, or the configured second offset includes a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0174] In some embodiments, in the above condition 2, if the available random access opportunity (RA occasion) is for two-step random access (2-step RA), then the available random access opportunity (RA occasion) may be:

[0175] A random access opportunity for sending a random access preamble (RA preamble), for example, the random access opportunity (RA occasion) is a random access opportunity (RA occasion) associated with a first synchronization signal block (SSB), and a synchronization signal reference signal received power (SS-RSRP) of the first SSB is higher than a configured second threshold; or

[0176] An available physical uplink shared channel opportunity (PUSCH occasion), for example, the available physical uplink shared channel opportunity (PUSCH occasion) is used to transmit MsgA, and the available physical uplink shared channel opportunity (PUSCH occasion) is associated with the available random access opportunity (RA occasion); or

[0177] The random access opportunity for sending the random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) that arrives later.

[0178] In some embodiments, in the above-mentioned condition 2, if the available random access opportunity (RA occasion) is for four-step random access (4-step RA), then the available random access opportunity (RA occasion) may be: a random access opportunity (RA occasion) associated with a second synchronization signal block (SSB), and the synchronization signal reference signal received power (SS-RSRP) of the second SSB is higher than a configured third threshold.

[0179] In some embodiments, as shown in FIG10 , the method may further include:

[0180] Operation 1003: If the predetermined condition in the time domain is not satisfied, perform random access-based small data transmission (RA-SDT) or perform random access.

[0181] In operation 1003 , the predetermined condition in the time domain is not satisfied, which may include: the above condition 2 is not satisfied; or both the above condition 1 and the above condition 2 are not satisfied.

[0182] In operation 1003, a random access-based small data transmission (RA-SDT) is performed, including sending a resume request message, wherein a resume cause of the resume request message is a terminal terminated small data transmission (MT-SDT).

[0183] In operation 1003, random access is performed, which may be legacy random access (legacy RA), for example, including: sending a resume request message, wherein the resume cause of the resume request message is MT-access.

[0184] According to an embodiment of the second aspect, compared with condition 2), operations 1002 and 1003 of the present application utilize condition 2, which can respond to the paging of the network device more promptly.

[0185] For example, for situation A2 in Figure 9, the RA occasion before the CG-SDT occasion does not meet the condition 2 of this application, "there is no available random access opportunity (RA occasion) between the initiation (initiation) of small data transmission (SDT) and the next configuration authorization opportunity (CG occasion)", so according to the embodiment of the second aspect of the present application, the terminal device can use the RA occasion to perform RA-SDT (different from performing CG-SDT based on condition 2), thereby being able to respond to the paging of the network device earlier.

[0186] For another example, in case B1 of Figure 9, the CG-SDT occasion is before the RA occasion, which satisfies condition 2 of this application: "There is no available random access opportunity (RA occasion) between the initiation (initiation) of small data transmission (SDT) and the next configuration authorization opportunity (CG occasion)", so the terminal device uses the CG-SDT occasion to perform CG-SDT (different from the inability to perform CG-SDT based on condition 2), and thus can respond to the paging of the network device earlier.

[0187] Embodiments of the third aspect

[0188] The third aspect of the present application provides an apparatus for performing small data transmission, which is applied to a terminal device, for example, the terminal device 102 in Figure 1. The apparatus corresponds to the method for performing small data transmission in the first aspect of the present application.

[0189] FIG11 is a schematic diagram of an apparatus for performing small data transmission in an embodiment of the third aspect. As shown in FIG11 , the apparatus 1100 for performing small data transmission includes a first processing unit 1101. The first processing unit 1101 controls the terminal device so that the terminal device performs the following operations:

[0190] Initiate a small data transfer (SDT); and

[0191] When the next valid configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, configuration grant-based small data transmission (CG-SDT) is performed.

[0192] In some embodiments, the valid configuration grant opportunity (CG occasion) includes:

[0193] Configuration Grant (CG) resources configured for the Small Data Transfer (SDT); and / or

[0194] The synchronization signal block (SSB) associated with the configuration grant (CG) resource is available (available); and / or

[0195] The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than the configured first threshold.

[0196] In some embodiments, the association between the configuration grant (CG) resource and the synchronization signal block (SSB) is configured by a network device.

[0197] In some embodiments, the configured first threshold is cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

[0198] In some embodiments, initiating a small data transmission (SDT) includes:

[0199] The medium access control (MAC) layer of the terminal device receives an indication from the radio resource control (RRC) layer to initiate a small data transmission (SDT); or

[0200] The terminal device instructs a high-layer to initiate a small data transmission (SDT); or

[0201] The medium access control (MAC) layer of the terminal device evaluates whether a condition for initiating a small data transmission (SDT) is met; or

[0202] The medium access control (MAC) layer of the terminal device evaluates whether the conditions for performing configuration-granted small data transmission (CG-SDT) are met.

[0203] In some embodiments, satisfying a predetermined condition in the time domain includes:

[0204] The time interval between the initiation of the small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion) is less than a configured first offset; and / or

[0205] There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion), or the time interval between the next valid configuration grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

[0206] In some embodiments, the configured first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0207] In some embodiments, the configured second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0208] In some embodiments, the available random access opportunities (RA occasions) include:

[0209] A random access opportunity for sending a random access preamble (RA preamble); or

[0210] Available physical uplink shared channel opportunity (PUSCH occasion); or

[0211] The random access opportunity for sending the random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) are the ones that arrive later.

[0212] In some embodiments, the available random access opportunities (RA occasions) include:

[0213] A random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured second threshold.

[0214] In some embodiments, the available physical uplink shared channel opportunity (PUSCH occasion) is associated with the available random access opportunity (RA occasion).

[0215] In some embodiments, a random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured third threshold.

[0216] In some embodiments, when the predetermined condition is not satisfied, random access-based small data transmission (RA-SDT) or random access is performed.

[0217] In some embodiments, performing random access-based small data transmission (RA-SDT) includes:

[0218] A resume request message is sent, wherein a resume cause of the resume request message is a terminal terminated small data transfer (MT-SDT).

[0219] In some embodiments, performing random access includes:

[0220] A resume request message is sent, wherein a resume cause of the resume request message is MT-access.

[0221] For further description of the embodiment of the third aspect, reference may be made to the description of the relevant contents of the embodiment of the first aspect.

[0222] Embodiments of the fourth aspect

[0223] The fourth aspect of the present application provides an apparatus for performing small data transmission, which is applied to a terminal device, for example, the terminal device 102 in Figure 1. The apparatus corresponds to the method for performing small data transmission in the second aspect of the present application.

[0224] FIG12 is a schematic diagram of an apparatus for performing small data transmission in an embodiment of the fourth aspect. As shown in FIG12 , the apparatus 1200 for performing small data transmission includes a second processing unit 1201. The second processing unit 1201 controls the terminal device so that the terminal device performs the following operations:

[0225] Initiate a small data transfer (SDT); and

[0226] When a next configuration grant opportunity (CG occasion) satisfies a predetermined condition in the time domain, performing configuration grant-based small data transmission (CG-SDT), wherein satisfying the predetermined condition in the time domain includes:

[0227] There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next configured grant opportunity (CG occasion), or the time interval between the next configured grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

[0228] In some embodiments, initiating a small data transmission (SDT) includes:

[0229] The medium access control (MAC) layer of the terminal device receives an indication from the radio resource control (RRC) layer to initiate a small data transmission (SDT); or

[0230] The terminal device instructs a high-layer to initiate a small data transmission (SDT); or

[0231] The medium access control (MAC) layer of the terminal device evaluates whether a condition for initiating a small data transmission (SDT) is met; or

[0232] The medium access control (MAC) layer of the terminal device evaluates whether the conditions for performing configuration-granted small data transmission (CG-SDT) are met.

[0233] In some embodiments, satisfying a predetermined condition in the time domain further includes:

[0234] The time interval between the initiation of the small data transmission (SDT) and the next configuration grant opportunity (CG occasion) is less than a configured first offset.

[0235] In some embodiments, the configured first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0236] In some embodiments, the configured second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0237] In some embodiments, the available random access opportunities (RA occasions) include:

[0238] A random access opportunity for sending a random access preamble (RA preamble); or

[0239] Available physical uplink shared channel opportunity (PUSCH occasion); or

[0240] The random access opportunity for sending the random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) are the ones that arrive later.

[0241] In some embodiments, the available random access opportunities (RA occasions) include:

[0242] A random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured second threshold.

[0243] In some embodiments, the available physical uplink shared channel opportunity (PUSCH occasion) is associated with the available random access opportunity (RA occasion).

[0244] In some embodiments, a random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured third threshold.

[0245] In some embodiments, if the predetermined condition is not satisfied, random access based small data transmission (CG-SDT) or random access is performed.

[0246] In some embodiments, performing random access based small data transmission (CG-SDT) includes:

[0247] A resume request message is sent, wherein a resume cause of the resume request message is a terminal terminated small data transfer (MT-SDT).

[0248] In some embodiments, performing random access includes:

[0249] A resume request message is sent, wherein a resume cause of the resume request message is MT-access.

[0250] For further description of the embodiment of the fourth aspect, reference may be made to the description of the relevant contents of the embodiment of the second aspect.

[0251] Embodiments of the fifth aspect

[0252] The embodiment of the fifth aspect of the present application provides a method for performing small data transmission, which is applied to a network device, for example, the network device 101 in Figure 1. The device corresponds to the method for performing small data transmission in the embodiment of the first aspect.

[0253] FIG13 is a schematic diagram of a method for performing small data transmission according to an embodiment of the fifth aspect. As shown in FIG13 , the method includes:

[0254] Operation 1301: Send configuration information of small data transmission based on configuration authorization (CG-SDT config) to the terminal device; and

[0255] Operation 1302: Receive a first resume request (resume request) message, a second resume request (resume request) message, or a third resume request (resume request) message sent by the terminal device.

[0256] In operation 1302, a resume cause of a first resume request message is a terminal terminated small data transfer (MT-SDT). For example, the terminal device sends the first resume request message to the network device when executing a CG-SDT. For another example, the network device may receive the first resume request message on a configuration grant opportunity (CG occasion).

[0257] The resume cause of the second resume request message is a terminal terminated small data transfer (MT-SDT). For example, the terminal device sends the second resume request message to the network device when performing RA-SDT. For another example, the network device may receive the second resume request message in a PUSCH occasion indicated by a RAR or a PUSCH occasion configured for a payload of an MSGA.

[0258] The resume cause (resume cause) of the third resume request (resume request) message is terminal terminated access (MT-access). For example, the terminal device sends the third resume request to the network device when performing random access (for example, existing random access).

[0259] In some embodiments of operation 1302, the network device may receive the first resume request message on a valid configuration grant opportunity (CG occasion).

[0260] The valid configuration authorization opportunity (CG occasion) includes:

[0261] Configuration Grant (CG) resources configured for the Small Data Transfer (SDT); and / or

[0262] The synchronization signal block (SSB) associated with the configuration grant (CG) resource is available (available); and / or

[0263] The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than the configured first threshold.

[0264] Among them, the one or more synchronization signal blocks (SSBs) associated with the configuration grant (CG) resource can be configured by the network device, for example, the network device can configure the one or more synchronization signal blocks (SSBs) associated with the configuration grant (CG) resource.

[0265] In some embodiments, the configured first threshold is cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

[0266] As shown in FIG13 , the method further includes:

[0267] Operation 1303: The network device configures a first offset and / or a second offset for the terminal device.

[0268] Among them, the first offset is a parameter of the time interval between the initiation of small data transmission (SDT) and the next valid configuration authorization opportunity (CG occasion) or the next configuration authorization opportunity (CG occasion); the second offset is a parameter of the time interval between the next valid configuration authorization opportunity (CG occasion) or the next configuration authorization opportunity (CG occasion) and the available random access opportunity (RA occasion).

[0269] For example, the first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion; the second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0270] Embodiments of the sixth aspect

[0271] The embodiment of the sixth aspect of the present application provides an apparatus for performing small data transmission, which is applied to a network device, for example, the network device 101 in Figure 1. The apparatus corresponds to the method for performing small data transmission in the embodiment of the fifth aspect.

[0272] FIG14 is a schematic diagram of an apparatus for performing small data transmission according to an embodiment of the sixth aspect. As shown in FIG14 , the apparatus 1400 includes a third processing unit 1401. The third processing unit 1401 controls a network device so that the network device performs the following operations:

[0273] Sending configuration information of small data transmission based on configuration authorization (CG-SDT config) to the terminal device; and

[0274] Receive a first resume request (resume request) message, a second resume request (resume request) message, or a third resume request (resume request) message sent by the terminal device.

[0275] In some embodiments, the resume cause of the first resume request message is a terminal terminated small data transfer (MT-SDT). For example, the terminal device sends the first resume request to the network device when performing a CG-SDT. For another example, the network device may receive the first resume request message on a configuration grant opportunity (CG occasion).

[0276] The resume cause of the second resume request message is a terminal terminated small data transfer (MT-SDT). For example, the terminal device sends the second resume request message to the network device when performing RA-SDT. For another example, the network device may receive the second resume request message in a PUSCH occasion indicated by a RAR or a PUSCH occasion configured for a payload of an MSGA.

[0277] The resume cause (resume cause) of the third resume request (resume request) message is terminal terminated access (MT-access). For example, the terminal device sends the third resume request to the network device when performing random access (for example, existing random access).

[0278] In some embodiments, the network device may receive the first resume request message on a valid configuration grant opportunity (CG occasion).

[0279] The valid configuration authorization opportunity (CG occasion) includes:

[0280] Configuration Grant (CG) resources configured for the Small Data Transfer (SDT); and / or

[0281] The synchronization signal block (SSB) associated with the configuration grant (CG) resource is available (available); and / or

[0282] The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than the configured first threshold.

[0283] Among them, the one or more synchronization signal blocks (SSBs) associated with the configuration grant (CG) resource can be configured by the network device, for example, the network device can configure the one or more synchronization signal blocks (SSBs) associated with the configuration grant (CG) resource.

[0284] In some embodiments, the configured first threshold is cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

[0285] In some embodiments, the operation further includes: the network device configuring a first offset and / or a second offset for the terminal device.

[0286] Among them, the first offset is a parameter of the time interval between the initiation of small data transmission (SDT) and the next valid configuration authorization opportunity (CG occasion) or the next configuration authorization opportunity (CG occasion); the second offset is a parameter of the time interval between the next valid configuration authorization opportunity (CG occasion) or the next configuration authorization opportunity (CG occasion) and the available random access opportunity (RA occasion).

[0287] For example, the first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion; the second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0288] Embodiments of the seventh aspect

[0289] An embodiment of the seventh aspect of the present application provides a communication system, which may include a network device and a terminal device.

[0290] Figure 15 is a schematic diagram of an electronic device according to an embodiment of the seventh aspect. As shown in Figure 15 , electronic device 1500 may correspond to terminal device 102 or network device 101 in Figure 1 . Electronic device 1500 may include a processor 1510 and a memory 1520; memory 1520 stores data and programs and is coupled to processor 1510. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0291] For example, the processor 1510 may be configured to execute a program to implement at least one of the method in the first aspect embodiment, the method in the second aspect embodiment, and the method in the fourth aspect embodiment.

[0292] As shown in Figure 15 , the terminal device 1500 may further include: a communication module 1530, an input unit 1540, a display 1550, and a power supply 1560. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1500 does not necessarily include all of the components shown in Figure 15 , and these components are not essential. Furthermore, the terminal device 1500 may also include components not shown in Figure 15 , for which reference may be made to the prior art.

[0293] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method in the embodiment of the first aspect and / or the method in the embodiment of the second aspect.

[0294] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method in the embodiment of the first aspect and / or the method in the embodiment of the second aspect.

[0295] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method in the embodiment of the fifth aspect.

[0296] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method in the embodiment of the fifth aspect.

[0297] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0298] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0299] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0300] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0301] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0302] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0303] The terminal side method of the first aspect embodiment:

[0304] 1. A method for performing small data transmission, applied to a terminal device, the method comprising:

[0305] Initiate a small data transfer (SDT); and

[0306] When the next valid configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, configuration grant-based small data transmission (CG-SDT) is performed.

[0307] 2. The method as described in Note 1, wherein:

[0308] The valid configuration authorization opportunity (CG occasion) includes:

[0309] Configuration Grant (CG) resources configured for the Small Data Transfer (SDT); and / or

[0310] The synchronization signal block (SSB) associated with the configuration grant (CG) resource is available (available); and / or

[0311] The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than the configured first threshold.

[0312] 3. The method as described in Note 2, wherein:

[0313] The association between the configuration grant (CG) resource and the synchronization signal block (SSB) is configured by a network device.

[0314] 4. The method as described in Note 2, wherein:

[0315] The configured first threshold is cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

[0316] 5. The method as described in Note 1, wherein:

[0317] The initiating of a small data transmission (SDT) includes:

[0318] The medium access control (MAC) layer of the terminal device receives an indication from the radio resource control (RRC) layer to initiate a small data transmission (SDT); or

[0319] The terminal device instructs a high-layer to initiate a small data transmission (SDT); or

[0320] The medium access control (MAC) layer of the terminal device evaluates whether a condition for initiating a small data transmission (SDT) is met; or

[0321] The medium access control (MAC) layer of the terminal device evaluates whether the conditions for performing configuration-granted small data transmission (CG-SDT) are met.

[0322] 6. The method as described in Note 1, wherein:

[0323] The predetermined condition in the time domain is satisfied, including:

[0324] The time interval between the initiation of the small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion) is less than a configured first offset; and / or

[0325] There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion), or the time interval between the next valid configuration grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

[0326] 7. The method as described in Supplementary Note 6, wherein:

[0327] The configured first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0328] 8. The method as described in Supplementary Note 6, wherein:

[0329] The configured second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0330] 9. The method as described in Supplementary Note 6, wherein:

[0331] The available random access opportunities (RA occasions) include:

[0332] A random access opportunity for sending a random access preamble (RA preamble); or

[0333] Available physical uplink shared channel opportunity (PUSCH occasion); or

[0334] The random access opportunity for sending the random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) are the ones that arrive later.

[0335] 10. The method as described in Supplementary Note 9, wherein:

[0336] The available random access opportunities (RA occasions) include:

[0337] A random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured second threshold.

[0338] 11. The method as described in Supplementary Note 9, wherein:

[0339] The available physical uplink shared channel opportunity (PUSCH occasion) is associated with the available random access opportunity (RA occasion).

[0340] 12. The method as described in Supplementary Note 6, wherein:

[0341] A random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured third threshold.

[0342] 13. The method as described in Note 1, wherein:

[0343] If the predetermined condition is not satisfied, random access-based small data transmission (RA-SDT) or random access is performed.

[0344] 14. The method as described in Note 13, wherein:

[0345] Perform random access-based small data transmission (RA-SDT), including:

[0346] A resume request message is sent, wherein a resume cause of the resume request message is a terminal terminated small data transfer (MT-SDT).

[0347] 15. The method as described in Note 13, wherein:

[0348] Perform random access, including:

[0349] A resume request message is sent, wherein a resume cause of the resume request message is MT-access.

[0350] The terminal side method of the second aspect embodiment:

[0351] 1. A method for performing small data transmission, applied to a terminal device, the method comprising:

[0352] Initiate a small data transfer (SDT); and

[0353] When the next configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, a configuration grant-based small data transmission (CG-SDT) is performed.

[0354] Wherein, satisfying the predetermined condition in the time domain includes:

[0355] There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next configured grant opportunity (CG occasion), or the time interval between the next configured grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

[0356] 2. The method as described in Note 1, wherein:

[0357] The initiating of a small data transmission (SDT) includes:

[0358] The medium access control (MAC) layer of the terminal device receives an indication from the radio resource control (RRC) layer to initiate a small data transmission (SDT); or

[0359] The terminal device instructs a high-layer to initiate a small data transmission (SDT); or

[0360] The medium access control (MAC) layer of the terminal device evaluates whether a condition for initiating a small data transmission (SDT) is met; or

[0361] The medium access control (MAC) layer of the terminal device evaluates whether the conditions for performing configuration-granted small data transmission (CG-SDT) are met.

[0362] 3. The method as described in Note 1, wherein:

[0363] The satisfying of the predetermined condition in the time domain further includes:

[0364] The time interval between the initiation of the small data transmission (SDT) and the next configuration grant opportunity (CG occasion) is less than a configured first offset.

[0365] 4. The method as described in Note 3, wherein:

[0366] The configured first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0367] 5. The method as described in Note 1, wherein:

[0368] The configured second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0369] 6. The method as described in Note 3, wherein:

[0370] The available random access opportunities (RA occasions) include:

[0371] A random access opportunity for sending a random access preamble (RA preamble); or

[0372] Available physical uplink shared channel opportunity (PUSCH occasion); or

[0373] The random access opportunity for sending the random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) are the ones that arrive later.

[0374] 7. The method as described in Supplementary Note 6, wherein:

[0375] The available random access opportunities (RA occasions) include:

[0376] A random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured second threshold.

[0377] 8. The method as described in Supplementary Note 6, wherein:

[0378] The available physical uplink shared channel opportunity (PUSCH occasion) is associated with the available random access opportunity (RA occasion).

[0379] 9. The method as described in Supplement 3, wherein:

[0380] A random access opportunity (RA occasion) associated with a synchronization signal block (SSB) having a synchronization signal reference signal received power (SS-RSRP) higher than a configured third threshold.

[0381] 10. The method as described in Supplement 1, wherein:

[0382] If the predetermined condition is not satisfied, random access-based small data transmission (CG-SDT) or random access is performed.

[0383] 11. The method as described in Supplementary Note 10, wherein:

[0384] Perform random access-based small data transmission (CG-SDT), including:

[0385] A resume request message is sent, wherein a resume cause of the resume request message is a terminal terminated small data transfer (MT-SDT).

[0386] 12. The method as described in Note 10, wherein:

[0387] Perform random access, including:

[0388] A resume request message is sent, wherein a resume cause of the resume request message is MT-access.

[0389] The network device side method of the first aspect embodiment:

[0390] 1. A method for performing small data transmission, applied to a network device, the method comprising:

[0391] Sending configuration information of small data transmission based on configuration authorization (CG-SDT config) to the terminal device; and

[0392] receiving a first resume request message, a second resume request message, or a third resume request message sent by the terminal device,

[0393] The resume cause of the first resume request message is MT-SDT.

[0394] The resume cause of the second resume request message is MT-SDT.

[0395] The resume cause (resume cause) of the third resume request (resume request) message is terminal terminated access (MT-access).

[0396] 2. The method as described in Note 1, wherein:

[0397] The first resume request message is received on a valid configuration grant opportunity (CG occasion).

[0398] 3. The method as described in Note 2, wherein:

[0399] The valid configuration authorization opportunity (CG occasion) includes:

[0400] Configuration Grant (CG) resources configured for the Small Data Transfer (SDT); and / or

[0401] The synchronization signal block (SSB) associated with the configuration grant (CG) resource is available (available); and / or

[0402] The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than the configured first threshold.

[0403] 4. The method according to any one of Notes 1 to 3, wherein:

[0404] The network device configures the one or more synchronization signal blocks (SSBs) associated with the configuration grant (CG) resource.

[0405] 5. The method as described in Note 3, wherein:

[0406] The configured first threshold is cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

[0407] 6. The method according to any one of Supplements 1 to 5, wherein

[0408] The network device configures a first offset for the terminal device, where the first offset is a parameter of the time interval between the initiation of a small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion) or the next configuration grant opportunity (CG occasion).

[0409] 6b. The method as described in Note 6, wherein the first offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

[0410] 7. The method according to any one of Supplementary Notes 1 to 5, wherein

[0411] The network device configures a second offset for the terminal device, where the second offset is a parameter of the time interval between the next valid configuration grant opportunity (CG occasion) or the next configuration grant opportunity (CG occasion) and an available random access opportunity (RA occasion).

[0412] 7b. The method as described in Note 7, wherein the second offset includes cg-SDT-MaxDurationToNext-CG-Occasion or a time offset different from cg-SDT-MaxDurationToNext-CG-Occasion.

Claims

1. A device for performing small data transmission, applied to a terminal device, the device comprising a first processing unit, the first processing unit controlling the terminal device so that the terminal device performs the following operations: Initiate a small data transfer (SDT); and When the next valid configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, a configuration grant-based small data transmission (CG-SDT) is performed.

2. The device according to claim 1, wherein: The effective configuration authorization opportunity (CG occasion) includes: Configuration Grant (CG) resources configured for the small data transfer (SDT); and / or A synchronization signal block (SSB) associated with a configuration grant (CG) resource is available (available); and / or The synchronization signal reference signal received power (SS-RSRP) of the synchronization signal block (SSB) associated with the configuration grant (CG) resource is higher than the configured first threshold.

3. The device as claimed in claim 2, wherein: The configured first threshold is cg-SDT-RSRP-ThresholdSSB or a reference signal received power (RSRP) threshold configured for terminal terminated small data transmission (MT-SDT) that is different from cg-SDT-RSRP-ThresholdSSB.

4. The device according to claim 1, wherein: The initiating of a small data transmission (SDT) comprises: The media access control (MAC) layer of the terminal device receives an indication from the radio resource control (RRC) layer to initiate a small data transmission (SDT); or The high-layer instruction of the terminal device initiates a small data transmission (SDT); or The media access control (MAC) layer of the terminal device evaluates whether a condition for initiating a small data transmission (SDT) is met; or The medium access control (MAC) layer of the terminal device evaluates whether the conditions for performing configuration-grant-based small data transmission (CG-SDT) are met.

5. The device according to claim 1, wherein: The satisfying of the predetermined condition in the time domain includes: The initiation of the small data transfer (SDT) and the next valid configuration grant opportunity (CG occasion) is less than the configured first offset; and / or There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next valid configuration authorization opportunity (CG occasion), or the time interval between the next valid configuration authorization opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

6. The device according to claim 5, wherein: The available random access opportunities (RA occasions) include: A random access opportunity for sending a random access preamble (RA preamble); or An available physical uplink shared channel opportunity (PUSCH occasion); or The random access opportunity for sending a random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) are the ones that arrive later.

7. The device of claim 1, wherein: If the predetermined condition is not satisfied, random access-based small data transmission (RA-SDT) or random access is performed.

8. The device according to claim 7, wherein: Perform random access-based small data transfer (RA-SDT), including: A resume request message is sent, wherein a resume cause of the resume request message is a MT-SDT.

9. The device according to claim 7, wherein: Perform random access, including: A resume request message is sent, wherein a resume cause of the resume request message is a terminal terminated access (MT-access).

10. A device for performing small data transmission, applied to a terminal device, the device comprising a second processing unit, the second processing unit controlling the terminal device so that the terminal device performs the following operations: Initiate a small data transfer (SDT); and When the next configuration grant opportunity (CG occasion) meets the predetermined conditions in the time domain, a configuration grant-based small data transmission (CG-SDT) is performed. in, The satisfying of the predetermined condition in the time domain includes: There is no available random access opportunity (RA occasion) between the initiation (initiation) of the small data transmission (SDT) and the next configured grant opportunity (CG occasion), or the time interval between the next configured grant opportunity (CG occasion) and the available random access opportunity (RA occasion) is less than the configured second offset.

11. The device of claim 10, wherein: The initiating of a small data transmission (SDT) comprises: The media access control (MAC) layer of the terminal device receives an indication from the radio resource control (RRC) layer to initiate a small data transmission (SDT); or The high-layer instruction of the terminal device initiates a small data transmission (SDT); or The media access control (MAC) layer of the terminal device evaluates whether a condition for initiating a small data transmission (SDT) is met; or The medium access control (MAC) layer of the terminal device evaluates whether the conditions for performing configuration-grant-based small data transmission (CG-SDT) are met.

12. The device of claim 10, wherein: The satisfying of the predetermined condition in the time domain also includes: The time interval between the initiation of the small data transmission (SDT) and the next configuration grant opportunity (CG occasion) is less than the configured first offset.

13. The device of claim 12, wherein: The available random access opportunities (RA occasions) include: A random access opportunity for sending a random access preamble (RA preamble); or An available physical uplink shared channel opportunity (PUSCH occasion); or The random access opportunity for sending a random access preamble (RA preamble) and the available physical uplink shared channel opportunity (PUSCH occasion) are the ones that arrive later.

14. The device of claim 10, wherein: If the predetermined condition is not satisfied, random access-based small data transmission (RA-SDT) or random access is performed.

15. The device of claim 14, wherein: Perform random access-based small data transfer (RA-SDT), including: A resume request message is sent, wherein a resume cause of the resume request message is a MT-SDT.

16. A device for performing small data transmission, applied to a network device, the device comprising a third processing unit, the third processing unit controlling the network device so that the network device performs the following operations: Sending configuration information of small data transmission based on configuration authorization (CG-SDT config) to the terminal device; and receiving a first resume request message, a second resume request message or a third resume request message sent by the terminal device, in, A resume cause of the first resume request message is a MT-SDT. A resume cause of the second resume request message is a MT-SDT. A resume cause (resume cause) of the third resume request (resume request) message is terminal terminated access (MT-access).

17. The device of claim 16, wherein: The network device receives the first recovery request message on a valid configuration grant opportunity (CG occasion).

18. The device of claim 16, wherein: The operations also include: The network device configures one or more synchronization signal blocks (SSBs) associated with the configuration grant (CG) resource.

19. The device of claim 16, wherein: The operations also include: The network device configures a first offset for the terminal device, where the first offset is a parameter of the time interval between the initiation of a small data transmission (SDT) and the next valid configuration grant opportunity (CG occasion) or the next configuration grant opportunity (CG occasion).

20. The device of claim 16, wherein: The operations also include: The network device configures a second offset for the terminal device, where the second offset is a parameter of the time interval between a next valid configuration grant opportunity (CG occasion) or a next configuration grant opportunity (CG occasion) and an available random access opportunity (RA occasion).

Images