Method and communication device for acquiring resources

Abstract

The present application provides a method and communication device for acquiring resources. In this method, a terminal device can simultaneously indicate one or more of a buffer status report, a power headroom report, or information about the number of data packets to a network device, and the network device can configure resources for the terminal device based on one or more of the buffer status report, power headroom report, or information about the number of data packets. If the terminal device simultaneously indicates multiple of the buffer status report, power headroom report, or information about the number of data packets to the network device, this can avoid the terminal device having to send three times and the network device having to receive three times, thereby helping to reduce power consumption of both the terminal device and the network device.

Description

Technical Field

[0001] The present application relates to the field of communications, and more particularly to a method and a communication device for acquiring resources in the field of communications. Background Art

[0002] In some scenarios, terminal devices need to send parameters to network devices. The network devices can then allocate data transmission resources to the terminal devices based on the parameters reported by the terminal devices. When a terminal device needs to send multiple parameters to the network device, the terminal device must send these parameters separately, resulting in high overhead. Furthermore, the terminal device must send and the network device must receive these parameters multiple times, which results in high energy consumption for both the terminal and network devices. Summary of the Invention

[0003] The embodiments of the present application provide a method and a communication device for acquiring resources, which can reduce the energy consumption of the terminal device and the network device, and can also reduce signaling overhead.

[0004] According to a first aspect, a method for acquiring resources is provided. The method is applicable to a terminal device, comprising: indicating at least one of a buffer status report, a power headroom report, or data packet quantity information to a network device, wherein the buffer status report is used to indicate the amount of data in the buffer, the power headroom report is used to indicate the power headroom of the terminal device, and the data packet quantity information is used to indicate the number of data packets to be subsequently transmitted;

[0005] Resources configured by the network device according to at least one of a buffer status report, a power headroom report, or information on the number of data packets are acquired.

[0006] In the above solution, the terminal device can simultaneously indicate one or more of the following: a buffer status report, a power headroom report, or the number of data packets to the network device, and the network device can configure resources for the terminal device based on the following: the buffer status report, the power headroom report, or the number of data packets. If the terminal device simultaneously indicates multiple of the following: the buffer status report, the power headroom report, or the number of data packets to the network device, this avoids the need for the terminal device to send three times and the network device to receive three times, thereby helping to reduce power consumption of both the terminal device and the network device.

[0007] Optionally, the method is applicable to scenarios where small packets are transmitted.

[0008] Optionally, the method is applicable to a scenario where the terminal device is in an RRC non-connected state. Optionally, the method is applicable to a scenario where the terminal device is in an RRC inactive (RRC_INACTIVE) state.

[0009] Optionally, the buffer status report is used to provide the network device with information on the amount of uplink data in the MAC entity.

[0010] Optionally, the buffer status report is used to provide the network device with information on the amount of uplink packet data in the MAC entity. Optionally, the uplink packet data is available uplink packet data of the logical channel corresponding to the SDT DRB.

[0011] Optionally, the number of data packets subsequently transmitted may be the uplink and / or downlink transmission expected by the terminal device, and the transmission may be a small packet transmission.

[0012] Optionally, the power headroom of the terminal device may indicate information about a difference between a nominal maximum transmission power of the terminal device and an estimated transmission power of the terminal device.

[0013] Optionally, the estimated transmission power of the terminal device may indicate the estimated transmission power of an uplink shared channel (UL-SCH) of each activated serving cell.

[0014] Optionally, the estimated transmission power of the terminal device may indicate the estimated transmission power of the UL-SCH and the physical uplink control channel of the special cell.

[0015] Optionally, the estimated transmission power of the terminal device may indicate the estimated transmission power of a channel sounding reference signal of each activated serving cell.

[0016] Optionally, the estimated transmission power of the terminal device may indicate a power backoff, where the power backoff is used to meet a maximum allowed exposure requirement of a serving cell operating in frequency range 2.

[0017] Optionally, a first MAC CE is sent to the network device, where the first MAC CE is used to indicate at least one of a buffer status report, a power headroom report, or the number of data packets, the buffer status report is used to indicate the amount of data in the buffer, the power headroom report is used to indicate the power headroom of the terminal device, and the number of data packets is used to indicate the number of data packets to be subsequently transmitted; and resources configured by the network device according to the first MAC CE are obtained.

[0018] In the above solution, one or more of a buffer status report, a power headroom report, or information about the number of data packets can be indicated by the first MAC CE. If the first MAC CE indicates multiple items of the buffer status report, the power headroom report, or information about the number of data packets, one MAC CE corresponds to one MAC subheader, thereby saving MAC subheader overhead. If a terminal device needs to indicate three items of the buffer status report, the power headroom report, and information about the number of data packets, three MAC CEs may be required. Three MAC CEs correspond to three MAC subheaders, resulting in a relatively large MAC subheader overhead. In the present application, multiple items of the buffer status report, the power headroom report, or information about the number of data packets can be indicated by the first MAC CE. The first MAC CE corresponds to one MAC subheader, thereby saving MAC subheaders and facilitating overhead savings.

[0019] Optionally, if the logical channel priority (LCP) of the first MAC CE is higher than the logical channel priority of the data to be sent, the terminal device gives priority to sending the first MAC CE to the network device. For example, the data to be sent may be small packet data or small data. That is, when the terminal device needs to send the first MAC CE and small data in the SDT scenario, the terminal device may compare the logical channel priority of the first MAC CE with the logical channel priority of the small data. If the logical channel priority of the first MAC CE is higher than the logical channel priority of the small data, in the case of limited resources, the first MAC CE is given priority when packaging. If there are remaining resources after packaging the first MAC CE, the small data may be packaged again; if there are no remaining resources after packaging the first MAC CE, the terminal device sends the small data on the resources configured by the network device according to the first MAC CE. In other words, the terminal device needs to give priority to sending the first MAC CE to the network device so that the network device can configure resources for the terminal device.

[0020] Optionally, after obtaining the resources configured by the network device according to the first MAC CE, if one or more of the buffer status report, power headroom report or data packet quantity information changes, the terminal device can send a second MAC CE on the acquired resources, and the second MAC CE is used to indicate the changed buffer status report, the changed power headroom report or the changed data packet quantity information.

[0021] In some possible implementations, if the first MAC CE is used to indicate the buffer status report, the bits carried by the first indication field included in the first MAC CE are used to indicate the buffer status report; if the first MAC CE is used to indicate the power headroom report, the bits carried by the second indication field included in the first MAC CE are used to indicate the power headroom report; if the first MAC CE is used to indicate the quantity information of the data packets, the bits carried by the third indication field included in the first MAC CE are used to indicate the quantity information of the data packets.

[0022] In the above solution, the bits carried by the first indication field, the second indication field and the third indication field included in the first MAC CE are used to indicate the buffer status report, the power headroom report and the number of data packets respectively.

[0023] Optionally, the first MAC CE can be a fixed length in a fixed format. If the first MAC CE is used to indicate a buffer status report, the first MAC CE includes a first indication field. If the first MAC CE does not indicate a buffer status report, the first MAC CE does not include the first indication field, and the original field of the first indication field is a reserved bit. If the first MAC CE is used to indicate a power headroom report, the first MAC CE includes a second indication field. If the first MAC CE does not indicate a power headroom report, the first MAC CE does not include the second indication field, and the original field of the second indication field is a reserved bit. If the first MAC CE is used to indicate the number information of data packets, the first MAC CE includes the first indication field. If the first MAC CE does not indicate the number information of data packets, the first MAC CE does not include the third indication field, and the original field of the third indication field is a reserved bit.

[0024] Optionally, the first MAC CE may not be in a fixed format, and the length of the first MAC CE may not be fixed. If the first MAC CE is used to indicate a buffer status report, the first MAC CE includes a first indication field; if the first MAC CE does not indicate a buffer status report, the first MAC CE does not include the first indication field, and the length of the first MAC CE is reduced by the length of the first indication field; if the first MAC CE is used to indicate a power headroom report, the first MAC CE includes a second indication field; if the first MAC CE does not indicate a power headroom report, the first MAC CE does not include the second indication field, and the length of the first MAC CE is reduced by the length of the second indication field; if the first MAC CE is used to indicate the number information of data packets, the first MAC CE includes a first indication field; if the first MAC CE does not indicate the number information of data packets, the first MAC CE does not include a third indication field, and the length of the first MAC CE is reduced by the length of the third indication field.

[0025] In some possible implementations, it is characterized in that the first MAC CE includes a fourth indication field, and the bits carried by the fourth indication field are used to indicate whether the first MAC CE includes the first indication field.

[0026] In the above scheme, the bit carried by the fourth indication field included in the first MAC CE is used to indicate whether the first MAC CE includes the first indication field. If the bit carried by the fourth indication field is used to indicate that the first MAC CE includes the first indication field, the network device can parse the first indication field according to the fourth indication field, otherwise the network device does not parse the first indication field.

[0027] Optionally, the number of bits corresponding to the fourth indication field is 1. For example, if the bit carried by the fourth indication field is 1, it indicates that the first MAC CE includes the first indication field, and if the bit carried by the fourth indication field is 0, it indicates that the first MAC CE does not include the first indication field.

[0028] Optionally, the first MAC CE may not include the fourth indication field, and the first MAC CE includes the first indication field by default, or the first MAC CE does not include the first indication field by default.

[0029] In some possible implementations, the first MAC CE includes a fifth indication field, and the bits carried by the fifth indication field are used to indicate the type of buffer status report indicated by the bits carried by the first indication field.

[0030] In the above solution, the bits carried by the fifth indication field included in the first MAC CE are used to indicate the type of buffer status report indicated by the first indication field. In this way, the network device can determine the type of buffer status report indicated by the first indication field based on the fifth indication field.

[0031] Optionally, if there is a fourth indication field, and the bit carried by the fourth indication field indicates that the first MAC CE includes the first indication field, then the first MAC CE includes the fifth indication field; optionally, if there is a fourth indication field, and the graduation indication carried by the fourth indication field indicates that the first MAC CE does not include the first indication field, then the first MAC CE does not include the fifth indication field.

[0032] In some possible implementations, the first MAC CE includes a sixth indication field, and the bits carried by the sixth indication field are used to indicate whether the first MAC CE includes the second indication field.

[0033] In the above scheme, the bit carried by the sixth indication field included in the first MAC CE is used to indicate whether the first MAC CE includes the second indication field. If the bit carried by the sixth indication field is used to indicate that the first MAC CE includes the second indication field, the network device can parse the second indication field according to the sixth indication field, otherwise the network device does not parse the second indication field.

[0034] Optionally, the number of bits corresponding to the sixth indication field is 1. For example, if the bit carried by the sixth indication field is 1, it indicates that the first MAC CE includes the second indication field, and if the bit carried by the sixth indication field is 0, it indicates that the first MAC CE does not include the second indication field.

[0035] Optionally, the first MAC CE may not include the sixth indication field, and the first MAC CE includes the second indication field by default, or the first MAC CE does not include the second indication field by default.

[0036] In some possible implementations, the first MAC CE includes a seventh indication field, and the bits carried by the seventh indication field are used to indicate whether the first MAC CE includes the third indication field.

[0037] In the above scheme, the bit carried by the seventh indication field included in the first MAC CE is used to indicate whether the first MAC CE includes the third indication field. If the bit carried by the seventh indication field is used to indicate that the first MAC CE includes the third indication field, the network device can parse the third indication field according to the seventh indication field, otherwise the network device does not parse the third indication field.

[0038] Optionally, the number of bits corresponding to the seventh indication field is 1. For example, if the bit carried by the seventh indication field is 1, it indicates that the first MAC CE includes the third indication field, and if the bit carried by the seventh indication field is 0, it indicates that the first MAC CE does not include the third indication field.

[0039] Optionally, the first MAC CE may not include the seventh indication field, and the first MAC CE includes the third indication field by default, or the first MAC CE does not include the third indication field by default.

[0040] In some possible implementations, the sending of the first MAC CE to the network device includes: when it is determined that there is small packet data in the buffer, sending the first MAC CE to the network device, the first MAC CE being used to indicate the buffer status report and the power headroom report, the buffer status report being used to indicate the amount of small packet data in the buffer.

[0041] In the above solution, when it is determined that there is small packet data in the buffer, the sending of the power headroom report and the status buffer report is triggered. Therefore, the first MAC CE can indicate the buffer status report and the power headroom report.

[0042] In some possible implementations, when it is determined that there is subsequent transmission, the first MAC CE is sent to the network device, and the first MAC CE is used to indicate the quantity information of the data packets and the power headroom report, and the quantity information of the data packets is used to indicate the number of data packets of the small packet data to be transmitted subsequently.

[0043] In the above solution, when it is determined that there is subsequent transmission, the sending of the quantity information of the data packets and the power headroom report is triggered. Therefore, the first MAC CE can indicate the quantity information of the data packets and the power headroom report.

[0044] In some possible implementations, when it is determined that there is small packet data in the buffer and that there is subsequent transmission, the first MAC CE is sent to the network device, and the first MAC CE is used to indicate the buffer status report, the number information of the data packets and the power headroom report, the buffer status report is used to indicate the amount of small packet data in the buffer, and the number information of the data packets is used to indicate the number of data packets of the small packet data to be transmitted subsequently.

[0045] In the above solution, when it is determined that there is subsequent transmission and small packet data exists in the buffer, the sending of the quantity information of the data packets, the power headroom report and the buffer status report is triggered.

[0046] In the embodiment of the present application, “subsequent transmission” can be understood as: small data that arrives subsequently. Alternatively, “subsequent transmission” in the embodiment of the present application can be replaced by small data that arrives subsequently.

[0047] In some possible implementations, the terminal device is in a radio resource control (RRC) non-connected state, and sending the first MAC CE to the network device includes: sending the first MAC CE to the network device through a random access process.

[0048] In the above scheme, the terminal device can send the first MAC CE to the network device through a random access process, for example, sending the first MAC CE to the network device through message 3 or message A in the random access process. In this way, it is possible for the terminal device to send the first MAC CE to the network device.

[0049] In some possible implementations, the terminal device is in a radio resource control (RRC) non-connected state, and the sending of the first MAC CE to the network device includes: sending the first MAC CE to the network device through pre-configured resources.

[0050] Optionally, the terminal device may send auxiliary information to the network device during a random access procedure or on pre-configured resources. The auxiliary information is used to instruct the network device not to terminate packet data transmission with the terminal device. The network device configures resources for the terminal device based on the auxiliary information, and the terminal device sends a first MAC CE to the network device on the resources configured by the network device based on the auxiliary information. In other words, the terminal device may send indication information to the network device indicating not to terminate packet data transmission for the terminal device. The network device does not terminate packet data transmission for the terminal device based on the indication information and configures resources. The terminal device may send the first MAC CE on the configured resources. Optionally, the auxiliary information may be a buffer status report or information about the number of data packets.

[0051] In the above solution, when the terminal device is in the RRC non-connected state, it can send the first MAC CE to the network device through pre-configured resources. In this way, it is possible for the terminal device to send the first MAC CE to the network device.

[0052] In some possible implementations, the acquiring the resources configured by the network device according to the first MAC CE includes: acquiring the resources scheduled by the network device through first downlink control information DCI according to the first MAC CE.

[0053] Optionally, the first DCI scheduled resource may be a dynamically scheduled resource, and the dynamically scheduled resource may be a dynamically scheduled uplink periodic resource or one dynamically scheduled resource or multiple dynamically scheduled non-periodic resources.

[0054] Optionally, if the terminal device sends a first MAC CE to the network device through a random access process, it is assumed that the terminal device requires the network device to dynamically schedule resources through the first DCI, or it can be understood that the pre-configured resources of the terminal device are invalid, and therefore the network device is expected to dynamically schedule resources through the first DCI.

[0055] In some possible implementations, the acquiring the resources configured by the network device according to the first MAC CE includes: acquiring pre-configured resources configured by the network device according to the first MAC CE.

[0056] In the above solution, the network device can reconfigure pre-configured resources for the terminal device based on the first MAC CE.

[0057] Optionally, if the terminal device sends the first MAC CE to the network device through a random access process, it is assumed that the terminal device requires the network device to reconfigure resources, or it can be understood that the preconfigured resources already configured by the terminal device are invalid, and therefore the network device is expected to reconfigure the preconfigured resources.

[0058] In some possible implementations, the acquiring the resources configured by the network device according to the first MAC CE includes: using pre-configured resources configured in advance by the network device as the resources configured by the network device according to the first MAC CE.

[0059] In the above solution, the terminal device can use the pre-configured resources configured in advance by the network device as the resources configured by the network device according to the first MAC CE. That is, the network device does not need to reconfigure resources, and the terminal device directly adopts the previously configured pre-configured resources.

[0060] Optionally, after receiving the first MAC CE, the network device may send indication information to the terminal device for instructing to continue to use the pre-configured resources configured in advance, and the terminal device continues to use the pre-configured resources configured in advance according to the indication information.

[0061] Optionally, after sending the first MAC CE, the terminal device does not receive resources configured by the network device after a preset time period, and continues to use the pre-configured resources configured in advance by default.

[0062] Optionally, the terminal device may send data to the network device or receive data from the network device based on the resources configured by the network device according to the first MAC CE.

[0063] In some possible implementations, the MAC subheader corresponding to the first MAC CE is a first MAC subheader, and the first MAC subheader includes an eighth indication field, and the bits carried by the eighth indication field are used to indicate that the value of the logical channel identifier LCID corresponding to the first MAC CE is a first value, and the first value is used to indicate that the first MAC CE is used to indicate at least two of the buffer status report, the power headroom report, or the quantity information of the data packets.

[0064] In the above scheme, the first MAC CE corresponds to the first MAC subheader, and the eighth indication field in the first MAC subheader indicates that the LCID of the first MAC CE is the first value. In this way, after the network device receives the first MAC subheader, it determines that the first MAC CE is a composite MAC CE carrying multiple parameters.

[0065] In some possible implementations, the information on the number of data packets is also used to indicate the number of data packets to be received, and the method further includes: the terminal device receives a second DCI from the network device, and the second DCI is used to indicate the resources for the terminal device to receive downlink data; the terminal device receives downlink data from the network device on the resources for receiving downlink data.

[0066] Optionally, the resources indicated by the second DCI for the terminal device to receive downlink data include: a dynamically scheduled resource or a dynamically scheduled semi-persistent scheduling (SPS) resource or a dynamically scheduled periodic resource or a plurality of dynamically scheduled non-periodic resources.

[0067] According to a second aspect, a method for acquiring resources is provided, the method being applicable to a network device, comprising: obtaining at least two of a buffer status report, a power headroom report, or data packet quantity information from a terminal device, wherein the buffer status report is used to indicate the amount of data in the buffer, the power headroom report is used to indicate the power headroom of the terminal device, and the data packet quantity information is used to indicate the number of data packets subsequently transmitted by the terminal device;

[0068] Resources are configured for the terminal device according to at least two of the buffer status report, the power headroom report, or the quantity information of the data packets.

[0069] In the above solution, the terminal device can simultaneously indicate one or more of the following: a buffer status report, a power headroom report, or the number of data packets to the network device, and the network device can configure resources for the terminal device based on the following: the buffer status report, the power headroom report, or the number of data packets. If the terminal device simultaneously indicates multiple of the following: the buffer status report, the power headroom report, or the number of data packets to the network device, this avoids the need for the terminal device to send three times and the network device to receive three times, thereby helping to reduce power consumption of both the terminal device and the network device.

[0070] Optionally, the method further includes: receiving data sent by the terminal device on the configured resources.

[0071] In some possible implementations, if the first MAC CE is used to indicate the buffer status report, the bits carried by the first indication field included in the first MAC CE are used to indicate the buffer status report; if the first MAC CE is used to indicate the power headroom report, the bits carried by the second indication field included in the first MAC CE are used to indicate the power headroom report; if the first MAC CE is used to indicate the quantity information of the data packets, the bits carried by the third indication field included in the first MAC CE are used to indicate the quantity information of the data packets.

[0072] In some possible implementations, the first MAC CE includes a fourth indication field, and the bits carried by the fourth indication field are used to indicate whether the first MAC CE includes the first indication field.

[0073] In some possible implementations, the first MAC CE includes a fifth indication field, and the bits carried by the fifth indication field are used to indicate the type of buffer status report indicated by the bits carried by the first indication field.

[0074] In some possible implementations, the first MAC CE includes a sixth indication field, and the bits carried by the sixth indication field are used to indicate whether the first MAC CE includes the second indication field.

[0075] In some possible implementations, the first MAC CE includes a seventh indication field, and the bits carried by the seventh indication field are used to indicate whether the first MAC CE includes the third indication field.

[0076] In some possible implementations, the receiving a first MAC CE from the terminal device includes:

[0077] receiving the first MAC CE from the terminal device through a random access procedure of the terminal device; or,

[0078] The first MAC CE is received from the terminal device through preconfigured resources.

[0079] In some possible implementations, configuring resources for the terminal device according to the first MAC CE includes:

[0080] Scheduling resources for the terminal device through a first DCI according to the first MAC CE; or,

[0081] configuring corresponding pre-configured resources for the terminal device according to the first MAC CE; or,

[0082] The pre-configured resources configured in advance for the terminal device are used as the resources configured for the terminal device according to the first MAC CE.

[0083] In some possible implementations, the MAC subheader corresponding to the first MAC CE is a first MAC subheader, and the first MAC subheader includes an eighth indication field, and the bits carried by the eighth indication field are used to indicate that the value of the logical channel identifier LCID corresponding to the first MAC CE is a first value, and the first value is used to indicate that the first MAC CE is used to indicate at least two of the buffer status report, the power headroom report, or the quantity information of the data packets.

[0084] In some possible implementations, the buffer status report is used to indicate the amount of small packet data in the buffer, and the data packet quantity information is used to indicate the number of data packets of the small packet data to be subsequently transmitted.

[0085] In some possible implementations, the method further includes: after receiving the first MAC CE, determining not to end transmission of the packet data with the terminal device;

[0086] If the first MAC CE is used to indicate the buffer status report and / or the quantity information of the data packets, then after receiving the amount of data in the buffer indicated by the buffer status report, and / or the number of data packets to be sent indicated by the quantity information of the data packets, the transmission of the small packet data between the terminal device is terminated.

[0087] Optionally, determining not to end the transmission of the packet data with the terminal device may be replaced by: not releasing the terminal device or not sending an RRC release message to the terminal device or the terminal device continuing to maintain the current state without change, etc.

[0088] In some possible implementations, the information on the number of data packets is also used to indicate the number of data packets to be received, and the method further includes: sending a second DCI to the terminal device, where the second DCI is used to indicate the resources for the terminal device to receive downlink data; and the network device sends downlink data to the terminal device on the resources for the terminal device to receive downlink data.

[0089] Specifically, for the detailed description of the second aspect or any possible implementation of the second aspect, please refer to the first aspect or any possible implementation of the first aspect.

[0090] In a third aspect, a communication device for acquiring resources is provided, wherein the communication device is used to execute the method in any possible implementation of the first aspect, or execute the method in any possible implementation of the second aspect. Optionally, the communication device may include a unit of the method described in any embodiment of the present application. Optionally, the communication device may include a processing unit and a transceiver unit. The transceiver unit can communicate with the outside, and the processing unit is used to perform data processing. The transceiver unit may also be referred to as a communication interface or a communication unit.

[0091] The communication device can be used to execute the actions performed by the terminal device in any possible implementation of the first aspect. In this case, the communication device can be called a terminal device, the transceiver unit is used to execute the transceiver-related operations on the terminal device side in any possible implementation of the first aspect, and the processing unit is used to execute the processing-related operations on the terminal device side in any possible implementation of the first aspect.

[0092] The communication device can be used to execute the actions performed by the network device in any possible implementation of the second aspect. In this case, the communication device can be called a network device, the transceiver unit is used to execute the transceiver-related operations on the network device side in any possible implementation of the second aspect, and the processing unit is used to execute the processing-related operations on the network device side in any possible implementation of the second aspect.

[0093] In a fourth aspect, a communication device is provided, which includes a processor and a memory, the processor being coupled to the memory, the memory being used to store computer programs or instructions, and the processor being used to execute the computer programs or instructions stored in the memory, so that the method in the above-mentioned first aspect or any possible implementation of the first aspect is executed, or the method in the above-mentioned second aspect or any possible implementation of the second aspect is executed, or the method described in other embodiments of the present application is executed.

[0094] For example, the processor is used to execute a computer program or instruction stored in the memory, so that the communication device executes the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.

[0095] Optionally, the device includes one or more processors.

[0096] Optionally, the device may further include a memory coupled to the processor.

[0097] Optionally, the device may include one or more memories.

[0098] Optionally, the memory may be integrated with the processor or provided separately.

[0099] Optionally, the device may further include a transceiver.

[0100] In a fifth aspect, a communication system is provided, which includes the communication device in the third aspect for executing the method in any possible implementation of the first aspect and the communication device for executing the method in any possible implementation of the second aspect; or, the communication system includes the communication device in the fourth aspect for executing the method in any possible implementation of the first aspect and the communication device for executing the method in any possible implementation of the second aspect.

[0101] In a sixth aspect, a computer-readable storage medium is provided, on which is stored a computer program (also referred to as instructions or codes) for implementing the method in the first aspect or any possible implementation manner of the first aspect.

[0102] For example, when the computer program is executed by a computer, the computer can execute the method in the first aspect or any possible implementation of the first aspect. The computer can be a communication device.

[0103] For another example, when the computer program is executed by a computer, the computer can execute the method in the second aspect or any possible implementation of the second aspect. The computer can be a communication device.

[0104] In a seventh aspect, the present application provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in a memory to perform the method of the first aspect and any possible implementation thereof, or the method of the second aspect and any possible implementation thereof, or the method described in other embodiments of the present application.

[0105] Optionally, the chip further includes a memory, and the memory is connected to the processor via a circuit or wire.

[0106] In an eighth aspect, the present application provides a computer program product, comprising a computer program (also referred to as instructions or codes), wherein when the computer program is executed by a computer, the computer implements the method of the first aspect or any possible implementation of the first aspect, or, when the computer program is executed by a computer, the computer implements the method of the second aspect or any possible implementation of the second aspect, or, when the computer program is executed by a computer, the computer implements the method of the implementation in any embodiment of the present application.

[0107] In a ninth aspect, the present application provides a communication device comprising a unit for implementing the method described in any embodiment of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0108] Figure 1 It is a schematic diagram of a communication system provided in an embodiment of the present application.

[0109] Figure 2A It is a structural diagram of the user plane air interface protocol stack provided in an embodiment of the present application.

[0110] Figure 2B It is a structural diagram of the control plane air interface protocol stack provided in an embodiment of the present application.

[0111] Figure 3 This is a schematic diagram of the RRC state transition provided in an embodiment of the present application.

[0112] Figure 4 This is a schematic diagram of the MAC subheader corresponding to the short BSR MAC CE and the short truncated BSR MAC CE provided in an embodiment of the present application.

[0113] Figure 5 It is a schematic diagram of a short BSR MAC CE and a short truncated BSR MAC CE provided in an embodiment of the present application.

[0114] Figure 6 This is a schematic diagram of the MAC subheader corresponding to the long BSR MAC CE and the long truncated BSR MAC CE provided in an embodiment of the present application.

[0115] Figure 7 It is a schematic diagram of a long BSR MAC CE and a long truncated BSR MAC CE provided in an embodiment of the present application.

[0116] Figure 8 This is a format diagram of DCQR and AS RAI MAC CE provided in an embodiment of the present application.

[0117] Figure 9A and Figure 9B This is a format diagram of the PHR MAC CE provided in an embodiment of the present application.

[0118] Figure 10 This is a schematic diagram of SDT based on the principle of four-step random access provided in an embodiment of the present application.

[0119] Figure 11 This is a schematic diagram of performing SDT based on the principle of two-step random access provided in an embodiment of the present application.

[0120] Figure 12 Schematic diagram of CG-SDT provided in an embodiment of the present application.

[0121] Figure 13 It is a schematic diagram of the DRB provided in an embodiment of the present application.

[0122] Figure 14 This is a schematic diagram of a method for transmitting data provided in an embodiment of the present application.

[0123] Figures 15-18 This is a format diagram of the first MAC CE provided in an embodiment of the present application.

[0124] Figure 19 This is a schematic diagram of the network device provided in an embodiment of the present application, including a CU and a DU.

[0125] Figure 20-25 This is a schematic diagram of a method for transmitting small data provided in an embodiment of the present application.

[0126] Figure 26 This is a schematic diagram of a data transmission device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0127] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0128] It should be understood that the methods, situations, categories and divisions of the embodiments in the present application are only for the convenience of description and should not constitute special limitations. The features of various methods, categories, situations and embodiments can be combined without contradiction.

[0129] It should also be understood that the terms "first," "second," and "third" in the embodiments of this application are for distinction only and should not constitute any limitation on this application. It should also be understood that in the various embodiments of this application, the order of the sequence numbers of the processes does not imply a specific order of execution. The order of execution of the processes should be determined by their functions and inherent logic, and should not constitute any limitation on the implementation of the embodiments of this application.

[0130] Figure 1 Schematic diagram of a communication system applicable to the embodiment of the present application. Figure 1 As shown, the wireless communication system may include at least one network device 110, the network device 110 and one or more terminal devices (eg Figure 1 1 and 120). When network device 110 sends a signal, network device 110 is a transmitter and terminal device 120 is a receiver. Conversely, when terminal device 120 sends a signal, terminal device 120 is a transmitter and network device 110 is a receiver.

[0131] The network device 110 may be an access network device for communicating with the terminal device 110. The network device 110 may be a base transceiver station (BTS) in a GSM system or a CDMA system, a base station node B (NB) in a WCDMA system, an evolved NodeB (eNB or eNodeB) in an LTE system, a wireless controller in a cloud radio access network (CRAN) scenario, a next-generation base station (g Node B, gNB) in the fifth-generation mobile networks (5G), i.e., new radio (NR), or a base station in other future network systems. It may also be a component or part of a network device, such as a central unit (CU), a distributed unit (DU), or a baseband unit (BBU). Alternatively, the network device 110 may be a relay station, an access point, an in-vehicle device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network, etc., and the embodiments of the present application are not limited thereto.

[0132] The terminal device 120 may refer to user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a handheld device, a wearable device, a computing device, a portable device or an in-vehicle device, a terminal in the form of a smart phone, smart glasses, a terminal device in a 5G network, or a terminal device in a future-evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0133] It is understandable that Figure 1The network device 110 in the embodiment can also be replaced by the terminal device 120. That is, the embodiment of the present application is applied to scenarios of direct communication such as device to device (D2D). For example, it can be applied to vehicle to everything (V2X).

[0134] For the convenience of description, the device numbers are omitted below. For example, “terminal device” refers to “terminal device 120” and “network device” refers to “network device 110”.

[0135] Figure 2A FIG. 1 shows a schematic diagram of the structure of a user plane air interface protocol stack provided by an embodiment of the present application. Figure 2A As shown, the user plane air interface protocol stack includes but is not limited to the service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), media access control (MAC), and physical (PHY) layers. The SDAP layer is located below the PDCP layer. The SDAP layer is used to map quality of service (QoS) to data radio bearers (DRBs).

[0136] Figure 2B FIG. 1 shows a schematic diagram of the structure of a control plane air interface protocol stack provided by an embodiment of the present application. Figure 2B As shown, the control plane air interface protocol stack includes but is not limited to the radio resource control (RRC) layer, the PDCP layer, the RLC layer, the media access control (MAC) layer, and the physical (PHY) layer. The lower layer of the RRC layer is the PDCP layer.

[0137] exist Figure 2A and Figure 2BIn the PDCP layer, the RLC layer is located below the PDCP layer. The PDCP layer processes RRC messages on the control plane and performs IP header compression to reduce the number of bits transmitted on the radio interface. The PDCP layer is also responsible for control plane encryption and integrity protection of transmitted data. At the receiving end, the PDCP protocol layer performs the corresponding decryption and decompression operations. A PDCP entity can be configured for each radio bearer. The RLC layer is responsible for segmentation / concatenation, retransmission control, and duplicate detection. The RLC layer provides services to the PDCP layer and an RLC entity can be configured for each radio bearer. The MAC layer controls the multiplexing of logical channels, retransmission of hybrid automatic repeat requests, and scheduling of uplink and downlink links. The MAC layer provides services to the RLC layer in the form of logical channels. The PHY layer manages encoding / decoding, modulation / demodulation, multi-antenna mapping, and other types of physical layer functions. The PHY layer provides services to the MAC layer in the form of transport channels.

[0138] like Figure 2A and Figure 2B As shown in the figure, the MAC layer can provide services to higher layers (such as the RLC layer) via logical channels (logical channels, LCH). According to the type of information sent, logical channels can be classified into control channels for transmitting control information on the control plane and traffic channels for transmitting user data on the user plane. Figure 2A In the MAC layer and the RLC layer, the logical channel can be called a traffic channel. Figure 2BIn the present invention, the logical channel between the MAC layer and the RLC layer can be called a control channel. Among them, the control channel may include but is not limited to a common control channel (CCCH) and a dedicated control channel (DCCH). The traffic channel may include but is not limited to a dedicated traffic channel (DTCH). The CCCH can exist at all times, and a terminal device that does not have an RRC connection with a network device can also use the CCCH to transmit information. The DCCH can be used to transmit dedicated control information between a terminal device and a network device. The DTCH can be used to transmit user data between a terminal device and a network device. Generally, the DCCH and DTCH do not exist at all times, but can only be used for communication between the terminal device and the network device after the network device connected to the terminal device restores the terminal device context (terminal device context). Among them, the terminal device context includes but is not limited to the terminal device identifier, radio bearer (RB) related configuration, security related configuration of integrity protection and encryption, quality of service related configuration, etc. When a network device configures a logical channel for a terminal device, it also indicates the logical channel group (LCG) to which the logical channel belongs. That is, the network device knows which LCG each logical channel belongs to.

[0139] At the RRC layer, a terminal device typically exists in three states: RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE. These three states are explained below.

[0140] RRC_CONNECTED state

[0141] If a terminal device establishes an RRC connection with a network device, the terminal device is in the RRC_CONNECTED state. In the RRC_CONNECTED state, the terminal device can establish a user plane and control plane connection with the network device; the network device and the terminal device also store the context of the terminal device's access-stratum (AS); the network device can know the cell to which the terminal device belongs; the terminal device can receive data sent by the network device, and the terminal device can also send data to the network device; the terminal device can measure the channel between the terminal device and the network device, and report the measurement results to the network device, and the network device can determine whether to switch the cell to which the terminal device belongs based on the measurement results. In other words, in the RRC_CONNECTED state, the terminal device and the network device can not only transmit data normally, but the network device can also manage the terminal device. If a terminal device in the RRC_CONNECTED state wants to send uplink data to the network device, it needs to maintain synchronization with the network device based on the timing advance (TA). If a terminal device in the RRC_CONNECTED state does not obtain uplink synchronization, the terminal device can initiate random access (RA) to the network device. When the terminal device's uplink timing advance timer (TAT) keeps running, the terminal device maintains uplink synchronization. When the terminal device's TAT ​​times out, the terminal device's uplink synchronization fails. If the terminal device needs to send uplink data to the network device again, it needs to initiate an RA to obtain a new TA.

[0142] RRC_IDLE state

[0143] If the terminal device has not established an RRC connection with the network device, the terminal device is in the RRC_IDLE state. In the RRC_IDLE state, the terminal device can select a PLMN, receive system messages broadcast by the network device, reselect a cell, and receive paging messages.

[0144] RRC_INACTIVE state

[0145] If the terminal device establishes an RRC connection with the network device, the terminal device enters the RRC_CONNECTED state. If the terminal device has no data transmission needs with the network device within the preset time period in the RRC_CONNECTED state, the network device may determine that the terminal device has entered the RRC_INACTIVE state and may send an RRC release (RRC Release with Suspend Indication) message carrying a suspend indication to the terminal device. After the terminal device receives the RRC Release with Suspend Indication message, the terminal device retains its own context and enters the RRC_INACTIVE state.

[0146] Among them, the above three states in the RRC layer can be converted to each other, such as Figure 3 As shown, when the terminal device is in the RRC connected (RRC_CONNECTED) state, the network device can send an RRC release message to the terminal device, and the terminal device can release the RRC resources between it and the network device and then enter the RRC idle (RRC_IDLE) state. When the terminal device is in the RRC idle (RRC_IDLE) state, it can send an RRC establishment request message to the network device, and the network device can establish an RRC connection with the terminal device based on the RRC establishment request message, so that the terminal device can enter the RRC connected (RRC_CONNECTED) state. When the terminal device is in the RRC connected (RRC_CONNECTED) state, the network device can send an RRC release (RRC release with suspend indication) message carrying a suspend indication to the terminal device, and after receiving the RRC release with suspend indication message, the terminal device enters the RRC inactive (RRC_INACTIVE) state. When the terminal device is in the RRC inactive (RRC_INACTIVE) state, if there is data to be transmitted, the terminal device can send an RRC resume request message to the network device, and the network device can send an RRC resume response message to the terminal device. After the terminal device receives the resume response message, it can send an RRC recovery completion message to the network device, and the terminal device enters the RRC_CONNECTED state and resumes using the context of the terminal device. It can be understood that compared to entering the RRC_CONNECTED state from the RRC_IDLE state, the terminal device enters the RRC CONNECTED state faster from the RRC_INACTIVE state. If the terminal device is in the RRC_INACTIVE state, the network device can send an RRC release message to the terminal device, and the terminal device can release the RRC resources between it and the network device and then enter the RRC_IDLE state.

[0147] When the terminal device needs to transmit data to the network device in the RRC_INACTIVE state, the terminal device can send an RRC resume request message to the network device, and the network device can send an RRC recovery response message to the terminal device. After the terminal device receives the RRC recovery response message, it can send an RRC recovery completion message to the network device, and the terminal device enters the RRC_CONNECTED state.

[0148] The following introduces three parameters: buffer status reporting (BSR), power headroom report (PHR), and release assistance indication (RAI).

[0149] Introduction to BSR

[0150] In some possible scenarios, when the terminal device is in the RRC_CONNECTED state, the network device may configure the terminal device with relevant parameters for reporting the BSR by the terminal device. For example, the network device may configure at least one parameter of periodicBSR-Timer, retxBSR-Timer, logicalChannelSR-DelayTimerApplied, logicalChannelGroup, logicalChannelSR-Mask or logicalChannelSR-DelayTimer. For the definitions of these parameters, please refer to the description of protocol 38321. When the terminal device is in the RRC_CONNECTED state, if the terminal device has uplink data to send to the network device, the terminal device may send a BSR to the network device according to these parameters configured by the network device. The BSR indicates the amount of data to be transmitted in the buffer of the terminal device. The network device may allocate resources to the terminal device through downlink control information (DCI) according to the amount of data indicated by the BSR.

[0151] In some embodiments, the terminal device sends a medium access control (MAC) control element (CE) to the network device. The MAC CE is used to carry the BSR, also known as a BSR MAC CE.

[0152] The terminal device can report the BSR MAC CE when any of the following conditions are met, for example:

[0153] 1) When uplink (UL) data for the logical channels included in an LCG arrives at the MAC layer, and before the UL data arrives, the terminal device's uplink data buffer contains no data, that is, before the UL data arrives, the terminal device's uplink data buffer is empty. The terminal device triggers a BSR report. Triggering a BSR report by the terminal device refers to the terminal device reporting a BSR MAC CE. If the terminal device only needs to report the BSR corresponding to one LCG at this time, the terminal device reports a short BSR MAC CE. If the terminal device needs to report the BSR corresponding to multiple LCGs at this time, the terminal device reports a long BSR MAC CE.

[0154] 2) When the UL data of the logical channel included in a certain LCG reaches the MAC layer, and the priority of the logical channel corresponding to the UL data is higher than the priority of any logical channel included in any other LCG, that is, high-priority UL data is currently arriving, the terminal device triggers BSR reporting. The terminal device triggering BSR reporting refers to the terminal device reporting BSR MAC CE. If the terminal device only needs to report the BSR corresponding to one LCG at this time, the terminal device reports a short BSR MAC CE; if the terminal device needs to report the BSRs corresponding to multiple LCGs at this time, the terminal device reports a long BSR MAC CE.

[0155] 3) If the retxBSR-Timer times out and at least one logical channel in an LCG has UL data to transmit, the terminal device triggers a BSR report. Triggering a BSR report by the terminal device means reporting a BSR MAC CE. If the terminal device only needs to report the BSR corresponding to one LCG at this time, the terminal device reports a short BSR MAC CE; if the terminal device needs to report the BSRs corresponding to multiple LCGs at this time, the terminal device reports a long BSR MAC CE.

[0156] Among them, when condition 1) or condition 2) or condition 3) is met, triggering the terminal device to report the BSR MAC CE can be called a regular BSR.

[0157] 4) If the network device allocates uplink transmission resources to the terminal device, but the amount of data the terminal device needs to transmit is less than the size of the uplink transmission resources, the remaining resources are used to transmit padding bits. If the size of the padding bits is larger than the size of the BSR MAC CE and its corresponding subheader, the terminal device triggers a BSR report. The terminal device triggering a BSR report means that the terminal device uses the resources corresponding to the padding bits to report the BSR MAC CE.

[0158] When the padding bit is greater than or equal to the short BSR MAC CE but less than the long BSR MAC CE: if the terminal device needs to report the BSRs corresponding to multiple LCGs, and if the padding bit size is equal to the sum of the short BSR MAC CE and the subheader size of the short BSR MAC CE, the terminal device reports a short truncated BSR MAC CE, and the short truncated BSR MAC CE indicates the BSR corresponding to the LCG with the highest logical channel priority among the multiple LCGs; if the padding bit size is greater than the sum of the short BSR MAC CE and the subheader size of the short BSR MAC CE, the terminal device reports a long truncated BSR MAC CE;

[0159] When the padding bit is greater than or equal to the short BSR MAC CE but less than the long BSR MAC CE: If the terminal device only needs to report the BSR corresponding to one LCG, the terminal device reports the short BSR MAC CE;

[0160] When the padding bit is greater than or equal to the long BSR MAC CE: the terminal device reports a long BSR MAC CE, which can indicate the BSRs corresponding to all LCGs with data to be transmitted;

[0161] Among them, when condition 4) is met, the BSR MAC CE reported by the terminal device is called a padding BSR.

[0162] 5) If the periodicBSR-Timer expires, the terminal device triggers a BSR report. Triggering a BSR report by the terminal device refers to reporting a BSR MAC CE. If the terminal device only needs to report the BSR corresponding to one LCG, the terminal device reports a short BSR MAC CE. If the terminal device needs to report the BSR corresponding to multiple LCGs, the terminal device reports a long BSR MAC CE.

[0163] Among them, when condition 5) is met, the BSR MAC CE reported by the terminal device is called a periodic BSR.

[0164] The BSR MAC CE reported by the terminal device can be divided into short BSR MAC CE, long BSR MAC CE, short truncated BSR MAC CE and long truncated BSR MAC CE. The sizes of short BSR MAC CE and short truncated BSR MAC CE are fixed, while the sizes of long BSRMAC CE and long truncated BSR MAC CE are variable and not fixed. Each BSR MAC CE corresponds to a MAC subheader, and the MAC subheader corresponding to each BSR MAC CE includes a unique logical channel identity (LCID) for identifying the BSR MAC CE. For example, if Figure 4 The LCID value in is 59 as shown in Table 1, indicating a short truncation of the BSR MAC CE. Figure 4 The LCID value in is 61 in Table 1, indicating a short BSR MAC CE. For example, the MAC subheader corresponding to the short BSR MAC CE and the short truncated BSR MAC CE is as follows: Figure 4 As shown, the MAC subheader occupies one byte, wherein Table 1 can be Table 6.2.1-2 in protocol 38321, Figure 4 It can be in protocol 38321 Figure 6 .1.2-3. The formats of short BSRMAC CE and short truncated BSR MAC CE are as follows Figure 5 As shown, Figure 5 It can be protocol 38321 Figure 6 .1.3.1-1. The MAC subheader corresponding to the long BSRMAC CE and the long truncated BSR MAC CE is as follows Figure 6 As shown, the MAC subheader occupies two bytes. The formats of the long BSR MAC CE and the long truncated BSR MAC CE are as follows: Figure 7 As shown, Figure 6 The LCID in is 60 as shown in Table 1, indicating that the BSRMAC CE is a long truncated BSR MAC CE. Figure 6 The LCID in is 62 in Table 1, indicating that the BSR MAC CE is a long BSR MAC CE. Figure 6 This can be Figure 6.1.2-1 in Protocol 38321. Figure 7 It can be in protocol 38321 Figure 6 .1.3.1-2. Among them, Figure 4-Figure 7The R in the MAC subheader indicates a reserved bit; the LCID is used in the MAC subheader to indicate which MAC CE it is, that is, to indicate the physical meaning of the MAC CE; the LCG ID indicates the reported logical channel group identifier; the F is used for MAC CEs of variable size and indicates the length of the L field. If F = 0, L is 8 bits; if F = 1, L = 16 bits. For example, in some cases, if Figure 6 The MAC subheader shown occupies three bytes, so L = 16 bits. i (i=0~7) is used to indicate the LCG ID of the buffer size field corresponding to the reported LCG, i=0~7. For short truncated BSR MAC CE and short BSR MAC CE, the buffer size field indicates the amount of data of the LCG identified by the LCG ID. For long truncated BSR MAC CE and long BSR MAC CE, the buffer size field indicates the amount of data of the LCG identified by the LCG ID. i The data volume of the LCG whose value is 1, for example, LCG0 to LCG7 are 01010110 respectively, then the buffer size 1 can be the data volume of LCG1, the buffer size 2 can be the data volume of LCG3, the buffer size 3 can be the data volume of LCG5, and the buffer size 4 can be the data volume of LCG6. Figure 7 m=4, that is, the terminal device reports the data volume corresponding to 4 logical channel groups out of 8 logical channel groups. A logical channel group may include multiple logical channels.

[0165] Table 1

[0166]

[0167]

[0168] Introduction to RAI

[0169] The terminal device can send RAI information to the network device. The RAI information is used to notify the network device of the subsequent UL data volume or downlink (DL) data volume of the terminal device, for example, the uplink and / or downlink transmission expected by the terminal device, which can be a small packet transmission. When the upper layer of the terminal device (for example, the upper layer includes the RRC layer and / or NAS layer) triggers the RAI information reporting, the terminal device reports the RAI information to the network device through the access stratum (AS). For example, when business data arrives at the upper layer, the upper layer of the terminal device can trigger the RAI information reporting.

[0170] When the terminal device reports RAI information at the AS layer, it can report RAI information during the random access process. That is, the terminal device reports RAI information to the network device through the random access process in the RRC non-connected state (RRC_INACTIVE state or RRC_IDLE state). For example, the terminal device can report RAI information through the downlink channel quality report (DCQR) and AS RAI MAC CE in message 3 of the random access process. DCQR and AS RAI MAC CE are as follows: Figure 8 As shown, Figure 8 It can be in protocol 36321 Figure 6 .1.3.19-1. Figure 8 In the, R is a reserved field, the quality report (quality report) is used to indicate the downlink channel quality, the AS RAI value is different, the physical meaning of DCQR and AS RAI MAC CE is different, wherein the triggering condition of DCQR may be that the network device sends an indication message to the terminal device, instructing the terminal device to report DCQR, for example, the network device sends a MAC CE to the terminal device, and the MAC CE instructs the terminal device to report DCQR, or, the triggering condition of DCQR may be that the network device notifies the terminal device to report DCQR in a broadcast message, the format of DCQR and AS RAI MAC CE may be fixed or not fixed, if the network device does not indicate or notify the terminal device to report DCQR, the field corresponding to DCQR does not exist or exists but is a reserved field. In 3GPP LTE protocol 36321, the values ​​of AS RAI are shown in Table 2. Among them, the MAC subheader of DCQR and AS RAI MAC CE is the same as that of BSR. Figure 4 or Figure 6 The LCID value in the MAC subheader of the DCQR and AS RAI MAC CE can be a specific value to identify the DCQR and AS RAI MAC CE. For example, the LCID value in the MAC subheader of the DCQR and AS RAI MAC CE can be a value in Table 6.2.1-2 of protocol 36321.

[0171] Table 2

[0172]

[0173]

[0174] Introduction to PHR

[0175] In some possible scenarios, when the terminal device is in the RRC_CONNECTED state, the network device can configure the terminal device with relevant parameters for reporting PHR by the terminal device. For example, the network device can configure at least one parameter of phr-PeriodicTimer, phr-ProhibitTimer, phr-Tx-PowerFactorChange, phr-Type2OtherCell, phr-ModeOtherCG, multiplePHR, mpe-Reporting-FR2, mpe-ProhibitTimer or mpe-Threshold. The definitions of these parameters are described in protocol 38331. Optionally, the network device can configure the relevant parameters of PHR through RRC messages. When the terminal device is in the RRC_CONNECTED state, it can report PHR to the network device. PHR indicates the difference between the maximum transmission power supported by the terminal device and the current estimated transmission power of the terminal device. The difference can be called power margin. The network device can schedule resources for the terminal device based on the PHR. Optionally, if the terminal device is in the RRC_INACTIVE state, the terminal device uses a default MAC configuration, the default MAC configuration includes a default PHR configuration, and the default PHR configuration includes at least one parameter of phr-PeriodicTimer, phr-ProhibitTimer or phr-Tx-PowerFactorChange.

[0176] In some embodiments, the terminal device sends a MAC CE to the network device, where the MAC CE is used to carry the PHR, also referred to as a PHR MAC CE.

[0177] The terminal device may report a PHR MAC CE when any of the following conditions are met, for example:

[0178] 1) If the terminal device has uplink resources for transmitting new data, the uplink resources for the terminal device to transmit new data can be understood as the network device configuring uplink resources for the terminal device to transmit new data, and the prohibitPHR-Timer times out or has timed out and the path loss transformation value is greater than phr-Tx-PowerFactorChange dB since the last transmit power margin report. The path loss transformation value can be the transformation value between the measured path loss of the current path loss reference and the measured path loss of the path loss reference when the PHR was last reported.

[0179] 2) When the phr-PeriodicTimer times out, the terminal device can report the PHR MAC CE.

[0180] 3) The terminal device receives configuration or reconfiguration of the PHR function from a higher layer, and the configuration or reconfiguration of the PHR function is not for disabling the PHR function.

[0181] 4) Activate a secondary cell (SCell). This SCell is any SCell with a configured uplink of a MAC entity, and the firstActiveDownlinkBWP-Id of this SCell is not set to the dormant bandwidth part (BWP). That is, the downlink BWP of this SCell is not a dormant BWP. The configured uplink can mean that the SCell has an uplink, or that the SCell has pre-configured uplink resources. The SCell of the MAC entity can be a SCell that the MAC entity can use, a SCell in which the MAC entity is working, or a SCell used by the MAC entity when sending or receiving data.

[0182] 5) Adding a primary secondary cell (PSCell), for example, the PScell ​​is a primary secondary cell newly added or modified by the network device for the terminal device.

[0183] 6) When the terminal device has uplink resources for transmitting new data, the uplink resources for the terminal device to transmit new data can be understood as the network device configuring uplink resources for the terminal device to transmit new data, the prohibitPHR-Timer times out or has timed out, and for any activated serving cell with a configured uplink for any MAC entity, the following are true:

[0184] There are uplink resources allocated by the network device for transmission of the terminal device or there is PUCCH transmission in the current cell, and the power backoff required by the terminal device for the cell due to power management has changed by more than ph-Tx-PowerFactorChange dB since the last PHR transmission, where the last PHR transmission may be when there are uplink resources allocated by the network device for transmission of the terminal device or there is PUCCH transmission in the current cell, and the terminal device transmits a PHR; the parameter related to power management is power management maximum power reduction (P-MPR), which can be used to ensure compliance with applicable electromagnetic energy absorption requirements and to address unnecessary emission / self-density requirements when transmitting simultaneously on multiple radio access technologies in scenarios that are not within the scope of the third generation partnership project (3GPP) radio access network (RAN) specifications; it can also be used to ensure compliance with applicable electromagnetic energy absorption requirements in close detection situations, and to meet requirements requiring lower maximum output power.

[0185] 7) When the activated BWP of the SCell with uplink of any MAC entity of the terminal device switches from the dormant BWP to the non-dormant DL BWP, or the activated BWP switches from the dormant BWP to the non-dormant BWP, and the non-dormant BWP is the BWP with the configured uplink SCell available to any MAC entity, the terminal device reports the PHR MAC CE.

[0186] 8) If mpe-Reporting-FR2 is configured and mpe-ProhibitTimer is not running, the measured P-MPR is equal to or greater than mpe-threshold since the last PHR was transmitted, where mpe-threshold can be the threshold value of at least one serving cell operating in FR2; or if mpe-Reporting-FR2 is configured and mpe-ProhibitTimer is not running, the measured P-MPR has changed by more than phr-Tx-PowerFactorChange dB since the last PHR was transmitted due to the measured P-MPR being equal to or greater than mpe-threshold.

[0187] The MAC subheader corresponding to the PHR MAC CE is similar to the BSR. Figure 4 or Figure 6The MAC subheaderLCID value of the PHR MAC CE can be a specific value to identify the PHR MAC CE. In NR protocol 38321, optionally, the format of the PHR MAC CE reported by the terminal device can be as follows: Figure 9A As shown, Figure 9A The single entry PHR MAC CE in Table 1 is shown when the LCID value is 57. Figure 9A It can be in protocol 38321 Figure 6 .1.3.8-1. The format of the PHR MAC CE reported by the terminal device can also be the multiple entry PHR MAC CE when the LCID value in Table 1 is 54 and / or 56. The format of the PHR MAC CE reported by the terminal device is controlled by the network device. For example, when the network device sets multiplePHR to true, the terminal device reports the multiple entry PHR MAC CE, and the terminal device can indicate PHRs related to multiple SCells.

[0188] Figure 9A The meaning of the P field value is as follows: If the network device is configured with the mpe-reporting-FR2 parameter and the current cell of the terminal device operates in the FR2 frequency band, then in order to meet the MPE requirements, when the P value is 0, it means that the P-MPR value is less than the P-MPR_00 defined in 38.133; when the P value is 1, it means that the P-MPR value is greater than or equal to the P-MPR_00 defined in 38.133. Among them, P-MPR can be understood as the power fallback of the maximum output of power management, which is the maximum available output transmission power reported by the terminal device. The network device can refer to the P-MPR for resource scheduling. P-MPR_00 is a predefined P-MPR range, which is a P-MPR greater than or equal to 3dB and less than 6dB. Therefore, the terminal device can report the current P-MPR value range to the network device through the P value. For example, when the P value is 0, it means that the current P-MPR of the terminal device is less than 3dB. When the P value is 1, it means that the current P-MPR of the terminal device is greater than 6dB. For FR2, power fallback can be understood as P-MPR-related information. The terminal device reports this information to ensure that it complies with the maximum permissible exposure (MPE) required by frequency range 2 (FR). The MPE is used to limit the amount of radio frequency radiation to the human body.

[0189] If the network device is not configured with mpe-reporting-FR2 or the terminal device's current cell operates in the FR1 frequency band, the P field indicates whether power fallback due to power management is applied. If power fallback due to power management is not applied and P CMAX,f,c If the field has different values, the value of P is 1. Otherwise, the value of P is 0. It is understandable that if power fallback caused by power management is not applied, the terminal device will adjust P CMAX,f,c , and set the P field to 1; if power backoff caused by power management is applied, P CMAX,f,c Unchanged, and the P field is set to 0.

[0190] Figure 9A The PH field in the PH field indicates the level of the power headroom. For example, if the field is 6 bits long, the terminal device can indicate 64 power headroom levels through this field, where each power headroom level corresponds to a power headroom measurement value range. Therefore, the terminal device can indicate the power headroom measurement value range through the PH field.

[0191] Figure 9A The meaning of the MPE field in is as follows: This field is 2 bits long. If the network device is configured with the mpe-reporting-FR2 parameter, and the cell where the terminal device is currently located operates in the FR2 frequency band, and the P field is set to 1, the MPE field indicates the power fallback applied to meet the MPE requirement. At this time, the 2 bits of this field can indicate 4 measured P-MPR values, for example, P-MPR_00, P-MPR_01, P-MPR_02, and P-MPR_03. As mentioned above, each value corresponds to a P-MPR range. If the network device is not configured with mpe-reporting-FR2 or the cell where the terminal device is currently located operates in the FR1 frequency band or if the P field is set to 0, the MPE field is meaningless, that is, the MPE field should be understood as a reserved bit R.

[0192] Figure 9A P in CMAX,f,c Field identifier calculates the P corresponding to the PH field CMAX,f,c .

[0193] Optionally, the format of the PHR MAC CE reported by the terminal device can be as follows: Figure 9B As shown, Figure 9B It can be in protocol 36321 Figure 6 .1.3.6-1. Figure 9B The PH field indicates the power margin, and the R field is a reserved bit.

[0194] The above introduces BSR, RAI and PHR. If the terminal device needs to report these three parameters, it needs to report them through three different MAC CEs respectively. The three MAC CEs need to correspond to three different MAC subheaders, which will result in a relatively large signaling overhead.

[0195] In some scenarios, a terminal device in an RRC non-connected state (including an RRC_INACTIVE state or an RRC IDLE state) has a need to transmit data, and the data packets that need to be transmitted are very small. Such data packets can be called small data (smalldata), or small packet data. Small data can include instant messages from the terminal device's application (APP), the APP's heartbeat packet, or the APP's push message; for example, small data can include: periodic data from wearable devices, business data from IoT devices, etc. If in order to transmit small data, the terminal device needs to enter the RRC_CONNECTED state from the RRC non-connected state, and the signaling required for the terminal device to enter the RRC CONNECTED state from the RRC non-connected state is even greater than smalldata, resulting in unnecessary power consumption and signaling overhead for the terminal device. Therefore, it is necessary to transmit small packet data to the network device in the RRC non-connected state.

[0196] In an embodiment of the present application, the network device and the terminal device can determine whether the data is small data based on the data size, wherein data smaller than a preset value can be called small data. For example, the preset value can be 500 bytes, 300 bytes, etc. Alternatively, the network device and the terminal device can also determine whether the data is small data based on the data tag or data type. Specifically, the network device and the terminal device can negotiate the data tag or data type based on the size of the data. For example, the data tag can include big data or small data; for another example, data with a data type of heartbeat packet, instant message, or periodic data is small data, and data with a data type of file, video, or audio is big data.

[0197] To address the issue of excessive overhead associated with transmitting very small amounts of data when the terminal device is in the RRC non-connected state, the terminal device can transmit small data without entering the RRC_CONNECTED state. The terminal device can utilize the principle of random access (RA) for small data transmission (SDT), also known as RA-SDT. Alternatively, the terminal device can utilize pre-configured grants (CG) for SDT, also known as CG-SDT. RA-SDT and CG-SDT are described below.

[0198] RA-SDT

[0199] In a wireless communication system, before a terminal device communicates with a network device, it must first initiate a random access process to obtain uplink synchronization with the network device, or the terminal device initiates random access in response to a paging message from the network device. Random access is divided into four-step random access (4-step RA) and two-step random access (2-step RA). Optionally, when the terminal device is not configured with contention free random access, the terminal device may initiate 4step-RA or 2step-RA based on the relative size of the currently measured reference signal receiving power (RSRP) and the preset RSRP threshold. For example, when the currently measured RSRP is greater than or equal to the preset RSRP threshold, the terminal device may initiate 2step-RA. When the currently measured RSRP is less than the preset RSRP threshold, the terminal device may initiate 4step-RA. Therefore, the principle of four-step random access can be used for SDT or the principle of two-step random access can be used for SDT. As Figure 10 As shown, SDT is performed using the principle of four-step random access.

[0200] S1010, a network device sends a broadcast message to a terminal device, where the broadcast message includes first resource configuration information, where the first resource configuration information is used to indicate a random access resource.

[0201] The random access resource may also be called RA occasion.

[0202] Optionally, the first resource configuration information may further specifically indicate which random access resources are used to initiate normal random access, and which random access resources are used to send message 1 during the RA-SDT process.

[0203] S1020, the terminal device sends a preamble (preamble), also known as message 1, according to the random access resource indicated by the first resource configuration information, and the network device receives the preamble sent by the terminal device.

[0204] The preamble code may be generated by the terminal device according to specific rules, but the network device can recognize the preamble code generated by the terminal device.

[0205] In some embodiments, if the terminal device is to perform SDT, the preamble in S1020 may be different from the preamble when the terminal device is to initiate normal random access without performing SDT. In other words, the network device may use different preambles to distinguish the intention of the terminal device, such as whether the terminal device intends to perform SDT or to initiate normal random access.

[0206] In some embodiments, if the first resource configuration information further specifically indicates which random access resources are used to initiate normal random access and which random access resources are used to send message 1 during the SDT process, the terminal device may send message 1 in S1020 on different random access resources based on different intentions. In this way, the network device may use different resources for receiving preamble codes to distinguish the intention of the terminal device, such as whether the terminal device intends to perform SDT or to initiate normal random access.

[0207] In other embodiments, the preamble code in S1020 may also be the same as the preamble code used by the terminal device to initiate normal random access without performing SDT.

[0208] In other embodiments, the random access resource for sending the preamble code in S1020 may also be the same as the random access resource for the terminal device to initiate normal random access without performing SDT.

[0209] S1030, in response to S1020, the network device sends a random access response (RAR) message, also called message 2, to the terminal device.

[0210] The RAR message may include the second resource configuration information. Optionally, the RAR message may also include at least one of a temporary cell radio network temporary identifier (T-CRNTI) and a timing advance (TA). The second resource configuration information is used to indicate the resources used by the terminal device to send message 3. The TA is used by the terminal device to obtain uplink synchronization.

[0211] S1040, the terminal device sends an RRC request message and small data to the network device on the resources indicated by the second resource configuration information, also known as message 3.

[0212] When the terminal device is in different RRC states and in different business scenarios, the RRC request message may be different. For example, the message 3 sent by the terminal device in the RRC IDLE state (optionally, the terminal device may store the terminal device context such as the configuration information for obtaining the key for encrypting uplink small data, or the terminal may not store its context) may include an RRC connection request (RRCConnectionRequest) message, an RRC connection resumption request (RRCConnectionResumeRequest) message, an RRC data early transmission (RRCEarlyDataRequest) message, an RRC resumption (RRCResumeRequest) message, an RRC establishment request (RRCSetupRequest) message or other RRC messages with the same function but not standardized by the third generation partnership project (3GPP). The message 3 sent by the terminal device in the RRC INACTIVE state may also include an RRCConnectionRequest message, an RRCConnectionResumeRequest message, an RRCCEarlyDataRequest message, an RRCResumeRequest message, an RRCSetupRequest message or other RRC messages with the same function but not standardized by 3GPP.

[0213] When the terminal device uses Figure 2B When the control plane protocol stack shown in FIG3 performs RA-SDT, small data can be carried in message 3, carried by signaling radio bearers (SRB) and transmitted on CCCH. For example, small data can be carried in the non-access stratum (NAS) related IE (such as dedicated Info NAS IE) included in the RRCEarlyDataRequest message and transmitted on CCCH. When the terminal device uses Figure 2A When the user plane protocol stack shown performs RA-SDT, the small data included in Message 3 is transmitted via the DTCH using the user plane protocol stack above the MAC layer. The RRC request message included in Message 3 is transmitted via the CCCH using the control plane protocol stack above the MAC layer. The small data and RRC request message can be encapsulated at the MAC layer and sent to the network device via the PHY layer.

[0214] In other embodiments, if the preamble in S1020 is the same as the preamble used by the terminal device to initiate normal random access without performing SDT, or if the random access resource for sending the preamble in S1020 is the same as the random access resource for transmitting the preamble used by the terminal device to initiate normal random access without performing SDT, the RRC request message may carry intent information, where the intent information is used to indicate the terminal device's intention to initiate SDT. That is, in message 3, the RRC request message may carry the terminal device's intention to initiate SDT instead of normal random access.

[0215] S1050: In response to S1040, the network device sends an RRC response message to the terminal device, where the RRC response message includes a next hop chaining count (NCC), where the NCC is used by the terminal device to determine a key for the next SDT.

[0216] For example, the RRC response message may be an RRC release message, wherein different RRC request messages correspond to different RRC response messages.

[0217] In some embodiments, after S1040, if the network device has downlink small data to send to the terminal device, S1050 may include: in response to S1040, the network device sends an RRC response message and downlink small data to the terminal device.

[0218] In some embodiments, when the terminal device utilizes Figure 2B When the control plane protocol stack shown transmits the small data in S1040, the network device may carry the downlink small data in the response message in S1050. The downlink small data may be carried in the RRC response message and transmitted on the CCCH. For example, the RRC response message is an RRC Early Data Complete message, and the downlink small data may be carried in the NAS layer-related IE included in the RRC Early Data Complete message and transmitted on the CCCH.

[0219] In some embodiments, when the terminal device utilizes Figure 2A When the user plane control protocol shown transmits small data S1040, S1050 includes: the network device can send an RRC response message and downlink small data to the terminal device, the downlink small data can be transmitted on the DTCH, and multiplexed with the RRC response message transmitted on the DCCH at the MAC layer.

[0220] In some embodiments, the network device identifies that the terminal device is for SDT transmission based on the preamble sent by the terminal device or the resource of the received preamble or the intention information carried in the RRC request message. Therefore, after the network device receives the RRC request message and small data of S1040, the network device determines that the terminal device has performed SDT in S1040. Then, in S1050, the RRC response message sent by the network device may also include the NCC used to calculate the next SDT key of the terminal device.

[0221] In some embodiments, if after S1040, the terminal device or network device has no need to further transmit data, the RRC response message in S1050 can also be used to indicate that the uplink packet data transmission of the terminal device is successful, and instruct the terminal device to remain in the current RRC non-connected state. For example, the RRC response message is an RRC EarlyDataComplete message, an RRC Connection Release (RRCConnectionRelease) message, an RRC Release (RRC Release) message, or other RRC messages with the same function but not standardized by 3GPP. The terminal device can obtain the success of the uplink packet data transmission based on the RRC response message.

[0222] In some embodiments, if the terminal device does not receive the RRC response message in S1050, it is considered that the small data transmission in S1040 is unsuccessful. If the terminal device receives the RRC response message in S1050, it is considered that the small data transmission in S1040 is successful. In other words, the terminal device can use whether the RRC response message is received to determine whether the small data transmission in S1040 is successful.

[0223] In some embodiments, if after S1040, the terminal device or the network device has a need to further transmit data, and the network device determines that it can trigger entry into the RRC_CONNECTED state, the RRC response message in S1050 can be used to instruct the terminal device to enter the RRC CONNECTED state. For example, the RRC response message is an RRC connection establishment (RRCConnectionSetup) message, an RRC connection recovery (RRCConnectionResume) message, an RRC establishment (RRCSetup) message, an RRC recovery (RRCResume) message, or other RRC messages with the same function but not standardized by 3GPP. The terminal device can obtain the success of the small data transmission in the above-mentioned S1040 based on the RRC response message. That is, the terminal device can infer that the network device has successfully received the small data in S1040 based on the terminal device entering the RRC CONNECTED state indicated by the RRC response message.

[0224] In some embodiments, the RRC response message is used to indicate that the uplink small packet data transmission of the terminal device has failed, and to instruct the terminal device to remain in the current non-connected state. For example, the RRC response message is an RRC Connection Reject (RRCConnectionReject) message, an RRC Reject (RRCReject) message, or other RRC messages with the same function but not standardized by 3GPP. The terminal device can obtain the uplink small packet data transmission failure based on the RRC response message and maintain the current non-connected state based on the RRC response message.

[0225] like Figure 11 As shown, it is shown that SDT is performed using the principle of two-step random access.

[0226] S1110, the network device sends a broadcast message to the terminal device, where the broadcast message includes first resource configuration information, and the first resource configuration information is used to indicate a random access resource.

[0227] The random access resource may also be called RA occasion.

[0228] For the random access resource indicated by the first resource configuration information, refer to the description of S1010.

[0229] S1120, the terminal device sends a preamble, an RRC request message and small data to the network device according to the random access resources indicated by the resource configuration information, which is called message A.

[0230] The preamble may be generated by the terminal device according to a specific rule, but the network device can recognize the preamble generated by the terminal device. For a description of the preamble and the random access resource for sending the preamble, refer to the description of S1020.

[0231] The RRC request message may be different when the terminal device is in different RRC states and in different service scenarios. Figure 10 The description of the RRC request message in S1040 will not be repeated here.

[0232] When the terminal device uses Figure 2B When the control plane protocol stack performs RA-SDT, the terminal device sends a preamble, an RRC request message, and small data. The small data can be carried in message A, carried by the SRB, and transmitted on the CCCH. For example, the small data can be carried in the non-access stratum (NAS) related IE (such as the dedicated information NAS (dedicatedInfoNAS) IE) included in the RRC EarlyDataRequest message and transmitted on the CCCH.

[0233] When the terminal device uses Figure 2A When the user plane protocol stack performs RA-SDT, the terminal device sends a preamble, an RRC request message, and small data. The small data and preamble are transmitted via the DTCH using the user plane protocol stack above the MAC layer, while the RRC request message is transmitted via the CCCH using the control plane protocol stack above the MAC layer. The small data, RRC request message, and preamble can be encapsulated at the MAC layer and sent to the network device via the PHY layer.

[0234] In other embodiments, if the preamble in S1120 is the same as the preamble used by the terminal device to initiate normal random access without performing SDT, or if the random access resource used to send the preamble in S1120 is the same as the random access resource used to transmit the preamble used by the terminal device to initiate normal random access without performing SDT, the RRC request message in S1120 may carry intent information, where the intent information is used to indicate the terminal device's intention to initiate SDT. That is, in message A, the RRC request message may carry the terminal device's intention to initiate SDT instead of normal random access.

[0235] S1130: The network device sends an RRC response message to the terminal device. The RRC response message carries the next hop chaining count (NCC) used to encrypt the small data. The RRC response message is also called message B. This step is similar to S1050 and will not be repeated here.

[0236] For example, the RRC response message may be an RRC release message. For example, the RRC response message may correspond to the RRC request message in S1120. Different RRC request messages correspond to different RRC response messages.

[0237] It should be noted that after the terminal device receives the RRC response message of S1130, the terminal device may still be in the RRC non-connected state, or may enter the RRC connected state.

[0238] In some embodiments, before S1130, if the network device has downlink small data to send to the terminal device, the network device can send the downlink small data to the terminal device. Figure 10 Description of S1050.

[0239] The above introduces RA-SDT, and the following combines Figure 12 Introducing CG-SDT.

[0240] S1210: The terminal device sends a CG-SDT resource request message to the network device in the RRC_CONNECTED state. The CG-SDT resource request message is used to request the network device to configure CG-SDT.

[0241] Optionally, the terminal device can send a CG-SDT resource request message to the network device at any time in the RRC_CONNECTED state. Or the terminal device can determine that there may be small data in the future in the RRC_CONNECTED state, and then send a CG-SDT resource request message to the network device. Or the terminal device is in the RRC_CONNECTED state, and the terminal device has no need to transmit data with the network device within a preset time period. The terminal device determines that it may be about to enter a non-connected state. In order to transmit small data in the non-connected state, the terminal device can send a CG-SDT resource request message to the network device.

[0242] S1220: The network device sends a response message to the terminal device in response to the CG-SDT resource request message, wherein the response message carries the CG-SDT configuration.

[0243] Among them, the CG-SDT configuration is used to indicate the time-frequency position and resource period of the terminal device for transmitting small data. That is to say, the network device can pre-configure resources for CG-SDT for the terminal device when the terminal device is in the RRC_CONNECTED state. When the terminal device enters the RRC non-connected state, the terminal device can use the resources pre-configured by the network device in the RRC_CONNECTED state to perform CG-SDT. This can save transmission delay, eliminate the need for dynamic scheduling of resources, and reduce signaling overhead. For the convenience of description below, the resources indicated by the CG-SDT configuration are referred to as CG resources.

[0244] Optionally, the CG-SDT configuration may also instruct the terminal device to perform SDT on a data radio bearer (DRB), or may also instruct the terminal device to perform SDT on a DRB and a DRB that cannot perform SDT. SDT transmission can only be performed on the DRB indicated by the CG-SDT configuration, and the terminal device cannot perform SDT transmission on a DRB not indicated by the CG-SDT configuration. For example, Figure 13As shown, the CG-SDT configuration indicates that the terminal device can perform SDT on DRB 1 and DRB 2, the CG-SDT configuration does not indicate DRB 3, or the CG-SDT indicates that SDT cannot be performed on DRB 3. Therefore, the terminal device can only use the CG-SDT configuration to perform SDT on DRB 1 and DRB 2, and cannot use the CG-SDT configuration to perform SDT on DRB 3. For another example, CG-SDT configuration 1 indicates that the terminal device can perform SDT on DRB 1, CG-SDT configuration 2 indicates that the terminal device can perform SDT on DRB 2, and CG-SDT configuration 3 indicates that the terminal device cannot perform SDT on DRB 3. Then the terminal device can use CG-SDT configuration 1 to perform SDT on DRB 1, but cannot use CG-SDT configuration 2 to perform SDT on DRB 1, the terminal device can use CG-SDT configuration 2 to perform SDT on DRB 2, but cannot use CG-SDT configuration 1 to perform SDT on DRB 2, and the terminal device does not perform SDT on DRB 3.

[0245] like Figure 13 As shown, one DRB corresponds to one PDCP entity, one RLC entity and one logical channel (LCH), wherein the LCH is between the RLC layer and the MAC layer. One logical channel corresponds to one DRB.

[0246] Optionally, if the terminal device sends a CG-SDT resource request message to the network device at any time in the RRC_CONNECTED state; or the terminal device determines that there will be small data in the future and sends a CG-SDT resource request message to the network device, then the response message of the CG-SDT resource request message sent by the network device to the terminal device can be an RRC reconfiguration message, and the RRC reconfiguration message carries the CG-SDT configuration.

[0247] Optionally, if the network device determines that the terminal device needs to enter the RRC_INACTIVE state, the response message in S1220 may be an RRC release message carrying a suspend indication (RRC release with suspend indication), and the RRC release message carrying a suspend indication includes a CG-SDT configuration. After receiving the RRC release message carrying a suspend indication, the terminal device enters the RRC_INACTIVE state.

[0248] Optionally, if the network device determines that the terminal device needs to enter the RRC_IDLE state, the response message in S1220 may be an RRC release message that does not carry a pause indication, and the RRC release message includes a CG-SDT configuration. After receiving the RRC release message, the terminal device enters the RRC_IDLE state. Exemplarily, the CG-SDT resource request message in S1210 may be a preconfigured uplink resource configuration request (preconfigured uplink resource Configuration Request, PURConfigurationRequest) message, and the response message in S1220 may be an RRCConnectionRelease message. At this time, the CG-SDT configuration in the RRCConnectionRelease message may be PUR configuration information or PUR release indication information.

[0249] In some embodiments, the terminal device may not send a CG-SDT resource request message to the network device. The network device may directly configure CG-SDT resources for the terminal device. For example, the network device may refer to the terminal device's historical communication service conditions to configure CG-SDT resources for the terminal device. In this case, S1210 does not exist, and the network device may directly send the CG-SDT configuration in S1220 to the UE.

[0250] After S1220, the terminal device enters the RRC non-connected state, and when the terminal device has small data to transmit, S1230 is executed.

[0251] S1230, the terminal device sends small data to the network device on the resources indicated by the CG-SDT configuration.

[0252] Optionally, the resources indicated by the above-mentioned CG-SDT configuration are pre-configured by the network device for the terminal device. When small data arrives at the terminal device and is within the valid TA, that is, the TAT is running, the terminal device can use the resources indicated by the CG-SDT configuration to perform SDT. Optionally, the terminal device can only send small data during the CG-SDT process, or send both small data and RRC request messages. For example, if the resources indicated by the CG-SDT configuration are unique resources configured by the network device for the terminal device, and are non-shared resources, then during the CG-SDT process, the terminal device can only send small data on the resources indicated by the CG-SDT configuration. In this way, the network device can identify the terminal device that sends small data based on the resources that receive small data. For another example, if the resources indicated by the CG-SDT configuration are shared resources configured by the network device for multiple terminal devices, then during the SDT process, the terminal device can send small data and RRC request messages on the resources indicated by the CG-SDT configuration, so that the network device can use RRC messages to identify the terminal device.

[0253] The RRC request message may be different when the terminal device is in different RRC states. Figure 10 The description of the RRC request message in S1040 is not repeated here.

[0254] When the terminal device uses Figure 2B When the control plane protocol stack performs CG-SDT as shown, small data can be carried in the RRC request message, carried by the SRB and transmitted on the CCCH. For example, small data can be carried in the non-access stratum (NAS) related IE (such as the dedicated information NAS (dedicatedInfoNAS) IE) included in the RRC EarlyDataRequest message and transmitted on the CCCH.

[0255] When the terminal device uses Figure 2A When the user plane protocol stack shown in the figure performs CG-SDT, small data is transmitted via the DTCH using the user plane protocol stack above the MAC layer, and the RRC request message is transmitted via the CCCH using the control plane protocol stack above the MAC layer. The small data and RRC request message can be encapsulated at the MAC layer and sent to the network device via the PHY layer.

[0256] S1240: The network device sends a response message to the terminal device.

[0257] Among them, the response message in S1240 can be an RRC response message. After receiving the response message, the terminal device can determine that the network device has received the small data in S1230, and the terminal device maintains the RRC non-connected state.

[0258] Optionally, if the response message in S1240 is an RRC response message, the RRC response message may also include a CG-SDT configuration, that is, the CG-SDT configuration in S1220 is used for the terminal device to transmit the small data in S1230, and the CG-SDT configuration in S1240 is used for the terminal device to transmit small data next time.

[0259] Optionally, if the response message in S1240 is an RRC response message, the RRC response message is similar to the response message in S1050, and the terminal device can also enter the RRC connection state based on the RRC response message.

[0260] In addition, the response message in S1240 is similar to the description in S1050 and will not be repeated here.

[0261] The above describes CG-SDT and RA-SDT. Terminal devices can use CG-SDT and RA-SDT to transmit small data. CG-SDT and RA-SDT are suitable for different application scenarios.

[0262] For example, since the terminal device performs SDT, the resources indicated by the CG-SDT configuration are configured by the network device of the cell where the terminal device is located. Therefore, the resources indicated by the CG-SDT configuration are applicable to the terminal device in the cell covered by the network device. If the terminal device moves to the coverage of other network devices, the resources indicated by the CG-SDT configuration are no longer applicable. Since the mobility of terminal devices is limited in the field of Internet of Things (IoT), the cell of the terminal device is basically fixed and will not change much, so the terminal devices in the field of IoT can give priority to CG-SDT. For terminal devices with strong mobility, such as smart phones, they may move from the coverage of one network device to the coverage of another network device. If the terminal device is within the coverage of the network device after the movement, the resources indicated by the CG-SDT configuration sent by the network device before the movement are used for SDT, then data cannot be transmitted. Since the resources of RA-SDT message 1 or message A are broadcast in real time by the network device, RA-SDT can be given priority for terminal devices with strong mobility. Of course, whether the terminal device adopts CG-SDT or RA-SDT is not restricted by the scenario, and the SDT method can be determined based on the implementation of the terminal device.

[0263] For example, since the resources for performing CG-SDT are specially configured by the network device for the terminal device, the success rate of the terminal device performing SDT is higher. The random access resources of RA-SDT are broadcast by the network device. Terminal devices that can receive the broadcast message can initiate RA-SDT on the random access resources. Multiple terminal devices will compete for resources, which may lead to competition failure. Therefore, the success rate of RA-SDT is not as high as the success rate of CG-SDT, and CG-SDT may be more effective than RA-SDT. Normally, the terminal device gives priority to CG-SDT. The terminal device also needs to meet certain conditions when selecting CG-SDT. If the conditions are not met, the terminal device can select RA-SDT. For example, whether there are resources indicated by the CG-SDT configuration within the coverage of the normal uplink carrier (NUL) or the supplementary uplink (SUL) carrier where the terminal device is currently located, if there are resources indicated by the CG-SDT configuration, and if there are valid resources among the resources indicated by the CG-SDT configuration, the terminal device can select CG-SDT, otherwise select RA-SDT.

[0264] for Figure 10 In the RA-SDT, the terminal device needs to execute S1020 to S1050 to complete the transmission of small data in the RRC non-connected state. If the terminal device still has small data to transmit to the network device, it needs to execute S1020 to S1050 again, which will result in a large signaling overhead. In other words, a random access process must be initiated every time a small data is transmitted. Figure 11 In the RA-SDT, the terminal device needs to execute S1120 and S1130 to complete the transmission of small data in the RRC non-connected state. If the terminal device still has small data to transmit to the network device, it needs to execute S1120-S1130 again, which will result in a large signaling overhead, that is, a random access process must be initiated each time a small data is transmitted. In particular, if the RRC response message in S1050 or S1130 is an RRCConnectionRelease message or an RRCRelease message, the terminal device will continue to remain in the RRC non-connected state. Figure 12For CG-SDT, the terminal device needs to execute S1230 and S1240 in the RRC non-connected state to complete the transmission of small data. If the terminal device still has small data to transmit to the network device, it needs to execute S1230 and S1240 again, which will result in a relatively large signaling overhead. In other words, each time the terminal device and the network device complete the transmission of small data, the network device will release the transmission resources between the terminal device and the network device. If there is still small data in the future, the terminal device will have to execute RA-SDT or CG-SDT again, which will result in a relatively large signaling overhead.

[0265] That is, if the terminal device has small data to transmit subsequently, it is necessary to report at least one of the BSR, RAI, or PHR to the network device before the network device releases the terminal device, so that the network device can determine the resources used by the terminal device to report subsequent small data based on these parameters reported by the terminal device, and the terminal device can transmit subsequent small data to the network device before the network device releases the terminal device. If, as described above, the terminal device wants to report the BSR, RAI, or PHR, it needs to report them respectively through three different MAC CEs, and the three MAC CEs correspond to three different MAC subheaders, which will result in a relatively large signaling overhead.

[0266] In an embodiment of the present application, a terminal device may indicate at least one of a buffer status report, a power headroom report, or data packet quantity information through a MAC CE, wherein the buffer status report is used to indicate the amount of data in the buffer, the power headroom report is used to indicate the power headroom of the terminal device, and the data packet quantity information is used to indicate the number of data packets to be subsequently transmitted. The network device may configure resources based on the first MAC CE, and the terminal device may obtain resources configured based on the first MAC CE to transmit subsequent small data.

[0267] The following combination Figure 14 The data transmission method 1400 provided in an embodiment of the present application is described. The method 1400 includes:

[0268] S1410, the terminal device indicates at least one of a buffer status report, a power headroom report, or quantity information of data packets to the network device.

[0269] Optionally, the terminal device indicates at least two of the buffer status report, the power headroom report or the number information of the data packets to the network device, for example, indicating the buffer status report and the power headroom report, or indicating the power headroom report and the number information of the data packets, or indicating the buffer status report and the number information of the data packets, or indicating the buffer status report, the power headroom report and the number information of the data packets.

[0270] The buffer status report indicates the amount of data in the terminal device's buffer. The power headroom report indicates the terminal device's power headroom. The packet quantity information indicates the number of packets to be transmitted subsequently.

[0271] Optionally, the quantity information of the data packets is used to indicate the amount of data to be subsequently transmitted. Optionally, the quantity information of the data packets is used to indicate the amount of data to be subsequently transmitted and the number of data packets.

[0272] Optionally, if the number of data packets subsequently transmitted (or subsequently arriving) by the terminal device is greater than or equal to 1, the terminal device may simultaneously indicate the number information of the data packets and the power headroom report to the network device.

[0273] Optionally, if the terminal device determines that there is data to be transmitted in the buffer, for example, the amount of data in the buffer is 1 bit, the terminal device simultaneously indicates a buffer status report and a power headroom report to the network device.

[0274] Optionally, S1410 includes: the terminal device indicates at least one of a buffer status report, a power headroom report, or data packet quantity information to the network device through uplink control information (UCI) of layer 1. Optionally, the network device may implicitly indicate that the content indicated by the UCI is different through different physical uplink control channel (PUCCH) formats. For example, if the format of the UCI sent by the terminal device is a first PUCCH format, the UCI indicates a buffer status report and a power headroom report. For another example, if the format of the UCI sent by the terminal device is a second PUCCH format, the UCI indicates the quantity information of the data packets and the power headroom report.

[0275] Optionally, S1410 includes: the terminal device indicating at least one of a buffer status report, a power headroom report, or a number of data packets to the network device through an RRC message. Optionally, different information elements (IEs) in the RRC message can carry different content, for example, IE1 carries the power headroom report, IE2 carries the buffer status report, etc. The RRC message can be layer 3 signaling.

[0276] Optionally, S1410 includes: the terminal device sends a first MAC CE to the network device, where the first MAC CE is used to indicate at least one of a buffer status report, a power headroom report, or quantity information of data packets.

[0277] Optionally, in the RRC connected state, the terminal device may indicate at least one of a buffer status report, a power headroom report, or information on the number of data packets to the network device. Optionally, in the RRC connected state, the terminal device may send a first MAC CE to the network device.

[0278] Optionally, when the terminal device is in the RRC non-connected state, the terminal device may indicate at least one of the buffer status report, power headroom report or data packet quantity information to the network device. That is to say, in the SDT scenario corresponding to the RRC non-connected state or other scenarios corresponding to the RRC non-connected state, the terminal device may also indicate at least one of the buffer status report, power headroom report or data packet quantity information to the network device. For example, in the RRC_INACTIVE state or the RRC_IDLE state, at least one of the buffer status report, power headroom report or data packet quantity information may be indicated to the network device. Optionally, when the terminal device is in the SDT scenario corresponding to the RRC non-connected state or other scenarios corresponding to the RRC non-connected state, the terminal device may send a first MAC CE to the network device, that is, in the SDT scenario, the terminal device may send a first MAC CE.

[0279] The first MAC CE sent by the terminal device to the network device in the RRC non-connected state can be discussed in the following situations:

[0280] In the first scenario, if the terminal device determines that there is small packet data in the buffer, the terminal device may indicate a buffer status report to the network device. Alternatively, the terminal device may indicate a buffer status report and a power headroom report to the network device. For example, the first MAC CE sent may indicate a buffer status report, or may indicate a buffer status report and a power headroom report. In this case, the buffer status report indicates the amount of small packet data in the terminal device's buffer.

[0281] Optionally, based on the terminal device determining that the aforementioned BSR triggering conditions are met and that small packet data exists in the buffer, triggering the terminal device to report a buffer status report, the terminal device then instructs the network device to transmit the buffer status report. Optionally, the first MAC CE is used to instruct the buffer status report. Optionally, the first MAC CE may carry the buffer status report. In other words, the triggering conditions for the buffer status report in this embodiment of the present application may be that the aforementioned BSR triggering conditions are met and that small packet data exists in the buffer.

[0282] Optionally, the amount of data in the buffer indicated by the buffer status report mentioned in the embodiment of the present application may be the amount of available uplink packet data of the logical channel corresponding to the SDTDRB.

[0283] Optionally, if the terminal device determines that there is small packet data in the buffer, and further, the terminal device determines that the triggering condition of the PHR introduced above is met, the terminal device triggers to send a power headroom report; if the terminal device determines that the triggering condition of the BSR introduced above is met, the terminal device is triggered to send a buffer status report. For example, the amount of data indicated by the triggered buffer status report may be the amount of uplink small packet data. Therefore, the terminal device indicates the buffer status report and the power headroom report to the network device. Optionally, the first MAC CE is used to indicate the buffer status report and the power headroom report. That is, the triggering condition for the buffer status report in the embodiment of the present application may be satisfying the triggering condition of the BSR described above, and the triggering condition for the power headroom report in the embodiment of the present application may be satisfying the triggering condition of the PHR described above and satisfying the presence of small packet data in the buffer.

[0284] In the second scenario, if the terminal device determines that there will be subsequent transmission, the terminal device may indicate the number of data packets to the network device, or indicate the number of data packets and the power headroom report. For example, the first MACCE sent is used to indicate the number of data packets, or to indicate the number of data packets and the power headroom report. In this case, the number of data packets is used to indicate the number of data packets of the subsequently transmitted small packet data.

[0285] That is, if the terminal device determines that there is a subsequent transmission, the terminal device triggers the transmission of a power headroom report and the number of data packets. Optionally, the terminal device triggers the transmission of a power headroom report if: the terminal device determines that there is a subsequent transmission and the triggering condition of the PHR described above is met. That is, in the embodiment of the present application, the triggering condition for the number of data packets may be the satisfaction of the subsequent transmission, and the triggering condition for the power headroom report in the embodiment of the present application may be the satisfaction of the triggering condition of the PHR described above and the satisfaction of the subsequent transmission.

[0286] In case three, if the terminal device determines that there is small packet data in the buffer and that there is subsequent transmission, the terminal device can indicate the buffer status report and the number of data packets to the network device, or be used to indicate the buffer status report, power headroom report, and the number of data packets. For example, the first MAC CE sent is used to indicate the buffer status report and the number of data packets, or to indicate the buffer status report, power headroom report, and the number of data packets. In this case, the buffer status report is used to indicate the amount of small packet data in the terminal device buffer, and the number of data packets is used to indicate the number of data packets of the small packet data to be transmitted subsequently.

[0287] Optionally, the amount of data in the buffer of the buffer status report mentioned in the embodiment of the present application may be the amount of available uplink packet data of the logical channel corresponding to the SDT DRB.

[0288] Optionally, if the terminal device determines that the triggering conditions for the BSR described above are met, the terminal device is triggered to report a buffer status report. For example, the amount of data indicated by the triggered buffer status report may be the amount of uplink small packet data. If the terminal device determines that there will be subsequent transmission, the terminal device is triggered to report the number of data packets. Therefore, the terminal device indicates the number of data packets and the buffer status report to the network device. Optionally, the first MAC CE is used to indicate the number of data packets and the buffer status report. In other words, the triggering condition for the number of data packets in the embodiment of the present application may be that there will be subsequent transmission.

[0289] Optionally, when the terminal device determines that there is packet data in the buffer and / or that there is a subsequent transmission, the terminal device determines to send a power headroom report. Further, when the terminal device determines that the triggering conditions of the PHR described above are met, the terminal device is triggered to send a power headroom report. Based on the terminal device's determination that the triggering conditions of the BSR described above are met and that there is packet data in the buffer, the terminal device is triggered to report a buffer status report; when the terminal device determines that there is a subsequent transmission, the terminal device is triggered to report the number of data packets. Therefore, the terminal device indicates the number of data packets, the buffer status report, and the power headroom report to the network device. Optionally, the first MAC CE is used to indicate the number of data packets, the buffer status report, and the power headroom report. That is, the triggering conditions for the buffer status report in the embodiment of the present application can be the satisfaction of the triggering conditions of the BSR described above and the presence of packet data in the buffer. The triggering conditions for the number of data packets in the embodiment of the present application can be the satisfaction of the subsequent transmission. The triggering conditions for the power headroom report in the embodiment of the present application can be the satisfaction of the triggering conditions of the PHR described above and the presence of packet data in the buffer and / or the presence of a subsequent transmission.

[0290] Optionally, in Case 2 and Case 3, the terminal device determines that there will be subsequent transmission, including: the upper layer of the terminal device (such as the application layer or NAS layer) provides the AS layer with service type information, if the service type information provided by the upper layer indicates that the service type is multiple transmissions (mul-shot), the AS layer of the terminal device determines that there will be subsequent transmission, and the terminal device triggers reporting of the number of data packets. Optionally, the terminal device determines that there will be subsequent transmission, also including: when the upper layer of the terminal device (such as the application layer or NAS layer) determines that the current service type is multi-shot, the upper layer can notify the AS layer to trigger reporting of the number of data packets.

[0291] Optionally, the MAC subheader corresponding to the first MAC CE is the first MAC subheader, and the format of the first MAC subheader is as follows: Figure 4 As shown or Figure 6If the size of the first MAC CE is fixed, the format of the first MAC subheader is as follows: Figure 4 If the size of the first MAC CE is not fixed, the format of the first MAC subheader is as follows: Figure 6 shown. Figure 4 or Figure 6 The LCID in represents the physical meaning of the first MAC CE. Optionally, Figure 4 or Figure 6 The value of LCID in can be a first value to indicate that the physical meaning of the first MAC CE is that the first MAC CE is used to indicate at least one of the buffer status report, power headroom report or data packet quantity information. For example, the first value can be a value from 35 to 51 in Table 1, such as 35. The first value can be a fixed value. That is, the first MAC CE can be a composite MAC CE that can report one or more parameters at the same time and has only one MAC subheader. If the first MAC CE indicates multiple parameters at the same time, then compared to reporting multiple parameters separately which requires multiple MAC subheaders, the first MAC CE can save the MAC subheader overhead. Optionally, Figure 4 or Figure 6 The value of LCID in Table 1 can also be 33 or 34. In this case, the physical meaning of the first MAC CE can be indicated by extending the logical channel ID (eLCID) field to indicate that the first MAC CE is used to indicate at least one of the buffer status report, power headroom report or data packet quantity information. Figure 4 or Figure 6 The eLCID field is also included.

[0292] The format diagram of the first MAC CE is discussed below.

[0293] a) If the first MAC CE is used to indicate the buffer status report, the bits carried by the first indication field included in the first MAC CE are used to indicate the buffer status report.

[0294] For example, Figure 15 The format of the first MAC CE is shown. If the buffer status report is a short BSR MAC CE or a short truncated BSR MAC CE, the first indication field may occupy one byte. The format of the first indication field may be as follows: Figure 5 For example, the first indication field can be as follows Figure 16If the buffer status report is a long BSR MAC CE or a long truncated BSR MAC CE, the first indication field may occupy multiple bytes, each byte corresponding to a logical channel group. Figure 15 The case where the first indication field occupies multiple bytes is not shown.

[0295] Optionally, the first MAC CE includes a fourth indication field, and the bits carried by the fourth indication field are used to indicate whether the first MAC CE includes the first indication field. Figure 15 As shown, the fourth indication field can occupy one bit, and different values ​​of the bit in the fourth indication field represent different meanings. For example, when the value of the bit in the fourth indication field is 1, it indicates that the first MAC CE includes the first indication field, and when the value of the bit in the fourth indication field is 0, it indicates that the first MAC CE does not include the first indication field. For example, Figure 16 The fourth indicator field shown is B1.

[0296] It can be understood that the fact that the first MAC CE does not include the first indication field may indicate that the first MAC CE does not include the first indication field and the length of the first MAC CE is reduced by the length of the first indication field. For example, if the first indication field occupies one byte, then the fact that the first MAC CE does not include the first indication field indicates that the length of the first MAC CE is reduced by one byte. Alternatively, the fact that the first MAC CE does not include the first indication field may indicate that the first MAC CE does not include the first indication field, but the length of the first MAC CE is not reduced, and the length of the first indication field becomes a reserved bit. For example, if the first indication field occupies one byte, then the fact that the first MAC CE does not include the first indication field may indicate that the first MAC CE does not include the first indication field, but the length of the first indication field still exists. In other words, the fact that the first MAC CE does not include the first indication field indicates that the first indication field included in the first MAC CE does not exist or that the existing first indication field is meaningless.

[0297] Optionally, the first MAC CE may further include a fifth indication field, where the bits carried by the fifth indication field are used to indicate the type of buffer status report indicated by the bits carried by the first indication field. The number of bits occupied by the fifth indication field is related to the number of types of buffer status reports. If the number of types of buffer status reports is fixed, the number of bits occupied by the fifth indication field may be fixed. If the types of buffer status reports include short BSR, short truncated BSR, long BSR, and long truncated BSR, the number of bits occupied by the fifth indication field may be 2 bits, for example Figure 16 B2 in the fifth indicator field may be a fifth indicator field, and the fifth indicator field values ​​00, 01, 10, and 11 correspond to multiple types of buffer status reports respectively; or, if the number of types of buffer status reports is variable, for example, M types, the number of bits occupied by the fifth indicator field may be in This is a ceiling operation.

[0298] Optionally, when the fourth indication field indicates that the first MAC CE includes the first indication field, the fifth indication field may be present. Optionally, when the fourth indication field indicates that the first MAC CE does not include the first indication field, the first MAC CE may not include the fifth indication field. The fact that the first MAC CE does not include the fifth indication field may indicate that the first MAC CE does not include the fifth indication field and the length of the first MAC CE is reduced by the length of the fifth indication field. For example, if the fifth indication field occupies two bits, then the fact that the first MAC CE does not include the fifth indication field indicates that the length of the first MAC CE is reduced by two bits. Alternatively, the fact that the first MAC CE does not include the fifth indication field may indicate that the first MAC CE does not include the fifth indication field, but the length of the first MAC CE is not reduced, and the bits occupied by the fifth indication field become reserved bits. For example, if the fifth indication field occupies two bits, then the fact that the first MAC CE does not include the fifth indication field may indicate that the first MAC CE does not include the fifth indication field, but the length of the fifth indication field still exists. In other words, the fact that the first MAC CE does not include the fifth indication field indicates that the fifth indication field included in the first MAC CE does not exist or that the fifth indication field is meaningless.

[0299] It should be noted that the first MAC CE may not include the fourth indication field. The first indication field exists by default. If the terminal device wants to report a buffer status report, the bits carried by the first indication field are used to indicate the buffer status report. If the terminal device does not report a buffer status report, the bits occupied by the first indication field may be reserved bits.

[0300] It should also be noted that the first MAC CE may not include the fifth indication field, that is, the terminal device may not indicate the type of buffer status report. The terminal device reports a certain type of buffer status report, and the network device parses this type of buffer status report.

[0301] b) If the first MAC CE is used to indicate a power headroom report, the bits carried by the second indication field included in the first MAC CE are used to indicate a power headroom report.

[0302] For example, Figure 15 The format of the first MAC CE is shown. The second indication field can occupy one byte. The format of the second indication field can be as follows: Figure 9B The second indicator field can also occupy two bytes, and the format of the second indicator field can be as follows: Figure 9A For example, the second indication field can be as follows Figure 16 PHR MAC CE shown.

[0303] Optionally, the first MAC CE includes a sixth indication field, and the bits carried by the sixth indication field are used to indicate whether the first MAC CE includes the second indication field. Figure 15 As shown, the sixth indication field can occupy one bit, and the sixth indication field can be Figure 16 For example, when the value of the bit in the sixth indication field is 1, it indicates that the first MAC CE includes the second indication field, that is, when it is determined that there is small packet data in the subsequent transmission and / or buffer, the value of P is 1, and the network device can perform power control according to the power headroom report indicated by the bit carried by the second indication field. If there is no subsequent transmission and there is no small packet data in the buffer, the P field does not exist; when the value of the bit in the sixth indication field is 0, it indicates that the first MAC CE does not include the second indication field.

[0304] It can be understood that the fact that the first MAC CE does not include the second indication field may indicate that the first MAC CE does not include the second indication field and the length of the first MAC CE is reduced by the length of the second indication field. For example, if the second indication field occupies one byte, then the fact that the first MAC CE does not include the second indication field indicates that the length of the first MAC CE is reduced by one byte. Alternatively, the fact that the first MAC CE does not include the second indication field may indicate that the first MAC CE does not include the second indication field, but the length of the first MAC CE is not reduced, and the bits occupied by the second indication field become reserved bits. For example, if the second indication field occupies one byte, then the fact that the first MAC CE does not include the second indication field may indicate that the first MAC CE does not include the second indication field, but the length of the second indication field still exists. In other words, the fact that the first MAC CE does not include the second indication field indicates that the second indication field included in the first MAC CE does not exist or that the existing second indication field is meaningless.

[0305] It should be noted that the first MAC CE may not include the sixth indication field, and the second indication field exists by default. If the terminal device wants to report a power headroom report, the bits carried by the second indication field are used to indicate the power headroom report. If the terminal device does not report a power headroom report, the bits occupied by the second indication field may be reserved bits.

[0306] c) If the first MAC CE is used to indicate the number information of data packets, the bits carried by the third indication field included in the first MAC CE are used to indicate the number information of data packets.

[0307] Optionally, the bits carried by the third indication field may indicate an index for indicating the quantity information of data packets. In this way, a smaller number of bits may be used to indicate a larger number of data packets to be sent, thereby saving signaling overhead.

[0308] For example, Figure 15The form of the first MAC CE is shown. For example, the third indication field can be Figure 16 The SDT assistance indication (SAI) shown in FIG. 4 is an SDT assistance indication. In other words, SAI can be understood as the number information of data packets. Figure 15 and Figure 16 The third indication field occupies 3 bits, and the value of the third indication field bit can indicate the index value. Different index values ​​correspond to different numbers of data packets to be sent. As shown in Table 3, the three bits of the third indication field are 001, indicating that the number of data packets to be sent by the terminal device is 1. Of course, the value of the bits carried by the third indication field can also directly indicate the number of data packets to be sent. For example, as shown in Table 4, the value of the third indication field is 111, indicating that the number of data packets to be sent by the terminal device is 7. The more bits the third indication field occupies, the more data packets to be sent that can be indicated.

[0309] Table 3

[0310]

[0311]

[0312] Table 4

[0313] The value of the third indicator field Number of packets to be sent 000 0UL 001 1UL 010 2UL 011 3UL 100 4UL 101 5UL 110 6UL 111 7UL

[0314] Optionally, the first MAC CE includes a seventh indication field, and the bits carried by the seventh indication field are used to indicate whether the first MAC CE includes the third indication field. Figure 15 As shown, the seventh indication field may occupy one bit or multiple bits. For example, when the value of the bit in the seventh indication field is 1, it indicates that the first MAC CE includes the third indication field. When the value of the bit in the seventh indication field is 0, it indicates that the first MAC CE does not include the third indication field. Figure 16 The seventh indicator field shown is S.

[0315] It can be understood that the fact that the first MAC CE does not include the third indication field may indicate that the first MAC CE does not include the third indication field and the length of the first MAC CE is reduced by the length of the third indication field. For example, if the third indication field occupies three bits, then the fact that the first MAC CE does not include the third indication field indicates that the length of the first MAC CE is reduced by three bits. Alternatively, the fact that the first MAC CE does not include the third indication field may indicate that the first MAC CE does not include the third indication field, but the length of the first MAC CE is not reduced, and the length of the third indication field becomes a reserved bit. For example, if the third indication field occupies three bits, then the fact that the first MAC CE does not include the third indication field may indicate that the first MAC CE does not include the third indication field, but the length of the third indication field still exists. In other words, the fact that the first MAC CE does not include the third indication field indicates that the third indication field included in the first MAC CE does not exist or that the existing third indication field is meaningless.

[0316] Optionally, the number of data packets is also used to indicate the number of data packets to be received by the terminal device. In some scenarios, the terminal device can know the number of data packets to be received. For example, the terminal device sends 10 uplink data packets, and the network device needs to feedback a response packet for every 5 uplink data packets. Therefore, the terminal device can determine that the number of downlink data packets to be received is 2. For example, if the third indication field carries the number of data packets, the number of data packets carried by the third indication field can indicate the number of data packets to be sent and the number of data packets to be received by the terminal device, wherein the number of data packets to be sent and the number of data packets to be received can be a specific number of data or a range of data packet numbers. For example, assuming that the number of bits carried by the third indication field is 3, as shown in Table 5, UL shown in Table 5 represents uplink data packets, and DL represents downlink data packets. For example, the value of the third indication field is 011, indicating that the number of UL packets to be sent is 1 to 5, and the number of DL packets to be received is 1. For another example, as shown in Table 7, the value of the third indication field is 0001, indicating that the number of uplink packets to be sent is 0 and the number of downlink packet data to be received is 1.

[0317] Table 5

[0318]

[0319]

[0320] It should be noted that Figure 15 and Figure 16The format of the first MAC CE in the embodiment is only a schematic example. The first MAC CE may include at least one of a first indication field, a second indication field, a third indication field, a fourth indication field, a fifth indication field, a sixth indication field, or a seventh indication field. The length of the first indication field, the second indication field, the third indication field, the fourth indication field, the fifth indication field, the sixth indication field, or the seventh indication field may be specified by the protocol or may be variable. The positional relationship between the respective indication fields in the first indication field, the second indication field, the third indication field, the fourth indication field, the fifth indication field, the sixth indication field, or the seventh indication field may be specified by the protocol.

[0321] In some embodiments, the format of the first MAC CE can be fixed. Optionally, for a first MAC CE with a fixed format, the content indicated by the first MAC CE can be indicated by the LCID in the first MAC subheader corresponding to the first MAC CE. For example, the value of the LCID in the first MAC subheader is A, indicating that the first MAC CE indicates a buffer status report, the first MAC CE includes one byte, the first indication field in the first MAC CE occupies L bits of one byte, L is less than or equal to 8, and the 8-L bits in the first MAC CE excluding the first indication field are reserved bits. For example, the value of the LCID in the first MAC subheader is B, indicating that the first MAC CE indicates the number of data packets, the first MAC CE includes one byte, the third indication field in the first MAC CE occupies P bits of one byte, P is less than or equal to 8, and the 8-P bits in the first MAC CE excluding the third indication field are reserved bits. For example, if the value of LCID in the first MAC subheader is C, it indicates that the first MAC CE indicates a power headroom report, the first MAC CE includes one byte, the second indication field in the first MAC CE occupies Q bits of one byte, Q is less than or equal to 8, and the 8-Q bits in the first MAC CE except the second indication field are reserved bits. For example, if the value of LCID in the first MAC subheader is D, it indicates that the first MAC CE indicates a buffer status report and a power headroom report, the first MAC CE includes three bytes, the first indication field in the first MAC CE occupies W bits of one byte, the remaining 8-W bits of the byte are reserved bits, and the second indication field occupies two bytes, or the first MAC CE includes two bytes, the first indication field in the first MAC CE occupies W bits of one byte, the remaining 8-W bits of the byte are reserved bits, and the second indication field occupies one byte. For example, the value of LCID in the first MAC subheader is E, which means that the first MAC CE indicates the number information of data packets and the power headroom report. The first MAC CE includes three bytes. The third indication field in the first MAC CE occupies V bits of one byte, and the remaining 8-V bits of the byte are reserved bits. The second indication field occupies two bytes. If the first MAC CE includes two bytes, the third indication field in the first MAC CE occupies V bits of one byte, and the remaining 8-V bits of the byte are reserved bits, and the second indication field occupies one byte.For another example, the LCID value in the first MAC subheader is F, indicating that the first MAC CE indicates the buffer status report, the power headroom report, and the number of data packets. The first MAC CE includes three bytes, the first indication field in the first MAC CE occupies K bits of one byte, the third indication field of the first MAC CE occupies the remaining 8-K bits of the byte, and the second indication field occupies two bytes. Alternatively, the first MAC CE includes two bytes, the first indication field in the first MAC CE occupies K bits of one byte, the third indication field of the first MAC CE occupies the remaining 8-K bits of the byte, and the second indication field occupies one byte. If the second indication field occupies two bytes, the format of the second indication field is the same as . Figure 9A Similarly, or the second indicator field may not include Figure 9A If the second indicator field occupies one byte, the format of the second indicator field is the same as Figure 9B For example, A, B, C, E, D, and F can be 35, 36, 37, 38, 39, and 40 in Table 1, respectively. The above L, P, Q, W, V, L, and K are all positive integers less than 8.

[0322] Optionally, the format of the first MAC CE may be fixed, and the LCID in the first MAC subheader corresponding to the first MAC CE is a fixed value. If the first MAC CE does not indicate one of the parameters, the field corresponding to the parameter is a reserved bit, or the field corresponding to the parameter takes a value of 0. For example, Figure 17 As shown, the format of the first MAC CE is shown. The format of the first MAC CE is fixed. The length of the first MAC CE is fixed to three bytes. The first indication field occupies 4 bits, the second indication field occupies 2 bytes, and the third indication field occupies 4 bits. If the first MAC CE does not indicate a buffer status report, the 4 bits of the first indication field are reserved bits, or the 4 bits of the first indication field take a value of 0. Or the first indication field occupies 1 byte, the second indication field occupies 1 byte, and the third indication field occupies 4 bits. When the first indication field occupies 1 byte, the first indication field can be in a short BSR format. Or the length of the first MAC CE can be fixed to two bytes, the first indication field occupies 4 bits, the second indication field occupies 1 byte, and the third indication field occupies 4 bits. As shown Figure 18 As shown, BSR is the first indication field, SAI is the second indication field, and PHR is the third indication field. Figure 18The BSR in the BSR is used to indicate the amount of data in the buffer corresponding to the SDT DRB, or the BSR indicates an index value, which corresponds to a predefined table. For example, the table is shown in Table 6, and each index value corresponds to a range of data amount or a specific amount of data in the buffer. In this way, when the number of bits occupied by the first indication field is small, more data amount can be indicated, which is conducive to saving overhead. Figure 18 The SAI in the table indicates the specific number of subsequent ULs and DLs, or the SAI indicates an index value, which corresponds to a predefined table. For example, the table content is shown in Table 5 or Table 7, and each index value corresponds to a range or specific number of UL and DL numbers.

[0323] Table 6

[0324] The value of the first indicator field Amount of data in the buffer (in bits) 0000 (indicates index 0) 0 0001 (indicates index 1) (0,5] 0010 (indicates index 2) (5,10] 0011 (indicates index 3) (10,20] 0100 (indicates index 4) (20,40] …… …… 1111 (indicates index 15) Greater than or equal to 1000

[0325] Table 7

[0326] The value of the third indicator field The number of packets to be sent and the number of packets to be received 0000 (indicates index 0) 0UL, 0DL 0001 (indicates index 1) 0UL, 1DL 0010 (indicates index 2) 0UL, 2DL 0011 (indicates index 3) [1,3]UL,0DL 0100 (indicates index 4) [1,3]UL, 1DL …… …… 1111 (indicates index 15) ……

[0327] Optionally, the amount of data in the buffer that the buffer status report mentioned in the embodiment of the present application can indicate can be the amount of uplink packet data available in the logical channel corresponding to the SDT DRB. For example, the amount of data in the buffer that the buffer status report can indicate can be Figure 13 The amount of uplink packet data available for the logical channel corresponding to SDT DRB 1 or the amount of data in the buffer indicated by the buffer status report may be Figure 13 The amount of uplink packet data available in the logical channel corresponding to SDT DRB 2.

[0328] Optionally, the amount of data in the buffer indicated by the buffer status report mentioned in the embodiment of the present application may be the amount of MAC SDU (service data unit) data in the buffer, that is, the amount of data arriving at the upper layer.

[0329] Optionally, the amount of data in the buffer indicated by the buffer status report mentioned in the embodiment of the present application may be the amount of data of the available uplink MAC SDU of the logical channel corresponding to the SDTDRB.

[0330] Optionally, the first MAC CE may also indicate DCQR. Optionally, the third indication field carrying the quantity information of the data packet may also carry DCQR, for example, the third indication field may be Figure 8 Similarly, the third indication field may carry the quantity information and quality report of the data packets (wherein the quality report may be a DCQR). Alternatively, a ninth indication field different from the third indication field may carry a DCQR.

[0331] The above describes the format of the first MAC CE. The following describes how the terminal device indicates at least one of a buffer status report, a power headroom report, or the number of data packets to the network device:

[0332] Method 1: During the random access process, the terminal device indicates at least one of a buffer status report, a power headroom report, or the number of data packets to the network device.

[0333] Optionally, the terminal device sends a first MAC CE to the network device during the random access process, where the first MAC CE is used to indicate at least one of a buffer status report, a power headroom report, or information about the number of data packets. The network device receives the first MAC CE during the random access process of the terminal device. That is, the terminal device sends the first MAC CE to the network device in the RA-SDT.

[0334] Optionally, the terminal device sends a first MAC CE to the network device in RA-SDT, and the first MAC CE includes a second indication field. That is, the terminal device sends the first MAC CE to the network device in RA-SDT, which implies that the CG-SDT of the terminal device is invalid. Therefore, the terminal device expects the network device to dynamically schedule resources or the network device to reconfigure CG-SDT. Therefore, it is necessary to indicate the power margin of the terminal device to the network device through the second indication field so that the network device can dynamically schedule resources or reconfigure CG-SDT.

[0335] Optionally, the terminal device may send a small amount of data and a first MAC CE to the network device once during the random access process.

[0336] For example, in Figure 10 In the four-step random access process shown, the terminal device may send a first MAC CE to the network device in message 3 of S1040. That is, the terminal device may send a small amount of data once in message 3 and also indicate the first MAC CE to the network device so that the network device determines resources for the terminal device based on the first MAC CE and the parameters indicated by the first MAC CE.

[0337] For example, in Figure 11 In the two-step random access process shown, the terminal device can send a first MAC CE to the network device in message A in S1120.

[0338] When the terminal device uses Figure 2BWhen the control plane protocol stack shown in the figure performs RA-SDT, small data can be carried in message 3 or message A, carried by SRB and transmitted on CCCH. After the MAC layer generates the first MAC CE, the MAC layer multiplexes the SRB containing small data with the first MAC CE and sends it to the network device through the PHY layer. Figure 2A When the user plane protocol stack shown performs RA-SDT, the small data included in message 3 or message A is transmitted through DTCH using the user plane protocol stack at the upper layer of the MAC layer, and the RRC request message included in message 3 or message A is transmitted through CCCH using the control plane protocol stack at the upper layer of the MAC layer. After the MAC layer generates the first MAC CE, the MAC layer multiplexes the small data, RRC request message and the first MAC CE together and sends them to the network device through the PHY layer.

[0339] It should be noted that if the terminal device sends the first MAC CE to the network device in message 3 in S1040 or message A in S1120, due to resource limitations, the resources may be insufficient. The terminal device can give priority to sending the first MAC CE in message 3 in S1040. If the resources for sending small data are insufficient, the small data may not be sent and the first MAC CE may be sent; or in order to send the first MAC CE, part of the small data originally sent in message 3 in S1040 or message A in S1120 may be sent in message 3 in S1040 or message A in S1120, and the remaining small data may be sent on the resources configured by the network device in S1420.

[0340] Method 2: The terminal device indicates at least one of a buffer status report, a power headroom report, or the quantity information of data packets to the network device on preconfigured resources.

[0341] Optionally, the terminal device sends a first MAC CE to the network device on preconfigured resources, where the first MAC CE is used to indicate at least one of a buffer status report, a power headroom report, or information about the number of data packets. The network device receives the first MAC CE on the preconfigured resources. Optionally, the terminal device sends the first MAC CE to the network device in a CG-SDT.

[0342] Optionally, when the terminal device sends a first MAC CE to the network device in the CG-SDT, it indicates that the current CG-SDT is valid. Optionally, the terminal device may not include the second indication field. That is, the terminal device determines that the network device may not reconfigure resources for the terminal device because the current CG-SDT is valid, so the terminal device may not indicate the power margin of the terminal device to the network device. Optionally, the terminal device may also include a second indication field, that is, the terminal device determines that even if the current CG-SDT is valid, the network device may reconfigure resources for the terminal device, so the terminal device may indicate the power margin of the terminal device to the network device, that is, the first MAC CE may include a second indication field. In other words, when the terminal device sends the first MAC CE via CG-SDT, it may include or may not include the second indication field. If the first MACCE does not include the second indication field, the network device determines that the terminal device continues to use the currently valid CG-SDT. If the first MACCE includes the second indication field, the network device may determine based on the second indication field whether the terminal device continues to use the currently valid CG-SDT or determines to reconfigure resources for the terminal device. Optionally, the resources reconfigured by the network device according to the second indication field may be dynamically scheduled resources, or reconfigured CG-SDT resources.

[0343] For example, in Figure 12 In the CG-SDT shown, the terminal device may send a first MAC CE to the network device in S1230. The manner in which the terminal device sends the first MAC CE is similar to manner 1 and is not further described. That is, the terminal device may send a small amount of data once on the resources indicated by the CG-SDT configuration, and also indicate the first MAC CE to the network device, so that the network device determines resources for the terminal device based on the first MAC CE and the parameters indicated by the first MAC CE.

[0344] For example, in different scenarios of method one and method two, the first MAC CE includes different indication fields. As shown in Table 8, the first column indicates the type of SDT in different scenarios. The second to fourth columns respectively indicate whether the third indication field, the second indication field, and the first indication field are included. For the scenario in which there is only one SDT in the second and third rows, that is, the number of data packets is 0, indicating that there is no subsequent small data after the current SDT is transmitted, the terminal device may not send the first MAC CE to the network device. For the fourth and fifth rows, although there is only one SDT scenario, since the size of the data packet corresponding to one SDT is larger than the size of message 3 or message A or the pre-configured resource, the data packet corresponding to the one SDT needs to be divided into multiple transmissions, that is, there is data to be transmitted in the buffer of the terminal device, and the first MAC CE also needs to be transmitted during the transmission of the SDT. Therefore, the first MAC CE may include the second indication field and the first indication field, but does not include the third indication field. For the sixth and seventh rows, when there are multiple SDTs, the first MAC CE may include a first indication field, a second indication field, and a third indication field. In this case, the corresponding situation may be that the buffer status report carried by the first indication field indicates that the data in the buffer is the remaining data of the first SDT among the multiple SDTs. For the eighth row, when there are one or more SDTs, if the transmission is not completed in message 3 or message A or pre-configured resources, the first MAC CE includes a first indication field, and the buffer status report carried by the first indication field indicates the data in the buffer. If the first indication field exists, the second indication field also exists. If the application layer does not provide information on the number of data packets, the third indication field does not exist. For the ninth and tenth rows, when there are multiple SDTs, the first MAC CE may include a second indication field and a third indication field. In this case, the corresponding situation may be that the first SDT data packet among the multiple SDTs is transmitted in message 3 or message A or pre-configured, and there is no data in the buffer. It should be noted that in Table 8, one SDT means that there is no subsequent small data after the transmission of one small data, so the number of data packets to be transmitted is 0, and multiple SDTs mean that there are multiple data packets after the transmission of one small data, so the number of data packets to be transmitted is greater than 1.

[0345] Table 8

[0346]

[0347] Optionally, after receiving the first MAC CE, the network device indicates that there is subsequent small data, and determines not to release the transmission resources between the terminal device and the network device. Alternatively, after receiving the first MAC CE, the network device indicates that there is subsequent small data, and determines not to end the current SDT process of the terminal device and release it to the RRC non-connected state. Alternatively, after receiving the first MAC CE, the network device indicates that there is subsequent small data, and determines not to send an RRC response message to the terminal device, such as not sending an RRC release message.

[0348] For example, if the network device is a distributed network device, the network device includes a centralized unit (CU) and a distributed unit (DU), wherein the CU includes an RRC layer and a PDCP layer, and the DU includes an RLC layer, a MAC layer, and a PHY layer. The DU can receive a first MAC CE, and the DU can send a first indication message to the CU based on the first MAC CE, and the first indication message is used to instruct the CU not to immediately end the current SDT process. After receiving the first indication message, the CU will not immediately end the current SDT process, but will wait for the terminal device to complete the subsequent SDT before ending the SDT and releasing the UE to the RRC non-connected state. The DU can send the first indication message to the CU through a message on the F1 interface, such as Figure 19 As shown, the F1 interface is the interface between CU and DU. Figure 19 The Uu interface in the first indication information is the interface between the terminal device and the network device. Optionally, the first indication information may also instruct the CU not to immediately release the terminal device or to instruct not to immediately send an RRC message. When the first MAC CE is used to indicate a buffer status report and / or the number of data packets, the first indication information may also indicate the number of subsequent data packets and / or the amount of data in the buffer.

[0349] S1420: The network device configures resources for the terminal device according to at least one of the buffer status report, the power headroom report, or the quantity information of the data packets.

[0350] Optionally, if the terminal device indicates a buffer status report to the network device, the network device configures resources for the terminal device based on the amount of data in the buffer indicated by the buffer status report. Optionally, if the buffer status report indicates the amount of data in the buffer corresponding to the SDT DRB, the network device configures resources for the corresponding SDT DRB based on the amount of data in the buffer corresponding to the SDT DRB indicated by the buffer status report.

[0351] Optionally, if the terminal device indicates a buffer status report and a power headroom report to the network device, the network device configures resources for the terminal device according to the amount of data in the buffer indicated by the buffer status report and the power headroom of the terminal device indicated by the power headroom report.

[0352] Optionally, if the terminal device indicates the number of data packets to the network device, the network device configures resources for the terminal device according to the number of data packets for subsequent transmission indicated by the number of data packets.

[0353] Optionally, if the terminal device indicates the number of data packets and the power headroom report to the network device, the network device configures resources for the terminal device based on the number of subsequently transmitted data packets indicated by the number of data packets and the power headroom of the terminal device indicated by the power headroom report.

[0354] Optionally, if the terminal device indicates a buffer status report, data packet quantity information and a power headroom report to the network device, the network device configures resources for the terminal device based on the amount of data in the buffer indicated by the buffer status report, the number of data packets to be subsequently transmitted indicated by the data packet quantity information and the power headroom of the terminal device indicated by the power headroom report.

[0355] Optionally, if the terminal device indicates at least one of a buffer status report, a power headroom report, or the number of data packets through the first MAC CE, Optionally, S1420 may include: the network device configuring resources for the terminal device according to the first MAC CE.

[0356] The following discusses different situations in which the network device configures resources for the terminal device according to the first MAC CE.

[0357] Case 1, optionally, S1420, including: the network device can dynamically schedule resources for the terminal device according to the first MAC CE, for example, the network device can send first downlink control information (DCI) to the terminal device, and the first DCI can indicate the resources scheduled by the network device for the terminal device. Optionally, the resource scheduled by the network device for the terminal device indicated by the first DCI can be a dynamically scheduled resource. Optionally, the resource scheduled by the network device for the terminal device indicated by the first DCI can be a periodic resource or a non-periodic resource.

[0358] Optionally, if the terminal device indicates at least one of a buffer status report, a power headroom report, or the number of data packets to the network device through the random access process of the above-mentioned method 1, it is assumed that the terminal device expects the network device to dynamically schedule resources for the terminal device. Alternatively, it is assumed that the current pre-configured resources of the terminal device are invalid (CG-SDT is invalid), and the network device is expected to dynamically schedule resources for the terminal device.

[0359] Case 2, optionally, S1420 includes: the network device may configure pre-configured resources for the terminal device according to the first MAC CE.

[0360] For example, the network device may send a CG-SDT configuration to the terminal device, where the CG-SDT configuration is used to indicate pre-configured resources for performing SDT.

[0361] Optionally, if the terminal device indicates at least one of a buffer status report, a power headroom report, or the number of data packets to the network device through the random access process of the above-mentioned method 1, it is assumed that the terminal device expects the network device to reconfigure preconfigured resources for the terminal device. Or, it is assumed that the current preconfigured resources of the terminal device (CG-SDT is invalid) are invalid, and the network device is expected to reconfigure preconfigured resources for the terminal device. Optionally, the preconfigured resources reconfigured by the network device may be reconfigured CG-SDT resources.

[0362] In case three, as an alternative to S1420, the network device determines to use the pre-configured resources as the resources for the terminal device to transmit data. In other words, the network device may no longer configure resources for the terminal device, and the pre-configured resources already configured for the terminal device can also transmit subsequent small data.

[0363] Optionally, the network device may instruct the terminal device to continue using the already configured preconfigured resources.

[0364] Optionally, if the terminal device does not receive new resources configured by the network device within a preset time period, the terminal device defaults to using the pre-configured resources that have been configured. For example, if the terminal device does not receive new resources configured by the network device during the timer running, the terminal device defaults to using the pre-configured resources that have been configured.

[0365] Optionally, after S1420, method 1400 further includes S1430.

[0366] S1430, the terminal device sends data to the network device according to the resources configured in S1420.

[0367] For case 1 in S1420 , the terminal device sends data to the network device on dynamically scheduled resources. For example, the terminal device sends data on aperiodic resources or periodic resources indicated by the DCI, such as sending small data.

[0368] Optionally, if the terminal device sends a first MAC CE to the network device in message 3 in S1040, the network device dynamically schedules resources for the terminal device after S1040 and before S1050, and the terminal device sends subsequent small data to the network device on the dynamically scheduled resources between S1040 and S1050. When the network device receives the subsequent small data, the network device can execute S1050. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1050 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data to be subsequently transmitted, or the subsequent small data includes small packet data in the buffer and small packet data to be subsequently transmitted.

[0369] Optionally, if the terminal device sends a first MAC CE to the network device in message A in S1120, the network device dynamically schedules resources for the terminal device after S1120 and before S1130, and the terminal device sends subsequent small data to the network device on the dynamically scheduled resources between S1120 and S1130. When the network device receives the subsequent small data, the network device can execute S1130. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1050 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data to be subsequently transmitted, or the subsequent small data includes small packet data in the buffer and small packet data to be subsequently transmitted.

[0370] Optionally, if the terminal device sends the first MAC CE to the network device in S1230, the network device dynamically schedules resources for the terminal device after S1230 and before S1240, and the terminal device sends subsequent small data to the network device on the dynamically scheduled resources between S1230 and S1240, when the network device receives the subsequent small data, the network device can execute S1240. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1240 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data for subsequent transmission, or the subsequent small data includes small packet data in the buffer and small packet data for subsequent transmission.

[0371] For the second scenario in S1420 , the terminal device sends data to the network device on the pre-configured resources. For example, if the terminal device wants to send small data, the terminal device sends the data on the pre-configured resources.

[0372] Optionally, if the terminal device sends a first MAC CE to the network device in message 3 in S1040, the network device preconfigures resources for the terminal device after S1040 and before S1050, and the terminal device sends subsequent small data to the network device on the preconfigured resources between S1040 and S1050. When the network device receives the subsequent small data, the network device can execute S1050. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1050 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data to be subsequently transmitted, or the subsequent small data includes small packet data in the buffer and small packet data to be subsequently transmitted.

[0373] Optionally, if the terminal device sends a first MAC CE to the network device in message A in S1120, the network device preconfigures resources for the terminal device after S1120 and before S1130, and the terminal device sends subsequent small data to the network device on the preconfigured resources between S1120 and S1130. When the network device receives the subsequent small data, the network device can execute S1130. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1050 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data to be subsequently transmitted, or the subsequent small data includes small packet data in the buffer and small packet data to be subsequently transmitted.

[0374] Optionally, if the terminal device sends the first MAC CE to the network device in S1230, the network device preconfigures resources for the terminal device after S1230 and before S1240, and the terminal device sends subsequent small data to the network device on the preconfigured resources between S1230 and S1240, and when the network device receives the subsequent small data, the network device can execute S1240. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1240 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data to be subsequently transmitted, or the subsequent small data includes small packet data in the buffer and small packet data to be subsequently transmitted.

[0375] For situation three in S1420 , the terminal device sends data to the network device using pre-configured resources configured in advance.

[0376] Optionally, if the terminal device sends a first MAC CE to the network device in message 3 in S1040, the terminal device sends subsequent small data to the network device on the pre-configured resources configured in advance between S1040 and S1050. When the network device receives the subsequent small data, the network device can execute S1050. That is, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1050 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data for subsequent transmission, or the subsequent small data includes small packet data in the buffer and small packet data for subsequent transmission.

[0377] Optionally, if the terminal device sends a first MAC CE to the network device in message 3 in S1120, the terminal device sends subsequent small data to the network device on the pre-configured pre-configured resources between S1120 and S1130, and when the network device receives the subsequent small data in the buffer, the network device can execute S1130. That is, after the network device ensures that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1050 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data for subsequent transmission, or the subsequent small data includes small packet data in the buffer and small packet data for subsequent transmission.

[0378] Optionally, if the terminal device sends the first MAC CE to the network device in S1230, the terminal device sends subsequent small data to the network device on the pre-configured pre-configured resources between S1230 and S1240, and when the network device receives the subsequent small data, the network device can execute S1240. That is to say, after ensuring that the subsequent small data is received, the network device can end the current SDT process of the terminal device through S1240 and release the terminal device to the RRC non-connected state, avoiding the need for the terminal device to re-initiate a random access to transmit subsequent small data, thereby saving signaling overhead. Optionally, the subsequent small data includes small packet data in the buffer, or the subsequent small data includes small packet data for subsequent transmission, or the subsequent small data includes small packet data in the buffer and small packet data for subsequent transmission.

[0379] Optionally, if the number of data packets indicated by the terminal device to the network device also indicates the number of data packets to be received. The method also includes: in S1420, the network device may also indicate to the terminal device through the second DCI the resources for receiving downlink data. The terminal device receives the downlink data sent by the network device on the resources indicated by the second DCI. Optionally, the resource indicated by the second DCI may be a dynamically scheduled transmission resource, or a downlink semi-persistent scheduling (SPS) resource, or a dynamically scheduled periodic resource, or a plurality of dynamically scheduled non-periodic resources.

[0380] It should be noted that, in the embodiments of the present application, only the case where the terminal device is in an RRC non-connected state and the terminal device transmits packet data to the network device is described as an example. The embodiments of the present application can also be applied to non-SDT scenarios where the terminal device is in an RRC connected state or in an RRC non-connected state. For example, the terminal device can send a first MAC CE to the network device in an RRC connected state or in a non-SDT scenario where the terminal device is in an RRC non-connected state, and the first MAC CE is used to indicate at least one of a buffer status report, a power headroom report, or the number of data packets. For example, the first MAC CE is used to indicate at least one of a buffer status report, a power headroom report, or the number of data packets. The network device can configure resources for the data packets to be transmitted by the terminal device and / or the amount of data in the buffer based on at least one of the buffer status report, the power headroom report, or the number of data packets. The terminal device transmits the buffered data and / or the data packets to be sent to the network device in the RRC connected state on the configured resources.

[0381] In order to better illustrate the method for transmitting data provided by the embodiment of the present application, Figure 20-25 Describes a method for transmitting small data. Figure 20 and Figure 21The description is that the terminal device indicates the buffer status report, the number of data packets and the power headroom report to the network device through the first MAC CE. Figure 22 and Figure 23 The description is that the terminal device indicates the quantity information of data packets and the power headroom report to the network device through the first MACCE. Figure 24 and Figure 25 The description is that the terminal device indicates the buffer status report and the power headroom report to the network device through the first MAC CE.

[0382] Figure 20 The first MAC CE is sent through RA-SDT, and the first MAC CE indicates a buffer status report, the number of data packets, and power headroom information, such as Figure 20 As shown, the method 2000 includes:

[0383] S2001, the terminal device is in an RRC non-connected state (for example, in the RRC_INACTIVE state), a data packet arrives at a higher layer of the terminal device (for example, the higher layer includes the RRC layer and / or the NAS layer), and the service corresponding to the arriving data packet is multi-shot transmission.

[0384] For example, the current service is instant messaging. When data arrives, the terminal device can obtain two pieces of feedback information from the network device corresponding to the uplink data, such as the transmission control protocol (TCP) feedback of the instant message and the transmission status notification of the instant message.

[0385] At S2002, the terminal device's access stratum (AS) determines that the size of the currently arriving data packet is smaller than the small data size threshold and determines that an SDT process can be initiated. In other words, the arriving data corresponds to a multi-shot SDT service. The AS layer of the terminal device triggers the sending of data packet quantity information to the network device. This data packet quantity information indicates the number of small packets to be transmitted subsequently.

[0386] That is to say, the terminal device determines the corresponding service type based on the currently arrived data, and the terminal device predicts the number of subsequently arriving data packets based on the service type. If the size of the currently arrived data packet is smaller than the small data size threshold, the terminal device determines that the sizes of subsequently arriving data packets are all smaller than the small data size threshold. Therefore, the number of data packets of subsequently arriving small packet data can be indicated by the number information of the data packets.

[0387] Optionally, the small data size threshold may be specified by a protocol or configured by a network device.

[0388] Optionally, after S2001, the upper layer of the terminal device provides the AS layer of the terminal device with a service type of multiple transmissions. The AS layer of the terminal device determines that the service type provided by the upper layer is multiple transmissions, and determines that the currently arriving data packet meets the small data size threshold. The AS layer of the terminal device triggers the sending of the quantity information of the data packet to the network device.

[0389] Optionally, after S2001, the upper layer of the terminal device notifies the AS layer to trigger the sending of the quantity information of the data packet. When the data packet reaches the AS layer, the AS layer of the terminal device determines that the size of the data packet is less than the small data size threshold, the AS layer of the terminal device triggers the sending of the quantity information of the data packet to the network device.

[0390] If CG-SDT is invalid, the terminal device determines to initiate RA-SDT.

[0391] S2003, the terminal device determines to send small data in message 3 or message A. When assembling the package or before assembling the package, the terminal device determines that it cannot complete the transmission of the current small data through message 3 or message A in one time, that is, there is still remaining small data in the buffer, and if the conditions for triggering the reporting of the buffer status report are met, the terminal device triggers the sending of the buffer status report to the network device. The buffer status report is used to indicate the data amount of the small data in the buffer.

[0392] Optionally, when assembling the package, the terminal device determines that it is impossible to complete the transmission of the current small data through message 3 or message A once, including: when assembling the package, the terminal device determines that there are insufficient resources to send message 3 or message A, resulting in the inability to transmit the current small data, so the remaining small data needs to be saved in the buffer.

[0393] Optionally, if the terminal device triggers sending a buffer status report, then the power headroom report is triggered. Optionally, if the terminal device triggers sending the number of data packets, then the power headroom report is triggered. In other words, if the terminal device triggers sending a buffer status report and / or data packet data information, then the power headroom report is triggered.

[0394] S2004: The terminal device sends small data and a first MAC CE to the network device in message 3 or message A. The first MAC CE is used to indicate status buffer report, power headroom report and data packet quantity information.

[0395] Optionally, if small data and the first MAC CE are sent via message A, similar to S1120, message A may also include a preamble and an RRC request message. That is, if RA-SDT is performed, the first MAC CE, preamble, small data, and RRC request message may be sent via message A.

[0396] Optionally, if small data and the first MAC CE are sent via message 3, similar to S1040, message 3 may also include an RRC request message. That is, if RA-SDT is performed, the first MAC CE, small data, and RRC request message may be sent via message 3.

[0397] It is understood that, as an alternative to S2004, the terminal device sends the first MAC CE in message 3 or message A. That is, if resources for sending message 3 or message A are limited, the terminal device determines to send the first MAC CE in message 3 or message A and may not send the currently arriving small data. The currently arriving small data may be buffered, and the buffer status report may indicate the amount of data in the buffer.

[0398] S2005: After receiving the first MAC CE in message 3 or message A, the network device configures resources for the terminal device according to the buffer status report, power headroom report and data packet information indicated by the first MAC CE.

[0399] Optionally, in S2005, the resources allocated by the network device to the terminal device may be dynamically scheduled resources or pre-configured CG-SDT resources.

[0400] Optionally, after receiving the first MAC CE in message 3 or message A, the network device determines not to end the current SDT.

[0401] S2006, the terminal device is in an RRC non-connected state (for example, in an RRC_INACTIVE state), and sends subsequent small data to the network device on the resources configured by the network device.

[0402] Optionally, the subsequent small data may include small data in the buffer and subsequently arrived small data, and the number of subsequently arrived small data may be the number of data packets indicated by the number information of the data packets.

[0403] Optionally, after receiving subsequent small data, the network device may end the SDT.

[0404] Figure 21 In the embodiment, the first MAC CE is sent via CG-SDT, and the first MAC CE indicates a buffer status report, the number of data packets, and power headroom information. Figure 21 As shown, the method 2100 includes:

[0405] S2101, the terminal device is in an RRC non-connected state (for example, in an RRC_INACTIVE state), a data packet arrives at a higher layer of the terminal device (for example, the higher layer includes an RRC layer and / or a NAS layer), and the service corresponding to the arriving data packet is multi-shot transmission.

[0406] For example, the current service is instant messaging. When data arrives, the terminal device can obtain two pieces of feedback information from the network device corresponding to the uplink data, such as the TCP feedback of the instant message and the transmission status notification of the instant message.

[0407] At step S2102, the terminal device's access stratum (AS) determines that the size of the currently arriving data packet is less than the small data size threshold and determines that an SDT process can be initiated. In other words, the service corresponding to the arriving data is a multi-shot SDT transmission. The AS layer of the terminal device triggers the transmission of data packet quantity information to the network device. This data packet quantity information indicates the number of small packets to be transmitted subsequently.

[0408] That is to say, the terminal device determines the corresponding service type based on the currently arrived data, and the terminal device predicts the number of subsequently arriving data packets based on the service type. If the size of the currently arrived data packet is smaller than the small data size threshold, the terminal device determines that the sizes of subsequently arriving data packets are all smaller than the small data size threshold. Therefore, the number of data packets of subsequently arriving small packet data can be indicated by the number information of the data packets.

[0409] Optionally, the small data size threshold may be specified by a protocol or configured by a network device.

[0410] Optionally, after S2101, the upper layer of the terminal device provides the AS layer of the terminal device with a service type of multiple transmissions. The AS layer of the terminal device determines that the service type provided by the upper layer is multiple transmissions, and determines that the currently arriving data packet meets the small data size threshold. The AS layer of the terminal device triggers the sending of the quantity information of the data packet.

[0411] Optionally, after S2101, the upper layer of the terminal device notifies the AS layer to trigger the sending of the quantity information of the data packet. When the data packet reaches the AS layer, the AS layer of the terminal device determines that the size of the data packet is less than the small data size threshold, the AS layer of the terminal device triggers the sending of the quantity information of the data packet to the network device.

[0412] If the CG-SDT is valid, the terminal device determines to initiate the CG-SDT. Alternatively, if the CG-SDT is valid and the RA-SDT is invalid, the terminal device determines to send the CG-SDT.

[0413] S2103, the terminal device determines to send small data on the resources indicated by the CG-SDT configuration. The terminal device determines that the transmission of the current small data cannot be completed through one CG-SDT resource when assembling the packet or before assembling the packet, that is, there is still remaining small data in the buffer, and if the conditions for triggering the reporting of the buffer status report are met, the terminal device triggers the sending of the buffer status report to the network device. The buffer status report is used to indicate the amount of small data in the buffer.

[0414] Optionally, when assembling a packet, the terminal device determines that it is not possible to complete the transmission of the current small data through one CG-SDT resource, including: when assembling a packet, the terminal device determines that sending one CG-SDT resource is not enough to transmit the small data once, resulting in the inability to transmit the current small data, and therefore the remaining small data needs to be saved in a buffer.

[0415] Optionally, if the terminal device triggers sending a buffer status report, then the power headroom report is triggered. Optionally, if the terminal device triggers sending the number of data packets, then the power headroom report is triggered. In other words, if the terminal device triggers sending a buffer status report and / or data packet data information, then the power headroom report is triggered.

[0416] S2104: The terminal device sends small data and a first MAC CE to the network device on the CG-SDT resource. The first MAC CE is used to indicate a buffer status report, a power headroom report, and the number of data packets.

[0417] It is understood that, as an alternative to S2004, the terminal device sends the first MAC CE on the CG-SDT resources. That is, if the CG-SDT resources are limited, the terminal device determines to send the first MAC CE on the CG-SDT resources and may not send the currently arriving small data. The currently arriving small data may be buffered, and the buffer status report may indicate the amount of data in the buffer.

[0418] S2105, after receiving the first MAC CE on the CG-SDT resource, the network device configures resources for the terminal device according to the buffer status report, power headroom report and data packet data information in the first MAC CE.

[0419] Optionally, in S2105, the resources allocated by the network device to the terminal device may be dynamically scheduled resources or pre-configured CG-SDT resources.

[0420] Optionally, the terminal device can continue to use the CG-SDT resources configured by the previous CG-SDT (for example, the resources configured by the CG-SDT in S1220 are the previously configured resources), that is, the network device can newly configure resources for the terminal device, or the terminal device can continue to use the CG-SDT resources configured by the previous CG-SDT, and the network device does not need to reconfigure resources.

[0421] Optionally, after receiving the first MAC CE on the CG-SDT resource, the network device determines not to end the current SDT.

[0422] S2106, the terminal device is in the RRC non-connected state, and the terminal device sends subsequent small data to the network device on the resources configured by the network device or the CG-SDT resources previously configured by CG-SDT.

[0423] Optionally, the subsequent small data may include small data in the buffer and subsequently arrived small data, and the number of subsequently arrived small data may be the number of data packets indicated by the number information of the data packets.

[0424] Optionally, after receiving subsequent small data, the network device may end the SDT.

[0425] Figure 22 In the embodiment, the first MAC CE is sent via RA-SDT, and the first MAC CE indicates the data information and power headroom information of the data packet. Figure 22 As shown, the method 2200 includes:

[0426] S2201, the terminal device is in an RRC non-connected state (for example, in the RRC_INACTIVE state), a data packet arrives at a higher layer of the terminal device (for example, the higher layer includes the RRC layer and / or the NAS layer), and the service corresponding to the arriving data packet is multi-shot transmission.

[0427] For example, the current service is instant messaging. When data arrives, the terminal device can obtain two pieces of feedback information from the network device corresponding to the uplink data, such as the TCP feedback of the instant message and the transmission status notification of the instant message.

[0428] In step S2202, the terminal device's access stratum (AS) determines that the size of the currently arriving data packet is smaller than the small data size threshold and determines that an SDT process can be initiated. In other words, the arriving data corresponds to a multi-shot SDT transmission (SDT) service. The AS layer of the terminal device triggers the sending of data packet quantity information to the network device. This data packet quantity information indicates the number of small packets to be transmitted subsequently.

[0429] That is to say, the terminal device determines the corresponding service type based on the currently arrived data, and the terminal device predicts the number of subsequently arriving data packets based on the service type. If the size of the currently arrived data packet is smaller than the small data size threshold, the terminal device determines that the sizes of subsequently arriving data packets are all smaller than the small data size threshold. Therefore, the number of data packets of subsequently arriving small packet data can be indicated by the number information of the data packets.

[0430] Optionally, the small data size threshold may be specified by a protocol or configured by a network device.

[0431] Optionally, after S2201, the upper layer of the terminal device provides the AS layer of the terminal device with a service type of multiple transmissions. The AS layer of the terminal device determines that the service type provided by the upper layer is multiple transmissions and that the currently arriving data packet meets the small data size threshold. The AS layer of the terminal device triggers the sending of the quantity information of the data packet to the network device.

[0432] Optionally, after S2201, the upper layer of the terminal device notifies the AS layer to trigger the sending of the number information of data packets. When the data packet reaches the AS layer, the AS layer of the terminal device determines that the size of the data packet reached is less than the small data size threshold, the AS layer of the terminal device triggers the sending of the number information of data packets.

[0433] Optionally, the terminal device triggers the sending of the number of data packets, thereby triggering the sending of a power margin report.

[0434] If CG-SDT is invalid, the terminal device determines to initiate RA-SDT.

[0435] S2203, the terminal device determines to send small data in message 3 or message A. When or before packet assembly, the terminal device determines that the first transmission of small data in the current multi-shot SDT can be completed through message 3 or message A once, that is, there is no remaining small data in the buffer, and it is determined not to send a buffer status report.

[0436] S2204: The terminal device sends small data and a first MAC CE to the network device in message 3 or message A. The first MAC CE is used to indicate the power headroom report and the number of data packets.

[0437] Optionally, if small data and the first MAC CE are sent via message A, similar to S1120, message A may also include a preamble and an RRC request message. That is, if RA-SDT is performed, the first MAC CE, preamble, small data, and RRC request message may be sent via message A.

[0438] Optionally, if small data and the first MAC CE are sent via message 3, similar to S1040, message 3 may also include an RRC request message. That is, if RA-SDT is performed, the first MAC CE, small data, and RRC request message may be sent via message 3.

[0439] S2205: After receiving the first MAC CE in message 3 or message A, the network device configures resources for the terminal device according to the quantity information of the data packets and the power headroom report in the first MAC CE.

[0440] Optionally, in S2205, the resources allocated by the network device to the terminal device may be dynamically scheduled resources or pre-configured CG-SDT resources.

[0441] Optionally, after receiving the first MAC CE in message 3 or message A, the network device determines not to end the current SDT.

[0442] S2206, the terminal device is in an RRC non-connected state (for example, in an RRC_INACTIVE state), and sends subsequent small data to the network device on the resources configured by the network device.

[0443] Optionally, the subsequent small data may include small data in the buffer and subsequently arrived small data, and the number of subsequently arrived small data may be the number of data packets indicated by the number information of the data packets.

[0444] Optionally, after receiving subsequent small data, the network device may end the SDT.

[0445] Figure 23 In the embodiment, the first MAC CE is sent through CG-SDT, and the first MAC CE indicates the number of data packets and the power headroom information. Figure 23 As shown, method 2300 includes:

[0446] S2301, the terminal device is in an RRC non-connected state (for example, in an RRC_INACTIVE state), a data packet arrives at a higher layer of the terminal device (for example, the higher layer includes an RRC layer and / or a NAS layer), and the service corresponding to the arriving data packet is multi-shot transmission.

[0447] For example, the current service is instant messaging. When data arrives, the terminal device can obtain two pieces of feedback information from the network device corresponding to the uplink data, such as the TCP feedback of the instant message and the transmission status notification of the instant message.

[0448] In step S2302, the terminal device's access stratum (AS) determines that the size of the currently arriving data packet is smaller than the small data size threshold and determines that an SDT process can be initiated. In other words, the arriving data corresponds to a multi-shot SDT service. The terminal device's AS triggers the sending of data packet quantity information to the network device. This data packet quantity information indicates the number of small packets to be transmitted subsequently.

[0449] That is to say, the terminal device determines the corresponding service type based on the currently arrived data, and the terminal device predicts the number of subsequently arriving data packets based on the service type. If the size of the currently arrived data packet is smaller than the small data size threshold, the terminal device determines that the sizes of subsequently arriving data packets are all smaller than the small data size threshold. Therefore, the number of data packets of subsequently arriving small packet data can be indicated by the number information of the data packets.

[0450] Optionally, the small data size threshold may be specified by a protocol or configured by a network device.

[0451] Optionally, after S2301, the upper layer of the terminal device provides the AS layer of the terminal device with a service type of multiple transmissions. The AS layer of the terminal device determines that the service type provided by the upper layer is multiple transmissions, and determines that the currently arriving data packet meets the small data size threshold. The AS layer of the terminal device triggers the sending of the quantity information of the data packet.

[0452] Optionally, after S2301, the upper layer of the terminal device notifies the AS layer to trigger the sending of the number of data packets. When the data packet reaches the AS layer, the AS layer of the terminal device determines that the size of the data packet is less than the small data size threshold, the AS layer of the terminal device triggers the sending of the number of data packets.

[0453] Optionally, the terminal device triggers the sending of the number of data packets, thereby triggering the sending of a power margin report.

[0454] If the CG-SDT is valid, the terminal device determines to initiate the CG-SDT. Alternatively, if the CG-SDT is valid and the RA-SDT is invalid, the terminal device determines to send the CG-SDT.

[0455] S2303: The terminal device determines to send small data on the resources indicated by the CG-SDT configuration. The terminal device determines that the small data transmission can be completed through one CG-SDT resource during packet assembly, that is, there is no remaining small data in the buffer. If the current small data transmission cannot be completed through one CG-SDT resource, that is, there is still remaining small data in the buffer, and if the conditions for sending a buffer status report are met, the terminal device determines to send a buffer status report, which is used to indicate the amount of small data in the buffer.

[0456] S2304: The terminal device sends small data and a first MAC CE to the network device on the CG-SDT resource. The first MAC CE is used to indicate the power headroom report and the number of data packets.

[0457] S2305: After receiving the first MAC CE on the CG-SDT resource, the network device configures resources for the terminal device according to the power headroom report and data information of the data packet in the first MAC CE.

[0458] Optionally, in S2305, the resources allocated by the network device to the terminal device may be dynamically scheduled resources or pre-configured CG-SDT resources.

[0459] Optionally, the terminal device can continue to use the CG-SDT resources configured by the previous CG-SDT (for example, the resources configured by the CG-SDT in S1220 are the previously configured resources), that is, the network device can newly configure resources for the terminal device, or the terminal device can continue to use the CG-SDT resources configured by the previous CG-SDT, and the network device does not need to reconfigure resources.

[0460] Optionally, after receiving the first MAC CE on the CG-SDT resource, the network device determines not to end the current SDT.

[0461] S2306, the terminal device is in the RRC non-connected state, and the terminal device sends subsequent small data to the network device on the resources configured by the network device or the CG-SDT resources previously configured by CG-SDT.

[0462] Optionally, the subsequent small data may include small data in the buffer and subsequently arrived small data, and the number of subsequently arrived small data may be the number of data packets indicated by the number information of the data packets.

[0463] Optionally, after receiving subsequent small data, the network device may end the SDT.

[0464] Figure 24The first MAC CE is sent via RA-SDT, and the first MAC CE indicates a buffer status report and power headroom information, such as Figure 24 As shown, the method 2400 includes:

[0465] S2401, the terminal device is in an RRC non-connected state (for example, in the RRC_INACTIVE state), a data packet arrives at a higher layer of the terminal device (for example, the higher layer includes the RRC layer and / or the NAS layer), and the service corresponding to the arriving data packet is a single-shot transmission.

[0466] For example, the current service is a heartbeat packet.

[0467] S2402: The access stratum (AS) of the terminal device determines that the size of the received data packet is smaller than the small data size threshold and determines that the SDT process can be initiated. In other words, the service corresponding to the received data is a single-shot SDT transmission.

[0468] Optionally, the small data size threshold may be specified by a protocol or configured by a network device.

[0469] If CG-SDT is invalid, the terminal device determines to initiate RA-SDT.

[0470] S2403, the terminal device determines to send small data in message 3 or message A. When assembling the package or before assembling the package, the terminal device determines that it cannot complete the transmission of the current small data through message 3 or message A in one time, that is, there is still remaining small data in the buffer, and if the conditions for triggering the reporting of the buffer status report are met, the terminal device triggers the sending of the buffer status report to the network device. The buffer status report is used to indicate the amount of small data in the buffer.

[0471] Optionally, when assembling the packet, the terminal device determines that it is impossible to complete the transmission of the current small data through message 3 or message A once, including: when assembling the packet, the terminal device determines that there are insufficient resources to send message 3 or message A, resulting in the inability to transmit the current small data and the first MAC CE, so the remaining small data needs to be saved in the buffer.

[0472] Optionally, the terminal device triggers sending of a buffer status report, which triggers sending of a power headroom report.

[0473] S2404: The terminal device sends small data and a first MAC CE to the network device in message 3 or message A. The first MAC CE is used to indicate a status buffer report and a power headroom report.

[0474] Optionally, if small data and the first MAC CE are sent via message A, similar to S1120, message A may also include a preamble and an RRC request message. That is, if RA-SDT is performed, the first MAC CE, preamble, small data, and RRC request message may be sent via message A.

[0475] Optionally, if small data and the first MAC CE are sent via message 3, similar to S1040, message 3 may also include an RRC request message. That is, if RA-SDT is performed, the first MAC CE, small data, and RRC request message may be sent via message 3.

[0476] It is understood that, as an alternative to S2404, the terminal device sends the first MAC CE in message 3 or message A. That is, if resources for sending message 3 or message A are limited, the terminal device determines to send the first MAC CE in message 3 or message A and may not send the currently arriving small data. The currently arriving small data may be buffered, and the buffer status report may indicate the amount of data in the buffer.

[0477] S2405: After receiving the first MAC CE in message 3 or message A, the network device configures resources for the terminal device according to the buffer status report and power headroom report indicated by the first MAC CE.

[0478] Optionally, in S2405, the resources allocated by the network device to the terminal device may be dynamically scheduled resources or pre-configured CG-SDT resources.

[0479] Optionally, after receiving the first MAC CE in message 3 or message A, the network device determines not to end the current SDT.

[0480] S2406: The terminal device is in an RRC non-connected state (for example, in an RRC_INACTIVE state), and sends small data in the buffer to the network device on resources configured by the network device.

[0481] Optionally, after the network device receives the small data in the buffer, it may end the SDT.

[0482] Figure 25 In the embodiment, the first MAC CE is sent via CG-SDT, and the first MAC CE indicates the buffer status report and the power headroom information. Figure 25 As shown, method 2500 includes:

[0483] S2501, the terminal device is in an RRC non-connected state (for example, in an RRC_INACTIVE state), a data packet arrives at a higher layer of the terminal device (for example, the higher layer includes an RRC layer and / or a NAS layer), and the service corresponding to the arriving data packet is a single-shot transmission.

[0484] S2502: The access stratum (AS) of the terminal device determines that the size of the received data packet is smaller than the small data size threshold and determines that the SDT process can be initiated. In other words, the service corresponding to the received data is a single-shot SDT transmission.

[0485] Optionally, the small data size threshold may be specified by a protocol or configured by a network device.

[0486] If the CG-SDT is valid, the terminal device determines to initiate the CG-SDT. Alternatively, if the CG-SDT is valid and the RA-SDT is invalid, the terminal device determines to send the CG-SDT.

[0487] S2503, the terminal device determines to send small data on the resources indicated by the CG-SDT configuration. The terminal device determines in the package assembly that the current small data transmission cannot be completed through one CG-SDT resource, that is, there is still remaining small data in the buffer, and if the conditions for sending a buffer status report are met, the terminal device triggers the sending of a buffer status report to the network device. The buffer status report is used to indicate the amount of small data in the buffer.

[0488] Optionally, when assembling a packet, the terminal device determines that the transmission of the current small data cannot be completed through one CG-SDT resource, including: when assembling a packet, the terminal device determines that sending one CG-SDT resource is not enough to transmit the small data and the first MACCE once, resulting in the inability to transmit the current small data, and therefore the remaining small data needs to be saved in a buffer.

[0489] Optionally, the terminal device triggers sending of a buffer status report, which triggers sending of a power headroom report.

[0490] S2504: The terminal device sends small data and a first MAC CE to the network device on the CG-SDT resource. The first MAC CE is used to indicate a buffer status report and a power headroom report.

[0491] It is understood that, as an alternative to S2504, the terminal device sends the first MAC CE on the CG-SDT resources. That is, if the CG-SDT resources are limited, the terminal device may determine to send the first MAC CE on the CG-SDT resources and may not send the currently arriving small data. The currently arriving small data may be buffered, and the buffer status report may indicate the amount of small data in the buffer.

[0492] S2505: After receiving the first MAC CE on the CG-SDT resource, the network device configures resources for the terminal device according to the buffer status report and power headroom report in the first MAC CE.

[0493] Optionally, in S2505, the resources allocated by the network device to the terminal device may be dynamically scheduled resources or pre-configured CG-SDT resources.

[0494] Optionally, the terminal device can continue to use the CG-SDT resources configured by the previous CG-SDT (for example, the resources configured by the CG-SDT in S1220 are the previously configured resources), that is, the network device can newly configure resources for the terminal device, or the terminal device can continue to use the CG-SDT resources configured by the previous CG-SDT, and the network device does not need to reconfigure resources.

[0495] Optionally, after receiving the first MAC CE on the CG-SDT resource, the network device determines not to end the current SDT.

[0496] S2506: The terminal device is in the RRC non-connected state and sends small data in the buffer to the network device on the resources configured by the network device or the CG-SDT resources previously configured by CG-SDT.

[0497] Optionally, after the network device receives the small data in the buffer, it may end the SDT.

[0498] In an embodiment of the present application, the terminal device determines whether CG-SDT is valid by determining whether at least one of the following conditions is met.

[0499] Condition 1: TAT is running, that is, the TA of the terminal device is valid, and the terminal device and the network device are in uplink synchronization state, which means that CG-SDT is valid, otherwise it is invalid.

[0500] Condition 2: Under the premise of TAT operation, the current RSRP of the terminal device is greater than the preset RSRP 1. In other words, if the current RSRP of the terminal device is greater than the preset RSRP 1, it means that the terminal device is close to the network device and the channel quality is good. If CG-SDT is performed, the success rate is high and CG-SDT is effective. If the current RSRP is less than or equal to the preset RSRP 1, it means that the terminal device is far from the network device and the channel quality is poor. If CG-SDT is performed, the success rate is low. Among them, RSRP 1 can be configured by the network device for both CG-SDT and RA-SDT.

[0501] Condition three: If the increase or decrease in the RSRP of the terminal device does not exceed RSRP 2 during the preset time period when the last TA was valid, CG-SDT is valid. In other words, whether the terminal device has moved can be determined based on the increase or decrease in the RSRP of the terminal device. If the increase or decrease in RSRP is greater than or equal to RSRP 2, it means that the terminal device has moved or moved a large distance relative to the last time the TA was valid. If CG-SDT is used, the success rate is low and CG-SDT is invalid. On the contrary, if the increase or decrease in RSRP is less than RSRP 2, it means that the terminal device has not moved or moved a small distance relative to the last time the TA was valid. If CG-SDT is used, the success rate is high and CG-SDT is valid.

[0502] Condition four: If the network device configures CG-SDT on SUL and / or NUL, the terminal device needs to compare the current RSRP with the RSRP 3 threshold preset by the base station to determine whether the CG-SDT configured on SUL or the CG-SDT configured on NUL is valid. Assuming that CG-SDT is configured on both SUL and NUL, the terminal device compares the current RSRP with RSRP 3. If it is less than RSRP3, the CG-SDT on SUL is selected. If it is greater than RSRP 3, the CG-SDT on NUL is selected. That is to say, if the network device configures CG-SDT on both SUL and NUL, if the current RSRP of the terminal device is less than RSRP3, it means that the terminal device is far away from the network device and the CG-SDT configured on SUL should be used. In other words, the CG-SDT on SUL is valid and the CG-SDT on NUL is invalid. If the current RSRP of the terminal device is greater than or equal to RSRP 3, it means that the terminal device is close to the network device and the CG-SDT configured on the NUL should be used. That is, the CG-SDT on the NUL is valid and the CG-SDT on the SUL is invalid. Assuming that the network device only configures CG-SDT on SUL, the terminal device compares the current RSRP with RSRP 3. If the current RSRP is less than RSRP 3, the CG-SDT on SUL is selected. At this time, CG-SDT is valid. If the current RSRP is greater than or equal to RSRP 3, CG_SDT cannot be used, that is, CG-SDT on SUL is invalid. In other words, the network device is configured with CG-SDT on SUL. If the terminal device is relatively far away from the network device, the CG-SDT on SUL can be used. Otherwise, CG-SDT on SUL is invalid. Assuming that the network device only configures CG-SDT on NUL, the terminal device compares the current RSRP with RSRP 3. If the previous RSRP is less than RSRP 3, CG_SDT cannot be used. If the previous RSRP is greater than or equal to RSRP_3, CG_SDT on NUL is selected. That is, CG-SDT on NUL is valid. In other words, the network device is configured with CG-SDT on NUL. Only when the terminal device is relatively close to the network device can the CG-SDT on NUL be used, otherwise CG-SDT on NUL is invalid.

[0503] Condition five: The range where the terminal device is located is the range covered by the network device, and the network device has configured CG resources for CG-SDT for the terminal device.

[0504] It should be noted that in the embodiments of the present application, the subsequent small data may include small data in the buffer, or may include small data that arrives subsequently (or is subsequently transmitted), or may include small data in the buffer and small data that arrives subsequently (or is subsequently transmitted). In different embodiments, the content of the subsequent small data may be different. In the embodiments of the present application, "subsequent transmission" can be understood as small data that arrives subsequently, that is, "subsequent transmission" can be replaced by small data that arrives subsequently, and "small data that arrives subsequently" can be replaced by "subsequent transmission".

[0505] It should be noted that, in the embodiments of the present application, the terminal device triggering "sending" certain information can also mean that the terminal device triggers "indicating" certain information. For example, the AS layer of the terminal device triggering the sending of the number of data packets to the network device can also mean that the AS layer of the terminal device triggers the indicating of the number of data packets to the network device. In other words, in the embodiments of the present application, the terminal device sending a certain parameter to the network device can mean directly sending the parameter or indicating the parameter.

[0506] It should be noted that, in the embodiment of the present application, the first MAC CE does not include a certain indication field. There are two ways to understand this. In one way, if the format of the first MAC CE is fixed and the length is fixed, the first MAC CE does not include a certain indication field, indicating that the bit corresponding to the indication field is a reserved bit; in another way, if the format of the first MAC CE is not fixed and the length is variable, the first MAC CE does not include a certain indication field, indicating that the indication field does not exist, and the first MAC CE reduces the length of the indication field.

[0507] It should be noted that the small data in the embodiment of the present application can also be called small packet data.

[0508] It should also be noted that the embodiments of the present application only take the process interaction between the terminal device and the network device as an example. In actual applications, the embodiments of the present application can also be used in D2D scenarios, and the network device in the aforementioned embodiments can be replaced by another terminal device.

[0509] It is understandable that the execution order of the above method embodiments is not limited by the numbering, and the execution order can be determined according to the internal logic. As long as there is no contradiction, the execution order of the method can be changed.

[0510] It is understood that the above method embodiments can be independent embodiments or embodiments that can be combined with each other. Steps in different method embodiments can be combined with each other to form another embodiment, and steps in the same method embodiment can also be combined with each other to form another embodiment.

[0511] It can be understood that the methods and operations implemented by the terminal device in the above-mentioned method embodiments can also be implemented by components that can be used for the terminal device (such as chips or circuits), and the methods and operations implemented by the network device in the above-mentioned method embodiments can also be implemented by components that can be used for the network device (such as chips or circuits).

[0512] The above describes the method embodiments provided by this application, and the following describes the device embodiments provided by this application. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for matters not described in detail, reference can be made to the method embodiments above. For the sake of brevity, they will not be repeated here.

[0513] Figure 26 1 shows a communication device 2600 provided in an embodiment of the present application. The communication device 2600 includes a processor 2610 and a transceiver 2620. The processor 2610 and the transceiver 2620 communicate with each other via an internal connection path. The processor 2610 is used to execute instructions to control the transceiver 2620 to send and / or receive signals.

[0514] Optionally, the communication device 2600 may further include a memory 2630, which communicates with the processor 2610 and the transceiver 2620 via an internal connection path. The memory 2630 is used to store instructions, and the processor 2610 can execute the instructions stored in the memory 2630. In one possible implementation, the communication device 2600 is used to implement the various processes and steps corresponding to the terminal device in the above-mentioned method embodiment. In another possible implementation, the communication device 2600 is used to implement the various processes and steps corresponding to the network device in the above-mentioned method embodiment.

[0515] It should be understood that the communication device 2600 can be specifically a network device or terminal device in the above-mentioned embodiments, or a chip or chip system. Correspondingly, the transceiver 2620 can be the transceiver circuit of the chip, which is not limited here. Specifically, the communication device 2600 can be used to execute the various steps and / or processes corresponding to the network device or terminal device in the above-mentioned method embodiments. Optionally, the memory 2630 can include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory can also include non-volatile random access memory. For example, the memory can also store device type information. The processor 2610 can be used to execute instructions stored in the memory, and when the processor 2610 executes the instructions stored in the memory, the processor 2610 is used to execute the various steps and / or processes of the above-mentioned method embodiments corresponding to the network device or terminal device.

[0516] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0517] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0518] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0519] According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, it enables the computer to execute the various steps or processes executed by the network device or terminal device in the above method embodiment.

[0520] According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores program code. When the program code runs on a computer, the computer executes the various steps or processes performed by the terminal device or network device in the above method embodiment.

[0521] According to the method provided in the embodiment of the present application, the present application also provides a communication system, which includes one or more terminal devices and one or more network devices as mentioned above.

[0522] The above-mentioned various apparatus embodiments correspond completely to the method embodiments, and the corresponding modules or units perform the corresponding steps. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be based on the corresponding method embodiments. There can be one or more processors.

[0523] In this application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information is called information to be indicated. In the specific implementation process, there may be many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as indicating the information to be indicated itself or the index of the information to be indicated. The information to be indicated may also be indirectly indicated by indicating other information, wherein the other information is associated with the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information may be achieved by means of the arrangement order of each information agreed in advance (such as specified in the protocol), thereby reducing the indication overhead to a certain extent.

[0524] In the embodiments of this application, each term and English abbreviation is provided for convenience of description and shall not constitute any limitation to this application. This application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0525] It should be understood that the term "and / or" as used herein describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the associated objects.

[0526] Those skilled in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented using 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. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0527] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can be based on the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0528] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0529] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0530] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0531] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0532] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0533] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for acquiring resources, characterized in that: The method is applicable to a terminal device and includes: Sending a first media access control (MAC) element (CE) to the network device, where the first MAC CE is used to indicate at least two of a buffer status report (BSR), a power headroom report (PHR), or information about the number of data packets, where the BSR is used to indicate the amount of data in the buffer, the PHR is used to indicate the power headroom of the terminal device, and the information about the number of data packets is used to indicate the number of data packets to be subsequently transmitted; Acquire resources configured by the network device according to the first MAC CE; Among them, the MAC subheader corresponding to the first MAC CE is a first MAC subheader, and the first MAC subheader includes an eighth indication field. The bits carried by the eighth indication field are used to indicate that the value of the logical channel identifier LCID corresponding to the first MAC CE is a first value, and the first value is used to indicate that the first MAC CE is used to indicate at least two of the buffer status report, the power headroom report or the quantity information of the data packet.

2. The method according to claim 1, characterized in that If the first MAC CE is used to indicate the buffer status report, the bits carried by the first indication field included in the first MAC CE are used to indicate the buffer status report; if the first MAC CE is used to indicate the power headroom report, the bits carried by the second indication field included in the first MAC CE are used to indicate the power headroom report; if the first MAC CE is used to indicate the quantity information of the data packets, the bits carried by the third indication field included in the first MAC CE are used to indicate the quantity information of the data packets.

3. The method according to claim 2, characterized in that The first MAC CE includes a fourth indication field, and the bits carried by the fourth indication field are used to indicate whether the first MAC CE includes the first indication field.

4. The method according to claim 2, characterized in that The first MAC CE includes a fifth indication field, and the bits carried by the fifth indication field are used to indicate the type of buffer status report indicated by the bits carried by the first indication field.

5. The method according to claim 2, characterized in that The first MAC CE includes a sixth indication field, and the bits carried by the sixth indication field are used to indicate whether the first MAC CE includes the second indication field.

6. The method according to claim 2, characterized in that The first MAC CE includes a seventh indication field, and the bits carried by the seventh indication field are used to indicate whether the first MAC CE includes the third indication field.

7. The method according to any one of claims 1 to 6, characterized in that The sending a first MAC CE to the network device includes: If it is determined that there is small packet data in the buffer, sending the first MAC CE to the network device, where the first MAC CE is used to indicate the buffer status report and the power headroom report, and the buffer status report is used to indicate the amount of small packet data in the buffer; or If it is determined that there is subsequent transmission, sending the first MAC CE to the network device, where the first MAC CE is used to indicate the quantity information of the data packets and the power headroom report, and the quantity information of the data packets is used to indicate the quantity of data packets of the small packet data to be subsequently transmitted; or When it is determined that there is small packet data in the buffer and that there is subsequent transmission, the first MAC CE is sent to the network device, where the first MAC CE is used to indicate the buffer status report, the quantity information of the data packets and the power headroom report, the buffer status report is used to indicate the amount of small packet data in the buffer, and the quantity information of the data packets is used to indicate the number of data packets of the small packet data to be transmitted subsequently.

8. The method according to any one of claims 1 to 6, characterized in that The terminal device is in a radio resource control (RRC) non-connected state, and the sending of a first MAC CE to the network device includes: Sending the first MAC CE to the network device through a random access procedure; or The first MAC CE is sent to the network device through preconfigured resources.

9. The method according to any one of claims 1 to 6, characterized in that The acquiring of resources configured by the network device according to the first MAC CE includes: Acquire resources scheduled by the network device through first downlink control information DCI according to the first MAC CE; or, Acquire pre-configured resources configured by the network device according to the first MAC CE; or, The pre-configured resources configured in advance by the network device are used as resources configured by the network device according to the first MAC CE.

10. The method according to any one of claims 1 to 6, characterized in that The data packet quantity information is further used to indicate the quantity of data packets to be received. The method further includes: The terminal device receives a second DCI from the network device, where the second DCI is used to indicate a resource for the terminal device to receive downlink data; The terminal device receives downlink data from the network device on the resource for receiving downlink data.

11. A method for obtaining resources, characterized in that: The method is applicable to a network device, including: receiving a first media access control (MAC) element (CE) from a terminal device, where the first MAC CE is used to indicate at least two of a buffer status report (BSR), a power headroom report (PHR), or information about the number of data packets, wherein the BSR is used to indicate an amount of data in a buffer, the PHR is used to indicate a power headroom of the terminal device, and the information about the number of data packets is used to indicate a number of data packets to be subsequently transmitted by the terminal device; configuring resources for the terminal device according to the first MAC CE; Among them, the MAC subheader corresponding to the first MAC CE is a first MAC subheader, and the first MAC subheader includes an eighth indication field. The bits carried by the eighth indication field are used to indicate that the value of the logical channel identifier LCID corresponding to the first MAC CE is a first value, and the first value is used to indicate that the first MAC CE is used to indicate at least two of the buffer status report, the power headroom report or the quantity information of the data packet.

12. The method according to claim 11, characterized in that If the first MAC CE is used to indicate the buffer status report, the bits carried by the first indication field included in the first MAC CE are used to indicate the buffer status report; if the first MAC CE is used to indicate the power headroom report, the bits carried by the second indication field included in the first MAC CE are used to indicate the power headroom report; if the first MAC CE is used to indicate the quantity information of the data packets, the bits carried by the third indication field included in the first MAC CE are used to indicate the quantity information of the data packets.

13. The method according to claim 12, characterized in that The first MAC CE includes a fourth indication field, and the bits carried by the fourth indication field are used to indicate whether the first MAC CE includes the first indication field.

14. The method according to claim 12, characterized in that The first MAC CE includes a fifth indication field, and the bits carried by the fifth indication field are used to indicate the type of buffer status report indicated by the bits carried by the first indication field.

15. The method according to claim 12, characterized in that The first MAC CE includes a sixth indication field, and the bits carried by the sixth indication field are used to indicate whether the first MAC CE includes the second indication field.

16. The method according to claim 12, characterized in that The first MAC CE includes a seventh indication field, and the bits carried by the seventh indication field are used to indicate whether the first MAC CE includes the third indication field.

17. The method according to any one of claims 11 to 16, characterized in that The receiving a first MAC CE from the terminal device includes: receiving the first MAC CE from the terminal device through a random access procedure of the terminal device; or The first MAC CE is received from the terminal device through preconfigured resources.

18. The method according to any one of claims 11 to 16, characterized in that The configuring resources for the terminal device according to the first MAC CE includes: Scheduling resources for the terminal device through a first DCI according to the first MAC CE; or, configuring corresponding pre-configured resources for the terminal device according to the first MAC CE; or, The pre-configured resources configured in advance for the terminal device are used as the resources configured for the terminal device according to the first MAC CE.

19. The method according to any one of claims 11 to 16, characterized in that The buffer status report is used to indicate the amount of small packet data in the buffer, and the data packet quantity information is used to indicate the number of data packets of the small packet data to be subsequently transmitted.

20. The method according to claim 19, wherein The method further comprises: After receiving the first MAC CE, determining not to end the transmission of the packet data with the terminal device; If the first MAC CE is used to indicate the buffer status report and / or the quantity information of the data packets, then after receiving the amount of data in the buffer indicated by the buffer status report, and / or the number of data packets to be sent indicated by the quantity information of the data packets, the transmission of the small packet data between the terminal device is terminated.

21. The method according to any one of claims 11 to 16, characterized in that The data packet quantity information is further used to indicate the quantity of data packets to be received. The method further includes: Sending a second DCI to the terminal device, where the second DCI is used to indicate resources for the terminal device to receive downlink data; The network device sends downlink data to the terminal device on the resource where the terminal device receives downlink data.

22. A communication device, characterized in that: comprising a processor for executing the method according to any one of claims 1 to 21.

23. A computer-readable storage medium, characterized in that A program or instruction for implementing the method according to any one of claims 1 to 21 is stored.

Images