Processing Method and Device for Small Data Transmission (SDT) to Fall Back to Non-SDT

Abstract

The embodiment of the present application discloses a method and apparatus for a small data transmission (SDT) to fallback to non-SDT, which can be applied to the cellular mobile communication technology. The method includes: during the SDT process of a terminal device, when it is determined that a specified trigger condition is met, the SDT process is fallback to a non-SDT process, so that the terminal device can fallback the SDT process to a non-SDT process before completing the SDT process, and thus the terminal device performs data transmission based on the non-SDT process, which is beneficial to reducing the service transmission delay.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method and apparatus for handling the fallback of small data transmission (SDT) to non-SDT. Background Art

[0002] In wireless communication technologies, a terminal device can transmit small data to a network device through a mechanism of small data transmission (SDT). Currently, after the random access channel (RACH) process of SDT is completed, the terminal device can establish a radio resource control (RRC) connection based on service requirements and transmit new uplink data based on the established RRC connection. That is, after the SDT process is completed, the terminal device communicates with the network device based on a non-SDT process. However, the above method of switching to a non-SDT process after the SDT process is completed easily leads to a large service transmission delay and affects the smooth progress of the communication process. Summary of the Invention

[0003] Embodiments of this application provide a method and apparatus for handling the fallback of small data transmission (SDT) to non-SDT, which can be applied to the scenario of communication between a terminal device and a network device in cellular mobile communication technologies, enabling the terminal device to fallback the SDT process to a non-SDT process before completing the SDT process, so that the terminal device transmits data based on the non-SDT process, which is beneficial to reducing the service transmission delay.

[0004] In a first aspect, embodiments of this application provide a method for handling the fallback of small data transmission (SDT) to non-SDT. The method is executed by a terminal device and includes: during the SDT process, in response to meeting a specified trigger condition, fallback the SDT process to a non-SDT process.

[0005] In this technical solution, during the SDT process of the terminal device, when it is determined that the specified trigger condition is met, the SDT process is fallback to a non-SDT process, enabling the terminal device to fallback the SDT process to a non-SDT process before completing the SDT process, so that the terminal device transmits data based on the non-SDT process, which is beneficial to reducing the service transmission delay.

[0006] In a possible implementation, the fallback of the SDT process to a non-SDT process includes: processing the connection configuration corresponding to the SDT process according to the connection configuration requirements of the non-SDT process.

[0007] In an alternative implementation manner, processing the connection configuration corresponding to the SDT process according to the connection configuration requirements of the non-SDT process includes at least one of the following processing actions: processing the radio bearer RB for the SDT process to resume data transmission according to the radio bearer RB requirements of the non-SDT process; resetting the MAC entity corresponding to the SDT process according to the medium access control MAC entity requirements of the non-SDT process; restarting the timer used in the SDT process or starting a new timer according to the timer requirements of the non-SDT process; processing the connection recovery request message corresponding to the SDT process according to the connection recovery request message requirements of the non-SDT process.

[0008] Optionally, the radio bearer RB requirements include any one of the following: suspending the RB; processing the packet data convergence protocol PDCP entity of the RB.

[0009] In a possible implementation manner, processing the packet data convergence protocol PDCP entity of the RB includes any one of the following: reconstructing the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process; transmitting the data packets of the PDCP entity of the RB when the non-SDT process has established a radio resource control RRC connection.

[0010] In an alternative implementation manner, transmitting the data packets of the PDCP entity of the RB includes any one of the following: transmitting the untransmitted data packets in the data packets of the PDCP entity of the RB when the transmission mode corresponding to the RB is the unacknowledged UM mode; transmitting the untransmitted data packets and / or the transmitted but not successfully acknowledged received data packets in the data packets of the PDCP entity of the RB when the transmission mode corresponding to the RB is the acknowledged mode.

[0011] Optionally, the connection recovery request message requirements include any one of the following: regenerating the connection recovery request message corresponding to the SDT process according to the security configuration information; reusing the connection recovery request message used in the SDT process.

[0012] In a possible implementation, the triggering condition includes any one of the following: receiving indication information sent by a network device, where the indication information is used to instruct the terminal device to fallback from the SDT process to the non-SDT process; determining that the number of data transmissions in the SDT process reaches a first threshold; determining that the data transmission volume corresponding to the data radio bearer in the SDT process reaches a second threshold; determining that the signal quality corresponding to the cell or beam supporting the SDT process reaches a third threshold; determining that the signal strength corresponding to the cell or beam supporting the SDT process reaches a fourth threshold; determining that the resource status of the configured grant CG physical uplink shared channel PUSCH resource supporting the SDT process is in an unavailable state.

[0013] In an alternative implementation, determining that the resource status of the configured grant CG physical uplink shared channel PUSCH resource supporting the SDT process is in an unavailable state includes any one of the following: in response to identifying a cell reselection from a cell supporting the CG PUSCH resource to a cell not supporting the CG PUSCH resource, determining that the resource status of the configured grant CG physical uplink shared channel PUSCH resource supporting the SDT process is in an unavailable state; in response to identifying that the uplink timing advance of the CG PUSCH resource fails, determining that the resource status of the configured grant CG physical uplink shared channel PUSCH resource supporting the SDT process is in an unavailable state.

[0014] Optionally, the indication information further includes the security configuration information.

[0015] In a possible implementation, the new security configuration information includes at least one of the following: a security algorithm, a security key, a next-hop chain count value for updating the security key, and a next-hop count value for updating the security key.

[0016] In a second aspect, an embodiment of the present application provides another method for processing the fallback of small data transmission (SDT) to non-SDT, which is executed by a network device. The method includes: sending indication information to a terminal device, where the indication information is used to instruct the terminal device to fallback from the SDT process to the non-SDT process during the SDT process.

[0017] In this technical solution, during the SDT process of the terminal device, the network device instructs the terminal device to fallback from the SDT process to the non-SDT process, so that the terminal device can fallback from the SDT process to the non-SDT process before completing the SDT process, and then the terminal device performs data transmission based on the non-SDT process, which is beneficial to reducing the service transmission delay.

[0018] In a possible implementation, the indication information further includes the security configuration information.

[0019] In another possible implementation, the security configuration information includes at least one of the following: a security algorithm, a security key, a next-hop chain count value for updating the security key, and a next-hop count value for updating the security key.

[0020] In a third aspect, an embodiment of the present application provides a processing device for a small data transmission (SDT) to fallback to non-SDT. This processing device for SDT to fallback to non-SDT has some or all of the functions of the terminal device in the method described in the first aspect above. For example, the functions of the processing device for SDT to fallback to non-SDT can have the functions of some or all of the embodiments in the present application, or can have the functions of any single embodiment in the present application implemented independently. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0021] In a fourth aspect, an embodiment of the present application provides another processing device for a small data transmission (SDT) to fallback to non-SDT. This processing device for SDT to fallback to non-SDT has some or all of the functions of the network device in the method example described in the second aspect above. For example, the functions of the processing device for SDT to fallback to non-SDT can have the functions of some or all of the embodiments in the present application, or can have the functions of any single embodiment in the present application implemented independently. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0022] In a fifth aspect, an embodiment of the present application provides a processing device for a small data transmission (SDT) to fallback to non-SDT. The device includes a processor, and when the processor calls a computer program in a memory, it executes the method described in the first aspect above.

[0023] In a sixth aspect, an embodiment of the present application provides a processing device for a small data transmission (SDT) to fallback to non-SDT. The device includes a processor, and when the processor calls a computer program in a memory, it executes the method described in the second aspect above.

[0024] In a seventh aspect, an embodiment of the present application provides a processing device for a small data transmission (SDT) to fallback to non-SDT. The device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory so that the device executes the method described in the first aspect above.

[0025] In an eighth aspect, an embodiment of the present application provides a processing device for small data transmission (SDT) to fallback to non-SDT. The device includes a processor and a memory, and a computer program is stored in the memory. The processor executes the computer program stored in the memory so that the device executes the method described in the second aspect above.

[0026] In a ninth aspect, an embodiment of the present application provides a processing device for small data transmission (SDT) to fallback to non-SDT. The device includes a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, and the processor is configured to run the code instructions so that the device executes the method described in the first aspect above.

[0027] In a tenth aspect, an embodiment of the present application provides a processing device for small data transmission (SDT) to fallback to non-SDT. The device includes a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, and the processor is configured to run the code instructions so that the device executes the method described in the second aspect above.

[0028] In an eleventh aspect, an embodiment of the present application provides a communication system. The system includes the processing device for small data transmission (SDT) to fallback to non-SDT described in the third aspect and the processing device for small data transmission (SDT) to fallback to non-SDT described in the fourth aspect. Alternatively, the system includes the processing device for small data transmission (SDT) to fallback to non-SDT described in the fifth aspect and the processing device for small data transmission (SDT) to fallback to non-SDT described in the sixth aspect. Alternatively, the system includes the processing device for small data transmission (SDT) to fallback to non-SDT described in the seventh aspect and the processing device for small data transmission (SDT) to fallback to non-SDT described in the eighth aspect. Alternatively, the system includes the processing device for small data transmission (SDT) to fallback to non-SDT described in the ninth aspect and the processing device for small data transmission (SDT) to fallback to non-SDT described in the tenth aspect.

[0029] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above network device. When the instructions are executed, the terminal device is caused to execute the method described in the first aspect above.

[0030] In a thirteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above terminal device. When the instructions are executed, the network device is caused to execute the method described in the second aspect above.

[0031] In a fourteenth aspect, the present application further provides a computer program product including a computer program. When it runs on a computer, the computer is caused to execute the method described in the first aspect above.

[0032] In a fifteenth aspect, the present application further provides a computer program product including a computer program, which, when running on a computer, causes the computer to execute the method described in the second aspect above.

[0033] In a sixteenth aspect, the present application provides a chip system, which includes at least one processor and an interface, and is used to support a network device to implement the functions involved in the first aspect. For example, it is used to determine or process at least one of the data and information involved in the above method. In a possible design, the chip system further includes a memory, and the memory is used to store the necessary computer programs and data of the network device. This chip system can be composed of chips or can include chips and other discrete devices.

[0034] In a seventeenth aspect, the present application provides a chip system, which includes at least one processor and an interface, and is used to support a terminal device to implement the functions involved in the second aspect. For example, it is used to determine or process at least one of the data and information involved in the above method. In a possible design, the chip system further includes a memory, and the memory is used to store the necessary computer programs and data of the terminal device. This chip system can be composed of chips or can include chips and other discrete devices.

[0035] In an eighteenth aspect, the present application provides a computer program, which, when running on a computer, causes the computer to execute the method described in the first aspect above.

[0036] In a nineteenth aspect, the present application provides a computer program, which, when running on a computer, causes the computer to execute the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the following will describe the drawings required to be used in the embodiments of the present application or the background technology.

[0038] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

[0039] Figure 2 is a schematic flowchart of a processing method for a small data transmission (SDT) to fall back to non-SDT provided by an embodiment of the present application;

[0040] Figure 3 is a schematic flowchart of another processing method for a small data transmission (SDT) to fall back to non-SDT provided by an embodiment of the present application;

[0041] Figure 4 is a schematic flowchart of another processing method for a small data transmission (SDT) to fall back to non-SDT provided by an embodiment of the present application;

[0042] Figure 5 is a schematic flowchart of another method for handling the fallback of small data transmission (SDT) to non - SDT provided by an embodiment of the present application;

[0043] Figure 6 is a schematic flowchart of another method for handling the fallback of small data transmission (SDT) to non - SDT provided by an embodiment of the present application;

[0044] Figure 7 is a schematic structural diagram of an apparatus for handling the fallback of small data transmission (SDT) to non - SDT provided by an embodiment of the present application;

[0045] Figure 8 is a schematic structural diagram of another apparatus for handling the fallback of small data transmission (SDT) to non - SDT provided by an embodiment of the present application;

[0046] Figure 9 is a schematic structural diagram of a chip provided by an embodiment of the present application. Detailed implementation manners

[0047] To better understand a method for handling the fallback of small data transmission (SDT) to non - SDT disclosed in an embodiment of the present application, the communication system applicable to the embodiment of the present application will be described first below.

[0048] Please refer to Figure 1 , Figure 1 , which is a schematic architecture diagram of a communication system provided by an embodiment of the present application. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of the devices shown are only for illustration and do not constitute a limitation on the embodiments of the present application. In practical applications, there may be two or more network devices and two or more terminal devices. Figure 1 Taking the communication system including a network device 101 and a terminal device 102 as an example.

[0049] It should be noted that the technical solutions of the embodiments of the present application can be applied to various communication systems. For example: Long Term Evolution (LTE) system, 5th generation (5G) mobile communication system, 5G New Radio (NR) system, or other future new mobile communication systems, etc.

[0050] The network device 101 in the embodiments of this application is an entity on the network side for transmitting or receiving signals. For example, the network device 101 may be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system, etc. The embodiments of this application do not limit the specific technologies and specific device forms adopted by the network device. The network device provided by the embodiments of this application may be composed of a central unit (CU) and a distributed unit (DU). Among them, the CU may also be referred to as a control unit. Adopting the CU-DU structure can split the protocol layer of the network device, such as a base station. The functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0051] The terminal device 102 in the embodiments of this application is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal device may be an automobile with communication functions, a smart automobile, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and so on. The embodiments of this application do not limit the specific technologies and specific device forms adopted by the terminal device.

[0052] In the above communication system, after the SDT process is usually completed, when the terminal device has a non-SDT process requirement, the terminal device uses the non-SDT process to transmit data with the network device. However, this method is likely to cause a relatively large service transmission delay, affecting the smooth progress of the communication process.

[0053] In the embodiments of the present application, during the SDT process of the terminal device, when it is determined that the specified trigger condition is met, the SDT process is rolled back to the non-SDT process, so that the terminal device can roll back the SDT process to the non-SDT process before completing the SDT process. Thus, the terminal device performs data transmission based on the non-SDT process, which is beneficial to reducing the service transmission delay.

[0054] It can be understood that the communication system described in the embodiments of the present application is to more clearly illustrate the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0055] The following describes in detail the method and device for handling the rollback of small data transmission (SDT) to non-SDT provided by the present application with reference to the accompanying drawings.

[0056] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of a method for handling the rollback of small data transmission (SDT) to non-SDT provided by an embodiment of the present application. This method is applied to Figure 1 the terminal device in the communication system shown. That is to say, this method is executed by Figure 1 the terminal device in the communication system shown, as Figure 2 shown, this method may include but is not limited to the following steps:

[0057] Step S201: During the SDT process, in response to meeting the specified trigger condition, roll back the SDT process to the non-SDT process.

[0058] In some embodiments, during the SDT process, the small data may be transmitted to the network device using the third message Msg3 in the four-step random access process.

[0059] In some embodiments, during the SDT process, the small data may be transmitted to the network device using the first message MsgA in the two-step random access process.

[0060] In some embodiments, during the SDT process, small data can be transmitted to the network device by configuring and authorizing Physical Uplink Shared Channel (PUSCH) resources.

[0061] Among them, the above-mentioned configured and authorized Physical Uplink Shared Channel (PUSCH) resources can be pre-configured by the network device for the terminal device.

[0062] Among them, the non-SDT process means that no service data is sent during the random access process of initial access, but only the Radio Resource Control (RRC) message of the Common Control Channel (CCCH) is sent, and service data transmission is performed after the RRC connection is restored.

[0063] The above-specified triggering condition refers to the condition for triggering the fallback from the SDT process to the non-SDT process.

[0064] In some embodiments, the above triggering condition may be: receiving indication information sent by the network device, where the indication information is used to indicate the terminal device to fallback from the SDT process to the non-SDT process.

[0065] In some other embodiments, the above triggering condition may be: determining that the number of data transmissions in the SDT process reaches a first threshold value.

[0066] In a possible implementation manner, the above first threshold value can be configured by the network device for the terminal device, or can be determined by the terminal device based on the communication standard used for communication with the network device. This embodiment does not specifically limit the acquisition method of the first threshold value.

[0067] In some other embodiments, the above triggering condition may be: determining that the data transmission volume corresponding to the Radio Bearer (RB) in the SDT process reaches a second threshold value.

[0068] Among them, the above DRB is used to send the service data of the terminal device.

[0069] Among them, the above DRB is used to send the service data of the terminal device.

[0070] For example, when transmitting uplink data of network configuration DRB-1, SDT can be selected, and the data volume of the uplink data needs to be less than or equal to 1000 bytes (i.e., the second threshold). If 500 bytes of uplink data arrive at DRB-1, the SDT process is selected. However, before the uplink data in the SDT process is successfully transmitted, an additional 600 bytes of data arrive at DRB-1. At this time, the data volume to be transmitted of DRB-1 is 1100 bytes, exceeding the network configuration of 1000 bytes, that is, exceeding the second threshold of the network configuration. At this time, it can be determined that the trigger condition for falling back from the SDT process to the non-SDT process is met.

[0071] It can be understood that to support data transmission and reception of the terminal device, different data types can be used for data transmission and reception through different radio bearers.

[0072] The radio bearers in this embodiment may include Data Radio Bearer (DRB) and signalling radio bearers (SRB).

[0073] The above SRB is used to transmit Radio Resource Control (RRC) control signalling.

[0074] The above SRB can be divided into SRB0, SRB1, SRB2, and SRB3.

[0075] SRB0: Used to transmit RRC messages of the Common Control Channel (CCCH).

[0076] SRB1: Used to transmit RRC messages of the Dedicated Control Channel (DCCH), and NAS (Non-Access Stratum) messages can be carried in the RRC messages. It is also used to transmit NAS messages before SRB2 is established.

[0077] SRB2: Used to transmit NAS messages of the DCCH logical channel and RRC messages containing path measurement information.

[0078] It should be noted that the above SRB2 has a lower priority than SRB1 and is configured by the network side after the activation of AS (Access Stratum) security.

[0079] SRB3: When the terminal device is configured with a non-standalone networking mode, it is used to send RRC messages on the DCCH logical channel for the SCG (Secondary Cell Group). Among them, the above non-standalone networking mode may include EUTRA-NR Dual Connection (EN-DC) with a 4G primary node and a 5G secondary node, and New Radio Dual Connection (NR-DC) with a 5G primary node and a 4G secondary node.

[0080] In a possible implementation, the above second threshold may be configured by the network device for the terminal device, or may be determined by the terminal device based on the communication standard used for communication with the network device. This embodiment does not specifically limit the acquisition method of the second threshold.

[0081] In some other embodiments, it is determined that the signal quality corresponding to the cell or beam supporting the SDT process reaches a third threshold.

[0082] In a possible implementation, the above third threshold may be configured by the network device for the terminal device, or may be determined by the terminal device based on the communication standard used for communication with the network device. This embodiment does not specifically limit the acquisition method of the third threshold.

[0083] In some embodiments, the above signal quality may be the Reference Signal Received Power (RSRP).

[0084] In some other embodiments, it is determined that the signal strength corresponding to the cell or beam supporting the SDT process reaches a fourth threshold.

[0085] In some embodiments, the above signal strength may be the Reference Signal Receiving Power (RSRP).

[0086] In a possible implementation, the above beam may be determined based on Synchronous Signal Block (SSB) information.

[0087] In another possible implementation, the above beam may be determined based on Channel State Information–Reference Signal (CSI-RS) information.

[0088] In another possible implementation, the above beam can be determined based on SSB and CSI-RS information.

[0089] As an exemplary implementation, the network device may send configuration information to the terminal device, where the configuration information may include SSB and / or CSI-RS information. Correspondingly, the terminal device may determine the corresponding beam based on the SSB and / or CSI-RS information.

[0090] In a possible implementation, the above fourth threshold may be configured by the network device for the terminal device, or may be determined by the terminal device based on the communication standard used for communication with the network device. The embodiment does not specifically limit the acquisition method of the fourth threshold.

[0091] In some other embodiments, the above trigger condition may be: determining that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state.

[0092] In a possible implementation, in response to identifying a cell reselection from a cell that supports the CG PUSCH resource to a cell that does not support the CG PUSCH resource, it is determined that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state. That is, in the case of identifying a cell reselection from a cell that supports the SDT CG resource to a cell that does not support the SDT CG resource, it is determined that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state.

[0093] In another possible implementation, in response to identifying that the uplink timing advance (TA) of the CG PUSCH resource fails, it is determined that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state.

[0094] As another possible implementation, the above trigger condition may be determining that the data transmission volume corresponding to the radio bearer (RB) in the SDT process reaches a second threshold, and determining that the signal quality corresponding to the cell or beam that supports the SDT process reaches a third threshold.

[0095] For example, the network device instructs the terminal device to trigger the SDT process as follows: the measured signal value RSRP of cell - 1 is greater than or equal to the threshold value - 1, and the amount of uplink data needs to be less than or equal to 1000 bytes. When 500 bytes of uplink data of the SDT DRB - 1 of the terminal device arrives and the RSRP of cell - 1 exceeds the threshold value - 1, the terminal device triggers the SDT process. However, before the uplink data in the SDT process is successfully sent, if it is detected that the RSRP value of cell - 1 of the terminal device is less than the threshold value - 1, it is determined that the trigger condition for falling back from the SDT process to the non - SDT process is met.

[0096] For another example, the network device instructs the terminal device to trigger the SDT process as follows: the measured signal value RSRP of beam - 1 is greater than or equal to the threshold value - 1, and the amount of uplink data needs to be less than or equal to 1000 bytes. When 500 bytes of uplink data of the SDT DRB - 1 of the terminal device arrives and the RSRP of beam - 1 exceeds the threshold value - 1, the terminal device triggers the SDT process. However, before the uplink data in the SDT process is successfully sent, if it is detected that the RSRP value of beam - 1 of the terminal device is less than the threshold value - 1, it is determined that the trigger condition for falling back from the SDT process to the non - SDT process is met.

[0097] It should be noted that this embodiment is only an exemplary illustration of the above - mentioned trigger conditions. In practical applications, other trigger conditions can also be set according to actual service requirements, and this embodiment does not make specific limitations in this regard.

[0098] In the embodiment of the present application, during the SDT process of the terminal device, when it is determined that the specified trigger condition is met, the SDT process is fallen back to the non - SDT process, so that the terminal device can fall back the SDT process to the non - SDT process before completing the SDT process. Thus, the terminal device performs data transmission based on the non - SDT process, which is beneficial to reducing the service transmission delay.

[0099] Please refer to Figure 3 , Figure 3 which is a schematic flowchart of another method for handling the fallback of small data transmission (SDT) to non - SDT provided by the embodiment of the present application. This method is applied to the Figure 1 terminal device in the communication system shown. As shown in Figure 3 , this method may include but is not limited to the following steps:

[0100] Step S301: During the SDT process, in response to meeting the specified trigger condition, process the connection configuration corresponding to the SDT process according to the connection configuration requirements of the non - SDT process.

[0101] In some embodiments, during the SDT process, small data can be transmitted to the network device using the third message Msg3 in the four-step random access process.

[0102] In some embodiments, during the SDT process, small data can be transmitted to the network device using the first message MsgA in the two-step random access process.

[0103] In some embodiments, during the SDT process, small data can be transmitted to the network device by configuring grant CG Physical Uplink Shared Channel (PUSCH) resources.

[0104] Among them, the above-mentioned configured grant CG Physical Uplink Shared Channel (PUSCH) resources can be pre-configured by the network device for the terminal device.

[0105] The above-specified triggering condition refers to the condition for triggering the fallback from the SDT process to the non-SDT process.

[0106] In some embodiments, the above triggering condition can be: receiving indication information sent by the network device, where the indication information is used to indicate the terminal device to fallback from the SDT process to the non-SDT process.

[0107] In some other embodiments, the above triggering condition can be: determining that the number of data transmissions in the SDT process reaches a first threshold.

[0108] In a possible implementation, the above first threshold can be configured by the network device for the terminal device, or can be determined by the terminal device based on the communication standard used for communication with the network device. The embodiment does not specifically limit the acquisition method of the first threshold.

[0109] In some other embodiments, the above triggering condition can be: determining that the data transmission volume corresponding to the data radio bearer (DRB) in the SDT process reaches a second threshold.

[0110] Among them, the above DRB is used to transmit the service data of the terminal device.

[0111] For example, the uplink data transmission of network configuration DRB-1 can select SDT, and the data volume of the uplink data needs to be less than or equal to 1000 bytes (i.e., the second threshold). If 500 bytes of uplink data arrives at DRB-1, the SDT process is selected. However, before the uplink data in the SDT process is successfully transmitted, an additional 600 bytes of data arrives at DRB-1. At this time, the data volume to be transmitted of DRB-1 is 1100 bytes, exceeding the network configuration of 1000 bytes, that is, exceeding the second threshold of the network configuration. At this time, it can be determined that the trigger condition for falling back from the SDT process to the non-SDT process is satisfied.

[0112] Among them, it can be understood that in order to support data transmission and reception of terminal devices, different data types can perform data transmission and reception through different radio bearers.

[0113] The radio bearers in this embodiment may include Data Radio Bearer (DRB) and signalling radio bearers (SRB).

[0114] The above SRB is used to send Radio Resource Control (RRC) control signalling.

[0115] The above SRB can be divided into SRB0, SRB1, SRB2, and SRB3.

[0116] SRB0: Used to send RRC messages of the Common Control Channel (CCCH).

[0117] SRB1: Used to send RRC messages of the Dedicated Control Channel (DCCH). NAS (Non-Access Stratum) messages can be carried in the RRC messages. It is also used to send NAS messages before SRB2 is established.

[0118] SRB2: Used to send NAS messages of the DCCH logical channel and RRC messages containing path measurement information.

[0119] Among them, it should be noted that the above SRB2 has a lower priority than SRB1 and is configured by the network side after the AS (Access Stratum) security is activated.

[0120] SRB3: When the terminal device is configured with a non-standalone networking mode, it is used to send RRC messages on the DCCH logical channel for the SCG (Secondary Cell Group). Among them, the above non-standalone networking mode may include the EUTRA-NR Dual Connection (EN-DC) with a 4G primary node and a 5G secondary node, and the New Radio Dual Connection (NR-DC) with a 5G primary node and a 4G secondary node.

[0121] In a possible implementation, the above second threshold may be configured by the network device for the terminal device, or may be determined by the terminal device based on the communication standard used for communication with the network device. This embodiment does not specifically limit the acquisition method of the second threshold.

[0122] In other embodiments, it is determined that the signal quality corresponding to the cell or beam supporting the SDT process reaches a third threshold.

[0123] In a possible implementation, the above third threshold may be configured by the network device for the terminal device, or may be determined by the terminal device based on the communication standard used for communication with the network device. This embodiment does not specifically limit the acquisition method of the third threshold.

[0124] In some embodiments, the above signal quality may be the Reference Signal Received Power (RSRP).

[0125] In other embodiments, it is determined that the signal strength corresponding to the cell or beam supporting the SDT process reaches a fourth threshold.

[0126] In some embodiments, the above signal strength may be the Reference Signal Receiving Power (RSRP).

[0127] In a possible implementation, the above beam may be determined based on the Synchronous Signal Block (SSB) information.

[0128] In another possible implementation, the above beam may be determined based on the Channel State Information–Reference Signal (CSI-RS) information.

[0129] In another possible implementation, the above beam can be determined based on SSB and CSI-RS information.

[0130] As an exemplary implementation, the network device may send configuration information to the terminal device, where the configuration information may include SSB and / or CSI-RS information. Correspondingly, the terminal device may determine the corresponding beam based on the SSB and / or CSI-RS information.

[0131] In a possible implementation, the above fourth threshold may be configured by the network device for the terminal device, or may be determined by the terminal device based on the communication standard used for communication with the network device. The embodiment does not specifically limit the acquisition method of the fourth threshold.

[0132] In some other embodiments, the above trigger condition may be: determining that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state.

[0133] In a possible implementation, in response to identifying a cell reselection from a cell that supports the CG PUSCH resource to a cell that does not support the CG PUSCH resource, it is determined that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state. That is, in the case of identifying a cell reselection from a cell that supports the SDT CG resource to a cell that does not support the SDT CG resource, it is determined that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state.

[0134] In another possible implementation, in response to identifying that the uplink timing advance (TA) of the CG PUSCH resource fails, it is determined that the resource status of the configured grant CG physical uplink shared channel PUSCH resource that supports the SDT process is in an unavailable state.

[0135] As another possible implementation, the above trigger condition may be determining that the data transmission volume corresponding to the radio bearer (RB) in the SDT process reaches a second threshold, and determining that the signal quality corresponding to the cell or beam that supports the SDT process reaches a third threshold.

[0136] For example, the network device instructs the terminal device to trigger the SDT process as follows: the measured signal value RSRP of cell - 1 is greater than or equal to the threshold value - 1, and the amount of uplink data needs to be less than or equal to 1000 bytes. When 500 - byte uplink data arrives at the SDT DRB - 1 of the terminal device and the RSRP of cell - 1 exceeds the threshold value - 1, the terminal device triggers the SDT process. However, before the uplink data in the SDT process is successfully sent, if it is detected that the RSRP value of cell - 1 of the terminal device is less than the threshold value - 1, it is determined that the trigger condition for falling back from the SDT process to the non - SDT process is met.

[0137] Another example is that the network device instructs the terminal device to trigger the SDT process as follows: the measured signal value RSRP of beam - 1 is greater than or equal to the threshold value - 1, and the amount of uplink data needs to be less than or equal to 1000 bytes. When 500 - byte uplink data arrives at the SDT DRB - 1 of the terminal device and the RSRP of beam - 1 exceeds the threshold value - 1, the terminal device triggers the SDT process. However, before the uplink data in the SDT process is successfully sent, if it is detected that the RSRP value of beam - 1 of the terminal device is less than the threshold value - 1, it is determined that the trigger condition for falling back from the SDT process to the non - SDT process is met.

[0138] It should be noted that this embodiment is only an exemplary illustration of the above - mentioned trigger conditions. In actual applications, other trigger conditions can also be set according to actual service requirements, and this embodiment does not make specific limitations in this regard.

[0139] In the embodiment of this application, during the SDT process of the terminal device, when triggering the fallback from the SDT process to the non - SDT process, based on the connection configuration requirements of the non - SDT process, the connection configuration of the SDT process is processed, so that the terminal device can fall back from the SDT process to the non - SDT process before completing the SDT process, and then the terminal device performs data transmission based on the non - SDT process, which is beneficial to reducing the service transmission delay.

[0140] In some embodiments, the processing of the connection configuration corresponding to the SDT process according to the connection configuration requirements of the non - SDT process includes at least one of the following processing actions:

[0141] Process the RB for resuming data transmission in the SDT process according to the radio carrier RB requirements of the non - SDT process.

[0142] Reset the MAC entity corresponding to the SDT process according to the medium access control MAC entity requirements of the non - SDT process.

[0143] Restart the timer used in the SDT process or start a new timer according to the timer requirements of the non - SDT process.

[0144] Process the connection restoration request message corresponding to the SDT process according to the requirements of the connection restoration request message of the non-SDT process.

[0145] It should be noted that the above reset MAC entity can abandon behaviors such as the random access process in the MAC entity, so that the terminal device can re-initiate the connection establishment restoration.

[0146] In this embodiment, during the SDT process, when the SDT process is rolled back to the non-SDT process, the connection configuration of the SDT process is processed, which can avoid the loss of service data during the rollback operation and improve the data transmission quality.

[0147] Please refer to Figure 4 , Figure 4 which is a schematic flow chart of another method for processing the rollback of small data transmission (SDT) to non-SDT provided by the embodiment of the present application. This method is applied to the Figure 1 terminal device in the communication system shown. As Figure 4 shown, this method may include but is not limited to the following steps:

[0148] Step S401: During the SDT process, in response to meeting the trigger condition for rolling back from the SDT process to the non-SDT process, process the radio bearer (RB) for resuming data transmission in the SDT process according to the requirements of the non-SDT process for the radio bearer RB.

[0149] It should be noted that for the trigger condition, reference can be made to the relevant description in the above embodiment, which will not be elaborated here.

[0150] In this embodiment, during the SDT process, when the SDT process is rolled back to the non-SDT process, processing the radio bearer (RB) for resuming data transmission in the SDT process according to the requirements of the non-SDT process for the radio bearer RB can avoid the loss of service data during the rollback operation and improve the data transmission quality.

[0151] In some embodiments, the above requirements for the radio bearer RB may be suspended RBs.

[0152] In an exemplary implementation, the above requirements for the radio bearer RB may be the PDCP entity and the radio link control (RLC) entity of the suspended RB.

[0153] In another exemplary implementation, the above requirements for the radio bearer RB may be to process the packet data convergence protocol (PDCP) entity of the RB.

[0154] In some embodiments, a possible implementation of processing the Packet Data Convergence Protocol (PDCP) entity of the RB is as follows: Reconstruct the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process.

[0155] As an example, when the transmission mode corresponding to the RB is the Unacknowledged Mode (UM), the behavior of reconstructing the PDCP entity of the RB is as follows: For each PDCP Service Data Unit (PDCP SDU) associated with a PDCP Sequence Number (SN) and not yet delivered to the lower layer protocol entity, treat this PDCP SDU as the first one received and processed from the upper layer, and perform transmission in ascending order according to the COUNT value associated with this PDCP SDU. For the running discard timer (discard Timer) associated with this PDCP SDU, continue to run (i.e., do not restart the discardTimer), so as to continue transmitting the data that has not been sent during the SDT process during the non-SDT process and avoid data loss.

[0156] As another example, for the DRB in the RLC AM mode in the suspended state, the behavior of reconstructing the PDCP entity of the RB is as follows: For each PDCP SDU associated with a PDCP SN, starting from the first PDCP SDU that has not been successfully acknowledged by the lower layer protocol entity for transmission, treat this PDCP SDU as the first one received and processed from the upper layer, and perform transmission in ascending order according to the COUNT value associated with this PDCP SDU. For the running discard timer (discard Timer) associated with this PDCP SDU, continue to run (i.e., do not restart the discardTimer), so as to continue transmitting the data that has not been sent during the SDT process during the non-SDT process and avoid data loss.

[0157] As another example, for the DRB in the RLC AM mode in the non-suspended state, the behavior of reconstructing the PDCP entity of the RB is as follows: For each PDCP SDU associated with a PDCP SN, for all PDCP SDUs (i.e., starting from the first PDCP SDU that has not been determined to be successfully sent by the lower layer protocol entity, including PDCP SDUs that have been successfully acknowledged and not successfully acknowledged by the lower layer), perform transmission in ascending order according to the COUNT value associated with this PDCP SDU.

[0158] In some other embodiments, another possible implementation of processing the PDCP entity of the RB is as follows:

[0159] When a Radio Resource Control (RRC) connection has been established during the non-SDT process, transmit the data packets of the PDCP entity of the RB.

[0160] In this embodiment, the RRC connection established in the above non-SDT process includes any one of the following: the random access process has been successfully completed; a connection resume (RRC Resume) message has been received; a connection setup (RRC Setup) message has been received.

[0161] As an exemplary implementation manner, when the terminal device starts to send an RRC connection resume request message, the timer starts timing. If the terminal device receives a connection resume (RRC Resume) message or a connection setup (RRC Setup) message from the network device side during the running of the timer, it is determined that the terminal device has established an RRC connection.

[0162] Optionally, a possible implementation manner for transmitting the data packets of the PDCP entity of the RB is as follows: when the transmission mode corresponding to the RB is the unacknowledged UM mode, the data packets that have not been sent in the data packets of the PDCP entity of the RB are transmitted.

[0163] In this embodiment, by transmitting the data packets that have not been sent in the SDT process in the non-SDT process, the occurrence of data loss is avoided, and the data transmission quality is improved.

[0164] Optionally, another possible implementation manner for transmitting the data packets of the PDCP entity of the RB is as follows: when the transmission mode corresponding to the RB is the acknowledged mode, the data packets that have not been sent and / or the data packets that have been sent but not successfully received and acknowledged in the data packets of the PDCP entity of the RB are transmitted.

[0165] Please refer to Figure 5 , Figure 5 which is a schematic flowchart of another method for handling the fallback from small data transmission (SDT) to non-SDT provided by the embodiment of the present application. This method is applied to Figure 1 the terminal device in the communication system shown in Figure 5 . As shown in

[0166] Step S501: In the SDT process, an indication message sent by the network device is received, where the indication message is used to indicate that the terminal device falls back from the SDT process to the non-SDT process.

[0167] Step S502: According to the security configuration information carried in the indication message, the connection resume request message corresponding to the SDT process is regenerated.

[0168] That is to say, in addition to carrying the indication of falling back from the SDT process to the non-SDT process, the indication message in this embodiment also carries security configuration information.

[0169] In some embodiments, the above security configuration information includes at least one of the following: a security algorithm, a security key, a next-hop chain count value for updating the security key, and a next-hop count value for updating the security key.

[0170] It can be understood that, on the basis of including the above step S502, the method of this embodiment may further include at least one of the following steps: Processing the radio carrier RBs for resuming data transmission in the SDT process according to the radio carrier RB requirements of the non-SDT process. Resetting the MAC entity corresponding to the SDT process according to the medium access control (MAC) entity requirements of the non-SDT process. Restarting the timer used in the SDT process or starting a new timer according to the timer requirements of the non-SDT process.

[0171] In another exemplary implementation, during the SDT process, in response to meeting the trigger condition for falling back from the SDT process to the non-SDT process, the connection recovery request message corresponding to the SDT process can be reused according to the requirements of the connection recovery request message of the non-SDT process. That is to say, when falling back to the non-SDT process, in the case of performing RRC connection recovery on the terminal device, the connection recovery request message corresponding to the SDT process can be used for RRC connection recovery, thereby realizing the connection recovery of the non-SDT process.

[0172] As an exemplary implementation, during the SDT process of the terminal device, the connection recovery request message generated for the SDT process can be stored in the cache, and when the trigger condition for falling back from SDT to non-SDT is detected, the connection recovery request message that could be used in the previous SDT process can be read from the cache, and in the non-SDT process, RRC connection recovery is also performed based on the read connection recovery request message, and data transmission is performed based on the recovered RRC connection.

[0173] It should be noted that, in this exemplary implementation, in addition to including the processing of reusing the connection recovery request message corresponding to the SDT process according to the requirements of the connection recovery request message of the non-SDT process, this embodiment may further include at least one of the following processes: Processing the radio carrier RBs for resuming data transmission in the SDT process according to the radio carrier RB requirements of the non-SDT process. Resetting the MAC entity corresponding to the SDT process according to the medium access control (MAC) entity requirements of the non-SDT process. Restarting the timer used in the SDT process or starting a new timer according to the timer requirements of the non-SDT process.

[0174] It should be noted that the above trigger condition can refer to the relevant descriptions of the above other embodiments, and this embodiment will not elaborate on it.

[0175] Please refer to Figure 6 ,Figure 6 is a schematic flowchart of another method for processing the fallback of Small Data Transfer (SDT) to non-SDT provided by an embodiment of this application. This method is applied to Figure 1 a network device in the communication system shown. That is to say, this method can be executed by Figure 1 a network device in the communication system shown. As shown in Figure 6 the method may include but is not limited to the following steps:

[0176] Step S601: Send indication information to the terminal device, where the indication information is used to indicate that during the SDT process of the terminal device, it falls back from the SDT process to the non-SDT process.

[0177] In the embodiment of this application, during the SDT process of the terminal device, the network device instructs the terminal device to fall back from the SDT process to the non-SDT process, so that the terminal device can fall back from the SDT process to the non-SDT process before completing the SDT process, and then the terminal device performs data transmission based on the non-SDT process, which is beneficial to reducing the service transmission delay.

[0178] Based on the above embodiments, during the SDT process of the terminal device, in order to further enhance the communication security, the above indication information may further include security configuration information.

[0179] Correspondingly, the terminal device can determine the connection recovery request message used in the non-SDT process according to the security configuration information.

[0180] As another exemplary implementation manner, the terminal device can generate a new security key according to the security configuration information indicated by the network device, and based on the new security key, determine the connection recovery request message used in the non-SDT process.

[0181] In some embodiments, the above security configuration information may include at least one of the following: security algorithm, security key, next-hop chain count value for updating the security key, and next-hop count value for updating the security key.

[0182] In the above embodiments provided by this application, the methods provided by the embodiments of this application are introduced from the perspectives of the network device and the terminal device respectively. To implement each function in the methods provided by the above embodiments of this application, the network device and the terminal device may include a hardware structure and software modules, and implement the above functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. A certain function among the above functions can be executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module.

[0183] Please refer to Figure 7 , Figure 7It is a schematic structural diagram of a processing device 70 for small data transmission (SDT) to fallback to non-SDT provided by an embodiment of the present application. Figure 7 The shown processing device 70 for small data transmission (SDT) to fallback to non-SDT may include a transceiver unit 701 and a processing unit 702. The transceiver unit 701 may include a sending unit and / or a receiving unit. The sending unit is used to implement the sending function, and the receiving unit is used to implement the receiving function. The transceiver unit 701 can implement the sending function and / or the receiving function.

[0184] The processing device 70 for small data transmission (SDT) to fallback to non-SDT can be a network device, or a device in a network device, or a device that can be used in matching with a network device. Alternatively, the processing device 70 for small data transmission (SDT) to fallback to non-SDT can be a terminal device, or a device in a terminal device, or a device that can be used in matching with a terminal device.

[0185] When the processing device 70 for small data transmission (SDT) to fallback to non-SDT is a terminal device: a processing module 701, configured to, during the SDT process, in response to meeting a specified trigger condition, fallback the SDT process to a non-SDT process.

[0186] In a possible implementation manner, the above-mentioned processing module 701 is specifically configured to: process the connection configuration corresponding to the SDT process according to the connection configuration requirements of the non-SDT process.

[0187] In a possible implementation manner, the processing module 701 includes at least one of the following processing actions:

[0188] Process the radio bearer (RB) for resuming data transmission in the SDT process according to the RB requirements of the non-SDT process.

[0189] Reset the MAC entity corresponding to the SDT process according to the medium access control (MAC) entity requirements of the non-SDT process.

[0190] Restart the timer used in the SDT process or start a new timer according to the timer requirements of the non-SDT process.

[0191] Process the connection recovery request message corresponding to the SDT process according to the connection recovery request message requirements of the non-SDT process.

[0192] In an alternative implementation manner, the above-mentioned RB requirements include any one of the following: suspend the RB; process the packet data convergence protocol (PDCP) entity of the RB.

[0193] In an exemplary embodiment, the PDCP entity and the radio link control (RLC) entity of the RB can be suspended.

[0194] In an alternative implementation, processing the packet data convergence protocol (PDCP) entity of the radio bearer (RB) includes any one of the following: reconstructing the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process; transmitting the data packets of the PDCP entity of the RB when a radio resource control (RRC) connection has been established in the non-SDT process.

[0195] In an alternative implementation, transmitting the data packets of the PDCP entity of the RB includes any one of the following: when the transmission mode corresponding to the RB is the unacknowledged (UM) mode, transmitting the data packets that have not been sent in the PDCP entity of the RB; when the transmission mode corresponding to the RB is the acknowledged mode, transmitting the data packets that have not been sent and / or the data packets that have been sent but not successfully received and acknowledged in the PDCP entity of the RB.

[0196] In an alternative implementation, the connection recovery request message requirements include any one of the following: regenerating the connection recovery request message corresponding to the SDT process according to the security configuration information; reusing the connection recovery request message used in the SDT process.

[0197] In an alternative implementation, the triggering conditions include any one of the following:

[0198] Receiving indication information sent by a network device, where the indication information is used to indicate that the terminal device should fall back from the SDT process to the non-SDT process.

[0199] Determining that the number of data transmissions in the SDT process reaches a first threshold value.

[0200] Determining that the data transmission volume corresponding to the data radio bearer in the SDT process reaches a second threshold value.

[0201] Determining that the signal quality corresponding to the cell or beam supporting the SDT process reaches a third threshold value.

[0202] Determining that the signal strength corresponding to the cell or beam supporting the SDT process reaches a fourth threshold value.

[0203] Determining that the resource status of the configured grant (CG) physical uplink shared channel (PUSCH) resource supporting the SDT process is in an unavailable state.

[0204] In an embodiment of the present application, determining that the resource status of the configured grant (CG) physical uplink shared channel (PUSCH) resource supporting the SDT process is in an unavailable state includes any one of the following:

[0205] In response to recognizing a cell reselection from a cell supporting CGPUSCH resources to a cell not supporting CGPUSCH resources, determine that the resource status of the configured grant CG physical uplink shared channel PUSCH resources supporting the SDT process is in an unavailable state.

[0206] In response to recognizing that the uplink timing advance of the CGPUSCH resources fails, determine that the resource status of the configured grant CG physical uplink shared channel PUSCH resources supporting the SDT process is in an unavailable state.

[0207] In a possible implementation, the indication information further includes security configuration information.

[0208] In a possible implementation, the security configuration information includes at least one of the following: security algorithm, security key, next-hop chain count value for updating the security key, and next-hop count value for updating the security key.

[0209] The processing device 70 for small data transmission (SDT) to fallback to non-SDT is a network device: a transceiver unit 702, which is used for sending indication information to a terminal device, where the indication information is used to indicate that the terminal device falls back from the SDT process to the non-SDT process during the SDT process.

[0210] In a possible implementation, the indication information further includes security configuration information.

[0211] In a possible implementation, the above security configuration information includes at least one of the following: security algorithm, security key, next-hop chain count value for updating the security key, and next-hop count value for updating the security key.

[0212] Please refer to Figure 8 , Figure 8 is a schematic structural diagram of another processing device 80 for small data transmission (SDT) to fallback to non-SDT provided by an embodiment of the present application. The processing device 80 for small data transmission (SDT) to fallback to non-SDT can be a network device, a terminal device, a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the terminal device to implement the above method. This device can be used to implement the method described in the above method embodiment, and specifically, reference can be made to the description in the above method embodiment.

[0213] The processing device 80 for returning the small data transmission SDT to non-SDT may include one or more processors 801. The processor 801 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and the communication data, and the central processing unit may be used to control the processing device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.) for returning the small data transmission SDT to non-SDT, execute a computer program, and process the data of the computer program.

[0214] Optionally, the processing device 80 for small data transmission SDT returning to non-SDT may also include one or more memories 802, on which a computer program 803 may be stored, and the processor 801 executes the computer program 803, so that the processing device 80 for small data transmission SDT returning to non-SDT performs the method described in the above method embodiment. The computer program 803 may be solidified in the processor 801, in which case the processor 801 may be implemented by hardware.

[0215] Optionally, data may also be stored in the memory 802. The processing device 80 for returning the small data transmission SDT to non-SDT and the memory 802 may be provided separately or integrated together.

[0216] Optionally, the processing device 80 for returning the small data transmission SDT to non-SDT may further include a transceiver 805 and an antenna 806. The transceiver 805 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 805 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

[0217] Optionally, the processing device 80 for returning small data transmission SDT to non-SDT may further include one or more interface circuits 807. The interface circuit 807 is used to receive code instructions and transmit them to the processor 801. The processor 801 executes the code instructions to enable the processing device 80 for returning small data transmission SDT to non-SDT to perform the method described in the above method embodiment.

[0218] The processing device 80 for returning the small data transmission SDT to the non-SDT is a terminal device: the processor 801 is used to execute Figure 2 Step S201 in the embodiment; Figure 3 Step S301 in the above method; Figure 4 Step S401 in Figure 5 The transceiver 805 is used to perform steps S501 and S502. Figure 6 Step S601 in .

[0219] In one implementation, the processor 801 may include a transceiver for implementing reception and transmission functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing reception and transmission functions may be separate or integrated together. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for signal transmission or transfer.

[0220] In one implementation, the processing device 80 for the small data transfer (SDT) to fallback to non-SDT may include a circuit, and the circuit may implement the functions of sending, receiving, or communicating in the foregoing method embodiments. The processor and transceiver described in this application may be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed-signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver may also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), BiCMOS, silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0221] The processing device for the small data transfer (SDT) to fallback to non-SDT described in the above embodiments may be a network device or a terminal device, but the scope of the processing device for the small data transfer (SDT) to fallback to non-SDT described in this application is not limited thereto, and the structure of the processing device for the small data transfer (SDT) to fallback to non-SDT may not be restricted by Figure 8 The processing device for the small data transfer (SDT) to fallback to non-SDT may be an independent device or may be a part of a larger device. For example, the processing device for the small data transfer (SDT) to fallback to non-SDT may be:

[0222] (1) An independent integrated circuit (IC), or a chip, or a chip system or subsystem;

[0223] (2) A set having one or more ICs, optionally, the IC set may also include storage components for storing data and computer programs;

[0224] (3) ASIC, such as a modem;

[0225] (4) A module that can be embedded in other devices;

[0226] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0227] (6) Others, etc.

[0228] For the case where the processing device that falls back to non-SDT for small data transmission SDT can be a chip or a chip system, reference can be made to Figure 9 The structural schematic diagram of the shown chip. Figure 9 The shown chip includes a processor 901 and an interface 902. Among them, the number of processors 901 can be one or more, and the number of interfaces 902 can be multiple.

[0229] For the case where the chip is used to implement the functions of the network device in the embodiments of the present application:

[0230] The interface 902 is used to receive code instructions and transmit them to the processor;

[0231] The processor 901 is used to run the code instructions to execute a method such as Figures 2 to 5 as described.

[0232] For the case where the chip is used to implement the functions of the terminal device in the embodiments of the present application:

[0233] The interface 902 is used to receive code instructions and transmit them to the processor;

[0234] The processor 901 is used to run the code instructions to execute a method such as Figure 6 as described.

[0235] Optionally, the chip further includes a memory 903, and the memory 903 is used to store necessary computer programs and data.

[0236] Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such a function is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art can use various methods to implement the functions for each specific application, but such implementation should not be construed as exceeding the scope protected by the embodiments of the present application.

[0237] The embodiments of the present application also provide a communication system, which includes the foregoing Figure 7 processing device for the small data transmission (SDT) of the terminal device in the foregoing embodiments to fall back to non-SDT and the processing device for the small data transmission (SDT) of the network device to fall back to non-SDT, or, the system includes the foregoing Figure 8 processing device for the small data transmission (SDT) of the terminal device in the foregoing embodiments to fall back to non-SDT and the processing device for the small data transmission (SDT) of the network device to fall back to non-SDT.

[0238] The present application also provides a readable storage medium, on which instructions are stored, and when the instructions are executed by a computer, the functions of any one of the foregoing method embodiments are implemented.

[0239] The present application also provides a computer program product, and when the computer program product is executed by a computer, the functions of any one of the foregoing method embodiments are implemented.

[0240] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a high-definition digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0241] Those of ordinary skill in the art can understand that the various numerical numbers such as the first and second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application, nor do they represent the order of precedence.

[0242] At least one in this application can also be described as one or more. The plurality can be two, three, four, or more, and this application does not make any restrictions. In the embodiments of this application, for a technical feature, the technical features in this technical feature are distinguished by "first", "second", "third", "A", "B", "C", and "D", etc. There is no order of precedence or size order among the technical features described by the "first", "second", "third", "A", "B", "C", and "D".

[0243] The corresponding relationships shown in each table in this application can be configured or predefined. The values of the information in each table are only examples and can be configured as other values, which are not limited in this application. When configuring the corresponding relationships between the configuration information and each parameter, it is not necessarily required to configure all the corresponding relationships shown in each table. For example, in the tables of this application, the corresponding relationships shown in some rows can also not be configured. Another example is that appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names understandable by the communication device, and the values or representation methods of the parameters can also use other values or representation methods understandable by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash maps, etc.

[0244] The predefined in this application can be understood as definition, pre - definition, storage, pre - storage, pre - negotiation, pre - configuration, solidification, or pre - firing.

[0245] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0246] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0247] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A processing method for reverting from a small data transfer (SDT) process to a non-SDT process, characterized in that, The method is executed by a terminal device, and the method includes: During the SDT process, in response to meeting a specified trigger condition, the SDT process is rolled back to a non-SDT process; Among them, the rolling back of the SDT process to a non-SDT process includes: According to the radio carrier RB requirements of the non-SDT process, process the RB for resuming data transmission in the SDT process; Among them, the radio carrier RB requirements include any one of the following: Suspend the RB; Process the packet data convergence protocol (PDCP) entity of the RB; Among them, the processing of the PDCP entity of the RB includes any one of the following: Reconstruct the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process; When a radio resource control (RRC) connection has been established in the non-SDT process, transmit the data packets of the PDCP entity of the RB.

2. The method according to claim 1, characterized in that The rolling back of the SDT process to a non-SDT process includes: According to the connection configuration requirements of the non-SDT process, process the connection configuration corresponding to the SDT process.

3. The method according to claim 2, wherein The processing of the connection configuration corresponding to the SDT process according to the connection configuration requirements of the non-SDT process includes at least one of the following processing actions: Reset the MAC entity corresponding to the SDT process according to the medium access control (MAC) entity requirements of the non-SDT process; Restart the timer used in the SDT process or start a new timer according to the timer requirements of the non-SDT process; Process the connection recovery request message corresponding to the SDT process according to the connection recovery request message requirements of the non-SDT process.

4. The method according to claim 1, wherein The transmission of the data packets of the PDCP entity of the RB includes any one of the following: When the transmission mode corresponding to the RB is the unacknowledged (UM) mode, transmit the data packets that have not been sent in the PDCP entity of the RB; When the transmission mode corresponding to the RB is the acknowledged mode, transmit the data packets that have not been sent and / or the data packets that have been sent but not successfully acknowledged in the PDCP entity of the RB.

5. The method according to claim 3, characterized in that, The connection recovery request message requirements include any one of the following: Regenerate the connection recovery request message corresponding to the SDT process according to the security configuration information; Reuse the connection recovery request message used in the SDT process.

6. The method according to claim 1, characterized in that, The suspension of the RB includes: Suspend the PDCP entity and the radio link control (RLC) entity of the RB.

7. The method according to claim 1, wherein The reconstruction of the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process includes: When the transmission mode corresponding to the RB is the unacknowledged UM mode, for each packet data convergence protocol service data unit (PDCP SDU) associated with a packet data convergence protocol sequence number (PDCP SN) number and not yet delivered to the lower layer protocol entity, the PDCP SDU is processed as being received from the upper layer for the first time, and transmission is performed in ascending order according to the COUNT value associated with the PDCP SDU. When the radio link control protocol acknowledged (RLC AM) mode data radio bearer (DRB) corresponding to the RB is in a suspended state, for each PDCP SDU associated with a PDCP SN number, starting from the first PDCP SDU not acknowledged as successfully transmitted by the lower layer protocol entity, the PDCP SDU is processed as being received from the upper layer for the first time, and transmission is performed in ascending order according to the COUNT value associated with the PDCP SDU. When the DRB of the RLC AM mode corresponding to the RB is in a non-suspended state, for each PDCP SDU associated with a PDCP SN number, all PDCP SDUs are transmitted in ascending order according to the COUNT value associated with the PDCP SDU.

8. The method according to any one of claims 1 to 7, characterized in that, The triggering condition includes any one of the following: Receiving indication information sent by a network device, where the indication information is used to instruct the terminal device to fallback from the SDT process to the non-SDT process; Determining that the number of data transmissions in the SDT process reaches a first threshold; Determining that the data transmission volume corresponding to the data radio bearer in the SDT process reaches a second threshold; Determining that the signal quality corresponding to the cell or beam supporting the SDT process reaches a third threshold; Determining that the signal strength corresponding to the cell or beam supporting the SDT process reaches a fourth threshold; Determining that the resource status of the configured grant (CG) physical uplink shared channel (PUSCH) resource supporting the SDT process is in an unavailable state.

9. The method according to claim 8, characterized in that Determining that the resource status of the configured grant (CG) physical uplink shared channel (PUSCH) resource supporting the SDT process is in an unavailable state includes any one of the following: In response to identifying a cell reselection from a cell supporting the CG PUSCH resource to a cell not supporting the CG PUSCH resource, determining that the resource status of the configured grant (CG) physical uplink shared channel (PUSCH) resource supporting the SDT process is in an unavailable state; In response to identifying that the uplink timing advance of the CG PUSCH resource has expired, determining that the resource status of the configured grant (CG) physical uplink shared channel (PUSCH) resource supporting the SDT process is in an unavailable state.

10. The method according to claim 8, wherein The indication information further includes the security configuration information.

11. The method according to claim 10, characterized in that, The security configuration information includes at least one of the following: security algorithm, security key, next-hop chain counter value for updating the security key, and next-hop counter value for updating the security key.

12. A processing method for reverting from a small data transfer (SDT) process to a non-SDT process, characterized in that, The method is executed by a network device, and the method includes: Send indication information to a terminal device, where the indication information is used to indicate that during the SDT process of the terminal device, it reverts from the SDT process to a non-SDT process; Wherein, the reversion from the SDT process to a non-SDT process includes: Process the radio bearer RB for resuming data transmission in the SDT process according to the radio bearer RB requirements of the non-SDT process; Wherein, the radio bearer RB requirements include any one of the following: Suspend the RB; Process the packet data convergence protocol PDCP entity of the RB; Wherein, the processing of the packet data convergence protocol PDCP entity of the RB includes any one of the following: Reconstruct the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process; Transmit the data packets of the PDCP entity of the RB when a radio resource control RRC connection has been established in the non-SDT process.

13. The method according to claim 12, wherein The indication information further includes security configuration information.

14. The method according to claim 13, wherein The security configuration information includes at least one of the following: security algorithm, security key, next-hop chain count value for updating the security key, and next-hop count value for updating the security key.

15. A processing device for reverting from a small data transfer (SDT) process to a non-SDT process, characterized in that, Applied in a terminal device, the apparatus includes: A processing unit, configured to, during the SDT process, in response to meeting a specified trigger condition, revert the SDT process to a non-SDT process; Wherein, the reversion of the SDT process to a non-SDT process includes: Process the radio bearer RB for resuming data transmission in the SDT process according to the radio bearer RB requirements of the non-SDT process; Wherein, the radio bearer RB requirements include any one of the following: Suspend the RB; Process the packet data convergence protocol PDCP entity of the RB; Wherein, the processing of the packet data convergence protocol PDCP entity of the RB includes any one of the following: Reconstruct the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process; Transmit the data packets of the PDCP entity of the RB when a radio resource control RRC connection has been established in the non-SDT process.

16. A processing device for reverting from a small data transfer (SDT) process to a non-SDT process, characterized in that, Applied in a network device, the apparatus includes: A transceiver unit, configured to send indication information to a terminal device, where the indication information is used to indicate that during the SDT process of the terminal device, it reverts from the SDT process to a non-SDT process; Wherein, the reversion from the SDT process to a non-SDT process includes: Process the radio bearer RB for resuming data transmission in the SDT process according to the radio bearer RB requirements of the non-SDT process; Wherein, the radio bearer RB requirements include any one of the following: Suspend the RB; Process the packet data convergence protocol PDCP entity of the RB; Wherein, the processing of the packet data convergence protocol PDCP entity of the RB includes any one of the following: Reconstruct the PDCP entity of the RB according to the configuration information of the PDCP entity corresponding to the non-SDT process; When the radio resource control (RRC) connection has been established in the non-SDT process, transmit the data packets of the PDCP entity of the RB.

17. A processing device for a small data transmission (SDT) to fall back to non-SDT, characterized in that, The device includes a processor and a memory. A computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to execute the method according to any one of claims 1 to 11.

18. A processing device for a small data transfer (SDT) to fallback to non-SDT, characterized in that, The device includes a processor and a memory. A computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to execute the method according to any one of claims 12 to 14.

19. A processing device for a small data transmission (SDT) to fallback to non-SDT, characterized in that, Comprising: A processor and an interface circuit; The interface circuit is configured to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the method according to any one of claims 1 to 11.

20. A processing device for a small data transmission (SDT) to fallback to non-SDT, characterized in that, Comprising: A processor and an interface circuit; The interface circuit is configured to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the method according to any one of claims 12 to 14.

21. A computer-readable storage medium for storing instructions that, when executed, implement the method according to any one of claims 1 to 11.

22. A computer-readable storage medium for storing instructions that, when executed, implement the method according to any one of claims 12 to 14.

Images