Timer activation method, device, terminal and storage medium

Abstract

The present application discloses a timer startup method, device, terminal, and storage medium, which belongs to the field of wireless communication technology. The method includes: determining a control parameter of a response time window timer based on the round-trip delay (RTT) between the terminal and the network-side device; after the terminal performs the uplink transmission, starting the response time window timer corresponding to the uplink transmission based on the control parameter; for the response time window timer corresponding to the uplink transmission corresponding to the uplink small data, the terminal can more accurately determine the start time offset and / or timer duration of the timer based on the RTT between the terminal and the network-side device, thereby more accurately controlling the time for monitoring the response from the network side, thereby achieving accurate reception of the above response and improving the transmission effect of the uplink small data.

Description

[0001] This application is a divisional application of the invention patent application with the application date of January 14, 2021, application number 202180071607.7, and invention name “Timer startup method, device, terminal and storage medium”. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a timer starting method, device, terminal and storage medium. Background Art

[0003] Small data transmission is a technology that enables a terminal to perform data transmission in an RRC_IDLE state (i.e., idle state) or an RRC_INACTIVE state (i.e., inactive state) based on energy-saving considerations.

[0004] In small data transmission technology, in order to ensure the success rate of data transmission, relevant technologies propose that after the terminal sends data during the small data transmission process, it can start a response time window timer. During the operation of the response time window timer, the terminal monitors the network side's response to the small data transmission, and determines whether to retransmit based on the monitoring situation. Summary of the Invention

[0005] The present invention provides a method, device, terminal, and storage medium for starting a timer. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides a timer start method, which is executed by a terminal, and the method includes:

[0007] Determine, based on the round-trip delay RTT between the terminal and the network-side device, a control parameter of the response time window timer; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission corresponding to the uplink small data and the start time of the response time window timer for the uplink transmission;

[0008] After the terminal performs the uplink transmission, a response time window timer corresponding to the uplink transmission is started based on the control parameter.

[0009] On the one hand, an embodiment of the present application provides an uplink early acquisition method, which is executed by a terminal and includes:

[0010] Before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability, obtaining a serving link TA of the terminal based on the positioning capability and ephemeris information;

[0011] Based on the service link TA, the TA of the terminal is acquired.

[0012] On the other hand, an embodiment of the present application provides a timer starting device for use in a terminal, the device comprising:

[0013] A parameter determination device, configured to determine a control parameter of a response time window timer based on a round-trip delay (RTT) between the terminal and the network-side device; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission corresponding to the uplink small data and the start time of the response time window timer for the uplink transmission;

[0014] A timer starting module is used to start a response time window timer corresponding to the uplink transmission based on the control parameter after the terminal performs the uplink transmission.

[0015] On the other hand, an embodiment of the present application provides an uplink early acquisition device for use in a terminal, the device comprising:

[0016] A first uplink advance acquisition module is configured to acquire a serving link TA of the terminal based on the positioning capability and ephemeris information before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability;

[0017] The second uplink advance acquisition module is configured to acquire the TA of the terminal based on the serving link TA.

[0018] On the other hand, an embodiment of the present application provides a computer device, which includes a processor, a memory and a transceiver, wherein the memory stores a computer program, and the computer program is used to be executed by the processor to implement the above-mentioned timer start method or uplink early acquisition method.

[0019] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above-mentioned timer start method or uplink early acquisition method.

[0020] In another aspect, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the above-described timer start method or uplink early acquisition method.

[0021] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0022] For the response time window timer corresponding to the uplink transmission corresponding to the uplink small data, the terminal can more accurately determine the start time offset and / or timer duration of the timer based on the RTT between the terminal and the network side device, thereby more accurately controlling the time for monitoring the response from the network side, and then achieving accurate reception of the above response, thereby improving the transmission effect of the uplink small data. In addition, it can also avoid the terminal from unnecessary monitoring of the downlink control signal, thereby achieving the effect of terminal power saving. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

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

[0025] Figure 2 This is a network architecture diagram of an NTN system provided by an embodiment of the present application;

[0026] Figure 3 This is a flowchart of a timer starting method provided by an embodiment of the present application;

[0027] Figure 4 This is a flowchart of an uplink early acquisition method provided by an embodiment of the present application;

[0028] Figure 5 This is a flowchart of an uplink transmission method provided by an embodiment of the present application;

[0029] Figure 6 This is a UE behavior timing diagram provided by an embodiment of the present application;

[0030] Figure 7 This is a UE behavior timing diagram provided by an embodiment of the present application;

[0031] Figure 8 This is a UE behavior timing diagram provided by an embodiment of the present application;

[0032] Figure 9 This is a UE behavior timing diagram provided by an embodiment of the present application;

[0033] Figure 10 is a block diagram of a timer starting device provided by one embodiment of the present application;

[0034] Figure 11 This is a block diagram of an uplink early acquisition device provided by an embodiment of the present application;

[0035] Figure 12 It is a structural diagram of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0037] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0038] Please refer to Figure 1 , which shows a schematic diagram of a network architecture of a communication system provided by an embodiment of the present application. The network architecture may include: a terminal 10 and a base station 20.

[0039] There are usually multiple terminals 10, and one or more terminals 10 can be distributed in the cell managed by each base station 20. The terminals 10 can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of user equipment (UE), mobile stations (MS), terminal devices, etc. For ease of description, in the embodiments of the present application, the above-mentioned devices are collectively referred to as terminals.

[0040] The base station 20 is a device deployed in the access network to provide wireless communication functions for the terminal 10. The base station 20 may include various forms of satellite base stations, macro base stations, micro base stations, relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in the 5G New Radio (NR) system, it is called gNodeB or gNB. With the evolution of communication technology, the name "base station" may change. For the convenience of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal 10 are collectively referred to as base stations.

[0041] Optional, Figure 1What is not shown is that the above network architecture also includes other network devices, such as: Central Network Control (CNC), Access and Mobility Management Function (AMF) device, Session Management Function (SMF) or User Plane Function (UPF) device, etc.

[0042] The "5G NR system" in the embodiments of the present disclosure may also be referred to as a 5G system or an NR system, but those skilled in the art will understand the meaning thereof. The technical solutions described in the embodiments of the present disclosure may be applicable to the 5G NR system, to subsequent evolved systems of the 5G NR system, or to systems prior to the 5G NR system, such as the Long Term Evolution (LTE) system.

[0043] Before introducing the solutions shown in the subsequent embodiments of this application, several noun concepts involved in this application are first introduced.

[0044] 1) 5G NR system

[0045] The 5G NR system is a next-generation wireless communication system designed to meet user requirements for wireless communication speed, latency, high-speed mobility, and energy efficiency, as well as the diverse and complex wireless communication services of tomorrow. The main application scenarios for the 5G system include enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0046] In the 5G network environment, in order to reduce air interface signaling and quickly restore wireless connections and data services, a new Radio Resource Control (RRC) state is defined, namely the RRC inactive state (RRC_INACTIVE). This state is different from the RRC idle state (RRC_IDLE) and RRC connected state (RRC_ACTIVE). The above three RRC states are as follows:

[0047] RRC_IDLE: Mobility is based on UE cell selection and reselection, paging is initiated by the CN, the paging area is configured by the CN, there is no UE AS context on the base station side, and there is no RRC connection between the UE and the base station.

[0048] RRC_CONNECTED: An RRC connection exists between the UE and the base station, and a UE AS context exists between the base station and the UE. The network knows the UE's location at the cell level. Mobility is controlled by the network. Unicast data can be transmitted between the UE and the base station.

[0049] RRC_INACTIVE: Mobility is based on UE cell selection and reselection. There is a connection between CN and NR. The UE AS context exists on a certain base station. Paging is triggered by the Radio Access Network (RAN). The RAN-based paging area is managed by the RAN. The network side knows the UE location based on the RAN paging area level.

[0050] 2) Non-terrestrial Network (NTN)

[0051] Relevant standards organizations are currently researching NTN technology, which generally uses satellite communications to provide communications services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages. First, satellite communications are not restricted by user location. For example, conventional terrestrial communications cannot cover areas such as oceans, high mountains, and deserts where communications equipment cannot be deployed or where there is a sparse population. However, satellite communications, because a single satellite can cover a large area and orbits the Earth, theoretically every corner of the globe can be covered. Second, satellite communications have significant social value. Satellite communications can provide low-cost coverage in remote mountainous areas and poor, underdeveloped countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting their development. Third, satellite communications offer long range, and the cost of communications does not increase significantly with increasing distance. Finally, satellite communications are highly stable and unaffected by natural disasters.

[0052] Communication satellites are categorized by their orbital altitude into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), Geostationary Earth Orbit (GEO), and High Elliptical Orbit (HEO). Currently, the primary research focus is on NTN technology for LEO and GEO satellites.

[0053] LEO satellites: Low-orbit satellites have an altitude range of 500 km to 1500 km, with an orbital period of approximately 1.5 to 2 hours. Signal propagation delay for single-hop communication between users is typically less than 20 ms. The maximum satellite visibility time is 20 minutes. Signal propagation distances are short, link loss is minimal, and the transmit power requirements for user terminals are low.

[0054] GEO satellites: Geosynchronous Earth Orbit satellites orbit at an altitude of 35,786 km and revolve around the Earth every 24 hours. The signal propagation delay for single-hop communication between users is typically 250 milliseconds.

[0055] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0056] Satellite beam: A satellite beam is the smallest unit of coverage provided by a satellite, corresponding to different directions. Typically, a single satellite uses hundreds or thousands of satellite beams to provide coverage. These satellite beams can be deployed as separate cells or within the same cell. To account for the potential for co-channel interference between adjacent satellite beams, a frequency reuse factor greater than 1 is typically used. This means that adjacent satellite beams are distinguished by using different frequencies / carriers / bands.

[0057] Currently, the R17 NTN standardization focuses on two NTN scenarios: transparent payload NTN and regenerated payload NTN. An NTN network typically consists of the following network elements:

[0058] 1. One or more gateways to connect satellites and terrestrial public networks.

[0059] 2. Feeder link: The link used for communication between the gateway and the satellite.

[0060] 3. Service link: The link used for communication between the terminal and the satellite.

[0061] 4. Satellite: Based on the functions it provides, it can be divided into two types: satellite based on transparent payload and satellite based on regenerative payload.

[0062] Transparent payload: The satellite only provides the functions of wireless frequency filtering, frequency conversion and amplification, that is, it only provides transparent forwarding of signals and does not change the waveform signal it forwards.

[0063] Regenerative payload: In addition to providing wireless frequency filtering, frequency conversion and amplification functions, satellites can also provide demodulation / decoding, routing / conversion, encoding / modulation functions. In other words, satellites have some or all of the functions of base stations.

[0064] 5. Intersatellite link: A link used for communication between satellites in a regenerative payload scenario.

[0065] Please refer to Figure 2 , which shows a network architecture diagram of the NTN system provided by an embodiment of the present application. Figure 2 As shown, the NTN system includes a terminal 201, a satellite 202, and a gateway device 203. Satellites 202 and gateway device 203 are wirelessly connected (feeder links), satellites 202 are wirelessly connected to each other (intersatellite links), and gateway device 203 is connected to a data network. Satellites 202 cover the Earth's surface via multiple satellite beams 202a, each covering a specific area. When a terminal 201 is within the coverage area of ​​a satellite beam 202a, it can initiate a random access request to establish a service link with base station 202 and conduct subsequent communications.

[0066] 3) Early Data Transmission (EDT)

[0067] EDT is introduced in LTE. During this process, the UE can always remain in the RRC-IDLE state, the suspended state, or the RRC_INACTIVE state to complete the transmission of small uplink and / or downlink data packets. For example, the process of the user plane transmission solution of EDT can be as follows:

[0068] S1: The UE selects one of the preambles from the group of preambles used to indicate EDT and sends it to the eNB, initiating the EDT transmission process. After receiving the corresponding preamble, the eNB configures uplink resources and TA for the UE through the RAR;

[0069] In step S2, the UE sends an RRCConnectionResumeRequest message to the eNB, including the Resume ID, the establishment cause, and the authentication token (shortResumeMAC-I). The UE resumes all signaling radio bearers (SRBs) and data radio bearers (DRBs) and derives new keys using the NextHopChaining Count (NCC) parameter included in the previous connection release message. User data is encrypted and transmitted on the Dedicated Traffic Channel (DTCH) and multiplexed with the RRCConnectionResumeRequest.

[0070] In S3, the eNB establishes an S1 connection, initiates a context recovery process to the Mobility Management Entity (MME), and reactivates the bearer between S1 and U.

[0071] S4, MME initiates a request to the Serving GateWay (S-GW) to reactivate the bearer between UE S1 and UE U for subsequent user data delivery to the S-GW.

[0072] S5: The MME confirms the restoration of the UE context to the eNB.

[0073] S6: User data is delivered to S-GW.

[0074] S7: If the S-GW has downlink data to send at this time, the S-GW delivers the downlink data to Enb.

[0075] S8: The eNB suspends the S1 connection, and the MME deactivates the UE S1-U bearer.

[0076] S9: The eNB sends an RRCConnectionRelease message to the UE to keep the UE in the suspended state.

[0077] For the above data transmission, the UE actually completes the transmission of small data packets without entering the connected state. The network configures a maximum transport block size (TBS) allowed by the current network in SIB2. The UE determines the amount of data to be transmitted. If it is less than the advertised maximum TB size, the UE can initiate EDT transmission. Otherwise, the UE uses the normal connection establishment process to enter the connected state to transmit data.

[0078] 4) Transmission based on preconfigured uplink resources (PUR)

[0079] LTE Release 16 further enhances uplink small data transmission in Narrowband Internet of Things (NB-IoT) and Enhanced Machine Type Communication (eMTC) scenarios, introducing a method for using pre-configured uplink resources (PURs) for data transmission in the IDLE state. When the cell in which a UE is located supports PUR transmission, the UE can request PUR configuration in the connected state using a PURConfigurationRequest. The PURConfigurationRequest optionally includes the requested PUR period, TBS, number of PURs, etc. The (ng-)eNB configures the PUR for the UE by including the PUR-Config field in the RRCConnectinRelease message and simultaneously releases the UE to the IDLE state. The PUR configuration is determined by the (ng-)eNB and may be based on the UE's request, UE registration information, and / or local policy.

[0080] The PUR 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.

[0081] In the user plane function optimization solution for the Evolved Packet System (EPS) / 5G System (5GS) cellular IoT, the following prerequisites must be met before a UE in the IDLE state uses the PUR for data transmission:

[0082] 1. Effective TA: The following two conditions must be met:

[0083] If the PUR-Time Alignment Timer is configured: the MAC layer confirms that the PUR-TimeAlignmentTimer is running;

[0084] If the Reference Signal Receiving Power (RSRP) change threshold (i.e., PUR-RSRP-ChangeThreshold or PUR-NRSRP-ChangeThreshold) is configured: the change (increase or decrease) of RSRP since the last TA validity verification is not greater than the configured RSRP change threshold.

[0085] 2. NCC; included in the RRCConnectionRelease message, used for the derivation of new keys;

[0086] 3. Effective PUR;

[0087] 4. There is a need to establish or restore an RRC connection, such as uplink data arriving;

[0088] For the EPS / 5GS cellular IoT user plane function optimization solution, the process of using PUR for data transmission by a UE in the IDLE state can be as follows:

[0089] S1, UE meets the above PUR transmission prerequisites;

[0090] In step S2, the UE sends an RRCConnectionResumeRequest message to the eNB / ng-eNB, including the Resume ID (for EPS scenarios) / Inactive-Radio Network Temporary Identity (I-RNTI) (for 5GS scenarios), establishment cause, and shortResumeMAC-I. The Resume ID / IRNTI is used by the base station to identify the context of the UE in the suspended state, and shortResumeMAC-I is used for identity authentication. The UE resumes all SRBs and DRBs, derives new keys using the NCC contained in the RRCConnectionRelease message of the last connection, and user data is encrypted and transmitted on the DTCH, multiplexed with the RRCConnectionResumeRequest message on the Common Control Channel (CCCH).

[0091] S3 executes the same steps as the MO-EDT transmission process under the EPS / 5GS cellular IoT user plane function optimization solution.

[0092] S4: After the eNB / ng-eNB delivers the user data to the core network, it keeps the UE in the IDLE state through the RRCConnectionRelease message. The RRCConnectionRelease message contains the following information:

[0093] a) Release Cause is set to RRC-Suspend;

[0094] b) resume ID / I-RNTI;

[0095] c) NCC;

[0096] d)DRB-ContinueROHC.

[0097] If the network has downlink data to send, it is encrypted and transmitted through the DTCH and multiplexed with the RRCConnectionRelease message on the dedicated control channel (DedicatedControl CHannel, DCCH).

[0098] To support PUR transmission, the RRC layer provides the following configuration parameters to the MAC layer:

[0099] PUR-RNTI; PUR response window length (PUR-ResponseWindowSize); uplink (Uplink, UL) authorization configuration information.

[0100] After the UE transmits using the PUR, if the last subframe used for uplink physical shared channel (PUSCH) transmission is subframe n, the UE starts the pur-ResponseWindowTimer in subframe n+4 and monitors the physical downlink control channel (PDCCH) scrambled by the PUR-RNTI during the operation of the pur-ResponseWindowTimer.

[0101] The duration of PUR-ResponseWindowTimer is PUR-ResponseWindowSize.

[0102] During the operation of PUR-ResponseWindowTimer, if the UE receives a PDCCH scrambled by PUR-RNTI and the PDCCH indicates an uplink grant for uplink retransmission, the UE retransmits on the uplink grant resources. Assuming that the last subframe used for the retransmitted PUSCH transmission is subframe m, the UE restarts PUR-ResponseWindowTimer in subframe m+4.

[0103] If the MAC layer receives an L1 ACK for the PUR transmission from the lower layer, or the UE receives a PDCCH scrambled with the PUR-RNTI and the MAC layer protocol data unit (PDU) is successfully decoded, the UE stops the PUR-ResponseWindowTimer. Otherwise, if the MAC layer receives a backoff indication for the PUR transmission from the lower layer, the UE stops the PUR-ResponseWindowTimer, indicates to the upper layer that the PUR backoff indication has been received, and discards the PUR-RNTI.

[0104] If the PUR-ResponseWindowTimer times out, the MAC layer indicates to the upper layer that the uplink transmission using the PUR has failed and discards the PUR-RNTI.

[0105] In order for the UE to maintain the TA and thus use the PUR for small data transmission, the upper layer can configure a timer PUR-TimeAlignmentTimer for the MAC layer.

[0106] When the MAC layer receives the PUR-TimeAlignmentTimer configuration from the upper layer, if the PUR-TimeAlignmentTimer is not running, it starts the PUR-TimeAlignmentTimer.

[0107] When the MAC layer receives the release of the PUR-TimeAlignmentTimer configuration from the higher layer, if the PUR-TimeAlignmentTimer is running, it stops the PUR-TimeAlignmentTimer.

[0108] If a Timing Advance Command (TAC) MAC layer control element (CE) or PDCCH indicating TA adjustment is received, the TA is adjusted based on the TAC MAC CE or PDCCH indication, and the PUR-TimeAlignmentTimer is started or restarted at the same time.

[0109] When determining the validity of the TA, the MAC layer may be asked to confirm whether the TA timer is in operation. When the TA timer times out, the MAC layer needs to provide feedback to the upper layer.

[0110] Rel-17 launched a project to study small data transmission under RRC_INACTIVE. The project objectives mainly focus on two directions: uplink small data transmission based on random access process (two-step / four-step) and uplink small data transmission based on pre-configured resources, such as configured grant (CG) type 1.

[0111] In the related art, on the one hand, considering the conversion time between the terminal's sending and receiving operations, the UE will wait for 4 subframes after using PUR to send small data before starting the UPR response window timer. The currently supported 4ms interval mainly considers the terminal processing delay after the terminal sends the uplink (for example, for NB-IoT, the UE needs to switch from uplink transmission to downlink reception), and the fastest round-trip delay RTT from the UE sending the uplink to receiving the network response. In the terrestrial network, the RTT time of signal transmission between the UE and the network is relatively short, so the time interval from the UE sending the uplink to starting the PUR response window timer mainly depends on the terminal's processing delay.

[0112] Compared with traditional terrestrial cellular networks, the signal propagation delay between UE and network in NTN increases significantly. Its RTT can even be much longer than the terminal processing time considered in existing standards. Therefore, the value of the PUR response window timer start time offset value needs to be redefined for NTN.

[0113] On the other hand, in LTE terrestrial networks, the UE's TA is fully controlled by the network. A UE in the RRC-IDLE state must verify the validity of its TA before using the PUR for uplink transmission. Only when the TA is valid can the PUR be used for uplink transmission. Currently, R17 NTN supports UEs with both Global Navigation Satellite System (GNSS) positioning capabilities and TA pre-compensation capabilities. For this type of UE, there is no solution in the relevant technology to estimate TA based on its own positioning capabilities.

[0114] The Small Data Transmission (SDT) currently under research in Release 17 NR presents similar challenges to PUR transmission in LTE when a UE in the RRC INACTIVE state uses the CG for small data transmission. For example, how does the UE determine a valid TA before using the CG for transmission? When does the UE start monitoring the network response after completing the small data transmission using the CG?

[0115] The solutions shown in the subsequent embodiments of this application propose a solution in which a terminal adjusts the monitoring start time and / or monitoring duration when transmitting uplink small data, and the terminal actively estimates the TA. For example, the solution involved in this application can be applied in communication scenarios such as NTN networks where the round-trip propagation delay of wireless signals between the terminal and the network side is large. This allows the terminal to obtain a more accurate TA when transmitting uplink small data, and more accurately control the time to monitor the response from the network side, thereby improving the transmission effect of uplink small data. In addition, it can also avoid unnecessary monitoring by the terminal, thereby achieving the purpose of terminal power saving.

[0116] Please refer to Figure 3 , which shows a timer start method provided by an embodiment of the present application. The method can be executed by a terminal, wherein the terminal can be Figure 1 or Figure 2 The method may include the following steps:

[0117] Step 301, based on the round-trip delay RTT between the terminal and the network side device, determine the control parameters of the response time window timer; the control parameters include at least one of the start time offset of the timer and the timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission corresponding to the uplink small data and the start time of the response time window timer for the uplink transmission.

[0118] Step 302: After the terminal performs the uplink transmission, start a response time window timer corresponding to the uplink transmission based on the control parameter.

[0119] To sum up, in the scheme shown in the embodiment of the present application, for the response time window timer corresponding to the uplink transmission corresponding to the uplink small data, the terminal can more accurately determine the start time offset and / or timer duration of the timer based on the RTT between the terminal and the network side device, thereby more accurately controlling the time for monitoring the response from the network side, and then achieving accurate reception of the above response, improving the transmission effect of the uplink small data, and also avoiding unnecessary monitoring by the terminal, thereby achieving the purpose of saving power for the terminal.

[0120] Please refer to Figure 4 , which shows an uplink early acquisition method provided by an embodiment of the present application. The method can be executed by a terminal, wherein the terminal can be Figure 1 or Figure 2 The method may include the following steps:

[0121] Step 401 : Before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability, the terminal's service link TA is acquired based on the positioning capability and ephemeris information.

[0122] The ephemeris information mentioned above refers to the satellite ephemeris corresponding to the satellites in the NTN system. Satellite ephemeris, also known as two-line orbital element (TLE), is an expression used to describe the position and velocity of a spacecraft (also known as a two-line orbital data system).

[0123] Satellite ephemeris uses the mathematical relationship between the six orbital parameters of Kepler's law to determine the time, coordinates, direction, speed and other parameters of the flying object with extremely high accuracy.

[0124] Satellite ephemeris can accurately calculate, predict, depict and track the time, position, speed and other operating status of satellites and flying objects; it can express the precise parameters of flying objects such as celestial bodies, satellites, spacecraft, missiles and space debris; it can place flying objects in three-dimensional space; and it can use time to depict the past, present and future of celestial bodies in three dimensions.

[0125] The time of the satellite ephemeris is calculated according to the world standard time, namely the Coordinated Universal Time (UTC); the satellite ephemeris can be updated regularly.

[0126] In a possible implementation, the service link is a link between a terminal and a satellite in the NTN network. Correspondingly, the service link TA (ie, TA_service link) is the TA that needs to be compensated due to the influence of the service link.

[0127] Step 402: Based on the service link TA, obtain the TA of the terminal.

[0128] The TA of the terminal refers to the TA used by the terminal during uplink transmission.

[0129] Since the distance between the terminal and the satellite in the NTN network is usually large and may also vary greatly, the distance between the terminal and the satellite will also have a great impact on the relationship between the two. In order to ensure that the wireless signal sent by the terminal can be received by the satellite at the correct time point, in an embodiment of the present application, the terminal can obtain the service link TA based on the positioning capability and ephemeris information, and then estimate the terminal's TA based on the service link TA.

[0130] In summary, in the solution shown in the embodiment of the present application, when a service link exists between the terminal and the network-side device, the terminal can combine the positioning capability and ephemeris information to obtain the service link TA that needs to be compensated due to the distance influence of the service link in the NTN, and then obtain the terminal's TA based on the service link TA, thereby achieving accurate prediction of the TA required for the terminal to perform uplink transmission, minimizing the impact of the communication distance between the terminal and the satellite in the NTN network on the uplink transmission corresponding to the uplink small data, and improving the accuracy of the uplink transmission in the NTN network.

[0131] Among them, the above Figure 3 The control scheme of the response time window timer provided by the embodiment shown is consistent with the above Figure 4 The solution for performing TA prediction by a terminal provided in the illustrated embodiment can be used independently.

[0132] Alternatively, the above Figure 3 The control scheme of the response time window timer provided by the embodiment shown is consistent with the above Figure 4 The terminal's TA prediction scheme provided in the illustrated embodiment can also be used in combination. For example, in an NTN network, the terminal can first predict the TA and, based on the RTT, obtain a start time offset and / or timer duration for the response time window timer. The terminal then performs uplink transmission corresponding to small uplink data based on the predicted TA and, after the uplink transmission, starts the response time window timer based on the timer start time offset and / or timer duration.

[0133] With the above Figure 3 The control scheme of the response time window timer provided by the embodiment shown is consistent with the above Figure 4 The embodiment shown in the figure provides a terminal for TA prediction. Figure 5 , which shows an uplink transmission method provided by an embodiment of the present application. The method can be executed by a terminal, wherein the terminal can be Figure 1 or Figure 2 The method may include the following steps:

[0134] Step 501: When the terminal has positioning capability and TA pre-compensation capability, the service link TA of the terminal is acquired based on the positioning capability and ephemeris information.

[0135] In a possible implementation manner, the terminal is a terminal in a non-radio resource control RRC connected state.

[0136] The above-mentioned terminal being in a non-RRC connected state may mean that the terminal is in an RRC_IDLE state, or in an RRC_INACTIVE state.

[0137] In an embodiment of the present application, in an NTN network, the UE can locate its own position based on its positioning capability, and can calculate the position of the serving satellite based on the ephemeris information. The distance of the serving link service link can be calculated based on these two position information. The distance of the serving link and the propagation rate of the wireless signal can be used to calculate the time delay (delay) for the wireless signal sent by the terminal to propagate to the location of the satellite. Based on this delay, the serving link TA can be calculated. For example, the serving link TA = 2*delay.

[0138] Step 502: Based on the service link TA, obtain the TA of the terminal.

[0139] The NTN system can include different network architectures. For example, the current NTN includes NTN based on transparent forwarding architecture and NTN based on regenerative forwarding architecture. Different NTN architectures have different corresponding ways of obtaining the terminal's TA based on the service link TA.

[0140] In one possible implementation, when the network where the terminal is located is an NTN based on a transparent forwarding architecture, and the terminal receives a public TA indicated by the system, the sum of the service link TA and the public TA is used as the TA of the terminal;

[0141] In an exemplary solution of an embodiment of the present application, if the current NTN is an NTN based on a transparent forwarding architecture and the system indicates a common TA (common TA), for example, indicating the TA for the NTN cell through broadcasting or other means, the TA of the terminal can be set to the service link TA + common TA.

[0142] In an exemplary solution, the system may also indicate the above-mentioned public TA through other methods besides broadcasting, for example, through RRC signaling, downlink control information, etc. The embodiment of the present application does not limit the method in which the system indicates the public TA.

[0143] In a possible implementation, when the network where the terminal is located is an NTN based on a transparent forwarding architecture and the terminal does not receive a public TA indicated by the system, the service link TA is used as the TA of the terminal.

[0144] In an exemplary solution of the embodiment of the present application, if the current NTN is an NTN based on a transparent forwarding architecture and the system does not indicate a public TA, the terminal can directly use the above service link TA as the TA of the terminal.

[0145] In a possible implementation, when the network where the terminal is located is an NTN based on a regeneration and forwarding architecture, the service link TA is used as the TA of the terminal.

[0146] In an exemplary solution of the embodiment of the present application, if the current NTN is an NTN based on a regeneration and forwarding architecture, the terminal may directly use the service link TA as the TA of the terminal.

[0147] In one possible implementation, before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability, without performing validity verification on the TA maintained by the terminal, the service link TA of the terminal is obtained based on the positioning capability and ephemeris information, and the TA of the terminal is obtained based on the service link TA.

[0148] In an embodiment of the present application, for a terminal in an NTN, when the terminal has positioning capability and TA pre-compensation capability and is in an RRC_IDLE state or an RRC_INACTIVE state, it is not necessary to perform validity verification on the TA maintained by itself, and directly obtain the service link TA of the terminal based on the positioning capability and ephemeris information, and obtain the TA of the terminal based on the service link TA.

[0149] In another possible implementation, before the terminal performs uplink transmission corresponding to uplink small data, the validity of the TA maintained by the terminal can be checked; when the TA maintained by the terminal fails the validity check and the terminal has positioning capability and TA pre-compensation capability, the terminal can obtain the service link TA of the terminal based on the positioning capability and ephemeris information, and obtain the terminal's TA based on the service link TA.

[0150] In an embodiment of the present application, for a terminal in an NTN, when the terminal has positioning capability and TA pre-compensation capability and is in an RRC_IDLE state or an RRC_INACTIVE state, if there is a need to send uplink small data, the TA maintained by the terminal can be first verified for validity. If the TA maintained by the terminal fails the validity check, when the terminal has positioning capability and TA pre-compensation capability, it can obtain the service link TA of the terminal based on the positioning capability and ephemeris information, and obtain the terminal's TA based on the service link TA.

[0151] In a possible implementation, when the TA maintained by the terminal passes the validity check, the TA maintained by the terminal is used as the TA of the terminal.

[0152] In an embodiment of the present application, for a terminal in an NTN, when the terminal has positioning capability and TA pre-compensation capability and is in an RRC_IDLE state or an RRC_INACTIVE state, if there is a need to send small uplink data, the TA maintained by the terminal can be first verified for validity. If the TA maintained by the terminal passes the validity check, the terminal does not need to reacquire the TA, that is, the currently maintained TA can be directly used.

[0153] After the terminal determines the TA of the terminal, when there is small uplink data, uplink transmission can be performed based on the TA of the terminal.

[0154] Step 503: Determine a control parameter of a response time window timer based on the round-trip delay (RTT) between the terminal and the network device.

[0155] Among them, the control parameter includes at least one of the timer start time offset and the timer duration; the timer start time offset is the time interval between the end time of the uplink transmission corresponding to the uplink small data and the start time of the response time window timer for the uplink transmission.

[0156] In an embodiment of the present application, when the terminal has small uplink data to transmit, the start time offset and / or timer duration of the response time window timer can be determined based on the round-trip delay RTT between the terminal and the network side device, so as to control the listening time for the response from the network side after the uplink transmission corresponding to the small uplink data.

[0157] For uplink small data, the method for determining the start time offset is different when uplink transmission is performed based on different resources.

[0158] In one possible implementation, when the uplink transmission is performed based on a preconfigured uplink resource PUR, or is an uplink retransmission indicated by a physical downlink control channel PDCCH scrambled based on a PUR radio network temporary identifier PUR-RNTI, the start time offset is the maximum value of the RTT and the first time offset; or, the start time offset is the RTT.

[0159] In an embodiment of the present application, for uplink transmission performed based on PUR, or for retransmission of uplink transmission performed based on PUR, the above-mentioned start time offset can be the maximum value between RTT and the first time offset, or RTT can be directly used as the start time offset.

[0160] In a possible implementation manner, the value of the first time offset is a predefined value.

[0161] In a possible implementation, the first time offset is 4 subframes.

[0162] The first time offset may be a predefined value, for example, a value predefined by a protocol, or a value predefined by a system (for example, indicated in advance by the system through broadcast or downlink signaling).

[0163] The first time offset may be 4 subframes, or may be other time lengths, such as 3 subframes or 5 subframes.

[0164] In one possible implementation, when the uplink transmission is performed based on the configured authorized CG resources, or is an uplink retransmission indicated by the PDCCH encrypted based on the first RNTI, the start time offset can be the maximum value between the RTT and the second time offset, or it can be the RTT; wherein the first RNTI is used to indicate the retransmission scheduling for the CG transmission in the RRC_INACTIVE state.

[0165] In a possible implementation, the value of the second time offset is a predefined value.

[0166] In another possible implementation, the value of the second time offset is a time interval from when the terminal completes the first repeated transmission of the uplink transmission PUSCH to the next PDCCCH monitoring opportunity.

[0167] In another possible implementation, the value of the second time offset is a time interval from when the terminal completes the last repeated transmission of the uplink transmission PUSCH to the next PDCCCH monitoring opportunity.

[0168] In an embodiment of the present application, for uplink transmission performed based on CG resources, or for retransmission of uplink transmission performed based on CG resources, RTT can be directly used as the start time offset, or the maximum value of RTT and the second time offset can be used as the start time offset.

[0169] In a possible implementation, the timer duration is determined based on a duration offset and an initial timer duration, where the initial timer duration is configured by the network.

[0170] In an embodiment of the present application, the terminal can determine a duration offset based on the round-trip delay RTT, and adjust the timer duration based on the duration offset, that is, combine the duration offset and the initial timer duration configured by the network to determine the actual timer duration used.

[0171] In a possible implementation, the timer duration is the sum of the duration offset and the initial timer duration.

[0172] In an embodiment of the present application, when the terminal determines the actual timer duration in combination with the duration offset and the initial timer duration configured by the network, it can directly add the duration offset to the initial timer duration to obtain the above-mentioned timer duration.

[0173] Alternatively, when the terminal determines the actual timer duration in combination with the duration offset and the initial timer duration configured by the network, the terminal may also determine the timer duration in other ways, for example, directly using the duration offset as the above-mentioned timer duration, or adding half of the initial timer duration to the duration offset as the above-mentioned timer duration. The embodiment of the present application does not limit the manner in which the terminal determines the actual timer duration in combination with the duration offset and the initial timer duration configured by the network.

[0174] For uplink small data, the method for determining the duration offset is different in the case of uplink transmission based on different resources.

[0175] In a possible implementation, when the uplink transmission is a transmission performed based on a PUR, or an uplink retransmission indicated by a physical downlink control channel PDCCH scrambled based on a PUR radio network temporary identifier PUR-RNTI,

[0176] The duration offset is a difference between a maximum of the RTT and a third time offset and the third time offset;

[0177] Alternatively, the duration offset is the difference between the RTT and a third time offset.

[0178] In an embodiment of the present application, for uplink transmission performed based on PUR, or for retransmission of uplink transmission performed based on PUR, the above-mentioned duration offset for adjusting the timer duration can be the difference between the maximum value between RTT and the third time offset and the third time offset, or the difference between RTT and the third time offset can be directly used as the duration offset.

[0179] In a possible implementation manner, the value of the third time offset is a predefined value.

[0180] In a possible implementation, the third time offset is 4 subframes.

[0181] The third time offset may be a predefined value, for example, a value predefined by a protocol, or a value predefined by a system (for example, indicated in advance by the system through broadcast or downlink signaling).

[0182] The third time offset may be 4 subframes, or may be other time lengths, such as 3 subframes or 5 subframes.

[0183] The first time offset and the third time offset may be the same time offset; or the first time offset and the third time offset may be different time offsets.

[0184] In one possible implementation, when the uplink transmission is a transmission performed based on CG resources, or an uplink retransmission indicated by a PDCCH encrypted based on the first RNTI, the duration offset is the RTT.

[0185] In an embodiment of the present application, for uplink transmission performed based on CG resources, or for retransmission of uplink transmission performed based on CG resources, the difference between RTT and the fourth time offset can be used as the duration offset, or the maximum value between RTT and the fourth time offset and the difference between the fourth time offset can be used as the duration offset.

[0186] In a possible implementation manner, the value of the fourth time offset is a predefined value.

[0187] In another possible implementation, the value of the fourth time offset is a time interval from when the terminal completes the first repetitive transmission of the uplink transmission PUSCH to the next PDCCCH monitoring opportunity.

[0188] In another possible implementation, the value of the fourth time offset is a time interval from when the terminal completes the last repeated transmission of the uplink transmission PUSCH to the next PDCCCH monitoring opportunity.

[0189] In a possible implementation, the hybrid automatic repeat request HARQ process used for the uplink transmission is a HARQ process with an uplink HARQ retransmission function enabled.

[0190] In the embodiment of the present application, for the uplink HARQ process, enabling the uplink HARQ retransmission function means that the network side performs retransmission scheduling based on the decoding result of the uplink reception.

[0191] In a possible implementation, when the network where the terminal is located is a non-terrestrial communication network NTN based on a transparent forwarding architecture, the RTT is a round-trip propagation delay of a wireless signal between the terminal and a ground base station in the NTN.

[0192] Since satellites do not function as base stations in non-terrestrial communication networks (NTNs) based on a transparent forwarding architecture, the round-trip delay between the terminal and the network is the delay associated with the round-trip propagation of wireless signals between the terminal and the ground base station. In other words, the RTT corresponds to the sum of the time it takes for a wireless signal from the terminal to be forwarded to the ground base station via the satellite and the time it takes for a wireless signal from the ground base station to be forwarded to the terminal via the satellite.

[0193] In a possible implementation, when the terminal receives a first common offset (common offset) indicated by the system, the RTT is the sum of the first common offset and the uplink advance TA of the terminal.

[0194] In a possible implementation, when the terminal does not receive the first common offset indicated by the system, the RTT is the TA of the terminal.

[0195] In an embodiment of the present application, in a non-terrestrial communication network NTN based on a transparent forwarding architecture, when a terminal obtains an RTT, the RTT may be calculated based on the TA of the terminal.

[0196] In an exemplary solution of an embodiment of the present application, if the current NTN is an NTN based on a transparent forwarding architecture and the system indicates a common offset, for example, by broadcasting or other means, the RTT between the terminal and the network side can be set to the common offset + the terminal's TA.

[0197] Alternatively, if the current NTN is an NTN based on a transparent forwarding architecture, the terminal may also calculate the RTT based on the terminal's TA and the first common offset. For example, the RTT may be obtained by adding the result of multiplying the first common offset by a coefficient (e.g., 1.2) to the terminal's TA. The embodiment of the present application does not limit the manner in which the terminal obtains the RTT based on the terminal's TA and the first common offset.

[0198] In an exemplary solution, the system may also indicate the commonoffset in other ways besides broadcasting, for example, through RRC signaling, downlink control information, etc. The embodiment of the present application does not limit the way in which the system indicates the commonoffset.

[0199] In another exemplary solution of the embodiment of the present application, if the current NTN is an NTN based on a transparent forwarding architecture and the system does not indicate a common offset, the terminal can directly use the terminal's TA as the RTT between the terminal and the network side.

[0200] Alternatively, if the current NTN is an NTN based on a transparent forwarding architecture, the terminal may also calculate the RTT based on the terminal's TA, for example, by multiplying the terminal's TA by a coefficient (e.g., 1.2) to obtain the aforementioned RTT. The embodiments of the present application do not limit the manner in which the terminal obtains the RTT based on the terminal's TA.

[0201] In a possible implementation, when the network where the terminal is located is an NTN based on a regenerative forwarding architecture, the RTT is a round-trip propagation delay of a wireless signal between the terminal and a satellite in the NTN.

[0202] Since satellites assume some or all of the base station functions in non-terrestrial communication networks (NTNs) based on a regenerative forwarding architecture, the round-trip delay between the terminal and the network side is the delay related to the round-trip propagation of the wireless signal between the terminal and the satellite. In other words, the above-mentioned RTT corresponds to the length of time it takes for the wireless signal sent from the terminal to propagate to the satellite.

[0203] In a possible implementation, the RTT is the TA of the terminal.

[0204] In an exemplary solution of the embodiment of the present application, if the current NTN is an NTN based on a regeneration and forwarding architecture, the terminal can directly use the TA of the terminal as the RTT between the terminal and the network side.

[0205] Alternatively, if the current NTN is based on a regenerative forwarding architecture, the terminal may also calculate the RTT based on the terminal's TA, for example, by multiplying the terminal's TA by a coefficient (e.g., 1.2) to obtain the aforementioned RTT. The embodiments of the present application do not limit the manner in which the terminal obtains the RTT based on the terminal's TA.

[0206] Step 504: After the terminal performs the uplink transmission, start a response time window timer corresponding to the uplink transmission based on the control parameter.

[0207] In an embodiment of the present application, after the terminal executes the uplink transmission corresponding to the uplink small data according to the TA, it can start the corresponding response time window timer of this uplink transmission based on the start time offset of the above-mentioned timer and / or the timer duration, and during the operation of the response time window timer, listen to the network side's response to this uplink transmission.

[0208] For example, when the control parameter includes a timer start time offset, the terminal starts the response time window timer in the subframe corresponding to the subframe in which the uplink transmission ends plus the start time offset. Optionally, in this case, the duration of the response time window timer can be a system-preconfigured duration (i.e., the initial timer duration).

[0209] For another example, when the control parameter includes a timer duration, after the uplink transmission ends and when the start time of the response time window timer arrives, the terminal starts a response time window timer with a running time equal to the timer duration. Optionally, in this case, the start time of the response time window timer may be a preset start time, for example, the start time of the response time window timer may be the fourth subframe after the end time of the uplink transmission.

[0210] For another example, when the above-mentioned control parameters include the start time offset and timer duration of the timer, the terminal starts the above-mentioned response time window timer on the subframe corresponding to the subframe where the above-mentioned uplink transmission ends plus the start time offset, and sets the duration of the response time window timer to the above-mentioned timer duration.

[0211] The embodiment of the present application discloses a method for transmitting small data in the uplink of a non-connected UE in an NTN. On the one hand, the UE's TA pre-compensation capability can be effectively utilized for uplink transmission. On the other hand, after the UE completes the uplink transmission using the configured uplink grant, the timing at which the UE starts the response window timer can be well adapted to the NTN scenario, thereby achieving the purpose of terminal power saving.

[0212] To sum up, in the scheme shown in the embodiment of the present application, for the response time window timer corresponding to the uplink transmission corresponding to the uplink small data, the terminal can more accurately determine the start time offset and / or timer duration of the timer based on the RTT between the terminal and the network side device, thereby more accurately controlling the time for monitoring the response from the network side, and then achieving accurate reception of the above response, thereby improving the transmission effect of the uplink small data. In addition, it can also avoid unnecessary monitoring of the downlink control signal by the terminal, thereby achieving the effect of power saving of the terminal.

[0213] In addition, in the solution shown in the embodiment of the present application, when a service link exists between the terminal and the network-side device, the terminal can combine positioning capabilities and ephemeris information to obtain the service link TA that needs to be compensated due to the distance influence of the service link in the NTN, and then obtain the terminal's TA based on the service link TA, thereby achieving accurate prediction of the TA required for the terminal to perform uplink transmission, minimizing the impact of the communication distance between the terminal and the satellite in the NTN network on the uplink transmission corresponding to the uplink small data, and improving the accuracy of the uplink transmission in the NTN network.

[0214] Based on the above Figure 5 In an exemplary solution of the embodiment shown, the process of transmitting small data using PUR by an NB-IoT or eMTC terminal in the IDLE state may be as follows:

[0215] For a UE with positioning capability and TA pre-compensation capability, the UE sends small data on the PUR based on the valid TA maintained by itself; or the UE determines the TA of the UE based on the GNSS positioning capability and ephemeris information, and / or the public TA broadcast by the network, and sends small data on the PUR. This process can refer to the above Figure 5 The contents of step 501 and step 502 in the embodiment shown are not described here in detail. After the UE completes the transmission based on the PUR, it determines the start time of the PUR response window timer based on the signal transmission round trip delay RTT between the UE and the network side.

[0216] The implementation process is as follows:

[0217] Step 1: The NB-IoT or eMTC UE receives an RRC release message from the network, indicating that the UE is released to the RRC IDLE state. The RRC release message includes a PUR-Config (PUR configuration); the UE in the RRC IDLE state uses the PUR to send uplink data.

[0218] Among them, for a UE with positioning capability and TA pre-compensation capability, the UE first determines its own TA before using the PUR to send uplink transmission, and uses the determined TA to send PUSCH on the PUR. The method for the UE to determine the TA is as follows:

[0219] Method 1: The UE does not need to verify the validity of the TA.

[0220] The UE determines its own TA based on GNSS positioning capabilities and ephemeris information, and / or the public TA broadcast by the network. For transparent forwarding NTN network architectures, the UE estimates the TA_service link corresponding to the service link based on positioning capabilities and ephemeris information. For example, if the network broadcasts the common TA for the NTN cell, the UE determines the compensated TA as TA = TA_service link + common TA. If the network does not broadcast the common TA, the UE determines the compensated TA as TA = TA_service link. For regenerative forwarding NTN network architectures, the UE estimates the TA_service link corresponding to the service link based on positioning capabilities and ephemeris information. The UE then determines the compensated TA as TA = TA_service link.

[0221] Method 2: The UE first verifies the validity of the TA.

[0222] If the verification result shows that the TA is valid, the UE uses the current maintenance TA value. If the verification result shows that the TA is invalid, the UE determines its own TA based on method 1.

[0223] For a UE that does not have the capability of performing TA pre-compensation based on positioning capability, the UE first performs TA validity verification. If the verification result shows that the TA is valid, the UE can use PUR to transmit data.

[0224] Step 2: Assuming that the last subframe used by the UE for PUSCH transmission using PUR is subframe n, the UE starts the PUR response window timer at subframe n+offset and monitors the PDCCH scrambled by PUR-RNTI during the PUR response window timer. The value of offset is:

[0225] offset=max(4, RTT); or, offset=RTT, where RTT is the RTT between the UE and the base station.

[0226] For the transparent forwarding NTN network architecture, RTT is the RTT between the UE and the terrestrial base station. It is determined as follows: if the network broadcasts a common offset, then RTT = TA + common offset, where the common offset is the network-compensated TA (i.e., the network-side UL timing advance offset relative to the UL timing). If the network does not broadcast a common offset, then RTT = TA.

[0227] For the regenerative forwarding NTN network architecture, RTT is the RTT between the UE and the satellite, that is, RTT = TA.

[0228] Step 3: During the PUR response window timer, if the UE receives a PDCCH scrambled with the PUR-RNTI and the PDCCH indicates an uplink grant for uplink retransmission, the UE retransmits on the uplink grant resources. Assuming that the last subframe used for the retransmitted PUSCH transmission is subframe n, the PUR response window timer is restarted at subframe n + offset. The offset is determined in the same manner as in step 3.

[0229] Please refer to Figure 6 , which shows a UE behavior timing diagram provided by an embodiment of the present application. In the above exemplary solution, the timing of UE uplink transmission, timer start, and response monitoring can refer to Figure 6 shown.

[0230] Based on the above Figure 5In an exemplary solution of the illustrated embodiment, after the UE completes PUR transmission, the length of the PUR response window timer may be determined (adjusted) based on the round-trip delay of signal transmission between the UE and the network.

[0231] The process of using PUR to transmit small data by an NB-IoT or eMTC terminal in IDLE state can be as follows:

[0232] Step 1: The NB-IoT or eMTC UE receives an RRC release message from the network, indicating that the UE should be released to the RRC IDLE state. The RRC release message contains the PUR-Config. The UE in the RRC IDLE state uses the PUR to send uplink data.

[0233] Step 2: Assuming that the last subframe used by the UE for PUSCH transmission using PUR is subframe n, the UE starts the PUR response window timer in subframe n+4 and monitors the PDCCH scrambled by PUR-RNTI during the PUR response window timer. The duration of the PUR response window timer is PUR-ResponseWindowSize+offset, where offset is the duration offset mentioned above, and the value of offset is:

[0234] offset=max(4, RTT)-4; or, offset=RTT-4.

[0235] The above PUR-ResponseWindowSize+offset is the initial timer duration set by the network.

[0236] Step 3. During the running of the PUR response window timer, if the UE receives a PDCCH scrambled by PUR-RNTI and the PDCCH indicates an uplink grant for uplink retransmission, the UE retransmits on the uplink grant resource. Assuming that the last subframe used for the retransmitted PUSCH transmission is subframe n, the PUR response window timer is restarted in subframe n+4.

[0237] Please refer to Figure 7 , which shows a UE behavior timing diagram provided by an embodiment of the present application. In the above exemplary solution, the timing of UE uplink transmission, timer start, and response monitoring can refer to Figure 7 shown.

[0238] Based on the above Figure 5 In an exemplary solution of the embodiment shown, the process of transmitting small data using CG resources by an NR terminal in the INACTIVE state may be as follows:

[0239] For UEs with positioning capabilities and TA pre-compensation capabilities, the UE sends small data on the CG based on its own valid TA or a TA determined based on GNSS positioning capabilities and ephemeris information, and / or the public TA broadcast by the network. After the UE completes the CG transmission, the start time of the first response window timer is determined based on the round-trip signal transmission delay between the UE and the network.

[0240] The implementation process is as follows:

[0241] Step 1: The NR UE receives an RRC release message from the network, indicating that the UE is released to the RRC INACTIVE state. The RRC release message contains a CG configuration, which is used by the UE to transmit small data in the RRC INACTIVE state. The UE in the RRC INACTIVE state uses the CG to send uplink data.

[0242] For a UE with both positioning capability and TA pre-compensation capability, the UE determines its own TA before using the CG to send uplink transmissions, and uses the TA to send PUSCH on the CG. The method for the UE to determine the TA is as follows:

[0243] Method 1: The UE does not need to verify the validity of the TA. The UE determines its own TA based on the GNSS positioning capability and ephemeris information, and / or the public TA broadcast by the network.

[0244] For the transparent forwarding NTN network architecture, the UE estimates the TA_service link corresponding to the service link based on positioning capabilities and ephemeris information: if the network broadcasts the common TA for the NTN cell, the UE determines the compensated TA as TA = TA_service link + common TA; if the network does not broadcast the common TA, the UE determines the compensated TA as TA = TA_service link.

[0245] For the regenerative forwarding NTN network architecture, the UE estimates the TA_service link corresponding to the service link based on the positioning capability and ephemeris information, and the UE determines the compensated TA as TA=TA_service link.

[0246] Method 2: The UE first verifies the validity of the TA. If the verification result shows that the TA is valid, the UE uses the current maintenance TA value. If the verification result shows that the TA is invalid, the UE determines its own TA based on Method 1.

[0247] For UE that does not have the capability to perform TA pre-compensation based on positioning capability, the UE first performs TA validity verification. If the verification result shows that the TA is valid, the UE can use CG to transmit data.

[0248] Step 2, the UE starts the first response window timer after a time offset offset after the first repetition (repeptition) or the last repetition transmission of the PUSCH using the CG, and monitors the PDCCH encrypted by the first RNTI during the operation of the first response window timer. The duration of the first response window timer is configured by the network, and the first RNTI is the UE-specific RNTI. The value of offset is offset = RTT; or offset is RTT, and the maximum value in a specific time interval, wherein the specific time interval can be the time interval from the moment of completing the first repetition (repeptition) or the last repetition transmission of the above-mentioned PUSCH to the next PDCCH monitoring opportunity; wherein the RTT is the RTT between the UE and the base station.

[0249] For the transparent forwarding NTN network architecture, RTT is the RTT between the UE and the terrestrial base station. It is determined as follows: if the network broadcasts a common offset, then RTT = TA + common offset, where the common offset is the network-compensated TA (i.e., the network-side UL timing advance offset relative to the UL timing). If the network does not broadcast a common offset, then RTT = TA.

[0250] For the regenerative forwarding NTN network architecture, RTT is the RTT between the UE and the satellite, that is, RTT = TA.

[0251] Step 3: During the operation of the first response window timer, if the UE receives a PDCCH scrambled by the first RNTI and the PDCCH indicates an uplink grant for uplink retransmission, the UE stops the first response window timer upon receiving the PDCCH. The UE retransmits on the uplink grant resources and restarts the first response window timer after a time offset after completing the PUSCH transmission.

[0252] Please refer to Figure 8 , which shows a UE behavior timing diagram provided by an embodiment of the present application. In the above exemplary solution, the timing of UE uplink transmission, timer start, and response monitoring can refer to Figure 8 shown.

[0253] Based on the above Figure 5In an exemplary solution of the illustrated embodiment, after the UE completes the CG transmission, the duration of the first response window timer can be determined based on the round-trip delay of the signal transmission between the UE and the network.

[0254] The implementation process is as follows:

[0255] Step 1: The NR UE receives an RRC release message from the network, indicating that the UE is released to the RRC INACTIVE state. The RRC release message contains a CG configuration, which is used by the UE to transmit small data in the RRC INACTIVE state. The UE in the RRC INACTIVE state uses the CG to send uplink data.

[0256] Step 2: The UE starts a first response window timer after completing the first retransmission of the PUSCH using the CG, or the first time unit (such as a time symbol) after the last retransmission, or the first PDCCH monitoring opportunity, and monitors the PDCCH scrambled by the first RNTI during the operation of the first response window timer. The duration of the first response window timer is the first duration + offset, where the first duration is configured by the network, and the offset is the difference between the RTT and a specific time interval; or the offset is the difference between the maximum value of the RTT and the specific time interval and the specific time interval (or, the offset is the maximum value between the difference between the RTT and the specific time interval and 0); wherein the specific time interval can be the time interval between the moment of completing the first retransmission (repeptition) or the last retransmission of the PUSCH and the next PDCCH monitoring opportunity; the RTT is the RTT between the UE and the base station. The first RNTI is a UE-specific RNTI.

[0257] Step 3: During the operation of the first response window timer, if the UE receives a PDCCH encrypted by the first RNTI and the PDCCH indicates an uplink grant for uplink retransmission, the UE stops the first response window timer upon receiving the PDCCH. The UE retransmits on the uplink grant resource and starts the first response window timer at the first time unit (such as a time symbol) after completing the first repetition (repetition) of the PUSCH or the last repetition or the first PDCCH monitoring opportunity, and monitors the PDCCH encrypted by the first RNTI during the operation of the first response window timer.

[0258] Please refer to Figure 9, which shows a UE behavior timing diagram provided by an embodiment of the present application. In the above exemplary solution, the timing of UE uplink transmission, timer start, and response monitoring can refer to Figure 9 shown.

[0259] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0260] Please refer to Figure 10 , which shows a block diagram of a timer starting device provided by an embodiment of the present application. The device is used in a terminal and has the function of implementing the steps executed by the terminal in the above-mentioned timer starting method. Figure 10 As shown, the device may include:

[0261] The parameter determination device 1001 is used to determine a control parameter of a response time window timer based on the round-trip delay RTT between the terminal and the network side device; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission corresponding to the uplink small data and the start time of the response time window timer for the uplink transmission;

[0262] The timer starting module 1002 is configured to start a response time window timer corresponding to the uplink transmission based on the control parameter after the terminal performs the uplink transmission.

[0263] In one possible implementation, when the uplink transmission is a transmission based on a pre-configured uplink resource PUR, or an uplink retransmission indicated by a physical downlink control channel PDCCH scrambled based on a PUR radio network temporary identifier PUR-RNTI, the start time offset is the maximum value of the RTT and the first time offset, or the start time offset is the RTT.

[0264] In a possible implementation manner, the value of the first time offset is a predefined value.

[0265] In a possible implementation manner, the first time offset is 4 subframes.

[0266] In a possible implementation, when the uplink transmission is performed based on the configured authorized CG resources, or is an uplink retransmission indicated by the PDCCH scrambled based on the first RNTI, the start time offset is the maximum value of the RTT and the second time offset, or the start time offset is the RTT;

[0267] The first RNTI is used to indicate the retransmission scheduling for CG transmission in RRC_INACTIVE state.

[0268] In a possible implementation manner, the value of the second time offset is a predefined value.

[0269] In a possible implementation, the value of the second time offset is a time interval between the terminal completing the first repetition of the uplink transmission and the next physical downlink control channel PDCCH monitoring opportunity;

[0270] Alternatively, the value of the second time offset is a time interval between the last repeated transmission of the uplink transmission completed by the terminal and the next PDCCH monitoring opportunity.

[0271] In a possible implementation, the timer duration is determined based on a duration offset and an initial timer duration, where the initial timer duration is configured by a network.

[0272] In a possible implementation, the timer duration is the sum of the duration offset and the initial timer duration.

[0273] In a possible implementation, when the uplink transmission is a transmission performed based on a PUR, or an uplink retransmission indicated by a physical downlink control channel PDCCH scrambled based on a PUR radio network temporary identifier PUR-RNTI,

[0274] The duration offset is the difference between the third time offset and the maximum value of the RTT and the third time offset; or the duration offset is the difference between the RTT and the third time offset.

[0275] In a possible implementation manner, the value of the third time offset is a predefined value.

[0276] In a possible implementation, the third time offset is 4 subframes.

[0277] In a possible implementation, when the uplink transmission is a transmission performed based on CG resources, or an uplink retransmission indicated by a PDCCH scrambled based on the first RNTI,

[0278] The duration offset is the difference between the maximum of the RTT and the fourth time offset and the fourth time offset;

[0279] Alternatively, the duration offset is the difference between the RTT and a fourth time offset.

[0280] In a possible implementation manner, the value of the fourth time offset is a predefined value.

[0281] In a possible implementation, the value of the fourth time offset is a time interval between the terminal completing the first repeated transmission of the uplink transmission and the next PDCCCH monitoring opportunity;

[0282] Alternatively, the value of the fourth time offset is a time interval between the last repeated transmission of the uplink transmission completed by the terminal and the next PDCCCH monitoring opportunity.

[0283] In a possible implementation, the hybrid automatic repeat request HARQ process used for the uplink transmission is a HARQ process with an uplink HARQ retransmission function enabled.

[0284] In a possible implementation, when the network where the terminal is located is a non-terrestrial communication network NTN based on a transparent forwarding architecture, the RTT is a round-trip propagation delay of a wireless signal between the terminal and a ground base station in the NTN.

[0285] In a possible implementation, when the terminal receives the first common offset indicated by the system, the RTT is the sum of the first common offset and the uplink advance TA of the terminal;

[0286] When the terminal does not receive the first common offset indicated by the system, the RTT is the TA of the terminal.

[0287] In a possible implementation, when the network where the terminal is located is an NTN based on a regenerative forwarding architecture, the RTT is a round-trip propagation delay of a wireless signal between the terminal and a satellite in the NTN.

[0288] In a possible implementation manner, the RTT is the TA of the terminal.

[0289] In a possible implementation, the apparatus further includes:

[0290] A first uplink advance acquisition module is configured to acquire a serving link TA of the terminal based on the positioning capability and ephemeris information before the terminal performs the uplink transmission when the terminal has positioning capability and TA pre-compensation capability;

[0291] The second uplink advance acquisition module is configured to acquire the TA of the terminal based on the serving link TA.

[0292] In a possible implementation, the second uplink early acquisition module is configured to:

[0293] When the network where the terminal is located is an NTN based on a transparent forwarding architecture, and the terminal receives a public TA indicated by the system, the sum of the service link TA and the public TA is used as the TA of the terminal;

[0294] When the network where the terminal is located is an NTN based on a transparent forwarding architecture and the terminal does not receive a public TA indicated by the system, the service link TA is used as the TA of the terminal.

[0295] In a possible implementation, the second uplink advance acquisition module is configured to use the serving link TA as the TA of the terminal when the network where the terminal is located is an NTN based on a regeneration and forwarding architecture.

[0296] In one possible implementation, the first uplink advance acquisition module is configured to, before the terminal performs the uplink transmission, when the terminal has positioning capability and TA pre-compensation capability, obtain the service link TA of the terminal based on the positioning capability and ephemeris information without performing validity verification on the TA maintained by the terminal.

[0297] In a possible implementation, the apparatus further includes:

[0298] A verification module is configured to verify the validity of the TA maintained by the terminal before the terminal performs the uplink transmission;

[0299] The first uplink advance acquisition module is configured to acquire the service link TA of the terminal based on the positioning capability and ephemeris information when the TA maintained by the terminal fails the validity check and the terminal has positioning capability and TA pre-compensation capability.

[0300] In a possible implementation, the apparatus further includes:

[0301] The third uplink advance acquisition module is configured to use the TA maintained by the terminal as the TA of the terminal when the TA maintained by the terminal passes the validity check.

[0302] In a possible implementation manner, the terminal is a terminal in a non-radio resource control (RRC) activated state.

[0303] To sum up, in the scheme shown in the embodiment of the present application, for the response time window timer corresponding to the uplink transmission corresponding to the uplink small data, the terminal can more accurately determine the start time offset and / or timer duration of the timer based on the RTT between the terminal and the network side device, thereby more accurately controlling the time for monitoring the response from the network side, and then achieving accurate reception of the above response, thereby improving the transmission effect of the uplink small data. In addition, it can also avoid unnecessary monitoring of the downlink control signal by the terminal, thereby achieving the effect of power saving of the terminal.

[0304] Please refer to Figure 11 , which shows a block diagram of an uplink early acquisition device provided by an embodiment of the present application. The device is used in a terminal and has the function of implementing the steps executed by the terminal in the above-mentioned timer start / uplink early acquisition method. Figure 11 As shown, the device may include:

[0305] A first uplink advance acquisition module 1101 is configured to, before the terminal performs uplink transmission corresponding to uplink small data, acquire a serving link TA of the terminal based on the positioning capability and ephemeris information when the terminal has positioning capability and TA pre-compensation capability;

[0306] The second uplink early acquisition module 1102 is configured to acquire the TA of the terminal based on the serving link TA.

[0307] In summary, in the solution shown in the embodiment of the present application, when a service link exists between the terminal and the network-side device, the terminal can combine the positioning capability and ephemeris information to obtain the service link TA that needs to be compensated due to the distance influence of the service link in the NTN, and then obtain the terminal's TA based on the service link TA, thereby achieving accurate prediction of the TA required for the terminal to perform uplink transmission, minimizing the impact of the communication distance between the terminal and the satellite in the NTN network on the uplink transmission corresponding to the uplink small data, and improving the accuracy of the uplink transmission in the NTN network. In addition, it can also avoid the terminal from unnecessary monitoring of the downlink control signal, thereby achieving the effect of terminal power saving.

[0308] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0309] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0310] Please refer to Figure 12 , which shows a schematic diagram of the structure of a computer device 1200 provided in one embodiment of the present application. The computer device 1200 may include: a processor 1201, a receiver 1202, a transmitter 1203, a memory 1204 and a bus 1205.

[0311] The processor 1201 includes one or more processing cores. The processor 1201 executes various functional applications and information processing by running software programs and modules.

[0312] The receiver 1202 and the transmitter 1203 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0313] The memory 1204 is connected to the processor 1201 via a bus 1205. The memory 1204 can be used to store computer programs, and the processor 1201 is used to execute the computer programs to implement the various steps performed by the terminal device in the above method embodiment.

[0314] In addition, the memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only memory, erasable programmable read-only memory, static random access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0315] In an exemplary embodiment, the computer device includes a processor, a memory, and a transceiver (the transceiver may include a receiver and a transmitter, the receiver is used to receive information, and the transmitter is used to send information);

[0316] In a possible implementation, when the computer device is implemented as a terminal,

[0317] The processor is configured to determine a control parameter of a response time window timer based on a round-trip delay (RTT) between the terminal and the network-side device; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission corresponding to the uplink small data and the start time of the response time window timer for the uplink transmission;

[0318] The processor is further configured to start a response time window timer corresponding to the uplink transmission based on the control parameter after the terminal performs the uplink transmission.

[0319] In another possible implementation, when the computer device is implemented as a terminal,

[0320] The processor is configured to, before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability, obtain a serving link TA of the terminal based on the positioning capability and ephemeris information;

[0321] The processor is further configured to obtain the TA of the terminal based on the service link TA.

[0322] The various steps of the method executed by the terminal in the embodiment of the present application can refer to the above Figure 3 、 Figure 4 or Figure 5 All or part of the steps executed by the terminal in the illustrated embodiment will not be described in detail here.

[0323] The present application also provides a computer-readable storage medium in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above Figure 3 、 Figure 4 or Figure 5 In the method shown, each step is executed by the terminal.

[0324] The present application also provides a computer program product or computer program, the computer program product or computer program including computer instructions, the computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the above-mentioned Figure 3 、 Figure 4 or Figure 5 In the method shown, each step is executed by the terminal.

[0325] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0326] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A timer starting method, characterized in that: The method is executed by a terminal, and includes: Before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability, obtaining a serving link TA of the terminal based on the positioning capability and ephemeris information; Based on the service link TA, obtaining the TA of the terminal; Determining a control parameter of a response time window timer based on a round-trip time delay (RTT) between the terminal and a network-side device; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission and the start time of the response time window timer for the uplink transmission; when the network where the terminal is located is a non-terrestrial communication network (NTN) based on a transparent forwarding architecture, and the terminal receives a first common offset indicated by the system, the RTT = the TA of the terminal + the first common offset; After the terminal performs the uplink transmission, a response time window timer corresponding to the uplink transmission is started based on the control parameter.

2. The method according to claim 1, characterized in that When the uplink transmission is a transmission based on a pre-configured uplink resource PUR, or an uplink retransmission indicated by a physical downlink control channel PDCCH scrambled by a PUR radio network temporary identifier PUR-RNTI, The startup time offset is the maximum value of the RTT and the first time offset; Alternatively, the start time offset is the RTT.

3. The method according to claim 2, characterized in that The value of the first time offset is a predefined value.

4. The method according to claim 3, characterized in that The first time offset is 4 subframes.

5. The method according to claim 1, wherein When the uplink transmission is a transmission performed based on the configuration authorized CG resource, or an uplink retransmission indicated by the PDCCH scrambled based on the first RNTI, The startup time offset is the maximum value of the RTT and the second time offset; Alternatively, the start time offset is the RTT; The first RNTI is used to indicate the retransmission scheduling for CG transmission in RRC_INACTIVE state.

6. The method according to claim 5, characterized in that The value of the second time offset is a predefined value.

7. The method according to claim 5 or 6, characterized in that The value of the second time offset is a time interval between the first repeated transmission of the uplink transmission completed by the terminal and the next physical downlink control channel PDCCH monitoring opportunity; Alternatively, the value of the second time offset is a time interval between the last repeated transmission of the uplink transmission completed by the terminal and the next PDCCH monitoring opportunity.

8. The method according to claim 1, characterized in that The timer duration is determined based on the duration offset and the initial timer duration, and the initial timer duration is configured by the network.

9. The method according to claim 8, characterized in that The timer duration is the sum of the duration offset and the initial timer duration.

10. The method according to claim 8 or 9, characterized in that When the uplink transmission is a transmission based on a PUR, or an uplink retransmission indicated by a physical downlink control channel PDCCH scrambled by a PUR radio network temporary identifier PUR-RNTI, The duration offset is a difference between a maximum of the RTT and a third time offset and the third time offset; Alternatively, the duration offset is the difference between the RTT and a third time offset.

11. The method according to claim 10, characterized in that The value of the third time offset is a predefined value.

12. The method according to claim 11, characterized in that The third time offset is 4 subframes.

13. The method according to claim 8 or 9, characterized in that When the uplink transmission is a transmission performed based on CG resources, or an uplink retransmission indicated by a PDCCH scrambled based on the first RNTI, The duration offset is a difference between a maximum value of the RTT and a fourth time offset and the fourth time offset; Alternatively, the duration offset is the difference between the RTT and a fourth time offset.

14. The method according to claim 13, characterized in that The value of the fourth time offset is a predefined value.

15. The method according to claim 13 or 14, characterized in that The value of the fourth time offset is the time interval between the terminal completing the first repeated transmission of the uplink transmission and the next PDCCCH monitoring opportunity; Alternatively, the value of the fourth time offset is a time interval between the last repeated transmission of the uplink transmission completed by the terminal and the next PDCCCH monitoring opportunity.

16. The method according to any one of claims 1 to 15, characterized in that The hybrid automatic repeat request HARQ process used for uplink transmission is a HARQ process with an uplink HARQ retransmission function enabled.

17. The method according to claim 1, wherein When the network where the terminal is located is a non-terrestrial communication network NTN based on a transparent forwarding architecture, and the terminal does not receive the first common offset indicated by the system, the RTT is the TA of the terminal.

18. The method according to any one of claims 1 to 17, characterized in that: When the network where the terminal is located is an NTN based on a regenerative forwarding architecture, the RTT is a round-trip propagation delay of a wireless signal between the terminal and a satellite in the NTN.

19. The method according to claim 18, characterized in that The RTT is the TA of the terminal.

20. The method according to any one of claims 1 to 19, characterized in that The acquiring the TA of the terminal based on the service link TA includes: When the network where the terminal is located is an NTN based on a transparent forwarding architecture, and the terminal receives a public TA indicated by the system, the sum of the service link TA and the public TA is used as the TA of the terminal; When the network where the terminal is located is an NTN based on a transparent forwarding architecture and the terminal does not receive a public TA indicated by the system, the service link TA is used as the TA of the terminal.

21. The method according to any one of claims 1 to 19, characterized in that The acquiring the TA of the terminal based on the service link TA includes: When the network where the terminal is located is an NTN based on a regeneration and forwarding architecture, the service link TA is used as the TA of the terminal.

22. The method according to any one of claims 1 to 21, characterized in that Before the terminal performs the uplink transmission, when the terminal has a positioning capability and a TA pre-compensation capability, acquiring a serving link TA of the terminal based on the positioning capability and ephemeris information includes: Before the terminal performs the uplink transmission, when the terminal has positioning capability and TA pre-compensation capability, the service link TA of the terminal is acquired based on the positioning capability and ephemeris information without performing validity verification on the TA maintained by the terminal.

23. The method according to any one of claims 1 to 21, characterized in that Before the terminal performs the uplink transmission, when the terminal has positioning capability and TA pre-compensation capability, before acquiring the serving link TA of the terminal based on the positioning capability and ephemeris information, the method further includes: Before the terminal performs the uplink transmission, performing a validity check on the TA maintained by the terminal; When the terminal has a positioning capability and a TA pre-compensation capability, acquiring the service link TA of the terminal based on the positioning capability and ephemeris information includes: When the TA maintained by the terminal fails the validity check and the terminal has positioning capability and TA pre-compensation capability, the service link TA of the terminal is acquired based on the positioning capability and ephemeris information.

24. The method according to claim 23, wherein The method further comprises: When the TA maintained by the terminal passes the validity check, the TA maintained by the terminal is used as the TA of the terminal.

25. The method according to any one of claims 1 to 24, characterized in that The terminal is a terminal in a non-radio resource control RRC activated state.

26. A timer starting device, characterized in that: The device is used in a terminal, and includes: A first uplink advance acquisition module is configured to acquire a serving link TA of the terminal based on the positioning capability and ephemeris information before the terminal performs uplink transmission corresponding to uplink small data, when the terminal has positioning capability and TA pre-compensation capability; A second uplink advance acquisition module, configured to acquire the TA of the terminal based on the serving link TA; A parameter determination device, configured to determine a control parameter of a response time window timer based on a round-trip delay (RTT) between the terminal and a network-side device; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission and the start time of the response time window timer for the uplink transmission; when the network where the terminal is located is a non-terrestrial communication network (NTN) based on a transparent forwarding architecture, and the terminal receives a first common offset indicated by the system, the RTT = the TA of the terminal + the first common offset; A timer starting module is used to start a response time window timer corresponding to the uplink transmission based on the control parameter after the terminal performs the uplink transmission.

27. A computer device, characterized in that: The computer device is implemented as a terminal, and the computer device includes a processor, a memory, and a transceiver; The processor is configured to, before the terminal performs uplink transmission corresponding to uplink small data, obtain a service link TA of the terminal based on the positioning capability and ephemeris information when the terminal has positioning capability and TA pre-compensation capability; and obtain a TA of the terminal based on the service link TA; The processor is further configured to determine a control parameter of a response time window timer based on a round-trip delay (RTT) between the terminal and a network-side device; the control parameter includes at least one of a start time offset of the timer and a timer duration; the start time offset of the timer is the time interval between the end time of the uplink transmission and the start time of the response time window timer for the uplink transmission; when the network where the terminal is located is a non-terrestrial communication network (NTN) based on a transparent forwarding architecture, and the terminal receives a first common offset indicated by the system, the RTT = the TA of the terminal + the first common offset; The processor is further configured to start a response time window timer corresponding to the uplink transmission based on the control parameter after the terminal performs the uplink transmission.

28. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the timer starting method according to any one of claims 1 to 25.

Images