WO2023108476A1

WO2023108476A1 - Communication method and apparatus

Info

Publication number: WO2023108476A1
Application number: PCT/CN2021/138314
Authority: WO
Inventors: 尤心; 林雪; 刘洋
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-12-15
Filing date: 2021-12-15
Publication date: 2023-06-22
Also published as: CN118104357A

Abstract

Embodiments of the present application provide a communication method and apparatus. The method comprises: a terminal device sends a first message to a network device, wherein the first message comprises first information recording small data transmission (SDT). The terminal device reports to the network device the first message comprising the first information for the SDT, so that the network device can optimize SDT configuration according to the first message, thereby effectively increasing the success rate of the SDT process.

Description

Communication method and device

technical field

The present application relates to the communication field, and in particular to a communication method and device.

Background technique

In the field of communication, for terminal equipment (User Equipment, UE) with small amount of data and low transmission frequency, in order to avoid unnecessary power consumption and signaling consumption, the research of Small Data Transmission (SDT) is currently proposed .

Currently, the network device can configure a CG (configured grant, configuration authorization) resource for the terminal device, so as to support the terminal device to execute the SDT process based on the CG resource. When performing SDT, the terminal device usually needs to select a carrier and a beam. If there are CG resources configured by the network device on the carrier and beam selected by the terminal device, the terminal device can execute the SDT process.

However, when the CG resource configured by the network device is inappropriate, there will be no CG resource on the carrier and beam selected by the terminal device, which will lead to a low success rate of the SDT process.

Contents of the invention

Embodiments of the present application provide a communication method and device to improve the success rate of the SDT process.

In the first aspect, the embodiment of the present application provides a communication method, including:

The terminal device sends a first message to the network device, where the first message includes first information recording small data transmission.

In a second aspect, the embodiment of the present application provides a communication device, including:

A sending module, configured for the terminal device to send a first message to the network device, wherein the first message includes first information recording small data transmission.

In a third aspect, an embodiment of the present application provides a terminal device, including: a transceiver, a processor, and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the communication method as described in the first aspect above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the above-mentioned first aspect. the communication method described above.

In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, wherein, when the computer program is executed by a processor, the communication method described in the first aspect above is implemented.

An embodiment of the present application provides a communication method and device, and the method includes: a terminal device sends a first message to a network device, where the first message includes first information recording small data transmission. The terminal device reports the first message including the first information of the small data transmission to the network device, so that the network device can optimize the SDT configuration according to the first message, thereby effectively improving the success rate of the SDT process.

Description of drawings

FIG. 1 is a schematic diagram of an uplink provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a communication scenario provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of the implementation of the SDT process based on the random access process provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of the implementation of the SDT process based on pre-configured resources provided by the embodiment of the present application;

FIG. 5 is a signaling flowchart of an ad hoc network provided by an embodiment of the present application;

FIG. 6 is a flowchart of a communication method provided by an embodiment of the present application;

FIG. 7 is a second flow chart of the communication method provided by the embodiment of the present application;

FIG. 8 is a first schematic diagram of implementation of resource selection by a terminal device provided in an embodiment of the present application;

FIG. 9 is a schematic diagram 2 of realizing resource selection by a terminal device according to an embodiment of the present application;

FIG. 10 is a schematic diagram 3 of realizing resource selection by a terminal device according to an embodiment of the present application;

FIG. 11 is a flowchart three of the communication method provided by the embodiment of the present application;

FIG. 12 is a schematic diagram 4 of realizing resource selection by a terminal device according to an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 14 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

In order to better understand the technical solutions of the present application, the related technologies involved in the present application will be further introduced in detail below.

For ease of understanding, the concepts involved in this application are explained first.

Terminal device: It can be a device that includes wireless transceiver functions and can cooperate with network devices to provide users with communication services. Specifically, the terminal equipment may refer to user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber 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, User Agent or User Device. For example, a terminal device may 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 wireless Handheld devices with communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in future 5G networks or networks after 5G, etc.

Network equipment: Network equipment can be equipment used to communicate with terminal equipment, for example, it can be a global system for mobile communication (Global System for Mobile Communication, GSM) or code division multiple access (Code Division Multiple Access, CDMA) communication system The base station (Base Transceiver Station, BTS), also can be the base station (NodeB, NB) in the Wideband Code Division Multiple Access (WCDMA) system, can also be the evolved type base station (Evolutional Node) in the LTE system B, eNB or eNodeB), or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network side device in a future 5G network or a network after 5G or a future evolved public land mobile network (Public Land Mobile Network, PLMN) network equipment in the network, etc.

The network device involved in the embodiment of the present application may also be called a radio access network (Radio Access Network, RAN) device. The RAN device is connected with the terminal device, and is used to receive the data of the terminal device and send it to the core network device. RAN equipment corresponds to different equipment in different communication systems, for example, in the 2G system, it corresponds to the base station and the base station controller, in the 3G system, it corresponds to the base station and the radio network controller (Radio Network Controller, RNC), and in the 4G system, it corresponds to the evolution Evolutionary Node B (eNB), which corresponds to the 5G system in the 5G system, such as the access network equipment (such as gNB, centralized unit CU, distributed unit DU) in New Radio (NR).

Beam: The embodiment of the beam in the NR protocol can be a spatial filter, or a spatial filter or spatial parameters. The beam used to transmit signals may be called a transmission beam (transmission beam, Tx beam), may be called a spatial domain transmit filter (spatial domain transmit filter) or a spatial domain transmit parameter (spatial domain transmit parameter); the beam used to receive signals may be called It is a reception beam (Rx beam), which can be called a spatial domain receive filter (spatial domain receive filter) or a spatial domain receive parameter (spatial domain receive parameter).

For example, a beam can be understood as a space resource, and can refer to a transmission or reception precoding vector with energy transmission directivity. Moreover, the sending or receiving precoding vector can be identified by index information, and the index information can correspond to a resource identifier (identity, ID) configured for the terminal, for example, the index information can correspond to a configured synchronization signal block (synchronization signal Block, SSB) identification or resource; also can correspond to the configuration of the channel state information reference signal (channel state information reference signal, CSI-RS) identification or resource; also can be the corresponding configured uplink sounding reference signal (sounding reference signal, SRS) identifier or resource. Optionally, the index information may also be index information explicitly or implicitly carried by a signal carried by a beam or by a channel. The energy transmission directivity may refer to precoding the signal to be sent through the precoding vector, the precoding signal has a certain spatial directivity, and receiving the precoding vector through the precoding vector The signal has better received power, such as satisfying the receiving demodulation signal-to-noise ratio, etc.; the energy transmission directivity may also mean that the same signal transmitted from different spatial positions received through the precoding vector has different received power. Optionally, the same communication device (such as a terminal device or network device) may have different precoding vectors, and different devices may also have different precoding vectors, that is, corresponding to different beams. Regarding the configuration or capability of the communication device, one communication device may use one or more of multiple different precoding vectors at the same time, that is, it may form one beam or multiple beams at the same time.

It can be understood that, the embodiment of the beam in the NR protocol listed above is only an example, and should not constitute any limitation to the present application. This application does not exclude the possibility of defining other terms to represent the same or similar meanings in future agreements.

Additionally, the beams may be wide beams, or narrow beams, or other types of beams. The beamforming technique may be beamforming technique or other techniques. Specifically, the beamforming technology may be a digital beamforming technology, an analog beamforming technology, or a hybrid digital/analog beamforming technology, and the like. Different beams can be considered as different resources. The same information or different information can be transmitted through different beams.

NUL: Among them, the uplink (UpLink, UL) refers to the physical channel of the signal from the terminal device to the network device, and the normal uplink is the normal uplink (Normal UpLink, NUL).

SUL: Among them, Supplementary Uplink (Supplementary UpLink, SUL) is a supplementary uplink. The frequency band used by SUL is lower than that used by NUL, and the coverage of SUL is larger than that of NUL. For example, it can be understood in conjunction with Figure 1. Figure 1 1 is a schematic diagram of the uplink provided by the embodiment of this application.

As shown in Figure 1, both NUL and SUL are uplinks, and the coverage of SUL is larger than that of NUL. Among them, the frequency of SUL is lower, and the signal loss is smaller, which can ensure the coverage of NUL.

Below, with reference to FIG. 2 , the applicable scenarios of the communication method in this application will be described.

FIG. 2 is a schematic diagram of a communication scenario provided by an embodiment of the present application. Please refer to FIG. 2 , including a network device 201 and a terminal device 202, wireless communication can be performed between the network device 201 and the terminal device 202, wherein the terminal device 202 can communicate with at least one core via a radio access network (Radio Access Network, RAN) network for communication.

Among them, the communication system can be Global System of Mobile communication (GSM for short) system, Code Division Multiple Access (CDMA for short) system, Wideband Code Division Multiple Access (Wideband Code Division Multiple Access for short) WCDMA) system, Long Term Evolution (LTE for short) system or 5th-Generation (5G for short) system.

Correspondingly, the network equipment can be a base station (Base Transceiver Station, referred to as BTS) in the GSM system or a CDMA system, or a base station (NodeB, referred to as NB) in a WCDMA system, or an evolved base station in an LTE system. (evolved NodeB, eNB for short), access point (access point, AP) or relay station, or a base station in the 5G system, etc., which are not limited here.

The 5G mobile communication system described in this application includes a non-standalone (NSA) 5G mobile communication system and/or a standalone (standalone, SA) 5G mobile communication system. The technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The communication system may also be a PLMN network, a device-to-device (device-to-device, D2D) network, a machine-to-machine (machine to machine, M2M) network, an IoT network, or other networks.

It can be understood that, if the technical solutions of the embodiments of the present application are applied to other wireless communication networks, corresponding names may also be replaced with names of corresponding functions in other wireless communication networks.

The network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application. For the evolution of architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

On the basis of the above introduction, the relevant technical background of the application is described below:

In the 5G NR system, there are three RRC states, namely: RRC_IDLE (RRC idle state), RRC_INACTIVE (RRC inactive state), and RRC_CONNECTED (RRC connected state).

The RRC_INACTIVE state is a new state introduced by the 5G system from the perspective of energy saving. For the UE in the RRC_INACTIVE state, the radio bearer and all radio resources will be released, but the UE side and the base station side retain the UE access context to quickly restore the RRC connection. Typically, UEs with infrequent data transmission are kept in the RRC_INACTIVE state.

Before Rel-16, the UE in the RRC_INACTIVE state does not support data transmission. When the uplink (Mobile Original, MO) or downlink (Mobile Terminated, MT) data arrives, the UE needs to restore the connection and release it to the INACTIVE state after the data transmission is completed. . For UEs with small amount of data and low transmission frequency, such a transmission mechanism will cause unnecessary power consumption and signaling overhead.

Therefore, Rel-17 set up a project to carry out research on Small Data Transmission (SDT) under RRC_INACTIVE. The project goals mainly have two directions: uplink small data transmission based on random Uplink small data transmission of pre-configured resources (such as CG type1), where the two types of small data transmission are introduced separately below.

Among them, in the uplink small data transmission process based on the random access process (two-step/four-step), the UE can perform data transmission in the random access process (such as the four-step random access process (4-step RACH), namely A UE in a non-connected state (that is, an idle state or an inactive state) can complete data transmission without RRC state switching.

In the SDT process based on the random access process, the UE may always remain in the idle state (idle) or suspend state (suspend) or inactive state (inactive) to complete the transmission of uplink and/or downlink small data packets, for example, it can It can be understood in conjunction with FIG. 3 , which is a schematic diagram of an implementation of an SDT process based on a random access process provided in an embodiment of the present application.

Wherein, the SDT process, for example, can be completed in a random access (random access, RA) process, referring to Fig. 3:

1. The UE can send a random access preamble (random access preamble) to the eNB.

Wherein, the random access preamble may also be referred to as a random access preamble sequence, or a preamble, or a preamble sequence.

In a possible implementation manner, the random access preamble and the time-frequency resources occupied by sending the random access preamble are called physical random access channel (physical random access channel, PRACH) resources.

Optionally, the terminal device may select a PRACH resource and select a preamble, and send the selected preamble on the selected PRACH resource. If the random access method is non-contention-based random access, the network device can specify the PRACH resource and preamble, and the network device can estimate the timing advance (timing advance, TA) based on the preamble sent by the terminal device, and the terminal device transmits The uplink authorization size required by Msg3. For example, a network device may broadcast available PRACH resources through system information.

2. The eNB can send a random access response (random access response, RAR) to the UE.

Among them, RAR can include the following information:

The subheader of the RAR includes a back-off indicator (BI), which is used to indicate the back-off time for retransmitting the Msg1.

RAPID in RAR: The preamble index received by the network response.

The RAR payload (payload) contains a timing advance group (timing advance group, TAG), which is used to adjust the uplink timing.

Uplink (up link, UL) grant: used to schedule the uplink resource indication of Msg3.

Temporary cell radio network temporary identifier (C-RNTI): used to scramble the PDCCH of Msg4.

If the terminal device receives the PDCCH scrambled by the RAR-RNTI, and the RAR contains the preamble index sent by itself, the terminal device considers that it has successfully received the random access response.

For random access based on non-contention, after the terminal device successfully receives Msg2, the random access process ends. For contention-based random access, after successfully receiving Msg2, the terminal device needs to continue to transmit Msg3 and receive Msg4.

3. The UE may send an RRC Connection Resume Request (RRCConnectionResumeRequest) to the eNB.

Among them, the RRC connection recovery request includes: recovery ID (resumeID), recovery reason (signaling initiated by the terminal, data originated by the terminal, abnormal data originated by the terminal or terminal call terminated) and short message integrity authentication Code (ShortResumeMAC-I) and other information.

At the same time, the UE can send uplink data (Uplink data) while sending the RRC connection recovery request.

4. The eNB may send an RRC connection release message (RRCConnectionRelease) to the UE.

The RRC connection release message may include: release cause (releaseCause), resume ID (resumeID), and network color code (Network Color Code, NCC).

At the same time, the eNB can send downlink data (Downlink data) while sending the RRC connection release message.

It can be understood that after the eNB sends the RRC connection release message to the UE, the UE can enter the inactive state (inactive), so for the SDT process described above, the UE does not actually enter the connection state, and the small data packet is completed. transmission.

It can be understood that the embodiment of the SDT process at the media access control layer (media access control, MAC) layer mainly affects the random access process. According to the original random access process, message 1 (Msg1) sends a preamble (preamble) for timing advance (timing advance, TA) measurement and request, and message 2 (Msg2) allocates uplink grant (UL grant) and TA , the message 3 (Msg3) carries on the transmission of the uplink common control channel (common control channel, CCCH), generally in this case it is the RRC connection establishment request or the RRC connection recovery request, and the message 4 (Msg4) carries out contention resolution. In the SDT based on the random access process, since data transmission without state transition is required, user data is directly sent in Msg3, and downlink data can be sent in Msg4.

In terms of configuration, the network will configure a maximum transmission block size (TB size) that the current network allows transmission on SIB2, where SIB is (system information block, system information block), and the UE can determine the amount of data to be transmitted, for example, If it is smaller than the maximum TB size of this broadcast, the UE can initiate SDT transmission; otherwise, the UE uses the normal connection establishment process and enters the connected state to transmit data.

Therefore, SDT can transmit small data (such as automatic reporting of water meters, etc.) through a simple signaling process for UEs in a non-connected state (ie idle state or inactive state) to avoid RRC state changes and RRC Signaling overhead.

The above describes the SDT process based on the random access process in conjunction with FIG. 3 . The SDT process based on the preconfigured resource is introduced below. For example, the UE can use the preconfigured uplink resource (Preconfigured Uplink Resource, PUR) for data transmission.

Among them, PUR is a resource configured by the network device for the terminal device, which is only valid in the currently configured cell, that is, when the UE detects a cell change and initiates random access in the new cell, the UE needs to release the PUR configured in the original cell .

It can be understood that the SDT based on pre-configured resources is similar to the EDT process based on random access described above, except that the process of sending a random access preamble to obtain TA and UL grant (uplink authorization) is omitted.

The process of data transmission using PUR can be understood in conjunction with FIG. 4 . FIG. 4 is a schematic diagram of the implementation of the SDT process based on pre-configured resources provided by the embodiment of the present application.

Referring to Figure 4, if the UE has valid PUR resources, the UE can directly send an RRC connection recovery request to the eNB, and the RRC connection recovery request includes information such as recovery ID, recovery reason, and short message integrity authentication code. At the same time, the UE can send uplink data while sending the RRC connection recovery request.

Afterwards, the eNB may send an RRC connection release message to the UE, and the RRC connection release message may include: release reason, recovery ID, and NCC. At the same time, the eNB can send downlink data and a timing advance command (Time Advance Command, TAC) while sending the RRC connection release message.

Therefore, as long as there are valid PUR resources in the UE, the UE can perform data transmission based on the PUR resources. An important prerequisite for the UE to perform data transmission using PUR is to have an effective timing advance (Time Advance, TA).

Here is a brief introduction to TA. An important feature of uplink transmission is the time-frequency orthogonal multiple access (orthogonal multiple access) of different UEs, that is, the uplink transmissions of different UEs from the same cell do not interfere with each other.

In order to ensure the orthogonality of uplink transmission and avoid intra-cell interference, the eNodeB requires that signals from different UEs in the same subframe but with different frequency domain resources (different RBs) arrive at the eNodeB to be basically aligned. As long as the eNodeB receives the uplink data sent by the UE within the scope of the CP (Cyclic Prefix), it can correctly decode the uplink data. Therefore, uplink synchronization requires that the signals from different UEs in the same subframe arrive at the eNodeB before the CP. Inside.

In order to ensure time synchronization on the receiving side (eNodeB side), LTE proposes a timing advance (Timing Advance) mechanism.

From the perspective of the UE side, TA is essentially a negative offset (negative offset) between the start time of receiving the downlink subframe and the time of transmitting the uplink subframe. By appropriately controlling the offset of each UE, the eNodeB can control the time when uplink signals from different UEs arrive at the eNodeB. For a UE that is farther away from the eNodeB, due to a larger transmission delay, it needs to send uplink data earlier than a UE that is closer to the eNodeB.

Specifically, the UE can receive TAC from the network device side, where TCA is a timing advance command, and the eNB informs the UE of the timing advance (TA) time by sending TAC to the UE, where TA is the specified timing advance, generally used For the UE's uplink transmission, in order to get the UE's uplink packet to reach the eNB at the desired time, estimate the radio frequency transmission experiment caused by the distance, and send the data packet in advance of the corresponding time.

Therefore, the UE can adjust the transmission time of uplink data based on the TAC. The purpose is to eliminate different transmission delays between UEs, align the arrival times of uplink signals of different UEs at the eNB, ensure uplink orthogonality, and reduce intra-cell interference.

Based on the above introduction, it can be determined that an important prerequisite for the UE to perform data transmission using PUR is to have a valid TA. According to the protocol, the conditions for judging whether the TA is valid include at least one of the following:

- TA timer (Timing Advance timer, TAT) is running; and/or

- Reference Signal Receiving Power (RSRP) change (increase or decrease) is not greater than/less than the set threshold;

Wherein, the configuration of the TAT, as a part of the PUR configuration, can be sent to the UE through the RRCConnectionRelease message.

Based on the above introduction, it can be determined that the UE in the RRC_INACTIVE state can execute SDT. In a possible implementation, the UE needs to meet certain trigger conditions to execute SDT. Specifically, the UE triggers SDT only when the following conditions are met:

-The data to be transmitted comes from radio bearers that can trigger SDT, such as Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB);

-The amount of data to be transmitted is less than the pre-configured data amount threshold of the network device;

- The downlink RSRP measurement result is greater than the pre-configured RSRP threshold of the network device;

- There is a valid SDT resource, eg RA-SDT resource and/or CG-SDT resource.

Wherein, the RA-SDT resource is the resource when the SDT is executed based on the random access process, and the CG-SDT resource is the resource when the SDT is executed based on the pre-configured resource.

At the same time, it should be noted that if the terminal device is configured with RA-SDT resources and CG-SDT resources at the same time, the terminal device will first determine whether the CG-SDT resource is valid. The conditions for determining whether the CG-SDT resource is valid are explained below , the judgment conditions include:

-There is a valid TA, and the judging method includes: SDT-TAT is in the running state, and/or, the RSRP variation does not exceed the pre-configured threshold;

- CG-SDT resources exist on the carrier (NUL or SUL) selected by the terminal device;

- There is a CG-SDT resource on the SSB selected by the terminal device;

If the terminal device determines that the judgment conditions introduced above cannot be satisfied, the terminal device can determine that there is no available CG-SDT resource at present, and then the terminal device can further judge whether the RA-SDT resource is valid. If it is valid, the terminal device can initiate an RA-SDT resource. SDT process, otherwise, initiate the RRC resume (recovery) process.

At the same time, it should be noted that during the SDT process, if the terminal device determines that the following events occur, it will consider the SDT to fail and enter the RRC_IDLE state:

- Cell reselection occurs during SDT;

-SDT failure detection timer (failure detection timer) timeout

-The radio link control layer (Radio Link Control, RLC) reaches the maximum number of transmissions, that is, RLC failure is detected.

The above introduces the relevant content of small data transmission, and then introduces SON (Self-Organizing Network, Self-Organizing Network) below.

SON (Self-Organizing Network, Self-Organizing Network) is a complete set of network concepts and norms derived with the development of the network. The main idea of SON is to realize some autonomous functions of the wireless network to reduce manual participation and reduce operating costs. Specifically, the SON can optimize the network parameter configuration according to the information reported by the terminal, and its signaling flow can be shown in FIG. 5 . FIG. 5 is a signaling flow chart of the ad hoc network provided by the embodiment of the present application.

As shown in Figure 5:

1. The network device sends the report information to the UE in the connected state, where the report information may be, for example, UEInformationRequest, and the report information UEInformationRequest may include the type of information that the network device needs the terminal device to report, for example, ra-ReportReq (random access report ), rlf-ReportReq (radio link failure report), etc., each of which has its own corresponding parameter field. Taking ra-ReportRequest as an example, when the parameter field of this parameter is set to true, it means that the network device needs the terminal device to report information related to the random result process.

2. The UE feeds back the corresponding type of report to the network device through the response message UEInformationResponse according to the instruction of the network device.

It can be understood that, according to different events, the terminal device may trigger and record the above-mentioned various types of reports. Taking ra-Report as an example, after each successful random access, the UE may, for example, store the random access procedure information in the VarRA-Report list maintained by the UE. When receiving the reporting request described above from the network side, the recorded random access report is reported to the network.

Based on the relevant content introduced above, the problems existing in the related technologies are explained below:

When performing SDT, the terminal device usually needs to select a carrier and a beam. If there are CG resources configured by the network device on the carrier and beam selected by the terminal device, the terminal device can execute the SDT process. However, when the CG resource configured by the network device is inappropriate, there will be no CG resource on the carrier and beam selected by the terminal device, which will lead to a low success rate of the SDT process.

Based on the problems in the prior art, this application proposes the following technical idea: because the small data transmission is a new feature introduced by R17, the SON framework of R17 and before does not support the problem reporting for SDT. Therefore, in order to optimize the SDT process, in the subsequent version of the SON research, it is necessary to add SDT process records and reports, so that network devices can optimize the SDT configuration according to the SDT-related information reported by the terminal equipment, so as to improve the SDT process. Success rate.

On the basis of the above introduction content, the communication method provided by the present application will be introduced below in combination with specific embodiments. Firstly, it will be described in conjunction with FIG. 6 , which is a flow chart of the communication method provided in the embodiment of the present application.

As shown in Figure 6, the method includes:

S601. The terminal device sends a first message to the network device, where the first message includes first information recording small data transmission.

In this embodiment, the terminal device may send first information to the network device, where the first information includes the first information recording the transmission of small data, that is to say, the terminal device may report the first information related to small data transmission to the network device. A piece of information, so that the network device can optimize the subsequent SDT configuration.

In a possible implementation, the terminal device can send the first information to the network device by itself, for example, it can report regularly with a preset time period, or it can also send the first information to the network device at the end of each small data transmission. Report the first information to the network device.

In another possible implementation manner, the terminal device may also send the first information to the network device when receiving the request message sent by the network device, where, for example, the request message sent by the network device may include the first information type, to instruct the terminal device to send the first information recording small data transmission to the network device.

And, the terminal device may also store the recorded first information locally, so as to send it to the network device in a subsequent process.

The communication method provided by the embodiment of the present application includes: the terminal device sends a first message to the network device, where the first message includes first information recording small data transmission. The terminal device reports the first message including the first information of the small data transmission to the network device, so that the network device can optimize the SDT configuration according to the first message, thereby effectively improving the success rate of the SDT process.

On the basis of the foregoing embodiments, it should be further noted that, if the terminal device wants to send the first message to the network device, the terminal device needs to first record the first information of the small data transmission. In a possible implementation manner, the terminal device may record the first information when at least one of the following preset events is met:

A first type of event, the first type of event is used to indicate that no CG resource is configured on the resource selected by the terminal device;

The second type of event, the second type of event is used to indicate that the resource selected by the terminal device is configured with a CG resource, and during the small data transmission process, the CG resource is invalid.

The resource selected by the terminal device may include a carrier and a beam. It can be understood that, when uplink data arrives, the terminal device needs to select a carrier and a beam in order to transmit the uplink data. The first type of event described above means that no CG resource is configured on the resource selected by the terminal device, and the second type of event described above means that the resource selected by the terminal device is configured with a CG resource, then the terminal device will Small data transmission is performed, but the CG resource is invalid during the subsequent small data transmission.

It can be understood that no matter whether it is the above-mentioned first type event or the second type event, the terminal device will not have available CG resources to implement the SDT process based on pre-configured resources. The CG resource in this embodiment is that the network device is the terminal Resources pre-configured by the device to execute the SDT process. Then, when the above-mentioned first-type event and/or second-type event occurs, it may be because the CG resources configured by the network device are not suitable, resulting in no available CG-SDT resources for the terminal device, then the terminal device can The first information of the small data transmission is recorded and reported to the network device, so that the network device optimizes the CG-SDT resource configuration.

Situations corresponding to the first type of event and the second type of event are respectively described below.

For example, the situation corresponding to the first type of event may first be described in conjunction with FIG. 7 to FIG. 10. FIG. 7 is the second flow chart of the communication method provided by the embodiment of the application, and FIG. 8 is the resource selection process of the terminal device provided by the embodiment of the application. Implementation schematic diagram 1, FIG. 9 is an implementation schematic diagram 2 of resource selection by a terminal device provided in an embodiment of the present application, and FIG. 10 is a schematic diagram 3 implementation of resource selection by a terminal device provided in an embodiment of the present application.

As shown in Figure 7, the method includes:

S701. The terminal device receives an RRC connection release message sent by the network device, and switches to an RRC inactive state according to the RRC connection release message.

In this embodiment, for example, the terminal device may receive the RRC connection release message sent by the network side, and enter the RRC inactive state with the RRC connection release message. It can be understood that, in this embodiment, the recording of the first information for small data transmission is determined by the terminal device in the RRC inactive state.

S702. The terminal device determines that there is small data to be sent.

When uplink data arrives, the terminal device can determine that there is currently data to be sent, and because the current terminal device is in the RRC inactive state, the terminal device can, for example, determine whether the above-mentioned conditions for initiating the SDT process are met, and then determine Whether to execute the SDT process subsequently.

In a possible implementation, if the terminal device determines that the amount of data to be transmitted is less than the pre-configured data volume threshold of the network device, the terminal device may determine that there is small data to be sent, and for the remaining conditions for triggering SDT described above, the terminal The device also needs to judge whether it is satisfied.

Based on the above introduction, it can be determined that among the conditions for triggering SDT, there is a condition that "valid SDT resources exist", and based on the above introduction, it can be determined that if the terminal device is configured with RA-SDT resources and CG- SDT resource, the terminal device first determines whether the CG-SDT resource is valid.

Wherein, the CG resource is configured for the network device, and in this embodiment, the CG resource is configured on the first carrier and at least one first beam, where the first carrier may be a NUL beam, or may also be a SUL beam, This embodiment does not limit this.

S703. When determining that the first type of event is satisfied, the terminal device records the first reported information of the small data transmission.

In one possible situation, if the terminal device currently determines that there are no available CG-SDT resources, it may record the first information of small data transmission when it is determined that the first type of event is satisfied, the first type of event in this embodiment For example, it may include at least one of the following:

Event 1: The carrier selected by the terminal device is the same as the first carrier, and the beam selected by the terminal device is different from the first beam.

Event 2: The carrier selected by the terminal device is a NUL carrier, and the first carrier is a SUL carrier.

Event 3: The carrier selected by the terminal device is a SUL carrier, and the first carrier is a NUL carrier.

It can be understood that when a terminal device performs data transmission, it usually needs to select a carrier and a beam, and the beam in this embodiment may be represented by SSB, for example. Wherein, when the terminal equipment performs resource selection, for example, carrier selection is performed firstly according to the carrier selection threshold, and then SSB selection is performed according to the SSB selection threshold.

Then it may happen that the carrier selected by the terminal device is the same as the first carrier configured with CG resources, but the beam selected by the terminal device is different from the first beam configured with CG resources. That is, the first event above can be understood with reference to FIG. 8 , for example.

For example, SSB is used to represent the beam, as shown in Figure 8. For example, the network device is configured with CG resources on SSB1 and SSB2, but the terminal device selects the threshold based on the SSB and determines that the SSBs that meet the threshold are SSB3 and SSB4, and a terminal appears. The case where the beam selected by the device is different from the first beam configured with CG resources is the event 1 described above.

For event 1, the reason why there are no available CG resources on the SSB selected by the terminal device may be that the network device does not consider the mobility of the terminal device when configuring the CG resources. For example, the terminal device is located between beam SSB1 and Under the coverage of SSB23, when the terminal device enters the inactive state, the network device only associates CG resources on SSB1 and SSB2.

However, due to the mobility of the terminal, when the SDT service is triggered, the terminal device determines that the SSBs that meet the threshold are SSB3 and SSB4, so the terminal device has no available CG resources. In this way, it not only wastes the CG resources that the network device associates with the terminal device on SSB1 and SSB2, but also may cause SDT failure.

The above is an explanation for event 1. At the same time, after the terminal device selects resources, it may happen that the carrier selected by the terminal device is different from the first carrier configured with CG resources. For example, it can be understood by referring to FIG. 9 and FIG. 10 .

As shown in Figure 9, for example, the network device is configured with CG resources on the SUL, but the terminal device determines that the carrier that satisfies the threshold is NUL based on the carrier selection threshold, then the carrier selected by the terminal device and the carrier configured with CG resources appear. The case where the first carrier is different is the second event described above.

And, as shown in Figure 10, for example, the network device is configured with CG resources on the NUL, but the terminal device determines that the carrier that meets the threshold is SUL based on the carrier selection threshold, then there will also be a difference between the carrier selected by the terminal device and the configuration. The case where the first carrier of the CG resource is different is the event three described above.

For Event 2 and Event 3, the reason why there is no available CG resource on the carrier selected by the terminal device may be that the network device configures CG resources on an inappropriate carrier, which in turn causes the terminal device to fail when executing the SDT process. Although the network device is configured with CG resources, the terminal device has no available CG resources because the configured carrier is inappropriate or the threshold value for NUL/SUL selection is not configured reasonably. In this way, it not only wastes the CG resource that the network device associates with the terminal device on another carrier, but also may cause SDT failure.

Therefore, when the terminal device determines that any of the first type of events described above is met, it can record the first information of small data transmission. In this embodiment, the first information for the first type of event can be specifically the first report information.

In a possible implementation manner, the first report information may include at least one of the following:

Resource information of resources selected by the terminal device; wherein, the resource information may include at least one of the following: a carrier selected by the terminal device; a beam selected by the terminal device; a first threshold corresponding to carrier selection; a second threshold corresponding to beam selection.

Device information of the terminal device; wherein, the device information may include at least one of the following: the location of the terminal device when it selects resources; the time when the terminal device selects resources.

The measurement result of the terminal device; wherein, the measurement result may include at least one of the following: the measurement result includes at least one of the following: RSRP of the downlink reference signal; reference signal received quality (Reference Signal Received Quality, RSRQ) of the downlink reference signal; Signal to Interference plus Noise Ratio (SINR) of the downlink reference signal Signal to Interference plus Noise Ratio (SINR).

The SSB measurement results of the terminal equipment when selecting the beam;

The arrival time of the first data, wherein the first data is small data to be transmitted by the terminal device;

The time when the terminal device enters the inactive state, or the time when the RRC release message is sent/received.

In the actual implementation process, the specific implementation of the first reported information can also be selected and set according to actual needs. In a possible implementation mode, any information related to small data transmission can be used as the first reported information in this embodiment. Report information.

S704. The terminal device sends a first message to the network device, where the first message includes the first report information.

After the terminal device determines the first report information of the small data transmission, it can send the first message including the first report information to the network device. The implementation method is similar to that described above and will not be repeated here.

At the same time, it should be noted that, for event 1 described above, by reporting the SSB measurement results of the terminal device when the SDT service is triggered, as well as parameters such as the time when the SDT is triggered, it can assist the network side to consider when configuring CG resources. The mobility factor of the terminal equipment.

And, for the second event introduced above, by reporting the measurement results of NUL/SUL when the SDT service is triggered by the terminal equipment, and the time to trigger the SDT and other parameters, the auxiliary network side can be used to consider the carrier of the terminal when configuring CG resources. choose.

Therefore, in this embodiment, when the terminal device determines that there are no available CG resources and determines that the first type of event occurs, it records the first information of small data transmission and reports the first message to the network device, thereby helping the network device to optimize the CG Resource configuration to avoid SDT failure due to unreasonable CG resource configuration.

The above is an introduction to the implementation of the first type of event. For example, the situation corresponding to the second type of event can be described below in conjunction with FIG. 11 to FIG. 12. FIG. 12 is a fourth schematic diagram of implementing resource selection by the terminal device provided in the embodiment of the present application.

As shown in Figure 11, the method includes:

S1101. The terminal device receives an RRC connection release message sent by a network device, and switches to an RRC inactive state according to the RRC connection release message.

Wherein, the implementation manner of S1101 is similar to the implementation manner of S701.

S1102. The terminal device determines that there is small data to be sent.

In a possible situation, if the terminal device currently determines that there are available CG-SDT resources for the SDT process, and other SDT trigger conditions are also met, the terminal device may trigger the SDT process to transmit uplink data.

It should be emphasized that the difference between this and the above-mentioned embodiment is that in the above-mentioned embodiment, the terminal device determines that there are no available CG resources, so the terminal device does not successfully initiate the SDT process based on pre-configured resources, but in this embodiment, the terminal If the device determines that there are currently available CG resources for executing the SDT process, and other conditions for triggering the SDT process are also met, the terminal device may trigger the SDT process based on pre-configured resources.

S1103. When determining that the second type of event is satisfied, the terminal device records the second reporting information of the small data transmission.

During the execution of the SDT by the terminal device, if it is determined that the second type of event is satisfied, the terminal device may record the first information of the small data transmission, and the second type of event in this embodiment may include at least one of the following, for example:

Event 1: When transmitting the first small data, the resources selected by the terminal device are configured with CG resources, and when transmitting the second small data, the resources selected by the terminal device are not configured with CG resources. The transmission time is later than the transmission time of the first small data;

Event 2: During the process of small data transmission performed by the terminal device, the CG resource configured on the resource selected by the terminal device is released.

It can be understood that when the terminal device performs data transmission, it usually needs to select a carrier and a beam. In this embodiment, if the terminal device determines that there are currently available CG resources, it can determine that there are CG resources on the carrier and beam selected by the terminal device. The CG resource specifically means that the carrier selected by the terminal device is the same as the first carrier configured with the CG resource, and the beam selected by the terminal device is the same as the first beam configured with the CG resource.

At the same time, it can be understood that for an SDT process, the SDT process will end only when the instruction information from the network device is received or the corresponding conditions are met, otherwise, the SDT process will continue. In one SDT process, multiple small data may be transmitted.

Then it may happen that when the terminal device transmits the first small data, the resource selected by the terminal device is configured with CG resources, but when the second small data after the first small data is transmitted, the resources selected by the terminal device are not configured with CG resources. CG resources are configured, wherein the second small data and the first small data are data transmitted in one SDT process, and the transmission time of the second small data is later than the transmission time of the first small data.

As described here, when the second small data is transmitted, the resources selected by the terminal device are not configured with CG resources. Specifically, the beam selected by the terminal device described above may be different from the first beam; and/or, the resource selected by the terminal device The selected carrier is different from the first carrier.

The currently introduced situation is event 1 in this embodiment, which can be understood with reference to FIG. 12 , for example.

For example, SSB is used to represent the beam, as shown in Figure 12. For example, the network device is configured with CG resources on SSB1 and SSB2. When the SDT service is just triggered, the terminal device selects the threshold based on the SSB, and determines that the SSB that meets the threshold is SSB1. and SSB2, and perform SDT transmission on the associated CG resources on SSB1 and SSB2.

However, in the subsequent transmission, for example, the terminal device selects the threshold based on the SSB and determines that the SSBs that meet the threshold are SSB3 and SSB4, then there will be no CG resource configured on the resource selected by the terminal device, which is the event described in this embodiment one. The current example in FIG. 12 is specifically a case where the beam selected by the terminal device is different from the first beam configured with CG resources.

For event 1, the reason why the terminal device has no available CG resources on its selected SSB during the CG-SDT process may be that the network device does not consider the mobility of the terminal device when configuring the CG resources. For example, the terminal device is connected to In the state, it is located under the coverage of beams SSB1 and SSB2. When the terminal device enters the inactive state, the network device only associates CG resources on SSB1 and SSB2.

Due to the mobility of the terminal device, when the SDT service is just triggered, the terminal device can perform SDT transmission on the CG resource associated with SSB1 and SSB2, but in the subsequent transmission, the terminal device moves to the coverage of SSB3 and SSB4, and also That is to say, the SSBs that meet the threshold are SSB3 and SSB4, but the network device does not associate CG resources for SSB3 and SSB4, so the terminal device has no available CG resources. As a result, the terminal device does not have available CG resources during the execution of the SDT, which may lead to failure of the SDT.

The above is the description for event 1. Meanwhile, when the terminal device is executing SDT, the CG resource configured on the resource selected by the terminal device may be released.

Wherein, the CG resource is released, which may include at least one of the following: the TA timer of the CG resource expires, and the CG resource is released; the change amount of the reference signal received power RSRP measured by the terminal device is greater than or equal to the preset threshold, and the CG resource is released. The resource is freed. Here is the second event in this embodiment.

For event 2, it may be that the network device does not understand the service arrival rules of the terminal device, which leads to the unreasonable configuration of CG resources and its validity configuration, which leads to the release of CG resources during the execution of SDT, which will lead to SDT. fail.

Therefore, when the terminal device determines that any of the first-type events described above is satisfied, it can record the first information of small data transmission. In this embodiment, the first information for the second-type event can be specifically the second report information.

In a possible implementation manner, the second report information may include at least one of the following:

The SSB measurement results of the terminal equipment when selecting the beam;

The time when the terminal device enters the inactive state, or the time when the RRC release message is sent/received;

TA timer duration;

The preset threshold corresponding to the RARP variation.

In the actual implementation process, the specific implementation of the second report information can also be selected and set according to actual needs. In a possible implementation mode, any information related to small data transmission can be used as the second report information in this embodiment. Report information.

And it should also be noted that the first reported information and the second reported information in this application are actually the first information, but for the purpose of distinguishing when describing different types of events, when the preset event is described as the first type of event, When the first information is first report information, and the preset event is a second type event, the first information is second report information.

S1104. The terminal device sends a first message to the network device, where the first message includes the second report information.

After the terminal device determines the second report information of the small data transmission, it can send the first message including the second report information to the network device. The implementation method is similar to that described above and will not be repeated here.

At the same time, it should be noted that for event 1 described above, by reporting the SSB measurement results of the terminal device when the SDT service is triggered, the location information of the terminal, and the time to trigger the SDT and other parameters, the auxiliary network side can be used to configure the CG later. Consider terminal mobility factors when determining resources.

And, for the second event described above, by reporting the TA timer duration and the preset threshold corresponding to the RARP variation, the secondary network side can be used to consider the service arrival rule of the terminal device when configuring the CG resources.

Therefore, in this embodiment, when the terminal device determines that there are available CG resources, but the CG resources fail in the subsequent SDT process, that is, when it is determined that the second type of event occurs, the first information of small data transmission is recorded and sent to the network The device reports the first message, so as to help the network device optimize the configuration of the CG resources, so as to avoid SDT failure caused by unreasonable configuration of the CG resources.

To sum up, the communication method provided by the embodiment of the present application can help network devices optimize SDT resources and parameter configurations by reporting the usage of CG resources, SDT failure information and parameter configurations to network devices through terminal devices, thereby effectively improving SDT success rate.

FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application. Referring to FIG. 13, the communication device 130 may include a sending module 1301 and a processing module 1302, wherein,

The sending module 1301 is configured for the terminal device to send a first message to the network device, wherein the first message includes first information recording small data transmission.

In a possible implementation manner, the device further includes: a processing module 1302;

The processing module 1302 is configured for the terminal device to record the first information when at least one of the following preset events is met:

A first-type event, where the first-type event is used to indicate that no CG resource is configured on the resource selected by the terminal device;

A second type of event, the second type of event is used to indicate that CG resources are configured on the resources selected by the terminal device, and during the small data transmission process, the CG resources are invalid.

In a possible implementation manner, the resource selected by the terminal device includes a carrier and a beam.

In a possible implementation manner, the CG resource is configured by a network device;

Wherein, the CG resource is configured on a first carrier and at least one first beam, and the first carrier is a normal uplink NUL carrier or a supplementary uplink SUL carrier.

In a possible implementation manner, the first type of event includes at least one of the following:

The carrier selected by the terminal device is the same as the first carrier, and the beam selected by the terminal device is different from the first beam;

The carrier selected by the terminal device is different from the first carrier.

In a possible implementation manner, the carrier selected by the terminal device is different from the first carrier, including:

The carrier selected by the terminal device is a NUL carrier, and the first carrier is a SUL carrier; or,

The carrier selected by the terminal device is a SUL carrier, and the first carrier is a NUL carrier.

In a possible implementation manner, the second type of event includes at least one of the following:

When transmitting the first small data, the resources selected by the terminal device are configured with CG resources; when transmitting the second small data, the resources selected by the terminal device are not configured with CG resources, wherein the second The transmission time of the small data is later than the transmission time of the first small data;

During the small data transmission process performed by the terminal device, the CG resource configured on the resource selected by the terminal device is released.

In a possible implementation manner, releasing the CG resource configured on the resource selected by the terminal device includes:

The time alignment TA timer of the CG resource expires, and the CG resource is released; or,

The change amount of the reference signal received power RSRP measured by the terminal device is greater than or equal to a preset threshold, and the CG resource is released.

In a possible implementation manner, when the preset event is the first type of event, the first information is first reporting information;

When the preset event is the second type of event, the first information is second reporting information.

In a possible implementation manner, the first report information and the second report information include at least one of the following:

Resource information of resources selected by the terminal device;

Device information of the terminal device;

a measurement result of the terminal device;

The SSB measurement result of the terminal device when selecting a beam;

The arrival time of the first data, where the first data is small data to be transmitted by the terminal device;

The time when the terminal device enters the inactive state.

In a possible implementation manner, the resource information includes at least one of the following:

the carrier selected by the terminal device;

the beam selected by the terminal device;

A first threshold corresponding to carrier selection;

Beam selection corresponds to the second threshold.

In a possible implementation manner, the device information includes at least one of the following:

The location where the terminal device is located when it selects resources;

The time when the terminal device selects resources.

In a possible implementation manner, the measurement results include at least one of the following:

RSRP of the downlink reference signal;

The reference signal received quality RSRQ of the downlink reference signal;

A signal-to-interference-plus-noise ratio (SINR) of the downlink reference signal.

In a possible implementation manner, the second report information further includes at least one of the following:

TA timer duration;

The preset threshold corresponding to the RARP variation.

In a possible implementation manner, the sending module 1301 is specifically configured to:

The terminal device receives the request message sent by the network device;

The terminal device sends the first information to the network device according to the request message.

In a possible implementation manner, the request message includes the type of the first information.

In a possible implementation manner, the processing module 1302 is also configured to:

The first information is stored before the terminal device receives the request message sent by the network device.

In a possible implementation manner, the terminal device is in an RRC inactive state.

Before the terminal device determines the first information when the small data transmission SDT is abnormal, the terminal device receives the RRC connection release message sent by the network device;

The terminal device switches to an RRC inactive state according to the RRC connection release message.

Before the terminal device determines the first information when the small data transmission SDT is abnormal, the terminal device determines that there is small data to be sent.

The communication device provided in the embodiment of the present application can execute the technical solutions shown in the above method embodiments, and its implementation principles and beneficial effects are similar, and will not be repeated here.

FIG. 14 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. Referring to FIG. 14 , the terminal device 140 may include: a transceiver 21 , a memory 22 , and a processor 23 . The transceiver 21 may include: a transmitter and/or a receiver. The transmitter may also be called a transmitter, a transmitter, a sending port, or a sending interface, and similar descriptions, and the receiver may also be called a receiver, a receiver, a receiving port, or a receiving interface, or similar descriptions. Exemplarily, the transceiver 21 , the memory 22 , and the processor 23 are connected to each other through a bus 24 .

The memory 22 is used to store program instructions;

The processor 23 is configured to execute the program instructions stored in the memory, so as to enable the terminal device 20 to execute any communication method shown above.

Wherein, the receiver of the transceiver 21 can be used to perform the receiving function of the terminal device in the above communication method.

An embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, the foregoing communication method is implemented.

An embodiment of the present application may further provide a computer program product, where the computer program product may be executed by a processor, and when the computer program product is executed, any communication method performed by the terminal device described above may be implemented.

The communication device, computer-readable storage medium, and computer program product in the embodiments of the present application can execute the communication method performed by the above-mentioned terminal device. For the specific implementation process and beneficial effects, refer to the above, and details will not be repeated here.

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

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by program instructions and related hardware. The aforementioned computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, it realizes the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present application. scope.

Claims

A communication method, characterized in that, comprising:

The terminal device sends a first message to the network device, where the first message includes first information recording small data transmission.
The method according to claim 1, further comprising:

The terminal device records the first information when at least one of the following preset events is met:

A first-type event, where the first-type event is used to indicate that no CG resource is configured on the resource selected by the terminal device;

A second type of event, the second type of event is used to indicate that CG resources are configured on the resources selected by the terminal device, and during the small data transmission process, the CG resources are invalid.
The method according to claim 2, wherein the resource selected by the terminal device includes a carrier and a beam.
The method according to claim 2 or 3, wherein the CG resources are configured by network equipment;

Wherein, the CG resource is configured on a first carrier and at least one first beam, and the first carrier is a normal uplink NUL carrier or a supplementary uplink SUL carrier.
The method according to claim 4, wherein the first type of event includes at least one of the following:

The carrier selected by the terminal device is the same as the first carrier, and the beam selected by the terminal device is different from the first beam;

The carrier selected by the terminal device is different from the first carrier.
The method according to claim 5, wherein the carrier selected by the terminal device is different from the first carrier, comprising:

The carrier selected by the terminal device is a NUL carrier, and the first carrier is a SUL carrier; or,

The carrier selected by the terminal device is a SUL carrier, and the first carrier is a NUL carrier.
The method according to any one of claims 4-6, wherein the second type of event includes at least one of the following:

When transmitting the first small data, the resources selected by the terminal device are configured with CG resources; when transmitting the second small data, the resources selected by the terminal device are not configured with CG resources, wherein the second The transmission time of the small data is later than the transmission time of the first small data;

During the small data transmission process performed by the terminal device, the CG resource configured on the resource selected by the terminal device is released.
The method according to claim 7, wherein releasing the CG resource configured on the resource selected by the terminal device includes:

The time alignment TA timer of the CG resource expires, and the CG resource is released; or,

The change amount of the reference signal received power RSRP measured by the terminal device is greater than or equal to a preset threshold, and the CG resource is released.
The method according to any one of claims 1-8, characterized in that,

When the preset event is the first type of event, the first information is first reporting information;

When the preset event is the second type of event, the first information is second reporting information.
The method according to claim 9, wherein the first report information and the second report information include at least one of the following:

Resource information of resources selected by the terminal device;

Device information of the terminal device;

a measurement result of the terminal device;

The SSB measurement result of the terminal device when selecting a beam;

The arrival time of the first data, where the first data is small data to be transmitted by the terminal device;

The time when the terminal device enters the inactive state.
The method according to claim 10, wherein the resource information includes at least one of the following:

the carrier selected by the terminal device;

the beam selected by the terminal device;

A first threshold corresponding to carrier selection;

Beam selection corresponds to the second threshold.
The method according to claim 10 or 11, wherein the device information includes at least one of the following:

The location where the terminal device is located when it selects resources;

The time when the terminal device selects resources.
The method according to any one of claims 10-12, wherein the measurement results include at least one of the following:

RSRP of the downlink reference signal;

The reference signal received quality RSRQ of the downlink reference signal;

A signal-to-interference-plus-noise ratio (SINR) of the downlink reference signal.
The method according to any one of claims 10-13, wherein the second reporting information further includes at least one of the following:

TA timer duration;

The preset threshold corresponding to the RARP variation.
The method according to any one of claims 1-14, wherein the terminal device sending the first information to the network device includes:

The terminal device receives the request message sent by the network device;

The terminal device sends the first information to the network device according to the request message.
The method according to claim 15, wherein the request message includes the type of the first information.
The method according to claim 15 or 16, wherein, before the terminal device receives the request message sent by the network device, further comprising:

The first information is stored.
The method according to any one of claims 1-17, wherein the terminal device is in an RRC inactive state.
The method according to any one of claims 1-18, wherein, when the small data transmission SDT is abnormal, the terminal device further includes before determining the first information:

The terminal device receives the RRC connection release message sent by the network device;

The terminal device switches to an RRC inactive state according to the RRC connection release message.
The method according to any one of claims 1-19, characterized in that, when the small data transmission SDT is abnormal, before determining the first information, the terminal device further includes:

The terminal device determines that there is small data to be sent.
A communication device, characterized by comprising:

A sending module, configured for the terminal device to send a first message to the network device, wherein the first message includes first information recording small data transmission.
The device according to claim 21, further comprising: a processing module;

The processing module is configured for the terminal device to record the first information when at least one of the following preset events is met:

A first-type event, where the first-type event is used to indicate that no CG resource is configured on the resource selected by the terminal device;

A second type of event, the second type of event is used to indicate that the resource selected by the terminal device is configured with a CG resource, and during the small data transmission process, the CG resource is invalid.
The apparatus according to claim 22, wherein the resource selected by the terminal device includes a carrier and a beam.
The device according to claim 22 or 23, wherein the CG resources are configured by network equipment;

Wherein, the CG resource is configured on a first carrier and at least one first beam, and the first carrier is a normal uplink NUL carrier or a supplementary uplink SUL carrier.
The device according to claim 24, wherein the first type of event includes at least one of the following:

The carrier selected by the terminal device is the same as the first carrier, and the beam selected by the terminal device is different from the first beam;

The carrier selected by the terminal device is different from the first carrier.
The apparatus according to claim 25, wherein the carrier selected by the terminal device is different from the first carrier, comprising:

The carrier selected by the terminal device is a NUL carrier, and the first carrier is a SUL carrier; or,

The carrier selected by the terminal device is a SUL carrier, and the first carrier is a NUL carrier.
The device according to any one of claims 24-26, wherein the second type of event includes at least one of the following:

When transmitting the first small data, the resources selected by the terminal device are configured with CG resources; when transmitting the second small data, the resources selected by the terminal device are not configured with CG resources, wherein the second The transmission time of the small data is later than the transmission time of the first small data;

During the small data transmission process performed by the terminal device, the CG resource configured on the resource selected by the terminal device is released.
The apparatus according to claim 27, wherein releasing the CG resource configured on the resource selected by the terminal device includes:

The time alignment TA timer of the CG resource expires, and the CG resource is released; or,

The change amount of the reference signal received power RSRP measured by the terminal device is greater than or equal to a preset threshold, and the CG resource is released.
The device according to any one of claims 21-28, characterized in that,

When the preset event is the first type of event, the first information is first reporting information;

When the preset event is the second type of event, the first information is second reporting information.
The device according to claim 29, wherein the first report information and the second report information include at least one of the following:

Resource information of resources selected by the terminal device;

Device information of the terminal device;

a measurement result of the terminal device;

The SSB measurement result of the terminal device when selecting a beam;

The arrival time of the first data, where the first data is small data to be transmitted by the terminal device;

The time when the terminal device enters the inactive state.
The device according to claim 30, wherein the resource information includes at least one of the following:

the carrier selected by the terminal device;

the beam selected by the terminal device;

A first threshold corresponding to carrier selection;

Beam selection corresponds to the second threshold.
The device according to claim 30 or 31, wherein the device information includes at least one of the following:

The location where the terminal device is located when it selects resources;

The time when the terminal device performs resource selection.
The device according to any one of claims 30-32, wherein the measurement results include at least one of the following:

RSRP of the downlink reference signal;

The reference signal received quality RSRQ of the downlink reference signal;

A signal-to-interference-plus-noise ratio (SINR) of the downlink reference signal.
The device according to any one of claims 30-33, wherein the second reporting information further includes at least one of the following:

TA timer duration;

The preset threshold corresponding to the RARP variation.
The device according to any one of claims 21-34, wherein the sending module is specifically used for:

The terminal device receives the request message sent by the network device;

The terminal device sends the first information to the network device according to the request message.
The device according to claim 35, wherein the request message includes the type of the first information.
The device according to claim 35 or 36, wherein the processing module is further used for:

The first information is stored before the terminal device receives the request message sent by the network device.
The apparatus according to any one of claims 21-37, wherein the terminal equipment is in an RRC inactive state.
The device according to any one of claims 21-38, wherein the processing module is further configured to:

Before the terminal device determines the first information when the small data transmission SDT is abnormal, the terminal device receives the RRC connection release message sent by the network device;

The terminal device switches to an RRC inactive state according to the RRC connection release message.
The device according to any one of claims 21-39, wherein the processing module is further configured to:

Before the terminal device determines the first information when the small data transmission SDT is abnormal, the terminal device determines that there is small data to be sent.
A terminal device, characterized in that it includes: a transceiver, a processor, and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executable instructions stored in the memory, so that the processor executes the communication method according to any one of claims 1 to 20.
A computer-readable storage medium, characterized in that, computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to realize the the communication method described above.
A computer program product, comprising a computer program, characterized in that, when the computer program is executed by a processor, the communication method according to any one of claims 1 to 20 is implemented.