A method and apparatus for processing uplink data

Abstract

This disclosure proposes an uplink data processing method and apparatus applicable to the field of communication technology. The method executed by the terminal device includes: during the Small Data Transmission (SDT) process, sending a first indication information to the network device. The first indication information is used to indicate whether the Non-SDT Radio Bearer (non-SDT DRB) on the terminal device side carries uplink data to be transmitted. This allows the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner, and then process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method and apparatus for processing uplink data. Background Technology

[0002] In a communication system, a terminal device can be configured with multiple data radio bearers (DRBs). Based on the method of data transmission, DRBs can be divided into small data transmission (SDT) DRBs and non-small data transmission (non-SDT) DRBs.

[0003] In related technologies, when a terminal device's SDT DRB has uplink data to send, the SDT process can be initiated to send data from the SDT DRB. During this process, how to handle non-SDT DRBs when they have uplink data to send is a problem that urgently needs to be solved. Summary of the Invention

[0004] This disclosure provides an uplink data processing method and apparatus that enables network devices to obtain non-SDT DRB information from the terminal device side in a timely manner, effectively avoiding data loss and minimizing the transmission latency of data carried in the non-SDT DRB.

[0005] In a first aspect, embodiments of this disclosure propose an uplink data processing method, which is executed by a terminal device. The method includes: during small data transmission (SDT) processing, sending first indication information to a network device, wherein the first indication information is used to indicate whether the non-small data transmission data radio bearer (non-SDT DRB) on the terminal device side carries uplink data to be transmitted.

[0006] The uplink data processing method proposed in this disclosure allows the terminal device to send a first indication message to the network device as needed during small data transmission SDT (Small Data Transmission Technique) to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be transmitted. This enables the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner and process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

[0007] Secondly, this disclosure also proposes an uplink data processing method, which is executed by a network device. The method includes: receiving first indication information sent by a terminal device, wherein the first indication information is used to indicate whether the non-small data transmission data radio bearer (non-SDT DRB) on the terminal device side carries uplink data to be transmitted.

[0008] Thirdly, embodiments of this disclosure provide a communication device that implements some or all of the functions of the terminal device described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment of this disclosure implemented individually. The functions may 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.

[0009] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0010] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0011] Fourthly, embodiments of this disclosure provide a communication device that implements some or all of the functions of the network device described in the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment of this disclosure implemented individually. The functions may 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.

[0012] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0013] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0014] Fifthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0015] In a sixth aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0016] In a seventh aspect, embodiments of this disclosure provide a communication device, the device including a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method described in the first aspect above.

[0017] Eighthly, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method described in the second aspect above.

[0018] In a ninth aspect, embodiments of this disclosure provide a communication device, comprising: a processor and an interface circuit; the interface circuit being configured to receive code instructions and transmit them to the processor; the processor being configured to execute the code instructions to perform the method described in the first aspect above.

[0019] In a tenth aspect, this disclosure provides a communication device, comprising: a processor and an interface circuit; the interface circuit being configured to receive code instructions and transmit them to the processor; the processor being configured to execute the code instructions to perform the method described in the second aspect above.

[0020] Eleventhly, embodiments of this disclosure provide an uplink data processing system, the system including the communication device described in the third aspect and the communication device described in the fourth aspect, or the system including the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system including the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system including the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0021] In a twelfth aspect, embodiments of this disclosure provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0022] In a thirteenth aspect, embodiments of this disclosure provide a computer-readable storage medium for storing instructions for use by the network device described above, which, when executed, cause the network device to perform the method described in the second aspect above.

[0023] In a fourteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0024] In a fifteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0025] In a sixteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0026] In a seventeenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting network devices in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0027] In an eighteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0028] In a nineteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0030] Figure 1 This is a schematic diagram of the architecture of a communication system proposed in an embodiment of this disclosure;

[0031] Figure 2 This is a schematic flowchart of an uplink data processing method according to an embodiment of the present disclosure;

[0032] Figure 3 This is a flowchart illustrating an uplink data processing method according to another embodiment of this disclosure;

[0033] Figure 4 This is a flowchart illustrating an uplink data processing method according to another embodiment of this disclosure;

[0034] Figure 5 This is a flowchart illustrating an uplink data processing method according to another embodiment of this disclosure;

[0035] Figure 6 This is a flowchart illustrating an uplink data processing method according to another embodiment of this disclosure;

[0036] Figure 7 This is a flowchart illustrating an uplink data processing method according to another embodiment of this disclosure;

[0037] Figure 8 This is a flowchart illustrating an uplink data processing method according to another embodiment of this disclosure;

[0038] Figure 9 This is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure;

[0039] Figure 10 This is a schematic diagram of the structure of a communication device according to another embodiment of the present disclosure;

[0040] Figure 11 This is a schematic diagram of the structure of a communication device according to another embodiment of the present disclosure;

[0041] Figure 12 This is a schematic diagram of the structure of a chip according to an embodiment of the present disclosure. Detailed Implementation

[0042] Embodiments of this disclosure are described in detail below. Examples of these embodiments are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0043] To facilitate understanding, the terminology used in this disclosure will be introduced first.

[0044] 1. Radio Resource Control (RRC)

[0045] Radio Resource Management (RRM) or Radio Resource Allocation (RRA) refers to the management, control, and scheduling of wireless resources through certain strategies and methods. While meeting the requirements of quality of service, it aims to make full use of limited wireless network resources, ensure coverage of the planned area, and maximize service capacity and resource utilization.

[0046] 2. Data Radio Bearer (DRB)

[0047] DRBs can be used to send service data from terminal devices.

[0048] 3. Signaling Radio Bearer (SRB)

[0049] SRB is a special type of radio bearer used only to transmit RRC and non-access stratum (NAS) messages.

[0050] To better understand the uplink data processing method proposed in this disclosure, the communication system used in this disclosure is described below.

[0051] like Figure 1 As shown, Figure 1 This is a schematic diagram of the architecture of a communication system proposed in an embodiment of this disclosure. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown is exemplified by a network device 101 and a terminal device 102.

[0052] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems.

[0053] The network device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can 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. This disclosure does not limit the specific technology or device form used in the network device. The network device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0054] The terminal device 102 in this disclosure is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, 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, etc. This disclosure does not limit the specific technology or device form used in the terminal device.

[0055] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in the embodiments of this disclosure are also applicable to similar technical problems.

[0056] The following is a detailed description of an uplink data processing method and apparatus proposed in this disclosure, with reference to the accompanying drawings.

[0057] Figure 2 This is a flowchart illustrating an uplink data processing method according to an embodiment of this disclosure, which can be executed by a terminal device. Figure 2 As shown, the method for processing this uplink data includes the following steps:

[0058] Step 201: During the Small Data Transmission (SDT) process, a first indication message is sent to the network device, wherein the first indication message is used to indicate whether the Non-Small Data Transmission Radio Bearer (nonSDT DRB) on the terminal device side carries uplink data to be transmitted.

[0059] Typically, depending on the network device's resource configuration, when in an idle or inactive state, the terminal device can directly send the data carried by the SDT DRB to the network device using the following methods:

[0060] The data carried by the SDT DRB can be directly sent to the network device using the third access message (message 3, Msg3) of the four-step random access procedure; the data carried by the SDT DRB can be directly sent to the network device using the first access message (message A, MsgA) of the two-step random access procedure; or, the data carried by the SDT DRB can be directly sent to the network device using dedicated physical uplink shared channel (PUSCH) resources, such as configure grant (CG) or preallocated uplink resource (PUR).

[0061] Four-step random access refers to an RRC connection established between a terminal device and a network device through four information exchanges. Specifically, the terminal device first sends a random access preamble (message 1, Msg1) to the network device. The network device then replies with a random access response (message 2, Msg2). Next, the terminal device sends a connection establishment request (message 3, Msg3). Finally, the network device returns a connection contention resolution response (message 4, Msg4) to the terminal device.

[0062] Two-step random access refers to an RRC connection established between a terminal device and a network device through two information exchanges. That is, the terminal device first sends a random access request to the network device, i.e., the first access message (message A, MsgA), and then the network device can return an access response to the terminal device, i.e., the second access message (message B, MsgB).

[0063] Accordingly, the SDT procedure can be a four-step random access procedure, or a two-step random access procedure, or a procedure that uses dedicated PUSCH resources to send data carried by the SDT DRB, etc. This disclosure does not limit it in this way.

[0064] Optionally, the first indication information may include at least one of the following: a first identifier for indicating whether uplink data to be transmitted is carried in the non-SDT DRB; a second identifier for indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier for indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; an identifier of the terminal device; and an identifier of the non-SDT DRB.

[0065] Optionally, the first identifier may be represented by the value of a specific bit or by a specific character, etc., and this disclosure does not limit it.

[0066] For example, according to the protocol, the values ​​of the first two bits in the first indication information are used to represent the first identifier. When the value of the first two bits is "01", it indicates that there is uplink data to be transmitted in the first non-SDT DRB; when the value of the first two bits is "10", it indicates that there is uplink data to be transmitted in the second non-SDT DRB; when the value of the first two bits is "00", it indicates that there is no uplink data to be transmitted in the non-SDT DRB; when the value of the first two bits is "11", it indicates that there is uplink data to be transmitted in both non-SDT DRBs, and so on. This disclosure does not limit this.

[0067] Alternatively, it can be agreed in advance that when the first indication information contains "AAA", it indicates that the non-SDT DRB carries uplink data to be sent, and when there is no "AAA", it indicates that the non-SDT DRB does not carry uplink data to be sent, and so on.

[0068] It should be noted that the above examples are merely illustrative and should not be construed as limiting the first instruction information, first identifier, etc., in the embodiments of this disclosure.

[0069] Optionally, when the terminal device determines that the uplink data to be sent is carried in the nonSDT DRB, the state of the nonSDT DRB is set to data transmission / reception state.

[0070] When the nonSDT DRB is set to the data transmission and reception state, the terminal device can read the amount of uplink data to be sent carried in the nonSDT DRB, and thus add the amount of data in the first indication information.

[0071] It is understandable that the amount of uplink data to be transmitted carried in the non-SDT DRB can be any value determined according to actual needs, such as 10 bytes (B), 100B, etc., and this disclosure does not limit it.

[0072] For example, if the terminal device determines that the amount of uplink data to be transmitted carried in the non-SDT DRB is 10B, then the second identifier added in the first indication information can be: 10B.

[0073] It should be noted that the above examples are merely illustrative and should not be taken as limitations on the amount of uplink data, the second identifier, etc., in the embodiments of this disclosure.

[0074] Furthermore, different non-SDT DRBs may belong to the same logical channel group or they may belong to different logical channel groups, and this disclosure does not limit this.

[0075] Optionally, the third identifier may be represented by the value of a specific bit, or by a specific character, etc., and this disclosure does not limit it in this way.

[0076] For example, the 10th to 20th bits in the first instruction information have been pre-agreed to represent the third identifier.

[0077] For example, the first non-SDT DRB belongs to logical channel group A, the second non-SDT DRB belongs to logical channel group B, and the third non-SDT DRB belongs to logical channel group A. Logical channel group A carries 100 bytes of uplink data to be transmitted, and logical channel group B carries 20 bytes of uplink data to be transmitted. According to the protocol, bits 10 to 15 of the first indication information correspond to the data volume for logical channel group A, and bits 16 to 20 correspond to the data volume for logical channel group B. After determining the data volume of the uplink data to be transmitted for logical channel group A, the terminal device can write that data volume into bits 10 to 15 of the first indication information; similarly, after determining the data volume of the uplink data to be transmitted for logical channel group B, the terminal device can write that data volume into bits 16 to 20 of the first indication information.

[0078] It should be noted that the above examples are merely illustrative and should not be construed as limiting the first indication information, logical channel group, third identifier, etc. in the embodiments of this disclosure.

[0079] In addition, the first instruction information may also include the identifier of the terminal device.

[0080] The identification style or presentation format of the terminal device can be pre-defined, such as: message authentication code for integrity (MACI), resume message authentication code for integrity (resume MACI), etc. This disclosure does not limit this.

[0081] In addition, the identifier for a non-SDT DRB can be at least one of the following: DRB identifier, logical channel identifier, and logical channel group identifier.

[0082] The DRB logo style or presentation format can be pre-defined, such as DRB3, DRBA, DRB CC, etc. This disclosure does not limit this.

[0083] In addition, according to the protocol configuration, logical channels can be divided into 0 to 15, of which logical channels 0, 1, and 2 correspond to SRBs, namely SRB0, SRB1, and SRB2 respectively, logical channels 3 to 10 correspond to DRBs, and the others 11 to 15 are reserved values.

[0084] Understandably, the correspondence between logical channels 3 to 10 and SDT DRBs and non-SDT DRBs can be pre-defined. This allows the terminal device to determine the logical channel identifier corresponding to any non-SDT DRB carrying uplink data to be transmitted, based on the correspondence, and then add the determined logical channel identifier to the first indication information. For example, if the terminal device determines that the non-SDT DRB carrying uplink data to be transmitted corresponds to logical channel 3, then logical channel 3 can be added to the first indication information.

[0085] It should be noted that the above examples are merely illustrative and should not be construed as limiting the logical channel identifier, DRB, etc., in the embodiments of this disclosure.

[0086] In addition, the identification style or presentation format of the logical channel group can be pre-defined, such as logical channel group A, logical channel group 00, etc., and this disclosure does not limit it.

[0087] Understandably, the correspondence between non-SDT DRBs and logical channel groups can be agreed upon in advance according to the protocol. Once the terminal device determines that any non-SDT DRB carries uplink data to be transmitted, it can determine the logical channel group identifier corresponding to that non-SDT DRB based on the correspondence, and then add the determined logical channel group identifier to the first indication information. For example, if the terminal device determines that the non-SDT DRB carrying uplink data to be transmitted corresponds to logical channel group A, then logical channel group A can be added to the first indication information.

[0088] It should be noted that the above examples are merely illustrative and should not be construed as limiting the logical channel group identifier, non-SDT DRB, etc., in the embodiments of this disclosure.

[0089] In this embodiment of the present disclosure, during the Small Data Transmission (SDT) process, the terminal device can send a first indication message to the network device as needed to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be transmitted. This allows the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner and process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

[0090] Figure 3 This is a flowchart illustrating another uplink data processing method provided in an embodiment of this disclosure. This method can be executed by a terminal device. Figure 3 As shown, the method for processing this uplink data includes the following steps:

[0091] Step 301: During the SDT process, based on the specified SRB, a first indication message is sent to the network device, wherein the first indication message is used to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be sent.

[0092] In addition, the specified SRB can be either SRB0 or ​​SRB1.

[0093] Typically, SRB0 can be used to send RRC messages on the common control channel (CCCH) logical channel. SRB1 can be used to send RRC messages on the dedicated control channel (DCCH) logical channel. This RRC message can carry NAS messages, and it can also be used to send NAS messages before SRB2 is established, etc.

[0094] Optionally, the first indication information can be represented by the specified bits in the specified SRB, according to the protocol or network configuration.

[0095] Optionally, the first indication information may include at least one of the following: a first identifier indicating whether uplink data to be transmitted is carried in the non-SDT DRB; a second identifier indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; an identifier of the terminal device; and an identifier of the non-SDT DRB. The identifier of the non-SDT DRB may be at least one of the following: a DRB identifier, a logical channel identifier, and a logical channel group identifier.

[0096] The style and implementation of each of the above-mentioned identifiers can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0097] Optionally, if the terminal device has already sent its identification information to the network device via the Common Control Channel (CCCH), then the terminal device's identification information in the Packet Data Convergence Protocol (PDCP) data in SRB1 can be deleted.

[0098] Normally, according to the protocol, the terminal device identifier is included at the end of the PDCP data in SRB1 by default. This disclosure considers that during SDT, the terminal device has already sent its identifier to the network device when sending information via CCCH. Therefore, the terminal device identifier can be deleted from the PDCP data in SRB1 to avoid duplicate transmission, effectively reducing the amount of uplink data sent and improving processing efficiency.

[0099] Optionally, during communication between the terminal device and the network device, after generating the RRC signaling for the SRB, a buffer status report (BSR) is triggered. In this disclosure, to avoid duplicate data transmission, the SDT process can be configured to prevent BSR triggering through a specified SRB. Therefore, during the SDT process, when the terminal device sends the first indication information to the network device through the specified SRB, the RRC signaling for that specified SRB will not trigger a buffer status report, meaning the first indication information will not be reported again through the BSR. This effectively avoids duplicate data transmission, reduces redundancy, and improves efficiency.

[0100] Accordingly, in order to avoid data loss and ensure the smooth operation of the communication process, after the SDT process is completed, the BSR can be triggered by a specified SRB so that the data sent by the terminal to the network device through the specified SRB will also be reported again through the BSR.

[0101] Optionally, during the SDT process, in order to ensure that the terminal device can send the first indication information to the network device in a timely manner, the sending priority of the specified SRB can be set to be higher than that of the BSR. This ensures that the first indication information can be sent to the network device first when uplink resources are limited, so as to minimize the loss of data carried in non-SDT DRBs.

[0102] Correspondingly, if the transmission priority of BSR is normally higher than that of SRB, but during SDT, in order to ensure that the data carried in non-SDT DRB can be sent to the network device in a timely manner, the transmission priority of the specified SRB is set to be higher than that of BSR. Then, after the SDT process is completed, the transmission priority of the specified SRB can be restored to the normal state agreed upon by the protocol, that is, the transmission priority of the specified SRB is set to be lower than that of BSR.

[0103] In this embodiment of the present disclosure, during the Small Data Transmission (SDT) process, the terminal device can send a first indication message to the network device as needed, based on a specified radio signaling bearer (SRB), to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be transmitted. This allows the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner, and then process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

[0104] Figure 4 This is a flowchart illustrating another uplink data processing method provided in an embodiment of this disclosure. This method can be executed by a terminal device. Figure 4 As shown, the method for processing this uplink data includes the following steps:

[0105] Step 401: Receive second indication information sent by the network device, wherein the second indication information is used to indicate the first triggering condition.

[0106] Step 402: During the SDT process, when the first triggering condition is met, send the first indication information to the network device.

[0107] The first indication information is used to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be sent.

[0108] Optionally, the first indication information may include at least one of the following: a first identifier indicating whether uplink data to be transmitted is carried in the non-SDT DRB; a second identifier indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; an identifier of the terminal device; and an identifier of the non-SDT DRB. The identifier of the non-SDT DRB may be at least one of the following: a DRB identifier, a logical channel identifier, and a logical channel group identifier.

[0109] The style and implementation of each of the above-mentioned identifiers can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0110] Optionally, the first triggering condition may include any of the following: the amount of uplink data to be sent in the non-SDT DRB is greater than or equal to a first threshold; the amount of uplink data to be sent in the non-SDT DRB is less than or equal to a second threshold; the terminal device does not send the first access message (message 1, Msg1) in the four-step random access; the terminal device does not send the third access message (message 3, Msg3) in the four-step random access; the terminal device does not send the first access message (message A, MsgA) in the two-step random access; the terminal device does not send SDT data through dedicated PUSCH resources; and the terminal device does not generate a medium access control (MAC) protocol data unit (PDU) corresponding to the data carried by the SDT DRB.

[0111] The first threshold and the second threshold can be determined by the terminal device according to the agreement, or they can be configured by the network device for the terminal device. This disclosure does not limit them.

[0112] Optionally, the first triggering condition is: the amount of uplink data to be transmitted in the non-SDT DRB is greater than or equal to a first threshold value. When this first triggering condition is met, the terminal device can send a first indication message to the network device, thereby prioritizing the transmission of large data volumes and delaying the transmission of small data volumes.

[0113] Optionally, the first triggering condition is: if the amount of uplink data to be sent in the non-SDT DRB is less than or equal to the second threshold value, then the terminal device sends the first indication information to the network device only when the amount of data carried in the non-SDT DRB is small, thereby avoiding data accumulation and reducing network congestion.

[0114] Optionally, the first triggering condition is: the terminal device has not sent the first access message (message 1, Msg1) in the four-step random access process. At this time, the terminal device has not yet started the four-step random access process, that is, it has not yet sent SDT data, and sending the first indication information to the network device will not affect the sending and transmission of SDT data.

[0115] Optionally, the first triggering condition is: the terminal device does not send the third access message (message 3, Msg3) in the four-step random access process.

[0116] Understandably, the terminal device can use the third access message (message 3, Msg3) in the four-step random access process to directly send the data carried by the SDT DRB to the network device. At this time, the terminal device has not yet sent the third access message (message 3, Msg3) in the four-step random access process, that is, it has not yet sent SDT data. Sending the first indication information to the network device at this time will not affect the sending and transmission of SDT data.

[0117] Optionally, the first triggering condition is: the terminal device does not send the first access message (message A, MsgA) in the two-step random access process.

[0118] Understandably, the terminal device can use the first access message (message A, MsgA) in the two-step random access process to directly send the data carried by the SDT DRB to the network device. At this time, the terminal device has not yet sent the first access message (message A, MsgA) in the two-step random access process, that is, it has not yet sent SDT data. Sending the first indication information to the network device at this time will not affect the sending and transmission of SDT data.

[0119] Optionally, the first triggering condition is: the terminal device has not sent SDT data through the dedicated PUSCH resource. It is understood that the terminal device can utilize PUSCH resources, such as CG and PUR. At this point, since the terminal device has not yet sent SDT data, sending the first indication information to the network device will not affect the sending and transmission of SDT data.

[0120] Optionally, the first triggering condition is: the terminal device has not generated a MACPDU corresponding to the data carried by the SDT DRB. It is understandable that if the terminal device has already generated a MACPDU corresponding to the data carried by the SDT DRB, it has completed the preparation work for transmitting SDT data. Sending the first indication information at this time might invalidate the generated MAC PDU, wasting resources. However, if the terminal device has not generated a MACPDU corresponding to the data carried by the SDT DRB, sending the first indication information to the network device at this time will not result in resource waste.

[0121] In this embodiment of the disclosure, the terminal device can first receive the second indication information sent by the network device, and then send the first indication information to the network device when the first triggering condition is met, thereby ensuring the reliable transmission of data carried by SDT DRB and avoiding the loss of data carried by non-SDT DRB.

[0122] Figure 5 This is a flowchart illustrating another uplink data processing method provided in an embodiment of this disclosure. This method can be executed by a terminal device. Figure 5As shown, the method for processing this uplink data includes the following steps:

[0123] Step 501: Receive third indication information sent by the network device, wherein the third indication information is used to indicate the second triggering condition.

[0124] Optionally, the second triggering condition may include any of the following: the terminal device does not send the first access message (message 1, Msg1) in the four-step random access, the terminal device does not send the third access message (message 3, Msg3) in the four-step random access, the terminal device does not send the first access message (message A, MsgA) in the two-step random access, the terminal device does not send SDT data through dedicated PUSCH resources, and the transmission priority of data carried by non-SDT DRB is higher than the transmission priority of data carried by SDT DRB.

[0125] The specific meanings of the four-step random access, the two-step random access, and each access message can be found in the detailed descriptions of other embodiments of this disclosure, and will not be repeated here.

[0126] Step 502: During the SDT process, a first indication message is sent to the network device, wherein the first indication message is used to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be sent.

[0127] Optionally, the first indication information may include at least one of the following: a first identifier indicating whether uplink data to be transmitted is carried in the non-SDT DRB; a second identifier indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; an identifier of the terminal device; and an identifier of the non-SDT DRB. The identifier of the non-SDT DRB may be at least one of the following: a DRB identifier, a logical channel identifier, and a logical channel group identifier.

[0128] The style and implementation of each of the above-mentioned identifiers can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0129] In this disclosure, steps 501 and 502 can be executed in parallel, or step 501 can be executed first and then step 502, or step 502 can be executed first and then step 501. This disclosure does not limit this.

[0130] Step 503: Based on the second triggering condition, stop the SDT process.

[0131] For example, if the second triggering condition is: the terminal device does not send the first access message (message 1, Msg1) in the four-step random access process, then the terminal device has not yet started the four-step random access process, has not sent SDT data, and stopping the SDT process will not affect the sending and transmission of SDT data.

[0132] It is understood that the second triggering condition for stopping the SDT process set in this disclosure causes the terminal device to stop the SDT process before the SDT data transmission is completed, so as to process the data carried by the non-SDT DRB in a timely manner. This ensures that the transmission of SDT data is not affected, and that the transmission priority of the data carried by the non-SDT DRB is higher than that of the data carried by the SDT DRB.

[0133] Optionally, in this disclosure, after receiving the first indication information sent by the terminal device, the network device may also send indication information to the terminal device to instruct the terminal device to stop the SDT process. Thus, upon receiving this indication, the terminal device can directly stop the SDT process.

[0134] In this embodiment of the present disclosure, the terminal device can first receive the third indication information sent by the network device, and then send the first indication information to the network device during the SDT process. When the second triggering condition is met, the SDT process is stopped. Thus, the transmission of SDT data will not be affected, and the transmission priority of the data carried by the non-SDT DRB is guaranteed to be higher than that of the data carried by the SDT DRB.

[0135] Figure 6 This is a flowchart illustrating another uplink data processing method provided in an embodiment of this disclosure. This method can be executed by a terminal device. Figure 6 As shown, the method for processing this uplink data includes the following steps:

[0136] Step 601: During the SDT process, a first indication message is sent to the network device. The first indication message is used to indicate whether the non-small data transmission data radio bearer (non-SDT DRB) on the terminal device side carries uplink data to be transmitted, and the transmission priority of the first indication message is lower than the transmission priority of the SDT DRB data.

[0137] Optionally, the first indication information may include at least one of the following: a first identifier indicating whether uplink data to be transmitted is carried in the non-SDT DRB; a second identifier indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; an identifier of the terminal device; and an identifier of the non-SDT DRB. The identifier of the non-SDT DRB may be at least one of the following: a DRB identifier, a logical channel identifier, and a logical channel group identifier.

[0138] The style and implementation of each of the above-mentioned identifiers can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0139] Optionally, in order to ensure reliable transmission of SDT data, before, during, or after the SDT process starts, the terminal device can set the transmission priority of the first indication information to be lower than the transmission priority of the data carried by the SDT DRB. That is, the data carried by the SDT DRB is transmitted first, and then the first indication information is transmitted, thereby avoiding data corruption and loss.

[0140] Optionally, the transmission priority of data carried by non-SDT DRB can be set to be lower than that of data carried by SDT DRB. This ensures that data carried by SDT DRB is transmitted first, followed by data carried by non-SDT DRB, thus effectively avoiding data corruption and loss.

[0141] Step 602: Receive the fourth indication information sent by the network device, and determine the end of the SDT process based on the fourth indication information.

[0142] The fourth indication information can be any of the following: the fourth access message (message 4, Msg4) in four-step random access, the second access message (message B, MsgB) in two-step random access, and the cell network temporary identifier C-RNTI.

[0143] Optionally, the terminal device receives the fourth access message (message 4, Msg4) in the four-step random access process sent by the network device.

[0144] Understandably, the terminal device can send SDT data to the network device in the third access message (message 3, Msg3) of the four-step random access process. The fact that the terminal device has received the fourth access message (message 4, Msg4) from the network device indicates that the SDT process has ended.

[0145] Optionally, the terminal device receives the second access message (message B, MsgB) in the two-step random access process sent by the network device.

[0146] Understandably, the terminal device can send SDT data to the network device in the first access message (message A, MsgA) of the two-step random access process. The fact that the terminal device has received the second access message (message B, MsgB) from the network device in the two-step random access process indicates that the SDT procedure has ended.

[0147] Optionally, the terminal device receives a cell-radionetwork temporary identifier (C-RNTI) sent by the network device. For SDT procedures using dedicated PUSCH resources, the terminal device receives an acknowledgment message C-RNTI from the network device, indicating that the SDT procedure has ended.

[0148] Optionally, the SDT process can be terminated once the specified number of SDT transmissions has been reached.

[0149] The specified number of SDT transmissions can be determined by the terminal device according to the protocol, or it can be configured by the network device for the terminal device; this disclosure does not limit this.

[0150] Optionally, the SDT process can be terminated once a specified SDT transmission duration is reached.

[0151] The specified SDT transmission duration can be determined by the terminal device according to the protocol, or it can be configured by the network device for the terminal device; this disclosure does not limit this.

[0152] Step 603: After the SDT process is completed, the transmission priority of the bearer channel used to carry the first indication information is set to the transmission priority before the change.

[0153] During the SDT process, to ensure that the data carried by the SDT DRB is not affected and can be transmitted smoothly, the transmission priority of the first indication information can be set to be lower than the transmission priority of the data carried by the SDT DRB. Then, after the SDT process ends, the terminal device can set the transmission priority of the bearer channel used to carry the first indication information back to its original priority, thereby ensuring that the terminal device can reliably communicate with the network device according to the protocol.

[0154] Similarly, after the SDT process is completed, the transmission priority of the data carried by the non-SDT DRB can be set back to the transmission priority before the change.

[0155] In this embodiment of the present disclosure, during SDT (Single Channel Transmission) process, if the terminal device determines that uplink data to be transmitted is carried in the non-SDT DRB, it can send a first indication message to the network device, setting the transmission priority of the first indication message to be lower than the transmission priority of the data carried in the SDT DRB. After receiving a fourth indication message from the network device, the transmission priority of the bearer channel used to carry the first indication message is set back to the transmission priority before the change. This not only ensures the reliable and timely transmission of the data carried in the SDT DRB, but also ensures that after the terminal device completes the transmission of the data carried in the SDT DRB, it can continue to use channel resources according to the priority order before the change.

[0156] Figure 7 This is a flowchart illustrating another uplink data processing method provided in an embodiment of this disclosure. This method can be executed by a network device. Figure 7 As shown, the method for processing this uplink data includes the following steps:

[0157] Step 701: Receive first indication information sent by the terminal device, wherein the first indication information is used to indicate whether the non-small data transmission data radio bearer (non-SDT DRB) on the terminal device side carries uplink data to be transmitted.

[0158] Optionally, the first indication information may include at least one of the following: a first identifier indicating whether uplink data to be transmitted is carried in the non-SDT DRB; a second identifier indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; an identifier of the terminal device; and an identifier of the non-SDT DRB. The identifier of the non-SDT DRB may be at least one of the following: a DRB identifier, a logical channel identifier, and a logical channel group identifier.

[0159] The style and implementation of each of the above-mentioned identifiers can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0160] Optionally, if the network device determines, based on the first indication information, that the non-SDT DRB on the terminal device side carries uplink data to be transmitted, it can determine to restore the RRC connection with the terminal device. If the network device determines, based on the first indication information, that the non-SDT DRB on the terminal device side does not carry uplink data to be transmitted, it can determine not to restore the RRC connection with the terminal device.

[0161] In this embodiment of the present disclosure, the network device can determine whether the non-SDT DRB on the terminal device side carries uplink data to be sent based on the first indication information received from the terminal device. This allows the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner and process the uplink data, effectively avoiding data loss and minimizing the transmission latency of the data carried in the non-SDT DRB.

[0162] Figure 8 This is a flowchart illustrating another uplink data processing method provided in an embodiment of this disclosure. This method can be executed by a network device. Figure 8 As shown, the method for processing this uplink data includes the following steps:

[0163] Step 801: Send second indication information to the terminal device, wherein the second indication information is used to indicate the first triggering condition.

[0164] The content and implementation of the first instruction information and the second instruction information can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0165] Optionally, the first triggering condition may include any of the following: the amount of uplink data to be sent in the non-SDT DRB is greater than or equal to a first threshold; the amount of uplink data to be sent in the non-SDT DRB is less than or equal to a second threshold; the terminal device does not send the first access message (message 1, Msg1) in the four-step random access; the terminal device does not send the third access message (message 3, Msg3) in the four-step random access; the terminal device does not send the first access message (message A, MsgA) in the two-step random access; the terminal device does not send SDT data through a dedicated PUSCH; and the terminal device does not generate a MACPDU corresponding to the data carried by the SDT DRB.

[0166] The effects of each triggering condition and the operations performed by the terminal device based on each triggering condition in this disclosure can be referred to in other embodiments of this disclosure, which will not be repeated here.

[0167] Optionally, the network device may also send a third indication message to the terminal device, wherein the third indication message is used to indicate the second triggering condition.

[0168] The second triggering condition may include any of the following: the terminal device does not send the first access message (message 1, Msg1) in the four-step random access; the terminal device does not send the third access message (message 3, Msg3) in the four-step random access; the terminal device does not send the first access message (message A, MsgA) in the two-step random access; the terminal device does not send SDT data through dedicated PUSCH resources; and the transmission priority of data carried by non-SDT DRB is higher than the transmission priority of data carried by SDT DRB.

[0169] The effects of each triggering condition in this disclosure and the operations performed by the terminal device based on different triggering conditions can be referred to in other embodiments of this disclosure, which will not be repeated here.

[0170] Step 802: During the SDT process, the terminal device receives the first indication information based on the specified signaling radio bearer (SRB).

[0171] The first indication information is used to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be transmitted. The specified SRB can be SRB0 or ​​SRB1.

[0172] Optionally, the first indication information can be represented by the specified bits in the specified SRB, according to the protocol or network configuration.

[0173] The content and implementation method of the terminal device sending the first indication information based on the specified SRB during the SDT process can be referred to in other embodiments of this disclosure, and will not be repeated here.

[0174] In this embodiment of the present disclosure, the network device can send a second indication information to the terminal device, and then receive the first indication information sent by the terminal device based on the specified signaling radio bearer (SRB). This allows the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner, and then process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

[0175] In the embodiments provided above, the methods proposed in this disclosure have been described from the perspectives of network devices and terminal devices, respectively. To implement the functions of the methods proposed in the embodiments of this disclosure above, the network device and the terminal device may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions can be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0176] like Figure 9As shown, Figure 9 This is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. The communication device 90 may include a transceiver module 901.

[0177] The transceiver module 901 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 901 can implement both sending and / or receiving functions.

[0178] The transceiver module 901 is used to send first indication information to the network device during the Small Data Transmission (SDT) process, wherein the first indication information is used to indicate whether the non-SDT DRB of the device carries uplink data to be transmitted.

[0179] Optionally, the transceiver module 901 is specifically used to send first indication information to the network device based on a specified signaling radio bearer (SRB).

[0180] Optionally, the specified SRB is SRB0 or ​​SRB1.

[0181] Optionally, the transceiver module 901 is also used to send the terminal device identification information to the network device via the general control channel (CCCH).

[0182] Optionally, the device 90 further includes:

[0183] Processing module 902 is used to delete the identification information of the terminal device in the Packet Data Convergence Protocol (PDCP) data in the specified SRB, wherein the specified SRB is SRB1.

[0184] Optionally, the processing module 902 is further configured to, during the SDT process, prevent the transceiver module from triggering the buffer status report BSR through the specified SRB; or, during the SDT process, set the transmission priority of the specified SRB to be higher than the transmission priority of the BSR.

[0185] Optionally, the processing module 902 is further configured to trigger a BSR through the specified SRB after the SDT process is completed; or, after the SDT process is completed, set the transmission priority of the specified SRB to be lower than the transmission priority of the BSR.

[0186] Optionally, the first indication information includes at least one of the following: a first identifier for indicating whether the non-SDT DRB carries uplink data to be transmitted; a second identifier for indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier for indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; the identifier of the terminal device; and the identifier of the non-SDT DRB.

[0187] Optionally, the identifier of the non-SDT DRB may be at least one of the following: DRB identifier, logical channel identifier, and logical channel group identifier.

[0188] Optionally, the transceiver module 901 is further configured to send the first indication information to the network device when the first triggering condition is met.

[0189] Optionally, the first triggering condition includes any one of the following: the amount of uplink data to be transmitted in the non-SDT DRB is greater than or equal to a first threshold; the amount of uplink data to be transmitted in the non-SDT DRB is less than or equal to a second threshold; the transceiver module does not transmit the first access message (message 1, Msg1) in the four-step random access; the transceiver module does not transmit the third access message (message 3, Msg3) in the four-step random access; the transceiver module does not transmit the first access message (message A, MsgA) in the two-step random access; the transceiver module does not transmit SDT data through the dedicated physical uplink shared channel PUSCH; and the transceiver module does not generate the Media Access Control (MAC) protocol data unit (PDU) corresponding to the data carried by the SDT DRB.

[0190] Optionally, the transceiver module 901 is further configured to receive second indication information sent by the network device, wherein the second indication information is used to indicate the first triggering condition.

[0191] Optionally, the processing module 902 is also used to stop the SDT process.

[0192] Optionally, the processing module 902 is specifically used to stop the SDT process based on a second triggering condition.

[0193] Optionally, the second triggering condition includes any of the following: the transceiver module does not send the first access message (message 1, Msg1) in the four-step random access; the transceiver module does not send the third access message (message 3, Msg3) in the four-step random access; the transceiver module does not send the first access message (message A, MsgA) in the two-step random access; the transceiver module does not send SDT data through the dedicated PUSCH; and the transmission priority of the data carried by the non-SDT DRB is higher than the transmission priority of the data carried by the SDT DRB.

[0194] Optionally, the transceiver module 901 is further configured to receive third indication information sent by the network device, wherein the third indication information is used to indicate the second triggering condition.

[0195] Optionally, the processing module 902 is further configured to set the transmission priority of the first indication information to be lower than the transmission priority of the data carried by the SDTDRB; or, set the transmission priority of the data carried by the non-SDTDRB to be lower than the transmission priority of the data carried by the SDTDRB.

[0196] Optionally, the transceiver module 901 is further configured to receive fourth indication information sent by the network device, and determine the end of the SDT process based on the fourth indication information; or,

[0197] Processing module 902 is further configured to determine that the specified number of SDT transmissions has been reached, and then determine that the SDT process has ended; or,

[0198] The processing module 902 is also used to determine that the specified SDT transmission duration has been reached and to determine that the SDT process has ended.

[0199] Optionally, the third indication information is any of the following: the fourth access message (message4, Msg4) in four-step random access, the second access message (message B, MsgB) in two-step random access, and the cell network temporary identifier C-RNTI.

[0200] Optionally, the processing module 902 is further configured to, after the SDT process is completed, set the transmission priority of the bearer channel used to carry the first indication information to the transmission priority before the change; or, after the SDT process is completed, set the transmission priority of the data carried by the non-SDT DRB to the transmission priority before the change.

[0201] Optionally, the processing module 902 is further configured to set the state of the non-SDT DRB to a data transmission / reception state when the non-SDT DRB carries uplink data to be transmitted.

[0202] The communication device 90 may be a terminal device (such as the terminal device in the aforementioned method embodiments), a device within a terminal device, or a device that can be used in conjunction with a terminal device.

[0203] The communication device disclosed herein allows the terminal device to send a first indication message to the network device as needed during Small Data Transmission (SDT) to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be transmitted. This enables the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner and process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

[0204] like Figure 10 As shown, Figure 10 This is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. The communication device 100 may include a transceiver module 1001.

[0205] The transceiver module 1001 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 1001 can implement the sending function and / or the receiving function.

[0206] The transceiver module 1001 is used to receive first indication information sent by the terminal device, wherein the first indication information is used to indicate whether the non-small data transmission data radio bearer (non-SDT DRB) on the terminal device side carries uplink data to be transmitted.

[0207] Optionally, the transceiver module 1001 is specifically used to receive the first indication information sent by the terminal device based on a specified signaling radio bearer (SRB).

[0208] Optionally, the specified SRB is SRB0 or ​​SRB1.

[0209] Optionally, the first indication information includes at least one of the following: a first identifier for indicating whether the non-SDT DRB carries uplink data to be transmitted; a second identifier for indicating the amount of uplink data to be transmitted carried in the non-SDT DRB; a third identifier for indicating the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; the identifier of the terminal device; and the identifier of the non-SDT DRB.

[0210] Optionally, the identifier of the non-SDT DRB is at least one of the following: DRB identifier, logical channel identifier, and logical channel group identifier.

[0211] Optionally, the transceiver module 1001 is further configured to send second indication information to the terminal device, wherein the second indication information is used to indicate the first triggering condition.

[0212] Optionally, the first triggering condition includes any one of the following: the amount of uplink data to be transmitted in the non-SDT DRB is greater than or equal to a first threshold; the amount of uplink data to be transmitted in the non-SDT DRB is less than or equal to a second threshold; the terminal device does not transmit the first access message (message 1, Msg1) in the four-step random access; the terminal device does not transmit the third access message (message 3, Msg3) in the four-step random access; the terminal device does not transmit the first access message (message A, MsgA) in the two-step random access; the terminal device does not transmit SDT data through the dedicated physical uplink shared channel PUSCH; and the terminal device does not generate the Media Access Control (MAC) data unit (PDU) corresponding to the data carried by the SDT DRB.

[0213] Optionally, the transceiver module 1001 is further configured to send third indication information to the terminal device, wherein the third indication information is used to indicate the second triggering condition.

[0214] Optionally, the second triggering condition includes any of the following: the terminal device does not send the first access message (message 1, Msg1) in the four-step random access; the terminal device does not send the third access message (message 3, MsgA) in the four-step random access; the terminal device does not send the first access message (message A, MsgA) in the two-step random access; the terminal device does not send SDT data through a dedicated PUSCH; and the transmission priority of data carried by non-SDT DRB is higher than the transmission priority of data carried by SDT DRB.

[0215] The communication device 100 may be a network device, a device within a network device, or a device that can be used in conjunction with a network device.

[0216] The communication device disclosed herein allows a network device to determine whether uplink data to be transmitted is carried in the non-SDT DRB on the terminal device side based on the first indication information received from the terminal device. This enables the network device to obtain the information of the non-SDT DRB on the terminal device side in a timely manner and process the uplink data, effectively avoiding data loss and minimizing the transmission delay of the data carried in the non-SDT DRB.

[0217] Figure 11This is a schematic diagram of another communication device 1100 provided in this embodiment. The communication device 1100 can be a network device, a terminal device, a chip, chip system, or processor that supports the network device in implementing the above methods, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0218] The communication device 1100 may include one or more processors 1101. The processor 1101 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0219] Optionally, the communication device 1100 may further include one or more memories 1102, which may store a computer program 1104. The processor 1101 executes the computer program 1104 to cause the communication device 1100 to perform the methods described in the above method embodiments. Optionally, the memory 1102 may also store data. The communication device 1100 and the memory 1102 may be provided separately or integrated together.

[0220] Optionally, the communication device 1100 may also include a transceiver 1105 and an antenna 1106. The transceiver 1105 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1105 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0221] Optionally, the communication device 1100 may further include one or more interface circuits 1107. The interface circuit 1107 is used to receive code instructions and transmit them to the processor 1101. The processor 1101 executes the code instructions to cause the communication device 1100 to perform the method described in the above method embodiments.

[0222] Communication device 1100 is a terminal device: processor 1101 is used to execute Figure 5 Step 503 in the middle Figure 6 Step 603, etc.; transceiver 1105 is used to perform Figure 2 Step 201 in Figure 3 Step 301 in Figure 4 Step 401 in Figure 4 Step 402 in Figure 5 Step 501 in Figure 5 Step 502 in Figure 6 Step 601 and Figure 6 Step 602, etc.

[0223] Communication device 1100 is a network device: transceiver 1105 is used to perform... Figure 7 Step 701 in Figure 8 Step 801 and Figure 8 Step 802, etc.

[0224] In one implementation, the processor 1101 may include a transceiver for implementing receiving and transmitting 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 receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0225] In one implementation, processor 1101 may store computer program 1103, which runs on processor 1101 and causes communication device 1100 to execute the methods described in the above method embodiments. Computer program 1103 may be embedded in processor 1101, in which case processor 1101 may be implemented in hardware.

[0226] In one implementation, the communication device 1100 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the aforementioned method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0227] The communication device described in the above embodiments may be a network device or a terminal device (such as the first terminal device in the foregoing method embodiments), but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 11 The communication device can be a standalone device or part of a larger device. For example, the communication device can be:

[0228] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0229] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0230] (3) ASIC, such as modem;

[0231] (4) Modules that can be embedded in other devices;

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

[0233] (6) Others, etc.

[0234] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 12 The diagram shows the structure of the chip. Figure 12 The chip shown includes a processor 1201 and an interface 1202. There can be one or more processors 1201, and multiple interfaces 1202.

[0235] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure:

[0236] Interface 1202 is used for execution Figure 2 Step 201 in Figure 3 Step 301 in Figure 4 Step 401 in Figure 4 Step 402 in Figure 5 Step 501 in Figure 5 Step 502 in Figure 6 Step 601 and Figure 6 Step 602, etc.

[0237] For cases where the chip is used to implement the functions of the network device in the embodiments of this disclosure:

[0238] Interface 1202 is used for execution Figure 7 Step 701 in Figure 8 Step 801 and Figure 8 Step 802, etc.

[0239] Optionally, the chip also includes a memory 1203 for storing necessary computer programs and data.

[0240] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0241] This disclosure also provides an uplink data processing system, which includes the aforementioned... Figure 9 The communication device or system in the embodiments includes the aforementioned Figure 10 The communication device in the embodiment, or the system including the aforementioned Figure 11 The embodiments include a communication device as a terminal device and a communication device as a network device.

[0242] This disclosure also provides a computer-readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0243] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0244] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer programs. When a computer program is loaded and executed on a computer, it generates, in whole or in part, the flow or function according to the embodiments of this disclosure. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, a computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0245] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0246] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0247] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0248] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0249] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0250] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for processing uplink data, characterized in that, The method is executed by a terminal device, and the method includes: During the Small Data Transmission (SDT) process, when a first triggering condition is met, a first indication information is sent to the network device based on a specified signaling radio bearer (SRB). The first indication information is used to indicate whether the non-SDT DRB on the terminal device side carries uplink data to be transmitted. During the SDT process, the buffer status report (BSR) is not triggered through the specified SRB. After the SDT process ends, the BSR is triggered through the specified SRB. The first triggering condition includes: the terminal device has not generated a Media Access Control (MAC) Protocol Data Unit (PDU) corresponding to the data carried by the SDT DRB.

2. The method of claim 1, wherein, The specified SRB is either SRB0 or ​​SRB1.

3. The method of claim 1, wherein, The method further includes: The terminal device sends its identification information to the network device via the General Control Channel (CCCH); and the terminal device deletes its identification information from the Packet Data Convergence Protocol (PDCP) data in the specified SRB, wherein the specified SRB is SRB1.

4. The method of claim 1, wherein, The method further includes: During the SDT process, the transmission priority of the specified SRB is set to be higher than that of the BSR.

5. The method of claim 4, wherein, The method further includes: After the SDT process is completed, the transmission priority of the specified SRB is set to be lower than that of the BSR.

6. The method of claim 1, wherein, The first indication information includes at least one of the following: A first identifier used to indicate whether the non-SDT DRB carries uplink data to be transmitted; A second identifier used to indicate the amount of uplink data to be transmitted carried in the non-SDT DRB; A third identifier used to indicate the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; The identifier of the terminal device; and The identifier of the non-SDT DRB.

7. The method of claim 6, wherein, The identifier of the non-SDT DRB is at least one of the following: DRB logo, Logical channel identifier, and Logical channel group identifier.

8. The method of claim 1, wherein, The method further includes: The system receives a second indication message sent by the network device, wherein the second indication message is used to indicate the first triggering condition.

9. The method of claim 1, wherein, The method further includes: Stop the SDT process.

10. The method of claim 9, wherein, The process of stopping the SDT includes: Based on the second triggering condition, the SDT process is stopped.

11. The method of claim 10, wherein, The second triggering condition includes any one of the following: The terminal device did not send the first access message Msg1 in the four-step random access process; The terminal device did not send the third access message Msg3 in the four-step random access process; The terminal device did not send the first access message MsgA in the two-step random access process; The terminal device did not send SDT data through its dedicated PUSCH; as well as The transmission priority of data carried by non-SDT DRB is higher than that of data carried by SDT DRB.

12. The method of claim 10, wherein, The method further includes: The third indication information sent by the network device is received, wherein the third indication information is used to indicate the second triggering condition.

13. The method of any one of claims 1-12, wherein, The method further includes: The transmission priority of the first indication information is set to be lower than the transmission priority of the data carried by the SDT DRB; or, The transmission priority of data carried by non-SDT DRB is set to be lower than that of data carried by SDT DRB.

14. The method of claim 13, wherein, The method further includes: Receive the fourth indication information sent by the network device, and determine the end of the SDT process based on the fourth indication information; or, Once the specified number of SDT transmissions is reached, the SDT process is considered complete; or... Once the specified SDT transmission duration is reached, the SDT process is considered complete.

15. The method of claim 14, wherein, The fourth instruction information is any one of the following: The fourth access message, Msg4, in the four-step random access method. The second access message MsgB in two-step random access, and Community network temporary identifier C-RNTI.

16. The method of claim 13, wherein, The method further includes: After the SDT process is completed, the transmission priority of the bearer channel used to carry the first indication information is set back to the transmission priority before the change; or After the SDT process is completed, the transmission priority of the data carried by the non-SDT DRB is set back to the transmission priority before the change.

17. The method of any one of claims 1-12, wherein, The method further includes: When the non-SDT DRB carries uplink data to be sent, the state of the non-SDT DRB is set to data transmission / reception state.

18. A method for processing uplink data, the method comprising: The method is performed by a network device, and the method includes: Based on a specified signaling radio bearer (SRB), the terminal device receives a first indication message sent by the terminal device. The first indication message is sent by the terminal device when a first triggering condition is met. The first indication message is used to indicate whether the non-small data transmission data radio bearer (nonSDT DRB) on the terminal device side carries uplink data to be transmitted. During the small data transmission SDT process, the terminal does not trigger a buffer status report (BSR) through the specified SRB. After the SDT process ends, the terminal triggers a BSR through the specified SRB. The first triggering condition includes: the terminal device does not generate a Media Access Control (MAC) protocol data unit (PDU) corresponding to the data carried by the SDT DRB.

19. The method of claim 18, wherein, The specified SRB is either SRB0 or ​​SRB1.

20. The method of claim 18, wherein, The first indication information includes at least one of the following: A first identifier used to indicate whether the non-SDT DRB carries uplink data to be transmitted; A second identifier used to indicate the amount of uplink data to be transmitted carried in the non-SDT DRB; A third identifier used to indicate the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; The identifier of the terminal device; and The identifier of the non-SDT DRB.

21. The method of claim 18, wherein, The identifier of the non-SDT DRB is at least one of the following: DRB logo, Logical channel identifier, and Logical channel group identifier.

22. The method of claim 18, wherein, The method further includes: Send a second indication message to the terminal device, wherein the second indication message is used to indicate the first triggering condition.

23. The method according to any one of claims 18-22, characterized in that, The method further includes: Send a third indication message to the terminal device, wherein the third indication message is used to indicate a second triggering condition.

24. The method as described in claim 23, characterized in that, The second triggering condition includes any one of the following: The terminal device did not send the first access message Msg1 in the four-step random access process; The terminal device did not send the third access message Msg3 in the four-step random access process; The terminal device did not send the first access message MsgA in the two-step random access process; The terminal device did not send SDT data through its dedicated PUSCH; as well as The transmission priority of data carried by non-SDT DRB is higher than that of data carried by SDT DRB.

25. A communication device, characterized in that, The device includes: The transceiver module is used to send first indication information to the network device based on a specified signaling radio bearer (SRB) when a first triggering condition is met during small data transmission SDT (Small Data Transmission Technique). The first indication information indicates whether the device carries uplink data to be transmitted in a non-SDT DRB (Non-Small Data Transmission Radio Bearer). During the SDT, the device does not trigger a buffer status report (BSR) through the specified SRB. After the SDT process ends, the device triggers a BSR through the specified SRB. The first triggering condition includes: the device has not generated a Media Access Control (MAC) Protocol Data Unit (PDU) corresponding to the data carried by the SDT DRB.

26. The apparatus as claimed in claim 25, characterized in that, The specified SRB is either SRB0 or ​​SRB1.

27. The apparatus as claimed in claim 25, characterized in that, The transceiver module is also used to send the terminal device identification information to the network device via the general control channel (CCCH). The device further includes: The processing module is used to delete the identification information of the terminal device in the Packet Data Convergence Protocol (PDCP) data in the specified SRB, wherein the specified SRB is SRB1.

28. The apparatus as claimed in claim 25, characterized in that, The device further includes: The processing module is used in the SDT process to set the transmission priority of the specified SRB to be higher than that of the BSR.

29. The apparatus as claimed in claim 28, characterized in that, The processing module is further configured to: After the SDT process is completed, the transmission priority of the specified SRB is set to be lower than that of the BSR.

30. The apparatus as claimed in claim 26, characterized in that, The first indication information includes at least one of the following: A first identifier used to indicate whether the non-SDT DRB carries uplink data to be transmitted; A second identifier used to indicate the amount of uplink data to be transmitted carried in the non-SDT DRB; A third identifier used to indicate the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; The device's identifier; and The identifier of the non-SDT DRB.

31. The apparatus as claimed in claim 30, characterized in that, The identifier of the non-SDT DRB is at least one of the following: DRB logo, Logical channel identifier, and Logical channel group identifier.

32. The apparatus as claimed in claim 26, characterized in that, The transceiver module is also used for: The system receives a second indication message sent by the network device, wherein the second indication message is used to indicate the first triggering condition.

33. The apparatus as claimed in claim 26, characterized in that, The device further includes: A processing module is used to stop the SDT process.

34. The apparatus as claimed in claim 33, characterized in that, The processing module is specifically used for: Based on the second triggering condition, the SDT process is stopped.

35. The apparatus as claimed in claim 34, characterized in that, The second triggering condition includes any one of the following: The transceiver module did not send the first access message Msg1 in the four-step random access process; The transceiver module did not send the third access message Msg3 in the four-step random access process; The transceiver module did not send the first access message MsgA in the two-step random access process; The transceiver module did not send SDT data through the dedicated PUSCH; as well as The transmission priority of data carried by non-SDT DRB is higher than that of data carried by SDT DRB.

36. The apparatus as claimed in claim 34, characterized in that, The transceiver module is also used for: The third indication information sent by the network device is received, wherein the third indication information is used to indicate the second triggering condition.

37. The apparatus according to any one of claims 26-34, characterized in that, The device further includes a processing module, the processing module being used for: The transmission priority of the first indication information is set to be lower than the transmission priority of the data carried by the SDT DRB; or, The transmission priority of data carried by non-SDT DRB is set to be lower than that of data carried by SDT DRB.

38. The apparatus as claimed in claim 35, characterized in that: The transceiver module is configured to receive fourth indication information sent by the network device, and determine the end of the SDT process based on the fourth indication information; or, The processing module is used to determine the end of the SDT process when a specified number of SDT transmissions has been reached; or... The processing module is used to determine when the specified SDT transmission duration has been reached and to determine when the SDT process has ended.

39. The apparatus as claimed in claim 38, characterized in that, The fourth instruction information is any one of the following: The fourth access message, Msg4, in the four-step random access method. The second access message MsgB in two-step random access, and Community network temporary identifier C-RNTI.

40. The apparatus as claimed in claim 37, characterized in that, The processing module is further configured to: After the SDT process is completed, the transmission priority of the bearer channel used to carry the first indication information is set back to the transmission priority before the change; or, After the SDT process is completed, the transmission priority of the data carried by the non-SDT DRB is set back to the transmission priority before the change.

41. The apparatus according to any one of claims 25-34, characterized in that, The device further includes a processing module, the processing module being used for: When the non-SDT DRB carries uplink data to be sent, the state of the non-SDT DRB is set to data transmission / reception state.

42. A communication device, characterized in that, The device includes: The transceiver module is used to receive first indication information sent by the terminal device based on a specified signaling radio bearer (SRB). The first indication information is sent by the terminal device when a first triggering condition is met. The first indication information is used to indicate whether the non-small data transmission data radio bearer (nonSDT DRB) on the terminal device side carries uplink data to be transmitted. During the small data transmission SDT process, the terminal does not trigger buffer status reporting (BSR) through the specified SRB. After the SDT process ends, the terminal triggers BSR through the specified SRB. The first triggering condition includes: the terminal device does not generate a Media Access Control (MAC) protocol data unit (PDU) corresponding to the data carried by the SDT DRB.

43. The apparatus as claimed in claim 42, characterized in that, The specified SRB is either SRB0 or ​​SRB1.

44. The apparatus as claimed in claim 42, characterized in that, The first indication information includes at least one of the following: A first identifier used to indicate whether the non-SDT DRB carries uplink data to be transmitted; A second identifier used to indicate the amount of uplink data to be transmitted carried in the non-SDT DRB; A third identifier used to indicate the amount of uplink data to be transmitted carried in the logical channel group to which the non-SDT DRB belongs; The identifier of the terminal device; and The identifier of the non-SDT DRB.

45. The apparatus as claimed in claim 44, characterized in that, The identifier of the non-SDT DRB is at least one of the following: DRB logo, Logical channel identifier, and Logical channel group identifier.

46. ​​The apparatus as claimed in claim 42, characterized in that, The transceiver module is also used for: Send a second indication message to the terminal device, wherein the second indication message is used to indicate the first triggering condition.

47. The apparatus according to any one of claims 42-46, characterized in that, The transceiver module is also used for: Send a third indication message to the terminal device, wherein the third indication message is used to indicate a second triggering condition.

48. The apparatus as claimed in claim 47, characterized in that, The second triggering condition includes any one of the following: The terminal device did not send the first access message Msg1 in the four-step random access process; The terminal device did not send the third access message Msg3 in the four-step random access process; The terminal device did not send the first access message MsgA in the two-step random access process; The terminal device did not send SDT data through its dedicated PUSCH; as well as The transmission priority of data carried by non-SDT DRB is higher than that of data carried by SDT DRB.

49. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 1 to 17.

50. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 18 to 24.

51. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 1 to 17.

52. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 18 to 24.

53. A computer-readable storage medium for storing instructions that, when executed, cause the method as described in any one of claims 1 to 17 to be implemented.

54. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 18 to 24 to be implemented.

Images