CN118318494A

CN118318494A - Wireless communication method, terminal equipment and network equipment

Info

Publication number: CN118318494A
Application number: CN202180102816.3A
Authority: CN
Inventors: 尤心; 林雪; 刘洋
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-12-14
Filing date: 2021-12-14
Publication date: 2024-07-09
Also published as: WO2023108416A1

Abstract

A wireless communication method, terminal equipment and network equipment are provided. The method comprises the following steps: the terminal device sends a first message to the network device, the first message including first information of the SDT. The terminal device reports a first message including first information of the SDT to the network device, and the network device is helped to optimize relevant parameters of the SDT based on the first information.

Description

Wireless communication method, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, a terminal device, and a network device for wireless communications.

Background

The self-organizing network (self-organizing network, SON) can optimize the network parameter configuration according to the information reported by the terminal equipment. However, the SON framework does not support small data transmission (SMALL DATA transmission, SDT), so that the network device cannot optimize the parameters related to the SDT.

Disclosure of Invention

In view of the above problems, the present application provides a method for wireless communication, a terminal device, and a network device.

In a first aspect, a method of wireless communication is provided, comprising: the terminal device sends a first message to the network device, the first message including first information of the SDT.

In a second aspect, there is provided a method of wireless communication, comprising: the network device receives a first message sent by the terminal device, wherein the first message comprises first information of the SDT.

In a third aspect, there is provided a terminal device comprising: and the sending unit is used for sending a first message to the network equipment, wherein the first message comprises first information of the SDT.

In a fourth aspect, there is provided a network device comprising: and the receiving unit is used for receiving a first message sent by the terminal equipment, wherein the first message comprises first information of the SDT.

In a fifth aspect, there is provided a terminal device comprising a processor, a memory, a communication interface, the memory being for storing one or more computer programs, the processor being for invoking the computer programs in the memory to cause the terminal device to perform the method of the first aspect.

In a sixth aspect, there is provided a network device comprising a processor, a memory, a communication interface, the memory for storing one or more computer programs, the processor for invoking the computer programs in the memory to cause the network device to perform the method of the second aspect.

In a seventh aspect, there is provided an apparatus comprising a processor for calling a program from a memory to perform the method of the first aspect.

In an eighth aspect, there is provided an apparatus comprising a processor for calling a program from a memory to perform the method of the second aspect.

In a ninth aspect, there is provided a chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of the first aspect.

In a tenth aspect, there is provided a chip comprising a processor for calling a program from a memory, so that a device on which the chip is mounted performs the method of the second aspect.

In an eleventh aspect, there is provided a computer-readable storage medium having stored thereon a program that causes a computer to execute the method of the first aspect.

In a twelfth aspect, there is provided a computer-readable storage medium having stored thereon a program that causes a computer to execute the method of the second aspect.

In a thirteenth aspect, there is provided a computer program product comprising a program for causing a computer to perform the method of the first aspect.

In a fourteenth aspect, there is provided a computer program product comprising a program for causing a computer to perform the method of the second aspect.

In a fifteenth aspect, there is provided a computer program for causing a computer to perform the method of the first aspect.

In a sixteenth aspect, there is provided a computer program for causing a computer to perform the method of the second aspect.

In the embodiment of the application, the terminal equipment reports the first information containing the SDT to the network equipment, and the network equipment is helped to optimize the related parameters of the SDT based on the first information.

Drawings

Fig. 1 is a diagram illustrating an example of a system architecture of a communication system applicable to an embodiment of the present application.

Fig. 2 is a schematic flow chart for SDT based on a two-step random access procedure.

Fig. 3 is a schematic flow chart for SDT based on a four-step random access procedure.

Fig. 4 is a schematic flow chart of information reporting under SON architecture.

Fig. 5 is a schematic flow chart of a wireless communication method according to an embodiment of the present application.

Fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Fig. 7 is a schematic structural diagram of a network device according to an embodiment of the present application.

Fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

Fig. 1 is a wireless communication system 100 to which embodiments of the present application are applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. Network device 110 may be a device that communicates with terminal device 120. Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices 120 located within the coverage area.

Fig. 1 illustrates one network device and two terminals by way of example, and the wireless communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

Optionally, the wireless communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that the technical solution of the embodiment of the present application may be applied to various communication systems, for example: fifth generation (5th generation,5G) systems or New Radio (NR), long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD), and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system, a satellite communication system and the like.

The Terminal device in the embodiments of the present application may also be referred to as a User Equipment (UE), an access Terminal, a subscriber unit, a subscriber station, a Mobile Station (MS), a Mobile Terminal (MT), a remote station, a remote Terminal, a mobile device, a user Terminal, a wireless communication device, a user agent, or a user equipment. The terminal device in the embodiment of the application can be a device for providing voice and/or data connectivity for a user, and can be used for connecting people, things and machines, such as a handheld device with a wireless connection function, a vehicle-mounted device and the like. The terminal device in the embodiments of the present application may be a mobile phone (mobile phone), a tablet (Pad), a notebook, a palm, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), and the like. Alternatively, the UE may be used to act as a base station. For example, the UEs may act as scheduling entities that provide side-uplink signals between UEs in V2X or D2D, etc. For example, a cellular telephone and a car communicate with each other using side-link signals. Communication between the cellular telephone and the smart home device is accomplished without relaying communication signals through the base station.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a radio access network device, for example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (radio access network, RAN) node (or device) that accesses the terminal device to the wireless network. The base station may broadly cover or replace various names in the following, such as: a node B (NodeB), an evolved NodeB (eNB), a next generation NodeB (gNB), a relay station, an access point, a transmission point (TRANSMITTING AND RECEIVING point, TRP), a transmission point (TRANSMITTING POINT, TP), a master MeNB, a secondary SeNB, a multi-mode radio (MSR) node, a home base station, a network controller, an access node, a radio node, an access point (access piont, AP), a transmission node, a transceiver node, a baseband unit (BBU), a remote radio unit (Remote Radio Unit, RRU), an active antenna unit (ACTIVE ANTENNA unit), a radio head (remote radio head, RRH), a Central Unit (CU), a Distributed Unit (DU), a positioning node, and the like. The base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip for placement within the aforementioned device or apparatus. The base station may also be a mobile switching center, a device-to-device D2D, a vehicle-to-everything (V2X), a device that performs a base station function in machine-to-machine (M2M) communication, a network-side device in a 6G network, a device that performs a base station function in a future communication system, or the like. The base stations may support networks of the same or different access technologies. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the network equipment.

The base station may be fixed or mobile. For example, a helicopter or drone may be configured to act as a mobile base station, and one or more cells may move according to the location of the mobile base station. In other examples, a helicopter or drone may be configured to function as a device to communicate with another base station.

In some deployments, the network device in embodiments of the application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

Network devices and terminal devices may be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. In the embodiment of the application, the scene where the network equipment and the terminal equipment are located is not limited.

It should be understood that the communication device referred to in the present application may be a network device or may also be a terminal device. For example, the first communication device is a network device, and the second communication device is a terminal device. As another example, the first communication device is a terminal device and the second communication device is a network device. As another example, the first communication device and the second communication device are both network devices, or are both terminal devices.

It should also be understood that all or part of the functionality of the communication device in the present application may also be implemented by software functions running on hardware or by virtualized functions instantiated on a platform, such as a cloud platform.

Currently, three radio resource control (radio resource control, RRC) states of the terminal device are defined in the protocol: an RRC CONNECTED (rrc_connected) state, an RRC IDLE (rrc_idle) state, and an RRC INACTIVE (rrc_inactive) state.

The rrc_connected state may refer to a state in which the terminal device is not RRC released after completing the random access procedure. An RRC connection exists between the terminal device and the network device (e.g., access network device). In the rrc_connected state, the terminal device may perform data transmission with the network device, for example, downlink data transmission and/or uplink data transmission. Or the terminal device may also perform transmission of a terminal device specific data channel and/or control channel with the network device to transmit specific information or unicast information of the terminal device.

The rrc_idle state refers to a state in which the terminal device resides in a cell, but is in when random access is not performed. The terminal device typically enters the rrc_idle state after power-on, or after RRC release. In the rrc_idle state, there is no RRC connection between the terminal device and the network device (e.g. the resident network device), the network device has no context for the terminal device stored, and no connection is established between the network device and the core network for the terminal device. If the terminal device needs to enter the rrc_connected state from the rrc_idle state, an RRC connection setup procedure needs to be initiated.

The rrc_inactive state is a state newly introduced from the viewpoint of energy saving in order to reduce air interface signaling, quickly restore wireless connection, and quickly restore data traffic. The rrc_inactive state is a state between the connected state and the idle state. The terminal device has previously entered the rrc_connected state and then released the RRC connection, radio bearers and radio resources with the network device, but the network device maintains the context of the terminal device in order to quickly restore the RRC connection. In addition, the connection established by the network device with the core network for the terminal device is not released, i.e. the user plane bearer and the control plane bearer between the RAN and the CN are maintained, i.e. there is a connection of the CN-NR.

For terminal devices with infrequent data transmissions, the terminal device may remain in the rrc_inactive state to conserve power. Before release 16, rel-16, the terminal device in rrc_inactive state does not support data transmission, i.e. does not support transmission of Mobile Originating (MO) data and mobile terminating (mobile terminated, MT) data. MO data refers to that the transmitting end of the data is a terminal device, and the transmission direction of the message is from the terminal device to the network device. MO data may also be referred to as upstream data. MT data refers to that the sending end of the data is a network device, and the transmission direction of the message is from the network device to a terminal device. MT data may also be referred to as downstream data.

When MO data or MT data arrives, the terminal device needs to restore the RRC connection, thereby entering the rrc_connected state. In the rrc_connected state, the terminal device may perform MO data or MT data transmission. After the MO data or MT data transmission is completed, the terminal device releases the RRC connection again and returns to the rrc_inactive state.

In the above procedure, the terminal device needs to switch from the rrc_inactive state to the rrc_connected state, and then switch from the rrc_connected state to the rrc_inactive state. Switching between different RRC states may result in increased power consumption of the terminal device. In some scenarios, however, the terminal device in rrc_inactive state needs to transmit some data (which may be referred to as packet data) with small data size and low transmission frequency, such as instant messaging messages, heartbeat packets, periodic data, and so on. If the terminal device switches to rrc_connected state and then performs data transmission, the signaling overhead required for the terminal device to perform RRC state switching may be even greater than the overhead required for transmitting the data, thereby causing unnecessary power consumption and signaling overhead.

In order to reduce the power consumption of the terminal device, the small data transfer SDT scheme in rrc_inactive state is discussed in Rel-17. In this scheme, the terminal device does not need to switch from the rrc_inactive state to the rrc_connected state for small data transmission, but can perform small data transmission in the rrc_inactive state. The small data transmission of the embodiment of the application can comprise uplink small data transmission and downlink small data transmission. The following will mainly describe for uplink small data transmission.

In the rrc_inactive state, there are two ways for the terminal device to perform SDT. One is SDT based on random access procedure and the other is SDT based on configuration grant (configured grant, CG). These two cases are described separately below.

SDT based on a random access procedure may refer to that a terminal device may perform SDT in the random access procedure. The random access mode may be a two-step random access procedure or a four-step random access procedure. For a two-step random access procedure, the terminal device may perform SDT in message 1 (msg 1). That is, the MSG1 of the two-step random access procedure can be used to carry data. For a four-step random access procedure, the terminal device may perform SDT in MSG 3. That is, MSG3 of the four-step random access procedure may be used to carry data.

In the random access procedure, the resource of the terminal device for SDT may be referred to as RA-SDT resource.

The two-step random access procedure and the four-step random access procedure are described below with reference to fig. 2 and 3, respectively.

Fig. 2 shows a schematic flow chart of SDT in a two-step random access procedure.

In step S210, the terminal device transmits MSG1 to the network device. The terminal device may send MSG1 on Random Access Channel (RACH) resources configured by the network device. The MSG1 may carry data to be transmitted (or referred to as uplink data or MO data). If MSG1 is utilized for SDT, the resources that transport MSG1 may also be referred to as RA-SDT resources. For example, the RA-SDT resource may be a RACH resource.

In step S220, the network device transmits MSG2 to the terminal device. A response to the data to be transmitted may be included in the MSG2.

Fig. 3 shows a schematic flow chart of SDT in a four-step random access procedure.

In step S310, the terminal device transmits MSG1 to the network device. The MSG1 carries a random access preamble.

In step S320, the network device transmits MSG2 to the terminal device. The MSG2 may also be referred to as a random access response (random access response, RAR). An uplink grant (UL grant) may also be included in MSG2 for scheduling uplink resource indications for MSG 3.

In step S330, the terminal device may send MSG3 to the network device on an uplink grant scheduled by the network device. Wherein, MSG3 carries data to be transmitted. If MSG3 is utilized for SDT, the resources that transmit MSG3 (i.e., the uplink grants scheduled by the network device) may also be referred to as RA-SDT resources.

In step S340, the network device transmits MSG4 to the terminal device. A response to the data to be transmitted may be included in the MSG4.

The configuration grant may also be referred to as an uplink grant. The configuration grant may refer to that the network device activates an uplink grant to the terminal device, and in the case that the deactivation instruction is not received, the terminal device may always use a resource (i.e., CG resource) specified by the activated uplink grant for uplink transmission. In the embodiment of the application, the terminal equipment can use CG resources to carry out SDT. CG resources for SDT may also be referred to as CG-SDT resources.

The type of configuration authorization may be CG type (type) 1 or CG type 2, for example. The configuration parameters of CG type 1 may be configured by RRC through higher layer signaling. The higher layer signaling may be IE ConfiguredGrantConfig, for example. The parameters needed for CG type 2 are also configured by IE ConfiguredGrantConfig, but the resources for CG type 2 need to be indicated by downlink control information (downlink control information, DCI) for activation and deactivation of the resources, only the resources that are activated by the DCI can be used.

CG type 1 and CG type 2 may be distinguished according to field rrc-ConfiguredUplinkGrant in IE ConfiguredGrantConfig. If field rrc-ConfiguredUplinkGrant is configured, the type of configuration grant is CG type 1, and if field rrc-ConfiguredUplinkGrant is not configured, the type of configuration grant is CG type 2.

Before SDT, the terminal device needs to judge whether the terminal device meets the condition of triggering SDT. Only if the condition for triggering the SDT is satisfied, the terminal device can perform the SDT. If the condition for triggering the SDT is met, the terminal device can initiate the SDT flow. If the condition triggering the SDT is not satisfied, the terminal device may initiate an RRC resume (resume) procedure. For example, the terminal device may switch from the rrc_inactive state to the rrc_connected state, thereby performing data transmission.

The conditions that trigger SDT may include one or more of the following conditions: the data to be transmitted comes from a radio bearer that can trigger the SDT; the data volume of the data to be transmitted is smaller than a pre-configured data volume threshold; the measurement result of the downlink reference signal received power (REFERENCE SIGNAL RECEIVING power, RSRP) is greater than a preconfigured RSRP threshold; there are valid SDT resources. The above conditions are described below, respectively.

In some embodiments, the condition that triggers the SDT is related to the radio bearer in which the data to be transmitted is located. The embodiment of the application can determine whether the terminal equipment meets the condition of triggering the SDT according to whether the data to be transmitted comes from the radio bearer which can trigger the SDT. If the data to be transmitted comes from a radio bearer that can trigger the SDT, the terminal device satisfies the condition of triggering the SDT. If the data to be transmitted is not from a radio bearer that can trigger the SDT, the terminal device does not satisfy the condition for triggering the SDT. The radio bearer may be, for example, a signaling radio bearer (SIGNALING RADIO BEARER, SRB) or a data radio bearer (data radio bearer, DRB).

In other embodiments, the condition that triggers the SDT is related to the amount of data to be transferred. If the data volume of the data to be transmitted is smaller, if the data to be transmitted is packet data, the terminal equipment meets the condition of triggering the SDT. If the data amount of the data to be transmitted is large, the terminal device does not meet the condition of triggering the SDT. The embodiment of the application can also determine whether the terminal equipment meets the condition of triggering the SDT by comparing the data volume of the data to be transmitted with the data volume threshold. If the data volume of the data to be transmitted is smaller than the data volume threshold, the terminal device meets the condition of triggering the SDT. If the data volume of the data to be transmitted is greater than or equal to the data volume threshold, the terminal device does not meet the condition of triggering the SDT. The data volume threshold may be pre-configured by the network device or it may be pre-defined in the protocol.

In other embodiments, the condition triggering the SDT is related to a measurement of the downlink RSRP. If the measurement result of the downlink RSRP is larger than the RSRP threshold, the signal quality is good, and the terminal equipment meets the condition of triggering the SDT. If the measurement result of the downlink RSRP is smaller than or equal to the RSRP threshold, the signal quality is poor, and the terminal equipment does not meet the condition of triggering the SDT. The RSRP threshold may be pre-configured by the network device or may be predefined in the protocol.

In other embodiments, the condition that triggers an SDT is related to whether there are valid SDT resources. If the valid SDT resource exists, the terminal device meets the condition of triggering the SDT, and the terminal device can use the valid SDT resource to perform data transmission. If no valid SDT resource exists, the terminal device does not meet the condition of triggering the SDT, and the terminal device does not have available SDT resources for data transmission. The SDT resources may be RA-SDT resources as described above, and/or CG-SDT resources.

If the terminal equipment is configured with the RA-SDT resource and the CG-SDT resource at the same time, the terminal equipment can judge whether the RA-SDT resource and the CG-SDT resource are effective or not at the same time when judging whether the effective SDT resource exists or not, or can judge whether one of the RA-SDT resource and the CG-SDT resource is effective or not at first, and then judge whether the other SDT resource is effective or not. For example, the terminal device may first determine whether there are valid RA-SDT resources and then determine whether there are valid CG-SDT resources. For another example, the terminal device may determine whether there is a valid CG-SDT resource, and then determine whether there is a valid RA-SDT resource. The following description will be made taking, as an example, whether the terminal device first determines that there is an effective CG-SDT resource, and then determines whether there is an effective RA-SDT resource.

In some embodiments, whether CG-SDT resources are valid is related to whether there is a valid time advance (TIMING ADVANCE, TA). The TA is related to the uplink synchronization of the terminal equipment, and if the TA is valid, the TA indicates that the terminal equipment is in an uplink synchronization state; if the TA is invalid, the terminal equipment is in an uplink out-of-step state. The embodiment of the application can determine whether CG-SDT resources are effective by judging whether effective TA exists or not. If there is a valid TA, this may indicate that CG-SDT resources are valid. If there is no valid TA, this may indicate that the CG-SDT resources are not valid.

Whether the TA is valid is related to whether a TA timer (TAT) of the SDT is in an operating state and/or whether a change amount of the RSRP measured by the terminal device exceeds an RSRP change amount threshold.

The network device may configure a TA timer for the terminal device, where the TA timer may be used for the terminal device to determine a duration in uplink synchronization. If the TA timer is in an operational state, i.e., the TA timer has not expired, it indicates that a valid TA is present. If the TA timer is not in an operational state, i.e., the TA timer times out, it indicates that there is no valid TA.

The TA timer may be started after the terminal device receives an RRC connection release (release) message or the terminal device enters an rrc_inactive state. The duration of the TA timer may be configured by the network device to the terminal device. For example, after receiving the RRC connection release message sent by the network device, the terminal device may enter an rrc_inactive state according to the indication information in the RRC connection release message. The RRC connection release message may further include configuration information of the SDT-TA timer, and the terminal device may start the SDT TA timer based on the configuration information of the SDT-TA timer.

The terminal device may measure RSRP of the downlink signal, and the change amount of RSRP may reflect the moving distance of the terminal device. The downlink signal may be, for example, a Positioning Reference Signal (PRS) signal. If the change amount of RSRP measured by the terminal device is smaller, which means that the moving distance of the terminal device is smaller, the TA is still valid. If the change amount of the RSRP measured by the terminal equipment is large, which means that the moving distance of the terminal equipment is large, the TA is invalid. The embodiment of the application can compare the variation of the RSRP with the RSRP variation threshold to determine whether the TA is valid. The terminal device may determine that the TA is valid if the amount of change in RSRP measured by the terminal device does not exceed the RSRP change amount threshold. The terminal device may determine that the TA is invalid if the amount of change in RSRP measured by the terminal device exceeds an RSRP change amount threshold. The RSRP change threshold may be pre-configured by the network device or may be pre-defined in the protocol.

The change amount of the RSRP measured by the terminal device may refer to an increase amount of the RSRP or a decrease amount of the RSRP. For example, the measurement result of the downlink RSRP when the terminal device receives the tracking area code (TRACKING AREA code, TAC) or the RRC release message last time is denoted as a. When the terminal device determines whether the TA is valid (or whether the SDT is triggered), the terminal device may measure the downlink RSRP, and the measured value is denoted as B. The RSRP variation threshold may include a first RSRP variation threshold and a second RSRP variation threshold. The terminal device may determine that the TA is valid if the increase amount of B to a does not exceed the first RSRP variation threshold, or the decrease amount of B to a does not exceed the second RSRP variation threshold. The first RSRP variation threshold and the second RSRP variation threshold may be equal or different, which is not specifically limited in the embodiment of the present application.

In other embodiments, whether CG-SDT resources are active is related to whether CG-SDT resources are present on a carrier selected by the terminal device. If CG-SDT resources are present on the selected carrier, the terminal device may determine that the CG-SDT resources are valid. If no CG-SDT resources are present on the selected carrier, the terminal device may determine that the CG-SDT resources are not valid. The carrier selected by the terminal device may be, for example, a Normal Uplink (NUL) carrier or a Supplementary Uplink (SUL) carrier.

In other embodiments, whether the CG-SDT resource is valid is related to whether the CG-SDT resource is present on a synchronization signal block (synchronization signal block, SSB) selected by the terminal device. If CG-SDT resources are present on the selected SSB, the terminal device may determine that the CG-SDT resources are valid. If no CG-SDT resources are present on the selected SSB, the terminal device may determine that the CG-SDT resources are not valid.

Through the mode, whether CG-SDT resources are effective or not can be judged. If CG-SDT resources are valid, the terminal device is indicated to meet the condition of triggering SDT. If the CG-SDT resource is not valid, the terminal device may further determine whether the RA-SDT resource is valid. If the RA-SDT resource is valid, the terminal device is indicated to meet the condition for triggering the SDT. If the RA-SDT resource is invalid, the condition for triggering the SDT is not met by the terminal device.

In the SDT process, the terminal device may have a SDT failure. If SDT fails, the terminal device may enter the RRC-IDLE state.

SDT failure is related to at least one of the following events: cell reselection occurs during SDT; the SDT failure detection timer (SDT failure detection timer) times out; the radio link control (radio link control, RLC) reaches the maximum number of transmissions. The maximum RLC transmission count indicates that the terminal device detects RLC failure (RLF).

In order to optimize network configuration and reduce network deployment cost and operation cost, a self-organizing network (self-organizing network, SON) technology is presented. SONs have self-configuring, self-optimizing, self-healing, etc. properties. Self-optimization may refer to the network device adaptively adjusting network parameters according to the running condition of the network, and optimizing the performance of the network.

In the SON architecture, the terminal device can record the process information of various events, and report the recorded information to the network device under the condition of receiving the indication report sent by the network device. The event recorded by the terminal device may include at least one of the following events: measurement event, connection establishment event, random access event, radio link detection event, mobility event.

Fig. 4 is a schematic flow chart of reporting event information by a terminal device. In step S420, the network device sends a UE information request (UEInformationRequest) to the terminal device, where the UEInformationRequest includes the information type that the network device needs to report by the terminal device.

UEInformationRequest may include, for example, at least one of the following: log measurement report request (logMeasReportReq), connection establishment failure report request (connEstFailReq), random access report request (ra-ReportReq), RLF report request (RLF-ReportReq), movement history report request (mobilityHistoryReportReq).

UEInformationRequest can be expressed in the following form:

Each of the above request information has a corresponding parameter field. When the parameter domain of a certain information is set to be "true", it indicates that the terminal device needs to report the information. When the parameter field of a certain information is set to "false" or is empty, it means that the terminal device does not need to report the information. For UEInformationRequest shown in the above figure, if the parameter fields of logMeasReportReq, connEstFailReq, ra-ReportReq, rlf-ReportReq, mobilityHistoryReportReq are true, the terminal device needs to Report logMeasReport, connEstFail, ra-Report and rlf-Report, mobilityHistoryReport.

After receiving UEInformationRequest sent by the network device, the terminal device in step S430 may send a UE information response to the network device according to the indication of the network device, that is, the value of the parameter domain of each information in UEInformationRequest (UEInformationResponse). UEInformationResponse may include information that the network device needs to report to the terminal device.

UEInformationResponse can be expressed in the following form:

The UEInformationResponse sent by the terminal device to the network device includes LogMeasReport, connEstFail, ra-Report and Rlf-Report, mobilityHistoryReport.

The terminal device may record the above various information, so as to send the relevant information to the network device when the network device indicates that the relevant information needs to be reported. Taking ra-Report as an example, the terminal device may store random access procedure information in a VarRA-Report list maintained by the terminal device after each successful completion of random access or failure of random access. And after the terminal equipment receives ra-ReportReq indicated by the network equipment, reporting the recorded ra-Report to the network equipment by the terminal equipment.

The network device may send UEInformationRequest to the terminal device, or may send UEInformationRequest to the terminal device after receiving the record information sent by the terminal device and having the record information available. As shown in fig. 4, the method shown in fig. 4 may further include step S410, where the terminal device transmits first indication information to the network device, where the first indication information may be used to indicate that recording information is available. The terminal device can record the process information of various events, and send first indication information to the network device after the process information of the events is recorded. After receiving the first indication information sent by the terminal device, the network device may determine whether to send UEInformationRequest to the terminal device according to the need.

After receiving UEInformationResponse sent by the terminal device, the network device can determine whether the parameter configuration of various events is reasonable according to the report information in UEInformationResponse. If the parameter configuration of a certain class of events is not reasonable, the network device may optimize these parameters.

The SDT described above is a new feature introduced by R17 and the SON framework before R17 does not support reporting for SDT. However, in the SDT process, there is also a phenomenon that the SDT related parameter configuration is unreasonable. How to optimize the relevant parameters of the SDT process, no clear solution exists at present.

In order to solve the above-mentioned problems, the technical solution provided by the embodiment of the present application is described in detail below with reference to fig. 5.

Fig. 5 is a schematic flow chart of a method of wireless communication provided by an embodiment of the present application. As shown in fig. 5, in step S510, the terminal device sends a first message to the network device. In some embodiments, the first message may be referred to as an SDT report message. The first message includes first information of the SDT. Or in some embodiments the first information may be referred to as SDT procedure information.

In some embodiments, the terminal device may notify the network device that the terminal device has an available first message before the terminal device sends the first message to the network device.

In some embodiments, the terminal device may determine whether to send the first message according to an indication of the network device. For example, the terminal device may record the first information of the SDT during the SDT. The terminal device may report the first message to the network device under the direction of the network device. Taking the SON framework as an example, the network device may send UEInformationRequest to the terminal device, and the UEInformationRequest may request that the terminal device report the first message. After receiving the SDT report request, the terminal device may send a first message to the network device.

The terminal equipment of the embodiment of the application can assist the network equipment to optimize the parameters and/or resources of the SDT by recording the first information of the SDT and reporting the first information of the SDT to the network equipment.

The recording of the first information may be triggered based on at least one event. In other words, the terminal device records the first information under the triggering of at least one event. The at least one event may be an event related to SDT failure, that is, the at least one event may be an event causing the terminal device to fail to complete SDT.

The embodiment of the present application does not specifically limit at least one event. For example, whether at least one event has an association with a CG-SDT resource is valid. And under the condition that the CG-SDT resource is invalid, the terminal equipment records the first information. For another example, the at least one event has an association with whether the RA-SDT resource is valid. And under the condition that the RA-SDT resource is invalid, the terminal equipment records the first information. For another example, the at least one event may have an association with the TA validity of the SDT. In case the TA is invalid or in case the terminal device detects that the TA is invalid, the terminal device records the first information.

The manner in which the TA is determined to be valid may be determined in the manner described above. As described above, whether the TA is valid has an association with whether the TA timer of the SDT times out and/or whether the change amount of the RSRP measured by the terminal device exceeds the RSRP change amount threshold. That is, at least one event has an association with whether the TA timer of the SDT has expired and/or whether the amount of change in RSRP measured by the terminal device exceeds the RSRP change amount threshold.

In some embodiments, at least one event has an association with whether the TA timer of the SDT has expired. For example, under the triggering of the expiration of the TA timer of the SDT, the terminal device records the first information of the SDT. The TA timer of the SDT may be started after the terminal device enters the rrc_inactive state, or the TA timer of the SDT may be started after the terminal device receives the RRC release message. The TA timer of the SDT may be configured by the network device for the terminal device through an RRC release message, or the TA timer of the SDT may be predefined in the protocol.

In other embodiments, the at least one event has an association with whether the RSRP change measured by the terminal device exceeds an RSRP change threshold. For example, the terminal device may measure RSRP and compare the RSRP of the two measurements. The terminal device may record the first information of the SDT if the change in RSRP of the two measurements exceeds the RSRP change threshold. The RSRP measured twice may refer to the RSRP measured twice consecutively, or may refer to the RSRP measured currently and the RSRP measured when the TAC or RRC release message is received last time. The change amount of the RSRP measured by the terminal device may refer to an increase amount of the RSRP or a decrease amount of the RSRP.

For example, the measurement result of the downlink RSRP when the terminal device receives the TAC or the RRC release message for the last time is denoted as a, and when the terminal device determines whether the TA is valid (or whether to trigger the SDT), the terminal device may measure the downlink RSRP, and its measurement value is denoted as B. The RSRP variation threshold may include a first RSRP variation threshold and a second RSRP variation threshold. The terminal device may determine that the TA is valid if the increase amount of B to a does not exceed the first RSRP variation threshold, or the decrease amount of B to a does not exceed the second RSRP variation threshold. The first RSRP variation threshold and the second RSRP variation threshold may be equal or different, which is not specifically limited in the embodiment of the present application.

At least one event is described below in connection with several examples. It should be appreciated that events in different examples may be combined with each other. That is, the terminal device may record the first information of the SDT while satisfying the following one or more events at the same time.

Example one

The at least one event may include a first event, which may refer to the SDT being triggered after the TA timer of the SDT expires, i.e., SDT-TAT expires AFTER WHICH SDT IS TRIGGER, e.g., no longer than a configured time slot. The terminal device may determine whether to trigger the SDT according to the manner described above. If the condition for triggering the SDT is met, the terminal equipment can initiate the SDT process and execute the transmission of uplink and downlink data. However, if the SDT is triggered after the TA timer of the SDT expires, the terminal device cannot successfully complete the SDT procedure due to the expiration of the TA timer of the SDT. If this occurs, the parameters or resource allocation representing the SDT are not reasonable. Thus, the terminal device may record the first information of the SDT under the trigger of the first event.

The SDT being triggered after the TA timer of the SDT times out may mean that the SDT is triggered within a preset time after the TA timer of the SDT times out, or that a time interval between a time when the TA timer of the SDT times out and a time when the SDT is triggered is less than the preset time. The preset time may be a short time, i.e., the SDT is triggered soon after the TA timer of the SDT expires. The preset time may be preconfigured by the network device or may be predefined in the protocol.

Example two

The at least one event may include a second event, which may refer to a TA timer of the SDT being timed out, and the change amount of the RSRP measured by the terminal device not exceeding a change amount threshold of the RSRP. Such as SDT-TAT expires but RSRP change is within the thres(For case both TAT and RSRP change threshold are configured for TA validation.TA timer and RSRP, can be used to determine if the TA is valid. When the change amount of the RSRP measured by the terminal equipment does not exceed the change amount threshold of the RSRP, the mobility of the terminal equipment is low, and the terminal equipment does not move in a large range. In this case, the TA of the terminal device is valid. But again indicates that the TA of the terminal device is invalid due to the expiration of the TA timer of the SDT. If this occurs, the TA timer representing the SDT does not match the RSRP variance threshold. Therefore, the terminal device can record the first information of the SDT under the triggering of the second event.

Example three

The at least one event may include a third event, which may refer to a TA timer of the SDT expiring after the terminal device triggers the CG-SDT. Such as SDT-TAT expires after CG-SDT IS TRIGGERED. Triggering the CG-SDT may include triggering a determination of whether CG-SDT resources are valid. In the above-described scheme, the conditions for triggering SDT include whether there are valid RA-SDT resources and/or CG-SDT resources. When judging whether effective RA-SDT resources and/or CG-SDT resources exist, the terminal equipment can firstly judge whether effective CG-SDT resources exist, and under the condition that effective CG-SDT resources do not exist, the terminal equipment can further judge whether effective RA-SDT resources exist.

The timing out of the TA timer of the SDT after the terminal device triggers the CG-SDT may refer to the timing out of the TA timer of the SDT in a preset time after the terminal device triggers the CG-SDT. The preset time may be a short time. For example, the TA timer of the SDT expires immediately after the terminal device triggers the CG-SDT. If the TA timer of the SDT times out after the terminal device triggers the CG-SDT, the terminal device does not have time to do RA-SDT. If this occurs, the configuration of parameters representing the SDT (e.g., TA timers) is not reasonable. Thus, the terminal device may record the first information of the SDT under the triggering of the third event.

Example four

The at least one event may include a fourth event, which may refer to a TA timer of the SDT expiring, and the terminal device detects that the target SSB meets a measurement threshold that triggers the CG-SDT. Wherein the target SSB is associated with CG resources (i.e., CG resources are configured on the target SSB). Such as SDT-TAT expires AFTER WHICH SDT IS TRIGGER, e.g., there is qualified SSB. The fourth event may refer to the expiration of the TA timer of the SDT, the SDT being triggered and the terminal device detecting that the target SSB meets the measurement threshold triggering CG-SDT.

Before sending the data to be transmitted, the terminal device can measure the SSB and select a target SSB with a measurement result meeting a preset value according to the signal measurement result of the SSB. Further, the terminal device may send the data to be transmitted on the target SSB. The signal measurement result of the SSB may include at least one of a measurement result of RSRP, a measurement result of reference signal quality (RSRQ), and a measurement result of signal-to-interference-and-noise ratio (SINR).

If the target SSB is associated with CG resources, the terminal device may use the SSB for SDT. But if the TA timer of the SDT times out, the terminal device will not be able to successfully complete the SDT procedure. If this occurs, the parameters (e.g., TA timer) or resources (e.g., SSB resources or CG resources) representing the SDT are not reasonably configured. Therefore, the terminal device may record the first information of the SDT under the trigger of the fourth event.

Example five

The at least one event includes a fifth event, which may mean that the TA timer of the SDT has not expired and the change in RSRP measured by the terminal device exceeds the RSRP change threshold. Such as SDT-TAT is running but RSRP CHANGE IS LARGER THAN THE THRES.

Both the TA timer and the amount of change in RSRP can be used to determine whether the TA is valid. When the change amount of the RSRP measured by the terminal equipment exceeds the change amount threshold of the RSRP, the mobility of the terminal equipment is high, and the terminal equipment moves in a large range. In this case, the TA of the terminal device is invalid. But from the perspective of the TA timer of the SDT, since the TA timer of the SDT has not timed out, it indicates that the TA of the terminal device is valid. That is, the TA timer does not match the RSRP variance threshold. Although the TA timer of the SDT does not time out, the terminal device cannot successfully complete the SDT procedure. If this occurs, the parameters representing the SDT (e.g., the TA timer or the RSRP variance threshold) are not reasonably configured. Therefore, the terminal device may record the first information of the SDT under the trigger of the fifth event.

The event triggering the terminal device to record the first information is described in detail above, and the content of the first information is described below.

The embodiment of the application does not specifically limit the specific content of the first information. For example, the first information relates to a TA timer. As another example, the first information is related to a measurement of RSRP. The terminal device reports the first information of the SDT, and can assist the network device to optimize the duration of the TA timer and the RSRP variation threshold for guaranteeing the validity of the TA. The specific contents of the first information are described in detail below. It is to be understood that the contents of the first information described below are combined with each other.

The first information may include a duration of a TA timer (e.g., SDT-TAT value). Under the condition that the duration configuration of the TA timer is unreasonable, the terminal equipment can report the duration of the TA timer to the network equipment so that the network equipment optimizes the configuration parameters (such as the duration of the TA timer) of the SDT. For example, the terminal device may report the duration of the TA timer to the network device under the triggering of at least one of the first event, the second event, the third event, the fourth event, and the fifth event. The network device may optimize parameters of the SDT (e.g., the duration of the TA timer) based on the duration of the TA timer.

The first information may include SDT-associated signal measurement information. The SDT-associated signals may include SSBs and/or PRSs, for example. In the fourth event, the terminal device may measure the SSB and determine the target SSB. In event two and event five described above, the terminal device may measure PRS to determine whether the RSRP change exceeds the RSRP change threshold. The measurement information of the signal may for example comprise at least one of the following: RSRP, RSRQ, SINR. For example, the terminal device may measure the RSRP of the SSB. For another example, the terminal device may measure RSRQ of PRS. In some implementations, the terminal device may report the SDT-associated signal measurement information to the network device under the triggering of at least one of the event two, the event four, and the event five. The network device may optimize parameters of the SDT (e.g., RSRP delta threshold) based on the signal measurement information associated with the SDT.

The first information may include a transmission or reception time of the RRC release message. The terminal device may start the TA timer after receiving the RRC release message. Therefore, the time when the network device sends the RRC release message or the time when the terminal device receives the RRC release message has an association relationship with the TA timer timeout. In the case that the TA timer is not reasonably set, for example, under the triggering of at least one of the first event, the second event, the third event, the fourth event, and the fifth event, the terminal device may report the sending or receiving time of the RRC release message to the network device, so that the network device optimizes parameters of the SDT (such as the sending or receiving time of the RRC release message).

The first information may include a time when the terminal device enters the inactive state. The terminal device may start the TA timer after entering the inactive state. Therefore, the time when the terminal device enters the inactive state has an association relationship with the TA timer timeout. Under the condition that the TA timer is not reasonably set, for example, under the triggering of at least one of the first event, the second event, the third event, the fourth event and the fifth event, the terminal device may report the time of entering the inactive state to the network device, so that the network device optimizes the configuration parameters of the SDT (such as the time of entering the inactive state by the terminal device).

The first information may include a trigger time of the SDT. Taking event one described above as an example, the SDT is triggered after its TA timer expires. An unreasonable factor for an event may be an unreasonable time for which the SDT is triggered. Therefore, the terminal device can report the triggering time of the SDT to the network device under the triggering of the first event, so that the network device optimizes the parameters of the SDT.

The first information may include a time interval between a trigger time of the SDT and the RRC release message. Such as Time duration between the reception of RRC RELEASE AND TRIGGER of SDT. Taking event one described above as an example, the SDT is triggered after its TA timer expires. An unreasonable factor for an event may be the mismatch between the trigger time of the SDT and the TA timer. Whether the TA timer times out is related to the sending or receiving time of the RRC release message, i.e. the triggering of event one is related to the triggering time of the SDT and the time interval between RRC release messages. Thus, the terminal device may report the triggering time of the SDT and the time interval between the RRC release messages to the network device, so that the network device optimizes the parameters of the SDT (such as the sending or receiving time of the RRC release messages).

The first information may include a time interval between a trigger time of the SDT and the terminal device entering the inactive state. Still taking event one described above as an example, the SDT is triggered after the TA timer of the SDT expires. An unreasonable factor for an event may be the mismatch between the trigger time of the SDT and the TA timer. Whether the TA timer times out or not is related to the time the terminal device enters the inactive state, i.e. the triggering of event one is related to the triggering time of the SDT and the time interval between the terminal device entering the inactive state. Therefore, the terminal device may report the triggering time of the SDT and the time interval between the terminal device entering the inactive state to the network device, so that the network device optimizes the parameter of the SDT (such as the time when the terminal device enters the inactive state).

The first information may include an RSRP variation threshold. Taking the event two and the event five described above as examples, the triggering of the event two and the event five is related to the RSRP variation threshold, that is, the RSRP variation threshold is set unreasonably, which results in the occurrence of the event two and the event five. Thus, the terminal device may report the RSRP variation threshold to the network device, so that the network device optimizes the parameter of the SDT (e.g., the RSRP variation threshold).

The method embodiments of the present application are described above in detail with reference to fig. 1 to 5, and the apparatus embodiments of the present application are described below in detail with reference to fig. 6 to 8. It is to be understood that the description of the method embodiments corresponds to the description of the device embodiments, and that parts not described in detail can therefore be seen in the preceding method embodiments.

Fig. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application. The terminal device shown in fig. 6 may be any of the terminal devices described above. The terminal device 600 comprises a transmitting unit 610. The sending unit 610 may be configured to send a first message to the network device, where the first message includes first information of the SDT.

Optionally, the recording of the first information is triggered based on at least one event, and the at least one event has an association with TA validity of the SDT.

Optionally, whether the at least one event is timed out by a TA timer of the SDT and/or whether the change amount of RSRP measured by the terminal device exceeds an RSRP change amount threshold has an association relationship.

Optionally, the recording of the first information is triggered based on at least one event, the at least one event including one or more of the following events: the SDT is triggered after the TA timer of the SDT expires; the TA timer of the SDT is overtime, and the variation of the RSRP measured by the terminal equipment does not exceed the RSRP variation threshold; after the terminal equipment triggers CG-SDT, the TA timer of the SDT is overtime; the TA timer of the SDT is overtime, and the terminal equipment detects that a target SSB meets a measurement threshold for triggering CG-SDT, wherein the target SSB is associated with CG resources; or the TA timer of the SDT is not timed out, and the change amount of the RSRP measured by the terminal equipment exceeds the RSRP change amount threshold.

Optionally, the SDT is triggered after a TA timer of the SDT expires, including: after the TA timer of the SDT is overtime, the SDT is triggered, and the time interval between the triggering time of the SDT and the overtime of the TA timer of the SDT does not exceed a first threshold value.

Optionally, the first information includes one or more of the following information: the duration of the TA timer of the SDT; the SDT-associated signal measurement information; the sending or receiving time of the RRC release message; the time when the terminal equipment enters the inactive state; the trigger time of the SDT; a time interval between the trigger time of the SDT and the RRC release message; or the RSRP variation threshold.

Fig. 7 is a schematic block diagram of a network device according to an embodiment of the present application. The network device shown in fig. 7 may be any of the network devices described above. The network device 700 comprises a receiving unit 710. The receiving unit 710 may be configured to receive a first message sent by a terminal device, where the first message includes first information of an SDT.

Fig. 8 is a schematic structural view of an apparatus of an embodiment of the present application. The dashed lines in fig. 8 indicate that the unit or module is optional. The apparatus 800 may be used to implement the methods described in the method embodiments above. The apparatus 800 may be a chip, a terminal device or a network device.

The apparatus 800 may include one or more processors 810. The processor 810 may support the apparatus 800 to implement the methods described in the method embodiments above. The processor 810 may be a general purpose processor or a special purpose processor. For example, the processor may be a central processing unit (central processing unit, CPU). Or the processor may be another general purpose processor, a digital signal processor (DIGITAL SIGNAL processor), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, a discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The apparatus 800 may also include one or more memories 820. The memory 820 has stored thereon a program that can be executed by the processor 810 to cause the processor 810 to perform the method described in the method embodiments above. The memory 820 may be separate from the processor 810 or may be integrated in the processor 810.

The apparatus 800 may also include a transceiver 830. The processor 810 may communicate with other devices or chips through the transceiver 830. For example, the processor 810 may transceive data with other devices or chips through the transceiver 830.

The embodiment of the application also provides a computer readable storage medium for storing a program. The computer-readable storage medium may be applied to a terminal or a network device provided in an embodiment of the present application, and the program causes a computer to execute the method performed by the terminal or the network device in the respective embodiments of the present application.

The embodiment of the application also provides a computer program product. The computer program product includes a program. The computer program product may be applied to a terminal or a network device provided in an embodiment of the present application, and the program causes a computer to execute the method executed by the terminal or the network device in the respective embodiments of the present application.

The embodiment of the application also provides a computer program. The computer program can be applied to a terminal or a network device provided in an embodiment of the present application, and cause a computer to perform a method performed by the terminal or the network device in each embodiment of the present application.

It should be understood that in embodiments of the present application, "B corresponding to a" means that B is associated with a, from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may 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. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may 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 may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital versatile disk (digital video disc, DVD)), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

The terminal device sends a first message to the network device, the first message comprising first information of the small data transfer SDT.
The method of claim 1, wherein the recording of the first information is triggered based on at least one event, and wherein the at least one event has an association with a time advance TA validity of the SDT.
The method according to claim 2, characterized in that the at least one event has an association with whether a TA timer of the SDT has expired and/or whether the amount of change in reference signal received power, RSRP, measured by the terminal device exceeds an RSRP change amount threshold.
The method of claim 1, wherein the recording of the first information is triggered based on at least one event comprising one or more of:

The SDT is triggered after the TA timer of the SDT expires;

The TA timer of the SDT is overtime, and the variation of the RSRP measured by the terminal equipment does not exceed the RSRP variation threshold;

after triggering configuration authorization CG-SDT by the terminal equipment, the TA timer of the SDT is overtime;

The TA timer of the SDT is overtime, and the terminal equipment detects that the target SSB meets the measurement threshold for triggering the CG-SDT, wherein the target synchronous signal block SSB is associated with CG resources; or alternatively

The TA timer of the SDT does not time out and the amount of change in RSRP measured by the terminal device exceeds an RSRP change amount threshold.
The method of claim 4, wherein the SDT is triggered after a TA timer of the SDT expires, comprising: after the TA timer of the SDT is overtime, the SDT is triggered, and the time interval between the triggering time of the SDT and the overtime of the TA timer of the SDT does not exceed a first threshold value.
The method of any one of claims 1-5, wherein the first information comprises one or more of the following:

The duration of the TA timer of the SDT;

the SDT-associated signal measurement information;

a transmission or reception time of a radio resource control RRC release message;

The time when the terminal equipment enters the inactive state;

The trigger time of the SDT;

a time interval between the trigger time of the SDT and the RRC release message; or alternatively

The RSRP variation threshold.
A method of wireless communication, comprising:

The network device receives a first message sent by the terminal device, wherein the first message comprises first information of small data transmission SDT.
The method of claim 7, wherein the recording of the first information is triggered based on at least one event, and wherein the at least one event has an association with a time advance TA validity of the SDT.
The method according to claim 8, wherein the at least one event has an association with whether a TA timer of the SDT has expired and/or whether a change in reference signal received power, RSRP, measured by the terminal device exceeds an RSRP change threshold.
The method of claim 7, wherein the recording of the first information is triggered based on at least one event comprising one or more of:

The SDT is triggered after the TA timer of the SDT expires;

The TA timer of the SDT is overtime, and the variation of the RSRP measured by the terminal equipment does not exceed the RSRP variation threshold;

after triggering configuration authorization CG-SDT by the terminal equipment, the TA timer of the SDT is overtime;

The TA timer of the SDT is overtime, and the terminal equipment detects that the target SSB meets the measurement threshold for triggering the CG-SDT, wherein the target synchronous signal block SSB is associated with CG resources; or alternatively

The TA timer of the SDT does not time out and the amount of change in RSRP measured by the terminal device exceeds an RSRP change amount threshold.
The method of claim 10, wherein the SDT is triggered after a TA timer of the SDT expires, comprising: after the TA timer of the SDT is overtime, the SDT is triggered, and the time interval between the triggering time of the SDT and the overtime of the TA timer of the SDT does not exceed a first threshold value.
The method according to any of claims 7-11, wherein the first information comprises one or more of the following information:

The duration of the TA timer of the SDT;

the SDT-associated signal measurement information;

a transmission or reception time of a radio resource control RRC release message;

The time when the terminal equipment enters the inactive state;

The trigger time of the SDT;

a time interval between the trigger time of the SDT and the RRC release message; or alternatively

The RSRP variation threshold.
A terminal device, comprising:

and the sending unit is used for sending a first message to the network equipment, wherein the first message comprises first information of the small data transmission SDT.
The terminal device of claim 13, wherein the recording of the first information is triggered based on at least one event, and wherein the at least one event has an association with a time advance TA validity of the SDT.
The terminal device according to claim 14, wherein the at least one event has an association with whether a TA timer of the SDT has expired and/or whether a change in reference signal received power, RSRP, measured by the terminal device exceeds an RSRP change threshold.
The terminal device of claim 13, wherein the recording of the first information is triggered based on at least one event comprising one or more of:

The SDT is triggered after the TA timer of the SDT expires;

The TA timer of the SDT is overtime, and the variation of the RSRP measured by the terminal equipment does not exceed the RSRP variation threshold;

after triggering configuration authorization CG-SDT by the terminal equipment, the TA timer of the SDT is overtime;

The TA timer of the SDT is overtime, and the terminal equipment detects that the target SSB meets the measurement threshold for triggering the CG-SDT, wherein the target synchronous signal block SSB is associated with CG resources; or alternatively

The TA timer of the SDT does not time out and the amount of change in RSRP measured by the terminal device exceeds an RSRP change amount threshold.
The terminal device of claim 16, wherein the SDT is triggered after a TA timer of the SDT expires, comprising: after the TA timer of the SDT is overtime, the SDT is triggered, and the time interval between the triggering time of the SDT and the overtime of the TA timer of the SDT does not exceed a first threshold value.
The terminal device according to any of claims 13-17, wherein the first information comprises one or more of the following information:

The duration of the TA timer of the SDT;

the SDT-associated signal measurement information;

a transmission or reception time of a radio resource control RRC release message;

The time when the terminal equipment enters the inactive state;

The trigger time of the SDT;

a time interval between the trigger time of the SDT and the RRC release message; or alternatively

The RSRP variation threshold.
A network device, comprising:

And the receiving unit is used for receiving a first message sent by the terminal equipment, wherein the first message comprises first information of the small data transmission SDT.
The network device of claim 19, wherein the recording of the first information is triggered based on at least one event, and wherein the at least one event has an association with a time advance TA validity of the SDT.
The network device according to claim 20, wherein the at least one event has an association with whether a TA timer of the SDT has expired and/or whether a change in reference signal received power, RSRP, measured by the terminal device exceeds an RSRP change threshold.
The network device of claim 19, wherein the recording of the first information is triggered based on at least one event comprising one or more of:

The SDT is triggered after the TA timer of the SDT expires;

The TA timer of the SDT is overtime, and the variation of the RSRP measured by the terminal equipment does not exceed the RSRP variation threshold;

after triggering configuration authorization CG-SDT by the terminal equipment, the TA timer of the SDT is overtime;

The TA timer of the SDT is overtime, and the terminal equipment detects that the target SSB meets the measurement threshold for triggering the CG-SDT, wherein the target synchronous signal block SSB is associated with CG resources; or alternatively

The TA timer of the SDT does not time out and the amount of change in RSRP measured by the terminal device exceeds an RSRP change amount threshold.
The network device of claim 22, wherein the SDT is triggered after a TA timer of the SDT expires, comprising: after the TA timer of the SDT is overtime, the SDT is triggered, and the time interval between the triggering time of the SDT and the overtime of the TA timer of the SDT does not exceed a first threshold value.
The network device of any of claims 19-23, wherein the first information comprises one or more of the following:

The duration of the TA timer of the SDT;

the SDT-associated signal measurement information;

a transmission or reception time of a radio resource control RRC release message;

The time when the terminal equipment enters the inactive state;

The trigger time of the SDT;

a time interval between the trigger time of the SDT and the RRC release message; or alternatively

The RSRP variation threshold.
A terminal device comprising a memory for storing a program, a processor for invoking the program in the memory, and a communication interface, to cause the terminal device to perform the method of any of claims 1-6.
A network device comprising a memory for storing a program, a processor for invoking the program in the memory to cause the network device to perform the method of any of claims 7-12, and a communication interface.
An apparatus comprising a processor configured to invoke a program from memory to perform the method of any of claims 1-6.
An apparatus comprising a processor configured to invoke a program from memory to perform the method of any of claims 7-12.
A chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1-6.
A chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 7-12.
A computer-readable storage medium, characterized in that a program is stored thereon, which program causes a computer to execute the method according to any one of claims 1-6.
A computer-readable storage medium, characterized in that a program is stored thereon, which program causes a computer to perform the method according to any of claims 7-12.
A computer program product comprising a program for causing a computer to perform the method of any one of claims 1-6.
A computer program product comprising a program for causing a computer to perform the method of any one of claims 7-12.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1-6.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 7-12.